z/OS


MVS System Messages

Volume 6 (GOS - IEA)

SA22-7636-24
 Note
Before using this information and the product it supports, read the information in “Notices” on page 915.

This edition applies to version 1, release 13, modification 0 of IBM z/OS (product number 5694-A01) and to all
subsequent releases and modifications until otherwise indicated in new editions.
This edition replaces SA22-7636-23
© Copyright IBM Corporation 1988, 2012.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
 Contents
About this document . . . . . . . . . v Chapter 6. HWI messages . . . . . . 67
Who should use documentation for MVS System
Messages . . . . . . . . . . . . . . . vi Chapter 7. HZR messages . . . . . . 77
How to use these documents . . . . . . . . vi
Where to find more information . . . . . . . vi
Chapter 8. HZS messages . . . . . . 85
Where to find the most current message
Message output from DISPLAY parameter of
information . . . . . . . . . . . . . vii
MODIFY command or HZSPRMxx . . . . . . 133
Information updates on the web . . . . . . vii
HZS0200I - DISPLAY SUMMARY message
Using LookAt to look up message explanations vii
output. . . . . . . . . . . . . . . 133
The z/OS Basic Skills Information Center . . . viii
HZS0201I - DISPLAY DETAIL message output 133
HZS0202I - DISPLAY POLICY DETAIL message
How to send your comments to IBM . . ix output. . . . . . . . . . . . . . . 135
If you have a technical problem . . . . . . . . ix HZS0204I - DISPLAY POLICY SUMMARY
message output. . . . . . . . . . . . 135
Summary of changes . . . . . . . . . xi HZS0203I - DISPLAY STATUS message output 135
Changes made in z/OS Version 1 Release 13, as
updated September 2012 . . . . . . . . . . xi Chapter 9. IAR messages . . . . . . 137
Changes made in z/OS Version 1 Release 13, as
updated April 2012 . . . . . . . . . . . . xi
Chapter 10. IARH messages . . . . . 155
Changes made in z/OS Version 1 Release 13 . . . xi
Changes made in z/OS Version 1 Release 12 . . . xi
Changes made in z/OS Version 1 Release 11 (as Chapter 11. IAZ messages . . . . . . 163
updated April 2010) . . . . . . . . . . . xii
Changes made in z/OS Version 1 Release 11 . . . xii | Chapter 12. ICM messages . . . . . 197

Chapter 1. Introduction . . . . . . . . 1 Chapter 13. ICP messages . . . . . . 199

Message format . . . . . . . . . . . . . 2
Format of the message body . . . . . . . . 2 Chapter 14. ICT messages . . . . . . 201
Messages sent to MCS/SMCS consoles . . . . 3
Messages sent to hardcopy log in JES2 system . . 4
Messages sent to hardcopy log in JES3 system . . 6
Chapter 15. ICU messages . . . . . . 219
Messages sent to the job log, to other data sets,
and to display terminals . . . . . . . . . 7 Chapter 16. IDA messages . . . . . . 243
Truncated data in multi-line messages . . . . . 7
Message description . . . . . . . . . . . . 8 Chapter 17. IDAHC messages . . . . 251
Description items . . . . . . . . . . . . 8
Routing codes . . . . . . . . . . . . . 9 Chapter 18. IDAI messages . . . . . 253
Descriptor codes. . . . . . . . . . . . 13
Message directory . . . . . . . . . . . . 16
Building your own message library . . . . . . 27 Chapter 19. IDAT messages . . . . . 255
Basic documents. . . . . . . . . . . . 27
Optional documents . . . . . . . . . . 27 Chapter 20. IDC messages . . . . . . 261
Translating messages . . . . . . . . . . . 27
Finding changes to system message texts . . . . 27 Chapter 21. IEA messages . . . . . . 629

Chapter 2. GOS messages . . . . . . 29 Chapter 22. IEAH messages . . . . . 887

Chapter 3. GPM messages . . . . . . 35 Chapter 23. IEATH messages . . . . 889

| Chapter 4. GSL messages . . . . . . 41 Chapter 24. IEAVEH messages . . . . 893

Chapter 5. HIS messages . . . . . . . 43 Chapter 25. IEAVTRH messages . . . 907

© Copyright IBM Corp. 1988, 2012 iii

Accessibility . . . . . . . . . . . . 913 Notices . . . . . . . . . . . . . . 915
Using assistive technologies . . . . . . . . 913 Policy for unsupported hardware. . . . . . . 916
Keyboard navigation of the user interface . . . . 913 Trademarks . . . . . . . . . . . . . . 916
z/OS information . . . . . . . . . . . . 913

iv z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

About this document
This information supports z/OS (5694-A01).

MVS™ System Messages primarily describe messages that are issued to the system
operator at the system console and system messages that are logged. These include
the following messages:
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 documents.
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 indicate the range of message prefixes in
the documents:
v z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631
v z/OS MVS System Messages, Vol 2 (ARC-ASA), SA22-7632
v z/OS MVS System Messages, Vol 3 (ASB-BPX), SA22-7633
v z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634
v z/OS MVS System Messages, Vol 5 (EDG-GFS), SA22-7635
v z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
v z/OS MVS System Messages, Vol 7 (IEB-IEE), SA22-7637
v z/OS MVS System Messages, Vol 8 (IEF-IGD), SA22-7638
v z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
v z/OS MVS System Messages, Vol 10 (IXC-IZP), SA22-7640

If you do not know which document describes a particular message, try using
LookAt (see “Using LookAt to look up message explanations” on page vii). Here
are some of the other types of messages on that bookshelf:
v z/OS MVS Dump Output Messages, SA22-7590
v z/OS MVS System Codes, SA22-7626
v z/OS and z/VM HCD Messages, SC33-7986
v z/OS JES2 Messages, SA22-7537
v z/OS JES3 Messages, SA22-7552
v z/OS TSO/E Messages, SA22-7786
v z/OS UNIX System Services Messages and Codes, SA22-7807
For a list of message documents sorted by message prefix, see “Message directory”
on page 16.

This document also contains the routing and descriptor codes that IBM assigns to
the messages that z/OS components, subsystems, and products issue. Routing and
descriptor codes are specified by the ROUTCDE and DESC keyword parameters on
WTO and WTOR macros, which are the primary methods that programs use to
© Copyright IBM Corp. 1988, 2012 v
 issue messages. The routing code identifies where a message will be displayed. The
descriptor code identifies the significance of the message and the color of the
message on operator consoles with color.

Who should use documentation for MVS System Messages

The system messages documents are for 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 documents

The system messages contain descriptions of messages, along with the following
topics:
v “Building your own message library” on page 27 tells how to create a
customized message library.
v “Message directory” on page 16 lists all message prefixes and the documents
containing the message descriptions.
v Chapter 1, “Introduction,” on page 1 describes how the system issues messages,
where it places them, and their formats.
v “Routing codes” on page 9 and “Descriptor codes” on page 13 contain an
introduction to routing and descriptor codes. These sections describe:
– The meaning of each code
– How to specify these codes
– How the system uses these codes
For information on using routing and descriptor codes to route messages, see
z/OS MVS Planning: Operations.

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 “Message description” on page 8.

Where to find more information

Where necessary, the message documents reference information in other books,
using shortened versions of the book title. For complete titles and order numbers
of the books for all products that are part of z/OS, see z/OS Information Roadmap.

Many message descriptions refer to the following terms. You need to consult the
reference listed below for more information:
v Data areas and control blocks: See z/OS MVS Data Areas in z/OS Internet
Library at http://www.ibm.com/systems/z/os/zos/bkserv/.
v Dumps: For examples of ABEND, stand-alone, and SVC dumps and how to read
them, see z/OS MVS Diagnosis: Tools and Service Aids. For examples of component
output from dumps and how to read and request it, see z/OS MVS Diagnosis:
Reference.

vi z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 v Identification of a component, subsystem, or product: See the z/OS 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 z/OS MVS System Codes.
v Logrec data set error records: For the formatted records, see z/OS 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 z/OS MVS Diagnosis: Tools and Service
Aids.
v hardware: Use the appropriate Principles of Operation document for the hardware
you have installed.

Where to find the most current message information

The MVS System Messages documents are cumulative. As messages are added to
the system they are added to the documents. Similarly, when messages are
changed on the system, they are changed in the documents. However, when a
message is deleted from the system (no longer issued), the message is not deleted
from the document. This means that users can look in the most recent message
documents for the most current descriptions of system messages.

To find the most current edition of a document, you can look on the Web. Point
your browser to the z/OS home page and click on Library:
http://www.ibm.com/systems/z/os/zos/

When you are in the z/OS library area, use the messages and codes database to
search for the message ID you are interested in.

Information updates on the web

For the latest information updates that have been provided in PTF cover letters
and Documentation APARs for z/OS, see the online document at:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/Shelves/ZDOCAPAR.

This document is updated weekly and lists documentation changes before they are
incorporated into z/OS publications.

Using LookAt to look up message explanations

LookAt is an online facility that lets you look up explanations for most of the IBM
messages you encounter, as well as for some system abends and codes. Using
LookAt to find information is faster than a conventional search because in most
cases LookAt goes directly to the message explanation.

You can use LookAt from these locations to find IBM message explanations for
z/OS® elements and features, z/VM®, z/VSE, and Clusters for AIX® and Linux:
v The Internet. You can access IBM message explanations directly from the LookAt
Web site at www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/.
v Your z/OS TSO/E host system. You can install code on your z/OS systems to
access IBM message explanations using LookAt from a TSO/E command line
(for example: TSO/E prompt, ISPF, or z/OS UNIX System Services).
v Your Microsoft Windows workstation. You can install LookAt directly from the
z/OS and Software Products DVD Collection (SK3T-4271) and use it from the

About this document vii

 resulting Windows graphical user interface (GUI). The command prompt (also
known as the DOS > command line) version can still be used from the directory
in which you install the Windows version of LookAt.
v Your wireless handheld device. You can use the LookAt Mobile Edition from
www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/lookatm.html with a
handheld device that has wireless access and an Internet browser.

You can obtain code to install LookAt on your host system or Microsoft Windows
workstation from:
v The z/OS and Software Products DVD Collection (SK3T-4271).
v The LookAt Web site (click Download and then select the platform, release,
collection, and location that suit your needs). More information is available in
the LOOKAT.ME files available during the download process.

The z/OS Basic Skills Information Center

The z/OS Basic Skills Information Center is a Web-based information resource
intended to help users learn the basic concepts of z/OS, the operating system that
runs most of the IBM mainframe computers in use today. The Information Center
is designed to introduce a new generation of Information Technology professionals
to basic concepts and help them prepare for a career as a z/OS professional, such
as a z/OS system programmer.

Specifically, the z/OS Basic Skills Information Center is intended to achieve the
following objectives:
v Provide basic education and information about z/OS without charge
v Shorten the time it takes for people to become productive on the mainframe
v Make it easier for new people to learn z/OS.

To access the z/OS Basic Skills Information Center, open your Web browser to the
following Web site, which is available to all users (no login required):
http://publib.boulder.ibm.com/infocenter/zos/basics/index.jsp

viii z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

How to send your comments to IBM
We appreciate your input on this publication. Feel free to comment on the clarity,
accuracy, and completeness of the information or give us any other feedback that
you might have.

Use one of the following methods to send us your comments:

1. Send an email to [email protected]
2. Visit the Contact z/OS web page at http://www.ibm.com/systems/z/os/zos/
webqs.html
3. Mail the comments to the following address:
IBM Corporation
Attention: MHVRCFS Reader Comments
Department H6MA, Building 707
2455 South Road
Poughkeepsie, NY 12601-5400
U.S.A.
4. Fax the comments to us as follows:
From the United States and Canada: 1+845+432-9405
From all other countries: Your international access code +1+845+432-9405

Include the following information:

v Your name and address
v Your email address
v Your telephone or fax number
v The publication title and order number:
z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)
SA22-7636-24
v The topic and page number related to your comment
v The text of your comment.
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.

IBM or any other organizations will only use the personal information that you
supply to contact you about the issues that you submit.

If you have a technical problem

Do not use the feedback methods listed above. Instead, do one of the following:
v Contact your IBM service representative
v Call IBM technical support
v Visit the IBM support portal at http://www.ibm.com/systems/z/support/

© Copyright IBM Corp. 1988, 2012 ix

x z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)
Summary of changes
This document contains terminology, maintenance, and editorial changes to
improve consistency and retrievability. Technical changes or additions to the text
and illustrations are indicated by a vertical line to the left of the change.

New, changed, or deleted messages can affect your system's automation routines.
To ensure that your installation's automation routines are current, review the new,
changed, and deleted messages listed in z/OS Summary of Message and Interface
Changes. z/OS Summary of Message and Interface Changes is available on the z/OS
Collection, SK3T-4271 and in the z/OS Internet library at:
http://www.ibm.com/servers/eserver/zseries/zos/bkserv/

Changes made in z/OS Version 1 Release 13, as updated September

2012
This document contains information previously presented in z/OS MVS System
Messages, Vol 6 (GOS-IEA), SA22-7636-23, which supports z/OS Version 1 Release
13.

For a comprehensive list of message changes, see z/OS Summary of Message and
Interface Changes.

Changes made in z/OS Version 1 Release 13, as updated April 2012

This document contains information previously presented in z/OS MVS System
Messages, Vol 6 (GOS-IEA), SA22-7636-22, which supports z/OS Version 1 Release
13.

For a comprehensive list of message changes, see z/OS Summary of Message and
Interface Changes.

Changes made in z/OS Version 1 Release 13

This document contains information previously presented in z/OS MVS System
Messages, Vol 6 (GOS-IEA), SA22-7636-21, which supports z/OS Version 1 Release
12.

For a comprehensive list of message changes, see z/OS Summary of Message and
Interface Changes.

Changes made in z/OS Version 1 Release 12

This document contains information previously presented in z/OS MVS System
Messages, Vol 6 (GOS-IEA), SA22-7636-20, which supports z/OS Version 1 Release
11.

Changed information:

The "Readers' Comments - We'd Like to Hear from You" section at the back of this
publication has been replaced with a new section “How to send your comments to

© Copyright IBM Corp. 1988, 2012 xi

 IBM” on page ix. The hardcopy mail-in form has been replaced with a page that
provides information appropriate for submitting readers comments to IBM.

For a comprehensive list of message changes, see z/OS Summary of Message and
Interface Changes.

Changes made in z/OS Version 1 Release 11 (as updated April 2010)

This document contains information previously presented in z/OS MVS System
Messages, Vol 6 (GOS-IEA), SA22-7636-19, which supports z/OS Version 1 Release
11.

For a comprehensive list of message changes, see z/OS Summary of Message and
Interface Changes.

Changes made in z/OS Version 1 Release 11

This document contains information previously presented in z/OS MVS System
Messages, Vol 6 (GOS-IEA), SA22-7636-18, which supports z/OS Version 1 Release
10.

For a comprehensive list of message changes, see z/OS Summary of Message and
Interface Changes.

xii z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Chapter 1. Introduction
The z/OS operating system issues messages from z/OS 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 WTO and WTOR macros: Most messages are issued through WTO and WTOR
macros to one of the following locations:
– Console
– Operations log(OPERLOG)
– System log (SYSLOG)
– 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 included with
each message.
v WTL macro or the LOG operator command: Some messages are issued through
the WTL macro or the LOG operator command to the system log (SYSLOG).
v Dumping services routines: Dump messages are issued through the Dumping
services routines and can appear in one of the following locations:
– 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 DFSMS/MVS access methods: Some messages are issued through DFSMS/MVS
access methods directly to one of the following locations:
– Output data set
– Display terminal

Messages are sent to different locations to meet some specific needs. For example,
messages routed to a console usually shows the result of an operator command
and sometimes require an operator reply, while messages recorded in the hardcopy
log permanently are often used for auditing. Understanding the locations where
you receive messages can help you manage your message flow.
Console
Messages sent to a multiple console support (MCS) console, an SNA multiple
console support (SMCS) console, or an extended MCS (EMCS) console are
intended for the operators. Operations can control which messages are
displayed. See z/OS MVS Planning: Operations 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.
Operations log
The operations log (OPERLOG) records all message traffic from each system in
a sysplex that activates the OPERLOG. The operations log consists of the
following data:
v Messages to and from all consoles
v Commands and replies entered by the operator
© Copyright IBM Corp. 1988, 2012 1
 System log
The system log (SYSLOG) is a SYSOUT data set that stores the messages and
commands from the current system. SYSOUT data sets are output spool data
sets on direct access storage devices (DASD) provided by the job entry
subsystem (either JES2 or JES3). 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.

Message format
A displayed or printed message can appear by itself or with other information,
such as a time stamp. The following topics show the format of the message body
and the formats of accompanying information when the message is sent to various
locations.

Format of the message body

The message body consists of three parts: the reply identifier (optional), the
message identifier, and the message text. The following formats are possible:

id CCCnnn text
id CCCnnns text
id CCCnnnns text
id CCCnnnnns text
id CCCSnnns text

id Reply identifier: It is optional. It appears if an operator reply is required. The

operator specifies it in the reply.
CCCnnn, CCCnnns, CCCnnnns, CCCnnnnns, CCCSnnns
Message identifier.
CCC
A prefix to identify the component, subsystem, or product that produced
the message. The prefix is three characters.
S The subcomponent identifier, which is an optional addition to the prefix to
identify the subcomponent that produced the message. The subcomponent
identifier is one character.
nnn, nnnn, nnnnn
A serial number to identify the individual message. The serial number is
three, four, or five decimal digits.

2 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 s An optional type code, which is one of the following:
A Action: The operator must perform a specific action.
D Decision: The operator must choose an alternative.
E Eventual action: The operator must perform action when time is
available.
I Information: No operator action is required.
S Severe error: Severe error messages are for a system programmer.
W Wait: Processing stops until the operator performs a required
action.
text
Text: The text provides information, describes an error, or requests an
operator action.

Note: The following messages have special format for the message body. Refer to
the specific message chapters for details.
v ADR messages
v CNL messages
v EWX messages
v IDA messages
v IEW messages
v IGW01 messages

Messages sent to MCS/SMCS consoles

Messages sent to MCS/SMCS consoles appear in one of the following formats:

f hh.mm.ss sysname jobname message

f hh.mm.ss sysname message
f hh.mm.ss jobname message
f hh.mm.ss message
f sysname jobname message
f sysname message
f jobname message
f message

f A screen character to indicate the status of certain messages, as follows:

| The operator has performed the action required for the message. The
message has been deleted.
- The message is for information only; no operator action is required.
The message was issued by the system or by a problem program.
* The message requires specific operator action and was issued by a
WTOR or by an authorized program. The message has a descriptor
code of 1, 2, or 11.
@ The message requires specific operator action and was issued by a
WTOR or by a problem program. The message has a descriptor code of
1, 2, or 11.
+ The message requires no specific operator action and was issued by a
problem program using a WTO macro.
blank The message requires no specific operator action.

Chapter 1. Introduction 3
 hh.mm.ss
Time stamp: the hour (00-23), minute (00-59), and second (00-59).
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.
message
Reply identifier, message identifier, and text.

Messages sent to hardcopy 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 hardcopy 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 hardcopy log appear in the format:

tcrrrrrrr sysname yyddd hh:mm:ss.th ident msgflags message

t message
t lid message

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

D Data line of a multiple-line message; this line may be the last line of
the message.
E End line or data-end line of a multiple-line message.
L Label line of a multiple-line message.
M First line of a multiple-line message.
N Single-line message that does not require a reply.
O Operator LOG command.
S Continuation of a single-line message or a continuation of the first line
of a multi-line message. This continuation may be required because of
the record length for the output device.
W A message that requires a reply.
X A log entry that did not originate with a LOG command or a system
message.
c The second character on the line indicates whether the line was generated
because of a command:
C Command input.
R Command response.
I Command issued internally. The job identifier contains the name of the
internal issuer.

4 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 blank Neither command input nor command response.
rrrrrrr
Hexadecimal representation of the routing codes 1 through 28. To understand
this hexadecimal number, convert it to binary; each binary 1 represents a
routing code. For example, X'420C' represents routing codes 2, 7, 13, and 14 as
shown here:
Hexadecimal: 4 2 0 C
Binary: 0 1 0 0 0 0 1 0 0 0 0 0 1 1 0 0
Routing Codes: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
sysname
The system name from the SYSNAME parameter in parmlib.
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 is 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 information about the
description of the hardcopy log message flags, see HCL in z/OS MVS Data
Areas in z/OS Internet Library at http://www.ibm.com/systems/z/os/zos/
bkserv/.
message
Reply identifier, message identifier, and text. The reply identifier and message
identifier appear only on the first line of a multiple-line message.

Chapter 1. Introduction 5
 Messages sent to hardcopy log in JES3 system
Messages sent to the JESMSG hardcopy log in a JES3 system appear in the format:

hh:mm:sst message

Messages sent to the MLOG/DLOG hardcopy log appear in the format:

dest console yyddd hhmmsstia[prefix] message

dest
JES3 destination class, which corresponds to the MVS routing code.
console
JES3 or MVS console name, as follows:
blank For a message issued without a console name.
nnnnn The JES3 console name (JNAME) from the JES3 initialization
stream. This applies to remote consoles only.
cnname The MCS console name, as specified on the NAME(cnname)
parameter under the CONSOLE definition in
SYS1.PARMLIB(CONSOLxx).
INTERNAL For a command generated by a problem program or operating
system routine.
NETWORK For a message issued to the network job entry (NJE) console.
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.

6 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 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 parameter on the MAINPROC statement
in the JES3 initialization stream.
jobname
The job name of the issuing program. It is all blanks for an system routine.
message
Reply identifier, message identifier, and text.

Messages sent to the job log, to other data sets, and to

display terminals
Messages sent to the job log, to other data sets, and to display terminals appear in
the format designed by the program that issued them.

Truncated data in multi-line messages

Under any one of the following conditions, the system might need to truncate a
multi-line message:
v When a message is being transported from one system to another in a sysplex,
the sending or receiving system might encounter an error that prevents some or
all of the message text from appearing. This can be caused by any of the
following:
– The issuing system is stopped or quiesced.
– The issuing system fails to end a multi-line message.
– The issuing system has an XCF buffer shortage.
– A disruption occurs in sysplex communication.
– An error occurs on the receiving system.
When one of the above conditions occurs, 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
v When no data line or endline has been issued for a multi-line message after an
interval of thirty seconds, the system issues the following endline:
MESSAGE TIMED OUT - MESSAGE COMPLETION FORCED
v When a connect request exceeds the limit of 65533 lines, the system truncates the
message with the following text:
EXCEEDED LINE LIMIT - MESSAGE COMPLETION FORCED
v When a multi-line message is issued with no end line, and it is not possible for
the system to obtain space to temporarily store the message, the system
truncates the message with the following text:
CONNECT UNAVAILABLE - MESSAGE COMPLETION FORCED
v When a multi-line connect request is issued, and the system is unable to obtain
space to store the connecting lines, the system truncates the message with the
following text:
CONNECT UNSUCCESSFUL - MESSAGE COMPLETION FORCED

Chapter 1. Introduction 7
 v When a message is too long to fit into 80% of the Console message cache, the
system truncates the message with the following text:
MESSAGE TRUNCATED FOR CONSOLE MESSAGE CACHE
v When there is a shortage of WTO buffers for display on MCS consoles, the
screen display may be truncated with one of the following lines of text:
NUMBER OF LINES EXCEEDED MLIM - MESSAGE TRUNCATED
STORAGE CONSTRAINT - MESSAGE TRUNCATED

Message description
The following topics describes the different message description items, and in
particular, the routing and descriptor codes.

Description items
The message explanation information is presented by the following items:
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 operator 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
z/OS 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

8 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 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 z/OS Problem Management and the appropriate diagnosis
guide for the product or element issuing the message, such as:
v DFSMS/MVS diagnosis guides and references
v z/OS JES2 Diagnosis
v z/OS JES3 Diagnosis
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.
Routing Code
For WTO or WTOR messages, the routing code of the message. See
“Routing codes” for more information about the code meaning.
Descriptor Code
For WTO or WTOR messages, the descriptor code of the message. See
“Descriptor codes” on page 13 for more information about the code
meaning.

Routing codes
Routing codes send system messages to the consoles where they are to be
displayed. More than one routing code can be assigned to a message to send it to
more than one console. For more information on message routing, see the
following topics:
v z/OS MVS Programming: Authorized Assembler Services Guide
v z/OS MVS Programming: Authorized Assembler Services Reference SET-WTO
v z/OS MVS Installation Exits
v z/OS MVS Initialization and Tuning Reference

Specification
The routing codes are specified in the ROUTCDE parameter of the WTO or WTOR
macro. If you specify a message which contains no routing codes, MVS may
provide one or more default routing codes, based upon the presence or lack of
other queuing specifications.

If you specify a message containing descriptor codes but no routing codes and no
target console, MVS will not assign any routing codes and will write the message
to the hardcopy log.

If you specify a message containing no routing codes, no descriptor codes, and no

target console, MVS will assign a default set of routing codes. This set of default
routing codes is specified at MVS initialization on the DEFAULT statement in your
CONSOLxx parmlib member. If a set of default routing codes was not provided on
the DEFAULT statement, MVS will assign routing codes 1 through 16.

Chapter 1. Introduction 9
 Routing code meaning
Routing codes appear within the associated message. The routing code field can
contain the following numeric values, special characters, or notes:
Code Meaning
1 Operator Action
The message indicates a change in the system status. It demands
action by a primary operator.
2 Operator Information
The message indicates a change in system status. It does not
demand action; rather, it alerts a primary operator to a condition
that might require action.
This routing code is used for any message that indicates job status
when the status is not requested specifically by an operator
inquiry. It is also used to route processor and problem program
messages to the system operator.
3 Tape Pool
The message gives information about tape devices, such as the
status of a tape unit or reel, the disposition of a tape reel, or a
request to mount a tape.
4 Direct Access Pool
The message gives information about direct access storage devices
(DASD), such as the status of a direct access unit or volume, the
disposition of a volume, or a request to mount a volume.
5 Tape Library
The message gives tape library information, such as a request by
volume serial numbers for tapes for system or problem program
use.
6 Disk Library
The message gives disk library information, such as a request by
volume serial numbers for volumes for system or problem
program use.
7 Unit Record Pool
The message gives information about unit record equipment, such
as a request to mount a printer train.
8 Teleprocessing Control
The message gives the status or disposition of teleprocessing
equipment, such as a message that describes line errors.
9 System Security
The message gives information about security checking, such as a
request for a password.
10 System/Error Maintenance
The message gives problem information for the system
programmer, such as a system error, an uncorrectable I/O error, or
information about system maintenance.

10 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

11 Programmer Information
This is commonly referred to as write to programmer (WTP). The
message is intended for the problem programmer. This routing
code is used when the program issuing the message cannot route
the message to the programmer through a system output
(SYSOUT) data set. The message appears in the JESYSMSG data
set.
12 Emulation
The message gives information about emulation. (These message
identifiers are not included in this publication.)
13-20 For customer use only.
21-28 For subsystem use only.
29 Disaster recovery.
30-40 For IBM use only.
41 The message gives information about JES3 job status.
42 The message gives general information about JES2 or JES3.
43-64 For JES use only.
65-96 Messages associated with particular processors.
97-128 Messages associated with particular devices.
* The message will be routed back to the consoles that initiated the
associated requests.
/ The message will be routed to different locations according to the
task issuing it. For example, */2/3 means the message is routed
back to the console that initiated the request, to a primary operator,
or to the tape pool.
# The message will be routed in one of the following ways:
v According to the routing indicators specified by the operator
v According to the default routing instructions previously
specified by the operator
v Back to the console that initiated the associated request
— The message has no routing code.
N/A A routing code is not applicable for the message.
Note 2 The message is issued by a WTO or WTOR macro, but has no
routing or descriptor codes (old format WTO or WTOR macro).
Note 3 The message has a routing code of 1, which sends the message to a
primary operator, and the message is also routed to the console
that it describes.
Note 4 The message is sent to all active consoles; this is a broadcast
message.
Note 5 The message has a routing code of 2, which sends the message to a
primary operator.
Note 6 The message is routed only to non-printer consoles. This message
is not issued by a WTO or WTOR macro.

Chapter 1. Introduction 11
 Note 7 The message is routed to consoles where one or more of the
following are active:
v MONITOR JOBNAMES
v MONITOR SESSIONS
v MONITOR STATUS
Note 9 The message is issued during the nucleus initialization program
(NIP) processing.
Note 10 The message is issued by the WTL macro.
Note 11 The message is routed to a SYSPRINT data set by data
management.
Note 12 The message is issued by a WTO or WTOR macro with
SYNCH=YES. See z/OS MVS Initialization and Tuning Reference for
more information.
Note 13 The message is routed only to receivers of the hardcopy message
set.
Note 14 The message is routed back to the console that initiated the request
and to all associated consoles.
Note 16 The message is routed to the IPCS print file IPCSPRNT.
Note 17 The message is issued by JES3. A JES3 destination class is specified
either by the initialization stream or by operator commands.
Note 18 The message is sent in response to a command to the console
where the command was entered.
Note 19 The message is written to a data set. If routing and descriptor
codes are also included for the message, the message might also be
displayed according to the specified routing and descriptor codes.
(The descriptor code does not apply to writing the message to the
data set.)
Note 20 JES3 does not issue the message. JES3 sends the message to
another subsystem for processing.
Note 21 This message is a trailer attached to multiple messages previously
issued. It has the same routing and descriptor codes as the first
line of the conglomerate.
Note 22 This message is routed to the transaction program (TP) message
log.
Note 23 This message is issued by the device controller. The routing code
will vary according to the device controller's task.
Note 24 This message is routed to the assembly listing.
Note 25 When this message is issued during IPL, the routing codes are 2
and 10 and the descriptor code is 12. When it is issued after IPL, it
has no routing code and the descriptor code is 5.
Note 26 When this message is issued during NIP processing, the descriptor
code is 12. When it is issued after NIP processing, the descriptor
code is 4.
Note 27 The indicated route codes are used only if this message is issued in
response to a reply of CKPTDEF during a JES2 checkpoint
reconfiguration. This message might be issued to a specific console

12 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 rather than directed by route code. For further information
concerning the routing of JES2 messages issued during a
reconfiguration, see z/OS JES2 Initialization and Tuning Guide.
Note 28 These routing and descriptor codes apply only when SMS issues
the message. If SMS returns the message to its caller and the caller
issues the message, the codes do not apply.
Note 29 This message is written to the JES3OUT data set.
Note 30 This message is issued by JES3. The message is written to the
*MODIFY CONFIG (*F MODIFY) log and/or the issuer of the *F
CONFIG command.
Note 31 The routing and descriptor codes for this message are dependent
on the setting of indicator bits within the S99EOPTS field in the
SVC 99 Request Block Extension (S99RBX). See the z/OS MVS
Programming: Authorized Assembler Services Guide, Processing
Messages and Reason Codes from Dynamic Allocation, for
additional information.
Note 32 Routing code 2 is only applicable if message IYP050D was issued.
Note 33 Routing code 2 is only applicable if message IZP050D was issued.
Note 34 This message is only displayed on the SMCS Console Selection
screen, and is not issued via WTO support.
Note 35 By default, IBM Health Checker for z/OS messages does not use
routing codes, but the installation can override the default to use
routing codes using either the MODIFY hzsproc command or in the
HZSPRMxx parmlib member. See IBM Health Checker for z/OS:
User's Guide for more information.
Note 36 This message is written to the JESYSMSG data set.

Descriptor codes
Descriptor codes describe the significance of messages. They indicate whether the
system or a task stops processing, waits until some action is completed, or
continues. This code also determines how the system will display and delete the
message.

Association with message type code

Descriptor codes are associated with message type codes, specified by a letter
following the message serial number, as follows:
Descriptor Code Type Code
1 W (wait)
2 A (action) or D (decision)
3 E (eventual action)
4 through 10 I (information)
11 E (critical eventual action)
12 and 13 I (information)

Valid combinations and restrictions for descriptor codes

Descriptor codes are specified in the DESC parameter of the WTO or WTOR
macro. The following restrictions apply when specifying descriptor codes:

Chapter 1. Introduction 13
 v Descriptor codes 1 through 6, 11, and 12 are mutually exclusive. Assign only one
of these codes to a message. If you assign two mutually exclusive codes to one
message, the system uses the most important code and ignores the other.
v Descriptor codes 7 through 10 and 13 can be assigned in combination with any
of the mutually exclusive codes.
v Descriptor code 9 can be used only with descriptor code 8.

Under certain conditions, the system uses a descriptor code other than that
specified in the macro as follows:
v The system assigns descriptor code 6 if the macro specifies a ROUTCDE
parameter, but no DESC parameter.
v The system assigns descriptor code 7 if all of the following are true:
1. A problem program issued the macro.
2. The macro omits both DESC and ROUTCDE parameters, or specifies
descriptor codes 1 or 2.
3. The message is not a multiple-line WTO message.
v The system assigns no descriptor code if all of the following are true:
1. An authorized program issued the macro.
2. The macro omits both DESC and ROUTCDE parameters.
3. The message is not a multiple-line WTO message.

Note: An authorized program has at least one of these characteristics:

– Authorized by the authorized program facility (APF)
– Runs in supervisor state
– Runs under PSW key 0 through 7

Message deletion
With multiple console support (MCS), action messages with descriptor code 1 or 2
issued by problem programs are assigned descriptor code 7; thus, they are
automatically deleted from the system at task or address space ending.

The system deletes messages issued by any program when that program issues the
DOM macro for a message.

The operator can manually remove all messages from a display console screen or
can set the console to roll messages off the screen.

Message Color
On operator consoles with color, the descriptor code determines the color of the
message. The use of color is explained in z/OS MVS System Commands. Also see the
descriptions of the CONSOLxx and MPFLSTxx parmlib members in z/OS MVS
Initialization and Tuning Reference.

Descriptor code meaning

Descriptor codes appear within the associated message. The descriptor code field
can contain the following numeric values, special characters or note.
Code Meaning
1 System Failure
The message indicates an error that disrupts system operations. To
continue, the operator must reIPL the system or restart a major
subsystem. This causes the audible alarm to be sounded.

14 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

2 Immediate Action Required
The message indicates that the operator must perform an action
immediately. The message issuer could be in a wait state until the
action is performed or the system needs the action as soon as
possible to improve performance. The task waits for the operator
to complete the action. This causes the audible alarm to be
sounded.

Note: When an authorized program issues a message with

descriptor code 2, a DOM macro must be issued to delete the
message after the requested action is performed.
3 Eventual Action Required
The message indicates that the operator must perform an action
eventually. The task does not wait for the operator to complete the
action.
If the task can determine when the operator has performed the
action, the task should issue a DOM macro to delete the message
when the action is complete.
4 System Status
The message indicates the status of a system task or of a hardware
unit.
5 Immediate Command Response
The message is issued as an immediate response to a system
command. The response does not depend on another system action
or task.
6 Job Status
The message indicates the status of a job or job step.
7 Task-Related
The message is issued by an application or system program.
Messages with this descriptor code are deleted when the job step
that issued them ends.
8 Out-of-Line
The message, which is one line of a group of one or more lines, is
to be displayed out-of-line. If a message cannot be displayed
out-of-line because of the device being used, descriptor code 8 is
ignored, and the message is displayed in-line with the other
messages.

Note: Multiline messages directed at an OOL area and routed by

either the UNKNIDS or INTIDS attributes will be forced “inline”.
9 Operator's Request
The message is written in response to an operator's request for
information by a DEVSERV, DISPLAY, or MONITOR command.
10 Not defined
Descriptor code 10 is not currently in use.
11 Critical Eventual Action Required

Chapter 1. Introduction 15
 The message indicates that the operator must perform an action
eventually, and the action is important enough for the message to
remain on the display screen until the action is completed. The
task does not wait for the operator to complete the action. This
causes the audible alarm to be sounded.
Avoid using this descriptor code for non-critical messages because
the display screen could become filled.
If the task can determine when the operator has performed the
action, the task should issue a DOM macro to delete the message
when the action is complete.
12 Important Information
The message contains important information that must be
displayed at a console, but does not require any action in response.
13 Automation Information
Indicates that this message was previously automated.
14-16 Reserved for future use.
/ The message will have different descriptor codes according to the
task issuing it. For example, 4/6 means the message can describe
system status or job status.
— The message has no descriptor code.
N/A A descriptor code is not applicable for the message.
Note 1 The descriptor code for an IBM Health Checker for z/OS check
exception message might vary, because the installation can override
the descriptor code either using the MODIFY hzsproc command or
in the HZSPRMxx parmlib member. See IBM Health Checker for
z/OS: User's Guide for more information. In addition to the
descriptor code selected by the installation, one of the following
descriptor codes is also included based on the severity of the
check:
v High severity checks use a descriptor code of 11.
v Medium severity checks use a descriptor code of 3.
v Low severity checks use a descriptor code of 12.

Message directory
To use a message prefix to locate the document containing a specific message, see
the following table.

Prefix Component Document title - order number

ABA DFSMShsm z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631
ACP LANRES z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631
ADF Time Sharing Option z/OS TSO/E User's Guide, SA22-7794
Extensions (TSO/E) session
manager z/OS TSO/E Command Reference, SC28-1881

z/OS TSO/E Messages, SA22-7786

ADM Graphical data display GDDM® Messages, SC33-0869
manager
ADR DFDSS z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631

16 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Prefix Component Document title - order number
ADRY DFDSS z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631
ADY Dump analysis and z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631
elimination (DAE)
AEM Graphical data display GDDM Messages, SC33-0869
manager
AFB VSFORTRAN VSFORTRAN Version 2 Language and Library Reference, SC26-4221
AHL Generalized trace facility z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631
(GTF)
z/OS MVS Dump Output Messages, GC28-1749
AIR Predictive Failure Analysis z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631
z/OS Problem Management, G325-2564
AIRH Predictive Failure Analysis z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631
z/OS Problem Management, G325-2564
AMA SPZAP service aid z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631
AMB LIST service aid z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631
AMD Stand-alone dump z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631
AMS Availability manager z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631

z/OS RMF Messages and Codes, SC33-7993

ANT Remote Copy z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631
ANF Starting with Release 8: z/OS Infoprint Server Messages and Diagnosis, G544-5747
Infoprint Server
AOF System Automation for IBM Tivoli System Automation for z/OS Messages and Codes, SC34-2574
OS/390®
AOM Administrative operations z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631
manager
AOP Infoprint server z/OS Infoprint Server Messages and Diagnosis, G544-5747
API Starting with Release 8: z/OS Infoprint Server Messages and Diagnosis, G544-5747
Infoprint Server
APS Print services facility (PSF) Print Services Facility™ Messages, S544-3675
ARC DFSMShsm z/OS MVS System Messages, Vol 2 (ARC-ASA), SA22-7632
ARRP System Control Program See message 52099 in Enterprise System/9000 Models 190, 210, 260, 320,
(SCP) 440, 480, 490, 570, and 610 Messages Part 2 for a complete message
explanation and appropriate responses; see GA23-0378
ASA MVS Reuse z/OS MVS System Messages, Vol 2 (ARC-ASA), SA22-7632
ASB Advanced z/OS MVS System Messages, Vol 3 (ASB-BPX), SA22-7633
Program-to-Program
Communications/MVS z/OS MVS Dump Output Messages, SA22-7590
(APPC/MVS)
ASD LANRES z/OS MVS System Messages, Vol 3 (ASB-BPX), SA22-7633
ASM Auxiliary storage manager z/OS MVS Dump Output Messages, SA22-7590
(ASM)
ASMA High Level Assembler for HLASM Programmer's Guide, SC26-4941
MVS & VM & VSE
ASR Symptom record (SYMREC) z/OS MVS Dump Output Messages, SA22-7590

Chapter 1. Introduction 17
 Prefix Component Document title - order number
ATB Advanced z/OS MVS System Messages, Vol 3 (ASB-BPX), SA22-7633
Program-to-Program
Communications/MVS z/OS MVS Dump Output Messages, SA22-7590
(APPC/MVS)
ATR Resource recovery services z/OS MVS System Messages, Vol 3 (ASB-BPX), SA22-7633
(RRS)
z/OS MVS Dump Output Messages, SA22-7590
ATRH Resource recovery services z/OS MVS System Messages, Vol 3 (ASB-BPX), SA22-7633
(RRS)
AVM Availability manager z/OS MVS System Messages, Vol 3 (ASB-BPX), SA22-7633
AXR System REXX z/OS MVS System Messages, Vol 3 (ASB-BPX), SA22-7633
| BCD Batch Runtime z/OS MVS System Messages, Vol 3 (ASB-BPX), SA22-7633
BFS IBM LAN server for MVS OS/390 MVS System Messages, Vol. 2, GC28-1785
BLG Information System, The Information/Management Library Messages and Codes, SC34-4459
Information Management
BLM Information System, The Information/Management Library Messages and Codes, SC34-4459
Information Management
BLS Interactive problem control z/OS MVS System Messages, Vol 3 (ASB-BPX), SA22-7633
system (IPCS)
z/OS MVS Dump Output Messages, SA22-7590
BLX Information System, The Information/Management Library Messages and Codes, SC34-4459
Information Management
BLW Loadwait/Restart z/OS MVS System Messages, Vol 3 (ASB-BPX), SA22-7633
BNH Network Problem NPDA Messages, SC34-2115
Determination Application
(NPDA)
BPX z/OS UNIX System Services z/OS MVS System Messages, Vol 3 (ASB-BPX), SA22-7633

z/OS MVS Dump Output Messages, SA22-7590

CBDA Hardware configuration z/OS and z/VM HCD Messages, SC33-7986
definition (HCD)
CBR Object access method (OAM) z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634
| CDS Open Cryptographic Service OCSF Application Programming, SC24-5899
| Facility (OCSF)
CEA Common Event Adapter z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634
®
CEE Language Environment z/OS Language Environment Debugging Guide, GA22-7560
CHS MVSSERV messages for the z/OS TSO/E Messages, SA22-7786
user and system programmer
CIM Managed System z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634
Infrastructure for Setup
(msys for Setup)
CMP Compression management z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634
services
CLB C/C++ class library runtime z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634
messages
CNL MVS message service (MMS) z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634

z/OS MVS Dump Output Messages, SA22-7590

CNZ Console Services z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634

18 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Prefix Component Document title - order number
COF Virtual lookaside facility z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634
(VLF)
z/OS MVS Dump Output Messages, SA22-7590

z/OS TSO/E Messages, SA22-7786

CPO z/OS MVS Capacity z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634
Provisioning
z/OS MVS Capacity Provisioning User’s Guide, SC33-8299
CRG Context Services z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634
CRU Integrated catalog forward z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634
recovery utility (ICFRU)
CSF Integrated Cryptographic z/OS Cryptographic Services ICSF Messages, SA22-7523
Service Facility (ICSF)
CSQ MQSeries® MQSeries for OS/390 V2R1 Messages and Codes, GC34-5375
CSR Callable services requests z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634
(CSR)
z/OS MVS Dump Output Messages, SA22-7590
CSV Contents supervision, virtual z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634
fetch, fetch
z/OS MVS Dump Output Messages, SA22-7590
CSY OPC/A Production Control OPC/A Messages, SH19-6448
System
CSZ OPC/A Network Event OPC/A Messages, SH19-6448
Communicator
CTX Context Services z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634
DFH Customer Information CICS/ESA Messages and Codes, SC33-0672
Control System/Virtual
Storage (CICS/VS)
DFQ Interactive storage Online only. To display the message explanation and suggested action,
management facility (ISMF) press the HELP key (PF1) twice when the message is currently
displayed. Otherwise, go to ISPF option 7.2 Display Panel, enter the
message ID in the message ID field, then press the HELP key (PF1)
twice to show the message explanation. For more information, see the
"Using Help Panels for Error Messages" topic in the z/OS DFSMS Using
the Interactive Storage Management Facility, SC26-7411.
DGT Interactive storage Online only. To display the message explanation and suggested action,
management facility (ISMF) press the HELP key (PF1) twice when the message is currently
displayed. Otherwise, go to ISPF option 7.2 Display Panel, enter the
message ID in the message ID field, then press the HELP key (PF1)
twice to show the message explanation. For more information, see the
"Using Help Panels for Error Messages" topic in the z/OS DFSMS Using
the Interactive Storage Management Facility, SC26-7411.
DLX DLF installation exit These messages are issued by the sample DLF installation exit,
COFXDLF2 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 document.
DMO Device Manager z/OS MVS System Messages, Vol 4 (CBD-DMO), SA22-7634

z/OS MVS Dump Output Messages, SA22-7590

™
DQD Cache RMF Reporter (CRR) Cache RMF Reporter Program Description/Operations Manual, SH20-6295
DRK OPC/A Event Manager OPC/A Messages, SH19-6448
Subsystem

Chapter 1. Introduction 19
Prefix Component Document title - order number
®
DSI NetView TME 10 NetView for OS/390 Messages, SC31-8237
DSM Document Composition DCF: Messages, SH35-0048
Facility
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 IBM Overlay Generation Language/370 User's Guide and Reference,
Language S544-3702
DZJ Print Management Facility Print Management Facility User's Guide and Reference, SH35-0059
EDC C/C++ Run-time Library z/OS Language Environment Debugging Guide, GA22-7560
EDG DFSMSrmm z/OS MVS System Messages, Vol 5 (EDG-GFS), SA22-7635
EDGH DFSMSrmm z/OS MVS System Messages, Vol 5 (EDG-GFS), SA22-7635
ELM IBM Communications Server z/OS Communications Server: SNA Messages, SC31-8790
— SNA
EQQ OPC/ESA OPC/ESA Messages and Codes, SH19-6719
ERB Resource Measurement z/OS MVS System Messages, Vol 5 (EDG-GFS), SA22-7635
Facility™ (RMF)
z/OS RMF Messages and Codes, SC33-7993
ERX Graphical data display GDDM Messages, SC33-0869
manager
EWX LANRES z/OS MVS System Messages, Vol 5 (EDG-GFS), SA22-7635
EZA IBM Communication Server z/OS Communications Server: IP Messages Volume 1 (EZA), SC31-8783
— IP
EZB IBM Communication Server z/OS Communications Server: IP Messages Volume 2 (EZB, EZD),
— IP SC31-8784
EZM Application Enabling
Technology (AET)/Auto OS/390 Application Enabling Technology: Administration and Programming,
UNIX System GC28–1993

OS/390 Application Enabling Technology: Customization Guide, GC28–1994

OS/390 MVS System Messages (EWX-IEB), GC28–1786

EZY z/OS Communication Server z/OS Communications Server: IP Messages Volume 3 (EZY), SC31-8785
— IP
EZZ z/OS Communication Server z/OS Communications Server: IP Messages Volume 4 (EZZ, SNM),
— IP SC31-8786
FAN(G) REXX/370 compiler IBM Compiler and Library for SAA REXX/370 User's Guide and Reference ,
SH19-8160
FDBX z/OS UNIX System Services z/OS UNIX System Services Messages and Codes, SA22-7807
FLM Software configuration and z/OS ISPF Messages and Codes
library manager
FOMC z/OS UNIX System Services z/OS UNIX System Services Messages and Codes, SA22-7807
FOMF z/OS UNIX System Services z/OS UNIX System Services Messages and Codes, SA22-7807
FOMI z/OS UNIX System Services z/OS UNIX System Services Messages and Codes, SA22-7807
FOMM z/OS UNIX System Services z/OS UNIX System Services Messages and Codes, SA22-7807
FOMO z/OS UNIX System Services z/OS UNIX System Services Messages and Codes, SA22-7807
FOMOA z/OS UNIX System Services z/OS UNIX System Services Messages and Codes, SA22-7807
FOMOG z/OS UNIX System Services z/OS UNIX System Services Messages and Codes, SA22-7807

20 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 Prefix Component Document title - order number
FOMOH z/OS UNIX System Services z/OS UNIX System Services Messages and Codes, SA22-7807
FSUM z/OS UNIX System Services z/OS UNIX System Services Messages and Codes, SA22-7807
FSUMA z/OS UNIX System Services z/OS UNIX System Services Messages and Codes, SA22-7807
FSUMB z/OS UNIX System Services z/OS UNIX System Services Messages and Codes, SA22-7807
FSUMF z/OS UNIX System Services z/OS UNIX System Services Messages and Codes, SA22-7807
FOR LE FORTRAN Library IBM Language Environment for MVS & VM FORTRAN Run-Time
Migration Guide, SC26-8499
GDE Distributed FileManager/ z/OS MVS System Messages, Vol 5 (EDG-GFS), SA22-7635
MVS (DFM/MVS)
GFSA Network File System Server z/OS Network File System Guide and Reference, SC26-7417
GFSC Network File System Server z/OS Network File System Guide and Reference, SC26-7417
Client Messages
GIM SMP/E SMP/E Messages, Codes, and Diagnosis,
GQD Graphical data display GDDM Messages, SC33-0869
manager
GQF Graphical data display GDDM Messages, SC33-0869
manager
| GSK Integrated Cryptographic z/OS Cryptographic Services System SSL Programming, SC24-5901
| Service Facility (ICSF)
HASP JES2, network job entry z/OS JES2 Messages, SA22-7537
facility for JES2
HIS Hardware instrumentation z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
services (HIS)
HWI Base Control Program z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
Internal Interface Services
HZS IBM Health Checker for z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
z/OS IBM Health Checker for z/OS: User's Guide
| HZR Runtime Diagnostics z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
| z/OS Problem Management
IAR Real storage manager (RSM) z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636

z/OS MVS Dump Output Messages, SA22-7590

IARH Real storage manager (RSM) z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
IAT JES3 z/OS JES3 Messages, SA22-7552
IAZ JES Common z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
ICE DFSORT sort program z/OS DFSORT Messages, Codes and Diagnosis Guide, SC26-7525
ICH Resource Access Control z/OS Security Server RACF Messages and Codes, SA22-7686
Facility (RACF®)
ICK Device Support Facilities Device Support Facilities User's Guide and Reference, GC35-0033
| ICM Library Server DB2® Content Manager V8.4.2: Messages and Codes, SC27-1349
ICN NCP/SSP/EP NCP/SSP/EP Messages and Codes, SC30-3169
ICP Input/Output Configuration z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
Program (IOCP)
Input/Output Configuration Program User's Guide and Reference,
GC28-1027

Chapter 1. Introduction 21
Prefix Component Document title - order number
ICQA Information Center Facility z/OS TSO/E Messages, SA22-7786
administrator messages
ICQC Information Center Facility z/OS TSO/E Messages, SA22-7786
user messages
ICT Programmed Cryptographic z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
Facility
ICU Cryptographic Unit Support z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
IDA Virtual storage access method z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
(VSAM) control block
expansion
IDC Access method devices z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
IEA v Allocation/unallocation z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
v Auxiliary storage manager z/OS MVS Dump Output Messages, SA22-7590
(ASM)
v Contents supervision
v Communications task
(COMMTASK)
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)
IEAH SDUMP (SCDMP) z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
IEATH Timer supervision z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
IEAVEH Supervisor Control z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
IEAVTRH Recovery Termination z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
Manager (RTM)
IEB Data Facility Product (DFP) z/OS MVS System Messages, Vol 7 (IEB-IEE), SA22-7637
utilities
IEC Data Facility Product (DFP) z/OS MVS System Messages, Vol 7 (IEB-IEE), SA22-7637
components
z/OS DFSMSdfp Diagnosis, GY27-7618

22 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Prefix Component Document title - order number
IEE v Auxiliary storage manager z/OS MVS System Messages, Vol 7 (IEB-IEE), SA22-7637
(ASM)
z/OS MVS Dump Output Messages, SA22-7590
v Communications task
(COMMTASK)
v Data Facility Product
(DFP) components
v JES2
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
IEF v Allocation/unallocation z/OS MVS System Messages, Vol 8 (IEF-IGD), SA22-7638
v Converter/interpreter z/OS MVS Dump Output Messages, SA22-7590
v Data Facility Product
(DFP) components
v Initial program load (IPL)
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 z/OS MVS System Messages, Vol 8 (IEF-IGD), SA22-7638
IEFI Converter/interpreter z/OS MVS System Messages, Vol 8 (IEF-IGD), SA22-7638
IEH Data Facility Product (DFP) z/OS MVS System Messages, Vol 8 (IEF-IGD), SA22-7638
utilities
IEV Assembler H Assembler H Version 2 Application Programming: Guide, SC26-4036

Chapter 1. Introduction 23
Prefix Component Document title - order number
IEW v DFSMS z/OS MVS System Messages, Vol 8 (IEF-IGD), SA22-7638
v Linkage editor
v Binder
v Transport utility
v Loader
IFA System management facilities z/OS MVS System Messages, Vol 8 (IEF-IGD), SA22-7638
(SMF)
z/OS MVS Dump Output Messages, SA22-7590
IFB Input/output environment z/OS MVS System Messages, Vol 8 (IEF-IGD), SA22-7638
recording routines: OBR and
SVC 76
IFC IFCDIP00 service aid for the z/OS MVS System Messages, Vol 8 (IEF-IGD), SA22-7638
logrec data set
Environmental Record Editing and Printing Program (EREP) User's Guide
IFCEREP0 and IFCEREP1 and Reference, GC28-1378
service aids
IFD Online test executive OS/390 MVS System Messages, Vol. 4, GC28-1787
program (OLTEP)
IFL Network Control Program 3704 and 3705 Control Program Generation and Utilities Guide and
(NCP) Reference Manual, GC30-3008

Advanced Communications Network Control Program/System Support Programs/Emulation Programs

Function (ACF) for Network Messages and Codes, SC30-3169
Control Program (NCP)
IFO MVS Assembler OS/VS - VM/370 Assembler Programmer's Guide, GC33-4021
IGD Storage management z/OS MVS System Messages, Vol 8 (IEF-IGD), SA22-7638
subsystem (SMS) of Data
Facility Product (DFP) z/OS MVS Dump Output Messages, SA22-7590
IGF Dynamic device z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
reconfiguration (DDR)
Machine check handler
(MCH)
IGGHC DFSMS Catalog z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
IGGN Data Facility Product (DFP) z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
IGV Virtual storage management z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
(VSM)
IGW Data Facility Product (DFP) z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
Storage management
subsystem (SMS) z/OS MVS Dump Output Messages, SA22-7590
IGY VS COBOL II VS COBOL II Application Programming Guide, SC26-4045
IGZ VS COBOL II VS COBOL II Application Programming: Debugging, SC26-4049,

z/OS Language Environment Debugging Guide, GA22-7560

IHJ Data Facility Product (DFP) z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
checkpoint/scheduler restart
IKF VS COBOL II VS COBOL II Application Programming: Debugging, SC26-4049
IKJ Time Sharing Option z/OS TSO/E Messages, SA22-7786
Extensions (TSO/E)
z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639

z/OS MVS Dump Output Messages, SA22-7590

24 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Prefix Component Document title - order number
IKM Programming Language/I z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
(PL/I) syntax checker
IKT Time Sharing Option z/OS TSO/E Messages, SA22-7786, SC27-0614, SC27-0470, SC23-0114
Extensions (TSO/E)
z/OS Communications Server: SNA Messages, SC31-8790
IBM Communications Server
— SNA
ILM IBM License Manager z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
ILR Auxiliary storage manager z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
(ASM)
ILX VS FORTRAN Compiler VS FORTRAN Version 2 Programming Guide for CMS and MVS,
SC26-4222
IHV System Automation for IBM Tivoli System Automation for z/OS Messages and Codes
OS/390
ING System Automation for IBM Tivoli System Automation for z/OS Messages and Codes, SC34-2574
OS/390
INM Interactive Data Transmission z/OS TSO/E Messages, SA22-7786
Facility (IDTF) TRANSMIT
and RECEIVE commands
IOAC Open Systems zEnterprise System, System z10, System z9 and eServer zSeries OSA-Express
Adapter-Express Customer's Guide and Reference, SA22-7935
(OSA-Express)
IOP Input/output configuration z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
program (IOCP)
IOS Input/output supervisor z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
(IOS)
z/OS MVS Dump Output Messages, SA22-7590
IPD FORTRAN syntax checker z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
IRA System resources manager z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
(SRM)
z/OS MVS Dump Output Messages, SA22-7590
®
IRD ESCON Director Device z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
Support (EDDS)
IRR Resource Access Control z/OS Security Server RACF Messages and Codes, SA22-7686
Facility (RACF)
IRX Time Sharing Option z/OS TSO/E Messages, SA22-7786
Extensions (TSO/E)
restructured extended
executor language (REXX)
ISG Global resource serialization z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639

z/OS MVS Dump Output Messages, SA22-7590

ISN Service Processor Interface z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
ISP Interactive system z/OS ISPF Messages and Codes
productivity facility
ISQ System Automation for IBM Tivoli System Automation for z/OS Messages and Codes
OS/390
ISRB Interactive system z/OS ISPF Messages and Codes
productivity facility
ISRL Library management facility z/OS ISPF Messages and Codes

Chapter 1. Introduction 25
Prefix Component Document title - order number
IST IBM Communications Server z/OS Communications Server: SNA Messages, SC31-8790
— SNA
ISU IBM Communications Server z/OS Communications Server: SNA Messages, SC31-8790
— SNA
ITA TOLTEP for Advanced Advanced Communications Function for VTAM Messages and Codes,
Communications Function SC27-0614, SC27-0470, SC23-0114
for Virtual
Telecommunications Access
Method (ACF/VTAM)
ITT Component trace z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639

z/OS MVS Dump Output Messages, SA22-7590

ITV Data-in-virtual z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639

z/OS MVS Dump Output Messages, SA22-7590

ITZ Transaction trace z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639

z/OS MVS Dump Output Messages, SA22-7590

IST IBM Communications Server z/OS Communications Server: SNA Messages, SC31-8790
— SNA
IVT IBM Communications Server z/OS Communications Server: SNA Messages, SC31-8790
— SNA
IWM Workload manager (WLM) z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639

z/OS MVS Dump Output Messages, SA22-7590

IXC Cross-system coupling z/OS MVS System Messages, Vol 10 (IXC-IZP), SA22-7640
facility (XCF)
z/OS MVS Dump Output Messages, SA22-7590
IXG System logger (SCLOG) z/OS MVS System Messages, Vol 10 (IXC-IZP), SA22-7640
IXL Cross System Extended z/OS MVS System Messages, Vol 10 (IXC-IZP), SA22-7640
Services (XES)
z/OS MVS Dump Output Messages, SA22-7590
IXP Input/output configuration z/OS MVS System Messages, Vol 10 (IXC-IZP), SA22-7640
program (IOCP)
ES/9000 ES/3090 IOCP User's Guide Volume A04, GC38-0097
IXZ JES common coupling z/OS MVS System Messages, Vol 10 (IXC-IZP), SA22-7640
services (JESXCF)
z/OS MVS Dump Output Messages, SA22-7590
IYP Input/output configuration z/OS MVS System Messages, Vol 10 (IXC-IZP), SA22-7640
program (IOCP)
zSeries® 900 IOCP User's Guide for IYP IOCP, SB10-7029
IZP Input/output configuration z/OS MVS System Messages, Vol 10 (IXC-IZP), SA22-7640
program (IOCP)
ES/9000 IOCP User's Guide and ESCON CTC Reference Volume A04,
GC38-0401
SNM IBM Communication Server z/OS Communications Server: IP Messages Volume 4 (EZZ, SNM),
— IP SC31-8786
USS IBM Communications Server z/OS Communications Server: SNA Messages, SC31-8790
— SNA

26 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Building your own message library
If you are operators or programmers in an installation, you can build your own
libraries of the message and code information that fits your specific needs. You can
place into binders the chapters and documents containing only the messages and
codes you receive.

Basic documents
Each installation requires at least one copy of each of the MVS System Messages
documents and of z/OS MVS Dump Output Messages. Regardless of the specific
options of your system, you will receive at the console or in listings some subset of
the messages in these documents.

Each installation also requires at least one copy of z/OS 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 documents for the
component, subsystem, or product that produces the codes. Codes produced by
installation-provided programs do not appear in IBM documents.

All programming and operations personnel need access to the basic documents,
although application programmers might not need to have their own copies.

Optional documents
For information about message changes for multiple z/OS elements including
JES2, JES3, RACF, TCP/IP, and others, see z/OS Summary of Message and Interface
Changes.

Translating messages
Using the MVS message service (MMS), you can translate MVS system messages
into other languages. The following messages cannot be translated:
v Initialization messages
v DFSMS/MVS messages
v JES3 messages
v Some complicated multiple-line messages

See z/OS MVS Planning: Operations and z/OS MVS Programming: Assembler Services
Guide for information about using the MMS.

Finding changes to system message texts

Automation routines are sensitive to message text changes between releases. So
before migrating from your current release to another one, you might need to
check out the message changes. The summary of changes of the related messages
books can be a helpful reference; an alternative can identify changes to message
texts more accurately: comparing the SYS1.MSGENU data set.

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.

Note that this method will not show changes to messages that are not translated:

Chapter 1. Introduction 27
 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.

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 with changed text, the output might show both an I and a D,
indicating that a record in the message file has been replaced:
I - IEE162I 46 &NNN. ROLL &A. MESSAGES (DEL=R OR RD)
D - IEE162I 46 &NNN. ROLL &A. MESSAGES (DEL=R, RD)

This means that, in message IEE162I, (DEL=R, RD) was replaced by (DEL=R OR RD).

Using this information, you can decide if your automation routines need to be
changed.

28 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Chapter 2. 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.
In the message text:
ssname
is the name of the SOMobjects subsystem.
productid
The SOMobjects product id.
productlvl
The SOMobjects product level.
compid
The SOMobjects component id.
System action: SOMobjects subsystem processing continues.
Source: SOM

GOS006I 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.
In the message text:
jobname
The name of the SOMobjects job or started procedure.
System action: The SOMobjects address space ends.
System programmer response: Ensure that the SOMobjects job name/procedure name is a valid subsystem name
(1-4 characters).
Source: SOM

GOS007I SOM/MVS ssname INPUT COMMAND PREFIX IS NOT VALID. DEFAULT PREFIX USED.
Explanation: A command prefix value that was specified as input to the SOMobjects subsystem ssname is not valid.
The prefix value is either greater than 8 characters, begins with an invalid symbol, or contains an imbedded blank.
In the message text:
ssname
is the name of the SOMobjects subsystem.
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 programmer response: If the bad command prefix was specified as a parameter in the job procedure that

© Copyright IBM Corp. 1988, 2012 29

GOS008I • GOS011I

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

GOS008I 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.
In the message text:
ssname
The name of the SOMobjects subsystem.
cmdprefix
is a 1-8 character command prefix.
System action: SOMobjects subsystem initialization continues.
Operator response: Whenever you enter one of the commands supported by the SOMobjects subsystem, you must
begin the command with the indicated command prefix (for example, cmdprefix STATUS).
Source: SOM

GOS009I SOM/MVS ssname INITIALIZATION COMPLETE.

Explanation: The SOMobjects subsystem ssname has completed its initialization.
In the message text:
ssname
is the name of the SOMobjects subsystem.
System action: The SOMobjects subsystem continues processing. It is now ready to accept distributed SOM requests.
Source: SOM

GOS010I SOM/MVS ssname ENDED.

Explanation: The SOMobjects subsystem ssname has completed shutting down.
In the message text:
ssname
is the name of the SOMobjects subsystem.
System action: The SOMobjects subsystem address space ends.
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.
In the message text:
ssname
is the name of the SOMobjects subsystem.
System action: The SOMobjects subsystem ends.
System programmer response: Examine the SYSLOG to determine the error message or abend that caused
initialization to fail and then correct the condition that caused the error.
Source: SOM

30 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 GOS012I • GOS021I

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.
In the message text:
ssname
The name of the SOMobjects subsystem.
System action: The SOMobjects subsystem that issued this message ends.
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

GOS013I SOM/MVS ssname IS NOT A VALID SUBSYSTEM.

Explanation: The SOMobjects subsystem ssname is not a defined subsystem name known by the system.
In the message text:
ssname
The name of the SOMobjects subsystem.
System action: The SOMobjects subsystem ends.
System programmer response: Ensure the 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 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.
In the message text:
server_name
The name of the SOMobjects server, which is specified on DSOM server utility commands. For a description of
those commands, see OS/390 SOMobjects Configuration and Administration Guide, GC28-1851.
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.
In the message text:
ssname
is the name of the SOMobjects subsystem.
System action: The SOMobjects subsystem ends. Distributed SOM requests will no longer be processed. Any usage
of servers, clients, and DSOM utilities will be affected.
Source: SOM

Chapter 2. GOS messages 31

GOS022I • GOS025I

GOS022I SOM/MVS ssname SUBSYSTEM FUNCTION DISABLEMENT FAILED.

Explanation: In the process of ending either normally 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.
In the message text:
ssname
The name of the SOMobjects subsystem.
System action: The SOMobjects subsystem ends. 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.
In the message text:
ssname
The name of the SOMobjects subsystem.
System action: System initialization continues.
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.
In the message text:
ssname
The name of the SOMobjects subsystem.
cmdname
The name of the command that was entered.
System action: The SOMobjects subsystem stops processing the command.
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.
In the message text:
ssname
The name of the SOMobjects subsystem.
cmdname
The name of the command that was entered.
System action: The SOMobjects subsystem stops processing the command.
Operator response: Contact your installation's security administrator to ensure both you and the console are

32 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 GOS026I • GOS032I

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.
In the message text:
ssname
The name of the SOMobjects subsystem.
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

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.
In the message text:
hh.mm.ss
The time in hours (00-23), minutes (00-59), and seconds (00-59).
ssname
The name of the SOMobjects subsystem.
System action: Processing continues.
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.
In the message text:
ssname
is the name of the SOMobjects subsystem.
System action: The SOMobjects subsystem ends.
Operator response: Contact the system programmer.
System programmer response: Examine the SYSLOG or the job's 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.
Source: SOM

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.
In the message text:
nnnnnnnn
Used by IBM for problem determination.
xxxxxxxx
Used by IBM for problem determination.

Chapter 2. GOS messages 33

GOS033I • GOS042I

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 (prefix ITT)
accompanying this message.
Source: SOM

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.

Explanation: In the process of ending either normally or abnormally, the SOMobjects subsystem ssname must wait
for distributed SOM (DSOM) servers to end before the subsystem is ended.
In the message text:
ssname
The name of the SOMobjects subsystem.
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

GOS042I SOM/MVS ssname WAITING FOR OMVS TO START.

Explanation: In the process of initialization, the SOMobjects subsystem ssname must wait for the z/OS UNIX
address space to initialize before completing subsystem initialization.
In the message text:
ssname
The name of the SOMobjects subsystem.
System action: The SOMobjects subsystem waits for the OMVS address space to initialize.
Source: SOM

34 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Chapter 3. 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.
System action: Processing continues.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM002I PM OF OS/390 DATA SERVER TERMINATED

Explanation: The PM of OS/390 data server has ended.
System action: System processing continues.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

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.
System action: The PM of OS/390 data server ends processing.
Operator response: Restart the PM of OS/390 data server.
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.
System action: The PM of OS/390 data server ends processing.
System programmer response: Ensure that the PM of OS/390 load library is APF authorized.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM005E INVALID COMMAND FOR PM OF OS/390

Explanation: An unsupported MODIFY command has been entered for the PM of OS/390 data server.
System action: Processing continues.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

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.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

© Copyright IBM Corp. 1988, 2012 35

GPM050I • GPM055I

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.
Operator response: Inform the system programmer.
System programmer response: Make sure that a valid GPMSRVxx PARMLIB member exists in the parameter library
(usually the PARMLIB concatenation).
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM051I TCP/IP IS NOT CURRENTLY OPERATIONAL ON THE HOST

Explanation: The TCP/IP is either not active on the host, or is not customized correctly. The GPMSERVE address
space has detected that TCP/IP services are not available.
System action: The host server terminates.
Operator response: Inform the system programmer.
System programmer response: Make sure that TCP/IP is customized correctly and is active before the DDS host
server is started.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

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.
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.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM054I PERMANENT ERROR IN RMF PM 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.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

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.
System programmer response: Make sure that all required prerequisites for the component are active and
operational (for example, TCP/IP). Make sure that the timeout option in the GPMSRVxx PARMLIB member
(TIMEOUT option) is set properly, and that the DDS host server is active.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

36 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 GPM056I • GPM061I

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.
System action: The server is terminated immediately.
System programmer response: Correct the erroneous option member.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM057I SPECIFIED HOSTNAME 'hostname' CANNOT BE RESOLVED

Explanation: One of the following parameters in the GPMSRVxx member contains a hostname that cannot be
resolved by the name server:
v DM_ACCEPTHOST
v SERVERHOST
v HTTP_ALLOWHTTP_ALLOW
System action: The indicated hostname is discarded.
System programmer response: Correct the erroneous option member.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

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 action: The server is terminated immediately.
Operator response: Inform the system programmer.
System programmer response: Make sure that a valid GPMSRVxx PARMLIB member exists in the parameter library
(usually the PARMLIB concatenation).
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

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.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM060I DDS SERVER READY FOR COMMANDS

Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)
Explanation: The DDS server is now accepting commands from the console.
User response: None.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM061I OPTIONS IN EFFECT: options

Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)
Explanation: This message lists the currently active options for the DDS server.
User response: None.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

Chapter 3. GPM messages 37

GPM062I • GPM064I

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
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM063I PERMANENT ERROR IN DM/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 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.
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
(DATAGRAM_PORT option) is free and can be used by the DDS host server.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM064I PERMANENT ERROR IN UNIX SESSION SERVER

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 session requests via UNIX domain
sockets (for example, PM of OS/390 APPC clients) has abnormally terminated.
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 (mainly z/OS 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 RMF PM will be used.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

38 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 GPM065I • GPM071I

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.
System programmer response: Make sure that the library, where the GPMDDSRV module resides (usually
SYS1.SERBLINK) is APF-authorized.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM066I DDS SERVER TERMINATED

Explanation: The DDS host server has terminated.
System action: None
System programmer response: None
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM067I VALUE xxxx IS NOT ALLOWED FOR OPTION yyyyy

Explanation: The specified option value is not allowed or outside the allowed range for the option.
System action: The server is terminated immediately.
System programmer response: Correct the erroneous option member.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

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.
System programmer response:
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.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM070I NON-RMF VERSION OF MODULE ERB3XDRS DETECTED

Explanation: The server has detected that the RMF service ERB3XDRS has returned an invalid return code/reason
code of 16/0. This combination of return code and reason code is not defined for RMF but has been used by a
vendor product to indicate that the ERB3XDRS service is not supported by this vendor product.
System action: The server is terminated with a fatal error.
System programmer response: Make sure that only the RMF version of the ERB3XDRS loadmodule is in the library
concatenation or LINKLIST.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM071I REGION SIZE IS TOO SMALL FOR THE SPECIFIED NUMBER OF CACHESLOTS
Explanation: The estimated storage size for the data cache exceeds the virtual storage size for the server address
space. The DDS server calculates the required storage size by multiplying the measured size for the first cache slot
with the number of configured cache entries (see CACHESLOTS parameter in GPMSRVxx). The size of the first cache

Chapter 3. GPM messages 39

GPM073I • GPM074I

slot is shown in the SYSPRINT output file. 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.
System programmer response: Check the following items:
v Increase the REGION size parameter on the JOB or EXEC card.
v Make sure that the requested region size is really available to the server program, for example, check that the
IEFUSI system exit does not reduce the requested region size.
v Reduce the number of cache slots in the GPMSRVxx PARMLIB member (CACHESLOTS option). The default
number of slots is 4 and the minimum number is 3.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM073I CANNOT BIND TO TCP/IP port nnnn on xxxxxx

Explanation: The DDS server is unable to use one of the configured TCP/IP port on the host. The most probable
reason for this message is that another application or another copy of the DDS server is already using the port.
System action: The server is terminated.
System programmer response: Check that no other application is running that is using the specified port number,
and that no second copy of the DDS server is running that uses the specified port.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

GPM074I FAILURE CREATING REGULAR EXPRESSION FOR {HTTP_ALLOW | HTTP_NOAUTH |

DM_ACCEPTHOST}
Explanation: The HTTPALLOW, HTTP_NOAUTH or DM_ACCEPTHOST specification in the GPMSRVxx member
contains invalid data.
System action: The server is terminated immediately.
System programmer response: Check the erroneous option member.
Source: Resource Measurement Facility (RMF) - Distributed Data Server (DDS)

40 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

|

| Chapter 4. GSL messages

|
| GSL100E Unexpected Successful SGD Add
| Explanation: An attempt was made to update a Storage Group with z/OSMF add storage data. The Storage Group
| definition was added and not replaced.
| System action: SGD is added not replaced as expected.
| Operator response: None.
| System programmer response: Search problem reporting databases for a fix for the problem. If no fix exists, contact
| the IBM Support Center.
| Source: z/OSMF add storage
| Routing Code: -
| Descriptor Code: -
|
| GSL101E Control Data Set in Use: datasetname
| Explanation: An attempt was made to access an SMS control data set (CDS) and the SMS CDS is currently in use by
| another user in an incompatible way.
| In the message text:
| datasetname
| The name of SMS CDS which could not be accessed.
| System action: Access of the CDS fails.
| Operator response: None.
| System programmer response: Try again to access the CDS when the CDS is no longer in use.
| Source: z/OSMF add storage
| Routing Code: -
| Descriptor Code: -
|
| GSL103E function RC:rc RS:rs SubRC:subrc SubRS:subrs
| Explanation: z/OSMF add storage was unable to complete the specified internal SMS function. The return code,
| reason code and sub return and reason codes are provided.
| In the message text:
| function The z/OSMF add storage function which failed.
| RC:rc The return code from the failing function.
| RS:rs The reason code from the failing function.
| SubRC:subrc
| The sub-return code from the failing function.
| SubRS:subrs
| The sub-reason code from the failing function.
| System action: The requested function failed.
| System programmer response: Search problem reporting databases for a fix for the problem. If no fix exists, contact
| the IBM Support Center.
| Source: z/OSMF add storage
| Routing Code: -
© Copyright IBM Corp. 1988, 2012 41
 GSL999I

| Descriptor Code: -
|
| GSL999I text
| Explanation: This message is for use by the IBM Support Center only.
| System action: The message documents internal processing and should normally be ignored.
| System programmer response: None.
| Source: z/OSMF add storage
| Routing Code: -
| Descriptor Code: -
|

42 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Chapter 5. HIS messages
HIS001I hisproc IS ALREADY ACTIVE
Explanation: A request to start the hardware instrumentation services (HIS) address space was received. However, it
is already active.
In the message text:
hisproc
The name of the HIS catalogued startup procedure.
System action: The system ignores the start request.
Operator response: None.
System programmer response: None.
Problem determination: Issue the DISPLAY A,LIST to list information about the active tasks.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISINIT
Routing Code: -
Descriptor Code: 5

HIS002I hisproc INITIALIZATION COMPLETE

Explanation: The hardware instrumentation services (HIS) address space is now initialized. You can now issue the
MODIFY hisproc command to start event counters and sampling data collection.
In the message text:
hisproc
The name of the HIS catalogued startup procedure.
System action: HIS is ready for work.
Operator response: None.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISINIT
Routing Code: 2
Descriptor Code: 4

HIS003I COMMAND DELIMITER ERROR, OR UNRECOGNIZED KEYWORD.

KEYWORD LAST PROCESSED: lastkw
Explanation: The system found an error in the MODIFY hisproc command that was issued. The command either has
a delimiter error, or the system detected an unrecognizable keyword.
This error can be caused by entering an incorrect keyword, or keyword value, that has more than its expected
number of characters. The message might indicate that a delimiter is missing or incorrectly placed. Valid delimiters
include:
v blank
v =
v (
v )

© Copyright IBM Corp. 1988, 2012 43

HIS004I • HIS005I

v '

In the message text:

lastkw
The last keyword that the system processed before the error occurred.
System action: The system does not complete the command issued.
Operator response: Verify the value entered for the identified keyword. Ensure that the length for the keyword is
within the specified limit. If a value is expected to be enclosed in quotation marks or parenthesis, verify that they are
a matched pair.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCMD
Routing Code: -
Descriptor Code: 5

HIS004I MODIFY hisproc COMMAND SYNTAX ERROR. DUPLICATE KEYWORD DETECTED: duplicatekw
Explanation: The system detected a duplicate keyword in the MODIFY hisproc command.
In the message text:
hisproc
The name of the HIS catalogued startup procedure.
duplicatekw
The name of the duplicate keyword.
System action: The system does not complete the command issued.
Operator response: Reissue the MODIFY hisproc command correctly.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCMD
Routing Code: -
Descriptor Code: 5

HIS005I MODIFY hisproc COMMAND SYNTAX ERROR. INCORRECT VALUE SPECIFIED FOR KEYWORD
keyword, WHERE ONE OF (goodval1 goodval2 goodval3 goodval4) WOULD BE CORRECT.
Explanation: The system detected an incorrect value for the identified keyword in the MODIFY hisproc command.
The acceptable values for the keyword are displayed.
In the message text:
hisproc
The name of the HIS catalogued startup procedure.
keyword
The name of the keyword with the incorrect value.
goodval1 goodval2 goodval3 goodval4
Acceptable values for the keyword.
System action: The system does not complete the command issued.
Operator response: Reissue the MODIFY hisproc command with an acceptable value for the identified keyword.

44 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HIS006I • HIS007I

System programmer response: None.

Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCMD
Routing Code: -
Descriptor Code: 5

HIS006I MODIFY hisproc COMMAND SYNTAX ERROR. INCORRECT VALUE SPECIFIED FOR KEYWORD
keyword. THE ALLOWED RANGE IS min-hex TO max-hex.
Explanation: The system detected an incorrect value for the identified keyword in the MODIFY hisproc command.
The message displays the allowed range for the keyword. The value used in the command must be hexadecimal.
In the message text:
hisproc
The name of the HIS catalogued startup procedure.
keyword
The name of the keyword with the incorrect value.
min-hex
Minimum value allowed, in hexadecimal, for the keyword.
max-hex
Maximum value allowed, in hexadecimal, for the keyword.
System action: The system does not complete the command issued.
Operator response: Reissue the MODIFY hisproc command with an acceptable value for the identified keyword.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCMD
Routing Code: -
Descriptor Code: 5

HIS007I MODIFY hisproc COMMAND SYNTAX ERROR. INCORRECT VALUE SPECIFIED FOR KEYWORD
keyword. THE ALLOWED RANGE IS min-number TO max-number textval
Explanation: The system detected an incorrect value for the identified keyword in the MODIFY hisproc command.
The acceptable values for the keyword are listed in the message.
In the message text:
hisproc
The name of the HIS catalogued startup procedure.
keyword
The name of the keyword with the incorrect value.
min-number
Minimum value allowed, in decimal, for the keyword.
max-number
Maximum value allowed, in decimal, for the keyword.
textval
The textval value can be blank, or one of the following:

Chapter 5. HIS messages 45

HIS009I

MINUTES
The specified value is in minutes.
SAMPLES/MINUTE
The specified value is in the number of samples per minute.
PAGES/PROCESSOR
The specified value is in the number of 4096-byte pages per processor unit (CPU).
System action: The system does not complete the command issued.
Operator response: Reissue the MODIFY hisproc command with an acceptable value for the identified keyword.
If the identified keyword is DURATION, you can specify unlimited duration for event counters by omitting the
keyword.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCMD
Routing Code: -
Descriptor Code: 5

HIS009I MODIFY hisproc COMMAND FAILED. SPECIFIED PATH INACCESSIBLE. BPX1ACC SERVICE
FAILED with RC=returncode, RSN=reasoncode.
Explanation: The MODIFY hisproc command failed. The specified (or default) file PATH is not accessible. The path
either does not exist, or does not have the required read and write access attributes.
When the system issued the UNIX Systems Services BPX1ACC service to verify the PATH value, it failed and
returned the listed return code and reason code. See the following list for return and reason code meanings:
RC=9C (EMVSINITIAL) and RSN=xxxx00F9
The HIS User ID, hisproc, has not been defined by the security product. When you add user hisproc, you must
create an OMVS segment with a default HOME directory.
RC=81 (ENOENT)
The specified file PATH does not exist.
RC=86 (ENOSYS) or 6F (EACCES)
HIS cannot access the file path specified (or default) on the MODIFY hisproc command. The file path might not
have the appropriate read or write access attributes for HIS to access it.
The ENOSYS error might be caused by HIS not having the correct authority to access the HOME directory.
Other return and reason codes
See z/OS UNIX System Services Messages and Codes for information about the return and reason codes.

See z/OS UNIX System Services Programming: Assembler Callable Services Reference for information about the BPX1ACC
service.

If you did not specify a path on the command, or if a relative path is specified, the system uses the default path
defined by the HOME directory of the OMVS segment when the hisproc user was added to the system (using the
ADDUSER TSO command). You must create an OMVS segment with a default HOME directory when you set up the
hardware instrumentation services (HIS) user. The default file path, if valid, is the path for all the output files of the
MODIFY hisproc command. If you specify a file path on the MODIFY hisproc command, the command overrides the
HOME directory value. For more information about defining OMVS segments, see z/OS UNIX System Services
Planning.

In the message text:

hisproc
The name of the HIS catalogued startup procedure.

46 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HIS010I

returncode
The return code from BPX1ACC.
reasoncode
The reason code from BPX1ACC.
System action: The system does not complete the command issued.
Operator response: Refer to the return code and reason code in the message for the exact cause of this error.
v If you do not specify a path on the MODIFY hisproc command, verify that there is a default path defined on the
HOME directory keyword in the OMVS segment of the hisproc user.
v If you specify a relative path, verify that the full path (when concatenated with the HOME directory in the OMVS
segment of the hisproc user) exists.
v If the path exists, verify that the path has the proper read and write access attributes.

Note: The path name is case sensitive.

You can display the home directory in the OMVS segment of the hisproc user by issuing the following TSO command:
ListUser hisproc OMVS noracf

You can enter the path name in either absolute form (starting with a “/”), or relative form (without a “/”). If you use
the relative form, the system uses the HOME directory of the OMVS segment for the hisproc user.
System programmer response: Ensure your HIS user ID, hisproc, is correctly defined:
v If the HIS user ID, hisproc, has not been defined by the security product, add the hisproc user ID by the following
TSO command, where the UID and HOME values are just examples:
ADDUSER hisproc OMVS(UID(25) HOME(’/user’))
v Specify a HOME directory in the OMVS segment for the added hisproc user. The HOME directory is the default
PATH for the MODIFY hisproc command.
v Add an OMVS segment or HOME directory to the hisproc user by the following TSO command, where the UID
and HOME values are just examples
ALTUSER hisproc OMVS(UID(25) HOME(’/user’))
v Create the HOME directory (or any specific file path) using the mkdir OMVS command. Set up appropriate file
access attributes with the chmod or chown OMVS commands.
If the problem was caused by a path or user ID setup error, you must correct the error and then stop (STOP hisproc)
and restart (START hisproc) the HIS address space before beginning data collection again. If you do not stop and
restart the HIS address space, the error can recur, even if you corrected it. You must restart the HIS address space for
any of the following actions:
v Defining a new path using mkdir
v Modifying the access attributes of an existing path using chmod
v Adding (ADDUSER) or altering (ALTUSER) the hisproc user ID. This includes (but is not limited to) altering the
OMVS segment or the HOME directory
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCMD
Routing Code: -
Descriptor Code: 5

HIS010I MODIFY hisproc,BEGIN COMMAND IGNORED. DATA COLLECTION ALREADY IN PROGRESS.

Explanation: The system cannot start processing the MODIFY hisproc,BEGIN command because HIS data collection is
already in progress.
In the message text:
hisproc
The name of the HIS catalogued startup procedure.

Chapter 5. HIS messages 47

HIS011I • HIS012I

System action: The system does not complete the command issued.
Operator response: End the ongoing HIS data collection by issuing the MODIFY hisproc,END before issuing a new
MODIFY hisproc,BEGIN request.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCMD
Routing Code: -
Descriptor Code: 5

HIS011I hisproc DATA COLLECTION STARTED

Explanation: Data collection has started in response to a MODIFY hisproc command.
In the message text:
hisproc
The name of the HIS catalogued startup procedure.
System action: The system continues processing.
Operator response: None.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISINIT
Routing Code: 2
Descriptor Code: 4

HIS012I hisproc DATA COLLECTION ENDED

Explanation: Data collection has ended because a MODIFY hisproc command has ended. The command has ended
because of one of the following reasons:
v In response to a STOP hisproc command
v In response to a MODIFY hisproc,END command
v The data collection duration has expired
v An error occurred

In the message text:

hisproc
The name of the HIS catalogued startup procedure.
System action: The system continues processing.
Operator response: None.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISINIT
Routing Code: 2
Descriptor Code: 4

48 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HIS013I • HIS014I

HIS013I MODIFY hisproc COMMAND SYNTAX ERROR.

textval keyword
Explanation: The system was unable to process the MODIFY hisproc command because of a syntax error. The
problem is one of the following situations:
v The value for the identified keyword must be enclosed within parentheses, but one or both parentheses might be
missing, or not in the expected locations.
v The EQUAL delimiter is missing from the identified keyword. For example, if the correct syntax for the keyword is
DURATION=30, this error message is issued if the identified keyword is specified as DURATION(30).
v The value for the identified keyword must be enclosed within single quotation marks, but one or both quotation
marks might be missing, or not in the expected locations.

In the message text:

hisproc
The name of the HIS catalogued startup procedure.
textval
text is one of the following descriptions:
MISSING LEFT OR RIGHT PARENTHESIS FOR KEYWORD keyword
A right or left parenthesis is missing for the identified keyword.
MISSING "EQUAL" DELIMITER FOR KEYWORD keyword
An equal delimiter ("=") is missing for the identified keyword.
MISSING SINGLE QUOTE DELIMITER FOR KEYWORD keyword
A single quotation mark delimiter is missing for the identified keyword.
keyword
The name of the keyword with the syntax error.
System action: The system does not complete the command issued.
Operator response: Correct and reissue the MODIFY hisproc command.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCMD
Routing Code: -
Descriptor Code: 5

HIS014I ERROR IN HARDWARE INSTRUMENTATION SERVICES. INSUFFICIENT BUFFER STORAGE

FOR THE AMOUNT IN THE BUFCNT KEYWORD.
Explanation: The hardware instrumentation services was unable to obtain sufficient buffer storage needed to process
the data collection request. The amount of storage to be obtained for each active processor is specified by the
BUFCNT keyword on the MODIFY hisproc command.
System action: The MODIFY hisproc command is not processed.
Operator response: There is insufficient system storage to process the MODIFY hisproc command. You can specify a
smaller BUFCNT value on the MODIFY hisproc command if the current value is too large.
Note that the BUFCNT value is the number of 4K pages to be used for each active processor in the configuration. It
is not the total buffer size for all the processors.
System programmer response: Make additional system storage available for the command.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISINIT

Chapter 5. HIS messages 49

HIS015I

Routing Code: -
Descriptor Code: 5

HIS015I hh.mm.ss DISPLAY HIS text

Explanation: This message is issued in response to the DISPLAY HIS command and displays the status or results of
the latest MODIFY hisproc command issued to start or stop collection of hardware event data. The contents of the
message will vary depending on the parameters issued with the MODIFY hisproc command.
In this message, text is:
hisproc hisasid statusn
COMMAND: MODIFY command-data
START TIME: yyyy/mm/dd hh:mm:ss
END TIME: yyyy/mm/dd hh:mm:ss
COMPLETION STATUS: comp-stat
FILE PREFIX: fileprefix
LOST SAMPLES: samplostcnt
COUNTER VERSION NUMBER 1: ctr-vers1
COUNTER VERSION NUMBER 2: ctr-vers2
COMMAND PARAMETER VALUES USED:
TITLE= title
PATH= pathname
DDNAME= ddname
COUNTER SET= ctrset-values
DURATION= duration-value (MINUTES)
CTRONLY
MAPONLY
BUFCNT= bufcnt (PAGES/PROCESSOR)
SAMPTYPE= samptype-values
SAMPFREQ= freq (SAMPLES/MINUTE)
DATALOSS= datalossact
STATECHANGE= statechange
SMFINTVAL= smfintval
MAPASID= xxxx
MAPJOB= zzzz

In the message text:

hh.mm.ss
The time in hours (00-23), minutes (00-59), and seconds (00-59) for the DISPLAY HIS command.
hisproc
The name of the (HIS) catalogued startup procedure.
hisasid
The address space ID of HIS.
status
The status of HIS, which is one of the following status:
NOT STARTED
HIS is not started.
IDLE
HIS is waiting for work.
ACTIVE
HIS is currently active and working.
ENDED
HIS has ended.
COMMAND: command-data
The text of the MODIFY hisproc command.
START TIME: yyyy/mm/dd hh:mm:ss

50 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HIS015I

yyyy/mm/dd
The date in year/month/day format when the MODIFY hisproc command started.
hh:mm:ss
The time in hours (00-23): minutes (00-59):seconds (00-59) format when the MODIFY hisproc command
started.
END TIME: yyyy/mm/dd hh:mm:ss
yyyy/mm/dd
The date in year/month/day format when the MODIFY hisproc command ended. If data collection is
still active, the end date will be displayed as ----/--/--.
hh:mm:ss
The time in hours (00-23): minutes (00-59):seconds (00-59) format when the MODIFY hisproc command
ended. If data collection is still active, the end time will be displayed as --:--:--.
COMPLETION STATUS: comp-stat
The command completion status can be:
NORMAL
The Modify hisproc command has completed normally. SMF records and OMVS output files are valid.
ABNORMAL
The Modify hisproc command has abnormally ended. SMF records and OMVS output files might be
incomplete and unusable.
-------- Data collection is still active. Output files are incomplete.
FILE PREFIX: fileprefix
The prefix for all the data collection output files. fileprefix is in the format SYSHISyyyymmdd.hhmmss.
LOST SAMPLES: samplostcnt
SampLostCnt is the cumulative running count of lost samples on all the processors because of buffer overflow
errors.
COUNTER VERSION NUMBER 1: ctr-vers1
ctr-vers1 is the version number for the basic and problem state counter sets that HIS is recording.
Note that the meaning and the number of counters in a counter set might change with a new machine model.
This counter set version number defines the contents of the basic and problem-state counter sets that are
installed on the machine. For more information about these counters for the supported counter version number
for each model, see publications on the Resource Link® home page at http://www.ibm.com/servers/
resourcelink.
COUNTER VERSION NUMBER 2: ctr-vers2
ctr-vers2 is the version number for the crypto-activity and extended counter sets that HIS is recording.
Note that the meaning and the number of counters in a counter set might change with a new machine model.
This counter set version number defines the contents of the basic and problem-state counter sets that are
installed on the machine.For more information about these counters for the supported counter version number
for each model, see publications on the Resource Link home page at http://www.ibm.com/servers/resourcelink.
TITLE= title
title is the text data from the TITLE= parameter on the MODIFY hisproc command.
PATH= pathname
pathname is the name of the path specified on the PATH= parameter of the MODIFY hisproc command.
DDNAME= ddname
ddname is the data definition name specified on the DDNAME= parameter of the MODIFY hisproc command.
COUNTER SET= ctrset-values
ctrset-values displays a list of the counter sets requested in the MODIFY hisproc command.
DURATION= duration-value (MINUTES)
duration-value displays the duration value, in minutes, of this run of HIS data collection.
CTRONLY
Indicates if you specified CTRONLY on the MODIFY hisproc command.

Chapter 5. HIS messages 51

 HIS015I

MAPONLY
Indicates if you specified MAPONLY on the MODIFY hisproc command.
BUFCNT= bufcnt
The value of the BUFCNT parameter on the MODIFY hisproc command in number of 4096-byte pages per
processor.
SAMPTYPE= samptype-values
samptype-values displays a list of the sample functions requested in the MODIFY hisproc command.
SAMPFREQ= freq
freq displays the sample frequency requested on the SAMPFREQ parameter on the MODIFY hisproc command in
number of samples per minute.
DATALOSS= datalossact
datalossact displays the action requested on the DATALOSS parameter on the MODIFY hisproc command for
| when data loss occurs during the instrumentation run. The datalossact value is one of the following:
IGNORE
Ignore the condition and continue with data sampling.
STOP
End the data sampling operation.
STATECHANGE= statechange
Displays the action requested in the MODIFY hisproc command if a significant state change is detected.
statechange is one of the following:
SAVE
Save the run data, marking an interval. Start the next interval for the current run.
IGNORE
Continue the current run.
STOP
Stop the run at the state change.
SMFINTVAL= smfintval
If SYNC, the recording is synchronized with the SMF global recording interval. Otherwise, the duration of time
between SMF record type 113, in minutes. For more information, see the topic on SMF global recording interval
in z/OS MVS System Management Facilities (SMF).
MAPASID= xxxx
This field is displayed if you requested load module mapping in the MODIFY hisproc command.
This field displays one or more address space IDs either from those entered on the MAPASID parameter or
derived from the MAPJOB parameter. The MAPASID parameter specifies the address space ID for which you
needed to collect load module mapping data.
Note that the job names in the MAPJOB parameter are converted to address space IDs at the point when load
module mapping data is to be collected, which is at the end of the data collection. No derived address space IDs
are displayed before this point.
MAPJOB= zzzz
This field is displayed if you requested load module mapping in the MODIFY hisproc command.
This field displays job name values from the MAPJOB parameter for which you needed to collect load module
mapping data.
System action: The system continues processing
Operator response: None.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISODSP
Routing Code: -

52 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HIS016I • HIS017I

Descriptor Code: 5

HIS016I HARDWARE INSTRUMENTATION SERVICES INVOCATION OF servicename SERVICE FAILED.

RC=returncode, RSN=reasoncode.
Explanation: The named service failed and returned a return code and reason code.
In the message text:
servicename
The name of the service that failed.
returncode
The hexadecimal return code from the failed service.
reasoncode
The hexadecimal reason code from the failed service.
System action: The requested operation failed. The system might issue additional error messages about the problem.
Operator response: Refer to accompanying error messages from the failed service.
If the failed service is a BPX1xxx service, refer to the following documentation:
v z/OS UNIX System Services Programming: Assembler Callable Services Reference for information about the service that
failed.
v z/OS UNIX System Services Messages and Codes for information about the return and reason codes from the service
that failed.
Retry the operator command and report the problem if it persists.
System programmer response: Refer to the error messages or dumps from the failed service
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISINIT, HISODSP, HISPCMD
Routing Code: 1,2
Descriptor Code: 4

HIS017I START hisproc COMMAND FAILED. SYSTEM STORAGE IS UNAVAILABLE

Explanation: This START hisproc command failed. Hardware instrumentation services (HIS) was unable to obtain
sufficient system storage to initialize the HIS address space.
In the message text:
hisproc
The name of the HIS catalogued startup procedure.
System action: Start hisproc command processing ends.
Operator response: There is insufficient system storage to process the START hisproc command. Retry the operation
at a later time.
System programmer response: Prepare additional system storage available.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISINIT
Routing Code: -
Descriptor Code: 5

Chapter 5. HIS messages 53

 HIS018I • HIS019I

HIS018I ERROR WRITING FILE filename.

SOME INSTRUMENTATION DATA CANNOT BE WRITTEN.
Explanation: Hardware instrumentation services (HIS) encountered an error writing to the identified
instrumentation file while processing a MODIFY hisproc command. Fewer data bytes than requested are written. It
might be caused by one of the following reasons:
The amount of data to be written is greater than the remaining space on the output device.
The amount of data to be written is greater than the file size limit for the process.

In the message text:

filename
The name of the output data file in UNIX System Services file format.
System action: The system failed the MODIFY hisproc command. The identified file is only partially created. The file
might not contain useful information.
Operator response: Verify that sufficient disk space is allocated to the identified UNIX Systems Services file, and
that the file size limit for the process is not exceeded. Issue the DISPLAY OMVS,OPTIONS command to list the current
limit value of MAXFILESIZE. If necessary, increase the MAXFILESIZE value using the SETOMVS MAXFILESIZE=nnnn
system command.
System programmer response: If the identified file has insufficient disk space, prepare additional disk space
available to the file directory. If the error is caused by the file size limit, increase the limit by issuing a SETOMVS
MAXFILESIZE=nnnn system command. See z/OS MVS System Commands for details.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCTR
Routing Code: 1,2
Descriptor Code: 4

HIS019I

EVENT COUNTERS INFORMATION

VERSION: version
FILE NAME: filename
COMMAND: command-data
| LOSS OF SAMPLE DATA ALERT: lost_sample
| SAMPLE BUFFER OVERFLOW COUNT: lost-samp-cnt
| LOSS OF COUNTER DATA ALERT: lost_counter
STATE CHANGE: statechange
| MODEL: mach-type-mach-model
COUNTER VERSION NUMBER 1: ctr-vers1
COUNTER VERSION NUMBER 2: ctr-vers2
COUNTER SET= ctrset-type
COUNTER IDENTIFIERS: ctrnum: ctr-desc
START TIME: yyyy/mm/dd hh:mm:ss
START TOD: hhhhhhhhhhhhhhhh
END TIME: yyyy/mm/dd hh:mm:ss
END TOD: hhhhhhhhhhhhhhhh
COUNTER VALUES (HEXADECIMAL)
FOR CPU cpunum
(CPU SPEED = cpuspeed CYCLES/MIC):
ctrnum1 – ctrnum2 yyy
Explanation: This message is written to a z/OS UNIX Systems Services file to list the event counter names and net
event counter values at the end of the instrumentation run. When the instrumentation run was initiated by a MODIFY
hisproc command, the initial event counter values are remembered. At the end of the run, the final event counter
values are captured. The displayed counter values are the delta incremental values of the instrumentation run on the
specified processor.

54 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HIS019I

Notes:
1. Each processor has its own set of event counters.
2. The END TIME will not be available for a processor that was once configured offline during the run.
3. The meaning and the number of counters in a counter set might change with a new machine model. Two counter
set version numbers are provided to identify the contents of the installed counter sets that are being recorded. For
information about the counters for the supported counter version number for each model, see publications on the
Resource Link home page at http://www.ibm.com/servers/resourcelink.

In the message text:

version
Version number of this message.
filename
The name of the output data file in z/OS UNIX file format.
command-data
The text of the MODIFY hisproc command.
| lost_sample
| If sampling is active during this run, indicates if sampling data has been lost because of hardware internal busy
| conditions; lost_sample is one of the following:
| YES Sample data loss was detected by the hardware.
| NO Sample data loss was not detected by the hardware.
lost-samp-cnt
If sampling is active during this run, lost-samp-cnt shows the total count of lost samples because of buffer
overflow errors.
| lost_counter
| Indicates if counter data has been lost because of hardware internal busy conditions; lost_counter is one of the
| following:
| YES Counter data loss was detected by the hardware.
| NO Counter data loss was not detected by the hardware.
statechange
Determine whether a state change has occurred during the time period this data represents, and what action was
taken. statechange is one of the following:
YES,STOP
State change detected, run was ended at state change. This interval represents the entire collection run.
YES,IGNORE
State change detected, run continued to normal end of run. This interval represents the entire collection
run.
YES,SAVE
State change detected, run will continue to normal end of run. This interval includes data up to the
state change. You can expect another file having the same file prefix with an increased sequence number
to contain the interval after the state change.
NO No state change was detected, run has ended normally. If the sequence number is 000 then this interval
represents the entire collection run. Otherwise, there were one or more state changes, and this interval
only represents data from the most recent state change to the end of the collection.
| mach-type
| The machine type Hardware Instrumentation Services (HIS) is running on.
| mach-model
| The machine model HIS is running on.
ctr-vers1
ctr-vers1 is the version number for the basic and problem-state counter sets that HIS is recording.

Chapter 5. HIS messages 55

HIS019I

This counter set version number defines the contents of the basic and problem-state counter sets that are
installed on the machine.
ctr-vers2
ctr-vers2 is the version number for the crypto-activity and extended counter sets that HIS is recording.
This counter set version number defines the contents of the crypto-activity and extended counter sets that are
installed on the machine.
ctrset-type
The counter set type. The counter values of each counter set will be displayed separately. ctrset-type is one of the
following:
BASIC The Basic counter set.
PROBLEM-STATE
The Problem-State counter set.
CRYPTO-ACTIVITY
The Crypto-activity counter set.
EXTENDED
The Extended counter set.
ctrnum
The counter number.
ctr-desc
The name of the counter identified by ctrnum. The counters in the Extended counter set depend on the machine
model.
yyyy/mm/dd
The date in year, month, and day when the instrumentation started or ended (or for this interval if a state
change occurred).
hh:mm:ss
The time in hours (00-23), minutes (00-59), and seconds (00-59) when the instrumentation started or ended (or for
this interval if a state change occurred).
hhhhhhhhhhhhhhhh
The time-of-day (TOD) value in hexadecimal format to show the time when the MODIFY hisproc command
started or ended (or for this interval if a state change occurred). If the TOD is not available, the end date will be
displayed as ----------------.
cpunum
The processor number (CPU) from which the event counters are collected.
cpuspeed
The processor speed (decimal) from which the event counters are being collected, in cycles/microsecond.
ctrnum1
Beginning event counter number of the listed range.
ctrnum2
Ending event counter number of the listed range.
yyy
One or more event counter values that are accumulated during the time period between the start time and end
time.
System action: The system continues processing.
Operator response: None.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCTR

56 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HIS020I • HIS022I

Routing Code: -
Descriptor Code: 4

HIS020I HARDWARE INSTRUMENTATION SERVICES MUST BE STARTED AS A STARTED TASK. JOB

jobname ENDS.
Explanation: The named batch job attempted to start hardware instrumentation services (HIS), but HIS must be
started as a started task.
In the message text:
jobname
The name of the batch job.
System action: The system ignores the request to start HIS.
Operator response: Enter a START hisproc command to start HIS.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISINIT
Routing Code: 1,2
Descriptor Code: 4

HIS021I UNEXPECTED ERROR OCCURRED. FILE filename MAY BE INCOMPLETE.

Explanation: Hardware instrumentation services (HIS) encountered an unexpected error while creating the
identified instrumentation file. The file might be incomplete.
In the message text:
filename
The name of the output data file in UNIX System Services file format.
System action: The system failed the MODIFY hisproc command. The identified file is only partially created. The file
might not contain useful information. An SVC dump might have already been taken for the unexpected error.
Operator response: If the problem recurs, contact the system programmer.
System programmer response: Search the problem reporting data bases for solving the problem. If you cannot solve
the problem, contact the IBM Support Center.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCTR
Routing Code: 1,2
Descriptor Code: 4

HIS022I hisproc DATA COLLECTION IS ENDING.

OUTPUT FILE PREFIX: fileprefix.
TITLE=title
Explanation: This message indicates that a HIS data collection run is ending, initiated by one of the following
events:
v STOP hisproc command.
v MODIFY hisproc,END command.
v Data collection duration expiration.
v An error occurring during data collection.

Chapter 5. HIS messages 57

HIS023I

v A state change was detected and the STATECHANGE action is STOP.

In addition to the SMF type 113 records, HIS produces a number of output files in the Unix System Services file
system.

Note: The jobs being measured in the data collection run must stay active for the mapping function to be performed.
If jobs end before the load module mapping is finished, (as indicated by system message HIS012I), the data collection
run might not include private load module information.
In the message text:
hisproc
The name of the HIS cataloged startup procedure.
fileprefix
fileprefix is the prefix for data collection output files in the UNIX System Services file format. The format for
fileprefix is , SYSHISyyyymmdd.hhmmss. The system generates the output files in the HOME directory that is
specified in the OMVS segment of the hisproc user, or in a user-specified directory.
title
Text data specified in the TITLE keyword in the MODIFY hisproc,BEGIN command. This helps you identify the
MODIFY command that started the data collection. If the TITLE keyword was not specified on the MODIFY
hisproc,BEGIN command, the message displays a null TITLE value.
System action: The system continues processing.
Operator response: None.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISINIT
Routing Code: 2
Descriptor Code: 4

HIS023I TOO MANY ADDRESS SPACES MATCHED BY WILDCARD MAPJOB NAMES.

NOT ALL CAN BE MAPPED FOR PRIVATE LOAD MODULE INFORMATION.
Explanation: During a data collection run initiated by the MODIFY hisproc command with parameter MAPJOB, the
system found that the number of address spaces that matched the requested wildcard MAPJOB names exceeds the
maximum that HIS supports. HIS supports a total of 128 address spaces for mapping load module information, using
a combination of the address spaces specified on the MAPJOB and MAPASID parameters. This message indicates
that HIS could not map all the requested MAPJOB address spaces, so the private load module and CSECT
information will not be produced for the address spaces that exceed the maximum supported.
System action: The system continues processing.
Operator response: Do one of the following:
v Reissue the command, ensuring that you specify 128 or less address spaces between the MAPJOB and MAPASID
parameters.
v If you need to map more than 128 address spaces, reissue the command using MAPASID=ALL. This maps the load
module information for all the active address spaces.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCMD
Routing Code: 2
Descriptor Code: 4

58 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HIS024I • HIS025I

HIS024I NO ACTIVE ADDRESS SPACES MATCHED BY THE MAPJOB LIST. PRIVATE LOAD MODULE
INFORMATION NOT MAPPED.
Explanation: During a data collection run initiated by the MODIFY hisproc command with parameter MAPJOB (but
not MAPASID), the system found that it could not match any active address spaces from the list specified on the
MAPJOB parameter. HIS will not produce any private load module information, but will produce mappings of the
LPA and the nucleus.
The system issues this informational message only if it is unable to match any active address spaces from the
information specified on the MAPJOB parameter (but not MAPASID) or if no MAPASID parameter has been
specified.

Note: The jobs being mentioned identified in the data collection run must stay active for the mapping function to be
performed. If the jobs end before the load module mapping is finished, (as indicated by system message HIS012I) the
data collection run might not include private load module information for the ended jobs.
System action: The system continues processing.
Operator response: Issue the command again if necessary, specifying one or more active address spaces on the
MAPJOB parameter. If private load module map information is not needed, you can let the current data collection
continue proceeding.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCMD
Routing Code: 2
Descriptor Code: 4

HIS025I DATA COLLECTION IS PREMATURELY ENDING.

failuretext
Explanation: During a data collection run initiated by the MODIFY hisproc command, the system encountered an
error that required that data collection stop. The output .SMP files are incomplete.
In the message text:
failuretext explaining the problem is one of the following:
SAMPLING BUFFER OVERFLOW OCCURRED
Meaning: The MODIFY command specified DATALOSS=STOP, and the hardware reported that sampling data
was lost.
Ensure that sufficient buffers are allocated for HIS data collection runs. You can specify the number of 4K data
buffers per processor for use in sampling by specifying the BUFCNT keyword on the MODIFY hisproc command.
To find the current BUFCNT setting, issue the DISPLAY HIS command during or after an instrumentation run.
Then, if appropriate, specify a larger BUFCNT value on the MODIFY hisproc command.
Operator action: You can display a running count of lost samples using the DISPLAY HIS command. If
occasional loss of data is tolerable, then specify DATALOSS=IGNORE, which is the default.
System programmer action: If sufficient buffers are assigned for HIS data collection and the error persists, verify
that an appropriate dispatching priority has been assigned to the instrumentation task to allow it to write the full
buffers to the file without delay.
SAMPLE FUNCTIONS AUTHORIZATION CONTROL CHANGED
Meaning: The authorization for the sampling facilities supported on this CPU changed while data collection was
active. Data collection results are unpredictable. The .SMP output files might be incomplete.
Operator action: You must authorize to the sampling facility types specified on the SAMPTYPE parameter of the
MODIFY hisproc command before starting HIS data collection runs. If you change the authorization for either the
sampling facilities or counter sets that are in-use while data collection is active, the data collection ends
prematurely. For information about how to set up the authorization of the sampling facilities and counter sets

Chapter 5. HIS messages 59

 HIS026I

through the support element (SE) console, see Support Element Operations Guide for IBM System z10™ machine on
the Resource Link home page at http://www.ibm.com/servers/resourcelink.
System programmer action: Avoid changing the authorization of the sampling facilities or counter sets during
the HIS data collections runs.
EVENT COUNTERS AUTHORIZATION CONTROL CHANGED
Meaning: The authorization for the counter sets supported on this CPU changed while data collection was
active. Data collection results are unpredictable. The .CNT output file might not be available.
Operator action: You must get authorized to the counter sets through the support element (SE) console before
starting the HIS data collection. If you change the authorization of either the sampling facilities or counter sets
that are in used while data collection is active, data collection ends prematurely. For information about how to
set up the authorization of the counter sets through the support element (SE) console, see Support Element
Operations Guide for IBM System z10 machine on the Resource Link home page at http://www.ibm.com/
servers/resourcelink.
System programmer action: Avoid changing the authorization of the sampling facilities or counter sets during
the HIS data collection runs.
MACHINE REPORTED SAMPLING DATA LOSS
| Meaning: The MODIFY command specified DATALOSS=STOP, and sampling data might be lost because of
| hardware internal busy conditions.
Operator action: If sampling data is lost because of internal hardware conditions, retry the operation. Report the
error to the system programmer if the error persists.
System programmer action: If sampling data is lost because of internal hardware busy conditions, search
problem reporting databases for solving the problem. If you cannot solve the problem, contact the IBM Support
Center.
MACHINE REPORTED COUNTER DATA LOSS
| Meaning: The MODIFY command specified DATALOSS=STOP, and counter data might be lost because of
| hardware internal busy conditions.
Operator action: If counter data is lost because of internal hardware conditions, retry the operation. Report the
error to the system programmer if the error persists.
System programmer action: If counter data is lost because of the internal hardware busy conditions, search
problem reporting data bases for solving the problem. If you cannot solve the problem, contact the IBM Support
Center.
System action: The system continues processing.
Operator response: See the operator action in the explanation for the particular failure text displayed.
System programmer response: See the System programmer action in the explanation for the particular failure text
displayed.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPWRK, HISINIT
Routing Code: 2
Descriptor Code: 4

HIS026I MODIFY hisproc COMMAND CANNOT BE PROCESSED.

failure-text
Explanation: The system could not process a MODIFY hisproc command because the CTRSET or SAMPTYPE
parameter values requested are either:
v Not supported on this CPU
v Not installed on this CPU
v Are not authorized for use

60 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HIS026I

The CTRSET parameter specifies the counter sets you use to collect data on a run:
v B (basic) and P or PROB (problem state) counter sets may be used if they are installed on the IBM System z10 or
later machines. You must first get authorized to use these counter sets explicitly through the SE console.
v C (Crypto) and E (extended) counter set availability is model dependent and installation is optional. These counter
sets also require explicit authorization through the SE console.
For information about how to set up the authorization of the counter sets, see Support Element Operations Guide for
IBM System z10 machine on the Resource Link home page at http://www.ibm.com/servers/resourcelink.

The SAMPTYPE specifies the sampling facility types you want to collect on a data run:
v The B (basic) sampling facility is installed and available on all the IBM System z10 or later machines. However,
you must authorize the sampling facility through the SE console explicitly.
v The D (diagnostic) sampling facility availability is CPU model dependent and installation is optional. This
sampling facility also requires explicit authorization through the SE console.
For information about how to set up the authorization of the sampling facilities, see Support Element Operations Guide
for System z10 machine on the Resource Link home page at http://www.ibm.com/servers/resourcelink.

In the message text:

hisproc
The name of the HIS cataloged startup procedure.
failure-text
The failure-text explaining the problem is one of the following ones:
BASIC COUNTER SET IS UNAUTHORIZED
The Basic counter set is unavailable.
System programmer action: Ensure that you authorize the indicated counter set for use by the hisproc
HIS Catalogued startup procedure.
PROBLEM-STATE COUNTER SET IS UNAUTHORIZED
The Problem-state counter set is unavailable.
System programmer action: Ensure that you authorize the indicated counter set for use by the hisproc
HIS Catalogued startup procedure.
CRYPTO-ACTIVITY COUNTER SET IS UNAVAILABLE
The Crypto-activity counter set is unavailable.
System programmer action: Ensure that the indicated optional counter set, if desired, is installed and
authorized for use by the hisproc HIS Catalogued startup procedure.
EXTENDED COUNTER SET IS UNAVAILABLE
The Extended counter set is unavailable.
System programmer action: Ensure that the indicated optional counter set, if desired, is installed and
authorized for use by the hisproc HIS Catalogued startup procedure.
BASIC SAMPLING FUNCTION IS UNAUTHORIZED
The Basic sample function is unavailable.
System programmer action: Ensure that you authorize the basic sampling function for use by the
hisproc HIS Catalogued startup procedure.
DIAGNOSTIC SAMPLING FUNCTION IS UNAVAILABLE
The Diagnostic sample function is unavailable.
System programmer action: Ensure that the indicated optional sampling function is installed and
authorized for use by the hisproc HIS Catalogued startup procedure.
NO COUNTER SETS ARE AVAILABLE
No counters are installed or authorized.
System programmer action: Ensure that you authorize the indicated counter set for use by the hisproc
HIS Catalogued startup procedure.

Chapter 5. HIS messages 61

HIS027I

System action: The system does not process the command issued.
Operator response: Ensure that all the specified counter sets (CTRSET parameter) or sampling facility types
(SAMPTYPE parameter) are installed and authorized on this system.
System programmer response: See the System programmer action in the explanation for the particular failure text
displayed.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCMD
Routing Code: -
Descriptor Code: 5

HIS027I COMMAND DELIMITER ERROR OR UNRECOGNIZED KEYWORD IN COMMAND FILE

SPECIFIED BY DDNAME: ddname
KEYWORD LAST PROCESSED: lastkw
Explanation: The system could not process a MODIFY hisproc command because it encountered one of the following
errors in the command file specified by the ddname displayed:
v A delimiter error in the command. For example, this might mean that a delimiter is missing or incorrectly placed.
The valid delimiters are:
– blank
– =
– (
– )
– '
v An unrecognizable keyword. This might be caused by:
– An incorrect keyword or keyword value that has longer number of characters than the maximum number of the
characters permitted.
– Keywords or keyword values that are not upper case. You must enter command keywords into the MVS
command file in UPPER case. Keyword values must also be entered in UPPER case, unless they are a quoted
string, which can be in mixed case.

In the message text:

ddname
The data definition name for the command file specified on the DDNAME parameter of the command.
lastkw
The name of the last keyword that was processed or was being processed when the system encountered the
error.
System action: The system does not process the command issued.
Operator response: Reissue the MVS command file (displayed in ddname) and ensure that:
v The value entered for the specified keyword is the correct length and that both keyword and keyword values are
all upper case.
v Delimiters entered for the command in the command file are in matched pairs.
v Quotation marks or parenthesis are entered in matched pairs.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCMD
Routing Code: -

62 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HIS028I • HIS029I

Descriptor Code: 5

HIS028I ERROR PROCESSING MVS COMMAND FILE: ddname.

failure-text
Explanation: The system could not process a MODIFY hisproc command because the system detected an error in the
DDNAME parameter. The MODIFY command specifies a DDNAME for an MVS command file containing the data
collection keywords. However, the specified ddname is incorrect, as displayed in the failure-text explanation.
In the message text:
ddname
The ddname identifies the MVS command file that contains the incorrect DDNAME.
failure-text
One of the following:
INCORRECT DDNAME SPECIFIED
Indicates that the DDNAME specified does not exist.
INCORRECT COMMAND FILE RECFM FORMAT
Indicates that the MVS command file the ddname specifies is in the wrong RECFM format. It must be a
RECFM format of LRECL=80 fixed-length record.
System action: The system does not process the command issued.
Operator response: Ensure that the ddname specified is correct and that it correctly identifies an MVS command file
with LRECL=80 fixed-length records and issue the command again.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCMD
Routing Code: -
Descriptor Code: 5

HIS029I ALL COUNTER SETS REQUESTED. SOME ARE UNAVAILABLE.

DATA COLLECTION CONTINUES WITH THE FOLLOWING COUNTER SETS:
CtrSetList
Explanation: A MODIFY hisproc command specified CTRSET=ALL, to request that all event counter sets be
recorded. However, not all the counter sets are installed or available. Data collection continues with the counter sets
that are installed and available.
CtrSetList
CtrSetList displays a list of the counter sets that are available.
System action: The system continues processing.
Operator response: If you want to perform data collection with more counter sets than the ones currently listed,
ensure that all wanted counter sets are installed and authorized for use by the hisproc z/OS cataloged startup
procedure for HIS.
You can explicitly specify the counter sets to be used by requesting them on the MODIFY hisproc command with the
CTRSET parameter. If you try to specify counter sets that are unavailable, the system issues message HIS026I to that
effect.
System programmer response: Verify that the required counter sets are installed and authorized.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCMD
Routing Code: -

Chapter 5. HIS messages 63

HIS030I • HIS031I

Descriptor Code: 5

HIS030I ERROR PROCESSING FILE: filename.

servicename FAILED WITH RC= returncode, RS= reasoncode.
Explanation: The system could not process a MODIFY hisproc command because the system detected an error when
processing the identified z/OS UNIX System Services file. Hardware instrumentation services issued a service, but
the service failed with a return code and a reason code.
In the message text:
filename
The name of an output data file in the UNIX System Services file format.
servicename
The name of the service that failed.
returncode
Return code that is issued with the failed service.
reasoncode
Reason code that is issued with the failed service.
System action: The system continues processing.
Operator response: If the failed service is a BPX1xxx service:
v For more information about the failed service, see z/OS UNIX System Services Programming: Assembler Callable
Services Reference.
v For the meanings and actions for the return code and reason code that were issued with the failed service, see
z/OS UNIX System Services Messages and Codes.

If running concurrently on multiple LPARS with a shared file system, and the failed service is BPX1OPN with RC=75
(EEXIST), the error might be caused by an incorrect configuration. A unique path for the output file must be created
for each LPAR sharing the file system. Correct the z/OS UNIX file problem and try the operator command again.

Otherwise, search the problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support
Center.
System programmer response: See the error messages or dumps from the failed service, if any.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISPCTR, HISPWRK
Routing Code: 1,2
Descriptor Code: 4

HIS031I REQUESTED FUNCTION IS UNSUPPORTED BY HARDWARE

Explanation: The system received a request to start the hardware instrumentation services (HIS), but the HIS
function is not supported by the current hardware. The HIS function can only be started on the hardware with the
CPU measurement facility installed. The facility is currently not installed on this machine.
System action: The system continues processing.
Operator response: None.
System programmer response: Verify that the appropriate CPU measurement facility is installed on the hardware.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISINIT
Routing Code: -

64 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HIS032I • HIS034I

Descriptor Code: 5

HIS032I STATE CHANGE DETECTED. ACTION=statechange.

Explanation: Hardware instrumentation services (HIS) detected a change in the system. The action specified in the
STATECHANGE parameter on the command has taken place.
In the message text:
statechange
Displays the action requested in the MODIFY hisproc command if a state change of the system occurs. statechange
is one of the following:
SAVE Save the run data, marking an interval. Start the next interval for the current run.
IGNORE
Continue the current run.
STOP Stop the run at the state change.
System action: The system takes the action specified.
Operator response: None.
System programmer response: None.
Problem determination: None.
Source: Hardware instrumentation services (HIS)
Detecting Module: HISINIT
Routing Code: 2
Descriptor Code: 4

| HIS034I DATA LOSS HAS OCCURRED, DATA COLLECTION CONTINUES. failure-text

| Explanation: During a data collection run initiated by the MODIFY hisproc command, the system encountered an
| error that caused data collection to be incomplete. The output .CNT and .SMP files might be incomplete. In the
| message text:
| failure-text
| is one of the following values:
| SAMPLING BUFFER OVERFLOW OCCURRED
| The MODIFY command specified DATALOSS=IGNORE, and the hardware reported that sampling data
| was lost.
| Ensure that sufficient buffers are allocated for HIS data collection runs. You can specify the number of
| 4K data buffers per processor for use in sampling by specifying the BUFCNT keyword on the MODIFY
| hisproc command. To find the current BUFCNT setting, issue the DISPLAY HIS command during or
| after an instrumentation run. Then, if appropriate, specify a larger BUFCNT value on the MODIFY
| hisproc command.
| Operator action: You can display a running count of lost samples using the DISPLAY HIS command.
| System programmer action: If sufficient buffers are assigned for HIS data collection and the error
| persists, verify that an appropriate dispatching priority has been assigned to the instrumentation task to
| allow it to write the full buffers to the file without delay.
| MACHINE REPORTED SAMPLING DATA LOSS
| The MODIFY command specified DATALOSS=IGNORE, and the hardware indicated sampling data
| might be lost because of hardware internal busy conditions.
| Operator action: Report the problem to the system programmer if the error persists.
| System programmer action: Sampling data is lost because of internal hardware busy conditions; search
| problem reporting databases for solving the problem. If you cannot solve the problem, contact the IBM
| Support Center.

Chapter 5. HIS messages 65

| MACHINE REPORTED COUNTER DATA LOSS
| The MODIFY command specified DATALOSS=IGNORE, and the hardware indicated counter data might
| be lost because of hardware internal busy conditions.
| Operator action: Report the problem to the system programmer if the error persists.
| System programmer action: Counter data is lost because of internal hardware busy conditions; search
| problem reporting databases for solving the problem. If you cannot solve the problem, contact the IBM
| Support Center.
| System action: The system processing continues.
| Operator response: See the operator action in the explanation for the particular failure text displayed.
| System programmer response: See the system programmer action in the explanation for the particular failure text
| displayed.
| Problem determination: None.
| Source: Hardware instrumentation services (HIS)
| Detecting Module: HISPWRK, HISINIT
| Routing Code: 2
| Descriptor Code: 4

66 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Chapter 6. HWI messages
HWI001I BCPII IS ACTIVE.
Explanation: The base control program internal interface (BCPii) address space is ready to process work.
System action: The system continues processing.
Operator response: None.
Application Programmer Response: None.
User response: None.
System programmer response: None.
Detecting Module: HWIAMIN2
Routing Code: 2
Descriptor Code: 4

HWI002I BCPII IS ALREADY ACTIVE.

Explanation: An operator tried to start the HWIBCPII component through the START HWISTART command when
the BCPii component was already active on MVS.
System action: BCPii remains active.
Operator response: None.
Application Programmer Response: None.
User response: None.
System programmer response: If BCPii APIs appear to be operating properly, no further action is required.
Detecting Module: HWIAMIN2
Routing Code: 2
Descriptor Code: 4

HWI003I BCPII ADDRESS SPACE CREATE FAILED. RC=rc, RSN=rsn.

Explanation: The BCPii address space create (ASCRE) failed.
In the message text:
rc The return code returned from the ASCRE macro.
rsn
The reason code returned from the ASCRE macro.
System action: The system does not start the BCPii component.
Operator response: Contact the system programmer.
Application Programmer Response: None.
User response: None.
System programmer response: Try to restart the BCPii address space. Consult the topic about BCPii in z/OS MVS
Programming: Callable Services for High-Level Languages. Search problem reporting data bases for a fix for the problem.
If no fix exists, contact the IBM Support Center.
Detecting Module: HWIAMIN1
Routing Code: 2

© Copyright IBM Corp. 1988, 2012 67

HWI004I • HWI007I

Descriptor Code: 4

HWI004I IMPROPER ATTEMPT TO INITIALIZE BCPII.

Explanation: There was an attempt to initialize BCPii improperly.
System action: An improper attempt to initialize BCPii has been rejected. BCPii is prevented from being submitted
as a job, and from being started as a task inappropriately. There is no effect on the BCPii address space.
Operator response: If required, BCPii can be initialized by referring to the HWISTART procedure.
Application Programmer Response: None.
User response: None.
System programmer response: Try to restart the BCPii address space through an IPL or the S HWISTART command.
Consult the topic about BCPii in z/OS MVS Programming: Callable Services for High-Level Languages. If the problem
recurs, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center.
Detecting Module: HWIAMIN1,HWIAMIN2
Routing Code: 2
Descriptor Code: 4

HWI005I STOP REQUEST WAS RECEIVED BY BCPII.

Explanation: The system has received the STOP HWIBCPII command that the operator issued, and is now
processing the request.
System action: Stop processing continues.
Operator response: None.
Application Programmer Response: None.
User response: None.
System programmer response: None.
Detecting Module: HWIAMIN2
Routing Code: 2
Descriptor Code: 4

HWI006I BCPII ADDRESS SPACE HAS ENDED.

Explanation: The BCPii address space has ended.
System action: BCPii services are not available until the address space is restarted.
Operator response: None.
Application Programmer Response: None.
User response: None.
System programmer response: None.
Detecting Module: HWIAMRSM
Routing Code: 2
Descriptor Code: 4

HWI007I BCPII IS ATTEMPTING COMMUNICATION WITH THE LOCAL CENTRAL PROCESSOR

COMPLEX (CPC).
Explanation: BCP initialization is attempting communication with the local central processing complex (CPC).
System action: BCPii address space initialization continues.

68 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HWI008I • HWI009I

Operator response: None.

Application Programmer Response: None.
User response: None.
System programmer response: None.
Detecting Module: HWIAMIN2
Routing Code: 1,2
Descriptor Code: 4

HWI008I BCPII FAILED TO CONNECT TO THE LOCAL CENTRAL PROCESSOR COMPLEX (CPC). RC=rc,
RSN=rsn. BCPII INITIALIZATION IS HALTED.
Explanation: BCPii initialization cannot connect to the host CPC.
In the message text:
rc The return code received from the internal invocation of the HWICONN API call made to the local CPC by
BCPii.
rsn
The reason code received from the diagnostic area of the HWICONN API call.
System action: BCPii initialization is stopped.
Operator response: Contact the system programmer.
Application Programmer Response: None.
User response: None.
System programmer response:
v Consult the topic about BCPii in z/OS MVS Programming: Callable Services for High-Level Languages and determine
the cause of the rc and rsn values returned from this message.
v Consult the topic about BCPii setup and installation in z/OS MVS Programming: Callable Services for High-Level
Languages for possible installation errors, omissions, or both.
Detecting Module: HWIAMIN2
Routing Code: 1,2
Descriptor Code: 4

HWI009I BCPII WAS UNABLE TO LOAD PART loadmod DURING INITIALIZATION. LOAD ABEND
CODE=abendcode, RSN=rsn. BCPII INITIALIZATION IS HALTED.
Explanation: BCPii initialization could not load the required module.
In the message text:
loadmod
The load module name that failed to load.
abendcode
The LOAD abend code.
rsn
The LOAD abend reason code.
System action: BCPii initialization is stopped.
Operator response: Contact the system programmer.
Application Programmer Response: None.
User response: None.

Chapter 6. HWI messages 69

HWI010I • HWI012I

System programmer response: Validate that this loadmod name exists in the configuration and is accessible through
LPA or LNKLST.
If the loadmod identified is CELHV003, the required Language Environment (LE) loadmods for BCPii are not
installed properly. To determine which libraries BCPii requires to be accessible, see the topic about BCPii in z/OS
MVS Programming: Callable Services for High-Level Languages.
Detecting Module: HWIAMIN1,HWIAMIN2
Routing Code: 1,2
Descriptor Code: 4

HWI010I BCPII DOES NOT OPERATE ON A VM GUEST. BCPII INITIALIZATION IS HALTED.

Explanation: BCPii operates only when running on a native z/OS image. BCPii does not initialize when running on
a VM guest.
System action: BCPii initialization is stopped.
Operator response: None.
Application Programmer Response: None.
User response: None.
System programmer response: If BCPii is required to be active, it needs to run on a native z/OS image.
Detecting Module: HWIAMIN2
Routing Code: 1,2
Descriptor Code: 4

HWI011I A NON-RECOVERABLE ERROR HAS OCCURRED IN BCPII INITIALIZATION.

Explanation: A severe system error has occurred that prevents BCPii from initializing.
System action: BCPii initialization is stopped.
Operator response: Contact the system programmer.
Application Programmer Response: None.
User response: None.
System programmer response: Try to restart the BCPii address space. Search problem reporting data bases for a fix
for the problem. If no fix exists, contact the IBM Support Center.
For additional information, see the topic about BCPii in z/OS MVS Programming: Callable Services for High-Level
Languages.
Detecting Module: HWIAMIN1
Routing Code: 1,2
Descriptor Code: 4

HWI012I BCPII WAS UNABLE TO ESTABLISH ITS RECOVERY ENVIRONMENT IN modname. RC=rc. BCPII
INITIALIZATION IS HALTED.
Explanation: A BCPii initialization module could not establish a recovery environment.
System action: BCPii initialization is stopped.
Operator response: Contact the system programmer.
Application Programmer Response: None.
User response: None.
System programmer response: Try to restart the BCPii address space. Search problem reporting data bases for a fix

70 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HWI013I • HWI014I

for the problem. If no fix exists, contact the IBM Support Center, supplying the name of the module and the return
code as returned on the message.
Detecting Module: HWIAMIN1,HWIAMIN2
Routing Code: 1,2
Descriptor Code: 4

HWI013I BCPII IS TERMINATING DUE TO A SYSTEM ERROR. terminating reason

Explanation: BCPii is terminating itself because of a severe error. See the associated terminating reason later in this
section for a more detailed explanation for this termination.
In the message text:
termination reason
The reason why BCPii is terminating:
A LANGUAGE ENVIRONMENT COULD NOT BE ESTABLISHED
BCPii could not initialize a required LE environment.
A SEVERE SERVER ERROR OCCURRED IN BCPII
BCPii could not recover from a server error and therefore, BCPii is no longer functional.
System action: BCPii initialization is stopped.
Operator response: Report this termination to the system programmer.
Application Programmer Response: None.
User response: None.
System programmer response: Try to restart the BCPii address space. Search problem reporting databases for a fix
for the problem. If no fix exists, contact the IBM Support Center.
Refer to the topic about BCPii in z/OS MVS Programming: Callable Services for High-Level Languages.
Detecting Module: HWIAMIN2,HWIAMCLP
Routing Code: 1,2
Descriptor Code: 4

HWI014I THE SNMP COMMUNITY NAME DEFINED FOR BCPII IN THE SECURITY PRODUCT FOR THE
LOCAL CPC IS NOT CORRECT.
Explanation: BCPii cannot connect to the local CPC because a valid SNMP community name has not been defined
correctly in the security product.
System action: BCPii initialization is stopped.
Operator response: Report this termination to the system programmer.
Application Programmer Response: None.
User response: None.
System programmer response: If you require BCPii to be active on this z/OS image, confirm that an SNMP
community name is defined correctly in the security product for the local processor and that it matches the
community name specified in the support element (SE) for the local processor. This error can also result if the
community name definition on the SE is not specified exactly as instructed (community name naming rules, netmask,
read/write permissions, etc...).
For additional information about the required BCPii community name that must be set up before BCPii is initialized,
see the topic about BCPii in z/OS MVS Programming: Callable Services for High-Level Languages.
Detecting Module: HWIAMIN2
Routing Code: 1,2
Descriptor Code: 4

Chapter 6. HWI messages 71

HWI015I • HWI017I

HWI015I BCPII IS WAITING FOR THE PRIMARY SUBSYSTEM TO BECOME ACTIVE TO ALLOW THE
BCPII COMMUNICATION RECOVERY ENVIRONMENT TO BE ESTABLISHED.
Explanation: BCPii is waiting for the BCPii communication recovery environment to be established to handle
unexpected errors during communication processing using the z/OS Language Environment. While BCPii is waiting
for the primary subsystem to become active, if a severe error occurs while processing a BCPii communications
request and a CEEDUMP is requested, one will not be taken. The CEEDUMP processing of BCPii requires the
primary subsystem to be active to write the dump to SYSOUT.
System action: BCPii initialization continues.
Operator response: Contact the system programmer if the primary subsystem does not become active in a timely
manner.
Application Programmer Response: None.
User response: None.
System programmer response: None.
Detecting Module: HWICMCON,HWIAMCMR
Routing Code: 1,2
Descriptor Code: 4

HWI016I THE BCPII COMMUNICATION RECOVERY ENVIRONMENT IS NOW ESTABLISHED.

Explanation: The BCPii communication recovery environment has been established to handle recovery for failures
requiring CEEDUMPs.
System action: The system continues processing.
Operator response: None.
Application Programmer Response: None.
User response: None.
System programmer response: None.
Detecting Module: HWIAMCMR
Routing Code: 1,2
Descriptor Code: 4

HWI017I THE BCPII COMMUNICATION RECOVERY ENVIRONMENT MAY BE UNAVAILABLE DUE TO

reason
Explanation: The BCPii communication recovery environment cannot be established or it becomes unavailable. This
error can be caused by the primary subsystem being stopped, or becoming inactive, or both. This error can also be
caused by failures occurring during the processing to build the recovery environment.
In the message text, reason is one of the following:
THE PRIMARY SUBSYSTEM NO LONGER BEING ACTIVE
The BCPii communication recovery environment is no longer available until the primary subsystem becomes
active again.
A SEVERE INTERNAL ERROR OCCURRED
An internal error is encountered during the processing to establish the BCPii communication recovery
environment that is required for a CEEDUMP to be taken if a failure occurs in BCPii communication
processing using the z/OS Language Environment.
System action: The system continues processing but the BCPii communication recovery environment is not
established. A symptom record is written to capture additional information to help diagnose the error.
Operator response: Contact the system programmer with the symptom record.
Application Programmer Response: None.

72 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HWI018I • HWI020I

User response: None.

System programmer response: Search problem reporting databases for a fix for the problem. If no fix exists, contact
the IBM Support Center. Consider consulting the symptom record for further diagnostics.
Detecting Module: HWIAMIN2,HWIAMCMR
Routing Code: 1,2
Descriptor Code: 4

HWI018I THE BCPII COMMUNICATION RECOVERY HAS DETECTED AN UNEXPECTED ERROR.

SYSOUT MAY CONTAIN DIAGNOSTICS FOR THIS PROBLEM.
Explanation: The BCPii communication recovery environment has detected an expected error. There might be
messages and a CEEDUMP in the SYSOUT for more detailed problem determination.
System action: The system continues processing.
Operator response: None.
Application Programmer Response: None.
User response: None.
System programmer response: None.
Detecting Module: HWISMSTK, HWIAMCAT
Routing Code: 1,2
Descriptor Code: 4

HWI019I BCPII REQUIRES THE FACILITY GENERAL-RESOURCE CLASS TO BE ACTIVATED IN THE

SECURITY PRODUCT.
Explanation: During BCPii initialization, an attempt was made to set up the security product to handle BCPii
requests. One of the service calls made requires the FACILITY general-resource class to be active.
System action: BCPii initialization is stopped.
Operator response: Report this termination to the system programmer.
Application Programmer Response: None.
User response: None.
System programmer response: BCPii is a system address space which allows authorized applications to
communicate with the Support Element. If your installation requires these services to be available, the FACILITY
general-resource class must be active in the security product. See your security product documentation for details
about how to activate this class.
Also see the topic about Setting up authority to use BCPii in z/OS MVS Programming: Callable Services for High-Level
Languages.
Detecting Module: HWIAMSEC
Routing Code: 1,2
Descriptor Code: 4

HWI020I BCPII IS WAITING FOR SECURITY PRODUCT INITIALIZATION.

Explanation: During BCPii initialization, BCPii detected that the security product has not completed its
initialization. BCPii requires the security product to be active prior to the completion of BCPii initialization, so that
BCPii can make various security product calls.
System action: BCPii will wait a predetermined length of time for the security product to initialize. If the security
product completes its initialization within the predetermined time period, BCPii initialization will continue. However
if the security product fails to initialize during this time period, then BCPii will halt its initialization.

Chapter 6. HWI messages 73

HWI021I • HWI051I

Operator response: None.

Application Programmer Response: None.
User response: None.
System programmer response: BCPii is a system address space that allows authorized applications to communicate
with the Support Element. If your installation requires these services to be available, then the security product needs
to initialize prior to the initialization of the HWIBCPII address space. If BCPii halts its initialization because the
security product is not initializing, you can restart BCPii using the START HWISTART command after the security
product has initialized.
Detecting Module: HWIAMSEC
Routing Code: 1,2
Descriptor Code: 4

HWI021I THE SECURITY PRODUCT FAILED TO INITIALIZE. BCPII INITIALIZATION IS HALTED.

Explanation: BCPii requires the security product to be active prior to the completion of BCPii initialization, so that
BCPii can make various security product calls. BCPii has waited for a predetermined amount of time (see message
HWI020I), but even after this time, the security product has not become active. BCPii initialization is halted.
System action: BCPii will wait a predetermined length of time for the security product to initialize. If the security
product completes its initialization within the predetermined time period, BCPii initialization will continue. However
if the security product fails to initialize during this time period, then BCPii will halt its initialization and gracefully
end.
Operator response: None.
Application Programmer Response: None.
User response: None.
System programmer response: BCPii is a system address space which allows authorized applications to
communicate with the Support Element. If your installation requires these services to be available, then the security
product needs to be initialized prior to the initialization of the HWIBCPII address space. If BCPii halts its
initialization because the security product not initializing, you can restart BCPii using the START HWISTART command
after the security product has initialized.
Detecting Module: HWIAMSEC
Routing Code: 1,2
Descriptor Code: 4

HWI051I BCPII COMPONENT TRACE HAS NOT BEEN STARTED. PARMLIB MEMBER member WAS NOT
FOUND, OR THE PARMLIB TRACEOPTS ARE IN ERROR OR SET OFF. RC=rc, RSN=rsn.
Explanation: BCPii cannot activate its component trace using the parmlib member name.
In the message text:
member
The CTIHWI00 parmlib member name that contains SYSBCPII component trace options.
rc The return code from the CTRACE DEFINE macro.
rsn
The reason code from CTRACE DEFINE macro.
System action: BCPii continues initialization processing, attempting to come up without CTRACE active.
Operator response: None.
System programmer response: Verify that the specified parmlib member exists and contains no syntax errors. For
explanation of the return and reason codes, see the description of the CTRACE macro in z/OS MVS Programming:
Authorized Assembler Services Reference ALE-DYN. Activate component trace by manually using the TRACE system

74 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HWI052I • HWI054I

command if tracing options are required. If the parmlib member is correct, provide this message text to your IBM
Support Center.
Detecting Module: HWIVMINT
Routing Code: 2
Descriptor Code: 12

HWI052I BCPII COMPONENT TRACE IS UNAVAILABLE DUE TO INTERNAL ERROR. BCPII

PROCESSING CONTINUES. RC=rc, RSN=rsn.
Explanation: BCPii component trace initialization failed because of internal errors. BCPii component trace
(SYSBCPII) is not available until the next time the BCPii address space is restarted.
In the message text:
rc The return code from the CTRACE DEFINE macro.
rsn
The reason code from CTRACE DEFINE macro.
System action: BCPii operates without component tracing.
Operator response: Report this message to the system programmer.
Application Programmer Response: None.
User response: None.
System programmer response: Consider restarting the BCPii address space if CTRACE tracing is required. If
problem occurs again after the restart, search problem reporting databases for a fix for the problem. If no fix exists,
contact the IBM Support Center.
Detecting Module: HWIV1INT
Routing Code: 2
Descriptor Code: 4

HWI053I THE BCPII CTRACE OPTIONS PROVIDED ARE NOT VALID.

Explanation: The trace options specified are not valid. These options were supplied in a BCPii CTRACE parmlib
member, or they were entered on the command line. This error can be reported by CTRACE DEFINE if the trace
options in parmlib were in error, or from a TRACE CT operator command. To start a component trace, issue a
TRACE CT command on the system console with valid options for component SYSBCPII.
System action: BCPii operates without component tracing.
Operator response: Issue a TRACE CT command with valid options for SYSBCPII.
Application Programmer Response: None.
User response: None.
System programmer response: Issue a TRACE CT command with valid options for SYSBCPII. For additional
details, see the CTRACE macro options in z/OS MVS Programming: Authorized Assembler Services Reference ALE-DYN.
Detecting Module: HWIPHTSS
Routing Code: 2
Descriptor Code: 4

HWI054I AN INTERNAL ERROR OCCURRED WHEN REQUESTING A SYSTEM DUMP WHILE

STOPPING CTRACE FOR COMPONENT SYSBCPII. RC=rc, RSN=rsn.
Explanation: An internal error occurred in requesting a system dump when a user issues a TRACE CT,OFF
command for component SYSBCPII. Component Trace has been stopped successfully, even though a call to SDUMPX
has failed.

Chapter 6. HWI messages 75

In the message text:
rc The return code from the SDUMPX macro.
rsn
The reason code from the SUMPX macro.
System action: BCPii operates with component tracing stopped.
Operator response: None.
Application Programmer Response: None.
User response: None.
System programmer response: Try to restart the BCPii address space. Search problem reporting databases for a fix
for the problem. If no fix exists, contact the IBM Support Center.
Detecting Module: HWIPHTSS
Routing Code: 2
Descriptor Code: 4

76 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 Chapter 7. HZR messages
This section contains the Runtime Diagnostics messages.

| HZR0106I THE JOBNAME FOR RUNTIME DIAGNOSTICS IS NOT CORRECT. JOB jobname IS IGNORED.
| Explanation: The job name for the Runtime Diagnostics is HZR. The address space is not started.
| In the message text:
| jobname
| The name of the batch job.
| System action: The system ignored the request to start Runtime Diagnostics.
| Operator response: Issue START HZR to start Runtime Diagnostics.
| System programmer response: None.
| Source: Runtime Diagnostics
| Detecting Module: HZRINIT, HZRMIMST
| Routing Code: -
| Descriptor Code: 5

HZR0107I RUNTIME DIAGNOSTICS WAS NOT STARTED UNDER THE MASTER SUBSYSTEM.
Explanation: The operator attempted to start the Runtime Diagnostics address space (HZR) under a subsystem other
than MASTER.
System action: Runtime Diagnostics fails to initialize.
| Operator response: HZR is not specified correctly in IEFSSNxx parmlib member. Contact the system programmer to
| fix the error.
| System programmer response: Ensure HZR is specified correctly in IEFSSNxx, and then start the subsystem by
| either:
| v Starting the Runtime Diagnostics address space (HZR) S HZR,SUB=MSTR
| v Dynamically adding the HZR subsystem, and then starting Runtime Diagnostics address space (HZR) using
| SETSSI,ADD,NAME=HZR and then S HZR
Source: Runtime Diagnostics
Detecting Module: HZRINCRE
Routing Code: -
Descriptor Code: 5

HZR0108I THE STARTED TASK ID FOR RUNTIME DIAGNOSTICS IS NOT CORRECT. startid IS IGNORED.
Explanation: The started task ID for Runtime Diagnostics is HZR. Issue START HZR to restart it. In the message
text:
startid
The name of the started task ID that was ignored.
System action: The system ignored the request to start Runtime Diagnostics.
Operator response: Issue START HZR to start Runtime Diagnostics.
System programmer response: None.
Source: Runtime Diagnostics

© Copyright IBM Corp. 1988, 2012 77

 HZR0109I • HZR0111I

Detecting Module: HZRINCRE

Routing Code: -
Descriptor Code: 5

HZR0109I RUNTIME DIAGNOSTICS WAS NOT STARTED AS A STARTED TASK.

Explanation: The operator did not start the Runtime Diagnostics address space as a started task.
System action: Runtime Diagnostics fails to initialize.
Operator response: Issue START HZR to start Runtime Diagnostics.
System programmer response: None.
Source: Runtime Diagnostics
Detecting Module: HZRINCRE
Routing Code: 1, 2, 10
Descriptor Code: 4

HZR0110I SDUMPX INVOCATION FAILED. RETCODE=rc RSNCODE=rsn

Explanation: Runtime Diagnostics attempted to invoke SDUMPX to gather diagnostic data in response to a DEBUG
option specified on the F HZR,ANALYZE command. The SDUMPX invocation failed and the return/reason codes are
recorded by this message. In the message text:
rc The return code provided by the SDUMPX macro.
rsn
The reason code provided by the SDUMPX macro.
System action: An SVC dump is not generated.
Operator response: None.
System programmer response: See the return code and reason code for SDUMPX in z/OS MVS Programming:
Authorized Assembler Services Reference LLA-SDU. Determine whether the failure was an environmental condition or a
program error.
Source: Runtime Diagnostics
Detecting Module: HZRIMAIN
Routing Code: -
Descriptor Code: 5

| HZR0111I RUNTIME DIAGNOSTICS IS ALREADY ACTIVE.

| Explanation: A request to start HZR was received, but it is already active.
| System action: The system ignores the start request.
| Operator response: None.
| System programmer response: None
| Source: Runtime Diagnostics
| Detecting Module: HZRINIT, HZRMIMST
| Routing Code: -
| Descriptor Code: 5

78 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZR0112I • HZR0200I

| HZR0112I RUNTIME DIAGNOSTICS INITIALIZATION COMPLETE.

| Explanation: Runtime Diagnostics initialization is now complete.
| System action: Runtime Diagnostics is ready for use.
| Operator response: None.
| System programmer response: None
| Source: Runtime Diagnostics
| Detecting Module: HZRINIT, HZRMIMST
| Routing Code: -
| Descriptor Code: 5

| HZR0113I RUNTIME DIAGNOSTICS HAS ENDED.

| Explanation: Runtime Diagnostics has terminated.
| System action: The HZR address space has terminated.
| Operator response: Restart the address space if necessary by issuing the START HZR command .
| System programmer response: None
| Source: Runtime Diagnostics
| Detecting Module: HZRINMTR
| Routing Code: 2, 10
| Descriptor Code: 5

| HZR0114I RUNTIME DIAGNOSTICS STOP REQUEST RECEIVED.

| Explanation: The STOP HZR command was issued. When the STOP HZR command is issued, all ANALYZE
| requests that are queued for processing are purged. When an ANALYZE request is in progress, the request is given
| 20 seconds to complete before the address space is stopped.
| System action: Processing for STOP HZR has begun. Message HZR0113I is subsequently issued when HZR has
| completed termination.

| Note: HZR0113I is not a command response.

| Operator response: None.
| System programmer response: None
| Source: Runtime Diagnostics
| Detecting Module: HZROCPRC, HZRMIMST
| Routing Code: -
| Descriptor Code: 5

HZR0200I RUNTIME DIAGNOSTICS RESULT

SUMMARY: text
REQ: RequestId SYSTEM: SystemName HOME: SystemHome hh:mm:ss - yyyy/mm/dd
INTERVAL: text
EVENTS: text
FOUND: nn - PRIORITIES: HIGH=nn MED=nn LOW=nn
TYPES: I/O=nn USS=nn XCF=nn CF=nn XES=nn
OPERLOG=nn LATCH=nn ASID=nn
RESULTS: text

Chapter 7. HZR messages 79

HZR0200I

ErrorData
RC=nn
RS=nn

----------------------------------------------------------------------
Explanation: This message displays the Runtime Diagnostic results. For complete information about Runtime
Diagnostics, see the topic on Runtime Diagnostics symptoms in z/OS Problem Management. If additional
component-specific messages follow, see the explanation for that message.
In the message fields:
SUMMARY: text
The text field contains one of the following:
v SUCCESS - Runtime Diagnostics completed successfully.
v QUALIFIED SUCCESS - SOME PROCESSING FAILED - Runtime Diagnostics completed with some failures.
v FAILED - ALL PROCESSING FAILED - Runtime Diagnostics did not complete. It failed.
v SUCCESS - NO EVENTS FOUND - Runtime Diagnostics completed successfully.
v QUALIFIED SUCCESS - SOME PROCESSING BYPASSED - Runtime Diagnostics completed successfully.
REQ: RequestId
The unique number that identifies this instance of Runtime Diagnostics.
SYSTEM: SystemName
The name of the system diagnosed by Runtime Diagnostics.
HOME: systemhome
The name of the home system on which Runtime Diagnostics is running.
hh:mm:ss - yyyy/mm/dd
The date and local time of Runtime Diagnostics output. The date is represented as year/month/day, and the
time is represented as hours (00–23), minutes (00–59), and seconds (00–59).
INTERVAL: Interval
The number of minutes back from request time that diagnosis starts.
EVENTS:
A list of the events that were found and diagnosed by Runtime Diagnostics.
FOUND: nn
The number of events that were found and diagnosed by Runtime Diagnostics.
PRIORITIES: HIGH=nn MED=nn LOW=nn
v HIGH= The number of high priority events that were diagnosed by Runtime Diagnostics.
v MED= The number of medium priority events that were diagnosed by Runtime Diagnostics.
v LOW= The number of low priority events that were diagnosed by Runtime Diagnostics.
TYPES:
The type and number of events found and diagnosed by Runtime Diagnostics.
I/O=nn
I/O error events diagnosed.
USS=nn
z/OS UNIX System Services error events diagnosed.
XCF=nn
Cross-system coupling facility (XCF) error events diagnosed.
CF=nn
Coupling facility (CF) error events diagnosed.
XES=nn
Cross-system extended services (XES) error events diagnosed.
OPERLOG=nn
Operations log (OPERLOG) error events diagnosed.

80 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZR0200I

LATCH=nn
Latch error events diagnosed.
ASID= nn
Address space error events diagnosed.
RESULTS: text
The text field contains one the following results of Runtime Diagnostics processing:
PROCESSING BYPASSED: type
Runtime Diagnostics processing bypassed one or more of the following events:
PROCESSING FAILURES: type
Runtime Diagnostics failed processing one or more of the following type of events:
I/O
Failure occurred processing I/O events.
USS
Failure occurred processing z/OS UNIX System Service events.
XCF
Failure occurred processing XCF events.
CF Failure occurred processing CF events.
XES
Failure occurred processing XES events.
OPERLOG
Failure occurred processing OPERLOG events.
LATCHES
Failure occurred processing LATCH events.
ASID
Failure occurred processing ASID events.
PAGERATE
Failure occurred processing PAGING events.
HIGHCPU
Failure occurred processing HIGHCPU events.
STORAGE
Failure occurred processing STORAGE events.
DUMP
Failure occurred processing DUMP events.
SYSTEM
Failure occurred processing SYSTEM events.
CONS
Failure occurred processing CONSOLE events.
LOOP
Failure occurred processing LOOP events.
ENQ
Failure occurred processing ENQ events.
LOCK
Failure occurred processing LOCK events.
ErrorData
Text which describes an error being reported by internal processing.
RC=nn
The return code.

Chapter 7. HZR messages 81

HZR0201I • HZR0203I

RS=nn
The reason code
System action: The system continues processing.
Operator response: If a condition exists, follow the recommended action.
System programmer response: If a condition exists, follow the recommended action.
Reference Documentation: For return codes, see the topic on Runtime Diagnostics messages and return codes in
z/OS Problem Management.
Source: Runtime Diagnostics
Detecting Module: HZRODISP
Routing Code: -
Descriptor Code: 5, 8, 9

HZR0201I RUNTIME DIAGNOSTICS SUCCESS. TIME

NO EVENTS WERE FOUND FOR SYSTEM:
Explanation: Runtime Diagnostics ran and completed successfully. There were no error events found or processed.
System action: The system continues processing.
Operator response: None.
System programmer response: None.
Source: Runtime Diagnostics
Detecting Module: HZRODISP
Routing Code: -
Descriptor Code: 5

HZR0202I RUNTIME DIAGNOSTICS FAILED. DIAG1= DIAG2=

Explanation: Runtime Diagnostics did not complete successfully. An error occurred that prevented it from collecting
and processing events.
System action: The system continues processing.
Operator response: None.
System programmer response: None.
Source: Runtime Diagnostics
Detecting Module: HZRODISP
Routing Code: -
Descriptor Code: 5

HZR0203I THE ANALYZE REQUEST HAS BEEN REJECTED.

THE MAXIMUM NUMBER OF REQUESTS ARE WAITING TO BE PROCESSED.

THE HZR ADDRESS SPACE IS TERMINATING.
IRRELEVANT DEBUG OPTION(S) SPECIFIED.
Explanation: Runtime Diagnostics has rejected a request because:
v The maximum number of outstanding requests are waiting to be processed.
v The HZR address space is terminating.
v One or more irrelevant DEBUG options were specified.
For example: Because HZR only performs loop detection on the home system, if DEBUG(NOLOOP) is specified when
SYSNAME(not_home_system_name), the DEBUG(NOLOOP) request is irrelevant.

82 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

System action: The current request is rejected.
Operator response: If the maximum number of outstanding requests are waiting to be processed, reissue the
request.
If the HZR address space is terminating, restart the HZR address space. Reissue the request.
If an irrelevant DEBUG option was specified, reissue the request with a relevant DEBUG option.
System programmer response: None.
Source: Runtime Diagnostics
Problem determination: For complete information about using the debug options, see the topic about Runtime
Diagnostics debug options in z/OS Problem Management:
Detecting Module: HZRRSPRS, HZROCPRC, HZRMIMST
Routing Code: -
Descriptor Code: 5

Chapter 7. HZR messages 83

84 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)
Chapter 8. HZS messages
This section includes the IBM Health Checker for z/OS component messages.

Check messages are documented in the messages or codes book for each element.

HZS0001I CHECK(checkowner,checkname):
Explanation: An exception message was found by the specified check. The severity and wtotype attributes of the
check indicated to write a low-severity message. A component-specific message follows. Refer to the documentation
for that message for additional information. Additional information might be present in the message buffer for the
check.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
System action: The system continues processing.
Operator response: Contact the system programmer.
System programmer response: Fix the condition that is referenced by the exception message and then rerun the
check to verify that the exception has been fixed.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS0002E CHECK(checkowner,checkname):
Explanation: An exception message was found by the specified check. The severity and wtotype attributes of the
check indicated to write a medium-severity message. A component-specific message follows. Refer to the
documentation for that message for additional information. Additional information might be present in the message
buffer for the check.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
System action: The system continues processing.
Operator response: Contact the system programmer.
System programmer response: Fix the condition that is referenced by the exception message and then rerun the
check to verify that the exception has been fixed.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

© Copyright IBM Corp. 1988, 2012 85

HZS0003E • HZS0005I

HZS0003E CHECK(checkowner,checkname):
Explanation: An exception message was found by the specified check. The severity and wtotype attributes of the
check indicated to write a high-severity message. A component-specific message follows. Refer to the documentation
for that message for additional information. Additional information might be present in the message buffer for the
check.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
System action: The system continues processing.
Operator response: Contact the system programmer.
System programmer response: Fix the condition that is referenced by the exception message and then rerun the
check to verify that the exception has been fixed.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS0004I CHECK(checkowner,checkname):
Explanation: An exception message was found by the specified check. The severity and wtotype attributes of the
check indicated to write a message to the hardcopy log only. A component-specific message follows. Refer to the
documentation for that message for additional information. Additional information might be present in the message
buffer for the check.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
System action: The system continues processing.
Operator response: Contact the system programmer.
System programmer response: Fix the condition that is referenced by the exception message and then rerun the
check to verify that the exception has been fixed.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS0005I SEE THE MESSAGE BUFFER FOR ADDITIONAL MESSAGES

Explanation: The number of exception messages for this check exceeds the limit that a check routine can be issued
to the operator console. The suppressed exception messages will be written only to the message buffer of the check.
This messages is displayed as part of the message text for HZS0001I, HZS002E, HZS003E, or HZS004I, depending
upon the severity of the check.
System action: The system continues processing.
Operator response: Contact the system programmer.

86 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0010I • HZS0012E

System programmer response: Refer to the message buffer for this check to see the additional messages.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS0010I THE HZSPDATA DATA SET CONTAINS NO RECORDS

Explanation: The data set defined by the HZSPDATA DD statement of the IBM Health Checker for z/OS proc is
empty. If this is the first time IBM Health Checker for z/OS has run on this system, this is normal. View the job log
for other messages associated If this is not the first time, view the job log for other messages associated with this
condition. Some checks rely on data that is saved from a prior IPL, to be useful. These checks cannot be performed.
System action: IBM Health Checker for z/OS address space initialization continues. Checks that do not rely on
information from a prior IPL are not affected.
Operator response: Contact the system programmer.
System programmer response: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKPD
Routing Code: 2
Descriptor Code: -

HZS0011E READING THE HZSPDATA DATA SET

Explanation: The system has begun to read the HZSPDATA data set.
System action: Upon completion of the read, the system DOMs the message. Conversely, if the read does not
complete (perhaps due to problems with the data set or its volume), the message will remain visible.
Operator response: If this message persists, notify the system programmer.
System programmer response: Check for configuration problems that would cause the system not to be able to
access the HZSPDATA data set successfully. If you have a backup copy of the data set you might want to restart IBM
Health Checker for z/OS specifying that alternate data set.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKPD
Routing Code: 1,2,10
Descriptor Code: 7,11

HZS0012E HZSPDATA DATA SET IS FULL. DATA SET NEEDS ROOM FOR n 4096-BYTE RECORDS
Explanation: The system attempted to write the persistent data but there was not enough room in the data set. The
message text provides information about the size of the data set needed to hold all the data.
In the message text:
n the number of records
System action: The system writes message HZS0013A or HZS0019A
Operator response: Allocate and initialize a new data set using the HZSALLCP job and provide that data set in
response to message HZS0013A or HZS0019A.
System programmer response: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKPD

Chapter 8. HZS messages 87

HZS0013A • HZS0015E

Routing Code: 1,2,10

Descriptor Code: 7,11

HZS0013A SPECIFY THE NAME OF AN EMPTY HZSPDATA DATA SET

Explanation: The system needs an HZSPDATA data set in order to write its persistent data.
System action: The system delays writing the persistent data until a response is received.
Operator response: Provide the name of an empty data set initialized by the HZSALLCP job. Look for preceding
HZS messages such as HZS0012E, HZS0014E, and HZS0015E which could provide additional information.
System programmer response: None.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKPD
Routing Code: 1,2,10
Descriptor Code: 7,11

HZS0014E THE HZSPDATA DATA SET CONTAINS DATA THAT IS NOT VALID. DIAG=diag
Explanation: The data read from the HZSPDATA data set is not valid. Either the data set was corrupted or you
specified the wrong data set. This data set was specified by the HZSPDATA DD statement or in response to message
HZS0013A or HZS0019A. Some checks rely on data that is saved from a prior IPL, to be useful. These checks cannot
be performed.
In the message text:
diag
Diagnostic information
System action: IBM Health Checker for z/OS processing continues. Checks that do not rely on information from a
prior IPL are not affected.
Operator response: Contact the system programmer.
System programmer response: Determine how the data set was corrupted. If you want IBM Health Checker for
z/OS to continue with a new data set create a new empty data set using the HZSALLCP job and specify that data set
in response to HZS0013A or HZS0019A. If you need IBM Health Checker for z/OS to use a different already-existing
data set that has valid data, stop IBM Health Checker for z/OS and then restart it, providing that other data set.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKPD
Routing Code: 1,2,10
Descriptor Code: 7,11

HZS0015E PROBLEM WITH HZSPDATA DATA SET:

idataprob
Explanation: The HZSPDATA data set is not valid. This data set was specified by the HZSPDATA DD statement or
in response to message HZS0013A or HZS0019A. Some checks rely on data that is saved from a prior IPL, to be
useful. These checks cannot be performed.
In the message text:
idataprob
One of the following:
DD NOT DEFINED
The HZSPDATA DD was not provided.
COULD NOT ALLOCATE
The data set could not be allocated.

88 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0016I

COULD NOT OPEN

The data set could not be opened.
DATA DOES NOT BELONG TO THIS SYSTEM
The data present was not created by a system of the same name as this system.
COULD NOT READ
An error was encountered reading the data set.
COULD NOT WRITE
An error was encountered writing to the data set.
DATA SET IS NOT EMPTY
The data set is not empty, as required.
DATA SET IS PARTITIONED
The data set is partitioned. That is not allowed.
UNEXPECTED ERROR
An unexpected error occurred. The data set might have been corrupted. This can occur in the following
cases:
v This is the first use of the data set and the data set was not initialized using JCL derived from the
HZSALLCP sample.
v A prior instance of IBM Health Checker for z/OS, whether during this IPL or another, ended with the last
write to the data set having run out of space.
v The data was written on a release later than z/OS 1.9 and is being read on z/OS 1.9 or an earlier z/OS
release
System action: IBM Health Checker for z/OS address space initialization continues. Checks that do not rely on
information from a prior IPL are not affected.
Operator response: Contact the system programmer.
System programmer response: Determine the problem with the data set. If you want IBM Health Checker for z/OS
to continue with a new data set create a new empty data set using the HZSALLCP job and specify that data set in
response to HZS0013A or HZS0019A. If you need IBM Health Checker for z/OS to use a different already-existing
data set that has valid data, stop IBM Health Checker for z/OS and then restart it, providing that other data set.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKPD
Routing Code: 1,2,10
Descriptor Code: 7,11

HZS0016I SYSHZS CTRACE DEFINITION FAILED. RC=rc, RSN=rsn

Explanation: The system cannot define the SYSHZS component trace.
In the message text:
rc The return code provided by the CTRACE DEFINE macro
rsn
The reason code provided by the CTRACE DEFINE macro
System action: The system runs without the SYSHZS component trace.
Operator response: Contact the system programmer.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Problem determination: For information about the CTRACE return and reason codes see z/OS MVS Programming:
Authorized Assembler Services Reference ALE-DYN.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSCTIT

Chapter 8. HZS messages 89

HZS0017I • HZS0019A

Routing Code: 2
Descriptor Code: 4,7

HZS0017I COMPONENT TRACE PARMLIB OPTION optname IS NOT VALID

Explanation: The system encountered an incorrect option in the CTIHZSxx parmlib member that had been specified
on a prior TRACE CT command.
In the message text:
optname
The specified option that is incorrect
System action: The system does not start the requested component trace. Processing continues with the next option
specified.
Operator response: Contact the system programmer.
System programmer response: Examine the options near the indicated character string for a misspelling or other
error. Correct the error in the parmlib member before reissuing the TRACE CT command.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSCTSSM
Routing Code: 2
Descriptor Code: 4,7

HZS0018I READING COMPLETE FOR THE HZSPDATA DATA SET

Explanation: The system has completed reading the HZSPDATA data set.
System action: The system continues after DOMing message HZS0011E.
Operator response: None
System programmer response: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKPD
Routing Code: 2
Descriptor Code: -

HZS0019A SPECIFY THE NAME OF AN EMPTY HZSPDATA DATA SET OR C TO CANCEL

Explanation: The system needs an HZSPDATA data set in order to write the persistent data. If you do not want the
most recent persistent data to be retained, reply 'C'. If the previous attempt to write the data ended in an error
condition, as indicated by a message such as HZS0014E or HZS0015E, then canceling will result in not having any of
the previously collected persistent data when you next start IBM Health Checker for z/OS.
System action: The system delays writing the persistent data until a response is received.
Operator response: Provide the name of an empty data set initialized by the HZSALLCP job. Look for preceding
HZS messages such as HZS0012E, HZS0014E, and HZS0015E that could provide additional information.
System programmer response: None.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKPD
Routing Code: 1,2,10
Descriptor Code: 7,11

90 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0020E • HZS0102I

HZS0020E WAITING FOR CHECKS TO COMPLETE

Explanation: Before proceeding with the ending of IBM Health Checker for z/OS, the system is waiting for check
routines that are currently running to complete.
System action: When the last currently running check completes, the system DOMs the message and continues with
the ending of IBM Health Checker for z/OS
Operator response: If you wish to speed IBM Health Checker for z/OS termination by deleting the checks that the
system is waiting for, you can force deletion of the checks by using the FORCE option on the F hzsproc,DELETE
command. Use FORCE only as a last resort, because it can be disruptive to your system, IBM Health Checker for
z/OS, and your checks. See 'How can I delete checks while IBM Health Checker for z/OS is terminating?' in the IBM
Health Checker for z/OS: User's Guide.
System programmer response: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKSCM
Routing Code: 1,2,10
Descriptor Code: 7,11

HZS0021E PERSISTENT DATA OVERLAY HAS BEEN DETECTED. NO MORE WRITING OF PERSISTENT
DATA WILL BE DONE
Explanation: An overlay of the data to be written to the HZSPDATA data set has been detected. In order to avoid
corrupting the data on the data set, no further writes of persistent data will be done.
System action: The system no longer attempts to write the persistent data.
Operator response: Contact the system programmer.
System programmer response: Consider stopping and restarting the IBM Health Checker for z/OS in order to have
the system use the valid persistent data that is in the HZSPDATA data set.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKPD
Routing Code: 1,2,10
Descriptor Code: 7,11

HZS0101I IBM HEALTH CHECKER FOR Z/OS IS ALREADY ACTIVE

Explanation: A request to start IBM Health Checker for z/OS was received. However, it is already active.
System action: The system ignores the start request.
Operator response: None
System programmer response: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINIT
Routing Code: 2
Descriptor Code: -

HZS0102I IBM HEALTH CHECKER FOR Z/OS MUST BE STARTED AS A STARTED TASK. JOB jobname
TERMINATES
Explanation: The named batch job attempted to start IBM Health Checker for z/OS. It must be started as a
STARTED task.
In the message text:

Chapter 8. HZS messages 91

HZS0103I • HZS0106I

jobname
The name of the batch job
System action: The system ends the job.
Operator response: Enter a START operator command to start IBM Health Checker for z/OS.
System programmer response: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINIT
Routing Code: 1,2,10
Descriptor Code: -

HZS0103I procname INITIALIZATION COMPLETE

Explanation: Initialization is now complete for IBM Health Checker for z/OS
In the message text:
procname
The name of the procedure used to start IBM Health Checker for z/OS.
System action: System processing continues.
Operator response: None
System programmer response: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINIT
Routing Code: 2
Descriptor Code: -

HZS0104I procname TERMINATION IS COMPLETE

Explanation: IBM Health Checker for z/OS processing is ending in response to a system command or as a result of
a system problem.
In the message text:
procname
The name of the procedure used to start IBM Health Checker for z/OS
System action: IBM Health Checker for z/OS ends.
Operator response: Contact your system programmer if there are error messages accompanying this message.
System programmer response: No action is required if this is a normal ending of IBM Health Checker for z/OS. If
this is an error situation, see the messages associated with the error.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINIT
Routing Code: 2
Descriptor Code: -

HZS0106I ERROR IN PARMLIB MEMBER memname ON LINE line-number, POSITION position-number:

THE statement STATEMENT IS NOT VALID WITHIN A PARMLIB MEMBER.
INPUT LINE:
input-line
Explanation: The system encountered an incorrect statement within a parmlib member.
In the message text:

92 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0107I • HZS0108I

memname
The name of the parmlib member containing the error
line-number
The number of the line containing the error
position-number
The position of the error in the line. The position number is the number of columns from the left.
statement
The statement type
input-line
The text of the line containing the PARMLIB statement
System action: The system ignores the erroneous statement. The system continues processing the rest of the parmlib
member
Operator response: None
System programmer response: Correct the error in the parmlib member before using it again.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSIPMU1
Routing Code: -
Descriptor Code: 5

HZS0107I THE LOG STREAM NAME logstream DOES NOT BEGIN WITH HZS
Explanation: The name of the log stream provided by the LOGSTREAM parameter of the MODIFY hzsproc
command does not begin, as required, with the letters 'HZS'.
In the message text:
logstream
The log stream name
System action: The system ignores the erroneous command.
Operator response: None
System programmer response: Provide a log stream name that begins with 'HZS'.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSIPMU1
Routing Code: -
Descriptor Code: 5

HZS0108I ERROR IN PARMLIB MEMBER memname:

THE LOG STREAM NAME logstream DOES NOT BEGIN WITH HZS
Explanation: The name of the log stream provided by the LOGSTREAM parameter of an HZSPRMxx parmlib
statement does not begin, as required, with the letters 'HZS'.
In the message text:
memname
The name of the parmlib member containing the error
logstream
The log stream name
System action: The system ignores the erroneous statement. The system continues processing the rest of the parmlib
member
Operator response: None

Chapter 8. HZS messages 93

HZS0109E • HZS0111I

System programmer response: Provide a log stream name that begins with 'HZS'.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSIPMU1
Routing Code: -
Descriptor Code: 5

HZS0109E IBM HEALTH CHECKER FOR Z/OS

ADDRESS SPACE USER IDENTITY DOES NOT HAVE ACCESS TO
UNIX SYSTEM SERVICES
Explanation: The user security profile is either missing or is incomplete, or the OMVS segment is not defined for
this user.
System action: The system continues. Checks that require UNIX System Services resources will not function
properly.
Operator response: None
System programmer response: Fix the security profile or define the OMVS segment.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINIT
Routing Code: 1,2,10
Descriptor Code: 7,11

HZS0110I THE CTRACE STATEMENT IS NOT VALID.

Explanation: The system encountered a CTRACE statement within the MODIFY hzsproc command.
System action: The system ignores the erroneous statement.
Operator response: None
System programmer response: Avoid using the CTRACE statement within the MODIFY hzsproc command. The
CTRACE statement is valid only within the hzsproc procedure.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSIPMU1
Routing Code: -
Descriptor Code: 5

HZS0111I ERROR IN PARMLIB MEMBER memname:

THE CTRACE STATEMENT IS NOT VALID
Explanation: The system encountered a CTRACE statement within a HZSPRMxx parmlib member.
In the message text:
memname
The name of the parmlib member containing the error
System action: The system ignores the erroneous statement. The system processing the rest of the parmlib member.
Operator response: None
System programmer response: Avoid using the CTRACE statement within the HZSPRMxx parmlib member. The
CTRACE statement is valid only within the hzsproc procedure.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSIPMU1
Routing Code: -

94 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0112E • HZS0120I

Descriptor Code: 5

HZS0112E COULD NOT OBTAIN RESTART AREA STORAGE

Explanation: There was not enough free virtual storage in the High Virtual Shared Area to satisfy the request.
System action: IBM Health Checker for z/OS continues. Remote checks will not automatically be restarted upon
restart of IBM Health Checker for z/OS.
Operator response: Issue the DISPLAY VS,HVSHARE command to get information on the size of the High Virtual
Shared Area and how much of it is allocated. Notify the system programmer.
System programmer response: Examine the information from the DISPLAY VS.HVSHARE'command.'If more than
80% of the High Virtual Shared Area is allocated, examine all programs that use High Virtual Shared Storage for
extraordinary storage requirements. Use the data returned by the Display VS,HVSHARE command and the
job/program usage of the High Virtual Shared Area as a guidance for setting the HVSHARE area size for the next
IPL.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINIT
Routing Code: 1,2,10
Descriptor Code: 7,11

HZS0113E COULD NOT CONNECT TO RESTART AREA STORAGE

Explanation: The attempt to connect to previously-obtained IARV64 REQUEST=GETSHARED storage was not
successful.
System action: IBM Health Checker for z/OS continues. Remote checks will not automatically be restarted upon
restart of IBM Health Checker for z/OS.
Operator response: Notify the system programmer.
System programmer response: Report the problem to IBM.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINIT
Routing Code: 1,2,10
Descriptor Code: 7,11

HZS0120I IBM HEALTH CHECKER FOR Z/OS IS ENDING DUE TO EXCESSIVE ERRORS
Explanation: IBM Health Checker for z/OS ends.
System action: The system runs without IBM Health Checker for z/OS.
Operator response: Contact the system programmer.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINIT
Routing Code: 1,2,10
Descriptor Code: -

Chapter 8. HZS messages 95

HZS0200I

HZS0200I hh.mm.ss CHECK SUMMARY

[THERE ARE NO CHECKS THAT MEET THE SPECIFIED CRITERIA]
CHECK OWNERCHECK NAMESTATESTATUS
checkownercheckname s1s2s3s4status
checkownerchecknames1 d gSYS=sysname
Explanation: Either a MODIFY hzsproc,DISPLAY command or a DISPLAY statement in parmlib member
HZSPRMxx was processed to request summary information about checks.
In the message text:
hh.mm.ss
The time in hours (00-23), minutes (00-59), and seconds (00-59)
checkowner
The owner of the check
checkname
The name of the check
s1 One of the following:
A ACTIVE: The specified check is in the ACTIVE state.
I INACTIVE: The specified check is in the INACTIVE state.

n/a: The specified check was deleted.
s2 One of the following:
E ENABLED: There are no conditions that would prevent the check from running if it is active.
D DISABLED: At least one condition exists that prevents the check from running on this system.

The specified check was deleted.
s3 One of the following:
G GLOBAL: The specified check is global, and therefore may be active on only one system in the sysplex.

The specified check is not global, and therefore may be active on multiple systems in the sysplex
simultaneously.
s4 One of the following:
+ The check issued execution warning message(s) the last time it ran.

The check did not issue any execution warning messages the last time it ran.
status
One of the following:
NEW COPY
Another check with the same owner and name is being deleted. The status of this check will change once
the old instance of the check has finished the delete process.
INACTIVE
The check currently inactive.
STARTING
The check is scheduled to start but has not yet started.
ENV N/A
The check is not applicable in the current system environment.
RUNNING
The specified check is currently running.
SUCCESSFUL
The check ran at least one time. No exceptions were found the last time that the check ran.
EXCEPTION-NONE
The check found SEVERITY(NONE) exception(s) the last time that it ran.

96 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0200I

EXCEPTION-LOW
The check found SEVERITY(LOW) exception(s) the last time that it ran.
EXCEPTION-MED
The check found SEVERITY(MEDIUM) exception(s) the last time that it ran.
EXCEPTION-HIGH
The check found SEVERITY(HIGH) exception(s) the last time that it ran.
PARAMETER ERROR
The parameters contain an incorrect value.
ABEND
The check ABENDed the last time that it ran.
UNEXP ERROR
The check encountered an unexpected error.
INIT ERROR
The check encountered an error during check initialization.
DELETE ERROR
The check encountered an error during check delete.
SCHEDULED
The specified check is currently scheduled to run.
USS NOT AVAIL
The specified check requires Unix System Services but those services are not currently available.
RAN ELSEWHERE
The last time an attempt was made to run the specified check, it was active on another system. The check is
no longer active on any system in the sysplex, and will become active on the first system that tries to run
the check
DELETE PENDING
The check is being deleted.
DELETED
The check was deleted.
UNSUCCESSFUL
The remote check did not process successfully. The pause token that it had provided was not valid so the
check routine could not be given control.
| MISSING DOM
| A check added with DOM(CHECK) did not DOM exception WTOs from a previous check iteration when the
| current iteration ended without check exception.
STATE column 2 d
DISABLED: The specified check was disabled becase it was active on another system in the sysplex
STATE column 3 g
GLOBAL: The specified check is global, and therefore may only be active on one system in the sysplex
sysname
The name of the system on which this check is active. If 'SYS=*NONE' is displayed, the check is no longer active
on any system in the sysplex, and will become active on the first system that tries to run the check. If
'SYS=*UNKNOWN' is displayed, the system on which this check is active can not be determined at this time.
System action: The system continues processing.
Operator response: None
System programmer response: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKDIS
Routing Code: -

Chapter 8. HZS messages 97

 HZS0201I

Descriptor Code: -

HZS0201I hh.mm.ss CHECK DETAIL

[THERE ARE NO CHECKS THAT MEET THE SPECIFIED CRITERIA]
CHECK(checkowner,checkname)
{ STATE: state [GLOBAL] STATUS: text
STATE: state GLOBAL STATUS: SYS=sysname
STATE: state date
}
[ DIAG: diag1_diag2]
EXITRTN: exitrtn
{ LAST RAN: lastdateNEXT SCHEDULED: nextdate
LAST RAN: lastdateNEXT SCHEDULED: nextsched
LAST RAN: (N/A) NEXT SCHEDULED: nextdate
LAST RAN: (N/A) NEXT SCHEDULED: nextsched
}
{ INTERVAL: ONETIME
INTERVAL: hhh:mm }
{ EXCEPTION INTERVAL: {SYSTEM ! HALF}
EXCEPTION INTERVAL: hhh:mm
}
| SYNCVAL: {SYSTEM|hh:mm|*:mm}
SEVERITY: severity
| DYNAMIC SEVERITY ALLOWED: {YES | NO}
WTOTYPE: wtotype
| DOM: {SYSTEM | CHECK}
SYSTEM DESCCODE: sysdesccode
ADDITIONAL DESCCODES: adddesccodes
ROUTCODES: routcodes
{ DELETED BY: STMT(polstmt)
DELETED BY: HZSCHECK(jobname)
DELETED BY: MODIFY COMMAND
DELETED BY: SYSTEM
DELETED BY: PARMLIB(parmlib)
}
{ MODIFIED BY: modby
MODIFIED BY: SYSTEM
MODIFIED BY: STMT(polstmt)
MODIFIED BY: HZSCHECK(jobname)
MODIFIED BY: PARMLIB(parmlib)
}
[ THERE ARE NO PARAMETERS FOR THIS CHECK]
parmtype parms
reasonfor reason
DEFAULT DATE: defaultdate[USER DATE: userdate ]
[ ORIGIN: origin
∨ ORIGIN: HZSPRMhzsprmxx ]
[ LOCALE: locale ]
[ REXXTSO: rexxtso ]
[ REXXOUT DSN: dsn ]
[ REXXIN DSN: dsn ]
[ REXX TIME LIMIT: timelimit ]
DEBUG MODE: debug VERBOSE MODE: verbose
REQUIRES USS RESOURCES
| [ POLICY STATEMENT polstmt WAS NOT APPLIED{ {DATE | SYNCVAL} CONFLICT]
[ UPDATES ARE PENDING]
CATEGORIES: category category category
[ INTERNAL DIAGNOSTICS - CHECK TOKEN: token]
[ ROUTINE: checkmod-check_addr MSGTBL: msgtable-msgtable_addr FUNC: func]
[ ASID: asid FUNC: func]

98 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0201I

[ LAST CPU TIME: lastcpu MAX CPU TIME: maxcpu]

[ REXX REQTOKEN: reqtoken_]
Explanation: The MODIFY,hzsproc,DISPLAY command was entered or a DISPLAY HZSPRMxx parmlib statement
was processed, requesting to display detailed information about check(s) that are (or were) registered with IBM
Health Checker for z/OS.. For complete information about parameter meanings, see Syntax and parameters for
HZSPRMxx and MODIFY hzsproc in IBM Health Checker for z/OS: User's Guide,
In the message text:
hh.mm.ss
The time in hours (00-23), minutes (00-59), and seconds (00-59)
checkowner
The owner of the check that matches the display criteria
checkname
The name of the check that matches the display criteria
state
One of the following:
ACTIVE(ENABLED)
ACTIVE: The check is in the ACTIVE state. (ENABLED): The check was started at least once, and there are
no conditions that would prevent the check from running.
ACTIVE(DISABLED)
ACTIVE: The check is in the ACTIVE state. (DISABLED): At least one condition exists that prevents the
check from running on this system.
INACTIVE(ENABLED)
INACTIVE: The check is in the INACTIVE state. (ENABLED): The check was started at least once, and there
are no conditions that would prevent the check from running.
INACTIVE(DISABLED)
INACTIVE: The check is in the INACTIVE state. (DISABLED): At least one condition exists that prevents the
check from running on this system.
DELETE PENDING
The specified check was deleted. The delete process is in progress.
DELETED
The specified check was deleted.
GLOBAL
The specified check is global, and therefore may be active on only one system in the sysplex.
text
is one of the following:
NEW COPY
The specified check is a new instance of a check that is being deleted. The STATUS of this check will change
once the old instance of the check has finished the delete process.
INACTIVE
The specified check is currently is INACTIVE.
STARTING
The specified check is starting check execution for the first iteration of the check.
ENV N/A
The specified check is not applicable in the current system environment.
RUNNING
The specified check is currently executing.
SUCCESSFUL
The specified check ran at least one time. No exception were found during the last iteration of the check.

Chapter 8. HZS messages 99

 HZS0201I

EXCEPTION-NONE
The specified SEVERITY(NONE) check ran at least one time. SEVERITY(NONE) exception(s) were found
during the last iteration of the check.
EXCEPTION-LOW
The specified check ran at least one time. SEVERITY(LOW) exception(s) were found during the last iteration
of the check.
EXCEPTION-MED
The specified check ran at least one time. SEVERITY(MEDIUM) exception(s) were found during the last
iteration of the check.
EXCEPTION-HIGH
The specified check ran at least one time. SEVERITY(HIGH) exception(s) were found during the last
iteration of the check.
PARAMETER ERROR
The specified check was disabled because the user parameters contain an invalid value. The check will not
be run again until the user parameters have been updated.
ABEND
The specified check ended abnormally during the last iteration of the check.
UNEXP ERROR
The specified check reported an unexpected error.
INIT ERROR
The specified check was stopped because an error was reported by the check during check initialization.
DELETE ERROR
The specified check was stopped because an error was reported by the check during check delete.
SCHEDULED
The specified check is currently scheduled to run.
USS NOT AVAIL
The specified check requires Unix System Services but those services are not currently available.
RAN ELSEWHERE
The last time an attempt was made to run the specified check, it was active on another system. The check is
no longer active on any system in the sysplex, and will become active on the first system that tries to run
the check
REXX NOT AVAIL
REXX TOO BUSY
UNSUCCESSFUL
The remote check did not process successfully. The pause token that it had provided was not valid so the
check routine could not be given control.
| MISSING DOM
| A check added with DOM(CHECK) did not DOM exception WTOs from a previous check iteration when the
| current iteration ended without check exception.
sysname
The name of the system on which this check is active. If 'SYS=*UNKNOWN' is specified, the system on which
this check is active can not be determined at this time.
date
The date and time the check was deleted. Format: mm/dd/yyyy hh:mm
diag1
The diagnostic data
diag2
The last 4 characters of the check diagnostic data
exitrtn
The name of the HZSADDCHECK dynamic exit routine that was used to add the check

100 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0201I

lastdate
The date and time the check last ran. Format: mm/dd/yyyy hh:mm
nextdate
The date and time the check is next scheduled to run. Format: mm/dd/yyyy hh:mm
nextsched
One of the following:
(INACTIVE)
The check is currently inactive.
(DISABLED)
The check is currently disabled. Note: checks that are global and are active on another system in the sysplex
may still have a next scheduled time on this system. When the next scheduled time is reached, if the check
is not active on another system in the sysplex, the check will run on this system.
(NOT SCHEDULED)
The check is not scheduled to run again.
LAST RAN: (N/A)
The check was not run.
(N/A)
The check was not run.
hhh
The hours part of the time from one check run to the next.
mm The minutes part of the time from one check run to the next.
SYSTEM
Apply system rules - use the interval value.
HALF
Apply system rules - If the interval is not ONETIME, use half the interval value.
| SYNCVAL: {SYSTEM|hh:mm|*:mm}
| SYSTEM
| Apply system rules - the check gets scheduled, as soon as possible after is has been added and the system
| uses the last check run end time to calculate any subsequent check run start times.
| hh:mm
| The time of day in hours and minutes that the check should be scheduled to run for the first time as well as
| for subsequent iterations, synchronized with the current INTERVAL (or, EXCEPTION INTERVAL) value.
| *:mm
| The minute of the current hour (or the next hour if the minute has already passed for the current hour) that
| the check should to be scheduled to run at for the first time, as well as for subsequent iterations,
| synchronized with the current INTERVAL (or, EXCEPTION INTERVAL) value.
severity
One of the following:
NONE
The specified check is currently defined as "SEVERITY(NONE)".
LOW
The specified check is currently defined as "SEVERITY(LOW)".
MEDIUM
The specified check is currently defined as "SEVERITY(MEDIUM)".
HIGH
The specified check is currently defined as "SEVERITY(HIGH)".
| DYNAMIC SEVERITY ALLOWED: {YES | NO}
| Displays whether or not the check is allowed to specify a dynamic severity. The dynamic severity can be

Chapter 8. HZS messages 101

 HZS0201I

| different than and take precedence over the current severity defined for the check. See the ALLOWDYNSEV
| parameter in Syntax and parameters for HZSPRMxx and MODIFY hzsproc in IBM Health Checker for z/OS: User's
| Guide for details.
wtotype
One of the following:
NONE
The updated WTO value is defined not to be issued as WTOs.
HARDCOPY
The updated WTO value is defined to be issued to the system hardcopy log only.
INFORMATIONAL
The update WTO value is defined to be issued as informational messages.
EVENTUAL ACTION
The update WTO value is defined to be issued as eventual action messages.
CRITICAL EVENTUAL ACTION
The update WTO value is defined to be issued as a critical eventual action messages.
| DOM: {SYSTEM | CHECK}
| Displays whether the check or the system delete the write to operator (WTO) messages from previous check
| iterations using delete operator message (DOM) requests. See the DOM parameter in Syntax and parameters for
| HZSPRMxx and MODIFY hzsproc in IBM Health Checker for z/OS: User's Guide for details.
sysdesccode
The system descriptor code used to write any exception messages issued by this check
adddesccodes
The list of additional descriptor codes used to write any exception messages issued by this check
routcodes
The list of routing codes used to write any exception messages issued by this check
polstmt
The name of the policy statement that deleted the check
jobname
The name of the job that issued the HZSCHECK macro request to delete this check
parmlib
The name of the parmlib member that contained the request to delete this check
modby
One of the following:
N/A
The check was not modified.
MODIFY COMMAND
The last time the check was modified, it was done through the MODIFY command.
parmtype
One of the following:
DEFAULT PARAMETERS:
The parameters defined by the PARMS keyword of the HZSADDCK macro that added the check
USER SUPPLIED PARAMETERS:
The parameters defined by an UPDATE or POLICY statement UPDATE request
parms
The parameters
reasonfor
One of the following:
REASON FOR CHECK:
The reason specified by the REASON keyword of the HZSADDCK macro that added the check

102 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0201I

REASON FOR UPDATE:

The reason defined for the most recent UPDATE or POLICY statement UPDATE request that modified the
check and that supplied a reason
reason
The reason
defaultdate
The date specified by the DATE keyword of the HZSADDCK macro that added the checkor the DATE parameter
of the ADD or ADDREPLACE statement of the HZSPRMxx parmlib member that added the check. Its format is
yyyymmdd.
userdate
The date defined for the most recent UPDATE or POLICY statement UPDATE request that modified the check
and that supplied a date. Its format is yyyymmdd.
origin
One of the following:
HZSADDCK
The check was added by HZSADDCK.
MODIFY
The check was added by the MODIFY command.
hzsprmxx
The parmlib member in which the check definition was found.
locale
One of the following options:
HZSPROC
The specified check runs in the IBM Health Checker for z/OS address space started by the hzsproc proc.
REMOTE
The specified check is remote to the IBM Health Checker for z/OS address space.
rexxtso
One of the following options:
NO The specified check runs in a MVS host environment.
YES
The specified check runs in a TSO host environment.
dsn
The name of the data set to which REXX output must be delivered when the check is in DEBUG mode.
timelimit
The number of seconds to which the execution of an iteration of the exec is to be limited. A value of 0 indicates
that there is no limit.
debug
One of the following options:
OFF
The specified check is not running in DEBUG mode.
ON The specified check is running in DEBUG mode. Additional messages might be written to the message
buffer and may help to diagnose problems with the check.
verbose
One of the following:
NO The specified check is not running in VERBOSE mode.
YES
The specified check is running in VERBOSE mode. Additional messages might be written to the message
buffer.

Chapter 8. HZS messages 103

HZS0201I

category
The category to which the check belongs
token
An internal token representing the check
checkmod
For a non-remote check, the name of the load module that is the check.
check_addr
For a non-remote check, the address of the load module within IBM Health Checker for z/OS.
msgtable
The name of the message table used by this check
msgtable_addr
The address of the message table within IBM Health Checker for z/OS
func
The current function for the check routine func is one of the following:
N/A
Not within the check routine
INIT
The INIT function
CHECK
The CHECK function
CLEANUP
The CLEANUP function
DELETE
The DELETE function
INITRUN
The INITRUN function
RUN
The RUN function
DEACTIVATE
The DEACTIVATE function
asid
For a remote not-REXX check, the ASID in which the check runs
lastcpu
The number of seconds of CPU time used the last'time the check function ran, in format'ss.ttt
maxcpu
The maximum number of seconds of CPU time used 'by the check routine, in format ss.ttt
reqtoken
The REXX ReqToken of the scheduled or running check.
System action: The system continues processing.
Operator response: None
System programmer response: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKDIS
Routing Code: -
Descriptor Code: -

104 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0202I

HZS0202I hh.mm.ss POLICY DETAIL

[THERE ARE NO POLICY STATEMENTS THAT MEET THE SPECIFIED CRITERIA]
POLICY(polname) STATEMENT: polstmt
{ ORIGIN: MODIFY COMMAND DATE: date
ORIGIN: parmlib DATE: date
}
pol_op CHECK(checkowner,checkname)
CATEGORIES cattype category category category
EXITRTN: exitrtn
REASON: reason
text
{ INTERVAL: ONETIME
INTERVAL: hhh:mm
}
{ EXCEPTION INTERVAL: {SYSTEM ! HALF}
EXCEPTION INTERVAL: hhh:mm
}
| SYNCVAL: {SYSTEM|hh:mm|*:mm}
SEVERITY: severity
WTOTYPE: wtotype
DESCCODE: desccodes
ROUTCODE: routcodes
PARAMETERS: parms
DEBUG MODE: debug
VERBOSE MODE: verbose
catoper CATEGORIES: category category category
| [ POLICY STATEMENT NOT APPLIED TO ONE OR MORE CHECKS DUE TO {OLD DATE |
| SYNCVAL}]
Explanation: The MODIFY,hzsproc,DISPLAY command was entered or a DISPLAY HZSPRMxx parmlib statement
was processed, requesting to display information policy statements in effect IBM Health Checker for z/OS. For
complete information about parameter meanings, see Syntax and parameters for HZSPRMxx and MODIFY hzsproc in
IBM Health Checker for z/OS: User's Guide,
In the message text:
hh.mm.ss
The time in hours (00-23), minutes (00-59), and seconds (00-59) for the MODIFY DISPLAY function
polname
The name of the policy
polstmt
The name of this policy statement
ORIGIN: MODIFY COMMAND
The policy was defined by the modify command.
date
The update policy date (yyyymmdd)
parmlib
The PARMLIB member that was used to define this policy statement
pol_op
One of the following:
DELETE
The specified policy statement will delete the check(s) that match.
UPDATE
The specified policy statement will update the check(s) that match.
checkowner
The owner of the check(s) that are the target of this policy statement

Chapter 8. HZS messages 105

 HZS0202I

checkname
The name of the check(s) that are the target of this policy statement
cattype
One of the following:
(ANY):
The target must already belong to at least one of the specified categories before the policy statement is
applied.
(EVERY):
The target must already belong to all of the specified categories before the policy statement is applied.
(ONLY):
The target must already belong to only the specified categories before the policy statement is applied.
(EXCEPT):
The target must already belong to only the specified categories before the policy statement is applied.
category
The policy statement category value
exitrtn
The name of the HZSADDCHECK that must be matched before the policy statement is applied
reason
The update reason
text
is one of the following:
ACTIVE
INACTIVE
hhh
The hours part of the time from one check run to the next
mm The minutes part of the time from one check run to the next
SYSTEM
Apply system rules - use the interval value
HALF
Apply system rules - If the interval is not ONETIME, use one-half of the interval value
| SYNCVAL: {SYSTEM|hh:mm|*:mm}
| SYSTEM
| Apply system rules - the check gets scheduled, as soon as possible after is has been added and the system
| uses the last check run end time to calculate any subsequent check run start times.
| hh:mm
| The time of day in hours and minutes that the check should be scheduled to run for the first time as well as
| for subsequent iterations, synchronized with the current INTERVAL (or, EXCEPTION INTERVAL) value.
| *:mm
| The minute of the current hour (or the next hour if the minute has already passed for the current hour) that
| the check should to be scheduled to run at for the first time, as well as for subsequent iterations,
| synchronized with the current INTERVAL (or, EXCEPTION INTERVAL) value.
severity
One of the following:
NONE
The update severity value is defined as "SEVERITY(NONE)".
LOW
The update severity value is defined as "SEVERITY(LOW)".
MEDIUM
The update severity value is defined as "SEVERITY(MEDIUM)".

106 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0202I

HIGH
The update severity value is defined as "SEVERITY(HIGH)".
wtotype
One of the following options:
NONE
The updated WTO value is defined not to be issued as WTOs.
HARDCOPY
The updated WTO value is defined to be issued to the system hardcopy log only.
INFORMATIONAL
The update WTO value is defined to be issued as informational messages.
EVENTUAL ACTION
The update WTO value is defined to be issued as eventual action messages.
CRITICAL EVENTUAL ACTION
The update WTO value is defined to be issued as a critical eventual action messages.
desccodes
The list of additional descriptor codes used to write any exception messages issued by this check
routcodes
The list of routing codes used to write any exception messages issued by this check
parms
The updated user parameters
debug
One of the following:
OFF
The specified check is not running in DEBUG mode.
ON The specified check is running in DEBUG mode. Additional messages might be written to the message
buffer and may help to diagnose problems with the check.
verbose
One of the following options:
NO The specified check is not running in VERBOSE mode.
YES
The specified check is running in Verbose mode. Additional messages might be written to the message
buffer.
catoper
One of the following:
REPLACE
The specified categories will replace the categories to which the target check(s) belong.
ADD
The target check(s) will be added to the specified categories.
REMOVE
The target check(s) will be removed from the specified categories
System action: The system continues processing.
Operator response: None
System programmer response: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKDIS
Routing Code: -
Descriptor Code: -

Chapter 8. HZS messages 107

HZS0203I

HZS0203I hh.mm.ss HZS INFORMATION

POLICY(policy)
OUTSTANDING EXCEPTIONS: exceptions
(SEVERITY NONE: noneexceptions LOW: lowexceptions MEDIUM: medexceptions HIGH: highexceptions)
ELIGIBLE CHECKS: eligiblechecks (CURRENTLY RUNNING: running)
INELIGIBLE CHECKS: ineligiblechecks DELETED CHECKS: deletedchecks
{ ASID: asid LOG STREAM: logstreamname - text
ASID: asid LOG STREAM: NOT DEFINED
}
LOG STREAM WRITES PER HOUR: writerate
LOG STREAM AVERAGE BUFFER SIZE: bufsize BYTES
[HZSPDATA DSN: dsname]
HZSPDATA RECORDS: numpdata
PARMLIB: parmlib
Explanation: The MODIFY,DISPLAY command was entered, or a DISPLAY parmlib statement was processed, to
display the current status of IBM Health Checker for z/OS.
In the message text:
hh.mm.ss
The time in hours (00-23), minutes (00-59), and seconds (00-59) for the MODIFY DISPLAY function
policy
The name of the policy that is currently in effect.
exceptions
The number of outstanding exceptions found by IBM Health Checker for z/OS. The number of outstanding
exceptions does not include exceptions that were found by checks are currently executing.
noneexceptions
The number of outstanding SEVERITY(NONE) exceptions issued.
lowexceptions
The number of outstanding SEVERITY(LOW) exceptions issued.
medexceptions
The number of outstanding SEVERITY(MEDIUM) exceptions issued.
highexceptions
The number of outstanding SEVERITY(HIGH) exceptions issued.
eligiblechecks
The number of checks that are currently registered with IBM Health Checker for z/OS that are eligible to run
(they are both ACTIVE and ENABLED)
running
The number of checks that are running
ineligiblechecks
The number of checks that are currently registered with IBM Health Checker for z/OS that are not eligible to run
(they are ACTIVE but DISABLED or they are INACTIVE
deletedchecks
The number of checks that are no longer registered with IBM Health Checker for z/OS
asid
The Address Space Identifier of IBM Health Checker for z/OS
logstreamname
The name of the log stream user to save check output
text
is one of the following:
DISCONNECTING
IBM Health Checker for z/OS is disconnecting from the specified log stream.

108 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0204I

DISCONNECTED
The log stream is currently not connected to IBM Health Checker for z/OS.
CONNECTING
IBM Health Checker for z/OS is connecting to the specified log stream.
CONNECTED
IBM Health Checker for z/OS is connected to the specified log stream.
SUSPENDED
IBM Health Checker for z/OS is trying to connect to the specified log stream. Log stream processing has
been temporarily suspended because of a transient error in the log stream.
ERROR
IBM Health Checker for z/OS was connected to the specified log stream. Log stream processing has been
suspended because of a permanent error in the log stream.
NOT DEFINED
The log stream is currently not defined to IBM Health Checker for z/OS.
writerate
The number of writes per hour to the log stream (when logger support is active) and the number of writes per
hour that were bypassed (when logger support was not active).
bufsize
The average size of buffers that were written to the log stream (when logger support was active) or that were
bypassed (when logger support was not active).
dsname
The name of the HZSPDATA data set when provided in response to message HZS0013A or HZS0019A.
numpdata
The number of records that were last written to the HZSPDATA data set or that would be written if the write
were to be done now.
parmlib
The suffixes of the current HZSPRMxx parmlibs that have been processed for the current POLICY statements
System action: The system continues processing.
Operator response: None
System programmer response: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKDIS
Routing Code: -
Descriptor Code: -

HZS0204I hh.mm.ss POLICY SUMMARY

[THERE ARE NO POLICY STATEMENTS THAT MEET THE SPECIFIED CRITERIA]
POLICY(polname)
STMT NAMETYPECHECK OWNERCHECK NAME
polstmtpol_opcheckowner checkname
polstmtpol_opcheckowner checkname
Explanation: Either a MODIFY hzsproc,DISPLAY command or a DISPLAY statement in parmlib member
HZSPRMxx was processed to request summary information about policy statements.
In the message text:
hh.mm.ss
The time in hours (00-23), minutes (00-59), and seconds (00-59)
polname
The policy name

Chapter 8. HZS messages 109

HZS0205I • HZS0344I

polstmt
The policy statement name
pol_op
One of the following:
UPD
This is a POLICY UPDATE statement.
DEL
This is a POLICY DELETE statement.
checkowner
The owner of the check
checkname
The name of the check
System action: The system continues processing.
Operator response: None
System programmer response: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKDIS
Routing Code: -
Descriptor Code: -

HZS0205I hh.mm.ss POLICY NAMES

NAMENAMENAMENAME
polnamepolnamepolname polname
Explanation: Either a MODIFY hzsproc,DISPLAY command or a DISPLAY statement in parmlib member
HZSPRMxx was processed to request the names of the existing policies.
In the message text:
hh.mm.ss
The time in hours (00-23), minutes (00-59), and seconds (00-59).
polname
The policy name.
System action: The system continues processing.
Operator response: None
System programmer response: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKDIS
Routing Code: -
Descriptor Code: -

HZS0344I THE LOGGER REQUEST HAS COMPLETED.

LOG STREAM logstream IS CONNECTED
Explanation: IBM Health Checker for z/OS will save the check output to the specified log stream.
In the message text:
logstream
The log stream name
System action: The system continues processing.

110 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0345I • HZS0346I

Operator response: None

System programmer response: None
Problem determination: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKLG1
Routing Code: 2,11
Descriptor Code: 5

HZS0345I THE LOGGER OFF REQUEST HAS COMPLETED

Explanation: IBM Health Checker for z/OS is not using the log stream to save check output.
System action: The system continues processing.
Operator response: None
System programmer response: None
Problem determination: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKLG1
Routing Code: 2,11
Descriptor Code: 5

HZS0346I THE LOGGER REQUEST HAS COMPLETED.

THE LOG STREAM IS text
Explanation: The LOGGER=ON request could not complete successfully.
In the message text:
ALREADY CONNECTED
IBM Health Checker for z/OS is already connected to a log stream.
IN ERROR
IBM Health Checker for z/OS could not connect to the log stream.
NOT DEFINED
A log stream name was not specified, and was not previously defined.
System action: The system continues processing.
Operator response:
v If the LOGGER=ON request specified a log stream name, verify the name of the log stream that was entered, and
reenter the command if the wrong log stream name was specified.
v If the LOGGER=ON request did not specify the name of the log stream name, and the name of the desired log
stream is known, reenter the command with the name of the desired log stream name.
v Contact the system programmer.
System programmer response:
v Verify the name of the target log stream.
v Fix the log stream error conditioned referenced by the accompanying HZS0348E message, and reenter the
command
Problem determination:
v HZS0348E will be issued if a log stream connect was unsuccessful. HZS034E will contain the return code and
reason code associated with the IXGCONN failure.
v Additional IXGxxxx messages may be written to the system log that may help to diagnose the IXGCONN failure.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKLG1

Chapter 8. HZS messages 111

HZS0348E • HZS0349E

Routing Code: 2,11

Descriptor Code: 5

HZS0348E COULD NOT CONNECT TO LOG STREAM logstream.

RETURN CODE: retcode REASON CODE: rsncode
Explanation: A error was encountered when IBM Health Checker for z/OS tried to connect to the specified log
stream. No check output will be saved in the log stream.
In the message text:
logstream
The log stream name
retcode
The return code of the IXGCONN request
rsncode
The reason code of the IXGCONN request
System action: The system continues processing.
Operator response: Contact the system programmer.
System programmer response: Correct the error and use IBM Health Checker for z/OS LOGGER request to restart
the log stream.
Problem determination:
v The Return codes and reason codes associated with the IXGCONN failure are documented in the z/OS MVS
Programming: Authorized Assembler Services Reference EDT-IXG.
v Additional IXGxxxx messages may be written to the system log that may help to diagnose the IXGCONN failure.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKLG1
Routing Code: 1,2,10
Descriptor Code: 7,11

HZS0349E IBM HEALTH CHECKER FOR Z/OS

COULD NOT WRITE TO LOG STREAM logstream.
RC: retcode REASON: rsncode
NO ADDITIONAL ATTEMPTS WILL BE MADE TO USE THE LOG STREAM
UNTIL IT HAS BEEN RESTARTED
Explanation: IBM Health Checker for z/OS will not use the specified log stream to save check output. The log
stream will not be used until the error has been cleared, and the log stream has been restarted.
In the message text:
logstream
The log stream name
retcode
The return code of the IXGWRITE request
rsncode
The reason code of the IXGWRITE request
System action: The system continues processing.
Operator response: None
System programmer response: Correct the error and use the IBM Health Checker for z/OS LOGGER request to
restart the log stream.
Problem determination: None
Destination: IBM Health Checker for z/OS

112 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0350E • HZS0400I

Detecting Module: HZSTKLG1

Routing Code: 1,2,10
Descriptor Code: 11,7

HZS0350E IBM HEALTH CHECKER FOR Z/OS

HAS SUSPENDED WRITING TO LOG STREAM logstream.
RC: retcode REASON: rsncode
ADDITIONAL ATTEMPTS WILL BE MADE TO USE THE LOG STREAM
Explanation: IBM Health Checker for z/OS could not use the specified log stream to save check output. The log
stream will be used to save check output when the error condition has been cleared up.
In the message text:
logstream
The log stream name
retcode
The return code of the IXGWRITE request
rsncode
The reason code of the IXGWRITE request
System action: If the situation is transient, the system DOMs the message.
Operator response: None
System programmer response: If the situation is not transient, then take action to correct the error.
Problem determination: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSTKLG1
Routing Code: 1,2,10
Descriptor Code: 11,7

HZS0400I CHECK(checkowner,checkname):
operation PROCESSING HAS BEEN COMPLETED
Explanation: The system processed the request.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
operation
One of the following:
ACTIVATE
The ACTIVATE request
DEACTIVATE
The DEACTIVATE request
DELETE
The DELETE request
REFRESH
The REFRESH request
RUN
The RUN request

Chapter 8. HZS messages 113

HZS0401I • HZS0403I

UPDATE
The UPDATE request
ADD
The ADD CHECK request
System action: The system continues processing.
Operator response: None
System programmer response: None
Problem determination: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINPRM
Routing Code: 2,11
Descriptor Code: 5

HZS0401I POLICY STATEMENT(polstmt):

operation PROCESSING HAS BEEN COMPLETED
Explanation: The system processed the request.
In the message text:
polstmt
The name of the policy statement
operation
One of the following:
ADD
The ADD POLICY statement request
REMOVE
The REMOVE POLICY statement request
ADDREPLACE
The ADDREPLACE POLICY statement request
System action: The system continues processing.
Operator response: None
System programmer response: None
Problem determination: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINPRM
Routing Code: 2,11
Descriptor Code: 5

HZS0403I operation PROCESSING HAS BEEN COMPLETED

Explanation: The system processed the request.
In the message text:
operation
One of the following:
ADD PARMLIB
The ADD PARMLIB request

114 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0404I

SET PARMLIB
The SET PARMLIB request
LOGGER
The LOGGER request
ADDNEW
The ADDNEW request
REPLACE PARMLIB
The REPLACE PARMLIB request
ACTIVATE POLICY
The ACTIVATE POLICY request
System action: The system continues processing.
Operator response: None
System programmer response: None
Problem determination: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINPRM
Routing Code: 2,11
Descriptor Code: 5

HZS0404I CHECK(checkowner,checkname):
REFRESH DELETE PROCESSING HAS COMPLETED. NO CHECKS WERE ADDED
Explanation: Refresh processing consists of deleting the requested checks and then calling the HZSADDCHECK
dynamic exit to re-add the checks. The first part of the processing completed successfully. No dynamic exit routine
added a new or already-deleted check
In the message text:
checkowner
The owner of the check
checkname
The name of the check
System action: The system continues processing.
Operator response: Contact the system programmer.
System programmer response: If this result is unexpected, issue the following command to check the exit routines:
DISPLAY PROG,EXITS,EXITNAME=HZSADDCHECK,DIAG

If the exit routine that had originally added this check is no longer associated with the exit, consult
component-specific documentation for that exit routine to re-add it. If the exit routine is still associated with the exit,
search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center.
Problem determination: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINPRM
Routing Code: 2,11
Descriptor Code: 5

Chapter 8. HZS messages 115

HZS0405I • HZS0406I

HZS0405I CHECK(checkowner,checkname):
DELETE FORCE=YES PROCESSING HAS COMPLETED
Explanation: The system processed the request.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
System action: The system continues processing.
Operator response: None
System programmer response: None
Problem determination: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINPRM
Routing Code: 2,11
Descriptor Code: -

HZS0406I CHECK(checkowner,checkname):
ADD PROCESSING WAS NOT SUCCESSFUL.
problem
Explanation: The system processed the request.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
problem
One of the following:
COULD NOT LOAD CHECK ROUTINE
The check routine could not be loaded.
COULD NOT LOAD MESSAGE TABLE
The msgtable could not be loaded.
CHECK ALREADY EXISTS
A check or a check description, with the same owner and name already exists.
CHECK DATE IS OLD
The date is older than the date of an existing check with the same owner and name.
BAD OWNER NAME
The owner contains characters that are not valid.
BAD CHECK NAME
The check name contains characters that are not valid.
System action: The system continues processing.
Operator response: None
System programmer response: None
Problem determination: None
Destination: IBM Health Checker for z/OS

116 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0407I • HZS0410I

Detecting Module: HZSINPRM

Routing Code: 2,11
Descriptor Code: 5

HZS0407I operation PROCESSING FOUND NO MATCH

Explanation: The system processed the request.
In the message text:
operation
One of the following:
ADD PARMLIB
The ADD PARMLIB request
SET PARMLIB
The SET PARMLIB request
ADDNEW
The ADDNEW request
REPLACE PARMLIB
The REPLACE PARMLIB request
ACTIVATE POLICY
The ACTIVATE POLICY request
System action: The system continues processing.
Operator response: None
System programmer response: None
Problem determination: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINPRM
Routing Code: 2,11
Descriptor Code: 5

HZS0410I CHECK(checkowner,checkname):
operation PROCESSING FOUND NO MATCH
Explanation: The system processed the request.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
operation
One of the following:
ACTIVATE
The ACTIVATE request
DEACTIVATE
The DEACTIVATE request
DELETE
The DELETE request

Chapter 8. HZS messages 117

HZS0411I • HZS0413I

REFRESH
The REFRESH request
RUN
The RUN request
UPDATE
The UPDATE request
ADD
The ADD CHECK request
System action: The system continues processing.
Operator response: None
System programmer response: None
Problem determination: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINPRM
Routing Code: 2,11
Descriptor Code: 5

HZS0411I POLICY STATEMENT(polstmt): REMOVE PROCESSING FOUND NO MATCH

Explanation: The system found no matching policy statements.
In the message text:
polstmt
The name of the policy statement
System action: The system continues processing.
Operator response: None
System programmer response: None
Problem determination: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINPRM
Routing Code: 2,11
Descriptor Code: 5

HZS0413I POLICY STATEMENT(polstmt): ADD NOT DONE, POLICY STATEMENT ALREADY EXISTS
Explanation: The system found that a policy statement of that name already exists
In the message text:
polstmt
The name of the policy statement
System action: The POLICY ADD was not done.
Operator response: None
System programmer response: None
Problem determination: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINPRM
Routing Code: 2,11

118 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS0414I • HZS0420E

Descriptor Code: 5

HZS0414I CHECK(checkowner,checkname): NO MATCHING CHECKS WERE DELETED. REFRESH

PROCESSING HAS COMPLETED
Explanation: The REFRESH processing found no matching checks to'refresh.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
System action: The system performs the ADDNEW part of the refresh processing.
Operator response: None
System programmer response: None
Problem determination: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSINPRM
Routing Code: 2,11
Descriptor Code: 5

| HZS0420E n CHECKS HAVE BEEN FOUND FOR WHICH AT LEAST ONE MATCHING POLICY
| STATEMENT HAD A CONFLICT WITH THE CHECK VALUES. THE POLICY STATEMENTS
| WERE NOT APPLIED TO THOSE CHECKS. THE FIRST CASE IS CHECK(checkowner,checkname),
| MATCHED BY POLICY STATEMENT polstmt
| THIS CHECK HAD A {DATE | SYNCVAL} CONFLICT.
| Explanation: A policy statement was not applied to a check because one of the following situations was detected:
| v The date in a policy statement is older than the date of a matching check. The check date is the date specified by
| the DATE keyword of the HZSADDCK macro that added the check or the DATE parameter of the ADD or
| ADDREPLACE statement of the HZSPRMxx parmlib member that added the check.
| v A SYNCVAL value was specified and an INTERVAL or EXCEPTIONINTERVAL value did not obey the following
| rules:
| – for SYNCVAL(hh:mm) and INTERVAL OR EXCEPTIONINTERVAL(hhh:mm) the (exception-) interval duration in
| total minutes hhh*60 + mm has to be a divisor or a multiple of 1440 minutes (24 hours).
| – for SYNCVAL(*:mm) and INTERVAL OR EXCEPTIONINTERVAL(hhh:mm) the (exception-) interval duration
| value in total minutes hhh*60 + mm has to be a divisor or a multiple of 60 minutes (one hour).
| Note that a conflict can occur when any of the following occur:
| v The policy statement specifies a SYNCVAL that is in conflict with the checks INTERVAL OR
| EXCEPTIONINTERVAL
| v The policy statement specifies an INTERVAL OR EXCEPTIONINTERVAL that is in conflict with the checks
| SYNCVAL
| v The policy statement specifies a SYNCVAL that is in conflict with an INTERVAL OR EXCEPTIONINTERVAL in
| the policy

| In the message text:

| checkowner
| The owner of the check
| checkname
| The name of the check
| polstmt
| The policy statement name

Chapter 8. HZS messages 119

 HZS0421I

System action: The system continues processing.

| Operator response: For a DATE conflict issue the MODIFY hzsproc,DISPLAY,POLICY,OUTDATED command to
| locate the policy statements that are outdated. For any conflict issue the MODIFY hzsproc,DISPLAY,
| HECK=(**)POLICYEXCEPTIONS command to determine the checks that were found for which a matching policy
| statement had a conflict. Provide this information to the system programmer.
| System programmer response: For a DATE conflict, examine the outdated policy statements and the checks to
| which they apply. Ensure that the parameters and values on the policy statement are still appropriate for the check(s)
| to which that policy statement applies. Update the policy statement with a new date and any other changed needed.
| For a SYNCVAL conflict, change the SYNCVAL or INTERVAL or EXCEPTIONINTERVAL value so that the
| INTERVAL or EXCEPTIONINTERVAL duration is an appropriate divisor or multiple of 24 hours or one hour
| respectively. To display the check values, issue the MODIFY
| hzsproc,DISPLAY,CHECK=(check_owner,check_name),DETAIL command for the check(s) identified by the MODIFY
| hzsproc,DISPLAY,CHECK=(*,*),POLICYEXCEPTIONS command and find the values that are in conflict.
Problem determination: None
Destination: IBM Health Checker for z/OS
| Detecting Module: HZSPKANP,HZSINPRM,HZSMIMST
Routing Code: 1,2,10
Descriptor Code: 7,11

| HZS0421I CHECK(checkowner,checkname)
| UPDATE NOT PROCESSED DUE TO {DATE | SYNCVAL} CONFLICT
| Explanation: A check was not processed because one of the following situations was detected:
| v The specified date on the UPDATE request is older than the date of the matching check. The check date is the
| date specified by the DATE keyword of the HZSADDCK macro that added the check or the DATE parameter of
| the ADD or ADDREPLACE statement of the HZSPRMxx parmlib member that added the check.
| v A SYNCVAL value was specified and an INTERVAL or EXCEPTIONINTERVAL value did not obey the following
| rules:
| – for SYNCVAL(hh:mm) and INTERVAL OR EXCEPTIONINTERVAL(hhh:mm) the (exception-) interval duration in
| total minutes hhh*60 + mm has to be a divisor or a multiple of 1440 minutes (24 hours).
| – for SYNCVAL(*:mm) and INTERVAL OR EXCEPTIONINTERVAL(hhh:mm) the (exception-) interval duration
| value in total minutes hhh*60 + mm has to be a divisor or a multiple of 60 minutes (one hour).

| In the message text:

| checkowner
| The owner of the check
| checkname
| The name of the check
| System action: The system continues processing.
| Operator response: None
| System programmer response: For a DATE conflict, make sure that the parameters and values on the UPDATE
| statement are appropriate for the check. Reissue the UPDATE with a new date and any other changed needed.
| For a SYNCVAL conflict, change the SYNCVAL or INTERVAL or EXCEPTIONINTERVAL value so that the
| INTERVAL or EXCEPTIONINTERVAL duration is an appropriate divisor or multiple of 24 hours or one hour
| respectively. To display the check values, issue the MODIFY
| hzsproc,DISPLAY,CHECK=(check_owner,check_name),DETAIL command and find the values that are in conflict.
| Problem determination: None
| Destination: IBM Health Checker for z/OS
| Detecting Module: HZSINPRM, HZSPKCHG, HZSMIMST
| Routing Code: 2,11

120 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS1001E • HZS1003E

| Descriptor Code: 5

HZS1001E CHECK(checkowner,checkname):
AN INSTALLATION PARAMETER ERROR WAS DETECTED.
Explanation: The check routine detected an error in the parameters supplied to the check.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
System action: The check will no longer run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1002E CHECK(checkowner,checkname): AN ERROR OCCURRED, DIAG: diag

Explanation: The error for this message was supplied by the check routine to report a failure on a system service.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
diag
Diagnostic data
System action: The check will no longer run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error and refresh the check.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1003E CHECK(checkowner,checkname):
THE CHECK IS NOT APPLICABLE IN THE CURRENT SYSTEM ENVIRONMENT.
Explanation: The check is not applicable in this system.
In the message text:
checkowner
The owner of the check

Chapter 8. HZS messages 121

HZS1084I • HZS1085I

checkname
The name of the check
System action: The system will not run the check.
Operator response: None
System programmer response: None
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1084I dsname was not found on volume volume

Explanation: The request to return data set information could not be completed because the data set was not on the
volume. This message appears only in the message of check message buffer and only when the check is in debug
mode.
In the message text:
dsname
The name of the data set
volume
The volume
System action: The system continues.
Operator response: Report this problem to the system programmer.
System programmer response: Either fix the data set or correct the situation that leads the system to be looking for
the information of data set.
Problem determination: None
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKDSI
Routing Code: -
Descriptor Code: -

HZS1085I Catalog information for dsname could not be retrieved. DIAG=diag

Explanation: The request to return data set information could not be completed because, although the data set was
allocated successfully, information from the catalog entry could not be retrieved. This message appears only in the
message of check buffer and only when the check is in debug mode or has explicitly requested this error processing.
In the message text:
dsname
The name of the data set
diag
Diagnostic data
System action: The system continues.
Operator response: Report this problem to the system programmer.
System programmer response: Search problem reporting databases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Problem determination: None

122 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS1201E • HZS1202E

Destination: IBM Health Checker for z/OS

Detecting Module: HZSPKDSI
Routing Code: -
Descriptor Code: -

HZS1201E CHECK(checkowner,checkname):
PARAMETER key IS REQUIRED BUT WAS NOT SPECIFIED
Explanation: The check parameter has a syntax error. This should be followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
key
The parameter in error
System action: The check will no longer run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1202E CHECK(checkowner,checkname):
PARAMETER key WAS SPECIFIED BUT IS NOT ALLOWED
Explanation: The check parameter has a syntax error. This might be followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
key
The parameter in error
System action: The check will not run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

Chapter 8. HZS messages 123

HZS1203E • HZS1205E

HZS1203E CHECK(checkowner,checkname):
PARAMETER keyn' IS NOT VALID
Explanation: The check parameter has a syntax error. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
key
The parameter in error
System action: The check will not run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1204E CHECK(checkowner,checkname):
UNEXPECTED END OF PARAMETER STRING
Explanation: The check parameter has a syntax error. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
System action: The check will no longer run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1205E CHECK(checkowner,checkname):
A PARAMETER WAS EXPECTED BUT 'parm' WAS FOUND INSTEAD
Explanation: The check parameter has a syntax error. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check

124 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS1206E • HZS1207E

parm
The parameter in error
System action: The check will not run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1206E CHECK(checkowner,checkname):
A DELIMITER WAS EXPECTED BUT 'parm' WAS FOUND INSTEAD
Explanation: The check parameter has a syntax error. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
parm
The parameter in error
System action: The check will no longer run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1207E CHECK(checkowner,checkname):
PARAMETER parm HAS TOO MANY VALUES, numvalues
Explanation: The check parameter has a syntax error. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
parm
The parameter in error
numvalues
The number of values
System action: The check will not run.
Operator response: Report this problem to the system programmer.

Chapter 8. HZS messages 125

HZS1208E • HZS1209E

System programmer response: Correct the error.

Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1208E CHECK(checkowner,checkname):
PARAMETER parm HAS TOO FEW VALUES, numvalues
Explanation: The check parameter has a syntax error. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
parm
The parameter in error
numvalues
The number of values
System action: The check will not run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1209E CHECK(checkowner,checkname):
PARAMETER parm IS NOT RECOGNIZED
Explanation: The check parameter has a syntax error. The indicated parameter was not processed might be
incorrect. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check.
checkname
The name of the check.
parm
The parameter in error. The parameter is up to a length of 17 characters.
System action: The check will not run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS

126 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS1210E • HZS1211E

Detecting Module: HZSPKMGB

Routing Code: -
Descriptor Code: -

HZS1210E CHECK(checkowner,checkname):
PARAMETER parm IS MISSING ITS VALUE
Explanation: The check parameter has a syntax error. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
parm
The parameter in error
System action: The check will no longer run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1211E CHECK(checkowner,checkname):
PARAMETER parm VALUE 'value' IS TOO LARGE
Explanation: The check parameter has a syntax error. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
parm
The parameter in error
value
The value in error
System action: The check will not run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

Chapter 8. HZS messages 127

HZS1212E • HZS1213E

HZS1212E CHECK(checkowner,checkname):
PARAMETER parm VALUE 'value' IS TOO SMALL
Explanation: The check parameter has a syntax error. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
parm
The parameter in error
value
The value in error
System action: The check will not run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1213E CHECK(checkowner,checkname):
PARAMETER parm VALUE 'value' IS TOO LONG
Explanation: The check parameter has a syntax error. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
parm
The parameter in error
value
The value in error
System action: The check will not run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

128 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS1214E • HZS1215E

HZS1214E CHECK(checkowner,checkname):
PARAMETER parm VALUE 'value' IS TOO SHORT
Explanation: The check parameter has a syntax error. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
parm
The parameter in error
value
The value in error
System action: The check will not run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1215E CHECK(checkowner,checkname):
PARAMETER parm VALUE 'value' IS NOT DECIMAL
Explanation: The check parameter has a syntax error. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
parm
The parameter in error
value
The value in error
System action: The check will not run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

Chapter 8. HZS messages 129

HZS1216E • HZS1218E

HZS1216E CHECK(checkowner,checkname):
PARAMETER parm VALUE 'value' IS NOT HEXADECIMAL
Explanation: The check parameter has a syntax error. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
parm
The parameter in error
value
The value in error
System action: The check will not run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1217E CHECK(checkowner,checkname):
PARAMETERS WERE SPECIFIED BUT NONE ARE ALLOWED
Explanation: The check requires that no parameters be specified, but there are parameters.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
System action: The check will not run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1218E CHECK(checkowner,checkname):
PARAMETER NUMBER n WAS NOT PROCESSED
Explanation: The check parameter has a syntax error. The indicated parameter was not processed and might be
incorrect. This should be followed by message HZS1001E.
In the message text:

130 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 HZS1219E • HZS1300I

checkowner
The owner of the check
checkname
The name of the check
n The number of the positional parameter in error
System action: The check will not run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error.
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1219E CHECK(checkowner,checkname):
MIXING POSITIONAL AND KEYWORD FORMATS IS NOT ALLOWED
Explanation: The check parameter has a syntax error. At least one keyword was of keyword format (for example,
key(value) or key=value) and another was of positional format (for example, value). The two formats cannot be
mixed. This is followed by message HZS1001E.
In the message text:
checkowner
The owner of the check
checkname
The name of the check
System action: The check will not run.
Operator response: Report this problem to the system programmer.
System programmer response: Correct the error. You might have an extra comma within the parameter string that
could result in a null (positional) parameter (for example, key=value,key2=value)
Problem determination: Refer to component documentation.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1300I EXEC exec DID NOT ISSUE 'CALL HZSLSTRT'

Explanation: The REXX check executable file was initiated but did not issue the required 'CALL HZSLSTRT'
operation.
In the message text:
exec
The name of the executable file.
System action: This iteration of the check is treated as "unsuccessful."
Operator response: None.
Application Programmer Response: Fix the executable file.
System programmer response: None.

Chapter 8. HZS messages 131

HZS1301I • HZS1302I

Problem determination: None.

Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

HZS1301I EXEC exec DID NOT COMPLETE SUCCESSFULLY.

[AXREXX COULD NOT ALLOCATE: dataset]
AXREXX SERVICE RETURN CODE: axrexxrc REASON CODE: axrexxrsn
AXREXX DIAG RETURN CODE: diagrc REASON CODE: diagrsn
Explanation: The REXX check exec did not complete successfully. When known, the return code from the exec is
provided. When the failure was due to not being able to allocate a required data set, the data set name is provided.
In the message text:
exec
The name of the executable file
dataset
The name of the data set that must be allocated by AXREXX based on the current check options
axrexxrc
The return code from the AXREXX service that the system used to invoke the exec
axrexxrsn
The reason code from the AXREXX service that the system used to invoke the exec
diagrc
The diagnostic return code from the AXREXX service
diagrsn
The diagnostic reason code from the AXREXX service
System action: This iteration of the check is treated as "unsuccessful."
Operator response: None.
Application Programmer Response: Fix the executable file or provide the necessary data set.
System programmer response: None.
Problem determination: Refer to the documentation for the AXREXX service.
Destination: IBM Health Checker for z/OS
Routing Code: -
Descriptor Code: -

HZS1302I CHECK COULD NOT BE STARTED. {AXREXX ! IEAVRLS} RC: rc REASON: rsn
Explanation: The system attempted to initiate the check but could not.
In the message text:
AXREXX
The AXREXX service used to start a PubItemIgnore REXX check
IEAVRLS
The IEAVRLS (release) service used to start a remote check
rc The return code from the service
rsn
The reason code from the service
System action: This iteration of the check is treated as "unsuccessful."

132 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Operator response: None.
Application Programmer Response: Clarify the meaning of the return code and reason code for the identified
service and correct the problem
System programmer response: None.
Problem determination: None.
Destination: IBM Health Checker for z/OS
Detecting Module: HZSPKMGB
Routing Code: -
Descriptor Code: -

Message output from DISPLAY parameter of MODIFY command or

HZSPRMxx

HZS0200I - DISPLAY SUMMARY message output

HZS0200I 13.15.35 CHECK SUMMARY
OWNER CHECK NAME STATESTATUS
check_owner check_name AD NEW COPY
IE NOT STARTED
AE STARTING
AD ENV N/A
ID ENV N/A
AEG RUNNING
AE SUCCESSFUL
AE EXCEPTION-NONE
AEG+EXCEPTION-LOW
IE EXCEPTION-MEDIUM
IE +EXCEPTION-HIGH
IE PARAMETER ERROR
AE ABEND
AD ABEND
AD UNEXPECTED ERROR
AD INIT ERROR
AD DELETE ERROR
DELETE PENDING
DELETED
ADG SYSNAME=SY345678
IDG SYSNAME=SY345678
A - ACTIVE I - INACTIVE
E - ENABLED D - DISABLED
G - GLOBAL CHECK + - ADDITIONAL WARNING MESSAGES ISSUED

HZS0201I - DISPLAY DETAIL message output

HZS0201I 13.15.35 CHECK DETAIL
CHECK(owner,name)
STATE: INACTIVE(ENABLED) GLOBAL STATUS: reason
STATE: INACTIVE(DISABLED) GLOBAL STATUS: reason
STATE: INACTIVE(DISABLED) STATUS: reason
STATE: INACTIVE(ENABLED) STATUS: reason
STATE: ACTIVE(ENABLED) GLOBAL STATUS: reason
STATE: ACTIVE(DISABLED) GLOBAL STATUS: reason
STATE: ACTIVE(ENABLED) STATUS: reason
STATE: ACTIVE(DISABLED) STATUS: reason
STATUS: NEW COPY
STATUS: ENV N/A

Chapter 8. HZS messages 133

 STATUS: STARTING
STATUS: RUNNING
STATUS: SUCCESSFUL
STATUS: EXCEPTION-NONE
STATUS: EXCEPTION-LOW
STATUS: EXCEPTION-MEDIUM
STATUS: EXCEPTION-HIGH
STATUS: PARAMETER ERROR
STATUS: INITIATION ERROR
STATUS: DELETE ERROR
STATUS: ABEND
STATUS: UNEXPECTED ERROR
STATE: INACTIVE(DISABLED) GLOBAL STATUS: SYSTEM=sysname78
STATE: ACTIVE(DISABLED) GLOBAL STATUS: SYSTEM=sysname78
STATE: DELETE PENDING
STATE: DELETED mm/dd/yyyy hh:mm
The check reported an unexpected condition DIAG: diag
EXITRTN: routine
LAST RUN: date time NEXT SCHEDULED: date time
LAST RUN: date time NEXT SCHEDULED: (INACTIVE)
LAST RUN: date time NEXT SCHEDULED: (DISABLED)
LAST RUN: date time NEXT SCHEDULED: (NOT SCHEDULED)
LAST RUN: (N/A) NEXT SCHEDULED: (INACTIVE)
LAST RUN: (N/A) NEXT SCHEDULED: (DISABLED)
LAST RUN: (N/A) NEXT SCHEDULED: (NOT SCHEDULED)
INTERVAL: hhh.mm SEVERITY: severity WTO: WTO_Desc
NONE HARDCOPY
LOW INFO
MEDIUM EVENTUAL
HIGH IMMEDIATE
DESCCODE: ##,##,##,##,##,##,##,##,##,##,##,##,##,##,##,##,##,##
ROUTCODE: ###,###,###,###,###,###,###,###,###,###,###,###,###
###,###,###........................................
DELETED BY: deleted by
POLICY(policy_name)
HZSCHECK(job_name)
MODIFY COMMAND
PARMLIB(HZSPRMxx)
MODIFIED BY: lastmodified
N/A
POLICY(policy_name)
HZSCHECK(job_name)
MODIFY COMMAND
PARMLIB(HZSPRMxx)

THERE ARE NO PARAMETERS IN EFFECT FOR THIS CHECK

DEFAULT PARAMETERS: 1st 40 characters of default parameters
next 40 characters of default parameters
USER SUPPLIED PARAMETERS: 1st 40 characters of user parameters
next 40 characters of user parameters
REASON FOR CHECK: 1st 47 characters of default reason
next 47 characters of default reason
REASON FOR UPDATE: 1st 47 characters of user reason
next 47 characters of user reason
DEFAULT DATE: yyyymmdd USER DATE: yyyymmdd DEBUG: debug
DEFAULT DATE: yyyymmdd DEBUG: debug
CATEGORIES: category_1 category_2 category_3
category_x category_y category_z
INTERNAL DIAGNOSTICS - CHECK TOKEN: pqeaddr/asid
ROUTINE: name-######## MSGTBL: name-######## FUNC: check-funct

134 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 N/A
INIT
CHECK
CLEANUP
DELETE
LAST CPU TIME: xxxx.yyyy MAX CPU TIME: xxxx.yyyy

HZS0202I - DISPLAY POLICY DETAIL message output

HZS0202I 13.15.35 POLICY DETAIL *
POLICY NAME: POLICY2 ORIGIN: MODIFY COMMAND DATE: yyyymmdd*
POLICY NAME: POLICY2 ORIGIN: HZSPRMxx DATE: yyyymmdd*
type CHECK(owner,name) *
DELETE *
UPDATE *
REASON: 1st 62 characters of user reason *
next 62 characters of user reason *
INTERVAL: hhh.mm *
SEVERITY: severity *
NONE *
LOW *
MEDIUM *
HIGH *
WTO: WTO_Desc *
HARDCOPY *
INFO *
EVENTUAL *
IMMEDIATE *
DESCCODE: ##,##,##,##,##,##,##,##,##,##,##,##,##,##,##,##,##,## *
ROUTCODE: ###,###,###,###,###,###,###,###,###,###,###,###,### *
###,###,###........................................ *
*
PARAMETERS: 1st 58 characters of user parameters *
next 58 characters of user parameters *
type CATEGORIES: category_1 category_2 category_3 *
REPLACE *
ADD *
REMOVE *
category_x category_y category_z *

HZS0204I - DISPLAY POLICY SUMMARY message output

HZS0204I 13.15.35 POLICY SUMMARY
NAME TYPE CHECK OWNER CHECK NAME
policy_nam UPD check_owner check_name
policy_nam DEL check_owner check_name

HZS0203I - DISPLAY STATUS message output

HZS0203I 13.15.35 HZS INFORMATION
OUTSTANDING EXCEPTIONS-########:
(NONE-######## LOW-######## MEDIUM-######## HIGH-########)
ELIGIBLE checks: ######## (CURRENTLY RUNNING: ########)
INELIGIBLE CHECKS:######## DELETED CHECKS: ########
ASID: #### LOG STREAM: logstream name - status
DISCONNECTING
DISCONNECTED
UNIDEFINED
CONNECTING
CONNECTED
SUSPENDED

Chapter 8. HZS messages 135

 ERROR
PARMLIB: xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx
xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx

136 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Chapter 9. IAR messages
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).
In the message text:
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.
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:
v 76 kilobytes
v The amount of storage available for a V=R area that does not overlap the CSA
Source: Real storage manager (RSM)
Detecting Module: IARMS, IAXMS
Routing Code: 1
Descriptor Code: 2

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:

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
System action: The system enters wait state X'A21'.
Operator response: See the operator response for wait state code X'A21'.
System programmer response: See the system programmer response for wait state code X'A21'.
Source: Real storage manager (RSM)
Detecting Module: IARMN, IAXMN
Routing Code: 1
Descriptor Code: 1

© Copyright IBM Corp. 1988, 2012 137

IAR004I • IAR005E

IAR004I THE RSU PARAMETER WAS NOT COMPLETELY SATISFIED

Explanation: During system initialization, the real storage manager (RSM) found that system storage requirements,
the LFAREA parameter and the REAL parameter have not left enough real storage to satisfy the reconfiguration
storage units (RSU) parameter. The LFAREA, 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.
System programmer response: Change the parameters in IEASYSxx before the next IPL.
Source: Real storage manager (RSM)
Detecting Module: IARMT, IAXMT
Routing Code: 2
Descriptor Code: 4

IAR005E PREFERRED AREA HAS EXPANDED, RECONFIGURABILITY AND PERFORMANCE MAY BE

IMPAIRED. text.
Explanation: The real storage manager (RSM) converted one or more non-preferred frames or 1 MB frames to
preferred frames. The system may no longer be able to reconfigure all or part of the storage in the non-preferred
area. If this expansion involves frames below 16 megabytes, the system can page fix these frames, which might lead
to performance problems.
In the message text, text is one of the following:
CHECK RSU VALUE
When running in z/Architecture® mode with a specified RSU of 0, there are still areas of real storage being
managed as preferred and non-preferred storage. Specifically, there is a class of real storage frames managed in a
special way called quad frames. These frames are used primarily to hold segment tables and must be 4
contiguous frames of real storage. The area occupied by quad frames is treated as non-preferred storage. During
times of heavy demand for real storage, frames from the area used by quad frames may be required for system
overhead and will be reallocated for system use for the duration of the IPL. In this case, message IAR005E is
issued.
POSSIBLY DUE TO RECOVERY IN PROGRESS
During recovery processing for the RSM, some available frames might appear to be not available to the system.
This condition is temporary and will be cleared when the recovery processing completes.
System action: The system can use the newly designated frames as preferred storage for additional long term
resident pages.
Operator response: Enter a DISPLAY M command to determine the number of frames remaining in the
non-preferred area.
System programmer response: Check that the reconfigurable storage unit (RSU) value specified in the IEASYSxx
parmlib member is appropriate for your installation. See z/OS MVS Initialization and Tuning Reference for more
information about the IEASYSxx parmlib member.
If the message indicates that recovery processing is in progress and the RSU value is appropriate, then no further
action is required. Additional frames will become available as the recovery processing completes.
Source: Real storage manager (RSM)
Detecting Module: IARUC, IAXUC
Routing Code: 1
Descriptor Code: 11

138 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAR006A • IAR008E

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.
System action: The system waits for the operator to reply.
Operator response: Reenter the VRREGN, REAL, or RSU parameter with a valid value.
Source: Real storage manager (RSM)
Detecting Module: IARMU, IARMS, IARMT, IAXMU, IAXMS, IAXMT
Routing Code: 1
Descriptor Code: 2

| 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.
| In the message text:
| 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.
| Source: Real storage manager (RSM)
| Detecting Module: IARQC
| Routing Code: 5
| Descriptor Code: -

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.
PREVIOUS INVOCATION TERMINATION HAS NOT COMPLETED.
THE RSM TRACE DATA SPACE COULD NOT BE CREATED.
TOTAL BUFFER SIZE EXCEEDS TRACE DATA SPACE SIZE
TOTAL SIZE OF BUFFERS REQUESTED IS INVALID
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.

Chapter 9. IAR messages 139

IAR009I • IAR010I

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.
Source: Real storage manager (RSM)
Detecting Module: IARQC
Routing Code: 5
Descriptor Code: -

IAR009I RSM COMPONENT TRACE HAS LOST AN ENTRY BECAUSE ALL BUFFERS WERE FULL.
Explanation: The operator started the real storage 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.
Operator response: Notify the system programmer.
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
Source: Real storage manager (RSM)
Detecting Module: IARQZ, IAXQZ

IAR010I RSM COMPONENT TRACE HAS WRAPPED AN ALREADY FULL BUFFER.

Explanation: The operator started the real storage 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.
Operator response: Notify the system programmer.
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

140 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAR011I • IAR012W

Source: Real storage manager (RSM)

Detecting Module: IARQZ, IAXQZ
Routing Code: 4
Descriptor Code: 1

IAR011I RSM COMPONENT TRACE EXTERNAL WRITER MAY HAVE LOST ENTRIES
Explanation: The operator started the real storage 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.
Source: Real storage manager (RSM)
Detecting Module: IARQZ, IAXQZ
Routing Code: 1
Descriptor Code: 4

IAR011W A PAGE WITHIN FLPA IS NOT PAGE FIXED.

Explanation: The real storage manager (RSM) detected pageable storage within the range of the fixed link pack area
(FLPA) or the EXTENDED FLPA.
System action: The system enters wait state X'A20'.
Operator response: See the operator response for wait state X'A20'.
System programmer response: See the system programmer response for wait state X'A20'.
Source: Real storage manager (RSM)
Detecting Module: IARMN, IAXMN
Routing Code: 2
Descriptor Code: 1

IAR012W A PAGE WITHIN PLPA OR MLPA HAS NO COPY ON AUXILIARY STORAGE

Explanation: The real storage manager (RSM) 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 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'.
Operator response: See the operator response for wait state X'A2A'.
System programmer response: See the system programmer response for wait state X'A2A'.
Source: Real storage manager (RSM)
Detecting Module: IARMN, IAXMN

Chapter 9. IAR messages 141

 IAR013I • IAR016I

Routing Code: 2
Descriptor Code: 1

| IAR013I xxxxxxM|G|T STORAGE IS RECONFIGURABLE

| Explanation: The indicated amount of storage, xxxxxxM|G|T (MB, GB, TB) has been made reconfigurable in
response to the value specified in the RSU parameter.
System action: The system continues processing.
Operator response: None.
System programmer response: None.
Source: Real storage manager (RSM)
Detecting Module: IARMT, IAXMT
Routing Code: 2
Descriptor Code: 4

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.
System action: The system continues processing. However, the excess storage is not used.
Operator response: None.
System programmer response: None.
Source: Real storage manager (RSM)
Detecting Module: IAXMN
Routing Code: 12

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, the
additional storage should be configured as expanded storage and the system re-IPLed.
System programmer response: None.
Source: Real storage manager (RSM)
Detecting Module: IARMI
Routing Code: -
Descriptor Code: -

IAR016I 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.
System action: The system continues processing. However, the expanded storage is not used.

142 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAR019I

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.
System programmer response: None.
Source: Real storage manager (RSM)
Detecting Module: IAXMN
Routing Code: 1
Descriptor Code: 12

| IAR019I text
| Explanation: Where text is one of the following message responses:
| The message is in response to the DISPLAY VIRTSTOR command.
| hh.mm.ss DISPLAY VIRTSTOR
| SOURCE ={xx|(OP)|DEFAULT}
| TOTAL LFAREA = aaaaaaaaaaaM
| LFAREA AVAILABLE = bbbbbbbbbbbbbbbM
| LFAREA ALLOCATED (1M) = cccccccccccccccM
| LFAREA ALLOCATED (4K) = dddddddddddddddM
| LFAREA ALLOCATED (PAGEABLE1M) = gggggggggggggggM
| MAX LFAREA ALLOCATED (1M) = eeeeeeeeeeeeeeeM
| MAX LFAREA ALLOCATED (4K) = fffffffffffffffM
| MAX LFAREA ALLOCATED (PAGEABLE1M) = hhhhhhhhhhhhhhhM
| UNABLE TO PROCESS COMMAND DUE TO LARGE PAGE REQUEST IN PROGRESS

| In the message text:

| xx|(OP)|DEFAULT
| The origin of the LFAREA and PLAREA specification can be a parmlib member (xx), operator supplied (OP)
| or the default value (DEFAULT).
| hh.mm.ss
| The hour (00-23), minute (00-59), and second (00-59) that the system issued this message.
| aaaaaaaaaaaaaaaM
| The total size of the 1 MB LFAREA and PLAREA, in megabytes (M). The amount displayed is the amount
| specified by the installation (or defaulted to) by the LFAREA keyword in the IEASYSxx parmlib member.
| LFAREA AVAILABLE = bbbbbbbbbbbbbbbM
| The amount of available 1 MB pages, in megabytes (M).
| LFAREA ALLOCATED (1M) = cccccccccccccccM
| The amount of allocated 1 MB pages on behalf of 1 MB page requests, in megabytes (M).
| LFAREA ALLOCATED (4K) = dddddddddddddddM
| The amount of allocated 1 MB pages on behalf of 4 KB page requests, in megabytes (M).
| LFAREA ALLOCATED (PAGEABLE1M) =gggggggggggggggM
| The amount, in megabytes, of allocated 1MB pages on behalf of pageable 1MB page requests.
| MAX LFAREA ALLOCATED (1M) = eeeeeeeeeeeeeeeM
| The maximum allocated 1 MB pages on behalf of 1 MB page requests, in megabytes (M).
| MAX LFAREA ALLOCATED (4K) = fffffffffffffffM
| The maximum allocated 1 MB pages on behalf of 4 KB page requests, in megabytes (M).
| MAX LFAREA ALLOCATED (PAGEABLE1M) = hhhhhhhhhhhhhhhM
| The high water mark, in megabytes, of allocated 1MB pages on behalf of pageable 1MB page requests.
| UNABLE TO PROCESS COMMAND DUE TO LARGE PAGE REQUEST IN PROGRESS
| Reissue the DISPLAY VIRTSTOR,LFAREA command when there are no large page requests in progress.
| System action: The system continues processing.
| Operator response: None.

Chapter 9. IAR messages 143

 IAR020I • IAR023A

| System programmer response: None.

| Source: Real storage manager (RSM)
| Detecting Module: IEECB903

IAR020I THE LFAREA WAS SPECIFIED BUT LARGE PAGE SUPPORT IS NOT AVAILABLE
Explanation: The LFAREA parameter was specified but large page support is not available.
System action: The system ignores the LFAREA parameter.
Operator response: Ensure that the right IEASYSxx member is used for this IPL. If the right IEASYSxx member is
used, but large page support is not available, contact your system programmer.
System programmer response: If the use of large pages is required, ensure that the right level of the z/OS
operating system is installed and that you are running on a machine that has the enhanced DAT facility installed.
Source: Real storage manager (RSM)
Detecting Module: IAXMT

IAR021I THE LFAREA WAS SPECIFIED BUT SUFFICIENT STORAGE IS NOT AVAILABLE
Explanation: The LFAREA parameter was specified but sufficient storage is not available.
System action: The LFAREA parameter is ignored.
Operator response: Ensure that the right IEASYSxx member is used for this IPL. If the right IEASYSxx member is
being used, but large page support is not available, contact your system programmer.
System programmer response: If the use of large pages is required, ensure that enough storage is installed for the
z/OS image. Large pages cannot be backed below 2 GB, so you need more than 2 GB of real storage in order to use
large page support. Also, if (80% of the online storage at IPL) minus 2 GB is less than 1MB, the LFAREA specification
is ignored.
Source: Real storage manager (RSM)
Detecting Module: IAXMN
Routing Code: 1
Descriptor Code: 12

IAR022I MAXIMUM AVAILABLE LFAREA SIZE IS YYYYYYM

Explanation: The LFAREA parameter was specified but the amount specified exceeds the maximum amount of
storage that can be specified for the LFAREA.
System action: The LFAREA parameter value is not accepted. The system issues a prompt for a re-specification of
the LFAREA value.
Operator response: Reply with an LFAREA value that does not exceed the maximum amount of storage. Use the
value to back large pages as indicated in the message above.
System programmer response: Ensure an appropriate LFAREA value is specified.
Source: Real storage manager (RSM)
Detecting Module: IAXMT

IAR023A INVALID LFAREA PARM- RESPECIFY OR PRESS ENTER FOR LFAREA=0M

Explanation: Not applicable value was specified on the LFAREA IEASYSxx parameter specified for the LFAREA.
System action: The LFAREA parameter value is not accepted. The system issues a prompt for a re-specification of
the LFAREA value. See z/OS MVS Initialization and Tuning Reference for information about valid specification of the
LFAREA parameter.
Operator response: Reply with valid LFAREA parameter value.

144 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAR024W • IAR026I

System programmer response: Ensure that an appropriate LFAREA value is specified.

Source: Real storage manager (RSM)
Detecting Module: IAXMT

IAR024W COMMON MEMORY OBJECT COULD NOT BE CREATED

Explanation: The real storage manager (RSM) could not successfully create a common memory object in high virtual
storage. The address portion of the program status word (PSW) contains X'xxxrrA2C' where rr is the reason code.
System action: The system enters wait state X'A2C'.
Operator response: See the operator response for wait state X'A2C'.
System programmer response: See the system programmer response for wait state X'A2C'.
Source: Real storage manager (RSM)
Detecting Module: IARMN

IAR025I THE LFAREA WAS NOT COMPLETELY SATISFIED - SIZE IS SET TO YYYYYYM
Explanation: The LFAREA parameter was specified but the amount specified could not be completely satisfied.
System action: The LFAREA parameter is ignored. Only the amount indicated in this message is used for Large
Page Support.
Operator response: Ensure that the right IEASYSxx member is used for this IPL. If the right IEASYSxx member is
being used, but the request could not be satisfied, contact your system programmer.
System programmer response: If the use of large pages is required, search problem reporting databases for a fix for
this problem. If no fix exists, contact the IBM Support Center.
Source: Real storage manager (RSM)
Detecting Module: IAXMT
Routing Code: 1
Descriptor Code: 12

IAR026I THE RSU VALUE SPECIFIED EXCEEDS THE TOTAL AMOUNT OF REAL STORAGE AVAILABLE
| ON THIS SYSTEM: yyyyyyyyM|G|T
Explanation: The RSU value was specified, but the amount specified exceeds the amount of real storage in the
system.
In the message text:
| yyyyyyyyM|G|T
| Amount of real storage, in MB, GB or TB, available in the system.
System action: The RSU parameter value is not accepted. The system issues message IAR006A to prompt for a
re-specification of the RSU value, or hit enter to accept the default. The default RSU value is 0.
Operator response: Reply with an RSU value that does not exceed the maximum amount of real storage, or hit
enter to accept the default. The RSU value must be chosen very carefully, because a large RSU value can ultimately
cause system performance problems and degradation.
System programmer response: Ensure that an appropriate RSU value is specified. For information about valid
specification of the RSU parameter, see z/OS MVS Initialization and Tuning Reference. For information about how to
choose the correct RSU value, see RSU Parameter Specification section and Specifying the RSU parameter section in
z/OS MVS System Commands.
Source: Real storage manager (RSM)
Detecting Module: IAXMT
Routing Code: 1

Chapter 9. IAR messages 145

 IAR028I • IAR030I

Descriptor Code: 12

IAR028I THE LFAREA SPECIFICATION RESULTED IN xxxxxxxx 1MB PAGES BEING RESERVED IN THE
LARGE FRAME AREA
Explanation: The LFAREA parameter was specified and resulted in the specified number of 1 MB pages to be
reserved in the large frame area.
In the message text:
xxxxxxxx
The number of 1 MB pages to be reserved.
System action: The system continues processing.
Operator response: None.
System programmer response: Use the information in this message to verify that the correct IEASYSxx member is
in use. If the LFAREA size is not what is desired, IPL z/OS with a corrected IEASYSxx member. For IEASYSxx, see
z/OS MVS Initialization and Tuning Reference.
Source: Real storage manager (RSM)
Detecting Module: IAXMT
Routing Code: 1
Descriptor Code: 12

| IAR029I RSU VALUE IS NOT VALID

| Explanation: The RSU specification is not a valid value.
| System action: The system continues and issues message IEA341A, which prompts for reentry of RSU.
| Operator response: Contact the system programmer for a valid RSU specification to enter at the prompt.
| System programmer response: Provide a valid RSU specification to enter at the prompt.
| Source: Real storage manager (RSM)
| Detecting Module: IAXMT
| Routing Code: 1
| Descriptor Code: 12

| IAR030I PAGESCM VALUE IS NOT VALID – AT THE FOLLOWING PROMPT RESPECIFY OR PRESS
| ENTER FOR PAGESCM=ALL.
| Explanation: The value specified for the PAGESCM parameter is not valid.
| System action: The PAGESCM value is not accepted. The system issues message IEA341A to prompt for a new
| PAGESCM value.
| Operator response: Reply with a valid PAGESCM value, or press Enter to use the default PAGESCM=ALL value.
| System programmer response: Determine the PAGESCM value to use.
| Source: Real storage manager (RSM)
| Detecting Module: IAXMT
| Routing Code: 1
| Descriptor Code: 12

146 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAR031I • IAR033I

| IAR031I USE OF STORAGE-CLASS MEMORY FOR PAGING IS ENABLED – PAGESCM=nnnnnnnnM |

| ALL, ONLINE=nnnnnnnnM
| Explanation: The system has successfully performed the initialization and setup required to use storage-class
| memory (SCM) for paging. The PAGESCM value displayed is the amount of SCM that was requested (or defaulted
| to) via the PAGESCM IEASYSxx parmlib parameter (in megabytes). The ONLINE value displayed is the amount of
| SCM that is available to the system (in megabytes).
| System action: The system continues processing. SCM will be used for paging in addition to the paging data sets
| that are also defined.
| Operator response: None.
| System programmer response: None.
| Source: Real storage manager (RSM)
| Detecting Module: IAXBI
| Routing Code: 2
| Descriptor Code: 4

| IAR032I USE OF STORAGE-CLASS MEMORY FOR PAGING IS NOT ENABLED – reason

| Explanation: Use of storage-class memory (SCM) was requested via the PAGESCM parameter, or the presence of
| SCM was detected on this system. However, the system did not enable the use of SCM for paging.
| In the message text, reason indicates why SCM was not enabled:
| PAGESCM = NONE
| NONE was specified for the PAGESCM parameter.
| SCM NOT SUPPORTED
| This system does not support the use of SCM.
| SCM NOT DEFINED
| This system supports the use of SCM, but SCM was not detected on this system.
| UNEXPECTED ERROR
| An unexpected error was encountered while initializing SCM. Message IAR033I provides additional error
| and diagnosis information.
| System action: System initialization continues. SCM will not be used for paging.
| Operator response: None.
| System programmer response: None.
| Source: Real storage manager (RSM)
| Detecting Module: IAXBI
| Routing Code: 2,10
| Descriptor Code: 4

| IAR033I RSM INVOCATION OF servicename SERVICE FAILED – RC=retcode, RSN=rsncode, DIAG1=diaginfo1,

| DIAG2=diaginfo2
| Explanation: An error or unexpected condition was encountered while the system was performing the initialization
| required to use storage-class memory (SCM) for paging. This message is followed by message IAR031I or IAR032I,
| depending on whether SCM will be used for paging.
| In the message text:
| servicename
| The service that encountered the error.
| retcode The hexadecimal return code provided by the service.

Chapter 9. IAR messages 147

 IAR034I • IAR036W

| rsncode The hexadecimal reason code provided by the service.

| diaginfo1, diaginfo2
| Internal diagnostic information associated with the error.
| System action: System processing continues.
| Operator response: Notify the system programmer.
| System programmer response: Contact the IBM Support Center with the messages issued by the system during the
| IPL.
| Source: Real storage manager (RSM)
| Detecting Module: IAXBI
| Routing Code: 2,10
| Descriptor Code: 4

| IAR034I ADDITIONAL STORAGE-CLASS MEMORY DETECTED

| Explanation: The system determined that additional storage-class memory (SCM) has been defined to the system.
| System action: None.
| Operator response: None.
| System programmer response: Issue the CONFIG SCM ONLINE command to make this additional storage-class
| memory (SCM) available for system use.
| Source: Real storage manager (RSM)
| Detecting Module: IAXBE
| Routing Code: 2
| Descriptor Code: 4

| IAR035I PERMANENT ERROR DETECTED IN STORAGE-CLASS MEMORY. ADDR=aaaaaaaa_aaaaaaaa

| Explanation: The system determined that a portion of storage-class memory (SCM) that is in use for paging has
| entered the permanent error state. The starting address of the SCM increment that has entered the permanent error
| state is aaaaaaaa_aaaaaaaa.
| System action: The system will not use the indicated increment of storage-class memory (SCM) for subsequent
| paging requests. References to pages already written to this SCM increment will result in a 028 abend.
| Operator response: Contact the system programmer.
| System programmer response: This message is an indication of a storage-class memory (SCM) hardware error.
| Contact IBM service for additional problem assistance.
| Source: Real storage manager (RSM)
| Detecting Module: IAXBB
| Routing Code: 2, 10
| Descriptor Code: 4

| IAR036W STORAGE-CLASS MEMORY IS REQUIRED WHEN *NONE* IS SPECIFIED ON THE PAGE=

| PARAMETER
| Explanation: *NONE* was specified for the first or second data set (or both) for the PAGE= parameter, but no
| storage-class memory (SCM) is available for paging.
| System action: The system enters wait state X'A2D'.
| Operator response: Refer to the operator response for wait state X'A2D'.
| System programmer response: Refer to the system programmer response for wait state X'A2D'.

148 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAR037A • IAR040I

| Source: Real storage manager (RSM)

| Detecting Module: IAXBI
| Routing Code: 2
| Descriptor Code: 1

| IAR037A xxxxxxxxM OF STORAGE-CLASS MEMORY (SCM) IN ERROR. REPLY C TO CONTINUE THE IPL
| WITH yyyyyyyyM SCM ONLINE.
| Explanation: The system determined that a portion of storage-class memory (SCM) is in the permanent error state.
| The SCM in error cannot be used for paging and was left logically offline. xxxxxxxxM is the amount of SCM that was
| found to be in the permanent error state. yyyyyyyyM is the amount of SCM that was brought online and is available
| for paging.
| System action: The system waits for confirmation to continue the IPL.
| Operator response: Check with the system programmer.
| System programmer response: Determine if there is enough paging space for the system to function. The paging
| space is the amount of SCM that is online, plus any paging data sets. If sufficient paging space exists, then reply C to
| let the system IPL normally. Otherwise, add more SCM or page data sets and then IPL the system.
| Source: Real storage manager (RSM)
| Detecting Module: IAXBI
| Routing Code: 1
| Descriptor Code: 2

| IAR040I REAL STORAGE AMOUNTS:

| TOTAL AVAILABLE ONLINE: xxx [M|G|T]

| LFAREA LIMIT FOR xM, xG, OR xT: xxx [M|G|T] | [0 (not supported)]
| LFAREA LIMIT FOR SUM OF 1M= AND 2G=: xxx[ M | G | T ] | [0 (not supported)]
| LFAREA LIMIT FOR 2GB PAGES FOR 2G= : [xxxxxxx] | [0 (not supported) ]
| Explanation: This is an informational message that describes certain views of storage that pertain to the sysparm
| LFAREA specification:
| TOTAL AVAILABLE ONLINE
| The amount of available online storage located at IPL, which is used to calculate each of the following
| limits.
| LFAREA LIMIT FOR xM, xG, OR xT
| The system limit used when xM, xG, or xT syntax is used for the LFAREA specification. This limit
| calculation is: [(80% of the total available online storage at IPL) minus 2G]. If the EDAT facility is not
| installed, 0 (not supported) is displayed.
| LIMIT FOR SUM OF 1M= AND 2G=
| The system limit used when 1M= and 2G= syntax is used for the LFAREA specification. This limit
| calculation is: [80% of (the total available online storage at IPL minus 4G)]. If the EDAT facility is not
| installed, 0 (not supported) is displayed.
| LFAREA LIMIT FOR 2GB PAGES FOR 2G=
| The limit of the number of 2GB pages that were found that could be specified for the 2G= subparameter on
| the LFAREA specification, provided the sum of 1M= and 2G= remains at or below the LIMIT FOR SUM OF
| 1M= AND 2G=. If the EDAT facility 2 is not installed, 0 (not supported) is displayed. Each 2GB page must
| reside in 2GB of contiguous storage starting on a 2GB boundary. If online storage is fragmented with offline
| increments such that there are gaps that prevent 2GB areas of contiguous storage on a 2GB boundary from
| being found, there can be fewer 2GB pages than the system limit would suggest.

| Note: This message is issued regardless of whether the LFAREA parameter was specified.
| System action: The IPL continues.

Chapter 9. IAR messages 149

 IAR041I • IAR042I

| Operator response: None.

| System programmer response: This message helps you determine the amounts of storage available for the large
| frame area, particularly if the amounts requested with the LFAREA parameter are not reflected in the IAR048I
| message. If the number of 2GB pages are fewer than expected, determine whether the storage is fragmented by
| offline storage increments.
| Source: Real storage manager (RSM)
| Detecting Module: IAXMT
| Routing Code: 1
| Descriptor Code: 12

| IAR041I LFAREA=(specification) WAS SPECIFIED BUT [2GB PAGE SUPPORT | 1MB PAGE SUPPORT IS
| AND 2GB PAGE SUPPORT ARE] NOT AVAILABLE.
| Explanation: The LFAREA parameter was specified using xM, xG, xT, or x% syntax or 1M= or 2G= syntax, but the
| required hardware support is not available.
| System action: If xM, xG, xT, or x% syntax was specified, the LFAREA specification is ignored and zero 1MB and
| zero 2GB pages are reserved in the large frame area.
| If 1M= or 2G= syntax was specified:
| v If a minimum amount of zero was specified for the page size or sizes that are not supported (for example,
| LFAREA=(1M=(4096,0),2G=(8,0)) or LFAREA=(1M=(4096,0),2G=(0) ), no pages are reserved in the large frame area
| for the unsupported page size or sizes and the IPL continues.
| v If a nonzero minimum amount was specified for the page size or sizes that are not supported (for example,
| LFAREA=(1M=(4096,1024),2G=(8,2)) or LFAREA=(1M=4096),2G=(8)) ), and PROMPT was specified explicitly or by
| default, the system prompts for reentry of the LFAREA parameter.
| v If a nonzero minimum amount was specified for the page size or sizes that are not supported, and NOPROMPT
| was specified, the LFAREA specification is ignored and zero 1MB and zero 2GB pages are reserved in the large
| frame area.
| Operator response: Ensure that the correct IEASYSxx member is used for this IPL. If the correct IEASYSxx member
| is used, but sufficient storage is not available, contact your system programmer.
| System programmer response: If 1MB or 2GB pages are required, ensure that the required hardware support is
| installed. Using 1MB pages requires installation of the enhanced DAT facility. Using 2GB pages requires installation
| of the enhanced DAT facility 2.
| Source: Real storage manager (RSM)
| Detecting Module: IAXMT
| Routing Code: 1
| Descriptor Code: 12

| IAR042I LFAREA=(specification) WAS SPECIFIED WHICH RESULTS IN A REQUEST FOR ZERO 1MB AND
| ZERO 2GB PAGES.
| Explanation: The LFAREA parameter specified a nonzero percentage, which resulted in a request for zero 1MB and
| zero 2GB pages. This can occur if the specified percentage is small, or if there is a small or insufficient amount of
| available online storage. If xM, xG, xT, or x% syntax is specified, a percentage request is calculated by first
| multiplying the percentage by the online real storage, and then subtracting 2G: (percentage * online real storage) – 2G.
| However, if 1M= or 2G= syntax is specified, a percentage request is calculated by first subtracting 4G from the online
| real storage, and then multiplying that by the percentage: (online real storage – 4G) * percentage. The result is then
| rounded down to the nearest respective 1MB or 2GB page boundary, which could result in a zero value.
| For example, on a 13G system, a request for LFAREA=(2G=10%) is calculated as 0.10 * (13G – 4G) = 0.9G, which
| rounded down to the nearest 2G page boundary becomes zero. In this example, a request for at least 23% is required
| to reserve at least one page, which is calculated as 0.23 * (13G – 4G) = 2.07G which is then rounded down to 2G. This
| message is issued when either a nonzero target percentage or a nonzero minimum percentage results in a request for
| zero target or zero minimum pages.

150 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAR043I

| System action: The system issues message IAR045I for each area with the amount of available storage and the
| minimum percentage required for at least one page. In addition, the system responds as follows if a nonzero
| percentage results in a request for zero pages because of insufficient storage:
| v If xM, xG, xT, or x% syntax was specified, the system reserves zero 1MB and zero 2G= pages and continues the
| IPL.
| v If 1M= or 2G= syntax was specified:
| – If PROMPT was specified, either explicitly or by default, the system prompts for reentry of the LFAREA
| parameter.
| – If NOPROMPT was specified, the LFAREA specification is ignored and zero 1MB or 2GB pages are reserved in
| the large frame area and IPL continues.
| Operator response: Ensure that the correct IEASYSxx member is used for this IPL. If the correct IEASYSxx member
| is used, but sufficient storage is not available, contact your system programmer.
| System programmer response: If 1MB or 2GB pages are required, ensure that enough storage is installed for the
| z/OS image and that the requested percentage is large enough to reserve the intended number of pages.
| Source: Real storage manager (RSM)
| Detecting Module: IAXMT
| Routing Code: 1
| Descriptor Code: 12

| IAR043I LFAREA=(specification) WAS SPECIFIED WHICH TOTALS [xxxxxxxM | xxxxG | xT] AND EXCEEDS
| THE SYSTEM LIMIT OF [yyyyyyyM | yyyyG | yT].
| Explanation: The LFAREA parameter specified for real storage to be reserved in the large frame area for 1MB or
| 2GB pages, but the request exceeds the system limit. If xM, xG, xT, or x% syntax is specified, the percentage request
| is calculated by first multiplying the percentage by the online real storage, and then subtracting 2G: (percentage *
| online real storage) – 2G. If 1M= or 2G= syntax is specified, the percentage request is calculated by first subtracting 4G
| from the online real storage, and then multiplying that by the percentage: (online real storage – 4G) * percentage. For
| 1M= and 2G= syntax, when both a target and a minimum amount are provided, the minimum amount is applied
| toward the limit and is used in the total amount indicated.
| System action: The system issues message IAR045I with the amount of available storage. In addition, the system
| responds as follows if a nonzero percentage results in a request for zero pages because of insufficient storage:
| v If xM, xG, xT, or x% syntax was specified, the system prompts for reentry of the LFAREA parameter.
| v If 1M= or 2G= syntax was specified:
| – If PROMPT was specified, either explicitly or by default, the system prompts for reentry of the LFAREA
| parameter.
| – If NOPROMPT was specified, the LFAREA specification is ignored and zero 1MB and zero 2GB pages are
| reserved in the large frame area and IPL continues.
| Operator response: Ensure that the correct IEASYSxx member is used for this IPL. If the correct IEASYSxx member
| is used, but sufficient storage is not available, contact your system programmer.
| System programmer response: If 1MB or 2GB pages are required, ensure that enough storage is installed for the
| z/OS image such that the requested amount of storage is not over the limit. Refer to the output of message IAR040I
| for the system limits.
| Source: Real storage manager (RSM)
| Detecting Module: IAXMT
| Routing Code: 1
| Descriptor Code: 12

Chapter 9. IAR messages 151

 IAR044I • IAR045I

| IAR044I LFAREA=(specification) WAS SPECIFIED WHICH EXCEEDS THE AMOUNT AVAILABLE IN THE
| LARGE FRAME AREA.
| Explanation: The LFAREA parameter specified for real storage to be reserved in the large frame area for 1MB or
| 2GB pages, but the request exceeds the online storage that is available for the large frame area. If the total amount of
| online real storage appears to be sufficient, storage fragmentation caused by offline storage can result in an
| insufficient number of 2GB pages being formed. For 1M= or 2G= syntax, when both a target and a minimum amount
| are provided, the minimum amount is compared against the available amount.
| System action: The system issues message IAR045I with the amount of available storage:
| v If xM, xG, xT, or x% syntax was specified, the system attempts to satisfy the request at a lesser amount and
| continue the IPL.
| v If 1M= or 2G= syntax was specified:
| – If PROMPT was specified, either explicitly or by default, the system prompts for reentry of the LFAREA
| parameter.
| – If NOPROMPT was specified, the LFAREA specification is ignored and zero 1MB and zero 2GB pages are
| reserved in the large frame area and IPL continues.
| Operator response: Ensure that the correct IEASYSxx member is used for this IPL. If the correct IEASYSxx member
| is used, but sufficient storage is not available, contact your system programmer.
| System programmer response: If 1MB or 2GB pages are required, ensure that enough contiguous storage is installed
| for the z/OS image. Refer to the output of message IAR040I for the number of 2GB pages that can be reserved.
| Source: Real storage manager (RSM)
| Detecting Module: IAXMT
| Routing Code: 1
| Descriptor Code: 12

| IAR045I VALID RANGE FOR LFAREA [xM, xG, xT | 1M= | 2G=] IS 0[M] TO xxxxxxx[M], OR 0% TO xx%.
| A MINIMUM OF yy% MUST BE SPECIFIED TO RESERVE AT LEAST ONE [1MB | 2GB] PAGE.
| Explanation: This message is issued after an error is detected in the LFAREA specification. This message is issued
| three times:
| 1. Once for 1MB pages using xM, xG, xT, or x% syntax.
| 2. Once for 1MB pages using 1M= syntax.
| 3. Once for 2GB pages using 2G= syntax.

| The message describes the valid values or ranges that can be specified for the 1MB and 2GB pages, and the
| minimum percentage that must be specified to reserve at least one 1MB or one 2GB page. The values indicate the
| amounts that can be specified as if only 1MB pages or only 2GB pages will be requested; when both 1MB and 2GB
| pages are requested, the sum of the requested amounts must not exceed the system limit.

| If the xM, xG, xT, or x% syntax is used, the system limit is calculated by first taking 80% of the online real storage at
| IPL, and then subtracting 2G: (80% * online real storage at IPL) - 2G. If the 1M= and 2G= syntax is used, the system
| limit is calculated by first subtracting 4G from the online real storage at IPL, and then multiplying that by 80%:
| (online real storage at IPL – 4GB) * 80%. Message IAR043I is issued if the requested amount is greater than the system
| limit.

| The range of percentages is included to reflect the valid range of pages, but there can be percentage values within the
| range that are between pages or less than a full page. Percentage requests are rounded down to the nearest 1MB or
| 2GB page boundary, which results in a request for zero pages if the calculation is less than one page. The minimum
| percentage required to reserve at least one page is provided in this message. Message IAR042I is issued if the
| requested percentage is not enough to reserve at least one page.

| A valid value of zero is indicated when the required hardware support is not available, or when there is not enough
| storage available for the large frame area, which is typically a result of fragmentation caused by offline storage.
| System action: The system continues and might prompt for reentry of the LFAREA value, depending on the error

152 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAR046I • IAR047I

| and whether the LFAREA specification allows a reentry prompt.

| Operator response: Inform the system programmer of the valid values or ranges that can be used for a reentering
| the LFAREA parameter.
| System programmer response: Use the provided values to determine whether the LFAREA specification has to be
| changed, or whether additional real storage has to be configured online. Refer to message IAR040I for additional
| information regarding storage amounts, system limits, and whether hardware support is available.
| Source: Real storage manager (RSM)
| Detecting Module: IAXMT
| Routing Code: 1
| Descriptor Code: 12

| IAR046I LFAREA=(specification) WAS SPECIFIED WHICH IS NOT VALID. REASON:

| [VALUE EXCEEDS MAXIMUM NUMBER OF DIGITS.]

| [MINIMUM VALUE GREATER THAN TARGET VALUE.]
| [MISSING EXPECTED VALUE.]
| [EXTRANEOUS CHARACTERS DETECTED.]
| [DUPLICATE KEYWORDS OR SPECIFICATIONS DETECTED.]
| [MUTUALLY EXCLUSIVE KEYWORDS OR VALUES DETECTED.]
| [MISSING MULTIPLIER M, G, OR T.]
| [UNRECOGNIZED SPECIFICATION.]
| [NON-NUMERIC DETECTED WHERE NUMERIC EXPECTED.]
| [PERCENTAGE WITH NON-PERCENTAGE IN SAME KEYWORD.]
| [REQUEST WITH PERCENTAGE EXCEEDS SYSTEM LIMIT.]
| Explanation: A syntax or specification error was detected with the LFAREA specification. The reason text describes
| the first error that was detected. There can be additional errors with the specification.
| System action: Message IAR047I is issued, followed by a prompt for reentry of the LFAREA.
| Operator response: When prompted, enter a valid LFAREA parameter
| System programmer response: Ensure that LFAREA is specified correctly. Refer to z/OS MVS Initialization and
| Tuning Reference for details on specifying the LFAREA parameter.
| Source: Real storage manager (RSM)
| Detecting Module: IAXMT
| Routing Code: 1
| Descriptor Code: 12

| IAR047I AT THE FOLLOWING PROMPT, SPECIFY THE COMPLETE LFAREA PARAMETER OR PRESS
| ENTER FOR ZERO 1MB AND ZERO 2GB PAGES
| Explanation: The LFAREA specification has one or more errors and the system will prompt for reentry of the
| LFAREA parmater. If the ENTER key is pressed instead of reentering the LFAREA specification, the system will
| reserve zero 1MB and zero 2GB pages.
| System action: The system continues and issues message IEA341A to prompt for reentry of the LFAREA parameter.
| Operator response: Contact the system programmer for a valid LFAREA specification to reenter.
| System programmer response: Provide a valid LFAREA specification when prompted. The LFAREA specification
| must include 1M= and 2G= if 1MB and 2G= pages are required. If no 1MB or 2G= pages are required, a specification
| of LFAREA=(1M=0,2G=0) provides a clear record of that intent. Refer to z/OS MVS Initialization and Tuning Reference
| for details on specifying the LFAREA parameter.
| Source: Real storage manager (RSM)
| Detecting Module: IAXMT

Chapter 9. IAR messages 153

 IAR048I

| Routing Code: 1
| Descriptor Code: 12

| IAR048I [LFAREA=(specification) WAS PROCESSED | LFAREA WAS NOT SPECIFIED | LFAREA WAS
| CANCELED] WHICH RESULTED IN xxxxxxx 1MB PAGE[S] AND yyyyyyy 2GB PAGE[S] [.
| REQUEST REDUCED DUE TO: | DUE TO: NOPROMPT SPECIFIED AND]

| [INSUFFICIENT STORAGE.]
| [OVER SYSTEM LIMIT.]
| [NO HARDWARE SUPPORT.]
| [INSUFFICIENT STORAGE AND OVER SYSTEM LIMIT.]
| [INSUFFICIENT STORAGE AND NO HARDWARE SUPPORT.]
| [OVER SYSTEM LIMIT AND NO HARDWARE SUPPORT.]
| Explanation: The LFAREA parameter was correctly specified, or was not specified, or was canceled and which
| resulted in the indicated number of 1MB and 2GB pages being reserved in the large frame area. The additional text is
| provided when the indicated conditions resulted in a reduced amount or zero pages. pages.
| System action: The system continues. If 1MB or 2GB pages were reserved in the large frame area, these pages are
| available for use.
| Operator response: None.
| System programmer response: Review this message to determine whether the intended number of 1MB and 2GB
| pages were reserved. Refer to the output of message IAR040I to determine whether the online storage at IPL is as
| expected.
| Source: Real storage manager (RSM)
| Detecting Module: IAXMT
| Routing Code: 1
| Descriptor Code: 12

154 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Chapter 10. IARH messages
IARH100I lowok AFQ Threshold is set correctly. The lowok Available Frame Queue threshold is currently set to
current frames. This satisfies the checkowner_or_installation specified minimum value of specified
frames.
Explanation: n/a
System action: n/a
Operator response: n/a
System programmer response: n/a
Problem determination: n/a
Source: n/a
Reference Documentation: n/a
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH100E lowok AFQ Threshold Value is Too Low

Explanation: The lowok Available Frame Queue threshold is currently set to current frames. This is lower than the
checkowner_or_installation specified minimum value of specified frames.
System action: n/a
Operator response: Please report this problem to the system programmer.
System programmer response: Review the member setting in the IEAOPTxx member of PARMLIB, and issue a set
OPT=xx command at the system console as required.
Problem determination: n/a
Source: Real Storage Manager
Reference Documentation: z/OS MVS Initialization and Tuning Reference
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH101I No V=R storage has been defined in this system. This is the IBM suggestion if no V=R jobs will be
executed.
Explanation: n/a
System action: n/a
Operator response: n/a
System programmer response: n/a
Problem determination: n/a
Source: n/a

© Copyright IBM Corp. 1988, 2012 155

IARH101E • IARH102E

Reference Documentation: n/a

Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH101E V=R Storage is Defined

Explanation: V=R storage has been defined on this system. If no jobs will be executed that require V=R storage,
IBM suggests that no V=R storage be defined.
System action: n/a
Operator response: Please report this problem to the system programmer.
System programmer response: If no V=R jobs will be run, set REAL=0 and VRREGN=0 in the IEASYSxx member of
PARMLIB before the next IPL. Please note that REAL=0 must be explicitly specified to remove V=R regions. If the
REAL parameter is not coded, a default value will be assigned.
Problem determination: n/a
Source: Real Storage Manager
Reference Documentation: z/OS MVS Initialization and Tuning Reference
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH102I No reconfigurable storage (RSU) has been defined on this system. This is the IBM suggestion if
storage is not required to be reconfigurable.
Explanation: n/a
System action: n/a
Operator response: n/a
System programmer response: n/a
Problem determination: n/a
Source: n/a
Reference Documentation: n/a
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH102E Reconfigurable storage is Defined

Explanation: Reconfigurable storage (RSU) has been defined on this system. If storage is not required to be
reconfigurable, then IBM recommends that no RSU be defined.
System action: n/a
Operator response: Please report this problem to the system programmer.
System programmer response: Set RSU=0 in the IEASYSxx member of PARMLIB before the next IPL.
Problem determination: n/a

156 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IARH108I • IARH108E

Source: Real Storage Manager

Reference Documentation: z/OS MVS Initialization and Tuning Reference
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH108I The current number of in use CADS entries is current, which represents pct% of the total allowed
CADS entries of total. The highest usage of CADS entries during this IPL is hwmpct%, or hwm total
entries. This is below the current checkowner_or_installation supplied threshold of threshold%.
Explanation: n/a
System action: n/a
Operator response: n/a
System programmer response: n/a
Problem determination: n/a
Source: n/a
Reference Documentation: n/a
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH108E CADS Threshold Met or Exceeded

Explanation: The current number of in use CADS entries is current, which represents pct% of the total allowed
CADS entries of total. This usage is at or above the current checkowner_or_installation supplied threshold of threshold%.
The highest usage of CADS entries during this IPL is hwmpct%, or hwm total entries.
Once the limit of total entries has been reached, no more common area dataspaces may be created. This may
adversely affect starting new jobs, or the continued operation of jobs already running.
System action: n/a
Operator response: Please report this problem to the system programmer.
| System programmer response: Verify the setting of the MAXCAD parameter in IEASYSxx. Changes to this value
will require an IPL to become effective.
Problem determination: n/a
Source: Real Storage Manager
Reference Documentation: z/OS MVS Initialization and Tuning Reference
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

Chapter 10. IARH messages 157

IARH109I • IARH110I

IARH109I The current setting of MEMLIMIT in SMFPRMxx is current bytes. For more information on this
value, consult z/OS MVS Initialization and Tuning Reference.
Explanation: n/a
System action: n/a
Operator response: n/a
System programmer response: n/a
Problem determination: n/a
Source: n/a
Reference Documentation: n/a
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH109E MEMLIMIT msg

Explanation: Currently, the MEMLIMIT setting in SMFPRMxx memlim.
Setting MEMLIMIT too low may cause jobs that rely on high virtual storage to fail. Setting MEMLIMIT too high may
cause over-commitment of real storage resources and lead to performance degradation or system loss.
System action: n/a
Operator response: Please report this problem to the system programmer.
System programmer response: An application programmer should consider coding the MEMLIMIT option on the
EXEC JCL card for any job that requires high virtual storage. This will provide job specific control over high virtual
storage limits. You may also want to consider using the IEFUSI exit. Finally, consider setting a system wide default
for MEMLIMIT in SMFPRMxx. Consult the listed sources for more information.
Problem determination: n/a
Source: Real Storage Manager
Reference Documentation: z/OS MVS Initialization and Tuning Reference
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH110I The current setting of HVSHARE in IEASYSxx is current bytes. This matches the
checkowner_or_installation suggested value of HVSHARE. pct% of the high virtual shared area is
currently allocated. The highest allocation during this IPL has been hwmpct%, or hwm. A warning
will be generated if the allocation of shared high virtual surpasses threshold%.
Explanation: n/a
System action: n/a
Operator response: n/a
System programmer response: n/a
Problem determination: n/a
Source: n/a
Reference Documentation: n/a

158 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IARH110E • IARH501L

Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH110E HVSHARE msg

Explanation: The current setting of HVSHARE in IEASYSxx is current bytes. This is moreless than the
checkowner_or_installation suggested value of default bytes.
The current allocation of shared high virtual storage is pct%, or current bytes. This is atabovebelow the
checkowner_or_installation supplied threshold of threshold% for shared high virtual storage allocation.
The HVSHARE setting controls the size of the shared area above 2G, directly affecting how much high virtual
storage may be shared by jobs active on the system. Setting this value too low may cause jobs relying on shared high
virtual storage to fail.
System action: n/a
Operator response: Please report this problem to the system programmer.
System programmer response: Verify the setting of HVSHARE in IEASYSxx. Changes to this value will require an
IPL to become effective.
Problem determination: n/a
Source: Real Storage Manager
Reference Documentation: z/OS MVS Initialization and Tuning Reference
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH500L check_name module debugstr Entry Code: entrycode Function Code: functioncode
Explanation: check_owner error detected.
System action: n/a
Operator response: n/a
System programmer response: n/a
Problem determination: n/a
Source: n/a
Reference Documentation: n/a
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH501L A failure was detected by modname, service RC: retcode RSN: reason
Explanation: An internal error occurred. Contact the owner for problem assistance.
System action: n/a
Operator response: n/a
System programmer response: n/a

Chapter 10. IARH messages 159

IARH502L • IARH900I

Problem determination: n/a

Source: n/a
Reference Documentation: n/a
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH502L check_name was entered with unexpected checker function code. Entry Code entry code, Function code
function code.
Explanation: An internal error occurred. Contact the owner for problem assistance.
System action: n/a
Operator response: n/a
System programmer response: n/a
Problem determination: n/a
Source: n/a
Reference Documentation: n/a
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH503L check_name was entered with unexpected checker entry code. Entry Code entry code, Function code
function code.
Explanation: An internal error occurred. Contact the owner for problem assistance.
System action: n/a
Operator response: n/a
System programmer response: n/a
Problem determination: n/a
Source: n/a
Reference Documentation: n/a
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH900I check_name cannot be processed because a parameter error was detected.

Explanation: n/a
System action: n/a
Operator response: n/a
System programmer response: n/a

160 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IARH901I

Problem determination: n/a

Source: n/a
Reference Documentation: n/a
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

IARH901I

The current parameters are:

active_check_parameters
A problem was detected while
processing the
keyword parameter. The error is:
error

Parameters should be specified in the form keyword(value) or keyword=value with multiple

parameters being separated by commas. The keyword for this parameter is key2. If you are not using
keywords, then you may specify the parameters positionally. In this case, this value only needs to
be in position pos. Consult the IBM Health Checker for z/OS User Guide for details on the
parameters expected by this check.
Explanation: n/a
System action: n/a
Operator response: n/a
System programmer response: n/a
Problem determination: n/a
Source: n/a
Reference Documentation: n/a
Automation: n/a
Detecting Module: RSM
Routing Code: n/a
Descriptor Code: n/a

Chapter 10. IARH messages 161

162 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)
Chapter 11. IAZ messages
IAZ0001I server_name Name token retrieval service failed, rc: rc
Explanation: The NETSERV initialization failed while trying to retrieve the name token.
In the message text:
server_name
The NJETCP server name.
rc The return code from the name token retrieval service.
System action: The NETSERV is terminated with an X'EC8' abend. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV server initialization
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0002I server_name TCT address not valid in name token

Explanation: The NETSERV initialization could not be completed because of a name token retrieval service failure.
In the message text:
server_name
The NJETCP server name.
System action: The NETSERV is terminated with an X'EC8' abend. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV server initialization
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0003I server_name Storage for IAZCMTCB data area could not be obtained
Explanation: The NETSERV initialization could not complete because storage could not be obtained for the MTCB.
In the message text:
server_name
The NJETCP server name.
System action: The NETSERV is terminated with an X'EC8' abend. The system writes an abend dump.
Operator response: Try to start the NETSERV again. If the problem persists, notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV server initialization

© Copyright IBM Corp. 1988, 2012 163

IAZ0004I • IAZ0006I

Detecting Module: IAZNJTCP

Routing Code: 8, 43
Descriptor Code: 4

IAZ0004I server_name Client ID could not be obtained for NETSERV server, rc:rc
Explanation: The NETSERV initialization could not be completed because the server task could not retrieve a client
id from TCP/IP. This message is preceded by message IAZ0545I, which provides additional diagnosis information.
In the message text:
server_name
The NJETCP server name.
rc The error value from the __getclientid() service.
System action: The NETSERV is terminated with an X'EC8' abend. The system writes an abend dump.
Operator response: Try to start the NETSERV again. If the problem persists, notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV server initialization
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0005I server_name TCB address not valid in socket chain element

Explanation: An error has occurred while detaching the socket subtasks in the NETSERV main task.
In the message text:
server_name
The NJETCP server name.
System action: The NETSERV is terminated with an X'EC8' abend. The system writes an abend dump.
Operator response: Try to start the NETSERV again. If the problem persists, notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0006I server_name Socket chain could not be created for the NETSERV server
Explanation: The NETSERV initialization failed.
In the message text:
server_name
The NJETCP server name.
System action: The NETSERV is terminated with an X'EC8' abend. The system writes an abend dump.
Operator response: Try to start the NETSERV again. If the problem persists, notify the system programmer.
System programmer response: Try to restart the server. If the problem persists, obtain the X'EC8' abend dump and
other relevant documentation, and contact the IBM Support Center.

164 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0007I • IAZ0009I

Source: NETSERV server initialization

Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0007I server_name Socket chain trailer not valid in IAZCMTCB

Explanation: An internal error was detected while processing a socket chain.
In the message text:
server_name
The NJETCP server name.
System action: The NETSERV is terminated with an X'EC8' abend. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV socket initialization
Detecting Module: IAZNJTCP, IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0008I server_name device_name Transmitter/Receiver RCB values not valid in IAZYTSCT

Explanation: The socket connection could not be initialized because of an incorrect combination of Transmitter and
Receiver sub-devices specified for the connection.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or the socket name if the device name does not exist.
System action: The X'EC8' abend is issued after the message and the corresponding socket connection is terminated.
The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV socket initialization
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0009I server_name device_name SCB value found not valid while decompressing NJE data
Explanation: The decompression routine on the receiving side of the connection encountered an error while
decompressing received data on the socket.
In the message text:
server_name
The NJETCP server name.

Chapter 11. IAZ messages 165

IAZ0010I • IAZ0011I

device_name
The device name associated with the socket, or the socket name if the device name does not exist.
System action: The X'EC8' abend is issued after the message and the corresponding socket connection is terminated.
The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV processing
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0010I server_name device_name Transmitter issued a Terminate and ABEND link command
Explanation: The transmitter sub-device has detected an error and requested that the socket connection be
terminated.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or the socket name if the device name does not exist.
System action: The X'EC8' abend with is issued after the message and the corresponding socket connection is
terminated. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center. JES2 ($HASP) or JES3 (IAT) messages preceding this message might be useful for problem
determination.
Source: Data transmission on the socket
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0011I server_name device_name Receiver issued a Terminate and ABEND link command
Explanation: An error was detected in the data passed to a JES specific processing routine associated with sending
or receiving data for a sub-device. The processing routine requested that the socket connection be terminated and
that a dump be taken.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or the socket name if the device name does not exist.
System action: The X'EC8' abend with is issued after the message and the corresponding socket connection is
terminated. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center. JES2 ($HASP) or JES3 (IAT) messages preceding this message might be useful for problem
determination.

166 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0012I • IAZ0014I

Source: Data reception on the socket

Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0012I server_name device_name NRQ chain element not valid in socket NRQ chain
Explanation: An internal error occurred processing the NRQ chain.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or the socket name if the device name does not exist.
System action: The X'EC8' abend with is issued after the message and the corresponding socket connection is
terminated. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: Process NRQ chain for the connection
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0013I server_name device_name Attempt to send Job data on the transmitter before the stream is active
Explanation: The transmitter sub-device attempted to send NJE data on the socket connection while it was not in an
active state.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or the socket name if the device name does not exist.
System action: The X'EC8' abend is issued after the message and the corresponding socket connection is terminated.
The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: Process NRQ chain for the connection
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0014I server_name device_name Transmitter buffer status not marked inprogress when being sent to TCP/IP
Explanation: An internal error occurred while attempting to send data on the TCP/IP socket connection.
In the message text:

Chapter 11. IAZ messages 167

IAZ0015I • IAZ0016I

server_name
The NJETCP server name.
device_name
The device name associated with the socket, or the socket name if the device name does not exist.
System action: The X'EC8' abend is issued after the message and the corresponding socket connection is terminated.
The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: Data transmission on the socket connection
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0015I server_name IAZCMTST pointer not valid in socket subtask parameter list
Explanation: The address of the IAZCMTST data area passed to the socket connection subtask from the NETSERV
server main task in its parameter list is corrupted.
In the message text:
server_name
The NJETCP server name.
System action: The X'EC8' abend is issued after the message and the corresponding socket connection is terminated.
The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV socket initialization
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0016I server_name Storage not obtained for socket chain element

Explanation: A storage shortage condition exists. The NETSERV is terminated.
The NETSERV address space limits the number of connections allowed in a single address space based on the size of
the available private storage region when the address space starts. When installation exits that get control in the
NETSERV address space use significant amounts of private storage or fail to free storage after it is no longer needed,
this condition can result in a storage shortage.
In the message text:
server_name
The NJETCP server name.
System action: The NETSERV is terminated with an X'EC8' abend. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: If the address space only has problems when it has run for a long time and the
number of socket connections remains constant, the problem is most likely to be related to storage leaks. Examine the
dump for storage leaks associated with data areas obtained in installation exits. If the problem appears to be related
to a storage leak in IBM code or the NETSERV allowing more connections than the address space can support, obtain
the X'EC8' abend dump and other relevant documentation, and contact the IBM Support Center.

168 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0017I • IAZ0019I

If the address space only has problems when the level of activity reaches a certain level and the problem goes away
when the number of active sockets is kept low, it is mostly likely that installation exits require significant amounts of
storage. You may need to use an additional NETSERV address space to handle the number of connections.
Source: NETSERV server processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0017I server_name Storage not obtained for IAZCMTST data area

Explanation: A storage shortage condition exists.
In the message text:
server_name
The NJETCP server name.
System action: The NETSERV is terminated with an X'EC8' abend. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV server processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0018I server_name NRQ chain element not valid in Server IAZYTNRQ chain
Explanation: An internal error was encountered processing JES commands.
In the message text:
server_name
The NJETCP server name.
System action: Depending on when the error was encountered, either the socket connection or the NETSERV is
terminated with an X'EC8' abend. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NJETCP server work processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0019I server_name device_name msgtext rc: retcode rsn:rsncode

Explanation: An internal error occurred.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or the socket name if the device name does not exist.

Chapter 11. IAZ messages 169

IAZ0020I

msgtext
One of the following:
v Internal error while resolving IP address of remote peer
v Internal error during NJETCP Signon
v Internal error while transmitting data on socket
v Internal error while receiving data on socket
retcode
Possible return codes, which are as listed in the table:

Value Description
1 JES input validation Error
2 Storage Allocation Error - Storage shortage condition

System action: The X'EC8' abend is issued after the message and the corresponding socket connection is terminated.
The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV socket initialization
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0020I server_name Storage not obtained for IAZYTSCT data area. Connection terminated
Explanation: Private storage for the main data area associated with a socket connection subtask (mapped by
IAZYTSCT) could not be obtained. This probably resulted from a shortage of above the line private storage.
The NETSERV address space limits the number of connections allowed in a single address space based on the size of
the available private storage region when the address space starts. When installation exits that get control in the
NETSERV address space use significant amounts of private storage or fail to free storage after it is no longer needed,
this condition can result in a storage shortage.
In the message text:
server_name
The NJETCP server name.
System action: The NETSERV socket connection is terminated. The X'EC8' abend is issued after the message and the
corresponding socket connection is terminated. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: If the address space only has problems when it has run for a long time and the
number of socket connections remains constant, the problem is most likely to be related to storage leaks. Examine the
dump for storage leaks associated with data areas obtained in installation exits. If the problem appears to be related
to a storage leak in IBM code or the NETSERV allowing more connections than the address space can support, obtain
the X'EC8' abend dump and other relevant documentation, and contact the IBM Support Center.
If the address space only has problems when the level of activity reaches a certain level and the problem goes away
when the number of active sockets is kept low, it is mostly likely that installation exits require significant amounts of
storage. You may need to use an additional NETSERV address space to handle the number of connections.
Source: NETSERV socket initialization
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

170 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0021I • IAZ0023I

IAZ0021I server_name device_name NJETCP Signon error: Record not valid - Expecting DLE ACK0
Explanation: An internal error occurred.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or the socket name if the device name does not exist.
System action: NETSERV socket connection is terminated. The X'EC8' abend is issued after the message and the
corresponding socket connection is terminated. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV socket initialization
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0022I server_name device_name NJETCP Signon error: Record not valid - Expecting SYN NAK or SOHENQ
Explanation: An internal error occurred.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or the socket name if the device name does not exist.
System action: NETSERV socket connection is terminated. The X'EC8' abend is issued after the message and the
corresponding socket connection is terminated. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV socket initialization
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0023I server_name device_name Call again processing failed for receiver: rcvno
Explanation: An unexpected error was received while calling a JES specific processing routine. The error occurred
when attempting to reprocess a record that had been previously passed to the JES specific processing routine.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or the socket name if the device name does not exist.
rcvno
The receiver number.

Chapter 11. IAZ messages 171

IAZ0024I • IAZ0025I

System action: NETSERV socket connection is terminated. The X'EC8' abend is issued after the message and the
corresponding socket connection is terminated. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV socket processing
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0024I server_name device_name Call again processing failed for transmitter: xmtno
Explanation: An unexpected error was received while calling a JES specific processing routine. The error occurred
when attempting to obtain a record to process from the JES specific processing routine.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or the socket name if the device name does not exist.
xmtno
The transmitter number.
System action: NETSERV socket connection is terminated. The X'EC8' abend is issued after the message and the
corresponding socket connection is terminated. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: NETSERV socket processing
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0025I server_name device_name Attempt to send data on the stream with pending transmitter cancel
Explanation: Data transmission was attempted while a cancel is pending. This is an internal error.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.
System action: NETSERV socket connection is terminated. The X'EC8' abend is issued after the message and the
corresponding socket connection is terminated. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: JOB/SYSOUT transmitter processing
Detecting Module: IAZNJSTK
Routing Code: 8, 43

172 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0026I • IAZ0028I

Descriptor Code: 4

IAZ0026I server_name user security profile missing or OMVS segment not defined
Explanation: The network server is not authorized to OMVS and therefore cannot be started.
In the message text:
server_name
The NJETCP server name.
System action: The server address space is ended and the network server device is brought down.
Operator response: Notify the system programmer.
System programmer response: Ensure that the userids associated with the JES and network server address spaces
are defined with an OMVS segment.
Source: NETSERV server initialization
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0027I server_name device_name Header/trailer sequence number mismatch

Explanation: The NJE headers and trailers can be segmented and set in multiple buffers across NJE. Each header
segment is assigned a sequence number by the NJE transmitter and these sequence numbers are validated by the NJE
receiver. This message is issued if the receiver gets a segment out of order. This message is most likely caused by an
error in the NJE transmitter.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.
System action: The NETSERV socket connection to the receiver is terminated. The X'EC8' abend is issued after the
message and the corresponding socket connection is terminated. The system writes an abend dump. The receiver
device is terminated and drained.
Operator response: Notify the system programmer.
System programmer response: The most likely cause of this message is an error on the NJE transmitter side. The
accompanying dump provides information on the actual data areas received. Inform the owner of the NJE transmitter
of the error and provide the diagnostic information obtained by the receiver.
Source: NETSERV socket processing
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0028I server_name device_name Incorrect RCB, SRCB or length detected

Explanation: Incorrect data was found in a buffer which makes a record impossible to process. This could be caused
by an invalid RCB, invalid SRCB, or inconsistent length.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.

Chapter 11. IAZ messages 173

IAZ0029I • IAZ0500I

System action: The X'EC8' abend is issued after the message and the corresponding socket connection is terminated.
The system writes an abend dump.
Operator response: Restart the connection. If the problem persists, notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation, and contact the
IBM Support Center.
Source: JES Common
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0029I server_name device_name Storage was not obtained for XRB buffers. Connection terminated
Explanation: A malloc() for the XRB failed when starting a connection. Processing cannot continue.
The NETSERV address space limits the number of connections allowed in a single address space based on the size of
the available private storage region when the address space starts. When installation exits that get control in the
NETSERV address space use significant amounts of private storage or fail to free storage after it is no longer needed,
this condition can result in a storage shortage.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.
System action: The X'EC8' abend is issued after the message and the corresponding socket connection is terminated.
The system writes an abend dump so that storage utilization can be analyzed.
Operator response: Start additional NETSRV servers to handle the connections.
System programmer response: If the address space only has problems when it has run for a long time and the
number of socket connections remains constant, the problem is most likely to be related to storage leaks. Examine the
dump for storage leaks associated with data areas obtained in installation exits. If the problem appears to be related
to a storage leak in IBM code or the NETSERV allowing more connections than the address space can support, obtain
the X'EC8' abend dump and other relevant documentation, and contact the IBM Support Center.
If the address space only has problems when the level of activity reaches a certain level and the problem goes away
when the number of active sockets is kept low, it is mostly likely that installation exits require significant amounts of
storage. You may need to use an additional NETSERV address space to handle the number of connections.
Source: JES Common
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0500I server_name Server socket could not be obtained TCP/IP rc: rc

Explanation: The NETSERV tried to obtain a socket from TCP/IP. This operation failed. This message is preceded
by message IAZ0545I, which provides additional diagnosis information.
In the message text:
server_name
The NJETCP server name.
rc The TCP/IP return code.
System action: The NETSERV is terminated.
Operator response: Notify the system programmer.

174 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0501I • IAZ0502I

System programmer response: See z/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the description of the socket() service and the possible return codes.
Source: NETSERV SOCKET INITIALIZATION
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0501I server_name Bind for the server socket failed TCP/IP rc: rc
Explanation: The bind for either the server socket or a client socket failed. This message is preceded by message
IAZ0545I, which provides additional diagnosis information.
In the message text:
server_name
The NJETCP server name.
rc The TCP/IP return code.
System action: None.
Operator response: Notify the system programmer.
System programmer response: See z/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the description of the bind() service and the possible return codes.
Source: NETSERV socket initialization
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0502I server_name Listen for the server socket failed, TCP/IP rc: rc
Explanation: The NETSERV initialization could not be completed because the server task could not prepare for
incoming client requests.
This message is preceded by message IAZ0545I, which provides additional diagnosis information.
In the message text:
server_name
NJETCP server name
rc The errno value from the TCP/IP listen() service.
System action: The NETSERV is terminated.
Operator response: Notify the system programmer.
System programmer response: See z/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the description of the listen() service and the possible return codes.
Source: NETSERV socket initialization
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

Chapter 11. IAZ messages 175

IAZ0503I • IAZ0505I

IAZ0503I server_name Host processor name could not be obtained, TCP/IP rc: rc
Explanation: The NETSERV initialization could not be completed because the host processor name could not be
obtained.
This message is preceded by message IAZ0545I, which provides additional diagnosis information.
In the message text:
server_name
The NJETCP server name.
rc The errno value from the TCP/IP gethostname() service.
System action: The NETSERV is brought down.
Operator response: Notify the system programmer.
System programmer response: See z/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the description of gethostname() service and the possible return codes.
Source: NETSERV server initialization
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0504I server_name Local host IP address could not be resolved, TCP/IP rc: rc
Explanation: The NETSERV initialization could not be completed because the host IP address could not be resolved.
This message is preceded by message IAZ0545I, which provides additional diagnosis information.
In the message text:
server_name
The NJETCP server name.
rc The return code from the TCP/IP service getaddrinfo().
System action: The NETSERV is brought down.
Operator response: Notify the system programmer.
System programmer response: See z/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the description of the getaddrinfo() service and the possible return codes.
Source: NETSERV server initialization
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0505I server_name Local host port number could not be resolved

Explanation: The getservbyname() function failed to resolve the service name associated with the NETSERV that is
initializing.
In the message text:
server_name
The NJETCP server name.
System action: The NETSERV is brought down after this message is issued.
Operator response: Notify the system programmer.
System programmer response: Either the service name is not defined to TCP/IP or it is defined but not for the

176 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0506I • IAZ0507I

protocol TCP. You can either correct the TCP/IP definition for the service name or associate an numeric port number
with your NETSERV.
Source: NETSERV server initialization
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0506I server_name Accept on the server socket failed, TCP/IP rc: rc

Explanation: The server attempted to accept a client connection but failed.
This message is preceded by message IAZ0545I, which provides additional diagnosis information.
In the message text:
server_name
The NJETCP server name.
rc The error value from the TCP/IP service accept().
System action: Processing continues including testing to ensure TCP/IP is still active. If the accept() requests
continue to fail, the NETSERV is terminated.
Operator response: Notify the system programmer.
System programmer response: See z/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the description of the accept() service and the possible return codes.
Source: NETSERV Server accept() service processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0507I server_name Client ID could not be obtained for NETSERV server, TCP/IP rc: rc
Explanation: The NETSERV initialization could not be completed because the NETSERV client id could not be
obtained.
This message is preceded by message IAZ0545I, which provides additional diagnosis information.
In the message text:
server_name
The NJETCP server name.
rc The errno value from __getclientid() service.
System action: The NETSERV is brought down.
Operator response: Notify the system programmer.
System programmer response: See z/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the description of __getclientid() service and the possible return codes. Check for any TCP/IP related
problems that can be traced from the return code. If cannot be traced, report the problem to the IBM Support Center.
Source: NETSERV server initialization
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

Chapter 11. IAZ messages 177

IAZ0508I • IAZ0510I

IAZ0508I server_name Error attaching connection subtask, IAZGATCH service rc: rc

Explanation: The ATTACH of the socket connection subtask failed.
In the message text:
server_name
The NJETCP server name.
rc The return code rc can be any one of the below:
v -1 - Internal parameter errors.
v >0 - The return code from the ATTACHX service.
System action: The socket connection is not started.
Operator response: Notify the system programmer.
System programmer response:
v For -1, report the problem to the IBM Support Center.
v For >0, See the return codes of ATTACHX service in z/OS MVS Programming: Authorized Assembler Services Reference
ALE-DYN.
Source: NETSERV server processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0509I server_name Socket chain could not be appended

Explanation: While resetting the NETSERV server, the server main task attempts to initialize the socket queue with
an initial queue element (IAZCSOCK). If the NETSERV cannot create the IAZCSOCK chain element, the NETSERV
server is brought down.
In the message text:
server_name
The NJETCP server name.
System action: A storage shortage condition exists while resetting the Server. The NJETCP Server would be brought
down. All the network connections would have been shutdown by this time.
Operator response: Notify the system programmer.
System programmer response: Restart the server after the storage shortage situation is relieved.
Source: NETSERV server reset
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0510I server_name NJETCP server bringing down all TCP/IP socket connections
Explanation: The message is issued as a result of a Reset server command (to the NETSERV server) and the
NETSERV is currently bringing down all the TCP/IP socket connections that are active.
This process may take some time depending on the state of the socket connections. Eventually all the socket
connections are closed and the server is in a state that it was when it was initially started without any socket
connections.
In the message text:
server_name
The NJETCP server name.

178 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0511I • IAZ0512I

System action: All the active TCP/IP socket connections on the NJETCP server are closed after this message is
issued.
Operator response: None.
System programmer response: None.
Source: NETSERV server reset
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0511I server_name Server port number could not be resolved, DEFAULT assumed: portno
Explanation: When a non-numeric TCP/IP service name was provided instead of a numeric port number, and the
NETSERV was not able to resolve the service name to a port number, a default port number was assumed.
In the message text:
server_name
The NJETCP server name.
portno
The default port number is assumed as follows:
v For JES2,
– If SECURE=YES is specified on the socket statement that is used for starting the NETSERV, the default port
number assumed is 2252.
– If SECURE=YES is not specified or if SECURE=NO is specified the default port number is 175.
v For JES3, the default port number is 175.
System action: None.
Operator response: None.
System programmer response: None.
Source: NETSERV server initialization
Detecting Module: IAZNJTCP
Routing Code: 8,43
Descriptor Code: 4

IAZ0512I server_name NJETCP Server cannot accept inbound requests due to storage shortage condition
Explanation: A storage shortage condition existed. New inbound connections on the server could not be accepted
until the storage shortage condition is relieved.
In the message text:
server_name
The NJETCP server name.
System action: IAZ0539I will be issued once the storage shortage condition is relieved.
Operator response: None.
System programmer response: None.
Source: NETSERV server processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

Chapter 11. IAZ messages 179

IAZ0513I • IAZ0514I

IAZ0513I server_name Error return from givesocket() call, TCP/IP rc: rc

Explanation: NETSERV was unable to make the socket available for an inbound connection.
This message is preceded by message IAZ0545I, which provides additional diagnosis information.
In the message text:
server_name
The NJETCP server name.
rc The errno value from givesocket() service.
System action: The inbound connection for which this message is issued fails after this message.
Operator response: Notify the system programmer.
System programmer response: Seez/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the description of givesocket() service and the possible return codes.
Source: NETSERV server processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0514I server_name [device_name] msgtext rc: retcode rsn:rsncode

Explanation: A TCP/IP related C-Socket API error occurred. See msgtext for the possible error messages.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.
msgtext
The TCP/IP related C-Sockets API errors which are as follows:
Connection Error
v retcode : return code from either the recv() or send() service.
v rsncode: reason code from the TCP/IP services if applicable. The reason code is obtained from
__errno2() service.
Specified TCP/IP stack name not valid
v retcode: return code from setibmopt() service
v rsncode: reason code from the setibmopt() if applicable. The reason code is obtained from __errno2()
service.
Error in TLS configuration
v retcode: return code from ioctl() service with TTLSi_Req_Type = TTLS_QUERY_ONLY.
v rsncode: reason code from the ioctl() if applicable. The reason code is obtained from __errno2() service.
Error while initiating TLS session
v retcode: return code from ioctl() service with TTLSi_Req_Type = TTLS_INIT_CONNECTION.
v rsncode: reason code from the ioctl() if applicable. The reason code is obtained from __errno2() service.
System action: The system terminates the TCP/IP connection for which the message is issued. Normally, other error
messages follow this message to give more information about the connection for which this message is issued.
Operator response: Notify the system programmer.
System programmer response: See z/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the services and the possible return codes.

180 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0515I • IAZ0516I

Source: NETSERV socket processing, NETSERV server initialization

Detecting Module: IAZNJSTK, IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0515I server_name [device_name] msgtext rc: retcode rsn:rsncode

Explanation: There are non-TCP/IP C-Sockets API related errors. The return codes point to the return codes of the
respective API service calls.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.
msgtext
The non-TCP/IP C-Sockets API related errors which are as follows:
WTO error
v retcode : errno value from __console2() service
v rsncode: reason code from __console2() service. The reason code is obtained from __errno2() service.
System action: None.
Operator response: Notify the System Programmer.
System programmer response: See z/OS XL C/C++ Run-Time Library Referencefor the __console2() service errno codes
and z/OS UNIX System Services Programming: Assembler Callable Services Reference for information on the reason codes.
Source: NETSERV processing
Detecting Module: IAZNJSTK, IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0516I server_name device_name Error while closing client socket, TCP/IP rc: rc
Explanation: The close() service failed.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.
rc The errno issued by the TCP/IP close() service.
System action: The NETSERV socket connection is terminated after this message is issued. This message does not
influence the termination of the connection.
Operator response: Notify the system programmer.
System programmer response: See z/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the description of the close() service and the possible return codes.
Source: NETSERV socket close
Detecting Module: IAZNJSTK, IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

Chapter 11. IAZ messages 181

IAZ0517I • IAZ0520I

IAZ0517I server_name Error return from getpeername() call,TCP/IP rc: rc

Explanation: The NETSERV socket initialization failed because the socket peer name could not be obtained.
This message is preceded by message IAZ0545I, which provides additional diagnosis information.
In the message text:
server_name
The NJETCP server name.
rc The errno value from the TCP/IP service getpeername() service.
System action: The NETSERV socket connection is brought down.
Operator response: Notify the system programmer.
System programmer response: See z/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the description of the getpeername() service and the possible return codes.
Source: NETSERV socket initialization
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0518I server_name device_name Error sending data on the socket, TCP/IP rc: rc
Explanation: An attempt to send data on a socket failed.
This message is preceded by message IAZ0545I, which provides additional diagnostic information.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.
rc The errno value from the TCP/IP send() service.
System action: The NETSERV socket connection is terminated.
Operator response: Notify the system programmer.
System programmer response: See z/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the description of the send() service and the possible return codes.
Source: NETSERV socket processing
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0520I server_name NJETCP Signon error: OHOST value not valid in rcdtype
Explanation: In the IPv4 TCP/IP NJE, TCP/IP signon processing, OPEN/OPEN SSL and ACK records are
exchanged by either of the connecting nodes. If the connection is secured by SSL, an OPEN SSL record is exchanged
instead of an OPEN. If the OHOST value in the OPEN , OPEN SSL or ACK records is not valid (that is expected by
the node receiving the record), the error message is issued.
In the message text:
server_name
The NJETCP server name.
rcdtype
The rcdtype can be any one of OPEN or OPEN SSL or ACK. See operator response for more details.

182 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0521I • IAZ0522I

System action: The socket connection is brought down after issuing this message.
Operator response: Notify the system programmer.
System programmer response: If this message is issued for an inbound connection and the rcdtype is OPEN/OPEN
SSL, the remote node probable specified an incorrect node name on the socket statement. Contact that node and
verify that the correct node name or number is associated with the IP address it is attempting to connect to.
If this message is issued for an outbound connection and the rcdtype is ACK, the remote node accepted the OPEN
/OPEN SSL sent by the local node, however sent the OHOST incorrectly in the ACK record. Contact the remote node
and verify that it has correctly defined the local node.
Source: NETSERV socket initialization - TCP/IP signon
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0521I server_name NJETCP Signon error: RHOST value not valid in rcdtype
Explanation: In the IPv4 TCP/IP NJE, TCP/IP signon processing, OPEN/OPEN SSL and ACK records are
exchanged by either of the connecting nodes. If the connection is secured by SSL, an OPEN SSL record is exchanged
instead of an OPEN record. If the RHOST value in the OPEN , OPEN SSL or ACK records is not valid (that is
expected by the node receiving the record), the error message is issued.
In the message text:
server_name
The NJETCP server name.
rcdtype
The rcdtype can be any one of OPEN or OPEN SSL or ACK. See system programmer response for more details.
System action: The socket connection is brought down after issuing this message.
Operator response: Notify the system programmer.
System programmer response: If this message is issued for an inbound connection and the rcdtype is OPEN/OPEN
SSL, the remote node probably filled in its node name or its IP address incorrectly in the OPEN/OPEN SSL record.
Contact that node and verify that the correct node name or number is associated with the IP address it is attempting
to connect to.
If this message is issued for an outbound connection and the rcdtype is ACK, the remote node accepted the
OPEN/OPEN SSL sent by the local node, however sent its RHOST (its node name or its IP address) incorrectly in the
ACK record. Contact the remote node and verify that it has correctly defined the local node.
Source: NETSERV socket initialization - TCP/IP signon
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0522I server_name NJETCP Signon error: NAK received for OPEN, rsn: rsn
Explanation: An NAK record is received as a response to the TCP/IP Signon record OPEN/OPEN SSL.
server_name
The NJETCP server name.
rsn
The NAK reason code.
System action: The NETSERV socket connection is terminated after this message.
Operator response: Notify the system programmer.

Chapter 11. IAZ messages 183

IAZ0523I • IAZ0524I

System programmer response: See Network Job Entry (NJE) Formats and Protocolsfor the description of NAK reason
codes and the possible reasons.
Source: NETSERV socket initialization - TCP/IP signon
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0523I server_name device_name Error return from Subtask Init routine. Connection terminated. rc: rc
Explanation: The socket connection did not initialize because of an error in the socket subtask initialization routine.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.
rc The return code from the JES specific subtask initialization routine. This is an internal return code whose
meaning depends on the JES being used.
System action: NETSERV socket connection is terminated.
Operator response: Notify your system programmer.
System programmer response: Look for any HASP or IAT messages (depending on the JES in use) which preceded
this message. Additionally, in the case of JES2, check if an active line device is available for starting the connection. If
the problem persists, contact the IBM Support Center.
Source: NETSERV socket initialization
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0524I server_name TCP/IP Signon record not valid: ACK or NAK expected
Explanation: During signon of a node using TCP/IP protocol, a signon record was detected that contained neither
ACK nor NAK. Possible causes of this condition are:
v Corruption of the signon record.
v The remote node IP address and port values are not valid on the socket statement.

In the message text:

server_name
The NJETCP server name.
System action: NETSERV socket connection is terminated. If it is an outbound connection, an OPEN or OPEN SSL
is sent to the remote node. An ACK or NAK is expected from the remote node as a reply.
Operator response: Notify the system programmer.
System programmer response: If the problem persists, activate internal and JES tracing on the socket. Use
information from the trace and search problem reporting databases for a fix to the problem. If no fix exists, contact
the IBM Support Center.
Source: NETSERV socket initialization
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

184 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0525I • IAZ0527I

IAZ0525I server_name device_name Inbound BCB count not valid in received buffer
Explanation: The BCB count for the buffer received on the socket connection is not the expected value for the
connection. The receive buffer is processed in spite of the message. In TCP/IP NJE, BCB counts are ignored. The
message is for informational purposes only.
If the buffers are not sent in the correct order by the transmitting side, other messages are issued indicating so and
the job stream is discarded.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.
System action: The NETSERV socket connection is terminated. The X'EC8' abend is issued after the message and the
corresponding socket connection is terminated. The system writes an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the X'EC8' abend dump and other relevant documentation and contact the
IBM support center.
Source: NETSERV socket processing
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0526I server_name device_name Error receiving data on the socket, rc: rc

Explanation: An error was encountered on a recv() function.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.
rc The return code from the TCP/IP service recv().
System action: NETSERV socket connection is brought down.
Operator response: Notify the system programmer.
System programmer response: See z/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the description of the recv() service and the possible return codes.
Source: NETSERV socket processing
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0527I server_name Duplicate socket found in socket chain with same IP address and Port, current outbound
request terminated
Explanation: While initializing a socket for a TCP/IP NJE connection, a socket was found containing the same name
as that of the outbound socket to be initialized. A possible cause of this is that a socket connection to the same
remote node with the same IP address and port was not active in TCP/IP but the status was not updated in the
NETSERV.
In the message text:

Chapter 11. IAZ messages 185

IAZ0528I • IAZ0529I

server_name
The NJETCP server name.
System action: The current outbound NETSERV socket connection is not established.
Operator response: Notify the system programmer.
System programmer response: Close the existing connection using relevant JES commands and start the new socket
connection.
Source: NETSERV socket initialization for outbound requests
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0528I server_name IP address of remote peer could not be resolved, TCP/IP rc: rc
Explanation: During a start socket request, the NETSERV was unable to establish a connection to the requested IP
address (or host name) and port. This error is preceded by message IAZ0545I, which reports a return code from the
failing TCP/IP service.
If the connection is defined using an IP address, the most likely cause of this message is that the IP address and port
combination does not exist on the internet. If the connection is defined using a host name, a possible cause of this
problem is that the host name and/or port are not correctly defined in TCP/IP.
In the message text:
server_name
The NJETCP server name.
rc The return code from the TCP/IP service getaddrinfo().
System action: NETSERV socket connection is not established.
Operator response: Notify the system programmer.
System programmer response: See z/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the description of the failing TCP/IP service and the possible return codes.
Source: NETSERV socket initialization
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0529I server_name Port number of remote peer could not be resolved by getservbyname() service
Explanation: An error occurred during a call to the getservbyname() service.
In the message text:
server_name
The NJETCP server name.
System action: The NETSERV socket connection is brought down after this message is issued.
Operator response: Notify the system programmer.
System programmer response: If a service name (port name) is associated with the target SOCKET statement
instead of a numeric port number, make sure that the service name specified is resolvable. If not, specify the port
number to which the server can connect to.
Source: NETSERV socket initialization
Detecting Module: IAZNJSTK
Routing Code: 8, 43

186 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0530I • IAZ0533I

Descriptor Code: 4

IAZ0530I server_name NJETCP Signon error: ONODE value not valid in rcdtype
Explanation: When a TCP/IP NJE signon is attempted using an IPv6 IP address, OPENNJE and ACKNJE records
are exchanged by either of the connecting nodes. This message is issued if the ONODE value in the "OPENNJE" or
"ACKNJE" records does not have a valid value as seen by the node receiving the record.
In the message text:
server_name
The NJETCP server name.
rcdtype
The rcdtype can be either OPENNJE or ACKNJE. See system programmer response for more information.
System action: The socket connection is brought down after this message is issued.
Operator response: Notify the system programmer.
System programmer response: If this message is issued for an inbound connection and the rcdtype is OPENNJE,
verify that the remote node specified a correct node name on the SOCKET statement.
If this message is issued for an outbound connection and the rcdtype is ACKNJE, the remote node accepted the
OPENNJE sent by the local node but sent the ONODE incorrectly in the ACKNJE record.
If no definition errors are found and this problem persists, use the appropriate JES commands to collect NETSERV
trace data for JES and COMMON trace points. Traces from the remote node can also be required using the
appropriate trace commands for that operating system. Use the trace information collected to search problem
reporting databases for a fix to this problem. More information on NJE and NETSERV tracing can be found in the
Diagnosis manuals for the corresponding JES. An explanation of the expected data flows can be found in Network Job
Entry (NJE) Formats and Protocols. If no fix is found, contact the IBM Support Center.
Source: NETSERV socket initialization- TCP/IP signon
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0533I server_name NJETCP Signon error: NAKNJE received for OPENNJE, rsn: rsn
Explanation: A NAKNJE record is received as a response to the TCP/IP Signon record OPENNJE.
In the message text:
server_name
The NJETCP server name.
rsn
The NAKNJE reason code.
System action: The NETSERV socket connection is terminated after this message is issued.
Operator response: Notify the system programmer.
System programmer response: See Network Job Entry (NJE) Formats and Protocols for the description of NAKNJE
reason codes (same as NAK reason codes) and the possible reasons.
Source: NETSERV socket initialization- TCP/IP signon
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

Chapter 11. IAZ messages 187

IAZ0534I • IAZ0535I

IAZ0534I server_name TCP/IP Signon record not valid: ACKNJE or NAKNJE expected
Explanation: During signon of a node using TCP/IP protocol, a signon record was detected that contained neither
ACKNJE nor NAKNJE. Possible causes of this condition are:
v Corruption of the signon record.
v The remote node IP address and port values are not valid on the socket statement.

In the message text:

server_name
The NJETCP server name.
System action: NETSERV socket connection is terminated.
Operator response: Notify the system programmer.
System programmer response: If no definition errors are found and this problem persists, use the appropriate JES
commands to collect NETSERV trace data for JES and COMMON trace points. Traces from the remote node can also
be required using the appropriate trace commands for that operating system. Use the trace information collected to
search problem reporting databases for a fix to this problem. More information on NJE and NETSERV tracing can be
found in the Diagnosis manuals for the corresponding JES. An explanation of the expected data flows can be found
in Network Job Entry (NJE) Formats and Protocols. If no fix is found, contact the IBM Support Center.
Source: NETSERV socket initialization
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0535I server_name NJETCP Signon error: RNODE value not valid in rcdtype
Explanation: When a TCP/IP NJE signon is attempted using an IPv6 IP address, OPENNJE and ACKNJE records
are exchanged by either of the connecting nodes. This message is issued if the RNODE value in the OPENNJE or
ACKNJE records does not have a valid value as seen by the node receiving the record.
In the message text:
server_name
The NJETCP server name.
rcdtype
The rcdtype can be any either OPENNJE or ACKNJE. See operator response for more information.
System action: The socket connection is brought down after this message is issued.
Operator response: Notify the system programmer.
System programmer response: If this message is issued for an inbound connection and the rcdtype is OPENNJE,
the remote note may have specified its node name incorrectly in the OPENNJE record.
If this message is issued for an outbound connection and the rcdtype is ACKNJE, the remote node accepted the
OPENNJE sent by the local node but sent the RNODE incorrectly in the ACKNJE record.
If no definition errors are found and this problem persists, use the appropriate JES commands to collect NETSERV
trace data for JES and COMMON trace points. Traces from the remote node can also be required using the
appropriate trace commands for that operating system. Use the trace information collected to search problem
reporting databases for a fix to this problem. More information on NJE and NETSERV tracing can be found in the
Diagnosis manuals for the corresponding JES. An explanation of the expected data flows can be found in Network Job
Entry (NJE) Formats and Protocols. If no fix is found, contact the IBM Support Center.
Source: NETSERV socket initialization- TCP/IP signon
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

188 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0536I • IAZ0538I

IAZ0536I server_name NJETCP SERVER RECEIVED A PURGE REQUEST

Explanation: The NETSERV server received a request from JES to stop the server.
In the message text:
server_name
The NJETCP server name.
System action: All of the socket connections within this server are closed and the server ends normally.
Operator response: None.
System programmer response: None.
Source: NETSERV server termination
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0537I server_name NJETCP SERVER WAITING FOR WORK

Explanation: The NETSERV server is initialized successfully and is ready to process work.
In the message text:
server_name
The NJETCP server name.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Source: NETSERV server processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 2, 7, 8

IAZ0538I server_name Storage not obtained for inbound requests

Explanation: The system tried and failed to obtain storage for the IAZCMTST and IAZCSOCK data areas for an
inbound socket connection request.
The NETSERV address space limits the number of connections allowed in a single address space based on the size of
the available private storage region when the address space starts. When installation exits that get control in the
NETSERV address space use significant amounts of private storage or fail to free storage after it is no longer needed,
this condition can result in a storage shortage.
In the message text:
server_name
The NJETCP server name.
System action: All requests to create an inbound socket are suspended until the storage shortage is relieved.
Operator response: If this condition persists or repeats frequently, notify the system programmer.
System programmer response: If the address space only has problems when it has run for a long time and the
number of socket connections remains constant, the problem is most likely to be related to storage leaks. Examine the
dump for storage leaks associated with data areas obtained in installation exits. If the problem appears to be related
to a storage leak in IBM code or the NETSERV allowing more connections than the address space can support, obtain
the X'EC8' abend dump and other relevant documentation, and contact the IBM Support Center.
If the address space only has problems when the level of activity reaches a certain level and the problem goes away

Chapter 11. IAZ messages 189

IAZ0539I • IAZ0541I

when the number of active sockets is kept low, it is mostly likely that installation exits require significant amounts of
storage. You may need to use an additional NETSERV address space to handle the number of connections.
Source: NETSERV server processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 2, 7, 8

IAZ0539I server_name NJETCP Server storage shortage relieved

Explanation: The storage shortage that caused message IAZ0538I to be issued previously has been relieved.
In the message text:
server_name
The NJETCP server name.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Source: NETSERV server processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0540I server_name NJETCP Server accepting inbound requests

Explanation: The NETSERV is now allowing other nodes to sign on to this node.
In the message text:
server_name
The NJETCP server name.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Source: NETSERV server processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0541I server_name NJETCP SERVER WAITING FOR TCP/IP

Explanation: TCP/IP was not available while starting the NETSERV, or the specified host name was not defined in
the current active TCP/IP stacks.
In the message text:
server_name
The NJETCP server name.
System action: The NETSERV waits until TCP/IP is active or until the TCP/IP configuration is corrected.
Operator response: Start the TCP/IP address space. If TCP/IP is up, notify the system programmer.
System programmer response: Take either of the following actions to correct the TCP/IP configuration:

190 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0542I • IAZ0543I

v Stop the NETSERV server and change the appropriate TCP/IP-related parameters on the associated SOCKET or
NETSERV statements.
v Correct the TCP/IP configuration. See z/OS Communications Server: IP Configuration Guide for customization
information.
Source: NETSERV server processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 2, 7, 8

IAZ0542I server_name IAZNJTCP for msgtext

Explanation: This message is issued during NETSERV initialization processing to display information on the level of
code running.
In the message text:
server_name
The NJETCP server name.
msgtext
The compile date, time and service level of the NETSERV component code.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Source: NETSERV server initialization
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0543I server_name device_name TCP/IP connection with IP Addr: ipaddr Port: port msgtext
Explanation: The message is issued to indicate the various stages of NETSERV socket connection processing.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.
ipaddr The IP address of the remote peer
port The port number of remote peer.
msgtext One of the following:
Initiated
Successful
ended due to TCP/IP error, rc: rc (TCP/IP error code)
ended due to stop connection request
ended due to NJETCP Server request
ended due to failure of NJETCP Signon to complete within allotted time
reset due to TLS session configuration error
reset due to halt connection request
reset due to TLS session initiation failure
reset by remote peer

Chapter 11. IAZ messages 191

IAZ0544I • IAZ0545I

System action: Processing continues if the message text indicates that the connection was initiated or successful. In
all other cases the socket connection is either not established or brought down.
Operator response: Notify the system programmer.
System programmer response: If this message was issued because of a failure to establish a connection, or because
of a connection ending due to an error, this message is preceded by message IAZ0545I, which provides additional
diagnostic information.
Source: NETSERV socket processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0544I server_name device_name NJE connection with IP Addr: ipaddr Port: port msgtext
Explanation: The messages is issued to indicate the NJE status of the NETSERV socket connection with a peer node.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.
ipaddr The IP address of the remote peer.
port The port number of remote peer.
msgtext One of the following:
successful
ended due to TCP/IP error
ended on receiving a signoff record from the remote node
System action: Processing continues. If this message was issued because of a failure to establish a connection, or
because of a connection ending due to an error, this message is preceded by message IAZ0545I, which provides
additional diagnosis information.
Operator response: Notify the system programmer.
System programmer response: Proceed as directed by the message IAZ0545I.
Source: NETSERV socket processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0545I server_name [device_name] error encountered in function function_name - EDCnnnnI error_text

Explanation: A call to a C function resulted in a run-time error. The EDCnnnnI C run-time message corresponding
to the error is displayed. This message is usually followed by another IAZ message which indicates the result of this
error.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.
function_name
The C function that resulted in an error.

192 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0546I • IAZ0547I

error_text
The text of the C run-time message EDCnnnnI, corresponding to the run-time error that occurred.
System action: None.
Operator response: Notify the system programmer.
System programmer response: See z/OS Communications Server: IP Sockets Application Programming Interface Guide and
Reference for the description of the service indicated by other messages issued with this one, and the possible return
codes of that service. Using the information from the indicated return code and other IAZ messages issued with this
one, determine if the problem is with your definitions. If no definition problem is found, search problem reporting
databases for a fix for the problem. If no fix exists, contact the IBM Support Center.
Source: NETSERV socket processing
Detecting Module: IAZNJTCP / IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0546I server_name ABEND CODE=Sxxx RC=rsn

Explanation: An abend occurred in the NETSERV address space during JES TCP/IP NJE processing.
In the message text:
server_name
The NJETCP server name.
Sxxx The system completion code in hexadecimal format.
rsn The reason code.
System action: The NETSERVE is terminated with an abend dump.
Operator response: Notify the system programmer.
System programmer response: Obtain the abend dump and other relevant documentation, and contact the IBM
Support Center.
Source: NETSERV Processing
Detecting Module: IAZNJTCP / IAZNJSTK
Routing Code: 1, 2, 10
Descriptor Code: 4

IAZ0547I server_name Server shutting down. TCP receive buffer size could not be set to the minimum value of
512
Explanation: The server could not set the minimum buffer size to 512, which is the minimum buffer size for the NJE
protocol.
In the message text:
server_name
The NJETCP server name.
System action: The server address space is ended and the network server is brought down.
Operator response: Notify the system programmer.
System programmer response: Ensure that the MAXRCVBUFRSIZE and RECVBUFRSIZE on the TCPCONFIG
statements in the TCP/IP configuration data set are at least 512 (and ideally, at least 32768).
Source: NETSERV processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43

Chapter 11. IAZ messages 193

IAZ0548I • IAZ0550I

Descriptor Code: 4

IAZ0548I server_name device_name Connection denied. TCP receive buffer size could not be set to the minimum
value of nnnnn
Explanation: The value of MAXBUFRSIZE on the TCPCONFIG statement has been changed since the network
server was started with the value below nnnnn.
In the message text:
server_name
The NJETCP server name.
device_name
The device name associated with the socket, or socket name if the device name does not exist.
nnnnn The minimum buffer size for the connection.
System action: The new connection is not allowed.
Operator response: Notify the system programmer.
System programmer response: Ensure that the MAXRCVBUFRSIZE and RECVBUFRSIZE on the TCPCONFIG
statements in the TCP/IP configuration data set are at least nnnnn (and ideally, at least 32768). Or, restart the network
server to allow it to use the newly configured value.
Source: NETSERV socket processing
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

IAZ0549I server_name Server shutting down. TCP receive buffer size could not be set to the previous value of
nnnnn
Explanation: All TCP/IP stacks that were being used by this NETSERV device were brought down, and restarted
with a new receive buffer size that is smaller than the previous receive buffer size. When the message is issued, there
are no active subdevices because TCP/IP had been stopped.
In the message text:
server_name
The NJETCP server name.
nnnnn The previous receive buffer size for the connection.
System action: The NETSERV is drained.
Operator response: Restart the NETSERV to allow it to use the new smaller buffer size.
System programmer response: None.
Source: NETSERV socket processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0550I server_name NJETCP Server socket closed because socket limit of nnn reached
Explanation: The number of connections that can be supported in a NETSRV address space is limited by the
amount of available extended private storage. Once the limit has been reached, the server socket is closed, preventing
any new connections from being established to this NETSRV.
If there are other NETSRV address spaces that are listening to the same IP addresses and port, new connections will
be directed to those other address paces by TCP/IP. Otherwise, connections will fail.

194 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IAZ0551I • IAZ1500I

In the message text:

server_name
The NJETCP server name.
nnn The address space calculated connection limit.
System action: The server socket is closed. Once the number of connections drops below the displayed limit, the
server socket is opened again and new connections can be established.
Operator response: This can be normal operation for your installation. The connections in use can be displayed
using JES or TCP/IP commands.
System programmer response: Consider adding an additional NETSERV address space to increase the capacity to
support NJE connections. Additional NETSERVs can share the same port and IP address. For more information on
port sharing, see the appropriate JES initialization manual ( z/OS JES2 Initialization and Tuning Reference or z/OS JES3
Initialization and Tuning Reference), and the z/OS Communications Server: IP Configuration Reference.
Source: JES Common
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ0551I server_name Connection denied. Socket limit of nnn reached

Explanation: The number of connections that can be supported in a NETSRV address space is limited by the
amount of available extended private storage. Once the limit has been reached, the server socket is closed and any
attempt to start a new connection from the local JES will fail with this message.
In the message text:
server_name
The NJETCP server name.
nnn The address space calculated connection limit.
System action: The attempt to start a new connection is failed.
Operator response: If additional NETSERV address spaces exist, send the request to start a new connection to a
different NETSERV address space,
Notify the system programmer if additional NETSERVs need to be defined, or locally originated connections need to
be better balanced between existing NETSERV address spaces.
System programmer response: Consider adding an additional NETSERV address space to increase the capacity to
support NJE connections. Or if additional NETSERV address spaces already exist, the locally originated connections
may need to be balanced between he existing NETSERV address spaces. For more information, see the appropriate
JES initialization manual ( z/OS JES2 Initialization and Tuning Reference or z/OS JES3 Initialization and Tuning Reference).
Source: JES Common
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ1500I server_name VRBMT: msgtext

Explanation: This message is issued to trace various events during TCP/IP NJE processing. It has been issued
because the verbose trace was activated at the NETSERV level.
In the message text:
server_name
The NJETCP server name.

Chapter 11. IAZ messages 195

IAZ1501I

msgtext
The verbose message issued from the NETSERV main task IAZNJTCP.
System action: None.
Operator response: None.
System programmer response: If this level of tracing is not wanted, use the appropriate JES command to turn off
VERBOSE tracing for this device.
Source: NETSERV server processing
Detecting Module: IAZNJTCP
Routing Code: 8, 43
Descriptor Code: 4

IAZ1501I server_name device_name Snnnn:msgtext

Explanation: This message is issued to trace various events during TCP/IP NJE processing. It has been issued
because the verbose trace was activated at the NETSERV socket level.
In the message text:
server_name
The NJETCP server name.
device_name
Device name associated with the socket, or socket name if the device name does not exist.
Snnnn
The socket sequence number within the NETSERV.
msgtext
The verbose message issued from the NETSERV socket task IAZNJSTK.
System action: Processing continues.
Operator response: None.
System programmer response: If this level of tracing is not wanted, use the appropriate JES command to turn off
VERBOSE tracing for this device.
Source: NETSERV socket processing
Detecting Module: IAZNJSTK
Routing Code: 8, 43
Descriptor Code: 4

196 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

|

| Chapter 12. ICM messages

| For information about IBM Content Manager, ICM messages, see DB2 Content
| Manager: Messages and Codes, SC27-1349, which you can find in the IBM
| Publications Center:
| http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss

© Copyright IBM Corp. 1988, 2012 197

198 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)
Chapter 13. ICP messages
See Input/Output Configuration Program User's Guide and Reference for additional
messages.

ICP050D SHOULD jobname WRITE TO LEVEL xx 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.
In the message text:
jobname The jobname.
xx The specified level.

Note: If the CBD.CPC.IOCDS resource of the FACILITY class exists in an installed security product (for example,
RACF), IOCP does not issue this message to the system operator. IOCP determines your authorization to write an
input/output configuration data set (IOCDS) from your authorization to update the CBD.CPC.IOCDS resource. If the
security administrator has authorized you to update this resource, IOCP writes the IOCDS. If you are not authorized
to update the resource, IOCP does not write the IOCDS.
System action: IOCP issues this message to request permission from the system operator for the job to write to the
specified level IOCDS in the support element. 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 support element with the
input/output configuration data generated by this job. The operator should use the Input/Output Configuration
panel 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 support
element.
A reply of ‘CANCEL’ ends the job immediately with system completion code X'222'.
Source: Input/output configuration program (IOCP)
Routing Code: 1,11
Descriptor Code: 7

ICP056I IOCP JOB jobname FAILED. DID NOT BUILD LEVEL xx IOCDS.
Explanation: A job was processing the input/output configuration program (IOCP) with a WRTCDS option other
than NO on the PARM parameter of an EXEC statement.
In the message text:
jobname The jobname.
xx The specified level.
System action: IOCP ends the job with return code 8. IOCP issues this message to inform the programmer and the
system operator, if the operator previously responded to message ICP050D, that this job failed to build the level
indicated input/output configuration data set (IOCDS).
One of the following occurred:
v An error was found in the IOCP input statements
v The system operator previously replied 'NO' to message ICP050D

© Copyright IBM Corp. 1988, 2012 199

ICP057I

v The CBD.CPC.IOCDS resource of the FACILITY class has been defined to an installed security product and you
have not been authorized by the security administrator to update access to the CBD.CPC.IOCDS resource.
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)
Routing Code: 2,11,Note 32
Descriptor Code: 6

ICP057I IOCP JOB jobname SUCCESSFUL. LEVEL xx IOCDS REPLACED.

Explanation: A job was processing the input/output configuration program (IOCP) with a WRTCDS option other
than NO on the PARM parameter of an EXEC statement.
In the message text:
jobname The jobname.
xx The specified level.
System action: IOCP ends the job with a return code of 0, 2, or 4. IOCP issues this message to inform the
programmer and the system operator, if the operator 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.
Source: Input/output configuration program (IOCP)
Routing Code: 2,11,Note 32
Descriptor Code: 6

200 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Chapter 14. 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)
Routing Code: 9
Descriptor Code: 4

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.

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)
Routing Code: 9
Descriptor Code: 4

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.

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 ends.
Application Programmer Response: Respond to the problem identified by the message appearing in the data set
defined by the SYSPRINT DD statement.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: 9
Descriptor Code: 4

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).
Operator response: Notify the system programmer.
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

© Copyright IBM Corp. 1988, 2012 201

ICT021I • ICT023I

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.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: 2,9,10
Descriptor Code: 4

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.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: 9
Descriptor Code: 4

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.
System action: Key manager processing ends.
Operator response: Notify the system programmer.
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.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: 2,9,10
Descriptor Code: 4

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 action: Key manager processing ends.
Operator response: Notify the system programmer.
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

202 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICT024I • ICT030I

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 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.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: 9
Descriptor Code: 4

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.
System action: Key manager processing ends.
Operator response: Notify the system programmer.
System programmer response: See the explanation of the accompanying VSAM physical I/O error message. Correct
the problem and rerun the job.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: 2,9,10
Descriptor Code: 4

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.
Operator response: Notify the system programmer.
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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: *,10,11

Chapter 14. ICT messages 203

ICT031I • ICT033I

Descriptor Code: 4

ICT031I INVALID CRYPTOGRAPHY USER SVC NUMBER SPECIFIED

Explanation: The Programmed Cryptographic Facility 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 action: Programmed Cryptographic Facility initialization processing ends.
Operator response: Notify the system programmer.
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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: *,10,11
Descriptor Code: 4

ICT032I CRYPTOGRAPHY INITIALIZATION UNABLE TO OPEN ddname

Explanation: The Programmed Cryptographic Facility initialization process invoked by the operator START
command or the key generator utility program was 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.
System action: Programmed Cryptographic Facility initialization processing ends.
Operator response: Notify the system programmer.
System programmer response: Verify that the 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 operator START command or rerun the
key generator utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: *,10,11
Descriptor Code: 4

ICT033I LOAD FAILED FOR CRYPTOGRAPHY INSTALLATION OPTIONS MODULE

Explanation: The Programmed Cryptographic Facility initialization process invoked by the operator START
command or the key generator utility program was unable to load the installation options module, ICTOPTNS.
System action: Programmed Cryptographic Facility initialization processing ends.
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 operator START
command or rerun the key generator utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: *,10,11
Descriptor Code: 4

204 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICT034I • ICT036I

ICT034I CRYPTOGRAPHY INITIALIZATION UNABLE TO ESTABLISH ESTAE CODE xxx

Explanation: The Programmed Cryptographic Facility initialization process invoked by the operator START
command or the key generator utility program was unable to establish an ESTAE recovery environment. The code
from ESTAE processing is specified by xxx.
System action: Programmed Cryptographic Facility initialization processing ends.
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.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: *,10,11
Descriptor Code: 4

ICT035I synad message from VSAM while processing CKDS

Explanation: A physical I/O error occurred during Programmed Cryptographic Facility initialization processing
while reading the host master key from the cryptographic key data set (CKDS).
System action: Programmed Cryptographic Facility initialization processing ends.
Operator response: Notify the system programmer.
System programmer response: See the explanation of the accompanying VSAM physical I/O error message. 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: *,10
Descriptor Code: 4

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 action: Programmed Cryptographic Facility initialization processing ends.
Operator response: Notify the system programmer.
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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: *,10,11
Descriptor Code: 4

Chapter 14. ICT messages 205

ICT040I • ICT043I

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.
System action: System processing continues.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: *,9
Descriptor Code: 4

ICT041I CRYPTOGRAPHY FACILITY HAS BEEN 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.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: *,9,11
Descriptor Code: 4

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.
Operator response: Notify the system programmer.
System programmer response: Respond to the problem described by the preceding message.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: *,9,10,11
Descriptor Code: 4

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 action: START command processing ends.
Operator response: Notify the system programmer.
System programmer response: Verify that a DD statement has been included in the START procedure for the CKDS
with the ddname SYSCKDS. Check the accompanying VSAM error message for additional information. Correct the
problem and reissue the operator START command.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: *,10,11
Descriptor Code: 4

206 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICT044I • ICT1001

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.
System action: START command processing ends.
Operator response: If the code is 14, reissue the operator START command. When the problem is corrected, reissue
the START command. For all other codes, contact your system programmer.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: *.10,11
Descriptor Code: 4

ICT045I 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.
System action: The START command is ignored.
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.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: *,11
Descriptor Code: 4

ICT046I 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.
Source: Programmed Cryptographic Facility (PCF)
Routing Code: *,9,11
Descriptor Code: 4

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.
System action: Processing ends for this control statement. Processing continues for any other control statements.
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.

Chapter 14. ICT messages 207

ICT1002 • ICT1006

Source: Programmed Cryptographic Facility (PCF)

ICT1002 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: Processing ends for this control statement. Processing continues for any other control statements.
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 on the EXEC
statement and providing the corrected control statement as input.
Source: Programmed Cryptographic Facility (PCF)

ICT1003 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.
System action: Processing ends for this control statement. Processing continues for any other control 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 generator utility
program, specifying the CHGK function on the EXEC statement and providing the corrected control statement as
input.
Source: Programmed Cryptographic Facility (PCF)

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.
System action: Processing ends for this control statement. Processing continues for any other control statements.
Application Programmer Response: Supply a valid 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 generator utility
program, specifying the CHGK function on the EXEC statement and providing the corrected control statement as
input.
Source: Programmed Cryptographic Facility (PCF)

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 precedes this
message.
System action: Processing ends for this control statement. Processing continues for any other control statements.
Application Programmer Response: Correct the keyword parameter or remove the redundant keyword parameter
on the control statement. Rerun the key generator utility program, specifying the CHGK function on the EXEC
statement and providing the corrected control statement.
Source: Programmed Cryptographic Facility (PCF)

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.

208 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICT1007 • ICT1010

The control statement containing the error precedes this message.

System action: Processing ends for this control statement. Processing continues for any other control statements.
Application Programmer Response: If the 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 CHGK function on the EXEC statement and providing the
corrected control statement.
Source: Programmed Cryptographic Facility (PCF)

ICT1007 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.
System action: Processing ends for this control statement. Processing continues for any other control 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.
Source: Programmed Cryptographic Facility (PCF)

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.
System action: Key generator utility processing ends.
Application Programmer Response: Supply the missing value in the PARM field of the EXEC statement and rerun
the key generator utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)

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 precedes this message.
System action: Processing ends for this control statement. Processing continues for any other control 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.
Source: Programmed Cryptographic Facility (PCF)

ICT1010 LABEL NOT FOUND; NOT PROCESSED

Explanation: A user requested the key generator 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.
System action: Processing ends for this control statement. Processing continues for any other control statements.
Application Programmer Response: Supply the correct label and rerun the key generator utility program, specifying
the CHGK function on the EXEC statement.
Source: Programmed Cryptographic Facility (PCF)

Chapter 14. ICT messages 209

ICT1011 • ICT1014

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.
System action: Key generator utility processing ends.
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, 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
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.
System action: Key generator utility processing ends.
Application Programmer Response: Follow local procedures.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00, ICTMKG01

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.
System action: Key generator utility processing ends. No control statements are processed.
Application Programmer Response: If the code is 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.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00, ICTMKG01

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.
System action: Key generator utility processing ends.
Application Programmer Response: Add the desired control statements to the SYSIN data set and rerun the key
generator utility program.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG01

210 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICT1015 • ICT1016

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.
System action: Key generator utility processing ends.
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.
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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00, ICTMKG01

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.
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.
System action: Key generator utility processing ends.
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.

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.

To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00, ICTMKG01

Chapter 14. ICT messages 211

ICT1017 • ICT1020

ICT1017 CRYPTOGRAPHY STARTED; INVALID KEY GENERATOR REQUEST

Explanation: The key generator utility program was unable to run because the Programmed Cryptographic Facility
was active.
System action: Key generator utility processing ends.
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.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00

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.
System action: Key generator utility processing continues.
Application Programmer Response: If the problem 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.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00, ICTMKG01

ICT1019 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, they are processed at this time.
System action: Key generator utility processing continues.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00

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.
System action: Key generator utility processing ends.
Application Programmer Response: Supply a valid keyword parameter in the PARM field. The valid keyword
parameters are SETM, CHGM, CHGK, and SEED. Rerun the key generator utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00

212 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICT1021 • ICT1023

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 statement for
the key generator utility program.
System action: Key generator utility processing ends.
Application Programmer Response: Supply a new 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. Rerun the key generator
utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00

ICT1022 INVALID SYNTAX FOR text

Explanation: In the message, text is one of the following:

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.
System action: Key generator utility processing ends.
Application Programmer Response: Correct the 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00

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 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.
System action: Key generator utility processing ends.
Application Programmer Response: Check the 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 MVS Programmed Cryptographic Facility:
Installation 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).
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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00, ICTMKG01

Chapter 14. ICT messages 213

ICT1024 • ICT1027

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.
System action: Processing ends for this control statement. Processing continues for any other control statements.
Application Programmer Response: Correct the control statement. Rerun the key generator utility program,
specifying the CHGK function on the EXEC statement and providing the corrected control statement.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG01

ICT1025 REQUIRED INPUTS FOR KEY GENERATION NOT AVAILABLE

Explanation: The key generator utility program 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.
System action: Processing ends for this control statement. Processing continues for any other control 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 CHGK function on the EXEC statement and providing the
control statement that was being processed when the problem occurred.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG01

ICT1026 UNEXPECTED VSAM ERROR CODE rc [FDBK code]

Explanation: An error occurred when the key generator utility program attempted to read from or write 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.
System action: Key generator utility processing ends.
System programmer response: For an explanation of the return code and feedback code, see the description of the
VSAM macro. Correct the problem and rerun the 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00, ICTMKG01

ICT1027 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.
System action: Key generator utility processing ends.
Application Programmer Response: If you want to change the host master key and secondary key-encrypting keys,

214 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICT1028 • ICT1031

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.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00

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.
System action: Key generator utility processing ends.
Application Programmer Response: Correct the value of the current host master key in the EXEC statement and
rerun the key generator utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00

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.
System action: Key generator utility processing ends.
Application Programmer Response: Supply a 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00

ICT1030 INVALID SMF DATA LENGTH FROM INSTALLATION EXIT; PROCESSING 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.
Application Programmer Response: Check the 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 MVS Programmed Cryptographic Facility:
Installation Reference Manual.) 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00, ICTMKG01

ICT1031 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.
System action: Key generator utility processing ends.

Chapter 14. ICT messages 215

ICT1032 • ICT1033

Application Programmer Response: The valid delimiters are comma, right and left parentheses, and blank. Correct
the error and rerun the key generator utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00

ICT1032 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
4 The Programmed Cryptographic Facility has not been initialized.
8 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.
System action: Key generator utility processing ends.
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 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00, ICTMKG01

ICT1033 CRYPTOGRAPHY CIPHER FUNCTION FAILED - CODE xx

Explanation: An error occurred during the processing of a CIPHER macro instruction issued by the key generator
utility program. In the message text, xx is the error return code from the macro. The values of xx and their
explanations are as follows:
Code Explanation
4 The Programmed Cryptographic Facility has not been initialized. The data could not be enciphered or
deciphered.
8 The operation requested was not valid; the macro was not CIPHER.
12 An ESTAE recovery environment could not be 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 action: Key generator utility processing ends.
Application Programmer Response: Contact your 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.

216 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICT1034 • ICT1036

Source: Programmed Cryptographic Facility (PCF)

Detecting Module: ICTMKG00

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
4 The Programmed Cryptographic Facility has not been initialized.
8 The operation requested was not valid.
12 An ESTAE recovery environment could not be 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.
System action: Key generator utility processing ends.
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 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00, ICTMKG01

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.
System action: Key generator utility processing ends.
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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00, ICTMKG01

ICT1036 CKDS ENTRY SUCCESSFULLY DELETED

Explanation: The key generator utility program has successfully deleted an entry from the cryptographic key data
set (CKDS). The control statement that was processed precedes this message.
System action: Processing continues.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG01

Chapter 14. ICT messages 217

ICT1037

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.
System action: Key generator utility processing ends.
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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Programmed Cryptographic Facility (PCF)
Detecting Module: ICTMKG00

218 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Chapter 15. ICU messages
ICU010I 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: Cryptographic Unit Support Program (CUSP)
Routing Code: 9
Descriptor Code: 4

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

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: Cryptographic Unit Support Program (CUSP)
Routing Code: 9
Descriptor Code: 4

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.

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 ends.
Application Programmer Response: Respond to the problem identified by the message appearing in the data set
defined by the SYSPRINT DD statement.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 9
Descriptor Code: 4

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.

Note: The security administrator must ensure that an authorized person was running the key generator utility
program. More information about the requester is in SMF record type 82.
System action: Key generator utility processing continues.

© Copyright IBM Corp. 1988, 2012 219

ICU014I • ICU021I

Source: Cryptographic Unit Support Program (CUSP)

Routing Code: 9
Descriptor Code: 4

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

Note: The security administrator must ensure that an authorized person was running the key generator utility
program. More information about the requester is in SMF record type 82.
System action: Key generator utility processing ends.
Application Programmer Response: Respond to any error messages that were issued.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 9
Descriptor Code: 4

ICU020I 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).
Operator response: Notify the system programmer.
System programmer response: See the explanation of the accompanying VSAM physical I/O error message in your
VSAM macro instruction book. 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 Cryptographic Unit Support (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.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9,10
Descriptor Code: 4

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.
System action: Key manager processing ends.
Operator response: Notify the security administrator.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 9

220 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICU022I • ICU026I

Descriptor Code: 4

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.
System action: Key manager processing ends.
Operator 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.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9,10
Descriptor Code: 4

ICU024I 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.
System action: Key manager processing ends.
Operator response: Notify the system programmer.
System programmer response: For an explanation of the return code and feedback code, see the description of the
VSAM macro. Correct the problem and rerun the job.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9,10
Descriptor Code: 4

ICU025I ENTRY xxxxxxxx FAILS AUTHENTICATION TEST

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.
Operator response: Notify the system programmer.
System programmer response: Ensure that the CKDS and MKDS that are mounted are the current versions of the
data sets. Rerun the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9
Descriptor Code: 4

ICU026I INTERNAL CKDS LOOKUP FAILED AND DISABLED. ERROR CODE xx yy

Explanation: A failure occurred in the cryptographic key table (CKT). xx and yy are the return and reason 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.

Chapter 15. ICU messages 221

ICU030I • ICU031I

Source: Cryptographic Unit Support Program (CUSP)

Return Code Reason Code Description

8 8 CKT address not passed by ICUMKM14.

16 CKT information passed from ICUMKM14 was not valid.
20 Invalid CKT record key passed by ICUMKM14.
24 Invalid record buffer passed by ICUMKM14.
28 No entries in CKT to retrieve.
32 Invalid CKT RKP passed by ICUMKM14.
40 CKT record failed modification detection check (MDC). CKT has
become corrupted.
12 36 Recovery environment could not be established in ICUMKM18.

ICU030I CRYPTOGRAPHY INITIALIZATION UNABLE TO LOCATE name IN LPA

Explanation: The Cryptographic Unit Support 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: Cryptographic Unit Support initialization processing ends.
Operator response: Notify the system programmer.
System programmer response: Determine if the 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 10,11,*
Descriptor Code: 4

ICU031I INVALID CRYPTOGRAPHY USER SVC NUMBER SPECIFIED

Explanation: The Cryptographic Unit Support initialization process invoked by the operator START command or the
key generator utility program has determined that the options module, ICUOPTN2, contains an user SVC number
that is not valid.
System action: Cryptographic Unit Support initialization processing ends.
Operator response: Notify the system programmer.
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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 10,11,*
Descriptor Code: 4

222 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICU033I • ICU042I

ICU033I LOAD FAILED FOR CRYPTOGRAPHY INSTALLATION OPTIONS MODULE

Explanation: The Cryptographic Unit Support initialization process invoked by the operator START command or the
key generator utility program was unable to load the installation options module, ICUOPTN2.
System action: Cryptographic Unit Support initialization processing ends.
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 operator START
command or rerun the key generator utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 10,11,*
Descriptor Code: 4

ICU034I CRYPTOGRAPHY INITIALIZATION UNABLE TO ESTABLISH ESTAE CODE xxx

Explanation: The Cryptographic Unit Support initialization process invoked by the operator START command or the
key generator utility program was unable to establish an ESTAE recovery environment. The code from ESTAE
processing is specified by xxx. See z/OS MVS Programming: Assembler Services Reference ABE-HSP for further
information.
System action: Cryptographic Unit Support initialization processing ends.
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, run the key generator utility program again. For all other
codes, contact your system programmer. When the problem is corrected, run the key generator utility program again.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 10,11,*
Descriptor Code: 4

ICU041I CRYPTOGRAPHY FACILITY HAS BEEN ACTIVATED

Explanation: An operator START command has successfully activated the Cryptographic Unit Support. All functions
of the facility are currently operational.
System action: The Cryptographic Unit Support is active.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 9,11,*
Descriptor Code: 4

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.
System action: START command processing ends. The Cryptographic Unit Support is not active.
Operator response: Notify the system programmer.
System programmer response: Respond to the problem described by the preceding message.
Source: Cryptographic Unit Support Program (CUSP)

Chapter 15. ICU messages 223

ICU043I • ICU045I

Routing Code: 9,10,11,*

Descriptor Code: 4

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 action: START command processing ends.
Operator response: Notify the system programmer.
System programmer response: Verify that a DD statement has been included in the START procedure for the CKDS
with the ddname SYSCKDS. Check the accompanying VSAM error message for additional information. Correct the
problem and reissue the operator START command.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 10,11,*
Descriptor Code: 4

ICU044I START jobname UNABLE TO ESTABLISH ESTAE CODE xxx

Explanation: The START procedure used to start the Cryptographic Unit Support, identified by jobname, was unable
to establish an ESTAE recovery environment.
System action: START command processing ends.
Operator response: If the code is 14, reissue the operator START command. For all other codes, notify your system
programmer. When the problem is corrected, reissue the START command.
System programmer response: The return code from ESTAE processing is specified by xxx. See z/OS MVS
Programming: Assembler Services Reference ABE-HSP for further information.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 10,11,*
Descriptor Code: 4

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.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 11,*
Descriptor Code: 4

224 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICU047I • ICU051I

ICU047I MODIFY CRYPTOGRAPHY COMMAND REJECTED

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.
Operator response: Ensure that the cryptographic units specified in the command are physically online. Reissue the
MODIFY command.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 9,*
Descriptor Code: 4

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.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 9,*
Descriptor Code: 4

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.
Operator response: Notify the security administrator.
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.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9
Descriptor Code: 4

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.
Operator response: Notify the system programmer.
System programmer response: Ensure that the 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.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9
Descriptor Code: 4

Chapter 15. ICU messages 225

ICU052I • ICU055I

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.
System action: Key generator utility processing ends.
Operator response: Notify the system programmer.
System programmer response: Ensure that the 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.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9
Descriptor Code: 4

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.
System action: Key generator utility processing ends.
Operator response: Notify the system programmer.
System programmer response: Ensure that the 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.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9
Descriptor Code: 4

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.
Operator response: Notify the system programmer. When the problem has been corrected, issue the START or
MODIFY command again.
Application Programmer Response: Notify the system programmer. When the problem has been corrected, run the
key generator utility again.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9,11
Descriptor Code: 4

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.
System action: If another cryptographic unit is available, processing continues. Otherwise, processing ends. A logrec
data set record is written.
Operator response: Contact hardware support. Notify the security administrator.
System programmer response: Run OLTEP diagnostics for the problem device.

226 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICU060I • ICU070I

Source: Cryptographic Unit Support Program (CUSP)

Routing Code: 2,9
Descriptor Code: 4

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.
Source: Cryptographic Unit Support Program (CUSP)

Return Code Reason Code Description

4 20 Error closing the CUSP CKDS.

12 4 Error opening the CUSP CKDS.
12 Unable to get storage for CKT (in subpool 231).
16 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.
28 Recovery environment could not be established in ICUMKM17.

ICU061I CRYPTOGRAPHY FACILITY HAS BEEN TERMINATED

Explanation: An operator STOP command has successfully deactivated the Cryptographic Unit Support. All current
sessions and all new sessions will fail.
System action: System processing continues.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 10,11,*
Descriptor Code: 4

ICU062I INITIALIZATION OF CRYPTOGRAPHY FACILITY AND OPEN SYSCKDS SUCCESSFUL

Explanation: An operator START command has 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.
System action: System processing continues.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 9,11,*
Descriptor Code: 4

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.
Operator response: Contact hardware support. Notify the security administrator.

Chapter 15. ICU messages 227

ICU071I • ICU074I

Source: Cryptographic Unit Support Program (CUSP)

Routing Code: 2,9,10
Descriptor Code: 4

ICU071I 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.
System action: If another cryptographic unit is available, processing continues. Otherwise, processing ends.
Operator response: Contact hardware support. Notify the security administrator.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9,20
Descriptor Code: 4

ICU072I NO DEVICE PATH TO DEVICE device-addr

Explanation: There is no physical I/O path to the cryptographic unit identified by device-addr.
System action: If another cryptographic unit is available, processing continues. Otherwise, processing ends.
Operator response: Notify the system programmer.
System programmer response: Ensure that the cryptographic unit is physically online and logically online (by
means of a VARY command) and that the cryptographic unit's physical key is locked. Then issue a MODIFY
command to add this unit to the configuration of cryptographic units, or issue a START command after the
Cryptographic Unit Support is stopped.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9,10
Descriptor Code: 4

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.
System action: If another cryptographic unit is available, processing continues. Otherwise, processing ends.
Operator response: Notify the system programmer.
System programmer response: Ensure that sufficient storage is available in subpool 252. Reissue the START
command or rerun the key generator utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9,10
Descriptor Code: 4

ICU074I 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.
System action: If another cryptographic unit is available, processing continues. Otherwise, processing ends.
Operator response: Notify the system programmer.
System programmer response: See z/OS MVS Programming: Authorized Assembler Services Guide for the explanation

228 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICU077I • ICU080I

of the error code. Correct the problem and reissue the START command or rerun the key generator utility.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9,10
Descriptor Code: 4

ICU077I DEVICE device-addr PREVIOUSLY ALLOCATED TO ANOTHER JOB OR TASK

Explanation: The Cryptographic Unit Support attempted to allocate the cryptographic unit identified by device-addr,
but the unit is allocated to another job or task in the system.
System action: If another cryptographic unit is available, processing continues. Otherwise, processing ends.
Operator response: Notify the system programmer 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9,10
Descriptor Code: 4

ICU078I DEVICE device-addr UNAVAILABLE - OFFLINE AND IN USE BY A SYSTEM COMPONENT

Explanation: The Cryptographic Unit Support attempted to allocate the cryptographic unit identified by device-addr,
but the unit was designated as not allocatable (UCBNALOC=ON).
System action: If another cryptographic unit is available, processing continues. Otherwise, processing ends.
Operator response: Notify the system programmer 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9,10
Descriptor Code: 4

ICU080I I/O INITIALIZATION UNABLE TO ESTABLISH ESTAE CODE xxx

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 z/OS MVS Programming: Assembler Services Reference ABE-HSP for further
information.
System action: The Cryptographic Unit Support I/O initialization or key generator utility ends.
Operator response: If the code is 4, reissue the operator START command or 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.
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.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.

Chapter 15. ICU messages 229

ICU081I • ICU084I

Source: Cryptographic Unit Support Program (CUSP)

Routing Code: 2,9,10
Descriptor Code: 4

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.
Operator response: Notify the system programmer.
System programmer response: Ensure that sufficient storage is available in subpool 227. Reissue the START
command or rerun the key generator utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9,10
Descriptor Code: 4

ICU082I 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.
System action: START command or key generator utility processing ends.
Operator response: Notify the system programmer.
System programmer response: Ensure that at least one cryptographic unit is defined during system generation.
Reissue the START command or rerun the key generator utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9,10
Descriptor Code: 4

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.
System action: START command or key generator utility processing ends.
Operator response: Notify the system programmer. When the problem is corrected, issue the START command
again.
Application Programmer Response: Notify the system programmer. When the problem is corrected, run the key
generator utility program again.
System programmer response: Ensure that sufficient storage is available in subpool 230.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9,10
Descriptor Code: 4

230 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICU085I • ICU1003

ICU085I NO CRYPTOGRAPHIC UNITS AVAILABLE

Explanation: All cryptographic units failed with one of the following errors:
v Key verification test failed
v Internal buffer test failed
v Sufficient storage to perform the internal buffer test could not be obtained.
v The cryptographic unit could not be opened.

One or more messages that explain the error precede this message.
System action: START command or key generator processing ends.
Operator response: Notify the system programmer.
System programmer response: Respond to the problem described by the preceding message.
Source: Cryptographic Unit Support Program (CUSP)
Routing Code: 2,9,10
Descriptor Code: 4

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 precedes this
message.
System action: Processing ends for this control statement. Processing continues for any other control statements.
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 z/OS 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.
Source: Cryptographic Unit Support Program (CUSP)

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.
System action: Processing ends for this control statement. Processing continues for any other control 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.
Source: Cryptographic Unit Support Program (CUSP)

ICU1003 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 precedes this message.
System action: Processing ends for this control statement. Processing continues for any other control 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 generator utility
program, specifying the CHGK function on the EXEC statement and providing the corrected control statement as
input.
Source: Cryptographic Unit Support Program (CUSP)

Chapter 15. ICU messages 231

ICU1004 • ICU1007

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 precedes this message.
System action: Processing ends for this control statement. Processing continues for any other control statements.
Application Programmer Response: Supply a valid 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 generator utility
program, specifying the CHGK function on the EXEC statement and providing the corrected control statement as
input.
Source: Cryptographic Unit Support Program (CUSP)

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.
System action: Processing ends for this control statement. Processing continues for any other control statements.
Application Programmer Response: Correct the keyword parameter or remove the redundant keyword parameter
on the control statement. Rerun the key generator utility program, specifying the CHGK function on the EXEC
statement and providing the corrected control statement.
Source: Cryptographic Unit Support Program (CUSP)

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

System action: Processing ends for this control statement. Processing continues for any other control statements.
Application Programmer Response: If the 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 CHGK function on the EXEC statement and providing the
corrected control statement.
Source: Cryptographic Unit Support Program (CUSP)

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.
System action: Processing ends for this control statement. Processing continues for any other control 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.
Source: Cryptographic Unit Support Program (CUSP)

232 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICU1008 • ICU1012

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.
System action: Key generator utility processing ends.
Application Programmer Response: Supply the missing value in the PARM field of the EXEC statement and rerun
the key generator utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

ICU1009 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 precedes this message.
System action: Processing ends for this control statement. Processing continues for any other control 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.
Source: Cryptographic Unit Support Program (CUSP)

ICU1010 LABEL NOT FOUND; NOT PROCESSED

Explanation: A user requested the key generator 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.
System action: Processing ends for this control statement. Processing continues for any other control statements.
Application Programmer Response: Supply the correct label and rerun the key generator utility program, specifying
the CHGK function on the EXEC statement.
Source: Cryptographic Unit Support Program (CUSP)

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.
System action: Key generator utility processing ends.
System programmer response: See the explanation of the accompanying VSAM physical I/O error message in your
VSAM macro instruction book. 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 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

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

Chapter 15. ICU messages 233

ICU1013 • ICU1017

System action: Key generator utility processing ends.

Application Programmer Response: Follow local procedures.
Source: Cryptographic Unit Support Program (CUSP)

ICU1013 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.
System action: Key generator utility processing ends. No control statements are processed.
Application Programmer Response: If the code is 14, run the key generator utility program again. For all other
codes, contact your system programmer. When the problem is corrected, run the key generator utility program again.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Source: Cryptographic Unit Support Program (CUSP)

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.
System action: Key generator utility processing ends.
Application Programmer Response: Add the desired control statements to the SYSIN data set and rerun the key
generator utility program.
Source: Cryptographic Unit Support Program (CUSP)

ICU1015 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. 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.
System action: Key generator utility processing ends.
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.

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

To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

ICU1017 CRYPTOGRAPHY STARTED; INVALID KEY GENERATOR REQUEST

Explanation: The key generator utility program was unable to run because the Cryptographic Unit Support was
active.
System action: Key generator utility processing ends.
Application Programmer Response: When the Cryptographic Unit Support is stopped and there are no

234 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICU1018 • ICU1023

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.
Source: Cryptographic Unit Support Program (CUSP)

ICU1018 KEY GENERATION NOT ALLOWED - text

text is
TOD CLOCK ERROR
SEED NOT SUPPLIED
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.
System action: Key generator utility processing continues.
Application Programmer Response: If the problem 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.
Source: Cryptographic Unit Support Program (CUSP)

ICU1019 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, they are processed at this time.
System action: Key generator utility processing continues.
Source: Cryptographic Unit Support Program (CUSP)

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.
System action: Key generator utility processing ends.
Application Programmer Response: Supply a valid keyword parameter in the PARM field. The valid keyword
parameters are SETM, CHGM, CHGK, and SEED. Rerun the key generator utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

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 statement for
the key generator utility program.
System action: Key generator utility processing ends.
Application Programmer Response: Supply a new host master key value and its complement in the PARM field of
the EXEC statement. See z/OS DFSMS Using Data Sets for a description of weak key values. Rerun the key generator
utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

ICU1023 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 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 precedes this message.

Chapter 15. ICU messages 235

ICU1024 • ICU1030

System action: Key generator utility processing ends.

Application Programmer Response: Check the 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 z/OS DFSMS Using Data Sets .) 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).
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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

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.
System action: Processing ends for this control statement. Processing continues for any other control statements.
Application Programmer Response: Correct the control statement. Rerun the key generator utility program,
specifying the CHGK function on the EXEC statement and providing the corrected control statement.
Source: Cryptographic Unit Support Program (CUSP)

ICU1025 REQUIRED INPUTS FOR KEY GENERATION NOT AVAILABLE

Explanation: The key generator utility program 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.
System action: Processing ends for this control statement. Processing continues for any other control 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 CHGK function on the EXEC statement and providing the
control statement that was being processed when the problem occurred.
Source: Cryptographic Unit Support Program (CUSP)

ICU1030 INVALID SMF DATA LENGTH FROM INSTALLATION EXIT; PROCESSING 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.
Application Programmer Response: Check the 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 z/OS DFSMS Using Data Sets 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 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

236 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICU1031 • ICU1033

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.
System action: Key generator utility processing ends.
Application Programmer Response: The valid delimiters are comma, right and left parentheses, and blank. Correct
the error and rerun the key generator utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

ICU1032 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
4 The Cryptographic Unit Support has not been initialized.
8 An incorrect operation was requested; the macro was not EMK.
12 An ESTAE recovery environment could not be 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.
System action: Key generator utility processing ends.
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 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 process the remaining control statements.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

ICU1033 CRYPTOGRAPHY CIPHER FUNCTION FAILED - CODE xx

Explanation: An error occurred during the processing of a CIPHER macro instruction issued by the key generator
utility program. In the message text, xx is the error return code from the macro. The values of xx and their
explanations are as follows:
Code Explanation
4 The Cryptographic Unit Support has not been initialized. The data could not be enciphered or deciphered.
8 An incorrect operation was requested; the macro was not CIPHER.
12 An ESTAE recovery environment could not be established or an unrecoverable I/O error 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.
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.
System action: Key generator utility processing ends.
Application Programmer Response: Contact your programming support personnel. When the problem has been

Chapter 15. ICU messages 237

ICU1034 • ICU1036

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 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

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:
Code Explanation
4 The Cryptographic Unit Support has not been initialized.
8 The operation requested was not valid.
12 An ESTAE recovery environment could not be established or an unrecoverable I/O error 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.
System action: Key generator utility processing ends.
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 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 process the remaining control statements.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

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.
System action: Key generator utility processing ends.
Application Programmer Response: See z/OS DFSMS Macro Instructions for Data Sets for the explanation of the
message. Correct the problem and rerun the key generator utility program as follows. If the SETM or CHGM
function was requested and the host 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 process the remaining control statements.
Notify the security administrator.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

ICU1036 CKDS ENTRY SUCCESSFULLY DELETED

Explanation: The key generator utility program has successfully deleted an entry from the cryptographic key data
set (CKDS). The control statement that was processed precedes this message.
System action: Processing continues.

238 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICU1038 • ICU1042

Source: Cryptographic Unit Support Program (CUSP)

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.
System action: Key generator utility processing ends.
Application Programmer Response: Notify the 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 process the remaining control statements.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

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 control statement containing the error precedes this message.
System action: Processing ends for this control statement. Processing continues for any other control statements.
Application Programmer Response: Correct the label on the control statement. Rerun the key generator utility
program, specifying the CHGK function on the EXEC statement providing the corrected control statement.
Source: Cryptographic Unit Support Program (CUSP)

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.
System action: Processing ends for this control statement. Processing continues for any other control statements.
Application Programmer Response: Rerun the key generator utility program, specifying the CHGK function on the
EXEC statement. Provide more than one LOCAL-GROUP control statement as necessary so that each does not specify
more than 64 labels.
Source: Cryptographic Unit Support Program (CUSP)

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.
System action: Processing ends for this control statement. Processing continues for any other control statements.
Application Programmer Response: Correct the format of the control statement or add the continuation card. Rerun
the key generator utility program, specifying the CHGK function on the EXEC statement and providing the corrected
control statement.
Source: Cryptographic Unit Support Program (CUSP)

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

Chapter 15. ICU messages 239

ICU1043 • ICU1045

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
control statement containing the error precedes this message.
System action: Processing ends for this control statement. Processing continues for any other control statements.
Application Programmer Response: Correct the control statement in error. Rerun the key generator utility program,
specifying the CHGK function on the EXEC statement and providing the corrected control statement.
Source: Cryptographic Unit Support Program (CUSP)

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'.
System action: Key generator utility processing ends.
Application Programmer Response: Notify the 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.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

ICU1044 THE ATTACH OF TASK ICUMKG04 FAILED WITH CODE xx

Explanation: An error occurred when the key 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.
System action: Key generator utility processing ends.
Application Programmer Response: Notify the security administrator. Ensure that the module ICUMKG04 is
properly loaded in SYS1.LINKLIB and rerun the key generator utility.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

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.
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.
System action: Key generator utility processing ends.
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.
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.

240 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 ICU1046 • ICU1048

For information on defining and reorganizing the CKDS, see z/OS DFSMS Access Method Services for Catalogs.The
commands needed to define, reorganize, and copy the data set are described in z/OS DFSMS Access Method Services
for Catalogs and z/OS DFSMS Macro Instructions for Data Sets.

Notify the security administrator.

To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

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.
System action: Key generator utility processing ends.
Application Programmer Response: Correct the 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.
Source: Cryptographic Unit Support Program (CUSP)

ICU1047 UNEXPECTED VSAM ERROR ON ddname CODE rc [FDBK code]

Explanation: An error occurred when the key 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.
System action: Key generator utility processing ends.
System programmer response: For an explanation of the return code and feedback code, see the description of the
VSAM macro. Correct the problem and rerun the utility program 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 process the remaining control statements. Notify the security administrator.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

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.
System action: Key generator utility processing ends.
Application Programmer Response: Correct the value of the old host master key in the EXEC statement and rerun
the key generator utility program.
To ensure that you have all the messages issued for this problem, specify MSGLEVEL=(1,1) for the job.
Source: Cryptographic Unit Support Program (CUSP)

Chapter 15. ICU messages 241

242 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)
Chapter 16. IDA messages
IDA messages 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.

IDA001 INVALID POSITIONAL PARAMETER, prm - IGNORED

Explanation: The specified positional parameter is not valid.
In the message text:
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 reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Detecting Module: IDAMDVRP
Routing Code: Note 11
Descriptor Code: -

IDA002 keyword KEYWORD REQUIRED - NOT SPECIFIED

Explanation: The caller omitted a required keyword.
In the message text:
keyword The keyword.
System action: The system does not expand the macro.
Application Programmer Response: This is probably an error in the calling program. Provide the required keyword
and value. Submit the job again.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: -

© Copyright IBM Corp. 1988, 2012 243

IDA003 • IDA005

IDA003 INVALID VALUE, value, SPECIFIED FOR keyword KEYWORD

Explanation: The value specified for the indicated keyword was incorrect.
In the message text:
value The specified value.
keyword The keyword.
System action: The system does not expand the macro.
Application Programmer Response: This is probably an error in the calling program. Correct the erroneous value.
Submit the job again.
System programmer response: 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 program listing, the
assembly listing, and the source input associated with the job.
Source: DFSMSdfp
Detecting Module: IDAMDVRP
Routing Code: Note 11
Descriptor Code: -

IDA004 keyword KEYWORD NOT VALID FOR EXECUTE FORM - IGNORED

Explanation: The indicated keyword is not valid for the execute form of the macro.
In the message text:
keyword The keyword.
System action: The system ignores the keyword. The system expands the macro normally.
Application Programmer Response: This is probably 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.
System programmer response: 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 program listing, the
assembly listing, and the source input associated with the job.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: -

IDA005 INVALID OR DUPLICATE SUBLIST ITEM FOR keyword KEYWORD, xxx

Explanation: The specified sublist item is not valid or is duplicated for the keyword.
In the message text:
keyword The keyword.
xxx The name of the sublist item.
System action: The system does not expand the macro.
Application Programmer Response: This is probably an error in the calling program. Correct the sublist item.
Resubmit the job.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Routing Code: Note 11

244 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDA006 • IDA008

Descriptor Code: -

IDA006 keyword VALUE, value, NOT VALID FOR LIST FORM

Explanation: The specified value for the keyword is not valid for the list form of the macro.
In the message text:
keyword The keyword.
value The specified value.
System action: The system does not expand the macro.
Application Programmer Response: This is probably an error in the calling program. Correct the erroneous value.
Submit the job again.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: -

IDA007 LOGIC ERROR IN MACRO mac

Explanation: The system detected a logic error in the macro.
In the message text:
mac The name of the macro.
System action: The system does not expand the macro.
Application Programmer Response: Determine where the error occurs in the macro. Correct the error. Run the job
again.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: -

IDA008 INCOMPATIBLE SUBLIST ITEMS. xxx AND yyy, FOR keyword KEYWORD
Explanation: The sublist items specified for the keyword are incompatible.
In the message text:
xxx
yyy The specified sublist names.
keyword The keyword.
System action: The system does not expand the macro.
Application Programmer Response: Remove one of the incompatible sublist items. Run the job again.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Routing Code: Note 11

Chapter 16. IDA messages 245

IDA009 • IDA011

Descriptor Code: -

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.
In the message text:
nnn The number of control block keywords specified.
System action: The system does not expand the macro.
Application Programmer Response: Remove all but one of the control block keywords. Run the job again.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: -

IDA010 EXIT ADDRESS REQUIRED FOR keyword KEYWORD - NOT SPECIFIED

Explanation: An exit address required for the keyword was not specified.
In the message text:
keyword The keyword.
System action: The system does not expand the macro.
Application Programmer Response: Supply the required exit address. Run the job again.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: -

IDA011 keyword IS NOT A VALID xxx KEYWORD - IGNORED

Explanation: The specified keyword is not valid for the control block.
In the message text:
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.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: -

246 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDA018 • IDA020

IDA018 VTAM KEYWORD, keyword, SPECIFIED WITHOUT SPECIFYING AM=VTAM

Explanation: The specified VTAM® keyword is not valid because AM=VTAM was not specified.
In the message text:
keyword The keyword.
System action: The system does not expand the macro.
Application Programmer Response: Either remove the incorrect keyword or specify AM=VTAM. Run the job again.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: -

IDA019 KEYWORDS keyword1 AND keywd2 ARE INCOMPATIBLE

Explanation: The indicated keywords cannot be specified together.
In the message text:
keyword1

keyword2
The specified keywords.
System action: The system does not expand the macro.
Application Programmer Response: Correct the error by specifying compatible keywords. Run the job again.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Detecting Module: IDA0192V
Routing Code: Note 11
Descriptor Code: -

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.
In the message text:
xxx The specified sublist item.
keyword The keyword.
System action: The system does not expand the macro.
Application Programmer Response: Specify AM=VTAM. Run the job again.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Detecting Module: IDA0200T

Chapter 16. IDA messages 247

IDA021 • IDA024

Routing Code: Note 11

Descriptor Code: -

IDA021 keyword1 AND keywd2 KEYWORDS MUST BE SPECIFIED TOGETHER BUT ONE IS MISSING
Explanation: The keywords specified in the message text form a pair. One cannot be specified without the other.
In the message text:
keyword1

keyword2
The keywords.
System action: The system does not expand the macro.
Application Programmer Response: Supply the missing keyword or remove the one specified. Run the job again.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: -

IDA022 CONFLICTING SUBLIST ITEMS WERE SPECIFIED FOR keyword KEYWORD

Explanation: The keyword was specified with conflicting sublist items.
In the message text:
keyword The keyword.
System action: The system does not expand the macro.
Application Programmer Response: Correct the sublist item or items that are in conflict. Run the job again.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: -

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.
In the message text:
keyword The keyword.
System action: The system does not expand the macro.
Application Programmer Response: Correct the error by specifying a non-VSAM keyword. Run the job again.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: -

248 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDA025 • IDA027

IDA025 www, xxx, yyy CONFLICTING SUBPARAMETERS IN keyword KEYWORD, www ASSUMED
Explanation: More than one subparameter was specified for the indicated keyword. This is an error.
In the message text:
www
xxx
yyy The specified subparameters.
keyword The keyword.
System action: The system expands the macro using www as the default.
Application Programmer Response: Specify one of the conflicting subparameters for the keyword. Run the job
again.
System programmer response: 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 program listing, the
assembly listing, and the source input for the job.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: -

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.
In the message text:
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
Routing Code: Note 11
Descriptor Code: -

IDA027 ALL FOUR PARAMETERS: keyword1, keywd2, keywd3, AND keywd4 MUST BE SPECIFIED.
Explanation: The indicated keywords must be specified in the macro.
System action: The request ends unsuccessfully.
Application Programmer Response: Probable user error. All of the listed keywords must be specified. Check the
spelling.
Source: DFSMSdfp
Detecting Module: IDAMDVRP
Routing Code: Note 11
Descriptor Code: -

Chapter 16. IDA messages 249

250 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)
Chapter 17. IDAHC messages
IDAHC101I VSAM INDEX TRAP IS ENABLED. CHECK(IBMVSAM,VSAM_INDEX_TRAP) RAN
SUCCESSFULLY AND FOUND NO EXCEPTIONS.
Explanation: VSAM INDEX TRAP IS ENABLED.
System action: The system continues processing.
Operator response: N/A
System programmer response: None.
Problem determination: N/A
Source: DFSMS VSAM
Reference Documentation: See message IDAHC102E.
Detecting Module: IDAHCCHK

IDAHC102E VSAM INDEX TRAP IS DISABLED

Explanation: CHECK(IBMVSAM,VSAM_INDEX_TRAP) found that the VSAM Index Trap is disabled. With the
VSAM Index Trap disabled, if VSAM has a problem, a damaged index buffer may be written into DASD corrupting
the data set.
System action: The system continues processing.
Operator response: Report this problem to the system programmer.
System programmer response: Issue the following command to enable the VSAM Index Trap:
V SMS,MONDS(IGWVSAM.BASE.INDEX.TRAP),ON
Problem determination: Issue the following command to check the status of the VSAM Index Trap function:
D SMS,MONDS(IGWVSAM.BASE.VSAM.DEBUG.FEATURES)
Source: DFSMS VSAM
Reference Documentation: For additional information on the VSAM Index Trap, see:
v APAR OA15368
v z/OS DFSMSdfp Diagnosis
v z/OS DFSMS Using Data Sets.
Routing Code: Note 35
Descriptor Code: 3 is the default set by this check. See note 1.

© Copyright IBM Corp. 1988, 2012 251

252 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)
Chapter 18. IDAI messages
IDAI1001E PUT FAILED, ERROR FOUND WHILE UPDATING THE INDEX DSN:dataset_index_name
REASON:error_description
Explanation: VSAM index trap has detected an error in the current index record being updated. The current PUT
will fail with a logical error, RPL feedback X'xx08006D'. Subsequent attempts to access this data with this control
block structure will fail with logical error RPL feedback X'xx08006E' until the data set is closed and reopened.
In the message text:
dataset_index_name
The name of the failing index.
error_description
The reason why index trap hits can be any of the following errors:
v High-used greater than high-allocated
v Not valid index pointer
v Duplicate index pointer
v Out of sequence index record
v Not valid section entry
v Not valid key length
v Horizontal pointer loop
v Duplicate key
v Too many spanned-record segments.
System action: The system continues processing.
Operator response: Report this problem to the system programmer.
Application Programmer Response: Issue the EXAMINE command on the failing data set. If the EXAMINE
command returns with return code 8 or higher, the data set is corrupted and must be recovered; otherwise, no action
is required and the data set can be reopened for continued processing.
System programmer response: If the data set is shared correctly, open a PMR and submit the following items:
v The dump
v An EXAMINE ITEST NODTEST, EXAMINE DTEST NOITEST, and LISTCAT command of the data set taken after
the trap hits
v DSS prints of the index component after the trap hits

Rename and save the corrupted data set in case IBM service needs additional documentation.
Source: DFSMS VSAM
Reference Documentation: z/OS DFSMSdfp Diagnosis.
Detecting Module: IDAM19R3
Routing Code: 2 and 11
Descriptor Code: 2

IDAI1002E PUT FAILED, ERROR FOUND WHILE UPDATING THE INDEX DSN:catalog_index_name
REASON:error_description
Explanation: VSAM index trap has detected an error in the current catalog index record being updated. The current
PUT will fail with a logical error, RPL feedback X'xx08006D'. Subsequent attempts to access this data with this control
block structure will fail with logical error RPL feedback X'xx08006E' until the data set is closed and reopened.
In the message text:

© Copyright IBM Corp. 1988, 2012 253

catalog_index_name
The name of the failing catalog index.
error_description
The reason why index trap hits can be any of the following errors:
v High-used greater than high-allocated
v Invalid index pointer
v Duplicate index pointer
v Out of sequence index record
v Invalid section entry
v Invalid key length
v Horizontal pointer loop
v Duplicate key
v Too many spanned-record segments
System action: The system continues processing.
Operator response: Report this problem to the system programmer.
Application Programmer Response: Application programmer should take an EXAMINE on the failing data set. If
EXAMINE returns with return code 8 or higher, the data set is broken and needs to be recovered; otherwise, no
action is needed and the data set can be reopened for continued processing.
System programmer response: System programmer should open a PMR and submit the following items if it is
determined that the data set is being shared properly.
v The dump
v An EXAMINE ITEST NODTEST, EXAMINE DTEST NOITEST, and LISTCAT of the data set taken after the trap
hits
v DSS prints of the index component after the trap hits

Rename and save the corrupted data set in case IBM service needs additional documentation.
Source: DFSMS VSAM
Reference Documentation: z/OS DFSMSdfp Diagnosis.
Detecting Module: IDAM19R3
Routing Code: 2 and 11
Descriptor Code: 2

254 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Chapter 19. IDAT messages
IDAT0001I VSAM DYNAMIC TRACE WAS INITIALIZED SUCCESSFULLY
Explanation: VSAM dynamic trace started task, IDAVDT, was started and initialized successfully.
System action: The system continues processing.
Operator response: Operator might now issue the supported MODIFY commands against IDAVDT.
System programmer response: None
Source: DFSMS VSAM
Reference Documentation: For additional information on the VSAM dynamic trace, see z/OS DFSMSdfp Diagnosis.
Detecting Module: IDAVDTRA

IDAT0002I THE FOLLOWING TRACE ENTRIES WERE STORED SUCCESSFULLY

entry# dsname jobname type
Explanation: The READIN function of IDAVDT was completed successfully and the trace entries defined in the
parmlib member were stored successfully into the dynamic trace save area.
In the message text:
entry# The entry number that will be used for other supported MODIFY commands.
dsname The data set name that is defined in the trace entry.
jobname The job name that is defined in the trace entry.
type The type of the trace entry.
System action: The system continues processing.
Operator response: Operator might now issue the supported MODIFY commands against the stored trace entry
using the entry#.
System programmer response: None
Source: DFSMS VSAM
Reference Documentation: For additional information on the VSAM dynamic trace, see z/OS DFSMSdfp Diagnosis.
Detecting Module: IDAVDTRA

IDAT0003E ERROR FOUND WHEN PROCESSING VSAM DYNAMIC TRACE FUNCTION

FUNCTION=functions ERROR=error_reason
Explanation: IDAVDT detected error when processing VSAM dynamic trace functions. The current processing
function failed and IDAVDT continues to wait for the new command.
In the message text:
functions
The current processing VSAM dynamic trace function.
error_reason
The reason why the current function failed.
System action: The system continues processing.
Operator response: Operator should check the error_reason to determine why the request failed and adjust the
command accordingly. Operator should also notify system programmer to determine if the PARMLIB member needs
to be corrected.

© Copyright IBM Corp. 1988, 2012 255

IDAT0004I • IDAT0005I

System programmer response: System programmer should correct the trace entry in the PARMLIB member if the
error is related to the entry in the PARMLIB.
Problem determination: The functions and error_reason in the message can be use to determine why the current
function failed.
Source: DFSMS VSAM
Reference Documentation: For additional information on the VSAM dynamic trace, see z/OS DFSMSdfp Diagnosis.
Detecting Module: IDAVDTRA and IDA019SB

IDAT0004I MORE THAN THE MAXIMUM OF EIGHT ENTRIES HAVE BEEN SPECIFIED
Explanation: IDAVDT READIN function completed successfully with more than eight entries were specified in the
PARMLIB member. Only the first eight trace entry defined will be store into the dynamic trace save area and the rest
of the trace entry will be ignored.
System action: The system continues processing.
Operator response: Operator should verify whether the needed trace entries were stored into the dynamic trace
area.
System programmer response: System programmer should make changes to the parmlib member according to the
need.
Source: DFSMS VSAM
Reference Documentation: For additional information on the VSAM dynamic trace, see z/OS DFSMSdfp Diagnosis.
Detecting Module: IDAVDTRA

IDAT0005I TRACE ENTRY N=entry# HAS THE FOLLOWING PARAMETERS: TYPE=entry_type

DSNAME=dsname JOBNAME=jobname VALID=YES|NO HOOK=(hook_point[,hook_point])
PARM1=parm1 PARM2=parm2 ECODE=ecode KEY=key
Explanation: IDAVDT DISPLAY function completed successfully and the message includes the information of the
requested trace entry.
In the message text:
entry# The entry number that is specified in the DISPLAY command.
entry_type
The type of the requested entry.
dsname The data set name that is defined in the requested trace entry.
jobname The job name that is defined in the requested trace entry.
hook_point
The hook points that are defined in the requested trace entry.
parm1 The parm1 value that is defined in the requested trace entry.
parm2 The parm2 value that is defined in the requested trace entry.
ecode The ecode value that is defined in the requested trace entry.
key The key value that is defined in the requested trace entry.
System action: The system continues processing.
Operator response: Operator can verify whether the trace entry information was stored successfully.
System programmer response: System programmer should make changes to the parmlib member according to the
need.
Source: DFSMS VSAM
Reference Documentation: For additional information on the VSAM dynamic trace, see z/OS DFSMSdfp Diagnosis.
Detecting Module: IDAVDTRA

256 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDAT0006I • IDAT0009I

IDAT0006I VSAM DYNAMIC TRACE IS NOW ENDED

Explanation: IDAVDT was stopped successfully after the STOP CONSOLE command is received.
System action: The system continues processing.
Operator response: None
System programmer response: None
Source: DFSMS VSAM
Reference Documentation: For additional information on the VSAM dynamic trace, see z/OS DFSMSdfp Diagnosis.
Detecting Module: IDAVDTRA

IDAT0007I TRACE ENTRY N=entry# IS ENTRY

Explanation: IDAVDT DISPLAY command is involved but the requested entry is empty.
In the message text:
entry# The entry number of the requested entry.
System action: The system continues processing.
Operator response: None
System programmer response: None
Source: DFSMS VSAM
Reference Documentation: For additional information on the VSAM dynamic trace, see z/OS DFSMSdfp Diagnosis.
Detecting Module: IDAVDTRA

IDAT0008I READIN COMPLETED. TABLE NOW CONTAIN NO ENTRY

Explanation: IDAVDT READIN function completed successfully with a PARMLIB member containing no entry.
System action: The system continues processing.
Operator response: None
System programmer response: None
Source: DFSMS VSAM
Reference Documentation: For additional information on the VSAM dynamic trace, see z/OS DFSMSdfp Diagnosis.
Detecting Module: IDAVDTRA

IDAT0009I TRACE ENTRY=entry# WAS ENABLED SUCCESSFULLY

Explanation: IDAVDT ENABLE command was completed successfully to enable the data set that is specified by the
user in the trace entry.
In the message text:
entry# The entry number of the requested entry.
System action: The system continues processing.
Operator response: None
System programmer response: None
Source: DFSMS VSAM
Reference Documentation: For additional information on the VSAM dynamic trace, see z/OS DFSMSdfp Diagnosis.
Detecting Module: IDA019SB

Chapter 19. IDAT messages 257

IDAT0010I • IDAT0013I

IDAT0010I TRACE ENTRY=entry# WAS DISABLED SUCCESSFULLY

Explanation: IDAVDT ENABLE command was completed successfully to disable the data set that is specified by the
user in the trace entry.
In the message text:
entry# The entry number of the requested entry.
System action: The system continues processing.
Operator response: None
System programmer response: None
Source: DFSMS VSAM
Reference Documentation: For additional information on the VSAM dynamic trace, see z/OS DFSMSdfp Diagnosis.
Detecting Module: IDA019SB

IDAT0011I TRACE ENTRY=entry#|ALL WAS VALIDATED SUCCESSFULLY

Explanation: IDAVDT VALIDATE command was completed successfully and the requested entry was now valid.
In the message text:
entry# The entry number of the requested entry.
System action: The system continues processing.
Operator response: None
System programmer response: None
Source: DFSMS VSAM
Reference Documentation: For additional information on the VSAM dynamic trace, see z/OS DFSMSdfp Diagnosis.
Detecting Module: IDAVDTRA

IDAT0012I TRACE ENTRY=entry#|ALL WAS INVALIDATED SUCCESSFULLY

Explanation: IDAVDT INVALIDATE command was completed successfully and the requested entry was now
invalid.
In the message text:
entry# The entry number of the requested entry.
System action: The system continues processing.
Operator response: None
System programmer response: None
Source: DFSMS VSAM
Reference Documentation: For additional information on the VSAM dynamic trace, see z/OS DFSMSdfp Diagnosis.
Detecting Module: IDAVDTRA

IDAT0013I ALL TRACE ENTRIES STATUS REMAIN UNCHANGED

Explanation: IDAVDT was stopped without invalidating all trace entries that was stored in the dynamic trace save
area because the user has specified the KEEP option when issuing the READIN command. All trace entries status
will remain unchanged.
System action: The system continues processing.
Operator response: None
System programmer response: None

258 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Source: DFSMS VSAM
Reference Documentation: For additional information on the VSAM dynamic trace, see z/OS DFSMSdfp Diagnosis.
Detecting Module: IDAVDTRA

Chapter 19. IDAT messages 259

260 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)
Chapter 20. IDC messages
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS cde
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.
In the message text:
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.
In the message text:
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.
In the message text:
nnn Depending on the command, nnn indicates the following:
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 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.
System action: The system continues processing.
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.
In the message text:
cde The condition code, as follows:
4 Attention message. The system will complete processing.

© Copyright IBM Corp. 1988, 2012 261

IDC0018I • IDC0063I

8 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
Detecting Module: IDCAL01, IDCBI01, IDCCC01, IDCDE01, IDCDL01, IDCLC01, IDCMP01, IDCRM01, IDCRS05,
IDCVY01, IDCXP01

IDC0018I UNABLE TO OBTAIN SERIALIZATION TO DEFINE PAGESPACE

Explanation: An attempt was made to define a pagespace, but an outstanding ENQ was found for the named
pagespace. This indicates that the pagespace may currently be in use by this or another system.
System action: The DEFINE is not performed.
User response: None
Operator response: None
Application Programmer Response: None
System programmer response: Verify that the name of the pagespace is not currently an active pagespace on any
system that shares the volume on which the pagespace is located. Change the name of the pagespace to be defined.
Source: IDCAMS
Detecting Module: IDCDE01

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.
In the message text:
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.
System action: The command continues processing.
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.

262 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0064I • IDC0068I

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.

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.
System 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 problem reporting data bases for a fix for the problem. If no fix 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.
System action: The command continues processing.
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.
In the message text:
nnn The number of backup copies that exceed the maximum.
System action: The command continues processing.
Application Programmer Response: The excess backup copies are scratched by:
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.

Chapter 20. IDC messages 263

IDC0073I • IDC0086I

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:
v The volume is being assigned to a different group
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
System action: The command continues processing.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCMV01

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.
In the message text:
csn The cartridge serial number.
volser The volume serial number.
jobname The jobname.
sss The stepname.
System action: The command continues processing.
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.
In the message text:
msn The cartridge serial numbers of the sequence one and sequence two cartridges.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCEV01, IDCCO01, IDCSR01

IDC0086I text UPDATED IN VOLUME LABEL

Explanation: text is one of the following:
SERIAL
OWNER
SERIAL, OWNER

The volume serial number, the owner name, or both was changed in the volume label.
System action: The command continues processing.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCMV01, IDCSR01

264 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0088I • IDC0105I

IDC0088I 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.
In the message text:
csn The cartridge serial number.
yyddd The date on which the cartridges were scratched.
System action: The command continues processing.
Source: DFSMSdfp
Detecting Module: IDCCO01, IDCSV01

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.
In the message text:
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
Detecting Module: IDCCO01, IDCRV01, IDCSV01

IDC0102I NO ACTIVE NON-GROUPED VOLUMES IN THE INVENTORY DATA SET

Explanation: There are no non-grouped, active mass storage volumes in the inventory data set.
System action: The system abnormally ends the command. The system returns a reason code from the Mass Storage
Volume Control functions.
Source: DFSMSdfp
Detecting Module: IDCLD01, IDCSD01

IDC0104I 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'.
System action: The system abnormally ends the command.
Source: DFSMSdfp
Detecting Module: IDCLD01, 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.
In the message text:

Chapter 20. IDC messages 265

IDC0106I • IDC0117I

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

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

IDC0107I NO DATA SETS ELIGIBLE FOR SELECTION ON VOLUME volser

Explanation: No data sets on the indicated volume met the criteria specified on the command for either listing or
scratching.
System action: If there are more volumes to be processed, the system processes the next volume. Otherwise, the
system abnormally ends the command.
Source: DFSMSdfp
Detecting Module: IDCLD01, IDCSD01

IDC0112I 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.
Source: DFSMSdfp
Detecting Module: IDCSD01

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.

In the message text:

volser The volume serial number.
grpname
The group name.
System action: The system continues processing; however, the system does not process the volume.
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.
Source: DFSMSdfp
Detecting Module: IDCMV01, IDCSR01

266 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0140I • IDC0181I

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.
System action: The system continues processing with the export of the integrated catalog facility catalog.
Source: DFSMSdfp

IDC0144I VOLUME SERIAL FOR catname DURING EXPORT DISCONNECT WAS volser
Explanation: This is an informational message indicating the volume serial number for the volume that contains the
catalog being disconnected.
In the message text:
catname The name of the catalog being disconnected.
volser The volume serial number.
System action: The system continues processing.
Source: DFSMSdfp

IDC0180I PASSWORD SPECIFICATION FOR entryname 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.
In the message text:
entryname
The entry name.
System action: The system maintains the passwords.
Application Programmer Response: Do not specify passwords.
Source: DFSMSdfp
Detecting Module: IDCAL01, IDCDE01, IDCMP01

IDC0181I construct USED IS constnme

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:
v DATACLASS
v MANAGEMENTCLASS
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.

In the message text:

construct
The construct.
constnme
The construct name.
System action: The system continues processing.
Source: DFSMSdfp

Chapter 20. IDC messages 267

IDC0182I • IDC0206I

Detecting Module: IDCDE01, IDCMP01

IDC0182I EXPIRATION DATE RESET TO yyyy.ddd

Explanation: The system issues this message for one of the following reasons:
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.
Operator response: None.
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
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

In the message text:

dsname The data set name.
action Indicates whether the GDS was recataloged, uncataloged or deleted.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCAL01

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.
System programmer response: If the problem 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI03

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.
Application Programmer Response: Remove the extra comma.

268 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0222I • IDC0254I

System programmer response: If the error recurs and the calling 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 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.
System programmer response: If the error recurs and the calling 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 SYSOUT output for
the job.
Source: DFSMSdfp
Detecting Module: IDCRI01

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.
Application Programmer Response: Correct the syntax of the parameters.
System programmer response: If the error recurs and the calling 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 SYSOUT output for
the job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC0234I WARNING: TOO FEW RIGHT PARENTHESES FOUND AT END OF COMMAND

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 system continues processing.
Application Programmer Response: Correct the syntax of the parameters.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

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

Chapter 20. IDC messages 269

IDC0339I • IDC0361I

on the IDCAMS completion message, IDC0002I. Perform the programmer response from message IDC0002I.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: -

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.
In the message text:
keyname
The key name.
keyval The key value.
System action: The system continues processing.
Application Programmer Response: Save the key value for use when the data set is deciphered.
Source: DFSMSdfp
Detecting Module: IDCIO01

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.
In the message text:
keyval The key value.
System action: The system continues processing.
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.
In the message text:
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.
System programmer response: If the error recurs and the program is not in error, look at the messages in 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

270 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0362I • IDC0363I

Detecting Module: IDCSA07

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.
In the message text:
dsname The data set name.
System action: The command continues to scratch and uncatalog remaining eligible data sets.
Application Programmer Response: Correct the error identified in the preceding message and do one of the
following:
v Run the SCRDSET command again
v Specify DELETE in the DISP parameter on the DD statement to scratch the data set
v Run the DELETE command to scratch the data set
System programmer response: If the error recurs and the program is not in error, look at the messages in 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 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 SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCSA07

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.

In the message text:

dsname The data set name.
System action: The command continues to scratch and uncatalog remaining eligible data sets. The system explains
the error with a preceding message.
Application Programmer Response: Correct the 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:
v Specify UNCATLG in the DISP parameter on the DD statement to uncatalog the data set.
v Run the DELETE command to uncatalog the data set.
v Run the IEHPROGM utility to uncatalog the data set.

If the data set was not scratched from the VTOC, do one of the following:
v Run the SCRDSET command again.
v Specify DELETE in the DISP parameter on the DD statement to scratch the data set.
v Run the DELETE command to scratch the data set.

Chapter 20. IDC messages 271

IDC0394I • IDC0397I

v Run the IEHPROGM utility to scratch and uncatalog the data set.
System programmer response: If the error recurs and the program is not in error, look at the messages in 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 reporting data bases for a fix for the problem. If no fix exists,
contact the IBM Support Center. Provide the JCL, the SYSOUT output, and all printed output and output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA07

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.
In the message text:
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 system continues processing.
Application Programmer Response: Correct the problem indicated by the Mass Storage System (MSS) reason codes.
Then issue the UNLOAD command.
Source: DFSMSdfp
Detecting Module: IDCSA06, IDCSA10
Routing Code: 1
Descriptor Code: 4

IDC0396I ** dsname NOT RECATALOGED

Explanation: The data set was not recataloged. The system writes a preceding message that explains the reason for
the error.
In the message text:
dsname The data set name.
System action: The command continues processing.
Application Programmer Response: Examine the preceding message for response.
Source: DFSMSdfp
Detecting Module: IDCSA07

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.
System action: The command continues processing.
Application Programmer Response: Use the access method services LISTCAT, DELETE, and DEFINE commands to

272 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0398I • IDC098D

determine the fields defined in the entry. Delete the entry and redefine the entry with the new device type.
System programmer response: If the error recurs and the program is not in error, look at the messages in 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.
If the error cannot be determined, 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, and all printed output and output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA07

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.
System action: The command continues processing.
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.
System programmer response: If the error recurs and the program is not in error, look at the messages in 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.
If the error cannot be determined, 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, and all printed output and output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA07

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.
In the message text:
jobname The jobname.
stepname
The job step.
System action: The system continues processing.
Operator response: Remove the cartridge from the cartridge access station.
Source: DFSMSdfp
Routing Code: 1
Descriptor Code: 3

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).
In the message text:
text STAGING PACK VTOCHEADER VTOC.

Chapter 20. IDC messages 273

IDC0508I • IDC0510I

volser The volume serial number.

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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD07

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.
In the message text:
ser The volume serial number.
return-code The return code. A 0 indicates success.
System action: The system continues processing.
Application Programmer Response: See message IDC3009I for a complete explanation of the return code.
Source: DFSMSdfp
Detecting Module: IDCDE01, IDCMP01, IDCRM01

IDC0509I INDEX ALLOCATION STATUS FOR VOLUME volser IS return-code

Explanation: The system indicates the allocation status for a volume containing the index component. The code
indicating the status is the virtual storage access method (VSAM) catalog return code.
In the message text:
ser The volume serial number.
return-code The return code. A 0 indicates success.
System action: The system continues processing.
Application Programmer Response: See message IDC3009I for a complete explanation of the return code.
Source: DFSMSdfp
Detecting Module: IDCDE01, IDCMP01, IDCRM01

IDC0510I CATALOG ALLOCATION STATUS FOR VOLUME volser IS return-code

Explanation: The system indicates the allocation status of a volume containing the virtual storage access method
(VSAM) catalog. The code indicating the status is the VSAM catalog return code.
In the message text:
ser The volume serial number.
return-code The return code. A 0 indicates success.
System action: The system continues processing.
Application Programmer Response: See message IDC3009I for a complete explanation of the return code.
Source: DFSMSdfp
Detecting Module: IDCDE01

274 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0511I • IDC0526I

IDC0511I SPACE ALLOCATION STATUS FOR VOLUME volser IS return-code

Explanation: The system indicates the allocation 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.
In the message text:
ser The volume serial number.
return-code The return code. A 0 indicates success.
System action: The system continues processing.
Application Programmer Response: See message IDC3009I for a complete explanation of the return code.
Source: DFSMSdfp
Detecting Module: IDCDE01

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.
In the message text:
x Either a D or an I. It indicates which component the data set names.
dsname The data set name.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCDE01

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.
In the message text:
ser The volume serial number.
System action: The system continues processing.
Application Programmer Response: Mount the named volume for any future operation that modifies the catalog
entry for the object just defined.
Source: DFSMSdfp
Detecting Module: IDCDE01, IDCMP01, IDCRM01

IDC0526I ALTERED ALLOCATION STATUS FOR VOLUME volser IS return-code

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.
In the message text:
ser The volume serial number.
return-code The return code. See message IDC3009I for an explanation of the return code.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCAL01

Chapter 20. IDC messages 275

IDC0531I • IDC0548I

IDC0531I ENTRY xxx ALTERED

Explanation: The system writes this message to indicate that the specified entry has been successfully altered.
In the message text:
xxx The altered entry.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCAL01

IDC0532I ** ENTRY xxx NOT ALTERED

Explanation: The system writes this message to indicate that the entry was not altered.
In the message text:
xxx The unaltered entry.
System action: The preceding message in the system output indicates the reason the entry was not altered. The
system continues processing.
Application Programmer Response: Correct the problem indicated by the previous message. Run the command
again.
Source: DFSMSdfp
Detecting Module: IDCAL01

IDC0534I ** MEMBER mem NOT RENAMED

Explanation: The system writes this message to indicate the member name that was not renamed.
In the message text:
mem The member name.
System action: The preceding message in the system output indicates the reason the member name was not
renamed. The system continues processing.
Application Programmer Response: Correct the problem indicated by the previous message. Run the command
again.
Source: DFSMSdfp
Detecting Module: IDCAL01

IDC0535I MEMBER mem RENAMED

Explanation: The indicated member has been successfully renamed.
In the message text:
mem The indicated member.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCAL01

IDC0548I ** MEMBER mem NOT DELETED

Explanation: The system writes this message to inform the operator or programmer that the member was not
deleted.
In the message text:
mem The indicated member.

276 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0549I • IDC0551I

System action: An associated message accompanies this message indicating why the member was not deleted. The
system continues processing.
Source: DFSMSdfp
Detecting Module: IDCDL01

IDC0549I MEMBER mem DELETED

Explanation: The system writes this message to indicate the member that has been successfully deleted.
In the message text:
mem The deleted member.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCDL01

IDC0550I ENTRY (x) dsname DELETED

Explanation: The specified data set name entry was deleted from the virtual storage access method (VSAM) catalog.
In the message text:
dsname The data set name.
x 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 system continues
processing.
Source: DFSMSdfp
Detecting Module: IDCDL01, IDCMP01, IDCRM01, IDCXP01

IDC0551I ** ENTRY dsname NOT DELETED

Explanation: The system writes this message to indicate that the entry that was not deleted. An accompanying
message will indicate why the entry was not deleted.
In the message text:
dsname The data set name.
System action: The named data set is not deleted.
Application Programmer Response: Correct the cause of the error.
System 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 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

Chapter 20. IDC messages 277

IDC0552I • IDC0594I

Detecting Module: IDCDL01, IDCXP01

IDC0552I THE ENTRY IS NOT A USERCATALOG WHILE THE REQUEST WAS TO DELETE A
USERCATALOG
Explanation: The system writes this message to indicate that the request was rejected, because user asked to delete a
USERCATALOG entry, and the entry specified in the request is not a USERCATALOG.
System action: The named entry is not deleted.
Application Programmer Response: Correct the cause of the error.
System programmer response: If the error recurs and the program is not in error, see the messages in the job log for
more information. 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
Detecting Module: IDCDL01, IDCDL02

IDC0553I ALL MEMBERS IN DATA SET dsname DELETED

Explanation: The system writes this message to indicate that all members in a PDS or PDSE have been successfully
deleted.
In the message text:
dsname The PDS or PDSE data set name.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCDL01

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.
In the message text:
ser The volume serial number.
System action: The volume is still owned by the catalog in which it was originally defined.
Source: DFSMSdfp
Detecting Module: IDCDL01

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.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCRP01

IDC0594I 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.
In the message text:

278 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0603I • IDC0622I

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 system continues processing.
Source: DFSMSdfp
Detecting Module: IDCXP01

IDC0603I CONNECT FOR USER CATALOG dsname SUCCESSFUL

Explanation: This message identifies the name of the catalog for which CONNECT completed successfully.
In the message text:
dsname The data set name.
System action: The system continues processing.
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.
In the message text:
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.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCMP01, IDCRM01

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
Detecting Module: IDCMP01

IDC0622I USERCATALOG catname DISCONNECTED

Explanation: A caller's catalog has been disconnected by IMPORTRA in order to connect a new pointer to the user
catalog.
In the message text:
catname The catalog name.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCRM01

Chapter 20. IDC messages 279

IDC0626I • IDC0637I

IDC0626I IMPORTRA SUCCEEDED FOR dsname

Explanation: The data set has been successfully imported.
In the message text:
dsname The data set name.
System action: Normal processing continues.
Source: DFSMSdfp
Detecting Module: 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.
In the message text:
nnn The number of entries converted.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCCC01

IDC0635I ** dsname NOT CONVERTED

Explanation: During CNVTCAT processing, the catalog entry data set was not converted.
In the message text:
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
Detecting Module: IDCCC01

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.
In the message text:
nnn The number of entries updated.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCCC01

IDC0637I ** dsname NOT UPDATED

Explanation: The operating system (OS) catalog entry specified was not converted.
In the message text:
dsname The data set name.

280 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0639I • IDC0659I

System action: An accompanying message contains the information required to correct the error. The system
continues processing.
Source: DFSMSdfp
Detecting Module: IDCCC01

IDC0639I SPHERE CONVERSION STARTED FOR dsname

Explanation: The conversion of the specified base sphere and its associations has started.
In the message text:
dsname The data set name.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCCC01

IDC0652I dsname SUCCESSFULLY BUILT

Explanation: Building of the alternate index identified by the data set name has been successfully completed with
no errors encountered.
In the message text:
dsname The data set name.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCBI01

IDC0657I REQUIRED SORT PRODUCT FUNCTIONS UNAVAILABLE

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.
Detecting Module: IDCBI01

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.
In the message text, reason-code is:
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

Chapter 20. IDC messages 281

IDC0665I • IDC0672I

IDC0665I 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

In the message text:

nnn The number of entries miscompared.
System action: The system continues processing.
Application Programmer Response: Determine 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.
In the message text:
ser The volume serial number.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCRC01

IDC0670I DATA SET SUCCESSFULLY EXPORTED

Explanation: The data set named in message IDC0674I was successfully retrieved and written to the portable data
set.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCRC01

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.
In the message text:
catname The catalog name.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCRC01

282 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0674I • IDC0686I

IDC0674I ** NAME IS dsname

Explanation: This second-level message gives the data set name of the object referred to in the preceding messages.
In the message text:
dsname The data set name.
System action: See the primary message.
Application Programmer Response: See the primary message.
Source: DFSMSdfp
Detecting Module: IDCRC01

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.
In the message text:
date Date on which data set was created.
time Time at which data set was created.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCRC01

IDC0680I VOLUME volser CREATED ON CARTRIDGES csn1 csn2

Explanation: A new volume was created.
In the message text:
volser The volume serial number.
csn1
csn2 The cartridge serial numbers.
System action: The command continues processing.
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.
In the message text:
volser The volume serial number.
System action: The command ends normally.
Application Programmer Response: Correct the error indicated in a preceding message. Run the command again.
Source: DFSMSdfp
Detecting Module: IDCCV01

Chapter 20. IDC messages 283

IDC0703I • IDC0711I

IDC0703I ** VOL volser COPIES TO CART csn1 csn2, DATE yyddd

Explanation: The volume was copied to the cartridges on the date indicated.
In the message text:
volser The volume serial number.
csn1
csn2 The cartridge serial numbers.
yyddd The date, in year and days.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCCO01

IDC0704I ** 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.
In the message text:
yyddd The date, in year and days.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCCO01

IDC0705I ** CARTRIDGES OF AN INCOMPLETE COPY VOLUME SELECTED FOR REUSE

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.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCCO01

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.
In the message text:
volser1 The volume serial number of the restored volume.
volser2 The volume serial number of the restoring volume.
yyddd The date, in year and days.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCRV01

284 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0722I • IDC0733I

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.
In the message text:
volser The volume serial number.
System action: The system continues processing.
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 ** 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.
In the message text:
volser The volume serial number.
System action: The system continues processing.
Application Programmer Response: Run the MODIFYV command to change the volume serial number of the active
volume. Correct the problem as indicated in the preceding message.
Source: DFSMSdfp
Detecting Module: IDCAV01

IDC0725I READWRITE ATTRIBUTE SET FOR VOLUME volser

Explanation: The volume is assigned the readwrite attribute as requested.
In the message text:
volser The volume serial number.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCAV01

IDC0731I VOLUME volser HAS BEEN MADE INACTIVE

Explanation: The designated volume was successfully deactivated and made nonmountable.
In the message text:
volser The volume serial number.
System action: The system continues processing.
Source: DFSMSdfp
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

Chapter 20. IDC messages 285

IDC0737I

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.
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 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 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.
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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSR01

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.

286 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0743I • IDC0748I

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.
System action: The command abnormally ends with an error message indicating the severity of the problem.
Application Programmer Response: If the 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCN01

IDC0743I FROM VOLUME COPIED TO THE TO VOLUME

Explanation: The source volume was successfully copied to the target volume.
System action: The command continues processing.
Source: DFSMSdfp
Detecting Module: IDCCN01

IDC0746I 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.
System action: The command continues processing.
Source: DFSMSdfp
Detecting Module: IDCCN01

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.
System action: The command continues processing.
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.
System action: The command continues processing.
Source: DFSMSdfp

Chapter 20. IDC messages 287

IDC0749I • IDC0780I

Detecting Module: IDCCN01

IDC0749I VTOC OF FROM VOLUME SCRATCHED

Explanation: The volume table of contents (VTOC) of the source volume was successfully scratched.
System action: The command continues processing.
Source: DFSMSdfp
Detecting Module: IDCCN01

IDC0751I CARTS csn1 csn2 SCRATCHED FOR VOLUME volser

Explanation: The requested volume was scratched. The cartridge IDs in the message are in reverse order from the
order in which they were scratched.
In the message text:
volser The volume serial number.
csn1
csn2 The cartridge serial numbers of the cartridges that were scratched.
System action: The command continues processing.
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.
In the message text:
yyddd The date, in year and days.
System action: The command continues processing.
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.
In the message text:
volser The volume serial number.
System action: The command continues processing.
Source: DFSMSdfp
Detecting Module: IDCRR01

IDC0780I SCRATCH CARTRIDGE csn EJECTED

Explanation: A scratch cartridge was ejected from the Mass Storage Facility (MSF).
In the message text:
csn The cartridge serial number.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCEC01

288 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0781I • IDC0791E

IDC0781I NUMBER OF SCRATCH CARTRIDGES EJECTED IS nnn

Explanation: A number of scratch cartridges were ejected successfully from the library.
In the message text:
nnn The number of scratch cartridges ejected.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCEC01

IDC783E SCRATCH CARTRIDGE csn EJECTED; jjj sss

Explanation: A scratch cartridge was ejected from the Mass Storage Facility (MSF).
In the message text:
csn The cartridge serial number.
jjj The jobname.
sss The job step.
System action: The system continues processing.
Operator response: Remove the scratched cartridge from the Cartridge Access Station and label it as a scratch
cartridge.
Source: DFSMSdfp
Routing Code: 1
Descriptor Code: 3

IDC0790I CARTRIDGE csn1 REPLACED BY CARTRIDGE csn1

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.
In the message text:
csn1 The cartridge serial number of the replaced cartridge.
csn2 The cartridge serial number of the replacing cartridge.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCRL01

IDC0791E 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.
In the message text:
csn The cartridge serial number.
UNIDENTIFIED
The cartridge serial number could not be identified.

Chapter 20. IDC messages 289

IDC0810I • IDC0813I

jjj The jobname.

sss The job step.
System action: The system continues processing.
Operator response: Remove the cartridge from the Cartridge Access Station and label it as an old or defective
cartridge.
Source: DFSMSdfp
Routing Code: 1
Descriptor Code: 3

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.
In the message text:
ser The volume serial number.
System action: The system begins processing of data sets on the volume.
Source: DFSMSdfp
Detecting Module: IDCSD01

IDC0811I dsname UNCATALOGED

Explanation: The data set entry was successfully removed from the catalog.
In the message text:
dsname The data set name.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCSD01

IDC0812I nnn DATA SETS WERE SCRATCHED FROM VOLUME volser

Explanation: The number of data sets scratched from the indicated volume is specified.
In the message text:
nnn The number of the data sets scratched.
ser The volume serial number.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCSD01

IDC0813I nnn CATALOGED GDG TYPE DATA SETS WERE NOT SCRATCHED
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.
In the message text:
nnn The number of the data sets that were not scratched.
System action: The system continues processing with the next volume.
Application Programmer Response: If the data sets must be scratched, use one of the following methods to scratch
them:

290 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0814I • IDC0817I

v Run the IEHPROGM utility.

v Run the DELETE command.
v Specify DELETE in the DISP parameter on the DD statement.
Source: DFSMSdfp
Detecting Module: IDCSD01

IDC0814I nnn CATALOGED MULTI-VOLUME DATA SETS WERE NOT SCRATCHED

Explanation: The number of cataloged multivolume data sets that were not scratched is specified. The SCRDSET
command does not scratch multivolume cataloged data sets.
In the message text:
nnn The number of multi-volume data sets that were not scratched.
System action: The system continues processing with 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
Detecting Module: IDCSD01

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.
In the message text:
ser The volume serial number.
grpname
The group name.
System action: The system processes the volume.
Source: DFSMSdfp
Detecting Module: IDCSD01

IDC0816I SYSCTLG DATA SET NOT SCRATCHED

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.
System action: The system continues processing with 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
Detecting Module: IDCSD01

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.
In the message text:

Chapter 20. IDC messages 291

IDC0832I • IDC0862I

grpname
The group name.
System action: If any groups remain to be processed, the system continues processing with the next group. If no
groups remain to be processed, the system abnormally ends the command.
Source: DFSMSdfp
Detecting Module: IDCSD01

IDC0832I NO text RECORDS EXIST IN THE INVENTORY

Explanation: text is one of the following:
BASE VOLUME
DUPLICATE VOLUME
NON—GROUPED VOLUME
CARTRIDGE INDEX
PLACE HOLDER
GROUP SCRATCH
GROUP CATALOG

No records of the type requested exist in the inventory.

System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCLV01
ICBVUT02

IDC0855I CHANGE OF prm SUCCESSFUL

Explanation: The specified TUNE command parameter was successfully changed.
In the message text:
prm The specified parameter.
System action: The command continues processing.
Source: DFSMSdfp
Detecting Module: IDCTU01

IDC0861I 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 DUPLICATE SELECTED CHECKID xxxxxxxx

Explanation: The same checkid was selected by the user more than once.
In the message text:
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.
Source: DFSMSdfp

292 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0863I • IDC0896I

Detecting Module: IDCCK01

IDC0863I DUPLICATE CHECKPOINT ENTRY xxxxxxxx

Explanation: A duplicate entry was found for a user-selected checkid already.
In the message text:
xxxxxxxx
The duplicated checkpoint entry.
System action: Normal processing continues.
Source: DFSMSdfp
Detecting Module: IDCCK01

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
Detecting Module: IDCLR01

IDC0877I 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.
In the message text:
nnn The number of records miscompared.
System action: The system continues processing.
Application Programmer Response: Determine whether recovery is required.
Source: DFSMSdfp
Detecting Module: IDCLR01

IDC0888I ** 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
Detecting Module: IDCRC01

IDC0896I MIGRATED ENTRY dsname DELETED

Explanation: The migration utility deleted the specified data set.
In the message text:
dsname The data set name.
System action: The system continues processing.

Chapter 20. IDC messages 293

IDC0922I • IDC0925I

Source: DFSMSdfp
Detecting Module: IDCDL01

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.
In the message text:
xxx The specified dump element.
System action: The system ignores the dump element.
Application Programmer Response: Correct the length and/or type of the specified dump element.
Source: DFSMSdfp
Detecting Module: IDCDB02

IDC0923I ‘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.
v Is an array header within an existing array specification.

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.
Application Programmer Response: Correct the fields of the specified array header.
Source: DFSMSdfp
Detecting Module: IDCDB02

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.
In the message text:
mac The macro entry point.
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
Detecting Module: IDCDB01

IDC0925I DUMP xxx PRODUCED AT DUMP POINT ‘mac’

Explanation: A dump was requested and produced at the specified UDUMP macro.
In the message text:
xxx The dump identifier.
mac The macro entry point.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCDB01

294 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC0932I • IDC0974I

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.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCSA11

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.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCSA11

IDC0935I STORAGE MANAGEMENT SUBSYSTEM DOES NOT EXIST.

Explanation: The system does not recognize the storage management subsystem (SMS) as a valid subsystem.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCSA11

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).
In the message text:
nnn The number of tracks.
System action: The command continues processing.
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 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.
In the message text:
volser The volume serial number.
System action: The system continues processing.
Application Programmer Response: Correct the error specified in the previous message. Run the command again to
set or clear the date-last-used field.

Chapter 20. IDC messages 295

IDC1002I • IDC01037I

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 problem. If no
fix exists, contact the IBM Support Center. Provide the JCL, the SYSOUT output for the job, and all printed output
and output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCVS03

IDC1002I RESETCAT CATALOG catname VOL volser LEVEL timestmp

Explanation: This message indicates the catalog to be reset and the time stamp on the volume.
In the message text:
catname The catalog name.
volser The volume serial number.
timestmp
The time stamp on the volume.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCRS01

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.
In the message text:
volser The volume serial number.
timestmp
The time stamp on the volume.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCRS01

IDC01037I catname HAS BEEN RESET

Explanation: This message indicates that RESETCAT processing has been completed for the indicated catalog.
In the message text:
catname The catalog name.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCRS01

296 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC01049I • IDC1116I

IDC01049I NON-VSAM/USERCATALOG ENTRIES MOVED TO NEW CATALOG'S 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 catalog's volume to the CRA on the new catalog's volume.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCRS01

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 Storage Volume Control Journal
data set.
In the message text:
cde The reason code returned from the Mass Storage System Communicator.
System action: The command continues processing. 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp

IDC1116I ERROR UPDATING CARTRIDGE LABEL: text

Explanation: text is one of the following:
VOLUME=volser, SEQ=nnn
CSN=csn [,CSN=csn2]

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.

In the message text:

volser The volume serial number.
nnn The sequence number.
csn
csn2 The cartridge serial numbers.
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

Chapter 20. IDC messages 297

IDC01120I • IDC01122I

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

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.
In the message text:
field The inconsistent field.
System action: The system continues processing.
Application Programmer Response: Investigate the 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.
System programmer response: 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 all printed output and output
data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCH04

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.
In the message text:
field The duplicated field.
System action: The system continues processing.
Application Programmer Response: Investigate the 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.
System programmer response: 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 all printed output and output
data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCH04

IDC01122I 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.
In the message text:
nnn The sum of individual counts.
counts The specified counts.
table The specified table.
System action: The system continues processing.

298 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC01123I • IDC01124I

Application Programmer Response: Investigate the 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, run the CHECKMSS command again.
System programmer response: 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 all printed output and output
data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCH04

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.
In the message text:
value The specified value.
table The table containing the field.
index The index that identifies the table.
System action: The system continues processing.
Application Programmer Response: See the programmer response for the primary message.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center. Provide all printed output and output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCH04

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.
In the message text:
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.
System action: The system continues processing.
Application Programmer Response: Investigate the inconsistency. Issue the DUMPMSS, LISTMSF, or LISTMSVI
command to obtain dumps of the tables with the inconsistency. If there is any doubt whether the inconsistency is
temporary or not, run the CHECKMSS command again.
System programmer response: 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 all printed output and output
data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCH04

Chapter 20. IDC messages 299

IDC1141I • IDC1178I

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.
System action: The system continues processing using EXPORT RECORDMODE.
Application Programmer Response: Verify the attributes of the data set the system is exporting.
Source: DFSMSdfp

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
Detecting Module: IDCXP0

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.
System action: The command ends normally.
Source: DFSMSdfp
Detecting Module: IDCAU03

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.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCXP01

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

300 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC01190I • IDC1252I

IDC01190I CARTRIDGE csn IS NOW A SCRATCH CARTRIDGE

Explanation: The cartridge with the specified cartridge serial number is now a scratch cartridge.
In the message text:
csn the cartridge serial number of the scratched cartridge.
System action: The system continues processing.
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.
In the message text:
dsname The data set name.
System action: REPAIRV DISPLAY/COPY ends. Control returns to access method services. The return code is 0.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD02
IDCRD06

IDC01236I TRACK cchh WAS DEBLOCKED INTO nnn RECORDS

Explanation: The DEBLOCK function has deblocked the R‘0/R’1 pair into a number of records (including R0).
In the message text:
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD04

IDC1252I 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.
System programmer response: 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 all printed output and output
data sets related to the problem and the control statements for the job.
Source: DFSMSdfp
Detecting Module: IDCRI04

Chapter 20. IDC messages 301

IDC01360I • IDC01381I

IDC01360I 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.
System action: The system continues processing.
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.
In the message text:
dscbname
The DSCB name.
System action: The system continues processing the current command.
Source: DFSMSdfp
Detecting Module: IDCDA02

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.
Detecting Module: IDCDA01

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.
In the message text:
dsname The specified data set name.
System action: The system continues processing the current command.
Application Programmer Response: Because the VVR may not correctly describe the extent of the data set, do the
following:
1. Copy the data set to a new data set.
2. Verify the correct number of records were copied.
3. Delete the old data set.
If the correct number of records was not copied, other methods will be required to restore the data set.
Source: DFSMSdfp

302 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC01402I • IDC01460I

IDC01402I SPHERE CONVERSION COMPLETED FOR dsname

Explanation: The conversion of the specified base sphere and its associations has completed successfully.
In the message text:
dsname The data set name.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCCC01

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 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.
In the message text:
dsname The data set name.
System action: The system continues processing with the next base object.
Application Programmer Response: Another message will give the name of the object and the reason it could not
be defined. Correct this problem. Run the job again.
Source: DFSMSdfp
Detecting Module: IDCCC01

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 volume's 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.
In the message text:
volser The volume serial number.
System action: The system continues processing if the delete of the volume's VSAM data space is successful.
Source: DFSMSdfp
Detecting Module: IDCCC01

IDC1412I 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 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.
In the message text:
nnn The number of entries merged.
System action: Normal processing continues.
Source: DFSMSdfp

Chapter 20. IDC messages 303

IDC01500I • IDC1544I

Detecting Module: IDCRP01

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.
In the message text:
volser The volume serial number.
System action: The system performed the I/O operation without error.
Source: DFSMSdfp
Detecting Module: IDCSS03

IDC1502I 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.
System action: The system continues processing. The passwords are not modeled.
Application Programmer Response: If the 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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCDE02

IDC1543I NEW KEYS AND/OR RECORDSIZE VALUES EQUAL TO PRIOR DEFAULT VALUES.
Explanation: The ALTER command specified the 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.
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 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 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
Detecting Module: IDCAL01

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

304 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC01551I • IDC01552I

Application Programmer Response: If the specified values are not correct, run an ALTER command to correct the
values.
System 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 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
Detecting Module: IDCAL01

IDC01551I type CACHING STATUS: stat FOR SD X‘ss’ DEV X‘dd’

Explanation: This message is routed to the systems console by the LISTDATA command in response to a request for
status with the WTO parameter.
In the message text:
type Identifies the DASD type.
stat Status, as follows:
v ACTIVE if the subsystem is active.
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.
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.
ss The address of the subsystem's 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
Detecting Module: IDCBD0I
Routing Code: 2
Descriptor Code: 4

IDC01552I SUBSYSTEM CACHING STATUS: stat-DEV X‘ddd’

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 IDC01553I, IDC01554I,
IDC01555I, and IDC01556I.
In the message text:
stat Status, as follows:
v ACTIVE if the subsystem is active.
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.
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.
Operator response: If the device associated with this message is attached via the IBM 3990 Model 3 or Model 6

Chapter 20. IDC messages 305

IDC01553I • IDC01554I

Storage Control, see IBM 3990/9390 Operations and Recovery Guide for detailed recovery actions.
Source: DFSMSdfp
Detecting Module: IDCLA01
Routing Code: 2
Descriptor Code: 4

IDC01553I NVS STATUS: stat DEV X‘ddd’

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.
In the message text:
stat Status, as follows:
v ACTIVE if the nonvolatile storage is active.
v DEACTIVATED-SUBSYSTEM ERROR when an internal subsystem error caused nonvolatile storage
termination.
v DEACTIVATED-HOST/SF when an explicit host system or support facility request caused nonvolatile
storage termination.
v DEACTIVATION IN PROGRESS when a request for deactivation has been received and the destage is in
progress.
v DEACTIVATION FAILED when a request for deactivation was received and the destage failed.
v DISABLED when the nonvolatile storage is disabled for maintenance.
ddd The device number on which the I/O operation occurred.
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.
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 Operations and Recovery Guide for detailed recovery actions.
Source: DFSMSdfp
Detecting Module: IDCLA01
Routing Code: 2
Descriptor Code: 4

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.
In the message text:
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 The device number on which the I/O operation occurred.
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.
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 Operations and Recovery Guide for detailed recovery actions.
Source: DFSMSdfp
Detecting Module: IDCLA01

306 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC01555I • IDC01557I

Routing Code: 2
Descriptor Code: 4

IDC01555I DUPLEX PAIR STATUS: stat {PRI | SEC} DEV X‘ddd’ {pri|sec} DEV X‘xx’
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 when the device in the status request is part of a duplex
pair. This message might appear with IDC01552I, IDC01553I, IDC01554I, and IDC01556I.
In the message text:
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 The device number on which the I/O operation occurred.
xx The channel connection address (CCA) of the other device in the duplex pair returned in the sense
subsystem status data.
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
Detecting Module: IDCLA01
Routing Code: 2
Descriptor Code: 4

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.
In the message text:
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.
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
Detecting Module: IDCLA01
Routing Code: 2
Descriptor Code: 4

IDC01557I ACCESS CODE FOR SCU X‘scu’ SC X‘sc’ IS X‘acode’

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.
In the message text:
scu The box serial number.

Chapter 20. IDC messages 307

IDC1561I • IDC1564I

sc The 2 hexadecimal digit storage cluster number.

acode The 8 hexadecimal digit remote access code.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCLA01
Routing Code: 2
Descriptor Code: 4

IDC1561I WKSPC LACKING FOR dsname

Explanation: A larger region size is required for this particular invocation of access method services and LISTCAT.
In the message text:
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.
System 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 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
Detecting Module: IDCLC02

IDC1562I ser VOLUME SERIAL NUMBER TOO LONG

Explanation: A volume serial number exceeds six characters for the LISTCAT SPACE request.
In the message text:
ser The volume serial number.
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 with the corrected volume serial numbers.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCLC01

IDC1564I chartyp IS AN UNKNOWN TYPE

Explanation: An entry returned from the catalog is a type not supported by LISTCAT.
In the message text:
chartyp The unsupported type.
System action: The LISTCAT command bypasses the entry and continues processing with a condition code of 4.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCLC01

308 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC1565I • IDC1567I

IDC1565I xxx NOT A REQUESTED TYPE

Explanation: A desired entry was not among the types requested.
In the message text:
xxx The desired type.
System action: The LISTCAT command bypasses the specified entry and continues processing with a condition code
of 4.
Application Programmer Response: Run the job again with the correct type or types specified.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCLC01

IDC1566I ** xxx NOT LISTED

Explanation: One of the following conditions is present:
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.

In the message text:

xxx The entry name.
System action: The system bypasses the designated entry. The system continues processing with a return code of 4.
Application Programmer Response: Correct the 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.
System 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 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
Detecting Module: IDCLC01

IDC1567I ** INVALID CONTROL INTERVAL NUMBER nnn

Explanation: An entry identified by a control interval number in the virtual storage access method (VSAM) catalog
does not exist.
In the message text:
nnn The incorrect control interval number.
System action: The system bypasses the designated entry. The system continues processing.
System 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 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

Chapter 20. IDC messages 309

IDC1569I • IDC1595I

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
Detecting Module: IDCLC01

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
Detecting Module: IDCRP01

IDC1575I ONLY {BACKUP|TARGET} DEFINES {dsname|ser}

Explanation: This message indicates that either the backup or target catalog does not contain the data set or volume
entry.
In the message text:
dsname The data set name.
ser The volume serial number.
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
Detecting Module: IDCRP01

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

310 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC1597I • IDC01605I

information for the data set. However, the RACF indicator is exported.
System action: The system continues processing the command.
Application Programmer Response: If the protection attributes are desired, specify the master level password or
have your user profile modified so it indicates RACF-alter access to the data set.
Source: DFSMSdfp
Detecting Module: IDCXP01

IDC1597I THE text PARAMETER IS INVALID FOR AN ICF CATALOG

Explanation: text is one of the following:
INHIBITSOURCE
INHIBITTARGET
PERMANENT

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.
System action: The system ignores the incorrect parameter. The system exports the object.
Application Programmer Response: If an ICF catalog is being exported, do not specify INHIBITSOURCE or
INHIBITTARGET and specify TEMPORARY.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCXP01

IDC01600I CACHING SET {ON | OFF} FOR (SUBSYSTEM CONTAINING) volser.

Explanation: The I/O operation to set the cache on or off completed successfully.
In the message text:
volser The volume serial number.
System action: the system sets the return code to 0.
Source: DFSMSdfp
Detecting Module: IDCSS03

IDC01603I 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 unit address
makes the second cache storage director accessible.
Operator response: Contact hardware support.
Source: DFSMSdfp
Detecting Module: IDCSS03

IDC01605I STORAGE DIRECTOR X‘yy’ SET {ON | OFF}, PREVIOUSLY {ON | OFF}
Explanation: The SETCACHE command to set the storage director on or off completed successfully.
In the message text:
yy Indicates the address of the storage director.

Chapter 20. IDC messages 311

IDC1631I • IDC1638I

System action: The system sets the return code to 0.

Source: DFSMSdfp
Detecting Module: IDCSC0I

IDC1631I 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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCCC01

IDC1632I CVOL POINTER ‘xxx’ TO VOLUME ‘ser’ NOT CONVERTED

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.
In the message text:
xxx The CVOL pointer.
ser The volume serial number.
System action: The system does not convert the entry.
Application Programmer Response: Use the DEFINE ALIAS command to create an alias entry in the master
catalog.
System 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 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
Detecting Module: IDCCC01

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.
System 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 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
Detecting Module: IDCCC01

312 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC1644I • IDC1645I

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.
In the message text:
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.
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

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.
In the message text:
key Indicates the nonunique key.
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.
Application Programmer Response: If the 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.

Then rebuild the alternate index using the BLDINDEX Command.

System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp

Chapter 20. IDC messages 313

IDC1646I • IDC01653I

Detecting Module: IDCBI01

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.
In the message text:
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.
System action: The alternate index record is created with only those pointers that could fit.
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

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.
v One or more alternate index records too short to contain all the prime key or RBA pointers.
All non-ending errors for this alternate index have been identified in messages that precede this message.

In the message text:

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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

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: Processing continues with the aliases defined and listed.
Application Programmer Response: None.
Source: DFSMSdfp
Detecting Module: IDCXP01

314 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC01654I • IDC1663I

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.
Application Programmer Response: None.
Source: DFSMSdfp
Detecting Module: IDCXP01

IDC01657I OBJECT WAS SMS-MANAGED WHEN EXPORTED. CHANGED TO UNMANAGED.

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.
System action: The object is imported to unmanaged storage.
Source: DFSMSdfp
Detecting Module: IDCMP01

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.
System action: The system continues processing.
Source: DFSMSdfp
Detecting Module: IDCRC01

IDC1662I OUT-OF-SYNC DATA SET NOT EXPORTED

Explanation: The virtual storage access method (VSAM) data set named in the message that follows is out of
synchronization and the FORCE parameter was 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
Detecting Module: IDCRC01

IDC1663I BYPASSED RELATION dsname

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.
In the message text:
dsname The name of the cluster, non-VSAM object, or generation data group (GDG).
System action: The system bypasses the related object. 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
Detecting Module: IDCRC02

Chapter 20. IDC messages 315

IDC1664I • IDC1679I

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.
In the message text:
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
Detecting Module: IDCRC02

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.
In the message text:
volser1
volser2 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.
Application Programmer Response: Get the two volumes in synchronization. Run the job again.
Source: DFSMSdfp
Detecting Module: IDCRC01

IDC1678I ** DATA SET EXPORTED WITH MINOR ERRORS

Explanation: An error occurred while processing an associated object for an object being exported.
System action: The system bypasses processing of the associated object.
Application Programmer Response: See the preceding message to determine the type of error and the recovery
procedure.
Source: DFSMSdfp
Detecting Module: IDCRC01

IDC1679I ** OUT-OF-SYNC DATA SET EXPORTED WITH MINOR ERRORS

Explanation: An error occurred while processing an 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.
System action: The system bypasses processing of the associated object.
Application Programmer Response: See the preceding message to determine the type of error and the recovery
procedure.
Source: DFSMSdfp
Detecting Module: IDCRC01

316 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC01700I • IDC01706I

IDC01700I INDEXTEST BEGINS

Explanation: The INDEXTEST diagnostic procedure is beginning to process.
System action: The system begins processing.
Source: DFSMSdfp

IDC01701I DATATEST BEGINS

Explanation: The DATATEST diagnostic procedure is beginning to process.
System action: The system begins processing.
Source: DFSMSdfp

IDC01702I HIGH-USED RBA IS rba

Explanation: This message displays the component high-used relative byte address (RBA) in decimal.
In the message text:
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.
In the message text:
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.
In the message text:
size Indicates the control interval size.
Source: DFSMSdfp

IDC01705I CONTROL AREA SIZE IS size

Explanation: This message displays the control area size in decimal.
In the message text:
size Indicates the control area size.
Source: DFSMSdfp

IDC01706I RBA IS rba

Explanation: This message displays a relative byte address (RBA) in decimal.
In the message text:
rba Indicates the relative byte address.
Source: DFSMSdfp

Chapter 20. IDC messages 317

IDC1707I • IDC01710I

IDC1707I ** 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.
In the message text:
ownerid Indicates the owner of the data.
yyddd The date, in year and days.
System action: The system continues processing.
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
Detecting Module: IDCCO01

IDC01707I CURRENT INDEX LEVEL IS level

Explanation: This message displays the level of the index being processed when an error is detected.
In the message text:
level Indicates the current index level.
Source: DFSMSdfp

IDC01708I nnn CONTROL INTERVALS ENCOUNTERED

Explanation: This message indicates the total number of control intervals read.
In the message text:
nnn The number of control intervals.
System action: The system continues processing.
Source: DFSMSdfp

IDC01709I DATATEST COMPLETE - NO ERRORS DETECTED

Explanation: The entire data component has been tested and no errors have been found.
System action: The system concludes processing normally.
Source: DFSMSdfp

IDC01710I DATA COMPONENT CONTAINS nnn RECORDS

Explanation: After DATATEST concludes, this message displays the number of records contained in the data set.
In the message text:
nnn The number of records.
System action: The system concludes processing normally.
Source: DFSMSdfp

318 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC01711I • IDC01718I

IDC01711I DATA COMPONENT CONTAINS nnn DELETED CONTROL INTERVALS

Explanation: After DATATEST concludes, this message displays the number of unreclaimed empty control intervals.
In the message text:
nnn The number of control intervals.
System action: The system concludes processing normally.
Source: DFSMSdfp

IDC01712I MAXIMUM LENGTH DATA RECORD CONTAINS nnn BYTES

Explanation: After DATATEST concludes, this message displays the length in decimal of the longest data record
encountered.
In the message text:
nnn The number of bytes.
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.
In the message text:
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.
In the message text:
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.
Source: DFSMSdfp

IDC01718I RECORD UPDATE NUMBER IS number

Explanation: This message displays the expected update number of the spanned record segment.
In the message text:
number The number of the record update.
Source: DFSMSdfp

Chapter 20. IDC messages 319

IDC01720I • IDC01727I

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.
In the message text:
rba The relative byte address.
Source: DFSMSdfp

IDC01722I nnn PERCENT FREE SPACE

Explanation: After DATATEST concludes, this message displays the percentage of free space in the data set.
In the message text:
nnn 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.

IDC01724I INDEXTEST COMPLETE - NO ERRORS DETECTED

Explanation: The entire index component has been tested and no errors have been found.
System action: The system concludes processing normally.
Application Programmer Response: Run DATATEST to validate the data component.
Source: DFSMSdfp

IDC01726I 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.
In the message text:
rba The relative byte address.
Source: DFSMSdfp

IDC01727I 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.
In the message text:
rba The relative byte address.
Source: DFSMSdfp

320 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC1742I • IDC1840I

IDC1742I 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.
Application Programmer Response: Use the IEHPROGM utility or the access method services DELETE and
DEFINE commands to recatalog data sets.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCN01

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.
System action: The command abnormally ends with a message.
Source: DFSMSdfp
Detecting Module: IDCEC01

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.
System action: Processing continues.
Application Programmer Response: Ensure that the specified volumes exist and are on line.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp

IDC01811I NUMBER OF n RECORDS PROCESSED WAS xxxx

Explanation: Indicates the number of n-type records written to the output data set.
In the message text:
n The type of record written.
xxxx The number of records written.
System action: Processing continues.
Source: DFSMSdfp

IDC1840I TRACE AREA EMPTY - NO DATA DUMPED

Explanation: An attempt was made to dump trace data but the trace areas requested were null.
System action: The command ends normally.
Application Programmer Response: Turn the trace on before requesting a dump.
System programmer response: 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 output data sets related to the problem.

Chapter 20. IDC messages 321

IDC1841I • IDC1860I

Source: DFSMSdfp
Detecting Module: IDCTR01

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.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCTR01

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).
System action: None.
System programmer response: None.
Detecting Module: IDCBI01

IDC01851I "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

Explanation: The checkid listed was selected by the user, but not found in the checkpoint data set.
In the message text:
xxxxxxxx
The check identification.
System action: The system continues processing, but the CHECKID is not processed.
Application Programmer Response: Verify the checkid spelling, and that the correct checkpoint data set was used.
System 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 problem reporting data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center. Provide the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCCK01

322 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC1864I • IDC1867I

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.
System 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 problem reporting data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center. Provide the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCCK01

IDC1865I xxxxxxxx ADDITIONAL VOLUME SERIAL NOT FOUND IN CHKPT DATA SET
Explanation: Probable checkpoint logic error. A type 1 or type 2 DSDR indicated the presence of a type 2 DSDR
which did not exist.
In the message text:
xxxxxxxx
The additional volume serial number.
System action: Incomplete CHKLIST information is listed. The system continues processing with the next
checkpoint entry.
Application Programmer Response: Keep all related data sets and listing for reference.
System 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 problem reporting data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center. Provide the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCCK01

IDC1866I UNEXPECTED EOF ON CHECKPOINT DATA SET

Explanation: End-of-file occurred while processing DSDRs.
System action: The system abnormally ends the CHKLIST utility.
Application Programmer Response: Keep all related data sets and listings for reference.
System 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 problem reporting data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center. Provide the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCCK01

IDC1867I CURRENT VOLUME NOT FOUND ‘xxxxxxxx’

Explanation: The volume sequence number exceeded the number of volumes for the indicated ddname.
In the message text:
xxxxxxxx
The ddname.
System action: The system continues processing.
Application Programmer Response: Keep all related data sets and listings for reference.
System 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 problem reporting data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center. Provide the JCL for the job.

Chapter 20. IDC messages 323

IDC1870I • IDC1875I

Source: DFSMSdfp
Detecting Module: IDCCK01

IDC1870I ** IGNORED VSAM ERROR READING CRA - CI ‘nn’X

Explanation: A LISTCRA function encountered an I/O error reading a catalog recovery area (CRA) record at the
specified control interval.
In the message text:
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.
Application Programmer Response: See the preceding message to determine the cause of the I/O error. Correct the
problem. Run the job again.
Source: DFSMSdfp
Detecting Module: IDCLR01, IDCCK01

IDC1871I ** IGNORED VSAM ERROR READING CATALOG - CI ‘nn’X

Explanation: A LISTCRA function encountered an I/O error reading a catalog record at the specified control
interval.
In the message text:
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.
Application Programmer Response: See the preceding message to determine the cause of the I/O error. Correct the
problem. Run the job again.
Source: DFSMSdfp
Detecting Module: IDCLR01, IDCLR02

IDC1875I ERROR TRANSLATING CRA CI FROM CATALOG CI - ‘nn’X

Explanation: An error occurred when translating an entry's catalog control interval number, which points at a
related entry, to a catalog recovery area (CRA) control interval before reading the entry.
In the message text:
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 programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCLR01

324 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC1878I • IDC1881I

IDC1878I xxxxxxxx IGNORED ERROR FROM FIELD MANAGEMENT

Explanation: An error occurred when called by LISTCRA.
In the message text:
xxxxxxxx
The LISTCRA procedure in control when the error was detected.

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.
GETPRT The entry type or the entry name in the CRA record.
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.
System action: The system bypasses the error. The system continues processing. 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 programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCLR01

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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCLR01

IDC1881I IGNORED OPEN FAILURE FOR ALTERNATE OUTPUT DATA SET

Explanation: LISTCRA encountered an error attempting to open the alternate output data set.
System action: The system ignores the error. The 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.

Chapter 20. IDC messages 325

IDC01880I • IDC01886I

Source: DFSMSdfp
Detecting Module: IDCLR01

IDC01880I RECOVERY SET FOR dsname

Explanation: A SHCDS FRSETRR command was executed for data set dsname.
Source: DFSMSdfp
Detecting Module: IDCSH07

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
Detecting Module: IDCSH08

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
Detecting Module: IDCSH09

IDC01883I RECOVERY RESET FOR dsname

Explanation: A SHCDS FRRESETRR command was executed for data set dsname.
Source: DFSMSdfp
Detecting Module: IDCSH10

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
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
Detecting Module: IDCSH12

IDC01886I NON-RLS UPDATE DENIED FOR dsname

Explanation: The data set that has been accessed in non-RLS mode is now denied access in non-RLS mode.
Source: DFSMSdfp
Detecting Module: IDCSH13

326 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC01887I • IDC01890I

IDC01887I SUBSYSTEM subsystem REMOVED

Explanation: The subsystem with connections remaining for RLS is removed. All lock and subsystem connectivity
information is deleted.
Source: DFSMSdfp
Detecting Module: IDCSH14

IDC01888I SPHERE dsn PURGED

Explanation: An SHCDS PURGE command for the specified VSAM sphere completed successfully.
In the message text:
dsn
The data set name of a VSAM sphere.
System action: The system continues processing.
Operator response: None
System programmer response: None
Problem determination: None
Source: DFSMSdfp
Detecting Module: IDCSH20

IDC01889I UNIT OF RECOVERY urid PURGED

Explanation: An SHCDS PURGE command for the specified unit of recovery completed successfully.
In the message text:
urid
The unit of recovery identifier.
System action: The system continues processing.
Operator response: None
System programmer response: None
Problem determination: None
Source: DFSMSdfp
Detecting Module: IDCSH20

IDC01890I RETRY SUCCESSFUL FOR SPHERE dsn

Explanation: An SHCDS RETRY command for the specified sphere completed successfully.
In the message text:
dsn
The data set name of the VSAM sphere.
System action: The system continues processing.
Operator response: None
System programmer response: None
Problem determination: None
Source: DFSMSdfp
Detecting Module: IDCSH19

Chapter 20. IDC messages 327

IDC01891I • IDC1887I

IDC01891I RETRY SUCCESSFUL FOR UNIT OF RECOVERY urid

Explanation: An SHCDS RETRY command for the specified unit of recovery completed successfully.
In the message text:
urid
The unit of recovery identifier.
System action: The system continues processing.
Operator response: None
System programmer response: None
Problem determination: None
Source: DFSMSdfp
Detecting Module: IDCSH19

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 action: The system bypasses the error. The system continues processing. There may be minor errors in the
list.
Application Programmer Response: Restore the volume on which the error occurred to a previous valid 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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCLR01

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.
In the message text:
ser The volume serial number.
cde The reason code, as follows:
Code Explanation
3 Time stamp for volume was not obtained.
6 I/O error reading the CRA record.
System action: The system continues processing.
Application Programmer Response: This message requires no action, but the problem causing it may cause other
messages that may require a response.
Source: DFSMSdfp
Detecting Module: IDCRC01

328 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC1890I • IDC1968I

IDC1890I 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.
System action: The system continues processing the command.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCDL01

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.
System action: The system continues processing the command.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCDL01

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

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.
Application Programmer Response: Correct the MARGINS specifications.
System 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 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
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.
In the message text:
FROM|TO
Indicate which value encountered the error for commands that process more than one value.

Chapter 20. IDC messages 329

IDC1969I • IDC1998I

volser The volume serial number.

System action: The command ends normally if no functions have been performed yet. If some functions have been
performed, the command continues processing.
Application Programmer Response: Run the job 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCVS01

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.
In the message text:
volser The volume serial number.
System action: The command continues processing.
Application Programmer Response: If the volume is 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCVS01

IDC1997I catname AND ITS DATA SETS TO BE DELETED, REPLY 'Y' TO DELETE 'N' TO CANCEL.
Explanation: This message is an attention that a Catalog is about to be deleted.
In the message text:
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
Detecting Module: IDCDL01

IDC1998I 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.
In the message text:

330 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC1999I • IDC2011I

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 z/OS
DFSMS Managing Catalogs.
Source: DFSMSdfp
Detecting Module: IDCDL01

| IDC1999I catname replaced by an import backup copy, its VVR and its VTOC to be deleted, REPLY 'Y' TO
| DELETE 'N' TO CANCEL.
| Explanation: A Catalog is about to be deleted with the RECOVERY option, which means that the VSAM volume
| record (VVR) and VTOC for the catalog will be deleted.
| v If you respond Y or YES, IDCAMS processes the command replacing the user catalog with an import backup copy
| and deletes the specified user catalog along with its VSAM Volume Record (VVR) and VTOC entries. The VVR and
| DSCB for each object in the catalog are not deleted.
| v If you respond N or NO, the system ends the delete process with a return code of 8.

| In the message text:

| catname
| The catalog being deleted.
| Operator response: Reply 'Y' to delete, or 'N' to cancel the command.
| System programmer response: To enable or disable this WTOR message, use the MODIFY
| CATALOG,DISABLE(DELFORCEWNG). command. Use the command F CATALOG, REPORT to display the status of
| the DELRECOVWING parameter. See z/OS DFSMS Managing Catalogs.
| Source: DFSMSdfp
| Detecting Module: IDCDL01 IDCDL02

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.
Application Programmer Response: Run the job again in a larger address space.
System 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 problem reporting data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center. Provide the JCL for the job.
Source: DFSMSdfp
Detecting Module: IDCLM01

Chapter 20. IDC messages 331

IDC2035I • IDC2055I

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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCTP06

IDC2053I STEP CONTAINS JOBCAT/STEPCAT, BUT JOBCAT/STEPCAT SUPPORT IS DISABLED

Explanation: A step that referenced a 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
but the use of JOBCAT and STEPCAT is disabled by the installation
System action: The indicated command is terminated.
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 STEPCAT DD statement if there is no need for it.
v Ensure that all referenced catalogs are connected to the system master catalog with an appropriate alias for the
data set being referenced and allow the data set to be found through a standard search.
If the actions above cannot be performed, the use of JOBCAT and STEPCAT support can be enabled by the
installation through the operator command MODIFY CATALOG,ENABLE(JOBSTEPCAT). It is not recommended this
facility be enabled except when absolutely needed.
Source: DFSMSdfp
Detecting Module: IDCTP06

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.
System action: The system ends the request.
Application Programmer Response: Acquire the proper RACF facility class authorization. Run the job again.
Source: DFSMSdfp
Detecting Module: IDCTP06

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.
In the message text:
returncode The return code.
rsncode The reason code.
System action: The function terminates.

332 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2065I

Application Programmer Response: None.

System programmer response: See the z/OS MVS Programming: Authorized Assembler Services Guide for more
explanation on the return code and reason code from IEFDB476.
Source: DFSMSdfp
Detecting Module: IDCTP06

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.
Application Programmer Response: Correct the 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 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.
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 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 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 volume label of the volume.
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 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
– 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.
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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCMV01, IDCSR01

Chapter 20. IDC messages 333

IDC2074I • IDC2076I

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.
In the message text:
ser The volume serial number.
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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCLD01

IDC2075I ** VOLUME volser CANNOT BE ACTIVATED

Explanation: An attempt to make the specified volume active and mountable failed. See preceding message for
further explanation of the failure.
In the message text:
volser The volume serial number.
System action: The command ends with an error message.
Application Programmer Response: Run the 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.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCV01, IDCMV01

IDC2076I ** CART csn1 [csn2] NOT IN MSF FOR COPY yyddd

Explanation: The cartridges assigned to the copy created on the indicated date cannot be found in the Mass Storage
Facility (MSF). See preceding message for additional information.
In the message text:
csn1
csn2 The cartridge serial numbers that identify the sequence one and sequence two cartridges not in the MSF.
yyddd The date, in year and days.
System action: The command ends with a message unless additional copies are specified for processing.
Application Programmer Response: Correct the condition as indicated in the preceding message. Run the command
after:
v Reentering the missing cartridges
v Selecting another copy volume

334 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2078I • IDC2080I

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
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCO01, IDCRV01, IDCSV01

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.
In the message text:
volser The volume serial number.
System action: The command ends with a message.
Application Programmer Response: Correct the error as indicated in the preceding message.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
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.
In the message text:
grpname
The group name.
System action: The command ends with a message unless additional groups are specified for processing.
Application Programmer Response: Correct the error as indicated in the preceding message. Verify that the group
name is specified correctly. Run the command again.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCV01, IDCLC01, IDCLV01, IDCMG01, IDCMV01, IDCSD01

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.
In the message text:
volser The volume serial number.
System action: The system sends messages about the job to the job log.
Application Programmer Response: Correct the error as indicated in the preceding message. Before running the
command again check that the volume serial number is specified correctly.

Chapter 20. IDC messages 335

IDC2084I • IDC2091I

System programmer response: 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 output data sets related to the problem.
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 the preceding message
for further explanation of the failure.
System action: The command continues processing.
Application Programmer Response: Correct the error as identified in the preceding message. Run the command
again.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCO01, IDCEV01, IDCSR01

IDC2087I ** CART csn1 [csn2] NOT SCRATCHED FOR COPY yyddd

Explanation: The cartridges assigned to the copy 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 that one cartridge. See the
preceding message for further explanation of the failure.
In the message text:
csn1
csn2 The cartridge serial numbers that identify the sequence one and sequence two cartridges not scratched.
yyddd The date, in year and days.
System action: The command continues processing.
Application Programmer Response: Correct the 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.
System programmer response: 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 output data sets related to the problem.
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 message for further explanation of the problem.
In the message text:
volser The volume serial number.
System action: The command continues processing.
Application Programmer Response: Run the MODIFYV command to change the volume attribute to READONLY
or READWRITE.

336 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2093I • IDC2095I

System programmer response: 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 output data sets related to the problem.
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

In the message text:

grpname
The group name
System action: The command continues processing.
Application Programmer Response: Run the 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.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCMV01

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.
In the message text:
FROM|TO
Designate which volume is unusable for those commands processing both a source and target volume
having the same volume serial numbers.
volser The volume serial number.
System action: The command ends with a message reflecting the severity of the error.
Application Programmer Response: Correct the 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 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.

Chapter 20. IDC messages 337

IDC2096I

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 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 restored if the volume is left partially renamed.
If ADDV, MODIFY, 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 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:
– 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 complete the rename operation if the volume is both inactive
and has a volume serial mismatch condition
– Running MODIFYV again to complete or retry the rename operation if the volume is active but has a mismatch
condition
– Running 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.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCLD01, IDCSD01, IDCRV01, IDCEV01, IDCMG01, IDCMV01, IDCSR01, IDCSV01,
IDCCN01, IDCCO01

IDC2096I {FROM|TO} VOLUME volser INCOMPLETELY COPIED IN A PRIOR OPERATION

Explanation: The specified volume was incompletely copied by the COPYV, RECOVERV, or CONVERTV commands
and cannot be used.
In the message text:
FROM|TO
Designate which volume is unusable for those commands processing both a source and target volume
having the same volume serial number.
volser The volume serial number.
System action: The command terminates with a message containing the severity code.
Application Programmer Response: Correct the 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 to the target
volume that is flagged as an incomplete copy volume. Otherwise, run SCRATCHV to scratch the target volume.

338 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2097I

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.
If the SCRATCHV command is run, the DD statement 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 standard information for the volume but also highlights the volume report with a note
that a copy operation failed for the preceding volume.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCO01, IDCLD01, IDCSD01, IDCSR01, IDCRV01, IDCEV01, IDCMG01, IDCMV01,
IDCCN01

IDC2097I {FROM|TO} VOLUME volser INCOMPLETELY CREATED IN A PRIOR OPERATION

Explanation: The specified volume was incompletely created by the CREATEV command and could not be used.
In the message text:
FROM|TO
Designate which volume is unusable for those commands processing both a source and target volume
having the same volume serial number.
volser The volume serial number.
System action: The command ends with a message 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCLD01, IDCSD01, IDCSR01, IDCRV01, IDCMG01, IDCMV01, IDCCN01, IDCEV01,
IDCCO01

Chapter 20. IDC messages 339

IDC2100I • IDC2103I

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.
In the message text:
return-code
The reason code.
System action: The command continues processing.
Application Programmer Response: Correct the error. Recatalog the data set using IEHPROGM utility or the access
method services DELETE and DEFINE commands.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA07

IDC2101I CATALOG RETURN CODE FOR RECAT REQUEST WAS return-code - REASON CODE rsncode
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.
In the message text:
return-code The return code.
rsncode The reason code.
System action: The command continues processing.
Application Programmer Response: Correct the error and recatalog the data set using the IEHPROGM utility or the
Access Method Services DELETE and DEFINE commands.
System programmer response: If the error recurs and the program is not in error, look at the messages in 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA07

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 X‘208’ or X‘224’ 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.
System action: The system continues processing with the next group if the request is for grouped volumes. If the
request is for non-grouped volumes, the system ends processing.
Application Programmer Response: Run the command again. If there is a permanent Inventory data set error,
contact the system programmer.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp

340 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2108I • IDC2110I

Detecting Module: IDCLD01, IDCSD01

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.
In the message text:
ser The volume serial number.
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
Detecting Module: IDCLD01, IDCSD01

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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCLD01, IDCSD01

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.
In the message text:
grpname
The group name.
System action: The system continues processing with the next group. If there are no more groups, the command
ends.
Application Programmer Response: Refer to the 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCLD01, IDCSD01

Chapter 20. IDC messages 341

IDC2111I • IDC2119I

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.
System action: The command ends.
Application Programmer Response: Refer to the preceding message for the type of Inventory data set error.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCLD01, IDCSD01

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.

In the message text:

grpname
The group name.
System action: The command ends with this message unless additional groups are specified for processing.
Application Programmer Response: Correct the error specified in the preceding message. Before running the
command again, check that the group name is specified correctly.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCLV01

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. See the
preceding message for further explanation of the failure.
In the message text:
grpname
The group name.
System action: The command ends with this message unless additional groups are specified for processing.
Application Programmer Response: Correct the error specified in the preceding message. Verify that the group
name is specified correctly. Run the command again.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCLV01

342 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2160I • IDC2370I

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.
In the message text:
xxxxxx Indicates the volume.
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.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCRC01

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.
System action: The system continues processing with 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 method services LISTCAT command to list catalog entries and
information about objects defined in the catalog.
If the error recurs and the program is not in error, look at the messages in the job log for more information. Search
problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the
JCL, the SYSOUT output for the job, and all printed output and output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA07

IDC2364I 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.
System action: The system continues processing with the next data set on the volume.
Application Programmer Response: If the data set entry is cataloged, rerun the SCRDSET command.
System programmer response: Issue the access method services LISTCAT command to list catalog entries and
information about objects defined in the catalog.
If the error recurs and the program is not in error, look at the messages in the job log for more information. Search
problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the
JCL, the SYSOUT output for the job, and all printed output and output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA07

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.
In the message text:

Chapter 20. IDC messages 343

IDC2371I • IDC2373I

ddname The data definition name.

x The macro return code.
System action: The command ends normally.
Application Programmer Response: Ensure the DD name in the FILE parameter is correct and there is a
corresponding DD statement in the JCL statements.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCIO05

IDC2371I UNABLE TO OBTAIN STORAGE FOR I/O PROCESSING

Explanation: There was insufficient storage to perform the necessary I/O processing.
System action: The command ends normally.
Application Programmer Response: Increase the region size for the job. Run the command again.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCIO05

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.
In the message text:
dsname The data set name.
System action: The command ends normally.
Application Programmer Response: Examine the write-to-programmer message issued by the OPEN macro for the
specific error code. Correct the problem. Run the command again.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCIO05

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.

In the message text:

dsname The data set name.
System action: The command ends normally. The requested function cannot be performed.

344 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2374I • IDC2376I

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)
2. The name of the DD statement for the data set (non-VSAM data sets).

Rerun the command.

System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCIO01

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.
In the message text:
dsname The data set name.
System action: The command continues processing.
Application Programmer Response: Examine the 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCIO05

IDC2375I **I/O ERROR volser IOS RC = return-code

Explanation: An I/O error occurred from the command.
In the message text:
volser The volume serial number.
return-code The IOS completion code, that comes from the IOSCOD field of the IOSB data area.
System action: The system ends processing of the command.
Application Programmer Response: This is a probable subsystem problem. Correct any error. Run the command
again.
Source: DFSMSdfp
Detecting Module: IDCIO05

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

Chapter 20. IDC messages 345

IDC2381I • IDC2386I

In the message text:

dsname The data set name.
System action: The command ends normally. The requested function is not performed.
Application Programmer Response: If the operator 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 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCIO01

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.
In the message text:
volser The volume serial number.
System action: The system demounts the mass storage volume. The command ends normally.
Application Programmer Response: Run the command again after the volume with the same serial number is
demounted.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA06

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.
In the message text:
ddname The data definition name.
System action: The command ends normally.
Application Programmer Response: Run the 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA06

346 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2387I • IDC2390I

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.
In the message text:
volser The volume serial number.
System action: The command ends normally.
Application Programmer Response: Examine the preceding message and correct the problem. Run the command
again.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA06

IDC2388I ** VOLUME volser COULD NOT BE DEMOUNTED

Explanation: The demount of the specified volume is unsuccessful. A preceding message gives the explanation for
this error.
In the message text:
volser The volume serial number.
System action: The command ends normally.
Application Programmer Response: Examine the preceding message and correct the problem. Run the command
again.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA06

IDC2390I VOLUME volser COULD NOT BE ENQUEUED FOR EXCLUSIVE USE

Explanation: The enqueue of the specified volume for exclusive use cannot be done because the volume serial is
enqueued for shared use.
In the message text:
volser The volume serial number.
System action: The command ends normally.
Application Programmer Response: Run the command again after the volume is not being used by any other job.
Specify the volume serial on the DD statement.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA06

Chapter 20. IDC messages 347

IDC2391I • IDC2552I

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.
In the message text:
return-code The return code.
System action: The system does not continue the function.
Application Programmer Response: Examine the return code and correct the problem. Run the command again.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA06

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.
System action: The system continues processing with the next data set on the volume.
Application Programmer Response: Uncatalog the data set, then recatalog it with the correct volume serial number.
System programmer response: Issue the access method services LISTCAT command to list catalog entries and
information about objects defined in the catalog.
If the error recurs and the program is not in error, look at the messages in the job log for more information. Search
problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the
JCL, the SYSOUT output for the job, and all printed output and output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA07

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.
System action: The system continues processing.
Application Programmer Response: Remove the asterisk (*) indicating a generic entry name or remove the member
name to achieve the desired alteration.
Source: DFSMSdfp
Detecting Module: IDCAL01

IDC2552I 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

348 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2553I • IDC2559I

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.
System programmer response: If the error recurs and the entry type is listed as valid in the LISTCAT, 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
Detecting Module: IDCAL01

IDC2553I ERASE OPTION IS INVALID FOR ENTRY TYPE

Explanation: Only virtual storage access method (VSAM) clusters and alternate indexes can be erased.
System action: The system does not delete the entry. The remaining VSAM entries, if any, are deleted.
Application Programmer Response: Submit the request again without the ERASE parameter.
System 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 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.
Source: DFSMSdfp
Detecting Module: IDCDL01

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.
System action: The system ends processing for this entry.
Application Programmer Response: Refer to the dynamic allocation error messages or supply a FILE parameter.
System 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 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. 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.
Source: DFSMSdfp
Detecting Module: IDCDL01

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.
System action: The system ends processing for the entry.

Chapter 20. IDC messages 349

IDC2563I • IDC2618I

Application Programmer Response: Remove the asterisk (*) which indicates a generic entry name or remove the
member name.
System 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 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
Detecting Module: IDCDL01

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.
Application Programmer Response: Run the job again with LISTCAT parameters that are compatible with the fields
specification.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCLC01

IDC2616I PATH path WAS NOT SUCCESSFULLY IMPORTED

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.
In the message text:
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
Detecting Module: IDCMP01

IDC2618I INVALID OBJECTS SUBPARAMETER FOR PATH path

Explanation: An OBJECTS subparameter other than NEWNAME or FILE was specified for path object.
In the message text:
path The path object.
System action: The system continues IMPORT processing, attempting to define any remaining paths from the
portable data set.
Application Programmer Response: Probable user error. Correct the OBJECTS parameter. Submit the job again.
Source: DFSMSdfp
Detecting Module: IDCMP01

350 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2620I • IDC2630I

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.

In the message text:

dsname The data set name.
System action: An associated message identifies the entry not converted.
Application Programmer Response: Resolve the duplicate name.
System 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 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
Detecting Module: IDCMP01

IDC2621I IMPORTRA FAILED FOR obj

Explanation: The object named could not be imported. The preceding messages will give the reason for the failure.
In the message text:
obj The specified object.
System action: The system continues processing with 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.

Application Programmer Response: Determine the cause of the failure by examining previous messages on the
SYSPRINT output. Correct the indicated error. Run the job again.
Source: DFSMSdfp
Detecting Module: IDCRM01

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.
System 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 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
Detecting Module: IDCRM01

Chapter 20. IDC messages 351

IDC2640I • IDC2647I

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.

In the message text:

dsname The data set name.
System action: The system ends processing for this 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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

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.
In the message text:
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

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.
System action: The system ends processing for this alternate index. However, BLDINDEX attempts to process any
other alternate indices identified by the OUTFILE or OUTDATASET parameter.
Application Programmer Response: Increase the virtual storage region size. Submit the job again.

352 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2648I • IDC2650I

System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

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.
System action: The system ends processing for this alternate index. However, BLDINDEX attempts to process any
other alternate indices specified by the OUTFILE or OUTDATASET parameter.
Application Programmer Response: Correct the external sort work file job control. Submit the job again.
Alternatively, provide enough virtual storage so that an internal sort can be performed.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

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.
System action: The system ends processing for this alternate index. However, BLDINDEX attempts to process any
other alternate indexes specified via the OUTFILE or OUTDATASET parameter.
Application Programmer Response: Correct the external sort work file job control, or provide enough virtual
storage so that an internal sort can be performed. Submit the job again.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

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.
System action: The system ends processing for this alternate index. However, BLDINDEX attempts to process any
other alternate indices specified by the OUTFILE or OUTDATASET parameter.
Application Programmer Response: Correct the sort work file job control. Alternatively, delete the alternate index.

Chapter 20. IDC messages 353

IDC2651I • IDC2655I

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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

IDC2651I DEFINE OF SORT WORK FILES FAILED

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.
System action: The system ends processing for this alternate index. However, BLDINDEX attempts to process any
other alternate indexes specified by the OUTFILE or OUTDATASET parameter.
Application Programmer Response: Correct the error as explained for the return code. Submit the job again.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

IDC2654I dsname WAS NOT BUILT

Explanation: An error was encountered for the alternate index. The message containing the error precedes this
message.
In the message text:
dsname The data set name.
System action: The system ends processing for this alternate index. However, BLDINDEX attempts to process any
other alternate indexes identified by the OUTFILE or OUTDATASET parameter.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

IDC2655I UNABLE TO LOCATE ATTRIBUTES OF dsname

Explanation: The virtual storage access method (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:
v Entry type
v Associated objects
v AMDSB control block for data objects

In the message text:

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

354 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2656I • IDC2660I

attempts to process any other alternate indices identified by the OUTFILE or OUTDATASET parameter.
Application Programmer Response: Follow the problem determination actions.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

IDC2656I LOCATE FAILED FOR dsname

Explanation: The virtual storage access method (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.
In the message text:
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.
Application Programmer Response: Correct the error as explained for the return code. Submit the job again.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

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.
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.
Detecting Module: IDCBI01

IDC2660I INVALID ENTRY TYPE IN CATALOG, OBJECT BYPASSED

Explanation: The entry type field indicates the object being exported is not one of the following:
v A virtual storage access method (VSAM) cluster
v Alternate index
v User catalog
v Non-VSAM object
v OS/VS2 generation data group (GDG)
System action: The system ends processing for the object.
Application Programmer Response: Redefine the object in error. For the object name, see the following second-level
message.

Chapter 20. IDC messages 355

IDC2666I • IDC2673I

System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRC01

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.
Source: DFSMSdfp
Detecting Module: IDCRC01

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.
In the message text:
ser The volume serial number.
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
Detecting Module: IDCRC01

IDC2671I WILL NOT PROCESS CRA ON VOLUME ser, DIFFERENT CATALOG NAME
Explanation: This volume does not belong to the catalog named in the following message.
In the message text:
ser The volume serial number.
System action: The system discontinues processing of this volume.
Application Programmer Response: Run the job with the correct catalog name.
Source: DFSMSdfp
Detecting Module: IDCRC01

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.
In the message text:
dname The specified DNAME.
System action: The system ends processing for this request.
Application Programmer Response: Correct the volume information in error. Run the job again.
Source: DFSMSdfp
Detecting Module: IDCRC01

356 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2675I • IDC2684I

IDC2675I DUPLICATE NAME ENCOUNTERED, NAME ON VOLUME ser BYPASSED

Explanation: Duplicate names were found in the catalog recovery areas (CRA) on two different volumes.
In the message text:
ser The volume serial number.
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.
Source: DFSMSdfp
Detecting Module: IDCRC01

IDC2677I ** DATA SET NOT EXPORTED

Explanation: An error occurred or a catalog field could not be located for the object being exported.
System action: The system ends processing for the EXPORTRA command.
Application Programmer Response: Determine the type of error from the preceding message, and redefine the
object.
Source: DFSMSdfp
Detecting Module: IDCRC01

IDC2681I ** VOLUME volser NOT CREATED

Explanation: The volume was not created for the specified volume serial number. A preceding message explains the
error.
In the message text:
volser The volume serial number.
System action: The command does not attempt to create any subsequent volumes and ends normally.
Application Programmer Response: Correct the error as indicated in the preceding message. Run the command
again.
Source: DFSMSdfp
Detecting Module: IDCRC01

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.
In the message text:
volser The volume serial number.
System action: The command scratches the partially created volume and ends processing normally.
Application Programmer Response: Correct the error as indicated in the preceding message. Run the command
again, requesting creation of the volumes not created.
Source: DFSMSdfp
Detecting Module: IDCCV01

Chapter 20. IDC messages 357

IDC2685I • IDC2688I

IDC2685I ** NO ATTEMPT MADE TO CREATE ADDITIONAL VOLUMES

Explanation: An error occurred preventing the creation of all volumes requested. A preceding message explains the
error.
System action: The command ends normally.
Application Programmer Response: Correct the error indicated in the preceding message. Run the command again,
requesting creation of the volumes not created.
Source: DFSMSdfp
Detecting Module: IDCCV01

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.
In the message text:
volser The volume serial number.
System action: The command ends normally. The volume record in the Inventory data set for the volume indicates
the volume was incompletely created.
Application Programmer Response: Correct the 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCV01

IDC2688I ** INCOMPLETE VOLUME CREATION FLAG NOT RESET FOR VOLUME volser
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.
In the message text:
volser The volume serial number.
System action: The command scratches the partially created volume.
Application Programmer Response: Correct the error indicated in the preceding message. Run the command again.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCV01

358 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2689I • IDC2761I

IDC2689I INSUFFICIENT NUMBER OF CARTRIDGES SPECIFIED ON COMMAND

Explanation: The number of cartridges specified in the CARTRIDGE parameter is insufficient to create the number
of new volumes requested.
System action: The command creates as many volumes as possible before ending normally.
Application Programmer Response: Specify 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.
Source: DFSMSdfp
Detecting Module: IDCCV01

IDC2752I ** CARTS csn1 cns2 NOT SCRATCHED FOR volser

Explanation: The requested volume was not scratched.
In the message text:
csn1
csn2 The unscratched cartridges.
volser The volume serial number.
System action: The command ends normally.
Application Programmer Response: Correct the error indicated in the preceding message. Run the command again.
Source: DFSMSdfp
Detecting Module: IDCCV01

IDC2753I VOLUME volser NOT SCRATCHED, COPIES EXIST

Explanation: The base volume was not scratched because copies still exist.
In the message text:
volser The volume serial number.
System action: The command ended normally.
Application Programmer Response: Correct the error that prevented the copies from being scratched. Run the
command again, specifying the ALL parameter.
Source: DFSMSdfp
Detecting Module: IDCSV01

IDC2761I ** 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.
In the message text:
yyddd The date, in year and days.
System action: The command either continues processing or ends depending on the severity of the error
encountered.
Application Programmer Response: Correct the error indicated in the preceding message. Run the command again
to remove records not removed.
Source: DFSMSdfp
Detecting Module: IDCSV01

Chapter 20. IDC messages 359

IDC2762I • IDC2782I

IDC2762I ** 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.
In the message text:
volser The volume serial number.
System action: The command ends normally.
Application Programmer Response: Correct the error indicated in the preceding message. Run the command to
remove the volume record.
Source: DFSMSdfp
Detecting Module: IDCRR01

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.
System programmer response: 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
Detecting Module: IDCRR01

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.
In the message text:
volser The volume serial number.
System action: The command ends normally.
Application Programmer Response: Correct the error indicated in the preceding message. Run the REMOVEVR
command again with the ALL parameter.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCRR01

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.
In the message text:
csn The cartridge serial number.

360 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2800I • IDC2801I

System action: The system continues processing.

Application Programmer Response: Correct the problem as identified in the preceding message. Run the command
again to eject the cartridge.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCEC01

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.
The following are valid attributes:
v bind/nobind,
v readonly/readwrite
v dasderase/nodasderase
v exclusive/shared,
v pagefault/nopagefault
System action: The command ends with a message.
Application Programmer Response: Correct the 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.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCMG01

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 explanation of the problem.
The following are valid attributes:
v bind/nobind
v readonly/readwrite,
v dasderase/nodasderase
v exclusive/shared
v pagefault/nopagefault
System action: The system continues processing.
Application Programmer Response: Correct the problem as identified in the preceding message. Run the MODIFYV
command to change the volume attributes of each volume that could not be updated.
System 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 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 output data sets
related to the problem.

Chapter 20. IDC messages 361

IDC2821I • IDC2831I

Source: DFSMSdfp
Detecting Module: IDCMG01

IDC2821I ** text REPORT NOT PRODUCED

Explanation: text is one of the following:
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.
Application Programmer Response: Check the previous error message for the cause of the failure. Correct the error.
Run the command again.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCLM01

IDC2823I ** text TOTAL COULD NOT BE CALCULATED

Explanation: text is one of the following:
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.
Application Programmer Response: Correct the error identified in the previous message. Run the command again.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCLM01

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.
System action: The system continues processing.
Application Programmer Response: Correct the error as indicated in the preceding message. Run the command
again to list volumes that could not be listed.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCLV01

362 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2833I • IDC2854I

IDC2833I ** CARTRIDGE RECORD csn NOT FOUND IN INVENTORY

Explanation: The cartridge record for the cartridge cannot be found in the Inventory data set.
In the message text:
csn The cartridge serial number.
System action: The system continues processing.
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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCLV01

IDC2843I FUNCTION SUSPENDED DUE TO I/O ERROR - RECORDS DUMPED nnn

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.
In the message text:
nnn The number of records dumped.
System action: No more data was dumped. The command ends normally.
Application Programmer Response: Run the command again to get the remaining trace data. If the problem
continues, reallocate and recatalog the data set which is getting I/O errors.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCTR01

IDC2853I ** DISPLAY OF prm NOT SUCCESSFUL

Explanation: An attempt to retrieve the information for the indicated tuning parameter failed. See preceding
message for an explanation of the error.
In the message text:
prm The tuning parameter.
System action: The command ended normally. The system does not display more parameters.
Application Programmer Response: Correct the error. Run the command again.
Source: DFSMSdfp
Detecting Module: IDCTU01

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.
In the message text:
prm The indicated parameter.
System action: The command ends normally. The system does not change any more tuning parameters.

Chapter 20. IDC messages 363

IDC2872I • IDC2879I

Application Programmer Response: Correct the error. Run the command again.
Source: DFSMSdfp
Detecting Module: IDCTU01

IDC2872I CRA IS OWNED BY catname

Explanation: The catalog recovery area (CRA) on this volume belongs to a catalog other than the one for which
COMPARE was specified.
In the message text:
catname 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
Detecting Module: IDCTU01

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.
Application Programmer Response: Specify the correct catalog name in the CATALOG parameter or correct the
cause of the Open error. Run the job again.
Source: DFSMSdfp
Detecting Module: IDCLR01

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.
System action: The system ignores the error. The system continues processing. An incomplete listing of the contents
of the catalog recovery area may result.
Application Programmer Response: Restore the volume on which the error occurred to a previous valid condition.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCLR01

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
Detecting Module: IDCLR01

364 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2882I • IDC2886I

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.
System action: The system ends processing for this CRA.
Application Programmer Response: Restore the volume on which the error occurred to a previous valid condition.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCLR01

IDC2884I IGNORED VERIFY FAILURE FOR CATALOG

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.
System action: The system ignores the command. The system continues processing. Erroneous miscompares or I/O
errors may result.
Application Programmer Response: Restore the volume on which the error occurred to a previous valid condition.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCLR01

IDC2886I UNABLE TO REFERENCE CRA ON VOLUME ser - REASON CODE cde

Explanation: When opening the catalog recovery area (CRA) the system detected an error.
In the message text:
ser The volume serial number.
cde The hex reason code, as follows:
Codes Explanation
1 Cannot verify the CRA.
2 Cannot open the CRA.
4 I/O error on control interval No.0
5 I/O error on control interval No.3
7 Error on number of directories.
8 Error on directory entries.
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.
Source: DFSMSdfp
Detecting Module: IDCRC01

Chapter 20. IDC messages 365

IDC2889I • IDC2894I

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.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCRC01

IDC2892I 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.
System action: The system does not delete the entry. The remaining entries, if any, are deleted.
Application Programmer Response: Specify the CLUSTER parameter or run a LISTCAT against the catalog to verify
the entry type. Correct the error. Run the job again.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp

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 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).
System action: The system does not delete the entry. The remaining entries, if any, are deleted.
Application Programmer Response: Correct the parameters specified. If RECOVERY is specified for a GDG, the
GENERATIONDATAGROUP parameter must be specified. Run the job again.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp

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.
System action: The system ends processing of the command.
Application Programmer Response: Correct the name specification. Run the job again.
System 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 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

366 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2895I • IDC2900I

Detecting Module: IDCDL01

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.
System action: The system does not 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.
System 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 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
Detecting Module: IDCDL01

IDC2899I MASK PARAMETER NOT ALLOWED FOR NVR, VVR, TRUENAME, LIBENT, VOLENT OR PDSE
DATA SET MEMBER DELETE
Explanation: If MASK parameter was specified on a DELETE command, you cannot specify the TYPE parameters of
TRUENAME, NVR, VVR, LIBENT, VOLENT and PDSE member data set in the same command. The DELETE MASK
command does not support these types of data sets.
System action: The DELETE command failed to proceed. A return code of 8 was issued.
Application Programmer Response: You might perform one of the following procedures:
v Remove the TYPE parameter of the DELETE command. Run the job again. The DELETE MASK command will be
completed. The data sets that are not TRUENAME, NVR, VVR, LIBENT, VOLENT and PDSE member will be
deleted.
v Remove the MASK parameter, and use the generic DELETE.
System 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 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
Detecting Module: IDCDL02

IDC2900I MASK PARAMETER NOT ALLOWED FOR MORE THAN ONE ENTRY-NAME TO BE SPECIFIED
IN ONE DELETE COMMAND
Explanation: When the MASK keyword is present in the DELETE command, only one entry-name is allowed to be
specified.
System action: The DELETE command failed to proceed. A return code of 8 was issued.
Application Programmer Response: You might perform one of the following procedures:
v Check the entry-names list. If there are no masking entry-names in the list, remove the MASK keyword in the
DELETE command, and reissue the command.
v Split the DELETE command to multiple DELETE commands, and issue with one masking entry-name at a time.
System 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 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
Detecting Module: IDCDL01

Chapter 20. IDC messages 367

IDC2901I • IDC2909I

IDC2901I MASKING ENTRY NAME REQUIRES A KEYWORD MASK TO BE SPECIFIED

Explanation: A masking entry name that contained double asterisks or percentage sign is specified in the DELETE
command, and a MASK keyword was not specified along with the command.
System action: The DELETE command failed to proceed. A return code of 8 was issued.
Application Programmer Response: You might perform one of the following procedures:
v Check the entry name. Correct it if it does not mean to be a masking entry name, and reissue the command.
v Specify MASK keyword to process the masking entry name, and reissue the command.
System 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 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
Detecting Module: IDCDL01

IDC2902I NO ENTRIES FOUND FOR MASK xxxxxxxxx.

Explanation: There are no entries found that match the filter key.
System action: The DELETE command failed to proceed. A return code of 8 was issued.
Application Programmer Response: You might perform one of the following procedures:
v Check the CATALOG name if specified. If it is not specified, check to make sure that the objects are in the
SYSTEM MASTER CATALOG.
v If objects are on a USER CATALOG, specify it with CAT(usercat).
System 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 problem reporting databases 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
Detecting Module: IDCDL02

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.
In the message text:
ddname The ddname.
System action: The volume cannot be accessed.
Application Programmer Response: Correct the erroneous ddname or provide a DD statement. Submit the job
again.
System 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 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
Detecting Module: IDCIO03

IDC2909I UNABLE TO SCRATCH dsname

Explanation: An error occurred while attempting to scratch the specified data set. A subsequent second-level
message explains the error.
In the message text:
dsname The data set name.
System action: The data set is not scratched.

368 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2910I • IDC2914I

System 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 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
Detecting Module: IDCSA08

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.
System 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 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
Detecting Module: IDCSA08

IDC2912I ** PASSWORD VERIFICATION FAILED

Explanation: The console operator did not supply the proper password for the data set to be scratched.
System action: The data set is not scratched.
Application Programmer Response: Submit the job again, supplying the correct password when prompted.
System 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 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
Detecting Module: IDCSA08

IDC2913I ** DATA SET HAS NOT EXPIRED ON VOLUME ser

Explanation: The PURGE option was not specified, and the data set retention period has not expired.
In the message text:
ser The volume serial number.
System action: The data set is not scratched.
Application Programmer Response: Submit the job again, specifying PURGE to delete the data set.
System 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 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
Detecting Module: IDCSA08

IDC2914I ** PERMANENT I/O ERROR ON VOLUME ser

Explanation: The volume table of contents (VTOC) cannot be read because of an I/O error.
In the message text:
ser The volume serial number.
System action: The data set is not scratched.
Application Programmer Response: Request that the volume be restored.

Chapter 20. IDC messages 369

IDC2915I • IDC2917I

System 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 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
Detecting Module: IDCSA08

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.
In the message text:
ser The volume serial number.
System action: The data set is not scratched.
Application Programmer Response: Ensure that a unit is available for mounting.
System 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 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
Detecting Module: IDCSA08

IDC2916I ** DATA SET WAS IN USE

Explanation: The data set to be scratched was in use.
System action: The data set is not scratched.
Application Programmer Response: To delete the data set, ensure that no one else is using the data set when you
run the job again.
System 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 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
Detecting Module: IDCSA08

IDC2917I NO RACF PROFILE ON resname

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.
In the message text:
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.
System action: If a Cache-DASD command was issued, the system continues processing. Otherwise, the command
ends.
Cache-DASD commands are as follows:
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.

370 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2918I • IDC2930I

System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA08

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.
In the message text:
resname The resource name.
System action: The system ends the command.
Application Programmer Response: Contact the RACF security administrator to acquire the proper authorization.
Run the job again.
System 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 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
Detecting Module: IDCSA08

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.
System action: The system ends the command.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA08

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.
System action: The data set is not scratched.
Application Programmer Response: Contact the RACF security administrator to acquire the proper authorization.
Run the job again.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA08

Chapter 20. IDC messages 371

IDC2950I • IDC2954I

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.
Application Programmer Response: Follow the problem determination steps.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCTP01

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.
Application Programmer Response: Follow the problem determination steps.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCTP01

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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCTP01

IDC2953I A REDO SUB-STRUCTURE IS NESTED

Explanation: A redo structure cannot be defined within the set of structures to be redone. This should not occur in a
valid program.
System action: The current redo operation is ended. All structures will be treated only once.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCTP01

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.

372 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2955I • IDC2961I

System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCTP05

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.
System 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 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
Detecting Module: IDCTP01

IDC2960I NO PSWDFILE FOR dsname

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.
In the message text:
dsname The data set name.
System action: The command ends normally.
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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCVS01

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.
In the message text:
FROM|TO
Indicate which volume contains the data set for those commands that process more than one command.
volser The volume serial number.
System action: The command ends normally.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCVS01

Chapter 20. IDC messages 373

IDC2963I • IDC2965I

IDC2963I 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.
In the message text:
FROM|TO
Indicate which volume encountered the error for the commands that process more than one volume.
System action: The command ends normally.
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. Run the command
again.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCVS01

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.
System action: The command continues processing.
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 utility's SCRATCH VTOC statement.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCVS01

IDC2965I ATTEMPT TO SCRATCH DATA SETS TERMINATED

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.
System action: The system does not make any further attempts to scratch a data set. The command continues
processing.
Application Programmer Response: Run the 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 utility's SCRATCH VTOC statement.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCVS01

374 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC2966I • IDC2972I

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 action: The command ends normally. The system performs no further function.
Application Programmer Response: Use the 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 information. 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 output
data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCVS01

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.
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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCVS01

IDC2971I RESERVE FOR VOLUME volser NOT SUCCESSFUL

Explanation: The reserve with the HAVE option returned an unsuccessful condition code.
In the message text:
volser The volume serial number.
System action: The command ends processing.
Application Programmer Response: Run the command again.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCVS01

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.
In the message text:
return-code The return code, as follows:
Code Explanation

Chapter 20. IDC messages 375

IDC2973I • IDC3004I

4 An I/O error occurred while reading the DSCBs.

8 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.
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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCVS03

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.
In the message text:
volser The volume serial number.
System action: Instead of attempting to copy only allocated cylinders, the system makes a copy of all cylinders of
the volume.
Application Programmer Response: Ensure that the VTOC is not in error. Try to list the VTOC using the IEHLIST
utility program.
System programmer response: If the error recurs and the program is not in error, look at the messages in the job
log for more information.
Source: DFSMSdfp
Detecting Module: IDCVS01

IDC3003I FUNCTION TERMINATED. CONDITION CODE IS cde.

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.
In the message text:
cde The condition code of the abnormally ended function.
System action: The system continues processing with 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.
Application Programmer Response: Preceding messages indicate the appropriate programmer response.
Source: DFSMSdfp
Detecting Module: IDCVS01

IDC3004I FUNCTION TERMINATED. INSUFFICIENT MAIN STORAGE.

Explanation: The region size was not large enough to process a functional command.
System action: The system continues processing with the next command.
Application Programmer Response: Increase the size of the storage allocated.

376 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3006I • IDC3008I

System 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 problem reporting data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center. Provide the JCL for the job.
Source: DFSMSdfp
Detecting Module: IDCAL01, IDCBI01, IDCCC01, IDCDE01, IDCED02, IDCLC01, IDCMP01, IDCPR01, IDCRC01,
IDCRM01, IDCRP01, IDCRS05, IDCVY01, IDCXP01

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.
Application Programmer Response: Correct the positioning parameter value. See the I/O error message description
for the I/O error indicated ahead of this message.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCPR01

IDC3007I CATALOG RETURN-CODE IS return-code

Explanation: A catalog error or exceptional condition occurred when processing a command. The system writes this
message when the catalog function requested cannot return a reason code for the failure.
In the message text:
return-code The return code.

For explanation of the catalog return codes, consult message IDC3009I where the return codes are listed with reason
codes. Since the reason codes are not available, consulting IDC3009I will help identify the type of problem but cannot
identify the specific failure.
System action: The system ends the command.
Application Programmer Response: Respond according to the return code listed in IDC3009I. Since there is no
reason code available, the complete action to take may not be available - however identifying the specific return code
will help in identifying the type of failure. IDCAMS may issue other messages preceding IDC3007I that further
describe the failure and these messages may be used to identify the specific problem.
System 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 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
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.
System action: The system ends the request.
System 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 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.

Chapter 20. IDC messages 377

IDC3009I

Source: DFSMSdfp
Detecting Module: IDCSA02

IDC3009I VSAM CATALOG RETURN CODE IS return-code - REASON CODE IS IGGOCLaa - reason-code
Explanation: Catalog management returned this return code and reason code as a result of a catalog error or
exceptional condition.
In the message text:
aa The module identifier.
return-code The return code
reason-code The reason code

For the explanations of a return code and reason code, find the underlined heading for the return code in the
following text and then scan for the associated reason code.

If you are using Library Server, to find the explanations of a return code and reason code quickly, enter the following
search argument:
IDC3009I return-code reason-code

Do not specify leading zeros. For example, suppose you want the find the explanations for the return code and
reason code in the following message:
IEC331I 004-33, XXXXXXXX, YYYYYYYY, OPN VSM ACB, ZZZZZZZZ

The search argument for return code 4 and reason code 33 follows:
IDC3009I 4 33

For the general description of a return code, enter the following search argument:
IDC3009I rcreturn-code

For example, for the general description of return code 4, enter IDC3009I rc4.

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 that have a common description. Most of these reason codes represent internal logic errors,
and they will indicate that you should contact the IBM Support Center.
System action: The system ends processing associated with the error return code.
Operator response: None, unless indicated for specific return and reason codes
Source: DFSMSdfp
Detecting Module: IGG0CLaa
Application Programmer Response: See the programmer response for the specific return code and reason code.
Inspect other messages concerning the DADSM subcomponent or open or close processing to aid in solving the
problem. If necessary, contact the IBM Support Center.
System 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 problem-reporting databases 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.
Some return and reason code combinations might also produce an SVC dump. This dump should also be provided
with any other documentation supplied to the IBM Support Center.
Descriptions of the return codes and reason codes follow.

RETURN CODE 4
Explanation: The system encountered an error while performing open/close processing for a catalog.

378 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

x 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.
2 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.
6 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.
8 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 programming support personnel.
23 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.
25 Explanation: Unable to get CSA storage (subpool 241).
Programmer Response: Increase the size of CSA or run the job when more CSA is
available.
26 Explanation: Unable to get storage for scheduler workarea (subpool 252).
Programmer Response: Increase the REGION size.
27 Explanation: Unable to get CSA for catalog (subpool 241).
Programmer Response: Increase the size of CSA or run the job when more CSA is
available.
30 Explanation: Unable to get in subpool 252.
Programmer Response: Increase the REGION size.
31 Explanation: The VVDS manager encountered an error processing a VSAM volume
record (VVR) request.
32 Explanation: The system was unable to complete verification that the required volume
is mounted.
Programmer Response: Ensure that the unit is available for mounting and that the
correct volume is mounted.
34 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 re-initializing the volume without doing an EXPORT DISCONNECT of any
user catalogs on the volume.
60 Explanation: Unable to get storage in subpool 252 (for EOV) or in subpool 253 (for
CLOSE).
Programmer Response: Increase the REGION size.
83 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.

Chapter 20. IDC messages 379

IDC3009I

Reason Code Description

84 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.
85 Explanation: Unable to get CSA for the catalog ACB or for the PCTT (subpool 241)
Programmer Response: Increase the size of the CSA or run the job when more CSA is
available.
86 Explanation: An error occurred while 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.
102 Explanation: An invalid catalog ACB address was passed in the catalog parameter list.
Programmer Response: Point the ACB pointer passed in the parameter list to the valid
ACB of a user catalog.
104 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.
Programmer Response: Check for allocation problem determination messages in the
job stream output. Follow the programmer response for these messages.
106 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.
Programmer Response: Check for allocation problem determination messages in the
job stream output. Follow the programmer response for these messages.
108 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.
Programmer Response: Check for allocation problem determination messages in the
job stream output. Follow the programmer response for these messages.
114 Explanation: 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.
116
Explanation: The CAS unallocation lock was not available.
Programmer Response: Contact the IBM Support Center.
118 Explanation: The catalog needed for this request has been deleted.
Programmer Response: Redefine the deleted catalog and reissue the request.
120 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.
122 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.

380 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

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 Description

0 Explanation: An entry was not found on LOCATE REQUEST.
Programmer Response: Ensure that the proper entry was specified.
2 Explanation: The catalog cluster record was not found.
Programmer Response: Call your programming support personnel.
6 Explanation: No record was found from record management.
Programmer Response: Ensure that 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.
8 Explanation: A request to place a record by key into a catalog resulted in a duplicate
key error from VSAM.
Programmer Response: Ensure that the entry name is spelled correctly and that the
proper catalog is being used.
12 Explanation: An incorrect entry type occurred for locate on the entry named. The data
set was not found in a catalog.
Programmer Response: Ensure that the proper data set name was specified in the job
control language DD statement.
14 Explanation: A generation data group (GDG) entry type for locate did not find the
specified entry in a catalog.
Programmer Response: Ensure that the proper data set name was specified in the job
control language DD statement.
16 Explanation: A GDG entry was found to be deleted from a catalog.
Programmer Response: Ensure that the proper data set name was specified in the job
control language DD statement.
18 Explanation: A GDG type of locate request specified an incorrect generation number.
Programmer Response: Ensure that the proper data set name was specified in the job
control language DD statement.
20 Explanation: The volume entry being removed from an catalog entry during ALTER
REMOVEVOLUMES processing cannot be found in the catalog record.
Programmer Response: Verify that the volume serial numbers specified actually exist
in the catalog entry for the data set being altered.
38 Explanation: A duplicate entry name or high level index name was found in the target
catalog during a define command. 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 data sets that currently exist with that same high-level qualifier.
40 Explanation: A DEFINE GDG command was not issued prior to the DEFINE
NONVSAM command with GDG entry name.
Programmer Response: Ensure that the GDG base is defined prior to defining the
non-VSAM with a GDG entry name.
42 Explanation: The catalog record for the requested entry could not be found.
Programmer Response: Ensure that the entry name specified on the access method
services command is in the catalog specified.

Chapter 20. IDC messages 381

IDC3009I

Reason Code Description

44 Explanation: A request to place a record by key into an ICF catalog resulted in a
duplicate key error from VSAM.
Programmer Response: If the spelling and catalog being used are correct, run the
DIAGNOSE command to analyze the catalog.
46 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.
50 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.
52 Explanation: A duplicate data component name was found.
Programmer Response: Ensure that all data component names are unique and run the
job again.
54 Explanation: A duplicate index component name was found.
Programmer Response: Ensure that all index component names are unique and run
the job again.

RETURN CODE 10
Explanation: An incorrect record type was found.

Reason Code Description

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

382 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

42 Explanation: A VVDS record contained inconsistent data.
Programmer Response: Run the DIAGNOSE command to check for a damaged VVDS
record.
50 Explanation: VVR or NVR exceeds its maximum size.

RETURN CODE 12
Explanation: An attempt to locate a needed component entry in a catalog record failed.

Reason Code Description

x Explanation: A required component was not found within a catalog record.
Programmer Response: Run the DIAGNOSE command to check for a damaged
catalog record. A SYS1.DUMP may have been produced for this error.

RETURN CODE 14
Explanation: A required cell has not been found in a catalog record when expected.

Reason Code Description

x Explanation: A required cell was not found in a catalog record during processing.
Programmer Response: Run the access method services DIAGNOSE command to
check for a damaged catalog record. A SYS1.DUMP may have been created.

RETURN CODE 16
Explanation: A user issued the ALTER REMOVEVOLUMES command against SMS volumes, which is not allowed.

Reason Code Description

x Explanation: An attempt was made to issue an ALTER command to remove SMS
volumes.
Programmer Response: Do not attempt the incorrect ALTER command. Correct the
commands and rerun the job.

RETURN CODE 18
Explanation: An ALTER error occurred.

Reason Code Description

0 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.
2 Explanation: An attempt to alter a data set's 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.

Chapter 20. IDC messages 383

IDC3009I

Reason Code Description

4-10 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 z/OS MVS System
Messages, Vol 2 (ARC-ASA) for an explanation of the reason code and take the
appropriate action.
12 Explanation: An attempt to alter a data set's security information was rejected.
Security information is no longer supported in catalogs.
Programmer Response: Remove the security-related parameters (READPW,
UPDATEPW, MASTERPW, CONTROLPW, ATTEMPTS, CODE, AUTHORIZATION)
and retry the alter request.
14 Explanation: An ALTER command failed to rename a data set into a generation data
group, because the data set has ACCOUNT information associated with it.
Programmer Response: Copy the data set to a new NonVSAM data set to remove the
ACCOUNT information. Then rename the new data set into the generation data group.
16 Explanation: An ALTER of a VSAM data set with an indirect volume serial is not
supported.
Programmer Response: Ensure that the data set is not a VSAM dataset with an
indirect volume serial, and rerun the ALTER.
98 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 z/OS MVS System
Messages, Vol 2 (ARC-ASA) for an explanation of the reason code and take the
appropriate action.

RETURN CODE 20
Explanation: There is insufficient space in the catalog to perform the requested update or addition.

Reason Code Description

0 Explanation: The catalog cannot be extended for one of the following reasons:
v There is no more space on the volume on which the catalog resides
v The maximum number of extents has been reached
v The catalog has reached the 4GB limit
v There is not enough contiguous space on the volume (required when the catalog’s
secondary allocation is defined in tracks).

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.

RETURN CODE 22

Explanation: The Field Vector Table (FVT) address is zero or an incorrect FVT field was found.

Reason Code Description

x Explanation: An invalid structure was passed as input to a catalog request.

Programmer Response: Contact the IBM Support Center.

384 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

RETURN CODE 24

Explanation: Permanent read error of a catalog.

Reason Code Description

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

RETURN CODE 26

Explanation: A VSAM record management error has occurred.

Reason Code Description

x Explanation: A VS record management error occurred while processing a catalog
request.

Programmer Response: Contact the IBM Support Center. An SVC dump will be
created for this error.

RETURN CODE 28

Explanation: Permanent I/O error in catalog.

Reason Code Description

2 Explanation: An I/O error processing the catalog occurred while processing an access
method services command that requires modifying 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.
4 Explanation: An I/O error occurred during catalog OPEN.

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.
6 Explanation: One or more entries were not deleted due to an I/O related error during
DELETE processing.

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.
26 Explanation: An I/O error occurred while writing the catalog's self-describing records.

Programmer Response: Contact the IBM Support Center.

28 Explanation: A close error occurred after the writing of the catalog's self-describing
records.

Programmer Response: Contact the IBM Support Center.

30 Explanation: An I/O error occurred writing records to the catalog.

Programmer Response: Contact the IBM Support Center.

Chapter 20. IDC messages 385

IDC3009I

RETURN CODE 30

Explanation: Automated Tape Library Data Server (ATLDS) processing error.

Reason Code Description

x Explanation: An internal logic error has occurred.

Programmer Response: Contact the IBM Support Center. An SVC dump may be
created for this error, depending on the specific reason code.
6 Explanation: Attempt to define an alias that relates to a volume category.

Programmer Response: This is an incorrect function. Possible user error.

18 Explanation: The required library name was not specified for a define library request.

Programmer Response: Supply a library name and rerun the job.

20 Explanation: Required library id was not specified for a define library request.

Programmer Response: Supply a library id and rerun the job.

22 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.
34 Explanation: Incorrect name was specified for a define volume category request.

Programmer Response: The volume category's name must begin with

SYS1.VOLCAT.V.
40 Explanation: Incorrect checkpoint indicator was specified for a define volume request.

Programmer Response: Supply a valid checkpoint indicator and rerun the job.
42 Explanation: Incorrect volume location was specified for a define volume request.

Programmer Response: Supply a valid volume location and rerun the job.
44 Explanation: Required library name not specified for a define volume request with a
volume location of library specified.

Programmer Response: Supply a library name and rerun the job.

46 Explanation: Incorrect volume use attribute specified for a define volume request.

Programmer Response: Supply a valid use attribute and rerun the job.
48 Explanation: Required volume name not specified for a define volume request.

Programmer Response: Supply a volume name and rerun the job.

50 Explanation: Incorrect date format specified.

Programmer Response: Re-specify the date in the following format: YYYY-MM-DD.

56 Explanation: Attempt to alter the number of scratch volume message thresholds for an
incorrect media type.

Programmer Response: Supply a valid media type and rerun the job.
58 Explanation: Attempt to alter the number of scratch volumes for an incorrect media
type.

Programmer Response: Supply a valid media type and rerun the job.

386 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

62 Explanation: No general volume category was found.

Programmer Response: Define SYS1.VOLCAT.VGENERAL then rerun the job.

66 Explanation: An attempt was made to create a volume or library record into a
non-volume catalog.

Programmer Response: Ensure the high-level qualifier of the volume or library record
matches the high-level qualifier of the volume catalog.
68 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.
70 Explanation: A duplicate entry name was found during define library or volume
request.

Programmer Response: Remove the duplicate entry and rerun the job.
72 Explanation: General volume category had been deleted or disconnected.

Programmer Response: Redefine or reconnect general volume category.

98 Explanation: Incorrect library name specified for a define library request. The library
name cannot begin with ‘V’.

Programmer Response: Supply a valid library name and rerun the job.
154 Explanation: Attempting to delete a library record which is not empty, or scratch
volumes is not equal to zero.

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
158 Explanation: Attempting to delete a 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.
168 Explanation: Attempting to delete a record without specifying the correct type in
catalog parameter list.

Programmer Response: Specify the type and rerun the job.

RETURN CODE 32

Explanation: There is an error in the catalog parameter list.

Reason Code Description

| x Explanation: The length of the catalog work area specified is either zero or too small.

| Programmer Response: If using the CSI, use the value returned in CSIREQLN for the
| workarea length and try again.

RETURN CODE 36

Explanation: Data set not found or DSCB indicates a VSAM data set.

Chapter 20. IDC messages 387

IDC3009I

Reason Code Description

2 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.
4 Explanation: A data set name was not found on the VTOC.

Programmer Response: Ensure that 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.
12 Explanation: A 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 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 DFSMS hierarchical storage manager
(DFSMShsm), the message with this return code was preceded by one or more DFSMShsm messages (ARCxxxI) that
indicate the processing error.

Reason Code Description

2 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 DFSMShsm determined that the data set was not migrated.

Programmer Response: Review the DFSMShsm message or messages and take the
appropriate action.
4 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).

Programmer Response: Review the DFSMShsm message or messages and take the
appropriate action.
8 Explanation: An error was encountered while attempting to delete a data set with a
volume serial of MIGRAT (the catalog entry indicated that the data set was migrated).

Programmer Response: Review the DFSMShsm message or messages and take the
appropriate action. Check if an attempt to delete a data set in an alternate catalog
occurred, while a duplicately named migrated data set exists in a catalog that can be
found in the standard search order (via the master catalog). If so, recall the migrated
data set and reissue the delete.
12 Explanation: The catalog installation exit module issued a locate request, and catalog
indicated that the request was not successful.

Programmer Response: Review the DFSMShsm message or messages and take the
appropriate action.

388 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

16 Explanation: The catalog installation 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 DFSMShsm was not ready to process the JES3 C/I request because of one of the
following reasons:
v DFSMShsm was not active.
v DFSMShsm 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.

Programmer Response: Review the DFSMShsm message or messages and take the
appropriate action. The DFSMShsm 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.
24 Explanation: The catalog installation exit module was processing a JES3 (C/I) request
for a data set, and determined that the request was from an unauthorized user.

Programmer Response: Review the DFSMShsm message or messages and take the
appropriate action. The DFSMShsm 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.
48 Explanation: The referenced data set is in an incomplete status.

Programmer Response: Recall the data set and then issue your request again.
50 Explanation: DFSMShsm generates this reason code when the installation is using the
DFSMShsm patch to prevent interactive TSO users from being placed in a wait state
while a data set is recalled. This code is generated to cause the locate to fail instead of
placing the TSO session in a wait state and may be ignored. The recall for the data set
has been scheduled and the function causing the recall should be tried again later.

Programmer Response: Submit the requested function again.

52 Explanation: For TSO HSM RECALL requents, the RECALL request has been
converted to a background request when the attention key is used and message
ARC1020I is replied to with 'Y'.

Programmer Response: Information only. No action is required.

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 Description

0 Explanation: The user provided work area is too small.

Programmer Response: Run the job again with a work area length that is at least
equal to the required length.
2 Explanation: The format 1 work area is too small.

Programmer Response: Run the job again with a work area length that is at least
equal to the required length.
8 Explanation: The volume list is too small to include the storage management
subsystem workarea.

Chapter 20. IDC messages 389

IDC3009I

RETURN CODE 42

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 Description

2 Explanation: A DADSM RENAME error occurred on branch entry.
4 Explanation: A DADSM ALLOCATE error occurred on branch entry.
6 Explanation: A DADSM SCRATCH error occurred on branch entry.

RETURN CODE 44

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 occurrences of this problem may indicate logic errors in components or products
that use catalog services.

Reason Code Description

2 Explanation: The delete catalog work area is too small.

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.
4 Explanation: The caller's 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.
6 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.
2. The system does not delete the catalog.

Programmer Response: Run the job again with a larger work area.
8 Explanation: The caller's 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.
12 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.
14 Explanation: The amount of data returned by the system cannot be contained in a
2-byte length field.

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.

RETURN CODE 45

Explanation: The Catalog encountered an unexpected error while issuing the UCBPIN macro.

390 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

1 Explanation: UCBPIN PIN returned an unexpected return code.

Programmer Response: Contact the IBM Service Center. An SVC dump might have
been produced for this error.
2 Explanation: UCBPIN UNPIN returned an unexpected return code.

Programmer Response: Contact the IBM Service Center. An SVC dump might have
been produced for this error.

RETURN CODE 46

Explanation: Catalog received an error from a VSAM request.

Reason Code Description

2 Explanation: VSAM has detected an internal error while processing a catalog index.

Programmer Response: Rerun the request. If the error continues, see z/OS DFSMSdfp
Diagnosis, Chapter 20 VSAM Diagnostic Aids, section entitled “Recovering from Index
Damage” for further instruction.

RETURN CODE 48

Explanation: Incorrect catalog function.

Reason Code Description

x Explanation: An internal logic error has occurred.

Programmer Response: Contact the IBM Support Center.

6 Explanation: An ALTER of a non-VSAM entry is not allowed for the fields being
modified.

Programmer Response: Ensure that 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.
8 Explanation: An ALTER of the catalog name is not allowed.

Programmer Response: Ensure that the catalog name was not used by mistake.
Catalog names can only be changed by DELETE and then re-DEFINE catalog
commands.
10 Explanation: Erase option delete, but file name is for incorrect catalog.

Programmer Response: Do not use a DD name on the catalog parameter in the access
method services DELETE command if erase processing is to be performed.
14 Explanation: A data set is update inhibited.

Programmer Response: Do not open a data set for reset processing that is inhibited for
update processing.
16 Explanation: A data set is not reusable.

Programmer Response: Do not open a non-empty data set for reset processing that is
not reusable.

Chapter 20. IDC messages 391

IDC3009I

Reason Code Description

18 Explanation: It is only valid to change the attributes or owner id fields of a GDG base
entry by the access method services ALTER command.

Programmer Response: Do not attempt the incorrect ALTER commands. Correct the
commands and rerun the job.
24 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.

Programmer Response: Do not attempt the incorrect ALTER commands. Correct the
commands and rerun the job.
26 Explanation: It is not valid to attempt to 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.

Programmer Response: Do not attempt the incorrect ALTER commands. Correct the
commands and rerun the job.
28 Explanation: It is not valid to attempt to 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.
29 Explanation: RBA too large for data set.
30 Explanation: It is not valid to delete the master catalog with the FORCE parameter.

Programmer Response: The master catalog cannot be deleted. Submit the job again.
36 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.
40 Explanation: An incorrect catalog management function, ALTER of a VVDS name,
occurred.

Programmer Response: Do not attempt the incorrect ALTER commands. Correct the
commands. Run the job again.
42 Explanation: The maximum number of extensions was exceeded.

Programmer Response: Redefine the catalog with a RECORDSIZE specifying a

maximum of 32400.
54 Explanation: An incorrect reset of a non-reusable data set was detected.

Programmer Response: Do not open a non-empty data set for reset processing that is
not reusable.
56 Explanation: The data set update is inhibited.

Programmer Response: Do not open a data set for reset processing that is inhibited for
update processing.
60 Explanation: A define no-allocate or RECATALOG was not APF authorized.

Programmer Response: Probable user error. Ensure that access method services is APF
authorized.
64 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.
70 Explanation: An ALTER LOCK of the master catalog is not allowed.

392 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

72 Explanation: An incorrect catalog management function alter of a non-VSAM data set
name that is cataloged with an indirect volser occurred.
74 Explanation: An alter newname of a tape data set is incorrect.

Programmer Response: Do not attempt the incorrect ALTER commands. Correct the
commands. Run the job again.
76 Explanation: An alter of non-VSAM data set that contains the extended format cell is
not allowed.

Programmer Response: None

78 Explanation: The conversion of SMS to non-SMS managed cannot be done for a data
set that contains the extended format cell.
80 Explanation: Define data set with extended format information is not valid for a
non-SMS data set.
90 Explanation: Re-cataloging a temporary VSAM data set is not allowed.
94 Explanation: The conversion of SMS to non-SMS managed cannot be done for a data
set that contains attributes extension information.
96 Explanation: Define data set with attributes extension information is not valid for a
non-SMS data set.
98 Explanation: A define of non-extended data set that contains compress information is
not allowed.

Programmer Response: None

102 Explanation: The request is against an SMS-managed data set, but the specified data
set is not SMS managed.
104 Explanation: The user is not authorized to issue ALTER no VVDS update.
108 Explanation: The specified SMS construct cannot be altered.
112 Explanation: A VSAM data set cannot be converted to an SMS managed data set
because not all of its components' names resolve to the same catalog.
118 Explanation: A SMS storage class construct cannot be blanks.
120 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.
122 Explanation: The ALTER NEWNAME is not allowed for VSAM data set when the new
name resolves to a different catalog than the current one.
124 Explanation: A VSAM data set cannot be converted to SMS managed because not all
of the volumes belong to the same storage group.
126 Explanation: A VSAM data set cannot be converted to SMS managed because not all
of its associated names in the sphere resolve to the same catalog.
128 Explanation: An SMS storage class construct cannot have a length of zero.
130 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.
132 Explanation: Altering a non-specific volume serial to a specific one is a stand-alone
function. No other ALTER functions are allowed.
134 Explanation: The user is not authorized to alter a non-specific volume or the user
attempted to alter a non-SMS managed data set to include non-specific volser.
136 Explanation: An incorrect component was supplied for ALTER non-specific volume.
140 Explanation: An ALTER GDG limit of 0 is not allowed.
142 Explanation: An ALTER fails due to unsuccessful DADSM UPDATE function.
144 Explanation: A Record unit of allocation not valid for linear data sets.
146 Explanation: The ALTER NONVSAM RECATALOG function and the caller pass SMS
information for conversion, but the caller is not authorized to use this function.
148 Explanation: Alter request is not valid for stand-alone function such as alter of backup
while open (BWO) data set.

Programmer Response: Ensure that the field requested to be altered is valid for
stand-alone function.

Chapter 20. IDC messages 393

IDC3009I

Reason Code Description

152 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.
156 Explanation: The alter backup while open (BWO) request is not for valid component
or record.

Programmer Response: Ensure that the BWO alter request is for cluster, data,
non-VSAM, or GDS only.
158 Explanation: The alter backup while open (BWO) indicator is incorrect for non-SMS
managed data sets

Programmer Response: Ensure that the data set is SMS-managed.

160 Explanation: An attempt was made to alter a non-SMS managed non-VSAM data set
to a name in the format of a GDS (for example, the name ends with GnnnnVnn).

Programmer Response: Change the name of the new data set to be a non-GDS format
name.
162 Explanation: An attempt was made to alter a non-SMS managed GDS to a non-GDS
name.
166 Explanation: An alter volume or device type on OAM entries is not allowed.

Programmer Response: None

168 Explanation: An attempt was made to alter an SMS-managed non-VSAM data set to a
GDS name (for example, the name ends with GnnnnVnn), but there is no GDG base
associated with the new name.

Programmer Response: Change the name of the new data set to one that has an
existing GDG base definition.
170 Explanation: When defining an OAM data set, a generation data set low level qualifier
(that is, G0000V00) or an increment of a GDG number (that is, +1) is invalid.

Programmer Response: Use a name other than the GDS low level qualifier or a GDG
increment number. Rerun the define request.
172 Explanation: REUSE was specified for a non-cluster component or a component that
had an AIX Associated with it.
174 Explanation: ALTER REUSE was specified for a cluster that has an AIX defined over
it.
175 Explanation: A DEFINE of a striped data set specified REUSE, which is invalid.
176 Explanation: ALTER REUSE was specified for a cluster that contains a KEYRANGE.
178 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.

184 Explanation: Attempted to ALTER the DDM file class attribute for other than a
CLUSTER or NONVSAM entry.
186 Explanation: Attempted to ALTER the pointer to the last active record for other than
CLUSTER or NONVSAM entry.
188 Explanation: Attempted to ALTER DFM attributes for a non-SMS data set.
190 Explanation: Attempted to ALTER DFM attributes for other than a CLUSTER entry.
192 Explanation: Attempted to ALTER DFM attributes for other than a CLUSTER or
NONVSAM entry.

394 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

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

Programmer Response: Verify that the name of the data set desired is an OAM data
set.
196 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.

Programmer Response: Verify that the name of the data set desired is an OAM data
set.
200 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.
202 Explanation: A request to re-catalog a temporary non-VSAM data set is not valid.

Programmer Response: Correct the request. If the error recurs, contact the IBM
Support Center.
204 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.

216 Explanation: Define of ACCOUNT information is invalid for non-SMS-managed data
sets.

Programmer Response: Ensure that the data set is SMS- managed and then rerun the
request.
218 Explanation: Alter of ACCOUNT information is invalid for non-SMS-managed data
sets.

Programmer Response: Ensure that the data set is SMS-managed and then rerun the
request.
222 Explanation: Extended attribute (AX) cell and ACCOUNT information are mutually
exclusive for define or alter request.

Programmer Response: Ensure that the AX cell and ACCOUNT information are not
both specified during define or alter of the data set.
226 Explanation: Multivolume DEFINE RECATALOG of a data set with an indirect volser
is not supported.

Programmer Response: Ensure that the VOLUME parameter for the DEFINE
RECATALOG has only one indirect volume serial specified before attempting the
DEFINED RECATALOG.

RETURN CODE 50

Explanation: An error has been detected in VVDS manager error. Message IEC331I might be produced for the error
and can contain additional information (SFI) for diagnostic use.

Chapter 20. IDC messages 395

IDC3009I

Reason Code Description

x Explanation: An internal logic error has 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.
2 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.

Programmer Response: None

4 Explanation: VVDS Manager parameter list had incorrect information. This attention
error code does not effect the operation of the request.

Programmer Response: Contact the IBM Support Center.

5 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.
6 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.

Programmer Response: Ensure that 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.
7 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.
8 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.
9 Explanation: A dynamic allocation will require a TIOT slot, but a search finds none
available. No SFI data.

Programmer Response: Contact the IBM Support Center.

10 Explanation: Bad return code from dynamic allocation issued from DFSMS/MVS. SFI
contains the SVC 99 reason code.

Programmer Response: Ensure that 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.
11 Explanation: The caller of the VVDS manager passed a volume serial number in the
parameter list and a UCB address. The UCB's 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.

Programmer Response: Contact the IBM Support Center.

396 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

12 Explanation: An attempt to allocate space on a DASD volume has failed. SFI contains
the historical return code from DADSM allocate.

Programmer Response: Ensure that 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.
13 Explanation: The VSAM volume data set (VVDS) request contained an invalid volume
serial number (VOLSER). The invalid VOLSER might be available with the structured
field introducers (SFI) information.

Programmer Response: Rerun the request with a valid VOLSER.

14 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.
16 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.

Programmer Response: Contact the IBM Support Center.

17 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.
18 Explanation: An I/O error has been detected while accessing a VVDS record. This
reason code results in message IEC161I being issued, which provides more information
about the error. An SVC dump may also have been created, depending on the type of
error that occurred.

Programmer Response: A DIAGNOSE should be run against the VVDS indicated in

message IEC161I. If an SVC dump was produced, contact the IBM Support Center.
25 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.
26 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.
28 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.

Chapter 20. IDC messages 397

 IDC3009I

Reason Code Description

30 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.
| 32 Explanation: The VVDS is full (maximum 1048575 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.
36 Explanation: A request to write a VVR could not be processed because the VVR was
larger than the max size of a valid VVR. SFI contains the VVR length.

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

Programmer Response: Ensure that the correct catalog is being used and that the
VVDS is correctly specified.
40 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.
80 Explanation: An internal VVDS logic error has occurred. If the SFI information
contains “IORUNING”, the job associated with the catalog request may have been
terminated abnormally (for example, operator CANCEL, TSO attention ) and this does
not represent an internal logic error.

Programmer Response: If the SFI information contains “IORUNING”, check console

and job logs for the associated job to see if it was abnormally terminated. You should
run a DIAGNOSE against VVDS on the volume indicated to check for any possible
damage. If the SFI information is not “IORUNING”, you should contact IBM Service.
82 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.

Programmer Response: Print the VVDS and VTOC. Contact the IBM Support Center.
84 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.

Programmer Response: Print the VVDS and VTOC. Contact the IBM Support Center.
85 Explanation: During synchronization processing of the VTOC and VVR extents, the
VVDS manager was unable to read the DSCBS.

Programmer Response: Print the VVDS and VTOC. Contact the IBM Support Center.
86 Explanation: The VVR for the VVDS number of extents field is not valid; it has more
than 123 extents in it. SFI contains the VVR's extent number.

Programmer Response: Print the VVDS. Contact the IBM Support Center.

398 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

87 Explanation: During open processing of a VSAM data set, the system discovered that
there were fewer extents in the VTOC than were described in the VVDS for the
component, or that the extent ranges did not match between the VVDS and VTOC.

System Action: The data set will not be permitted to open. Message IEC331I is issued
to detail which volume and component is incorrect.

Programmer Response: Use LISTCAT and LISTVTOC to determine the details of the
mismatch. The data set must be recreated to correct the error.
88 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.
89 Explanation: During open processing of a VSAM data set, the system discovered that
there were extra extents in the VTOC that are not described in the VVR.

System Action: Message IEC331I is issued to detail which volume and component of
the data set has extra extents on the volume. Open processing continues. In most
cases, on the next extend of the data set the extra extents will be recognized and
incorporated into the data set extents.
92 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.
94 Explanation: A VSAM OPEN request to open the VVDS failed. SFI contains ‘xxrrrrrr’,
where rrrrrr=register 15 from the OPEN and xx is ACBERFLG.

Programmer Response: Determine why the OPEN reason code was returned.
96 Explanation: A record read from the VVDS was found to be invalid.

System Action: Message IEC331I will be issued in the job log and will contain the
RBA and volume serial of the invalid record. An SVC dump will be created for the
problem.

Programmer Response: A DIAGNOSE of the VVDS should be performed and any

errors related to the VVDS corrected. If no errors are detected, contact IBM Service and
provide the SVC dump for analysis.
100 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.

Programmer Response: Determine the source of the non-VSAM data set and have it
renamed or removed.
126 Explanation: VVDS detected a potential problem with VVDS internal structure. When
attempting to correct problem a free control interval (CI) could not be found, which
was required for the repair operation. An SVC dump should have occurred.

Programmer Response: Run a DIAGNOSE and print the VVDS associated with the
problem. Contact IBM Service and provide the SVC dump plus the DIAGNOSE and
print of the problem VVDS.

RETURN CODE 52

Explanation: An error occurred while attempting to access a VTOC.

Chapter 20. IDC messages 399

IDC3009I

Reason Code Description

x Explanation: The reason codes associated with this error are from one of the following:
v OBTAIN return code
v DADSM diagnostic code or DADSM return code
v CVAF CVSTAT code.
Programmer Response: Ensure that there is enough space on the volume and in the
VTOC for the data set being defined. If space was available when the error occurred
and there were sufficient free format 0 DSCBs in the VTOC, contact the IBM Support
Center.

RETURN CODE 56

Explanation: A security verification failed.

Reason Code Description

2 Explanation: The system attempted to verify alter authority to the master catalog
(update authority for an ALTER NEWNAME), but 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.
4 Explanation: A non-system caller has specified request special authority level checking
in the catalog parameter list.

Programmer Response: Contact the IBM Support Center if the user written programs
are not calling catalog management.
6 Explanation: The user did not have the required access authority to the specified entry.

Programmer Response: Ensure the user has the proper RACF authorization for the
function being requested.
8 Explanation: The return code from the RACHECK REQUEST=AUTH was other than 0,
4, or 8.

Programmer Response: Determine the reason for the unexpected RACF return code.
14 Explanation: An implicit alter of a GDG was denied because the user did not have the
proper authority to the GDG base and the catalog.

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

Programmer Response: Ensure the caller is APF authorized, or system key or system
state.
30 Explanation: The caller was not authorized to the catalog when defining an SMS data
set into the master catalog.
32 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.

Programmer Response: Determine the reason for the unexpected RACF return code.
34 Explanation: An internal logic error has occurred.

Programmer Response: Contact the IBM Support Center.

400 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

36 Explanation: The caller is not authorized. When no profile exists for functions that
require RACF authorization, the caller must be at least APF authorized.
40 Explanation: RACF options do not permit use or cataloging of uncataloged non-SMS
managed data sets.
42 Explanation: Caller is not authorized to use the specified volume.

Programmer Response: Acquire authority to the specified volume and resubmit the
job.
44 Explanation: Caller is not authorized to update catalog for DEFINE ATL request

RETURN CODE 58

Explanation: An error was encountered in Define request of the dataset.

Reason Code Description

2 Explanation: The allocation quantity requested for the dataset resulted in an amount
greater than 16,777,215 CYL on the primary space quantity.

Programmer Response: Reduce the primary space quantity and rerun the request.
4 Explanation: The allocation quantity requested for the dataset resulted in an amount
greater than 16,777,215 CYL on the secondary space quantity.

Programmer Response: Reduce the secondary space quantity and rerun the request.
| 6 Explanation: The striped data set was allocated with a primary space allocation of
| more than 16777215 tracks. The maximum primary allocation in tracks that can be
| specified on the define is 16777215.

| Programmer Response: Reduce the primary space allocation and rerun the request.
| 8 Explanation: The striped data set was allocated with a secondary space allocation of
| more than 16777215 tracks. The maximum secondary allocation in tracks that can be
| specified on the define is 16777215.

| Programmer Response: Reduce the secondary space allocation and rerun the request.

RETURN CODE 60

Explanation: Incorrect entry type for requested action.

Reason Code Description

2 Explanation: Probable system error. An incorrect entry type for an extract operation
was detected.

Programmer Response: Ensure that 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.
4 Explanation: An incorrect entry type (cluster or non-VSAM) was detected.

Programmer Response: Ensure that 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.

Chapter 20. IDC messages 401

IDC3009I

Reason Code Description

6 Explanation: An incorrect cluster entry for ALTER of data set attributes was detected.

Programmer Response: Ensure that 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.
8 Explanation: An incorrect cluster or index entry for ALTER of buffer size was detected.

Programmer Response: Ensure that 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.
10 Explanation: An incorrect entry type (CLUSTER) to ALTER the FREESPACE or
WRITECHECK parameters was detected.

Programmer Response: Ensure that 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.
12 Explanation: An incorrect entry type (CLUSTER) to ALTER volumes was detected.

Programmer Response: Ensure that 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.
14 Explanation: Probable system error. An incorrect catalog parameter list was supplied
in an attempt to add a volume.

Programmer Response: Ensure that 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.
16 Explanation: An attempt was made to alter an SMS-managed data set to add or delete
volumes from the data set; however, one or more of the volume specifications were
specific volume serial numbers.

Programmer Response: Only nonspecific volume serial numbers can be added to or

removed from SMS-managed data sets. Correct the specification in the ALTER
command and retry it.
20 Explanation: The upgrade set association in the base cluster data record does not point
to an upgrade set record.

Programmer Response: Ensure that 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.

402 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

22 Explanation: The data association in the cluster record does not point to a data record.

Programmer Response: Ensure that 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.
26 Explanation: ALTER of EXCEPTIONEXIT was specified, but the entry is not a data or
index component.

Programmer Response: Ensure that 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.
28 Explanation: ALTER of average RECORDSIZE was specified, but the entry is not a
data or index component.

Programmer Response: Ensure that 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.
30 Explanation: ALTER of expiration date was specified but the entry is not a cluster,
alternate index, or path.

Programmer Response: Ensure that 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.
32 Explanation: ALTER of last back-up date was specified, but the component is not a
cluster, non VSAM, or GDS.
34 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.
36 Explanation: An alias entry may only be defined for non-VSAM or user catalog
entries.

Programmer Response: Do not attempt an incorrect DEFINE operation.

38 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.
40 Explanation: An input base record to catalog upgrade management is not an alternate
index, cluster or data type entry.

Programmer Response: Ensure that 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 11 option. Contact the IBM Support Center. Otherwise, correct the error.
Run the job again.

Chapter 20. IDC messages 403

IDC3009I

Reason Code Description

42 Explanation: An input base record to catalog reusable processing is not a data type
entry.

Programmer Response: Ensure that 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 11 option. Contact the IBM Support Center. Otherwise, correct the error.
Run the job again.
44 Explanation: An incorrect entry type was encountered in a DELETE operation, other
than the expected alias entry.

Programmer Response: Ensure that the proper entry name was specified and that the
catalog reflects the expected structure. It may be necessary to rebuild the catalog.
46 Explanation: An incorrect entry type was encountered in a DELETE operation, other
than the expected VVR type.

Programmer Response: Ensure that the proper entry name was specified.
48 Explanation: An entry type other than the expected NVR type was encountered in a
DELETE operation.
50 Explanation: An incorrect entry type, other than the expected BCS type, was
encountered in a delete operation.

Programmer Response: Ensure that the correct entry type was specified.
52 Explanation: ALTER of SMS constructs was specified, but the component is not a
cluster, non-VSAM, or GDS.
54 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.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.
60
Explanation: ALTER of FILEDATA is not allowed for non-SMS managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.
62 Explanation: An attempt has been made to alter DFM attributes for a non-SMS
managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.
64 Explanation: ALTER of 'DFM/NFSS ACCESS AUTH' field is not allowed for non-SMS
managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.
66 Explanation: ALTER of 'DFM/NFSS ACCESS TIME' field is not allowed for non-SMS
managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.

404 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

70 Explanation: ALTER of 'DFM/NFSS USERID' field is not allowed for non-SMS
managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.
72 Explanation: ALTER of 'DFM/NFSS GROUPID' field is not allowed for non-SMS
managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.
74 Explanation: ALTER of 'DFM/NFSS LAST SIZE CHANGE' field is not allowed for
non-SMS managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.
76 Explanation: ALTER of 'DFM/NFSS MODIFIED TIME' field is not allowed for
non-SMS managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.
78 Explanation: ALTER of 'DFM/NFSS ATTR CHNG TIME' field is not allowed for
non-SMS managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.
80 Explanation: ALTER of 'DFM/NFSS BINARY FILE SIZE' field is not allowed for
non-SMS managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.
82 Explanation: ALTER of 'DFM/NFSS LOGICAL RECORD COUNT' field is not allowed
for non-SMS managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set.
84 Explanation: ALTER of 'DFM/NFSS CHARS NO PADDING' field is not allowed for
non=SMS managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.
86 Explanation: ALTER of 'DFM/NFSS TEXT TIMESTAMP' field is not allowed for
non-SMS managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.
88 Explanation: ALTER of 'DFM/NFSS ATTRIBUTE EXTENSION FLAGS' is not allowed
for non-SMS managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.
90 Explanation: ALTER of 'DFM/NFSS EXTENSION AREA' field is not allowed for
non-SMS managed data set.

Programmer Response: Ensure that the entry being altered is an SMS managed VSAM
or non-VSAM data set. Correct the error. Run the job again.

Chapter 20. IDC messages 405

IDC3009I

Reason Code Description

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.

Programmer Response: Ensure that the entry being altered is eligible for RLS
processing. Correct the error. Run the job again.
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 temporary are not eligible for RLS access.

Programmer Response: Ensure that the entry being altered is eligible for RLS
processing. Correct the error. Run the job again.
96 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.

Programmer Response: Ensure that the entry being altered is eligible for RLS
processing. Correct the error. Run the job again.
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, keyrange or
temporary are not eligible for RLS access.

Programmer Response: Ensure that the entry being altered is eligible for RLS
processing. Correct the error. Run the job again.
100 Explanation: ALTER of the BWO flag is not allowed for non-SMS managed data set or
a linear data set.

Programmer Response: Ensure that the entry being altered is an SMS 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.

Programmer Response: Ensure that the name of the entry specified in the command is
correct. Ensure that the catalog 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 DUMP11 option. Contact the IBM Support Center. Otherwise, correct the error and
run the job again.
104 Explanation: Invalid entry type for alter of extended addressability data set.
106 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,
keyrange or temporary are not eligible for RLS access.

Programmer Response: Ensure that the entry being altered is eligible for RLS
processing. Correct the error. Run the job again.
108 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.

Programmer Response: Ensure that the entry being altered is eligible for RLS
processing. Correct the error. Run the job again.
110 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.

Programmer Response: Ensure that the entry being altered is eligible for RLS
processing. Correct the error. Run the job again.

406 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

112 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 temporary are not eligible for RLS
access.

Programmer Response: Ensure that the entry being altered is eligible for RLS
processing. Correct the error. Run the job again.

RETURN CODE 62

Explanation: An error was encountered while initializing the extension of a data set.

Reason Code Description

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

Programmer Response: Contact the 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 Description

x Explanation: An internal logic error has occurred.

Programmer Response: Contact the IBM Support Center.

6 Explanation: The association of a true name record in an ICF catalog is incorrect.

Programmer Response: Use access method services to define the associated base of the
true name record.
8
Explanation: The association of a true name record is not in the IEASYMxx member,
or the SYMBOLICRELATE function did not provide a symbolic item.

Programmer Response: Check the IEASYMxx to ensure that the item has a symbolic
item, or the SYMBOLICRELATE function does not provide a symbolic item.

RETURN CODE 66

Explanation: Bad DADSM parameter list.

Reason Code Description

x 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

Explanation: No space is available on the user volume. Only the primary volume will be used for ICF catalogs.

Chapter 20. IDC messages 407

IDC3009I

Reason Code Description

x 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 z/OS DFSMSdfp Diagnosis for
an explanation of the DADSM return and diagnostic codes.

Programmer Response: The return code is returned by DADSM.

22,24 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. If the data set being allocated was not
SMS-managed then reason code 20 indicates requested space was not available; The
primary allocation amount must be able to be allocated within 5 extents. For a non
SMS-managed VSAM data set the primary allocation amount must be available on
each volume if the data set is a multivolume data set.

Programmer Response: The storage group did not contain sufficient space to allocate
the data set. If this was a non SMS-managed data set being allocated, the volume(s)
did not have sufficient space for the primary allocation amount.
26 Explanation: An attempt to allocate an SMS-managed data set using the Best Fit
interface resulted in more than 255 extents for the data set. VSAM data sets are limited
to a maximum of 255 extents.

Programmer Response: This is most likely a result of significant fragmentation on the

volumes selected. Volume reorganization should be performed, or additional volumes
added to the storage group with sufficient contiguous space to allow to the allocate to
complete.
28 Explanation: The volume does not contain enough track-managed space to allocate the
BCS, VVDS or page data set.

Programmer Response: Try the request with a different volume.

RETURN CODE 70

Explanation: Component not found.

Reason Code Description

0 Explanation: An internal logic error has occurred processing a GDS record.

Programmer Response: Contact the IBM Support Center.

RETURN CODE 72

Explanation: The user volume is not mounted. The reason codes are from VSAM open/close/end-of-volume, volume
mount and verify routine IDA0192V.

Reason Code Description

4 Explanation: Unable to mount user volumes.

Programmer Response: Ensure that proper volumes are implicitly or explicitly

allocated by the JCL.
8 Explanation: An error occurred while attempting to mount the user volume. Examples
of possible errors include insufficient virtual storage for workareas or a time-stamp
mismatch problem.

Programmer Response: Verify that the 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.

408 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

RETURN CODE 74

Explanation: Cell not found.

Reason Code Description

0 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.
2 Explanation: The relate cell was not found in the base cluster sphere record while a
moved subrecord update was in progress.

Programmer Response: Run access method services DIAGNOSE command against the
catalog and then determine the action to be taken. Delete with the NOSCRATCH
parameter. Define with the RECATALOG parameter.
4 Explanation: An association cell was not found for a path or alias record while a
subrecord move update was in progress.

Programmer Response: Run access method services DIAGNOSE command against the
catalog and then determine the action to be taken. Delete with the NOSCRATCH
parameter. Define with the RECATALOG parameter.
10 Explanation: The SMS cell was not found in the VVDS entry for a data set, even
though the data set is SMS-managed.

Programmer Response: Run access method services DIAGNOSE command against the
catalog and then determine 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.
12 Explanation: The SMS cell was not found in the BCS entry for a data set, even though
the data set is SMS-managed.

Programmer Response: Run access method services DIAGNOSE command against the
catalog and then determine the action to be taken. The catalog may be repaired by
doing a DELETE NOSCRATCH, followed by DEFINE RECATALOG.

RETURN CODE 76

Explanation: No unit available for mounting or volume not mounted.

Reason Code Description

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

Programmer Response: Ensure that 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.

Chapter 20. IDC messages 409

IDC3009I

Reason Code Description

2 Explanation: The volume was not mounted when expected.

Programmer Response: Ensure that 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.
8 Explanation: A scan of the task I/O table (TIOT) failed to find a needed JCL DD
statement.

Programmer Response: Ensure that 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.

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.
10 Explanation: A scan of the task I/O table (TIOT) failed to find the user specified JCL
ddname statement.

Programmer Response: Ensure that 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.
12 Explanation: A scan of the task I/O table (TIOT) failed to find the user specified JCL
ddname statement.

Programmer Response: Ensure that JCL statements cause the proper volumes and
units to be allocated. Also, ensure that all dynamis 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 78

Explanation: Subrecord move error.

Reason Code Description

x Explanation: An internal logic error occurred while processing a subrecord.

Programmer Response: Contact the 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 Description

x Explanation: An internal logic error occurred.

Programmer Response: Contact the IBM Support Center.

410 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

0 Explanation: The related object is reusable.

Programmer Response: Correct the DEFINE command so that the entry named in the
RELATE parameter is proper for the type of object being defined.
2 Explanation: The related object is a relative-record data set or a linear data set.

Programmer Response: Correct the DEFINE command so that the entry named in the
RELATE parameter is proper for the type of object being defined.
4 Explanation: The related object does not exist.

Programmer Response: Correct the DEFINE command so that the entry named in the
RELATE parameter is proper for the type of object being defined.
6 Explanation: An alternate index or path is not allowed to be built over a catalog.

Programmer Response: Correct the DEFINE command so that the entry named in the
RELATE parameter is proper for the type of object being defined.
8 Explanation: The names of an alternate index or path and a related object are identical.

Programmer Response: Correct the DEFINE command so that the entry named in the
RELATE parameter is proper for the type of object being defined.
10 Explanation: There is no pointer to a related object of an alternate index or path.

Programmer Response: Correct the DEFINE command so that the entry named in the
RELATE parameter is proper for the type of object being defined.
12 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.

Programmer Response: Correct the DEFINE command so that the entry named in the
RELATE parameter is proper for the type of object being defined.
14 Explanation: A DEFINE PATH command specified a PATHENTRY name of a
PAGESPACE object.

Programmer Response: Correct the path entry name. Run the DEFINE PATH
command again.
16 Explanation: A DEFINE PATH command has specified a PATHENTRY name for a
VVDS.

Programmer Response: Correct the path entry name. Run the DEFINE PATH
command again.
20 Explanation: The related object for a DEFINE ALTERNATEINDEX is a VVDS.

Programmer Response: Correct the related name. Run the DEFINE AIX command
again.
28 Explanation: The related name specified for a DEFINE ALIAS command is for a record
type other than NONVSAM or USERCATALOG.

Programmer Response: Ensure that 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.
30 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.

Programmer Response: Correct the version number in the GnnnnVnn part of the
generation data set name. Run the DEFINE ALIAS command again.

Chapter 20. IDC messages 411

IDC3009I

Reason Code Description

36 Explanation: An AIX (alternate index) data set specified non-Extended-Format on the
define, but the base cluster is an Extended-Format data set.

Programmer Response: Check the definition of the base cluster to ensure that it is also
non-Extended-Format.
38 Explanation: An AIX (alternate index) data set specified Extended-Format on the
define, but the base cluster is not an Extended-Format data set.

Programmer Response: Check the definition of the base cluster to ensure that it is also
Extended-Format. The data class attribute is the source for requesting
Extended-Format, so verify that the proper data class was used
40 Explanation: The related object is a variable relative-record data set.
42 Explanation: The data set type in the RELATE parameter for a DEFINE
ALTERNATEINDEX command is an extended addressability ESDS.

Programmer Response: Change the type of the related data set to a non-extended
addressability ESDS.

RETURN CODE 84

Explanation: Date error.

Reason Code Description

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

Programmer Response: Specify the PURGE option if desired. Run the DELETE
command again.
2 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).
4 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.

Programmer Response: Specify the PURGE option if desired. Run the DELETE
command again.

RETURN CODE 86

Explanation: Recatalog error.

Reason Code Description

0 Explanation: No related PATHENTRY name was found on the path catalog record.

Programmer Response: Ensure that the PATHENTRY name is correct. If it is, refer to
access method services, DIAGNOSE command, to obtain additional information.

412 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

2 Explanation: An internal logic error occurred.

Programmer Response: Contact the IBM Support Center.

4 Explanation: Something other than a CLUSTER or alternate index type object specified
the RECATALOG parameter.

Programmer Response: Ensure that the object being recataloged is a cluster or

alternate index.
6 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.
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.

Programmer Response:

If no VVR exists, then re-issue the DEFINE command, without the RECATALOG
parameter, for the ICF catalog.

If the VVR exists but points to a different catalog, specify the correct catalog and
re-issue the DEFINE command with the RECATALOG parameter.

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 RECATALOG parameter.
8 Explanation: The RECATALOG parameter is incorrect on the DEFINE command for an
ICF catalog.
10 Explanation: The catalog associated with this data set does not match the catalog
name found in the VVR.

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.

If your data sets is not one of those types, print the VVR to determine which catalog
the data set should be associated with.
12 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.
14 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.
16 Explanation: NVR for the object being recataloged was not found on the volume serial
numbers specified.
18 Explanation: Something other than the expected NVR was retrieved.

Chapter 20. IDC messages 413

IDC3009I

Reason Code Description

20 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.
22 Explanation: The VVR/NVR catalog name does not match the name of the catalog
currently oriented to.
24 Explanation: The DEFINE RECATALOG command detected that a volume for a data
component is missing from the volume list.

Programmer Response: Ensure that any missing volumes are supplied when issuing
the DEFINE RECATALOG command.
26 Explanation: The DEFINE RECATALOG command detected that the last volume for a
data component is missing from the volume list.

Programmer Response: Ensure that any missing volumes are supplied when issuing
the DEFINE RECATALOG command.
28 Explanation: The DEFINE RECATALOG command detected that the last volume of a
stripe for a data component of a striped VSAM data set is missing from the volume
list.

Programmer Response: Ensure that any missing volumes are supplied when issuing
the DEFINE RECATALOG command.
30 Explanation: The DEFINE RECATALOG command detected that a volume for an
index component is missing from the volume list.

Programmer Response: Ensure that any missing volumes are supplied when issuing
the DEFINE RECATALOG command.
32 Explanation: The DEFINE RECATALOG command detected that the last volume for
an index component is missing from the volume list.

Programmer Response: Ensure that any missing volumes are supplied when issuing
the DEFINE RECATALOG command.
34 Explanation: The DEFINE RECATALOG command detected that the last volume of a
stripe for an index component of a striped VSAM data set is missing from the volume
list.

Programmer Response: Ensure that any missing volumes are supplied when issuing
the DEFINE RECATALOG command.
36 Explanation: An indirect volume serial was used in the DEFINE RECATALOG for a
VSAM non-LDS data set.

Programmer Response: Ensure that the data set is a VSAM linear data set and marked
zFS.
38 Explanation: DEFINE RECATALOG using an indirect VOLSER was attempted for a
VSAM indexed data set.

Programmer Response: Ensure that the data set is a VSAM linear data set and is
marked zFS.

414 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

40 Explanation: DEFINE RECATALOG using an indirect VOLSER entry was not marked
zFS or was a non-LDS data set.

Programmer Response: Ensure that the data set is a VSAM linear data set and marked
zFS.

RETURN CODE 90

Explanation: Delete error.

Reason Code Description

2 Explanation: An attempt was made to delete the Master Catalog.

Programmer Response: Determine if the correct catalog is specified. If so, run the job
again with a different master catalog.
4 Explanation: The system was unable to determine if the catalog is empty.

Programmer Response: Specify FORCE, RECOVERY, or run DIAGNOSE and

recommended action.
6 Explanation: An incorrect DELETE TRUENAME request was specified. The associated
base object exists.

Programmer Response: User error.

8 Explanation: A pagespace record was damaged. It could not be determined if
pagespace was active.

Programmer Response: Run DIAGNOSE and take the recommended action.

10 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.
12 Explanation: A required FILE parameter was not specified on the DELETE VVR
command.

Programmer Response: Specify FILE parameter. Run the job again.

14 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.
16 Explanation: DELETE VVR request for a VVR with an associated catalog.

Programmer Response: User error.

18 Explanation: The usercatalog parameter is missing.

Programmer Response: Specify the file parameter. Run the job again.
20 Explanation: DELETE NVR request for a NVR with an associated catalog.

Programmer Response: This is probably a user error.

22 Explanation: No DD was found to match the DD name on the DELETE NVR request.

Programmer Response: User error. Respecify the DDname in the FILE parameter. Run
the job again.

Chapter 20. IDC messages 415

IDC3009I

Reason Code Description

24 Explanation: The request is to delete an SMS data set only, but the data set is non-SMS
managed.

Programmer Response: This is probably a user error.

26 Explanation: A required FILE parameter was not specified on the DELETE NVR
command.

Programmer Response: This is probably a user error.

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

Programmer Response: This is probably a user error.

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

34 Explanation: DELETE VVR resulted in an attempt to delete a non-VSAM DSCB.
Nothing was deleted.

Programmer Response: User error. DELETE VVR cannot be used to delete non-VSAM
data sets.
36 Explanation: DELETE VVR resulted in an attempt to delete a DSCB whose name
resolves to an associated keyrange VVR. Nothing was deleted.

Programmer Response: User error. Use DELETE CLUSTER.

38 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.
40 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.
42 Explanation: An NVR was retrieved during a DELETE VVR request.

Programmer Response: User error. Specify DELETE NVR and run the job again.
44 Explanation: A VVR was retrieved during a DELETE NVR request.

Programmer Response: User error. Specify DELETE VVR and run the job again.
46 Explanation: DELETE VVR failed to specify the system master catalog name in the
catalog parameter.

Programmer Response: User error. Rerun the failing DELETE VVR job specifying the
system master catalog name in the catalog parameter.
48 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.
50 Explanation: DELETE failed because SMSVSAM Server was not available.

Programmer Response: Retry the operation when the SMSVSAM Server is available.

416 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

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

54 Explanation: DELETE failed because the data set is being renamed but it has not
completed.

Programmer Response: Rename the data set with the IDCAMS ALTER command and
then delete it.
| 56 Explanation: A DELETE USERCATALOG or EXPORT DISCONNECT command issued
| against a user catalog failed because the catalog contains one or more user catalog
| connector extension records, which are not allowed in a pre-z/OS V1R13 system.

| Programmer Response: In order to delete user catalog connector records, issue

| EXPORT DISCONNECT for the user catalog on a system at the z/OS V1R13 level or
| higher.

RETURN CODE 94

Explanation: A DADSM OBTAIN request failed during a catalog delete request.

Reason Code Description

4 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.
8 Explanation: OBTAIN did not find requested format-1 DSCB on specified volume.

Programmer Response: Ensure that the correct volume is mounted.

12 Explanation: OBTAIN encountered an I/O error in the volume's VTOC.

Programmer Response: Check for a possible hardware error.

x Explanation: The reason code is the OBTAIN return code.

Programmer Response: Determine the meaning of the obtain return code. Correct the
error. Run the job again.

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 Description

0 Explanation: The key specified for spanned record exceeds the control interval size.

Programmer Response: Correct the erroneous parameter (KEYS or RECORDSIZE).

Run the job again.
4 Explanation: The maximum logical record size for spanned records exceeds the control
area size.

Programmer Response: Correct the erroneous parameter (KEYS or RECORDSIZE).

Run the job again.

Chapter 20. IDC messages 417

 IDC3009I

Reason Code Description

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

Programmer Response: Correct the erroneous parameter (KEYS or RECORDSIZE).

Run the job again.
8 Explanation: The alternate index key position plus the key length for the base cluster
is larger than the record size.

Programmer Response: Correct the erroneous parameter (KEYS or RECORDSIZE).

Run the job again.

RETURN CODE 98

Explanation: An unusual condition occurred during an ALTER name of a unique or non-VSAM data set.

Reason Code Description

x Explanation: The reason code is the same as returned by the DADSM RENAME
function in the status byte of the RENAME volume list.

Programmer Response: Determine the meaning of the RENAME return code, as

documented in the "Status Codes from RENAME" section in z/OS DFSMSdfp Diagnosis.
Correct the error. Run the job again.

|| RETURN CODE 100

| Explanation: Generic locate error.

|
|| Reason Code Description
| 10 Explanation: The data set name is indicated as a NEWNAME in an ALTER
| NEWNAME request that has not completed.

| Programmer Response: Determine if the ALTER NEWNAME request has completed. If

| so, run the request again to get the correct information.
|
RETURN CODE 102

Explanation: A DADSM SCRATCH request failed during a catalog delete request for a unique or non-VSAM data set.

Reason Code Description

x Explanation: The reason code is the DADSM SCRATCH function status code.

Programmer Response: Determine the meaning of the SCRATCH status code. See z/OS
DFSMSdfp Diagnosis for these status codes and take the appropriate corrective action
before rerunning the job that failed.

|| RETURN CODE 104

| Explanation: An error occurred with a LOCATE request.

|

418 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

|| Reason Code Description

| 2 Explanation: At least one user catalog connector extension record was found when
| locating the association entries of a user catalog on a pre-V1R13 system. You can only
| use user catalog extension records on a z/OS V1R13 or later system. The system might
| not return all the association entries in the usercatalog.

| Programmer Response: Retry the operation on V1R13 or higher systems to retrieve all
| the association entries of a user catalog.
|
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 Description

0 Programmer Response: The message indicates that the caller's 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 Description

4 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.
8 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.

RETURN CODE 112

Explanation: Incorrect field parameter list (FPL).

Reason Code Description

4 Explanation: An internal logic error occurred.

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.

Chapter 20. IDC messages 419

IDC3009I

Reason Code Description

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

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 116

Explanation: A catalog record has been damaged, or contains inconsistent data.

Reason Code Description

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

RETURN CODE 118

Explanation: The data set name is ineligible for RACF definition.

Reason Code Description

0 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.
Programmer Response: Check the installation security subsystem guidelines for
defining a data set in the security subsystem. Modify the data set characteristics
accordingly.
12 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.

RETURN CODE 120

Explanation: Attempt to modify the non-existent or system field. This is a system error.

RETURN CODE 122

Explanation: Reflects error return code 8 when set by the common filter service.

Reason Code Description

0 Explanation: invalid field name passed.
Programmer Response: Contact the IBM Support Center.
2 Explanation: The storage management subsystem field in the BCS is inconsistent with
that field in the VVDS entries.
Programmer Response: Contact the IBM Support Center.

420 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

RETURN CODE 124

Explanation: Incorrect control interval number.

Reason Code Description

2 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.
34 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.
36 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: Run an access method services DIAGNOSE command, and
EXAMINE DATATEST against the catalog. The catalog may need to be recovered.

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 Description

ACS reason code = catalog Explanation: Catalog management can only support ACS services reason codes from
reason code + 1000 1000 to 1255. The ACS services return and reason codes are documented in the z/OS
DFSMSdfp Diagnosis.

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 z/OS DFSMSdfp Diagnosis 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 Description

0 Explanation: An integrity check of the user catalog parameter list (CPL), the FPL, or
the FVT, failed.
Programmer Response: Contact the IBM Support Center unless a user-written
program is interfacing directly with catalog management.
2 Explanation: A storage validity check failed on a user FPL or on the user work area
referenced from the CPL.
Programmer Response: Contact the IBM Support Center unless a user-written
program is interfacing directly with catalog management.
6 Explanation: A CPL field that references the work area is zero.
Programmer Response: Contact the IBM Support Center unless a user-written
program is interfacing directly with catalog management.

RETURN CODE 130

Explanation: An ALTER RENAME recatalog error.

Chapter 20. IDC messages 421

 IDC3009I

Reason Code Description

4 Explanation: Only the old name catalog entry remains to be deleted, but the VTOC
still has the DSCB with the old name.
6 Explanation: Only the old name catalog entry remains to be deleted, but the VVDS
still has the NVR with the old name.
8 Explanation: The DSCB has been renamed, but no DSCB with either the old name or
the new name can be found.
10 Explanation: The data set DSCB cannot be located.
12 Explanation: The NVR has been renamed, but the NVR with the new name cannot be
located.
14 Explanation: There should be an NVR with the old name, but that NVR cannot be
located.
16 Explanation: The DSCB has been renamed without error, but the NVR cannot be
renamed because there is already an NVR with that name.
| 18 Explanation: The data set name specified in NEWNAME is involved in another
| ALTER NEWNAME request that is not yet complete.

RETURN CODE 132

Explanation: Incorrect pointer value in argument list. Probable system error.

Reason Code Description

x 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 Response: Contact the IBM Support Center.
0 Explanation: Expected component not found.
10 Explanation: A UCB address passed to the Catalog Address Space was found to be
invalid during an attempt to capture the UCB in the Catalog Space.
Programmer Response: Attempt to rerun the failing request. If it continues to fail,
create an SVC dump by using the MODIFY CATALOG,DUMPON command and
contact the IBM Support Center.
20 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.
Programmer Response: Contact the IBM Support Center unless a user-written
program is interfacing directly with catalog management.
48 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.
Programmer Response: Run the DIAGNOSE command to check for a damaged
catalog record. Contact the IBM Support center if message IEC251I was issued.
122 Explanation: Define master catalog or user catalog with extended format information
or attributes extension information is not valid.
124 Explanation: Backout while open specification not valid for non-VSAM data set.
126 Explanation: Backout while open specification not valid for ALTER of non-SMS data
set.
128 Explanation: An internal logic error has occurred.
Programmer Response: Contact the IBM Support Center.
130 Explanation: An internal logic error has occurred.
Programmer Response: Contact the IBM Support Center.
132 Explanation: Record Level Sharing attributes not valid for non-VSAM data set.
134 Explanation: Record Level Sharing attributes not valid for non-SMS data set.

422 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

RETURN CODE 136

Explanation: Required parameters not supplied. Probable system error.

Reason Code Description

x Explanation: An internal logic error has occurred.
Programmer Response: Contact the IBM Support Center.
20 Explanation: The key length is required and has not been provided.
Programmer Response: Ensure that a valid key length is specified for the data set.
22 Explanation: A unique data set needs a DD statement for a rename, or the DD
statement is missing.
Programmer Response: Supply a dname job control statement.
32 Explanation: An alias name was not provided on a DEFINE command.
Programmer Response: Correct the DEFINE command. Run the job again.
34 Explanation: GDG limit or attribute data were not provided on a DEFINE command.
Programmer Response: Correct the DEFINE command. Run the job again.
40 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.
42 Explanation: An error occurred from IDA0192V while attempting to mount a volume
required for DELETE NONVSAM SCRATCH processing.
Programmer Response: Ensure that the mountable unit was allocated for DELETE
processing.
46 Explanation: No storage class information was passed for an SMS managed data set.

RETURN CODE 138

Explanation: DADSM RENAME error.

Reason Code Description

x Explanation: Volume status code from DADSM.

RETURN CODE 140

Explanation: Inconsistent or conflicting arguments were provided.

Reason Code Description

2 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.
4 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.
Programmer Response: Correct the DEFINE command.
6 Explanation: Key ranges were found on both data and cluster catalog FVT. 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.

Chapter 20. IDC messages 423

IDC3009I

Reason Code Description

8 Explanation: The work area is too small. 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.
10 Explanation: Space parameters were found on both cluster and data catalog FVT. 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.
20 Explanation: The key lengths for data and index are not equal. 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 Explanation: There are an unequal number of volume serial numbers and file sequence
numbers in list entries.
Programmer Response: Correct the input. Run the job again.
30 Explanation: More device type entries exist than volume serial numbers.
Programmer Response: Correct the input. Run the job again.
34 Explanation: An incorrect space request type on DEFINE was detected. 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.
44 Explanation: A relative-record data set has a maximum record length that is not equal
to the average record length.
Programmer Response: Correct the input. Run the job again.
60 Explanation: The logical record size for an ICF catalog has been exceeded. The
DEFINE ALIAS has caused the updated catalog record to exceed the catalog's logical
record size.
Programmer Response: Redefine the 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. If
the catalog record size is already 32,400, no more aliases may be defined for this
catalog. A new catalog will need to be created for subsequent aliases, or existing
aliases will need to be deleted from the current catalog.
62 Explanation: The maximum average logical record size is less than 4086 bytes for an
ICF catalog define.
Programmer Response: Increase the maximum average logical record size. Run the
DEFINE command again.
64 Explanation: An incorrect group code for field management was detected.
Programmer Response: This is a system programming error.
66 Explanation: The component key length exceeds the limit.
Programmer Response: Run the DIAGNOSE command to check for a damaged
catalog record.
72 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.
74 Explanation: The define of a VVDS had the INDEX option specified. A VVDS is an
entry sequenced data set.
Programmer Response: Remove the INDEX option. Run the define operation again.
78 Explanation: The request to field management was not valid.
Programmer Response: Check the CPL for calling field management.

424 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

80 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.
v Define a new ICF catalog with a larger maximum spanned record size. The default
is 32,400 bytes.
82 Explanation: Key ranges are not allowed on a DEFINE of an ICF catalog.
Programmer Response: Remove the KEYRANGES parameter. Run the DEFINE
command again.
84 Explanation: The REUSE parameter was specified with UNIQUE or KEY ranges.
Programmer Response: Remove one of the conflicting parameters. Run the DEFINE
command again.
90 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 an indirect volser
****** or a symbolic volser &xxxxx.
Programmer Response: If the indirect or the symbolic volser feature (a non-VSAM
data set defined with a volser of ******) is wanted, remove the other volsers from the
DEFINE request.
92 Explanation: A format 2 work area is incorrect for this catalog request.
Programmer Response: Run the job again with a format 1 work area.
94 Explanation: DEFINE NONVSAM no BCS for a non-SMS managed data set cannot be
requested.
96 Explanation: DEFINE NONVSAM no NVR for a non-SMS managed data set cannot be
requested.
98 Explanation: The new record length will exceed the maximum VVR or NVR size.
100 Explanation: The number of volumes passed exceeds the number of UCB addresses.
102 Explanation: The Volser in the UCB does not match the volser in the volume list.
104 Explanation: An incorrect number of device types were passed for the ALTER
non-specific volume request.
106 Explanation: An incorrect number of volumes were passed for the ALTER non-specific
volume request.
110 Explanation: Either of the following problems occurred:
v The calculation of space required for a VSAM data set resulted in a high-allocated
RBA greater than 4 GB, and the data set is not an extended addressability data set.
This might occur either during the initial definition or during an attempt to extend
the data set.
v The number of control intervals or control areas required for the data set exceeded 4
GB.

Programmer Response: Define the data set with a smaller space allocation request.
112 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 DEFINE command again.
116 Explanation: A request was made to compress a data set that is not an Extended
Format data set.

Programmer Response: Contact the IBM Support Center.

120 Explanation: Compressible request is allowed for KSDS data set only.

Programmer Response: Change the job to define the data set as a non-compressible
data set.

Chapter 20. IDC messages 425

IDC3009I

Reason Code Description

122 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.
124 Explanation: Invalid data set type for extended addressability.
Programmer Response: Clean up the GDG in error then catalog G1000Vxx.

RETURN CODE 142

Explanation: DADSM OBTAIN error.

Reason Code Description

x Explanation: Return code from OBTAIN.

RETURN CODE 144

Explanation: An incorrect entry name format or the name has an initial character as a numeric.

Reason Code Description

2 Explanation: An incorrect first character, non-alphabetic, was detected. The alternate
index or path name is incorrect.
Programmer Response: Correct the entry name.
6 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.
8 Explanation: A syntax error was encountered in examining a GDG name.
Programmer Response: Correct the name. Run the job again.
10 Explanation: A reserved high-level qualifier name was specified on an ICF define
operation. CATINDEX is a reserved high-level qualifier.
Programmer Response: Change the name to use a different high-level qualifier. Run
the define operation again.
12 Explanation: The data name specified for an SMS VSAM data set does not orient to
the same user catalog that the cluster did.
14 Explanation: The data set name to be added to the catalog does not meet the syntax
requirements for a valid cataloged data set name. For information about valid
cataloged data set names, see z/OS DFSMS Using Data Sets.
Programmer Response: Correct the data set name so that it meets the requirements for
a valid cataloged data set name.
16 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.

Reason Code Description

2 Explanation: An incorrect storage class name length was detected.
4 Explanation: An incorrect data class name length was detected.
6 Explanation: An incorrect management class name length was detected.

RETURN CODE 152

Explanation: A non-empty catalog cannot be deleted.

426 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

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

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 Description

2 Explanation: A GETMAIN failure occurred. There is insufficient virtual storage
available.
Programmer Response: Increase the region size available to the step.
10 Explanation: A GETMAIN failure occurred. There is insufficient virtual storage
available for the catalog communication area.
Programmer Response: Increase the region size available to the step.

RETURN CODE 168

Explanation: Unsupported device type.

Reason Code Description

2 Explanation: One of the following has occurred:
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.

Programmer Response: Specify a device type or device name that is acceptable to the
system.
4 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 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 Description

x Explanation: The return code from a failed DADSM RENAME.
2 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).

Chapter 20. IDC messages 427

IDC3009I

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. The problem might also be with the size of
the VTOC index or lack of room in it.

Reason Code Description

0 Programmer Response: Delete any unneeded data sets or data spaces from the volume
to make additional DSCBs available, or re-create the volume with a larger VTOC.

RETURN CODE 178

Explanation: An error occurred during ICF catalog processing of a VSAM partial release request.

Reason Code Description

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

Programmer Response: Run an IDCAMS verify against the data set to reset the
open-for-output indicator and re-run the partial release request.
4 Explanation: The data set is not an extended format VSAM cluster. Partial release
processing is supported only for extended format VSAM clusters.
6 Explanation: The data set name passed to a VSAM partial release request was not a
VSAM cluster data component.

Programmer Response: Ensure the name being passed is the VSAM cluster data
component and re-run the partial release request.
8 Explanation: A DADSM partial release request failed.

Programmer Response: Examine the job and system log for related messages
explaining the DADSM failure.
10 Explanation: An attempt was made to perform partial release processing against a
data set defined with guaranteed space. Guaranteed space data sets are not supported
for partial release processing.
12 Explanation: An attempt to release excess space has been made for this data set, but
the data set is not eligible for partial release processing. The data set is a multi-volume
data set that was created through space constraint relief processing and the high use
RBA for the data set is not in the range of an extent on the last volume of the data set.

System Action: The request to release the space is ignored.

14 Explanation: Rounding for multi-cylinder unit (MCU) boundary prevented partial
release of space.

System Action: The request to release the space is ignored.

18 Explanation: The primary volume RBAs are out of order for this multivolume partial
release request. Correct, and rerun.

Programmer Response: Run IDCAMS DEFINE RECATALOG with the volumes in

RBA order.

RETURN CODE 182

Explanation: Bad DADSM UPDATE parameter list.

428 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

x Explanation: Internal logic error.

Programmer Response: Contact the IBM Support center.

RETURN CODE 184

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
that is currently active.

Reason Code Description

0 Explanation: A rename is not allowed for an open data set. The backout has been done
successfully.
2 Explanation: The data set is currently open to another user.
4 Explanation: The data or index component (or both) is in use, and the data set cannot
be deleted.

Programmer Response: Run the command again. To ensure proper completion, specify
a disposition parameter of OLD, not SHR.
6 Explanation: The attempted DELETE or ALTER of a PAGESPACE, or attempted
DELETE CATALOG FORCE that implicitly deletes a PAGESPACE, cannot be allowed.
The pagespace is currently in use on this or another system sharing the volume that
contains the pagespace.

Programmer Response: If a PAGESPACE is to be deleted or altered, it must not be in

use by any system that shares the volume on which it is located.
8 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.

Programmer Response: Run the requested function again after verifying the data set is
not currently being dumped.
10 Explanation: An attempt has been made to alter one of the attributes LOG,
LOGSTREAMID, or BWO for a data set that is currently open.

System Action: The request is terminated.

Programmer Response: Reissue the ALTER request when the target data set is not
open.

RETURN CODE 186

Explanation: Error attempting to lock a catalog or access a locked catalog.

Reason Code Description

0 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 authorization. Run the job
again.

Chapter 20. IDC messages 429

IDC3009I

Reason Code Description

2 Explanation: Access was denied for one of the following reasons:
v No profile IGG.CATLOCK of class type FACILITY was found
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.
4 Explanation: The caller was not 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.
6 Explanation: The caller was not 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 authorization. Run the job again.

RETURN CODE 188

Explanation: As a catalog management return code:

Reason Code Description

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

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.

RETURN CODE 190

Explanation: Authorization error on a facility class function applied to SMS data sets.

Reason Code Description

0 Explanation: The function was ALTER BCS only.
2 Explanation: The function was DIRECTED CATALOG.
4 Explanation: The function was DEFINE NONVSAM with no BCS.
6 Explanation: The function was DEFINE NONVSAM with no NVR.
8 Explanation: The function was DELETE NVR with no BCS check.
10 Explanation: The function was DELETE NOSCRATCH.
12 Explanation: The function was DELETE GDG FORCE.
14 Explanation: The function was ALTER UNCONVERT from SMS managed VSAM data
set back to non-SMS managed.

430 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

Reason Code Description

16 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'.

RETURN CODE 192

Explanation: Maximum logical record length specified is greater than 32,761 for a non-spanned data set.

Reason Code Description

0 Programmer Response: Reduce the maximum logical record length or define the data
set as spanned.

RETURN CODE 194

Explanation: An error occurred during multi-level alias (MLA) facility processing.

Reason Code Description

8 Explanation: MLA was unavailable for the request.

Programmer Response: Enter the F CATALOG, MLA(REFRESH) or F CATALOG,

RESTART command to re-enable the MLA.
10 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.
14 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.
18 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.
20 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.
28 Explanation: An error occurred during a generic search of the alias table for the input
data set name.
30 Explanation: MLA was unable to obtain sufficient memory to hold its in-storage tables.
34 Explanation: MLA was unable to obtain sufficient memory to rebuild its in-storage
tables.
40 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.
42 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.
44 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.
46 Explanation: An error occurred during a generic search of the alias table for the input
data set name.

Chapter 20. IDC messages 431

IDC3009I

Reason Code Description

50 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 Description

0 Programmer Response: Reduce the control interval size of the data component.

RETURN CODE 198

Explanation: An attempt has been made to use an unsupported feature.

RETURN CODE 200

Explanation: The specified or defaulted control interval size of the index component is greater than the maximum
block size of the index device.

Reason Code Description

0 Programmer Response: Reduce the control interval size of the index component or use
a different device with a larger maximum block size.

RETURN CODE 202

Explanation: Storage management subsystem call error.

Reason Code Description

0 Explanation: An error was detected during a call to SMS.

Programmer Response: Print the OBR record to get the appropriate error messages.
2 Explanation: An error was detected during a call to determine whether all volumes
belong to the same storage group.
4 Explanation: An incorrect definition was passed to the SMS.
6 Explanation: Insufficient space was provided for that definition to the SMS subsystem.
8 Explanation: An attempt was made to 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.

Programmer Response: Redefine the 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.

RETURN CODE 204

Explanation: Key specification extends beyond end of maximum logical record.

Reason Code Description

0 Programmer Response: Reduce the key length, change the key position, or increase the
logical record length.

432 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

RETURN CODE 208

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.

Reason Code Description

0 Programmer Response: Increase the buffer size specified through the BUFFERSPACE
parameter of the DEFINE command.
4 Programmer Response: Increase the buffer size specified through the BUFFERSPACE
parameter of the ALTER command.

RETURN CODE 210

Explanation: Subsystem call error.

Reason Code Description

x 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 Description

0 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
v Device type
v Logical record size
4 Explanation: Specified and default values result in only one control interval per
control area for a key-sequenced data set.
Programmer Response: Correct the input. Run the job again.
6 Explanation: Using the specified or default values, the maximum index control
interval size for the device would be exceeded for nonunique objects.
Programmer Response: Increase the data control interval size or decrease the data
control area size.
8 Explanation: Using the specified or default values, the maximum index control
interval size for the device would be exceeded for unique objects.
Programmer Response: Increase the data control interval size or decrease the data
control area size.
10 Explanation: The buffer space is too small for a nonunique object.
Programmer Response: Correct the buffer size. Run the job again.
12 Explanation: The specified and default value result in only one control interval per
control area for a variable relative-record data set.

Chapter 20. IDC messages 433

IDC3009I

RETURN CODE 214

Explanation: Subsystem call error.

Reason Code Description

x Explanation: Return code from Subsystem call.

RETURN CODE 222

Explanation: Alter new name of a GDS, non-VSAM or cluster failed because an ACS service returns a non-zero
return code.

Reason Code Description

ACS reason code = catalog Explanation: Adding decimal 256 to the catalog reason code will give the correct ASC
reason code + decimal 256 reason code. The ACS services return and reason codes are documented in the z/OS
DFSMSdfp Diagnosis

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 z/OS DFSMSdfp Diagnosis &
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 Description

0 Explanation: The maximum number of volume extent (group occurrence) pointers
have been processed.
Programmer Response: Determine why the excessive values are being supplied.
2 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.
Programmer Response: Determine why the excessive values are being supplied.

RETURN CODE 226

Explanation: Test authorization macro failed. The caller is not authorized to perform the requested function.

Reason Code Description

4 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 locate (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.
Programmer Response: Respond to the particular error accordingly. If there is no fix
for the problem, contact the IBM Support Center.

434 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

RETURN CODE 228

Explanation: An error occurred while processing an Enhanced Catalog Sharing request. The following reasons may
be corrected by the installation. Codes not shown indicate an internal system error.

Reason Code Description

x An internal logic error has occurred.
Programmer Response: Contact the IBM Support Center.
2 ECS workarea storage is not available.
3 Coupling Facility connection error. If received with message IEC377I, fields aaaa and
bbbb contain the return and reason codes from IXLCONN.
4 An ECS request was made but the system is not ECS-active.
9 Coupling Facility disconnection error. If received with message IEC377I, fields aaaa and
bbbb contain the return and reason codes from IXLDISC.
13 ECS activation was requested for a catalog with the NOECSHARING attribute.
26 Returned on a non-ECS system when an attempt is made to access a catalog that is
ECS-active on another system.
28 Catalog is temporarily in use by a non-ECS system.
29 ECS-activation of a catalog is requested but the catalog does not have cross-system
share options or is not on a shared volume.
47 A Coupling Facility error has occurred.
Programmer Response: Consult the Coupling Facility messages that appear in the
system log and correct the associated problem. Then reactivate ECS.
48 An attempt was made to add a catalog to the Coupling Facility structure for Enhanced
Catalog Sharing use, but the structure is full.
Programmer Response: Increase the size of the ECS structure definition in the CFRM
policy.
58 An attempt was made to connect to the ECS structure but Catalog has detected that
the system is running as a VM guest. ECS cannot be activated.
65 Connecting to the CF cache is not allowed at this time until the structure is finished
with the rebuild.
Programmer Response: Wait for the rebuild to finish. If the CF cache is not
automatically reconnected after the rebuild, issue
F CATALOG,ECSHR(CONNECT) to connect.

RETURN CODE 232

Explanation: An error was encountered while Catalog Management was performing system management facility
(SMF) processing.

Reason Code Description

x 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 Description

0 Programmer Response: Use the access method services IMPORT CONNECT command
to put an entry for the user catalog into the master catalog.

Chapter 20. IDC messages 435

IDC3009I

RETURN CODE 240

Explanation: Required DD statement not supplied.

Reason Code Description

0 Explanation: An ALTER of expiration date was specified, but no DD statement was
supplied.
4 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.
8 Explanation: An incorrect device type was encountered 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.
14 Explanation: A delete of a unique object was specified, but no DD statement was
supplied.
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.
16 Explanation: A delete of a non-VSAM object with the scratch option was specified, but
no DD statement was supplied.
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.
18 Explanation: A delete of a VSAM object with the erase option was specified, but no
DD statement was supplied.
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.
22 Explanation: There was no DDname match found in the TIOT.
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.
34 Explanation: The system was unable to determine the DD statement name for a CRA.
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.
36 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.
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. Check the DYNAMNBR
parameter in the user's 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.

436 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3009I

RETURN CODE 242

Explanation: A physical I/O error occurred trying to erase the data set being deleted.

Reason Code Description

x Explanation: The reason codes correspond to the VSAM Record Management error
codes.
Programmer Response: Run the job again with the NOERASE option. The data set
cannot be deleted.

RETURN CODE 244

Explanation: Erase action failed. This condition arises when Catalog Management is unable to open the VSAM data
set being deleted.

Reason Code Description

x Explanation: The reason codes correspond to the VSAM OPEN error codes. The
system write message IEC161I with this message.
System Action: The system voids the delete action on that data set.
Programmer Response: Determine why 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 Description

x 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.
Programmer Response: Determine if an SVC dump was created for this failure, and
contact the IBM Support Center for assistance.

RETURN CODE 250

Explanation: VSAM Record Management has found a logical error during erase processing while deleting a VSAM
data set.

Reason Code Description

x Explanation: The reason codes correspond to the VSAM record management logical
error codes.
System Action: The system ignores the delete action on that data set. The system
continues processing.
Programmer Response: The data set cannot be erased. Run the DELETE command
again with the NOERASE option.

RETURN CODE 254

Explanation: An error was encountered during catalog reorientation.

Reason Code Description

2 Explanation: The opening of a catalog failed during catalog reorientation.
4 Explanation: The allocation of a catalog unit failed.

Chapter 20. IDC messages 437

IDC3010I • IDC3013I

IDC3010I UNABLE TO OPEN dsname

Explanation: The dname specified in the command indicated either concatenated catalogs or a different data set.
In the message text:
dsname
The data set name.
System action: The command ends with a condition code of 12.
Application Programmer Response: Ensure that the 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.
System 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 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
Detecting Module: IDCAL01, IDCBI01, IDCCC01, 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.
In the message text:
entname
The entry name.
Application Programmer Response: Verify that the entry name is spelled correctly.
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: IDCLC01, IDCMP01, and IDCSA02 processing associated with the entry name.

IDC3013I DUPLICATE DATA SET NAME

Explanation: One of the following conditions has occurred:
v The data set name supplied by the caller already exists in the specified catalog.
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.

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.
System action: The system ends processing of the command.
Application Programmer Response: Verify that the entry name is spelled correctly. 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.

438 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3014I • IDC3016I

Source: DFSMSdfp
Detecting Module: IDCTP06

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.
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.
System action: The system ends processing associated with the catalog error.
Application Programmer Response: See the programmer response associated with the second-level message.
Source: DFSMSdfp
Detecting Module: IDCTP06

IDC3015I ** VSAM CATALOG RETURN CODE IS return-code - REASON 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.
In the message text:
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.
Application Programmer Response: Contact your programming support personnel.
Source: DFSMSdfp
Detecting Module: IDCLC01

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.
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.
System action: The system ends the command.
Application Programmer Response: Ensure that the catalog specified by the command exists or determine why it
cannot be accessed.
Source: DFSMSdfp
Detecting Module: IDCTP06

Chapter 20. IDC messages 439

IDC3017I • IDC3020I

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 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.
System action: The system ends the command.
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
Detecting Module: IDCTP06

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 caller's RACF authorization was inadequate. 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.
System action: The system ends the command.
Application Programmer Response: Correct the password specified, obtain the required RACF authorization, or
determine why the verification routine did not allow access.
Source: DFSMSdfp
Detecting Module: IDCTP06

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.
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.
System action: The system ends the command.
Application Programmer Response: Ensure that the specified action is allowed for this entry type. The entry type
can be validated by the LISTCAT command.
Source: DFSMSdfp
Detecting Module: IDCTP06

IDC3020I UNABLE TO ALLOCATE SPACE ON USER VOLUME

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.
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.
System action: The system ends the command.
Application Programmer Response: Scratch unneeded data sets from the volume, or run an ALTER command to
add candidate volumes for the data set.
Source: DFSMSdfp
Detecting Module: IDCTP06

440 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3021I • 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 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.
System action: The system ends the command.
Application Programmer Response: Ensure that the volume is mounted.
Source: DFSMSdfp
Detecting Module: IDCTP06

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 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.
System action: The system ends the command.
Application Programmer Response: Correct the DEFINE command so that the entry named in the RELATE
parameter is correct.
Source: DFSMSdfp
Detecting Module: IDCTP06

IDC3023I UNEXPIRED PURGE DATE

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 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.
System action: The system ends the command.
Application Programmer Response: Specify the PURGE option. Run the command again.
Source: DFSMSdfp
Detecting Module: IDCTP06

IDC3024I VOLUME OWNED BY ANOTHER CATALOG

Explanation: Only one catalog may own or allocate space upon a given volume. 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.
System action: The system ends the command.
Application Programmer Response: Do one of the 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
Detecting Module: IDCTP06

Chapter 20. IDC messages 441

IDC3025I • IDC3028I

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 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.
System action: The system ends the command.
Application Programmer Response: Do one of the 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
Detecting Module: IDCTP06

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.
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.
System action: The system ends the command.
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
Detecting Module: IDCTP06

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. 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.
System action: The system ends the command.
Application Programmer Response: Do one of the following:
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.
Source: DFSMSdfp
Detecting Module: IDCTP06

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

442 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3029I • IDC3032I

System action: The system ends the command.

Application Programmer Response: Run the command again. Specify disposition of OLD, not SHR.
Source: DFSMSdfp
Detecting Module: IDCTP06

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 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.
System action: The system ends the command.
Application Programmer Response: Reduce the maximum logical record length or define the data set as spanned.
Source: DFSMSdfp
Detecting Module: IDCTP06

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 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.
System action: The system ends the command.
Application Programmer Response: Do one of the following:
v Reduce the control interval size.
v If the error occurred due to the index component's device type, use a different device with a larger blocksize.
Source: DFSMSdfp
Detecting Module: IDCTP06

IDC3031I KEY EXTENDS BEYOND MAXIMUM RECORD LENGTH

Explanation: The KEY specification extends beyond the end of the maximum logical record. 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.
System action: The system ends the command.
Application Programmer Response: Do one of the following:
v Reduce the key length
v Change the key position
v Increase the record length
Source: DFSMSdfp
Detecting Module: IDCTP06

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 second-level
message for the specific catalog management error code values.

Chapter 20. IDC messages 443

IDC3033I • IDC3037I

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.
System action: The system ends the command.
Application Programmer Response: Increase the BUFFERSPACE parameter of the DEFINE command.
Source: DFSMSdfp
Detecting Module: IDCTP06

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. 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.
System action: The system ends the command.
Application Programmer Response: Ensure that the volumes specified have been defined in the catalog against
which the request is being issued.
Source: DFSMSdfp
Detecting Module: IDCTP06

IDC3034I COMMAND FAILED DUE TO DUPLICATE RACF PROFILE

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.
System action: The system ends the command.
Application Programmer Response: Check the reason code on the accompanying IDC3009I message. Take the
recommended action for this reason code. Run the job again.
Source: DFSMSdfp
Detecting Module: IDCTP06

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.
System action: The system ends the command.
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

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.
System action: The system ends the request.
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.

444 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3062I • IDC3066I

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 message for further explanation of the
problem.
System action: The system ends the command.
Application Programmer Response: Correct the 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 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.
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 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-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.
If ADDV, MODIFYV, or STOREV terminates 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 standard information for the volume but also 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:
– 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 complete the rename operation if the volume is both inactive
and has a volume serial mismatch condition
– Running MODIFYV again to complete or retry the rename operation if the volume is active but has a mismatch
condition
– Running 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCMV01, IDCSR01

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. See the
preceding message for further explanation of the failure.
System action: The system ends the command with an error message.
Application Programmer Response: Correct the 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 cartridges of the incomplete copy volume for the new copy. Or run SCRATCHV to
scratch the incomplete copy volume before rerunning the COPYV command.

Chapter 20. IDC messages 445

IDC3067I

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 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 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 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 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 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.
If the SCRATCHV command is run, the DD statement 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 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.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCMV01, IDCSR01

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.
In the message text:
FROM|TO
Indicate which volume is unusable for those commands processing both a source and target volume having
the same volume serial numbers.
volser The volume serial number.
System action: The system ends the command with 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.

446 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3070I

v Do not specify a new serial number through the NEWSERIAL parameter in the command statement.
System programmer response: Enter the access method services LISTCAT command to list catalog entries and
information about objects defined in the 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 Center. Provide the JCL, the SYSOUT output for the job, and all printed output
and output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCN01, IDCCO01, IDCRV01

IDC3070I ** text NOT UPDATED IN VOLUME LABEL [OF TO VOLUME]

Explanation: text is one of the following:
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.

In the message text:

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.
System action: The system ends the command with 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 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. 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 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 For a rename operation failure for MODIFYV, recover from a MODIFYV rename by:
– Running ADDV to activate the volume if the volume is merely inactive and has no volume serial mismatch
condition.
– Running ADDV both to activate the volume and complete the rename operation if the volume is both inactive
and has a volume serial mismatch condition
– Running MODIFYV again to complete or retry the 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.

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.

Chapter 20. IDC messages 447

IDC3071I • IDC3077I

v For a rename operation failure for STOREV, run STOREV again or run MODIFYV to either backout or 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.
System programmer response: 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 output data sets related to the problem.
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. See the preceding message for further explanation of the failure.
System action: The system ends the command with an error message.
Application Programmer Response: Correct the error as identified by the preceding message. To run the command
again, follow the recovery actions identified for the recovery of space management.
System programmer response: 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 output data sets related to the problem.
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.
The possible attributes are as follows:
v bind/nobind
v readonly/readwrite
v dasderase/nodasderase
v exclusive/shared
v pagefault/nopagefault
System action: The system ends the command with an error message.
Application Programmer Response: Use the 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.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCN01, IDCRV01

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.
In the message text:
csn1
csn2 The cartridge serial numbers that identify the sequence one and sequence two cartridges not in the MSF.
volser The volume serial number.

448 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3081I • IDC3089I

System action: The system ends the command with a message.

Application Programmer Response: Correct the problem as indicated in the preceding message. If the cartridges are
outside the MSF, enter the cartridges again. Run the command again.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCV01

IDC3081I ** RECORD NOT RETRIEVED FROM INVENTORY FOR COPY yyddd, NO. nnn
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.
In the message text:
yyddd The date in year and days.
nnn The copy sequence number.
System action: The system ends the command with a message unless additional copies are to be processed.
Application Programmer Response: Correct the error as indicated in the preceding message. Before running the
command again, ensure that copy date and sequence number are specified correctly.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
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 explanation of the
problem.
System action: The system ends the command with an error message.
Application Programmer Response: Correct the error as identified in the preceding message. To run the command
again, follow the recovery actions for space management.
System programmer response: 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 output data sets related to the problem.
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.

In the message text:

volser The volume serial number.

Chapter 20. IDC messages 449

IDC3090I • IDC3092I

System action: The system ends the command with an error message.
Application Programmer Response: Run the 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.
System programmer response: 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 output data sets related to the problem.
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.
In the message text:
volser The volume serial number.
System action: The system ends the command with a message identifying the severity of the error.
Application Programmer Response: If the volume is recorded as active in the Inventory data set, use the MODIFYV
command to change the READONLY attribute to READWRITE. If the volume to be relabeled is inactive, use the
ADDV command and specify the READWRITE parameter.
System programmer response: 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 output data sets related to the problem.
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.
System action: The system ends the command with a message identifying the severity of the error.
Application Programmer Response: Run the command again with the FILE parameter specifying the name of a JCL
DD statement which allocates a unit with deferred mounting.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCMV01, IDCSR01

450 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3094I • IDC3113I

IDC3094I VOLUME volser CANNOT BE 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.
In the message text:
volser The volume serial number.
System action: The system ends the command with an error message.
Application Programmer Response: Run the 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.
System programmer response: 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 output data sets related to the problem.
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.
In the message text:
csn The cartridge serial number containing the incorrect length.
System action: The system ends the command with a message unless additional cartridges have been specified for
processing.
Application Programmer Response: Specify an 11- or 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 quotation marks because a blank is required as the fourth character.
System programmer response: 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 output data sets related to the problem.
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.
System action: The system ends the command.
Application Programmer Response: Remove the asterisk from the last position of the LEVEL parameter. Run the
command again.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01, IDCCO01, IDCCV01, IDCEC01, IDCEV01, IDCLV01, IDCMC01, IDCRL01

Chapter 20. IDC messages 451

IDC3114I • IDC3145I

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.

In the message text:

ser The volume serial number.
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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCLD01

IDC3143I THE OUTPUT DATA SET CANNOT BE THE SAME AS THE INPUT DATA SET
Explanation: The data set specified on the Outfile/Outdataset parameter is the same one that the system is
exporting.
System action: The system ends processing.
Application Programmer Response: Correct the source or target specifications. Run the job again.
System 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 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
Detecting Module: IDCAV01, IDCMV01

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.
System action: The system ends the command.
Application Programmer Response: Change the specification of portable data set to sequential organization.
Source: DFSMSdfp

452 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3170I • IDC3174I

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
v BUFNI
v CONTROLINTERVALSIZE
v FREESPACE
v IMBED
v NOREPLICATE
v RECORDSIZE
v REPLICATE
v SHAREOPTIONS
v STRNO
System action: The system ends processing of this command.
Application Programmer Response: Determine the catalog format to be defined. Remove the incorrect parameters
from the command or specify ICFCATALOG. Run the job again.
System 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 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

IDC3171I CATALOG PARAMETER NOT ALLOWED ON DEFINE PAGESPACE UNLESS RECATALOG

SPECIFIED
Explanation: An attempt was made to perform a DEFINE PAGESPACE command with a CATALOG subparameter
where RECATALOG was not specified. This is no longer allowed.
System action: The system ends the command with an error message and a condition code of 12.
Operator response: None.
Application Programmer Response: Remove the CATALOG parameter. When defining a new pagespace, the
pagespace must be able to be found by the normal catalog search order. If an alias is needed to orient the new data
set name to a specific user catalog, that alias should be defined before attempting the DEFINE PAGESPACE.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for this problem. If no fix exists, contact the IBM Support Center. Provide the JCL, the SYSOUT output
for the job, and all printed output and output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCDE01

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.
System action: The system ends processing of this command.
Application Programmer Response: Change the 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.
System programmer response: If the error recurs and the program is not in error, look at the messages in the job

Chapter 20. IDC messages 453

IDC3175I • IDC3180I

log for more information. 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

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.
System action: The system ends processing of this command.
Application Programmer Response: Change the 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.
System 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 problem reporting data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center. Provide the 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.
System action: The system ends processing of this command.
Application Programmer Response: Check the NAME and VOLUMES specifications. Change the parameter in
error. Run the job again.
System 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 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

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
Detecting Module: IDCAL01, IDCDE02

IDC3180I CA RECLAIM ALTER IS NOT VALID FOR THE DATA SET TYPE.
Explanation: The system issues this message because an ALTER of the RECLAIM setting was attempted on a
non-KSDS or a KSDS defined with IMBED.
System action: The ALTER command stops.
Operator response: None.
Application Programmer Response: Check to ensure that the data set is a KSDS.

454 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3183I • IDC3187I

Source: DFSMSdfp
Detecting Module: IDCAL01

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.
System action: The system ends processing of the 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
Detecting Module: IDCAL01, IDCDE02

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.
System action: The system ends processing of the command.
Application Programmer Response: Check the 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.
System action: The system ends processing of the 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

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
Detecting Module: IDCDE01

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

Chapter 20. IDC messages 455

IDC3190I • IDC3192I

Where xxxxxxxx is either SYS1 or another high level qualifier specified in the LOADxx member of SYS1.PARMLIB
and x is either a number from 0-9 or an uppercase alphabetic character A-Z.
System action: The system stops processing the command.
System programmer response: Specify a valid entryname.
Source: DFSMSdfp
Detecting Module: IDCDE01

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.
In the message text:
keywd The keyword.
System action: The system ends the command.
Application Programmer Response: Specify the proper data set name. Run the command again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCAL01

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.

System action: The system ends processing of this 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.
System 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 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
Detecting Module: IDCAL01

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.
System action: The system stops processing the command.
System programmer response: Use the IDCAMS ALTER command to change LOCATION from SHELF to LIBRARY
when altering LIBRARYNAME.
Source: DFSMSdfp
Detecting Module: IDCAL02

456 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3193I • IDC3198I

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.
In the message text:
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.
System action: The system ends the command.
Application Programmer Response: Check whether the data set name is the intended candidate for a ROLLIN
operation.
Source: DFSMSdfp
Detecting Module: IDCAL01

IDC3194I SMS CONSTRUCT conname SPECIFIED FOR NON-SMS MANAGED OBJECT

Explanation: An access method services ALTER 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.
In the message text:
conname
The construct name.
System action: The system ends processing of the ALTER command.
Application Programmer Response: Ensure that this request is made against only SMS managed objects.
Source: DFSMSdfp
Detecting Module: IDCAL01

IDC3195I OBJECT IS NOT SMS MANAGED

Explanation: An access method services ALTER command requested that a generation data set (GDS) be rolled in,
but the GDS is not managed by the storage management subsystem (SMS).
System action: The system ends processing of the command.
Application Programmer Response: Remove the ROLLIN specification on the ALTER command.
Source: DFSMSdfp
Detecting Module: IDCAL01

IDC3197I INVALID AUTHORIZATION TO ALTER STORAGECLASS OR MANAGEMENTCLASS

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.
System action: The system ends processing of the ALTER command.
Source: DFSMSdfp
Detecting Module: IDCAL01

IDC3198I SLOT VALUE CANNOT BE SPECIFIED FOR A MANUAL LIBRARY

Explanation: NUMBERSLOTS and NUMBEREMPTYSLOTS are not valid parameters for a manual library.
System action: The system stops processing the command.
System programmer response: Either remove the NUMBERSLOTS and/or NUMBEREMPTYSLOTS parameters or

Chapter 20. IDC messages 457

IDC3199I • IDC3202I

specify LOGICALTYPE(AUTOMATED) on the IDCAMS ALTER command.

Source: DFSMSdfp
Detecting Module: IDCAL02

IDC3199I LIBRARYNAME OF “SHELF” IS NOT ALLOWED WITH A LOCATION OF “LIBRARY”

Explanation: The LIBRARYNAME of SHELF can only be specified when LOCATION is SHELF.
System action: The system stops processing the command.
System programmer response: Choose a LIBRARYNAME other than SHELF or change the LOCATION parameter
to LIBRARY.
Source: DFSMSdfp
Detecting Module: IDCAL02

IDC3200I TOO MANY POSITIONAL PARAMETERS AFTER ‘prm’

Explanation: A parameter list has too many positional parameters specified.
In the message text:
prm The parameter list.
System action: Processing skips to the end of the command. The system resumes interpretation with the next
command.
Application Programmer Response: Remove the excess parameters. Run the command again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3201I CONSTANT ‘xxx’ EXCEEDS LENGTH LIMIT

Explanation: A constant is longer than the maximum allowed by the parameter definition or by the implementation.
In the message text:
xxx The constant that exceeded the maximum length.
System action: Processing skips to the end of the command. The system resumes interpretation with the next
command.
Application Programmer Response: See the definition of the parameter value in question. Specify an allowable
value. Run the command again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3202I 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.
Application Programmer Response: Correct the related error. Run the job again.

458 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3203I • IDC3207I

System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3203I ITEM ‘xxx’ DOES NOT ADHERE TO RESTRICTIONS

Explanation: The specified constant does not meet the naming restrictions on its format. This is usually a problem
in specifying data set names.
In the message text:
xxx The constant.
System action: Processing skips to the end of the command. The system resumes interpretation with the next
command.
Application Programmer Response: Check the data restrictions for the parameter and correct the item. Run the
command again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3205I DELIMITER ‘xxx’ IS NOT PROPERLY PRECEDED BY A CONSTANT OR KEY WORD

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.
In the message text:
xxx The delimiter.
System action: Processing skips to the end of the command. The system resumes interpretation with the next
command.
Application Programmer Response: Correct the usage. Run the command again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

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.
Application Programmer Response: Correct the related error. Run the job again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

Chapter 20. IDC messages 459

IDC3208I • IDC3211I

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.
In the message text:
keywd The keyword.
System action: Processing skips to the end of the command. The system resumes interpretation with the next
command.
Application Programmer Response: Check the requirements of the parameter. Correct the usage. Run the command
again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

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.
In the message text:
xxx The item before which the parenthesis is missing.
System action: Processing skips to the end of the command. The system resumes interpretation with the next
command.
Application Programmer Response: Correct the usage. Run the command again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3210I INVALID PARENTHESES FOR SPECIFYING REPEATED SUBPARAMETER LIST

Explanation: Parentheses for delimiting repetitions of a repeated subparameter list are missing or unmatched.
System action: Processing skips to the end of the command. The system begins interpretation with the next
command.
Application Programmer Response: Correct the usage. Run the command again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

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.
In the message text:
keywd The keyword.

460 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3212I • IDC3214I

System action: Processing skips to the end of the command. The system begins interpretation with the next
command.
Application Programmer Response: Check the usage of the keyword and the parentheses.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

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.
In the message text:
prm The positional parameter.
System action: Processing skips to the end of the command. The system begins interpretation with the next
command.
Application Programmer Response: Correct the usage. Run the job again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3213I KEY WORD ‘keywd’ APPEARS TOO OFTEN

Explanation: A keyword has been coded more than once in the same parameter list or subparameter list.
In the message text:
keywd The keyword.
System action: Processing skips to the end of the command. The system begins interpretation with the next
command.
Application Programmer Response: Remove the redundant keyword. Run the command again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3214I HEX OR BINARY CONSTANT SPECIFIED IMPROPERLY

Explanation: A hexadecimal or binary constant is not in its proper form.
System action: Processing skips to the end of the command. The system begins interpretation with the next
command.
Application Programmer Response: Correct the usage. Run the command again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp

Chapter 20. IDC messages 461

IDC3216I • IDC3219I

Detecting Module: IDCRI01

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.
Application Programmer Response: Correct the related error. Run the job again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3217I PASSWORD IMPROPER AFTER ‘prm’

Explanation: A password is found following a data item that does not allow a password.
In the message text:
prm The data item that does not allow a password.
System action: Processing skips to the end of the command. The system begins interpretation with the next
command.
Application Programmer Response: Remove the improper password. Run the command again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3218I TOO MANY REPEATED SUBPARAMETER LISTS APPEAR

Explanation: More repeated subparameter lists are coded than are allowed.
System action: Processing skips to the end of the command. The system begins interpretation with the next
command.
Application Programmer Response: Check the parameter description to see how many repetitions are allowed.
Correct the usage. Run the job again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3219I VERB NAME ‘verb’ UNKNOWN

Explanation: The specified verb name is not known to the system.
In the message text:
verb The verb name.
System action: Processing skips to the end of the command. The system begins interpretation with the next
command.

462 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3220I • IDC3223I

Application Programmer Response: Correct the improper verb name. Run the command again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

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.
In the message text:
prm The parameter in which the incorrect digit was found.
System action: Processing skips to the end of the command. The system begins interpretation with the next
command.
Application Programmer Response: Correct the usage. Run the command again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3221I CONSTANT ‘xxx’ NOT WITHIN VALUE RANGE

Explanation: A constant is of a value not within the range of values allowed for this parameter.
In the message text:
xxx The constant.
System action: Processing skips to the end of the command. The system begins interpretation with the next
command.
Application Programmer Response: Correct the usage. Run the command again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3223I TOO MANY CONSTANTS IN LIST BEGINNING AT ‘xxx’

Explanation: Too many constants have been coded in a list.
In the message text:
xxx The constant that begins the list.
System action: Processing skips to the end of the command. The system begins interpretation with the next
command.
Application Programmer Response: Check the parameter definition to see how many constants appear in the list.
Correct the usage. Run the job again.
System programmer response: 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 SYSOUT output for the
job.

Chapter 20. IDC messages 463

IDC3225I • IDC3240I

Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3225I REQUIRED (SUB)PARAMETER OF ‘prm’ IS MISSING

Explanation: The system issues this message for one of the following reasons:
v A parameter required by the command is missing.
v For Cache-DASD the specified parameter is required.

In the message text:

prm The required parameter.
System action: Processing skips to the end of the command. The system begins interpretation with the next
command.
Application Programmer Response: Add the missing parameter. Run the job again.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3226I INCONSISTENT PARAMETERS INVOLVING prm

Explanation: A user issued an IDCAMS command that has conflicting or inconsistent parameters.
In the message text:
prm The conflicting or inconsistent parameter.
System action: Processing skips to the end of the command; interpretation begins at the next command.
Application Programmer Response: Correct the error. Issue the command again.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3239I INVALID DELETE MASK KEY - 'filterkey

Explanation: The filter key either is invalid or has a high level qualifier that contains filter characters like % or *.
In the message text:
filterkey The filter key in error.
System action: The system prompts the caller for a valid filter key. See message “IDC3249” on page 467.
Application Programmer Response: Enter a valid filter key.
System programmer response: 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 all printed output and output
data sets related to the problem and the control statements for the job.
Source: DFSMSdfp
Detecting Module: IDCRI04

IDC3240I ‘prm’ VALUE OF ‘nnn’ OUT OF RANGE

Explanation: A number is either larger or smaller than is allowed for the specified parameter.
In the message text:
prm The specified parameter.

464 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3241I • IDC3243I

nnn Represents the first ten digits of the number.

System action: The system prompts the caller for a valid number. See message IDC3249I.
Application Programmer Response: Enter a number within the allowable value range.
System programmer response: 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 all printed output and output
data sets related to the problem and the control statements for the job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC3241I INVALID ‘prm’ NAME-xxx

Explanation: A DSNAME or DDNAME does not adhere to naming restrictions.
In the message text:
prm The specified parameter.
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.
System programmer response: 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 all printed output and output
data sets related to the problem and the control statements for the job.
Source: DFSMSdfp
Detecting Module: IDCRI04

IDC3242I ‘prm’ VALUE HAS INVALID LENGTH-xxx

Explanation: A constant is either too long or has a null length.
In the message text:
prm The specified parameter.
xxx The first sixty-three characters of the constant, if more than sixty-three were entered.
System action: The system prompts the caller for a valid constant. See message IDC3249I.
Application Programmer Response: Enter a valid constant.
System programmer response: 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 all printed output and output
data sets related to the problem and the control statements for the job.
Source: DFSMSdfp
Detecting Module: IDCRI04

IDC3243I ‘prm’ LIST TOO LONG BEGINNING AT xxx

Explanation: A list of nonnumeric constants or subparameter lists has too many elements.
In the message text:
prm The specified parameter.
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.

Chapter 20. IDC messages 465

IDC3244I • IDC3247I

System programmer response: 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 all printed output and output
data sets related to the problem and the control statements for the job.
Source: DFSMSdfp
Detecting Module: IDCRI04

IDC3244I ‘prm1’ (REPLY‘1’) AND prm2 (REPLY ‘2’) ARE IN CONFLICT

Explanation: Two parameters have been coded that conflict with each other.
In the message text:
prm1
prm2 The conflicting parameters.
System action: The system prompts the caller to 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.
System programmer response: 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 all printed output and output
data sets related to the problem and the control statements for the job.
Source: DFSMSdfp
Detecting Module: IDCRI04

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
Detecting Module: IDCRI04

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.
In the message text:
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.
System programmer response: 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 all printed output and output
data sets related to the problem and the control statements for the job.
Source: DFSMSdfp
Detecting Module: IDCRI04

466 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3248I • IDC3251I

IDC3248I ‘prm’ LIST TOO LONG BEGINNING AT nnn

Explanation: A list of numbers contains too many elements.
In the message text:
prm The specified parameter.
nnn The first ten digits of the number.
System action: The system prompts the caller to 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.
System programmer response: 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 all printed output and output
data sets related to the problem and the control statements for the job.
Source: DFSMSdfp
Detecting Module: IDCRI04

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.
Application Programmer Response: Enter a valid constant.
Source: DFSMSdfp
Detecting Module: IDCRI04

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.
System action: The system prompts the caller to 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
Detecting Module: IDCRI04

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.
In the message text:
nnn The subparameter list repetition.
System action: The system continues processing.
Application Programmer Response: Examine the indicated subparameter list repetition.
Source: DFSMSdfp
Detecting Module: IDCRI04

Chapter 20. IDC messages 467

IDC3253I • IDC3302I

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.
In the message text:
keywd The keyword.
System action: The system ends processing of the command.
Operator response: The TSO/E user should reenter the command with the proper keyword.
System programmer response: 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 all printed output and output
data sets related to the problem and the control statements for the job.
Source: DFSMSdfp
Detecting Module: IDCRI04

IDC3300I ERROR OPENING {dsname|ddname}

Explanation: An error was detected attempting to open the data set name. See associated message for explanation.
In the message text:
dsname The data set name.
ddname The ddname. Appears only when the data set name is not available.
System action: The system ends the command.
Application Programmer Response: Check the associated message.
System 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 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
Detecting Module: IDCRI04

IDC3301I ERROR CLOSING dsname

Explanation: An error was detected while attempting to close the data set. See the associated message in the
program listing for an explanation.
In the message text:
dsname The data set name.
System action: The system ends the command.
Application Programmer Response: Check the associated message.
System 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 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
Detecting Module: IDCIO02, IDCIO05

IDC3302I ACTION ERROR ON dsname

Explanation: An error was detected while attempting to access the data set. See the associated message in the
program listing for explanation.
In the message text:
dsname The data set name.

468 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3303I • IDC3306I

System action: The system ends the command.

Application Programmer Response: Check the associated message.
System programmer response: If the error recurs and the program is not in error, look at the messages in the job
log for more information.
Source: DFSMSdfp
Detecting Module: IDCIO02

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.
System 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 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
Detecting Module: IDCIO01, IDCIO03, IDCRS06

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.
System action: The system ends processing of the command.
Application Programmer Response: Check ddnames for incorrect spelling or check for missing DD statements.
Correct the error. Run the job again.
System 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 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
Detecting Module: IDCIO02

IDC3305I ** CANNOT BE OPENED FOR OUTPUT

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.
System action: The system ends processing of the command.
Application Programmer Response: Change the keyword value to specify either a VSAM or SAM data set.
System 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 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
Detecting Module: IDCIO02

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.
System action: The system ends processing of the command.

Chapter 20. IDC messages 469

IDC3307I • IDC3309I

Application Programmer Response: Change the JCL statement to specify a virtual storage access method (VSAM)
data set, or correct the usage of the data set.
System 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 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
Detecting Module: IDCIO02

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.
System action: The system ends processing of the command.
Application Programmer Response: Change the JCL statement to specify a keyed data set or correct the usage of
the data set in the command. Run the job again.
System 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 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
Detecting Module: IDCIO02

IDC3308I ** DUPLICATE RECORD xxx

Explanation: The output data set of a REPRO command already contains a record with the same key or record
number.
In the message text:
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.
System 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 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
Detecting Module: IDCIO02

IDC3309I ** RECORD xxx NOT WRITTEN. LENGTH INVALID.

Explanation: The specified record was not written for one of the following reasons:
v The record length was greater than the LRECL of the output data set (logical processing).
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.

In the message text:

xxx The first five bytes of the record in hexadecimal format.

470 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3310I • IDC3312I

System action: The system continues processing until four such errors occur, in which case no more records are
written to the data set.
Application Programmer Response: Redefine the output data set with the correct LRECL or control interval size.
System 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 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
Detecting Module: IDCIO01

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.
System action: The system ends processing of this command.
Application Programmer Response: Specify the correct key on the command. Run the job again.
System 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 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
Detecting Module: IDCIO01

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.
System action: The system ends processing of the command.
Application Programmer Response: Respecify the JCL statement defining a VSAM or ISAM data set or remove the
positioning parameter. Run the job again.
System 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 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
Detecting Module: IDCIO03

IDC3312I ** SYSTEM UNABLE TO OPEN

Explanation: DCBOFLG was not set after an OPEN request.
System action: The system ends the command.
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.
System 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 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
Detecting Module: IDCIO03

Chapter 20. IDC messages 471

IDC3313I • IDC3315I

IDC3313I synadaf-message
Explanation: An I/O error occurred for a non-virtual storage access method (VSAM) data set. The SYNADAF
message is written.
System action: The system ends the command.
Application Programmer Response: Check the explanation in the SYNADAF message. Correct the error. Submit the
job again.
System 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 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
Detecting Module: IDCIO02

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.
In the message text:
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.
System 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 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
Detecting Module: IDCIO01, IDCIO05

IDC3315I ** RECORD SIZE GREATER THAN 32760 NOT SUPPORTED

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. The maximum VSAM record size that can be handled by EXPORT
is:
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
System action: The system ends processing of this command.
Application Programmer Response: Do one of the 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.

472 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3316I • IDC3319I

System programmer response: Enter the access method services LISTCAT command to list catalog entries and
information about objects defined in the catalog.
If the error recurs and the program is not in error, look at the messages in the job log for more information. search
problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the
JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCIO01

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.
System action: The system ends the command.
Application Programmer Response: Correct the catalog keyword to specify a user catalog. Run the job again.
System 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 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
Detecting Module: IDCIO02

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.
System action: The system ends processing of this 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.
System 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 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
Detecting Module: IDCIO02

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.
System action: The system ends processing.
System 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 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
Detecting Module: IDCIO01, IDCIO02, IDCIO03

IDC3319I ** INCORRECT BLOCK-SIZE SPECIFIED FOR VARIABLE RECORD FORMAT

Explanation: A request to open a data set failed because of an incorrect block size specified for the data set with
variable record format or a ASCII variable record length.
System action: The application ends with error code 40.

Chapter 20. IDC messages 473

IDC3321I • IDC3326I

Application Programmer Response: Take one of the following steps and run the job again.
v Change the block size of the data set. The block size should be at least length of 5.
v Provide a data class, or a system determined block size user interface to hardcode a non-zero block size.
Source: DFSMSdfp
Detecting Module: IDCIO02

IDC3321I ** OPEN/CLOSE/EOV ABEND EXIT TAKEN

Explanation: The OPEN/CLOSE/EOV SVC routines detected an error, and an ABEND message has been written to
the system output data set.
System action: The system ends the command.
Application Programmer Response: Check the write-to-programmer (WTP) message written by the OPEN/CLOSE
routine. Correct the error. Submit the job again.
System 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 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
Detecting Module: IDCIO02

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.
System action: The system ends the command.
Application Programmer Response: Correct the data set name or type. Run the job again.
System 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 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
Detecting Module: IDCIO02

IDC3325I ** INCORRECT BLOCKSIZE SPECIFIED FOR IMPORTRA

Explanation: The data set cannot be opened due to an incorrect block size in the INFILE parameter.
System action: The system ends processing of the IMPORTRA command.
Application Programmer Response: Change the block size in the INFILE parameter to that used in the EXPORTRA
command. Run the job again.
Source: DFSMSdfp
Detecting Module: IDCIO01

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.
System action: The system ends processing of this command.
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.
System 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 problem reporting data bases for a fix for the problem. If no fix exists, contact the

474 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3327I • IDC3331I

IBM Support Center. Provide the JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCIO01

IDC3327I ** DUPLICATE RECORD IN UPGRADE SET - BASE RECORD xxx

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.
In the message text:
xxx 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.
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.
Application Programmer Response: If the 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.
System 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 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
Detecting Module: IDCIO02

IDC3330I ** xxx NOT FOUND

Explanation: The indicated entry does not exist in the directory.
In the message text:
xxx The entry not found.
System action: The system ends the command.
Application Programmer Response: Correct the entry name. Run the job again.
System 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 problem reporting data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center. Provide the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCIO01

IDC3331I ** mem ALREADY EXISTS

Explanation: A member with the new member name already exists in the PDS directory.
In the message text:
mem The member.
System action: The system ends the command.
Application Programmer Response: Specify a different new name. Run the job again.
System 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 problem reporting data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center. Provide the SYSOUT output for the job.
Source: DFSMSdfp

Chapter 20. IDC messages 475

IDC3332I • IDC3335I

Detecting Module: IDCIO03

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.
System 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 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
Detecting Module: IDCIO03

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.
Application Programmer Response: Ensure that the 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.
If it is not empty, delete whatever is defined in it, then delete it, and redefine it.
Enter the REPRO command again.
System programmer response: If the error recurs and the program is not in error, look at the messages in the job
log for more information.
Source: DFSMSdfp
Detecting Module: IDCIO02, IDCIO03, IDCSA02

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.
Application Programmer Response: Use the 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.
System 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 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
Detecting Module: IDCIO01

IDC3335I {ENCIPHER|DECIPHER} ERROR

Explanation: An error was detected while attempting to use a Programmed Cryptographic Facility service to
encipher or decipher data. See the accompanying message for an explanation of the error.
System action: The system ends the command.
Application Programmer Response: Respond to the problem described by the accompanying message.

476 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3336I

System 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 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
Detecting Module: IDCIO01

IDC3336I ** text RETURN CODE IS return-code

Explanation: text is one of the following:
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.

In the message text:

text The text of the message.
return-code The return code, as follows:
For CIPHER/EMK:
Code Explanation
4 PCF was not initialized.
12 The system encountered an error that forced an abnormal end.

For GENKEY/RETKEY:
Code Explanation
4 PCF was not active.
8 The key type was incorrect.
12 The key name was not found in the CKDS.
16 An installation exit caused the request to fail.
24 An error occurred in the installation exit routine.
28 The authorization check failed.
32 The key has incorrect parity.
36 The system encountered an error that forced an abnormal end.
System action: The system ends the command.
System 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 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
Detecting Module: IDCIO01

Chapter 20. IDC messages 477

IDC3337I • IDC3341I

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.
System action: The system ends the command.
Application Programmer Response: Change the DD 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.
System 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 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
Detecting Module: IDCIO01

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.
System action: The system ends the command.
Application Programmer Response: Change the DD 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.
System 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 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
Detecting Module: IDCIO01

IDC3340I SYSTEMKEYNAME text

Explanation: text is one of the following:
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.
System action: The system ends the command.
Application Programmer Response: Supply the needed key name or enciphered data encrypting key in the
command using the SYSTEMKEYNAME or SYSTEMDATAKEY parameter.
System 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 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
Detecting Module: IDCIO01

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.

478 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3350I • IDC3351I

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: The system ends the command.
Application Programmer Response: Supply the correct key. Run the job again.
System 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 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
Detecting Module: IDCIO01

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 z/OS DFSMS Macro Instructions for Data Sets.
In the message text:
synad The synad data.
message The message text.
System action: If possible, the system continues processing.
Application Programmer Response: Check the explanation of the error. Correct the error. Submit the job again.
System 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 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
Detecting Module: IDCIO01

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.
In the message text:
nnnnnnnn
The meaning of RPLFDBWD, the RPL Feedback Word. For detailed information on the RPL Feedback Word,
see z/OS DFSMS Macro Instructions for Data Sets.
rc The return code, as follows:
For a CLOSE Error
Code Explanation
4 The data set indicated by the access-method control block is already closed.
124 A request was cancelled from a use JRNAD Exit.
128 Index search horizontal chain pointer loop encountered.
129 TCLOSE was issued against a media manager's 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 program's address space for a work area for
CLOSE.

Chapter 20. IDC messages 479

IDC3351I

144 An uncorrectable I/O error occurred 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.
182 The SMSVSAM address space is not available.
184 An uncorrectable I/O error occurred 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.
4 The data set indicated by the 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 doesn't 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 volume's 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 z/OS DFSMS Access Method Services
for Catalogs 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 its processing. In addition, an empty cluster cannot be
verified.
118 Attention message: The data set was not properly closed but OPEN's implicit verify was
successfully processed.

480 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3351I

128 DD statement for this access method control block is missing or incorrect.
131 An error was detected by VSAM for a media manager CONNECT.
132 One of the following errors occurred:
v Not enough storage was available for work areas.
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.
133 Delete Volume processing for RESET(MACRF=RST) failed during open. The DDNAME needs to be
freed and re-allocated to the data set.
134 Invalid UCB address for UCB address conversion.
136 Not enough virtual-storage space is available in the program's address space for work areas, control
blocks, or buffers.
138 A 24-bit UCB address is required for Volume Mount but a 31-bit UCB address was passed.
140 The catalog indicates this data set has an incorrect physical record size.
144 An uncorrectable I/O error occurred 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 Security verification failed; the password specified in the access-method control block for a
specified level of access doesn't match the password in the catalog for that level of access; user is
not authorized to access this file.
160 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.
Improved control interval processing (ICIP) was specified for an extended format data set will also
result in this error.
For more information on this return code, see z/OS DFSMSdfp Diagnosis.
164 An uncorrectable I/O error occurred 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.
182 The SMSVASM address space is not available.
184 An uncorrectable I/O error occurred while VSAM was completing an I/O request.
188 The data set indicated by the 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.

Chapter 20. IDC messages 481

IDC3351I

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 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.
208 The ACB MACRF specification is GSR and caller is using a VS1 system.
209 An internal logic error has occurred during the OPEN. Further information may be provided in
message IEC161I in the joblog for the failing job. Use the information in that message to determine
the specific cause of the OPEN failure
212 The ACB MACRF specification is GSR or LSR and the data set requires create processing.
216 The ACB MACRF specification is GSR or LSR and the key length of the data set exceeds the
maximum key length specified in BLDVRP.
220 The ACB MACRF specification is GSR or LSR and the data set's 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 The ACB MACRF specification is GSR 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 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.
8 You attempted to store a record with a duplicate key, or there is a duplicate record for an alternate
index with the unique key option.
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.

482 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3351I

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 user's address space to complete the request.
44 Work area not large enough for the data record (GET with OPTCD=MVE).
56 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.
68 An attempt was made to use a type of processing (output or control-interval) that was not specified
when the data set was opened.
72 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.
76 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.
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 TRANSID was greater than
31 or the shared resource option was not specified.
6. ICI processing was specified, but a request other than a GET or a PUT was issued.
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
it's 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

Chapter 20. IDC messages 483

IDC3351I

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.
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:
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.
6. A record definition field is incorrect.
7. An index CI format is incorrect.
160 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 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:

484 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3380I

1. An attempt is being made to obtain a buffer in exclusive control.

2. A buffer is being invalidated.
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.

Note: See z/OS 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.
Application Programmer Response: Correct the cause of the error.
System 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 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
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.
In the message text:
ddname The DD name.
System action: The system ends the job.
Application Programmer Response: Run the job again after demounting the volume. This causes the device to be
assigned for exclusive control while the job or step is running.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCIO01, IDCIO02, IDCIO03, IDCRS06

Chapter 20. IDC messages 485

IDC3383I • IDC3385I

IDC3383I FILE ddname MUST SPECIFY A VIRTUAL UNIT

Explanation: The DD statement specified through the FILE parameter does not specify a virtual unit but a virtual
unit is required.
In the message text:
ddname The DD name.
System action: The system ends the command.
Application Programmer Response: Correct the UNIT parameter. Run the command again.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA06

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.
In the message text:
ddname The DD name.
System action: The system ends the command.
Application Programmer Response: Correct the UNIT parameter. Run the command again.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSA06

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.
In the message text:
ser The volume serial number.
System action: The system ends processing.
Application Programmer Response: Ensure that the DD statement named in the FILE parameter specifies 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp

486 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3392I • IDC3436I

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.
In the message text:
volser The volume serial number.
System action: The system ends the job.
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
Detecting Module: IDCSA06

| IDC3400I LOGREPLICATE OR NOLOGREPLICATE ALTER IS NOT VALID FOR THE ENTRY TYPE
| Explanation: An ALTER of LOGREPLICATE or NOLOGREPLICATE setting was attempted on a data set that is not
| a CLUSTER object.
| System action: Processing of the ALTER command was stopped.
| Application Programmer Response: Ensure that the data set to be altered is a CLUSTER object.
| System programmer response: If the error recurs and the program is not in error, refer to the messages in the job
| log for more information. Search problem reporting databases for a fix for the problem. If no fix exists, contact the
| IBM Support Center with the JCL and the SYSOUT output for the job.
| Source: DFSMSdfp
| Detecting Module: IDCAL01

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
Detecting Module: IDCSA06

IDC3436I CARTRIDGE TO BE MODIFIED COULD NOT BE LOCATED

Explanation: The request to modify a cartridge failed because the cartridge could not be found.
System action: The system ends the MODIFYC command.
Application Programmer Response: Check the input 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:
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.

Chapter 20. IDC messages 487

IDC3437I • IDC3500I

System programmer response: If the error recurs and the program is not in error, look at the messages in the job
log for more information.
Source: DFSMSdfp
Detecting Module: IDCMC01

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.
System action: The system ends the MODIFYC command.
Application Programmer Response: Check the input 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.
System programmer response: If the error recurs and the program is not in error, look at the messages in the job
log for more information.
Source: DFSMSdfp
Detecting Module: IDCMC01

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.
Application Programmer Response: Examine the 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
Detecting Module: IDCMC01

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. Seez/OS DFSMS Access Method Services for Catalogs for the
valid specification. If the error recurs and the program is not in error, search problem reporting data bases for a fix
for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCDE03

488 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3501I • 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.
System action: The command is ended.
Application Programmer Response: Probable user error. Ensure that the model object type is identical to that being
defined.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCDE02

IDC3503I 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.
System action: The command is ended.
Application Programmer Response: Probable user error. Check the elements in both lists, and make corrections
where needed.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCDE02

IDC3504I THE RANGE LIST CANNOT BE CONSTRUCTED

Explanation: In the construction of the RANGE LIST, the allotted area was not sufficient.
System action: The command is ended.
Application Programmer Response: Possible system error. Rerun the job with the PARM option--PARM TEST
(FULL((DEFN.1.1))); contact your system programmer.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCDE02

IDC3505I INCORRECT SPECIFICATION OF SPACE ALLOCATION

Explanation: The space parameters TRACKS, CYLINDER, or RECORDS do not appear on the appropriate object
parameter list.
System action: The command is ended.
Application Programmer Response: Probable user error. See the DEFINE command and space specifications in z/OS
DFSMS Access Method Services for Catalogs.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCDE01

Chapter 20. IDC messages 489

IDC3506I • IDC3514I

IDC3506I A REQUIRED VOLUME OR DEVT LIST HAS BEEN OMITTED

Explanation: The VOLUMES parameter does not appear in the command when required.
System action: The command is ended.
Application Programmer Response: Probable user 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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCDE01

IDC3507I 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.
System action: The command is ended.
Application Programmer Response: Probable user error. Specify RECORDSIZE and resubmit the job.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCDE01

IDC3513I DYNAMIC ALLOCATION FAILED OR FILE NOT CODED WHEN REQUIRED

Explanation: FILE was specified in a utility command and the ddname was not found.
System action: The command is ended.
Application Programmer Response: See if the ddname on the FILE parameter is the same as the corresponding dd
statement ddname.
Source: DFSMSdfp
Detecting Module: IDCDE01

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.
System action: The command is ended.
Application Programmer Response: Correct the KEYRANGES specifications.
Source: DFSMSdfp
Detecting Module: IDCDE02
IDCMP01

490 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3515I • IDC3519I

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.
Application Programmer Response: Correct either the average or the maximum size value.
Source: DFSMSdfp
Detecting Module: IDCDE02

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.
System action: Processing for the command is ended.
Application Programmer Response: Correct the DEFINE command.
Source: DFSMSdfp
Detecting Module: IDCDE01

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.
System action: The command is ended.
Application Programmer Response: Correct either the average or the maximum size value.
Source: DFSMSdfp
Detecting Module: IDCDE02

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.
System action: The command is ended.
Application Programmer Response: Correct the command by deleting either the REUSE or the UNIQUE and/or
KEYRANGES parameter; then rerun the job.
Source: DFSMSdfp
Detecting Module: IDCDE01

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.
System action: The command is ended.
Application Programmer Response: Redefine the object ensuring that data and index REUSE attributes are in
harmony.
Source: DFSMSdfp
Detecting Module: IDCDE01

Chapter 20. IDC messages 491

IDC3521I • IDC3525I

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.
System action: The command is ended.
Application Programmer Response: Correct the SPANNED parameter or the data set type specification.
Source: DFSMSdfp
Detecting Module: IDCDE01

IDC3522I 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.
System action: The command is ended.
Application Programmer Response: Correct the RECORDSIZE parameter, or specify the SPANNED parameter.
Source: DFSMSdfp
Detecting Module: IDCDE01

IDC3523I GENERATION DATA GROUP NAME EXCEEDS 35 CHARACTERS

Explanation: The name specified for a generation data group cannot exceed 35 characters.
System action: The command is ended.
Application Programmer Response: Shorten the generation data group name and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCDE02

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.
System action: The command is ended.
Application Programmer Response: Examine the 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.
System action: Processing of the command is ended.
Application Programmer Response: Supply the proper level password or have your RACF profile altered to the
required level of access. Rerun the job.
Source: DFSMSdfp
Detecting Module: IDCAL01

492 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3527I • IDC3531I

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.
System action: The command is ended.
Application Programmer Response: Verify that the catalog entry exists and the catalog being used is proper.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCAL01

IDC3528I 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.
System action: The command is ended.
Application Programmer Response: Verify which password is required and provide the password.
Source: DFSMSdfp
Detecting Module: IDCAL01

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.
System action: The command is ended.
Application Programmer Response: Correct the error and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCAL01

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.
System action: Processing continues.
Application Programmer Response: Make sure that the same PDS name is given in both the entry name and new
name parameters.
Source: DFSMSdfp
Detecting Module: IDCAL01

IDC3531I dsname IS A RLS DATA SET WHICH IS INCOMPATIBLE WITH THIS LEVEL OF DFSMS
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.
In the message text:
dsname The data set name.
System action: The system stops processing the command.
Application Programmer Response: Run command on appropriate level of DFSMS.
Source: DFSMSdfp

Chapter 20. IDC messages 493

IDC3536I • IDC3539I

Detecting Module: IDCAL02

IDC3536I INVALID USE OF * WITH THE NEWNAME PARAMETER

Explanation: If either the ENTRYNAME or NEWNAME parameter specifies a generic name (*), then both must.
System action: The command is ended.
Application Programmer Response: Ensure that both the ENTRYNAME and NEWNAME parameters specify a
generic name if either do.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCAL01

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.
System action: The command is ended.
Application Programmer Response: Correctly specify the name of an alternate index, or the data object name of an
alternate index.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCAL01

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.
System action: The command is ended.
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCAL01

IDC3539I KEYS AND/OR RECORDSIZE PARAMETER SPECIFIED FOR NON-EMPTY OBJECT

Explanation: The ALTER command specified the KEYS or RECORDSIZE parameter, but the cluster or alternate
index contains data records.
System action: The object's catalog entry is not altered.
Application Programmer Response: If you want to change key position and/or record size, you must delete,
redefine, and reload the object.
Source: DFSMSdfp
Detecting Module: IDCAL01

494 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3540I • IDC3546I

IDC3540I KEYS/RECORDSIZE VALUES CONFLICT WITH CONTROL INTERVAL SIZE

Explanation: The new key length, key position, or maximum record size is such as to require a larger control
interval.
System action: The object's catalog entry is not altered.
Application Programmer Response: Delete and redefine the object with the proper KEYS and RECORDSIZE
parameters.
Source: DFSMSdfp
Detecting Module: IDCAL01

IDC3541I 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 cluster's maximum record size. If the base cluster is spanned, the ending key position
must be in the base cluster's first control interval.
System action: The object's catalog entry is not altered.
Application Programmer Response: Correct the ALTER command or correct the base cluster's maximum record size
or control interval size.
Source: DFSMSdfp
Detecting Module: IDCAL01

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.
System action: Processing of the command is ended.
Application Programmer Response: Correct either the average or the maximum size value.
Source: DFSMSdfp
Detecting Module: IDCAL01

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.
System action: The object's catalog entry is not altered.
Application Programmer Response: Delete and correctly redefine the object.
Source: DFSMSdfp
Detecting Module: IDCAL01

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.
System action: Processing of the command is ended.
Application Programmer Response: Specify key length and position such that the key is entirely contained in the
base cluster record.
Source: DFSMSdfp
Detecting Module: IDCAL01

Chapter 20. IDC messages 495

IDC3547I • IDC3572I

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 entry's catalog data is not altered. Processing of the command is ended.
Application Programmer Response: Correct the entry name and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCAL01

IDC3558I FORCE OPTION IS INVALID FOR ENTRY TYPE

Explanation: The FORCE option on the DELETE command can only be used to delete data spaces, generation data
groups, and ICF user catalogs, but the FORCE option was specified on a DELETE command for some other type of
entry or was used in a generic DELETE with a user catalog object matching the generic pattern. If a user catalog was
encountered in a generic DELETE, use the RECOVERY, not FORCE parameter to obtain multiple user catalog
DELETEs, instead.
System action: The DELETE command does not complete. The system continues processing.
Application Programmer Response: None.
Source: DFSMSdfp

IDC3568I (xxx) INVALID USE OF *

Explanation: The level name starts or ends with an *, which is not allowed.
In the message text:
xxx The indicated level name.
System action: The command is ended.
Application Programmer Response: Correct the level name and rerun the job.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCLC01

IDC3570I DELIMITERS MUST NOT BE SPECIFIED WHEN RELOADING A CATALOG

Explanation: REPRO command delimiters (FROMKEY, TOKEY, etc.) cannot be specified for reloading a catalog.
System action: The command is ended.
Application Programmer Response: Remove delimiters from the REPRO command.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

IDC3572I TARGET CATALOG IS TOO SMALL TO CONTAIN THE BACKUP CATALOG

Explanation: The size of the target catalog is inadequate.
System action: The command is ended.
Application Programmer Response: Determine size of the backup catalog from LISTCAT output obtained at the

496 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3573I • IDC3577I

time of the unload. Redefine the target catalog with adequate space to contain the low key range of the catalog.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

IDC3573I text
Explanation: text is one of the following:
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

The target catalog name, its volume serial number, and/or the device type do not agree with the backup.
System action: The command is ended.
Application Programmer Response: Check whether you are reloading from the proper backup into the intended
catalog.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

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.
In the message text:
dsname The data set name.
System action: Processing is ended.
Application Programmer Response: Resolve problem described by preceding message(s), restore volumes and rerun
the job.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

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
v VVDS Sphere Record (maybe)

An additional record has been found.

System action: Processing is ended.
Application Programmer Response: Use the PRINT command to display the contents of the target catalog. If it

Chapter 20. IDC messages 497

IDC3578I • IDC3580I

contains more than the expected records redefine the catalog and rerun the job.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

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.
System action: Processing is ended.
Application Programmer Response: Correct the source or target catalog specification and rerun the job.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

IDC3579I 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.
System action: Processing is ended.
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

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

In the message text:

dsname The data set name.
System action: Processing is ended.
Application Programmer Response: Correct the ENTRIES specification and rerun the job.
System programmer response: If the error recurs and the program is not in error, search problem reporting data

498 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3581I • IDC3583I

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
Detecting Module: IDCRP01

IDC3581I REPRO OF CATALOGS CANNOT SPECIFY DELIMITERS

Explanation: The REPRO command does not process beginning and ending delimiters when you are copying
catalogs.
System action: The command is ended.
Application Programmer Response: Remove the incorrect parameters from the command and rerun job.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

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:
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.
System action: The command is ended.
Application Programmer Response: Check the status of the input and output data sets. REPRO is unable to satisfy
your request. Set up data sets correctly and rerun the job.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

IDC3583I ‘prm’ INCOMPATIBLE WITH INFILE DATA SET TYPE

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.
In the message text:
prm The specified parameter.
System action: The command is ended.
Application Programmer Response: Correct the parameters or data set specified and rerun.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCPR01
IDCRP01

Chapter 20. IDC messages 499

IDC3584I • IDC3586I

IDC3584I 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.
System action: The command is ended.
Application Programmer Response: To convert a 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
Detecting Module: IDCRP01

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.
v DECIPHER was specified and source is not a SAM or VSAM ESDS data set.

In the message text:

dsname The data set name.
System action: The command is ended.
Application Programmer Response: Change the DD 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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

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.
System action: The command is ended.
Application Programmer Response: Change the DD 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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

500 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3587I • IDC3592I

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.
System action: Processing is ended.
Application Programmer Response: Correct the source and/or target specifications and rerun the job.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

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.
System action: Processing is ended.
Application Programmer Response: Remove the MERGECAT parameter or correct the source and target catalog
specifications and rerun the job.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

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’.
System action: Processing is ended.
Application Programmer Response: Correct the source or target specifications and rerun the job.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

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.
System action: The command is ended. No export action takes place.
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCXP01

Chapter 20. IDC messages 501

IDC3593I • IDC3599I

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.
System action: The command is ended. No export action takes place.
Application Programmer Response: Something is wrong with the catalog entry for this cluster. If this happens,
consult your system programmer.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRX01, IDCCC01, IDCRC02, IDCXP01

IDC3596I 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.
System action: Processing of the command is ended.
Application Programmer Response: This data set cannot be exported under current catalog conditions. If you wish
to recover the data, use the REPRO command.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCXP01

IDC3598I OBJECT IS A VSAM VOLUME DATA SET WHICH CANNOT BE EXPORTED

Explanation: The object identified by the entry parameter in the EXPORT command is a VSAM volume Data Set
which cannot be exported.
System action: The command is ended. No export action takes place.
Application Programmer Response: Do not attempt to export a VSAM Volume Data Set.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCXP01

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.
In the message text:
catname The catalog name.
System action: The CNVTCAT or REPRO command is ended.
Application Programmer Response: You should restrict access to the catalog during this process and rerun the job.
System 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 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 output data sets
related to the problem.

502 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3602I • IDC3607I

Source: DFSMSdfp
Detecting Module: IDCXP01

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).
For IMPORTRA, message IDC2621I follows this message and gives the name of the failing cluster or alternate index.
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.
Application Programmer Response: Consult the message preceding this message in the program listing.
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 JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDXMP01, IDCRM01

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.
System action: IMPORT ends processing.
Application Programmer Response: Remove these subparameters in OBJECTS parameter and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCMP01

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.
System action: The command is ended.
Application Programmer Response: Ensure that the portable data set to be processed by IMPORT was created by
EXPORT, or that a portable data set to be processed by IMPORTRA was created by EXPORTRA. If the problem
recurs, do the problem determination action.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCMP01, IDCRM01

IDC3607I DELETE UNSUCCESSFUL - NOT A TEMPORARY DATA SET

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.
System action: The command is ended.
Application Programmer Response: Change the name, or delete the duplicate cluster if you mean to replace it.
System programmer response: If the error recurs and the program is not in error, search problem reporting data

Chapter 20. IDC messages 503

IDC3608I • IDC3610I

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
Detecting Module: IDCMP01

IDC3608I CONNECT FOR dsname FAILED

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.
In the message text:
dsname The data set name.
System action: The command is ended.
Application Programmer Response: See the message following this message in the program listing.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCMP01

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).
In the message text:
dsname The data set name.
System action: The command is ended.
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCMP01, IDCRM01

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.
System action: The command is ended.
Application Programmer Response: Specify device types and volumes in the command to connect a user catalog.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp

504 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3612I • IDC3615I

Detecting Module: IDCMP01

IDC3612I 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.
System action: The command is ended.
Application Programmer Response: Use the 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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCMP01

IDC3613I ERROR ENCOUNTERED OPENING PORTABILITY DATA SET

Explanation: The portability data set could not be opened.
System action: The command is ended.
Application Programmer Response: None. The preceding message in the listing explains why the entry data set
was not opened.
System 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 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
Detecting Module: IDCMP01, IDCRM01

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.
In the message text:
obj The specified object.
System action: The command is ended.
Application Programmer Response: Correct the object name.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCMP01

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.
System action: Processing for the command is ended.
Application Programmer Response: Correct the data set name specification in the JCL. Note that if the NEWNAME

Chapter 20. IDC messages 505

IDC3617I • IDC3624I

parameter is specified, the specified data set name must be that name specified in this parameter.
Source: DFSMSdfp
Detecting Module: IDCMP01

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.
(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.
Application Programmer Response: Delete and redefine the predefined data set with proper attributes. Then rerun
the job.
Source: DFSMSdfp
Detecting Module: IDCMP01

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.
Application Programmer Response: Determine the reason for the failure of the ALTER, correct the problem, and
rerun the job.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRM01

IDC3624I 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.
System action: Processing is ended.
Application Programmer Response: Correct the JCL statement. Ensure that it contains a data set name, volume,
unit, DISP=OLD, and the AMP=‘AMORG’ parameter.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRM01

506 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3625I • IDC3633I

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.
System action: The command is ended.
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCMP01

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.
System action: The command ends.
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRM01

IDC3629I 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
Detecting Module: IDCMP01, IDCRM01

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.
In the message text:
xxx The indicated index.
System action: Conversion is ended.
Application Programmer Response: Verify that the 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))))

Chapter 20. IDC messages 507

IDC3641I • IDC3682I

This will produce a SNAP dump at the error point.

System 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 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
Detecting Module: IDCCC01

IDC3641I dsname NOT A BASE CLUSTER

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.
In the message text:
dsname The data set name.
System action: Processing is ended for the entire BLDINDEX command.
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

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.
In the message text:
dsname The data set name.
System action: BLDINDEX processing is ended.
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 programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCBI01

IDC3682I FINAL CHARACTER(S) IN volser NOT NUMERIC

Explanation: A character in the volume serial number is not a numeric value and cannot be incremented to created
new volume serial numbers.
In the message text:
volser The volume serial number.
System action: Function ends normally.
Application Programmer Response: Specify a beginning volume serial number with adequate number of numeric
characters and rerun the command.
Source: DFSMSdfp

508 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3683I • IDC3700I

Detecting Module: IDCCV01

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.
In the message text:
volser The volume serial number.
System action: Command ends normally.
Application Programmer Response: Specify a volume serial number with a lower number or request less volumes
to be created and rerun the command.
Source: DFSMSdfp
Detecting Module: IDCCV01

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.
In the message text:
ser The volume serial number.
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 VTOC HEAD ADDRESS CANNOT EXCEED X'0012'

Explanation: The VTOC head address specified is too large; it cannot exceed X'0012'.
System action: The command ends. The return code is 12.
Application Programmer Response: Specify a VTOC head address not exceeding X‘0012’ and rerun the command.
Source: DFSMSdfp
Detecting Module: IDCMV01

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.
System action: The command ends with an error message.
Application Programmer Response: Correct the problem as indicated in the preceding message and rerun the
command.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCO01

Chapter 20. IDC messages 509

IDC3701I • IDC3706I

IDC3701I ** OLDEST BACKUP COPY RECORD CANNOT BE RETRIEVED FROM 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.
Application Programmer Response: Correct the problem as indicated in the preceding message and rerun the
command.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCO01

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.
In the message text:
yyddd The date in year and days.
System action: The command ends with an error message.
Application Programmer Response: Before rerunning the COPYV command, either:
v Run the SCRATCHV command to scratch the remaining cartridge of this unusable copy and delete the record from
the Inventory data set.
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
Detecting Module: IDCCO01

IDC3706I ** 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.
In the message text:
csn1
csn2 The cartridge serial numbers.
Application Programmer Response: Before 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 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 operations, LISTMSVI can be run the 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.

510 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3708I • IDC3710I

System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCO01

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 for
further explanation of the problem.
System action: The command ends with an error message.
Application Programmer Response: Correct the error condition as indicated in the preceding message and rerun the
command.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCO01

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.
In the message text:
csn1
csn2 The cartridge serial numbers.
System action: The command ends with an error message.
Application Programmer Response: Correct the error as indicated in the preceding message and rerun the
command.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCO01

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.
In the message text:
volser The volume serial number.
System action: The command ends with an error message.
Application Programmer Response: Rerun the command requesting a specific nonbackup copy volume if any exist.
System programmer response: 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 output data sets related to the problem.

Chapter 20. IDC messages 511

IDC3712I • IDC3726I

Source: DFSMSdfp
Detecting Module: IDCRV01

IDC3712I ** LATEST BACKUP COPY RECORD CANNOT BE RETRIEVED FROM 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 the preceding message for further explanation of the error.
System action: The command ends with an error message.
Application Programmer Response: Before rerunning the command correct the error as indicated in the preceding
message or specify another copy to be used in the recovery operation.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCRV01

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.
System action: The command ends with a message.
Application Programmer Response: Rerun the 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.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAV01

IDC3721I VOLUME volser IS ALREADY ACTIVE

Explanation: The designated volume is already active.
In the message text:
volser The volume serial number.
System action: The command ends with a message.
Application Programmer Response: None.
Source: DFSMSdfp
Detecting Module: IDCAV01

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.
System programmer response: 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 all printed output and output
data sets related to the problem.

512 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3730I • IDC3734I

Source: DFSMSdfp
Detecting Module: IDCAV01

IDC3730I VOLUME volser CANNOT BE RELABELED; COPIES EXIST

Explanation: The volume serial number of the volume cannot be changed because copies of the volume exist.
In the message text:
volser The volume serial number.
System action: The command ends with an error message.
Application Programmer Response: Rerun the 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.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSR01

IDC3732I ** VOLUME volser COULD NOT BE 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.
In the message text:
volser The volume serial number.
System action: Processing continues.
Application Programmer Response: Correct the error as identified in the preceding message.
Rerun STOREV or run MODIFYV to either backout or retry the rename operation.
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 restored if the volume is left
partially renamed.
If STOREV ends 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.
Source: DFSMSdfp
Detecting Module: IDCSR01

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

Chapter 20. IDC messages 513

IDC3736I

indicating the mismatch is set in the Inventory data set for the volume. See the preceding message for further
explanation of the problem.
System action: The command ends with an error message.
Application Programmer Response: Correct the 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
MODIFYV or STOREV to either backout or retry the 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 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 restored if the volume is left
partially renamed.
If ADDV, MODIFYV, or STOREV ends 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 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 both inactive and has a volume serial mismatch 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.
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 If a Rename Operation Failed for STOREV
Rerun STOREV or run MODIFYV to either backout or 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCSR01

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.
In the message text:
ddname The DD name.
System action: The command is ended.
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

514 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3738I • IDC3741I

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 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.
Application Programmer Response: Correct the error and rerun the command.
System programmer response: Enter the access method services LISTCAT command to list catalog entries and
information about objects defined in the 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 Center. Provide the JCL, the
SYSOUT output for the job, and all printed output and output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCN01

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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCN01

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.
In the message text:
ddname The specified DD name.
System action: The command ends normally.
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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCN01

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.
System action: The command ends normally.

Chapter 20. IDC messages 515

IDC3744I • IDC3770I

Application Programmer Response: Specify the VSAMCATALOG option on the RECATALOG parameter or omit
the control statement. Rerun the command.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCN01

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.
System action: The command ends normally.
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.
System 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 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 output data sets
related to the problem.
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.
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.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCN01, IDCSR01

IDC3770I VOLUME volser ACTIVE

Explanation: The volume is active and cannot be ejected.
In the message text:
volser The volume serial number.
System action: The command ends with an error message.
Application Programmer Response: Run the STOREV command to both deactivate and eject the volume.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCEV01

516 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3802I • IDC3835I

IDC3802I INVALID SIS PARAMETER

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.
System action: The request is ended and the group is not created or modified. Control is returned to the user with a
condition code of 12.
Application Programmer Response: Specify the correct combination of parameters and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCGR01, IDCMG01

IDC3820I ** 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.
Application Programmer Response: Check the preceding message to determine the exact error. Correct the error
and rerun the command.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCLM01

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.
System action: The command ends normally.
Application Programmer Response: Specify a valid MSF on the command and rerun the command.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCAU01, IDCLM01

IDC3835I AN MSVI ERROR WAS DETECTED WHILE PROCESSING CART (csn)

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.
In the message text:
csn The cartridge serial number.
System action: The command ends.
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.
System programmer response: 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, all printed output and output data sets related to the problem, and the program listing for the job.
Source: DFSMSdfp

Chapter 20. IDC messages 517

IDC3842I • IDC3852I

IDC3842I 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.
System action: The command ends normally.
Application Programmer Response: Rerun the TRACE command specifying either trace area X or trace area Y.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCTR01

IDC3844I 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.
Application Programmer Response: Correct the blocksize specification in the JCL and rerun the job.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCTR01

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.
Application Programmer Response: Correct the LRUCLOCK parameter and rerun the command.
Source: DFSMSdfp
Detecting Module: IDCTU01

IDC3851I 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.
System action: The command ends normally. No tuning parameters have been changed.
Application Programmer Response: Correct the ACTIVEPAGES parameter and rerun the command.
Source: DFSMSdfp
Detecting Module: IDCTU01

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).
System action: The command ends normally. No tuning parameters have been changed.
Application Programmer Response: Correct the LRUGROUPS parameter (which specifies the number of LRU clock
units) and rerun the command.

518 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3860I • IDC3885I

Source: DFSMSdfp
Detecting Module: IDCTU01

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.
System action: The command ends with an error message.
Application Programmer Response: Rerun the command after removing the conflicting parameters that specify
group attributes.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCMV01

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.
In the message text:
ser The volume serial number.
System action: The command ends. The return code is 12.
Application Programmer Response: Rerun the command or take the Problem Determination actions.
Source: DFSMSdfp

IDC3862I VTOC HEAD ADDRESS CANNOT EXCEED X'0012'

Explanation: The VTOC head address specified is too large; it may not exceed X'0012'.
System action: The command ends. The return code is 12.
Application Programmer Response: Specify a VTOC head address not exceeding X‘0012’ and rerun the command.
Source: DFSMSdfp

IDC3883I ** ERROR COUNT EXCEEDED UPPER LIMIT, FUNCTION TERMINATED

Explanation: A LISTCRA command encountered more than 50 I/O errors.
System action: Processing of the LISTCRA command is ended.
Application Programmer Response: See previous messages to determine the cause of the I/O errors. Correct the
problem, and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCLR01

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.
In the message text:
ser The volume serial number.
System action: Processing of the command is ended.

Chapter 20. IDC messages 519

IDC3897I • IDC3900I

Application Programmer Response: Ensure that the 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp

IDC3897I 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.
System programmer response: Determine the reason for the failure of the DELETE command; correct the problem
and rerun the job.
Source: DFSMSdfp

IDC3900I PUTGET ERROR CODE IS return-code

Explanation: The PUTGET macro instruction failed.
In the message text:
return-code The return code, as follows:
Code Explanation
8 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 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.
12 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.
16 The NOWAIT option was specified for TPUT and no line was put out or received.
20 The NOWAIT option was specified for TGET and no line was received.
24 Incorrect parameters were supplied to the PUTGET service routine.
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.
System action: The command is ended.
Application Programmer Response: Correct the error based on the return code information and rerun the job.
System 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 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
Detecting Module: IDCSA02

520 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC3901I • IDC3902I

IDC3901I ERROR QUALIFYING dsname

Explanation: The Time Sharing Option/Extensions (TSO/E) default service routine failed to qualify the data set
indicated.
In the message text:
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.
System 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 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
Detecting Module: IDCSA02

IDC3902I ** DEFAULT SERVICE ROUTINE ERROR CODE return-code, LOCATE ERROR CODE cde
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.
In the message text:
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
4 Return code from PUTLINE or PUTGET was not zero.
8 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.”
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.”
System action: Processing continues.
Application Programmer Response: The response depends on the return codes, rc and cde. Possible responses for
return code rc follow:
Code Response
4 Make sure the user is still logged on to the system.
8 Correct the data set name.
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.

Chapter 20. IDC messages 521

IDC3932I • IDC3936I

16 Respecify the data set name or recatalog the data set.

20 Respecify the data set name or recatalog the data set.
24 None.
28 Check to be sure the parameter list for IKJEHDEF was not improperly modified.
32 None.
36 Respecify the data set name.
System 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 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
Detecting Module: IDCSA02

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.
In the message text:
reason-code The reason code returned by SMS
System action: The system may end processing of the IDCAMS command.
Application Programmer Response: Refer to z/OS DFSMSdfp Diagnosis 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.
In the message text:
return-code The specified return code.
System action: The system ends processing of the command.
Application Programmer Response: None.
Source: DFSMSdfp
Detecting Module: IDCSA11

IDC3936I CVAFFILT ERROR RETURN CODE IS return-code - REASON CODE IS reason-code

Explanation: During DIAGNOSE processing, an error occurred in CVAFFILT.
In the message text:
return-code The return code.
reason-code The reason code.
System action: The system ends processing of the command.
Application Programmer Response: None.
Source: DFSMSdfp
Detecting Module: IDCSA11

522 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC4227I • IDC4230I

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.
Application Programmer Response: Correct the usage and rerun.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC4228I AN ‘END’ COMMAND IS INVALID

Explanation: An END modal command occurs without a matching DO modal command.
System action: The remainder of the command input stream is ignored.
Application Programmer Response: Correct the DO-END usage and rerun.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC4229I ‘IF’ COMMAND HAS INVALID RELATIONAL EXPRESSION

Explanation: An IF modal command has an incorrect relational expression.
System action: The remainder of the command input stream is ignored.
Application Programmer Response: Check the syntax and semantic requirements of the IF command. Correct the
usage and rerun.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC4230I ‘SET’ COMMAND HAS INVALID ASSIGNMENT EXPRESSION

Explanation: A SET modal command has an incorrect assignment expression.
System action: The remainder of the command input stream is ignored.
Application Programmer Response: Check the syntax and semantic restrictions on the SET command. Correct the
usage and rerun.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

Chapter 20. IDC messages 523

IDC4232I • IDC4999I

IDC4232I 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.
Application Programmer Response: Correct the usage and rerun.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

IDC4236I INPUT STREAM END-OF-FILE FOUND BEFORE END-OF-COMMAND

Explanation: Command input stream end-of-file has been found while scanning a command. There may be input
records missing.
System action: The current command is not processed.
Application Programmer Response: Add the missing data and rerun.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp

IDC4237I TOO MANY LEVELS OF ‘IF’ COMMAND NESTING

Explanation: IF modal commands have been nested to a level that cannot be handled.
System action: The remainder of the command input stream is ignored.
Application Programmer Response: Restructure the modal commands to conform to the restriction of ten levels of
nesting.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCRI01

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.
In the message text:
return-code The return code, as follows:
Code Explanation
24 Text processor’s print control table address not set in GDT.
28 No virtual storage available for one of the following:
v Text processor’s translate table.
v Initialization of the I/O adapter.
v Automatic (dynamic) storage of a module.
v Text processor dynamic storage.

524 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC01728I • IDC11003I

See the in-virtual storage trace tables to determine which is the correct condition.
32 There was a request to access an unopened data set.
36 The processor was unable to open SYSPRINT (or whichever DD name is employed to
denote the processor’s standard listing output data set).
40 Incorrect U-macro argument list found.
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).
System 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 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
Detecting Module: IDCSA01
Routing Code: 11
Descriptor Code: -

IDC01728I FOUND nnnnnn EMPTY CONTROL AREAS THAT HAVE NOT BEEN RECLAIMED.
Explanation: The VSAM KSDS contains unused control areas (CAs). Large storage fragmentation might result in
poor performance and ‘out of space’conditions. If the data set was defined with CA reclaim disabled or the function
not available, and the data set is now CA reclaim-enabled, this number of unreclaimed CAs is the total of
irreclaimable empty CAs before the enablement and a few that are left unreclaimed for data integrity after CA
reclaim was enabled. These empty CAs might be reclaimed by subsequent VSAM ERASE requests on the reinserted
records belonging to these CAs. Note that CA reclaim is not supported and is not performed for KSDSs defined with
IMBED.
In the message text:
nnnnnn The number of control areas found to be empty.
System action: There is no error. Processing continues.
Application Programmer Response: No action required. Options to eliminate fragmentation can involve reinserting
the ERASEd records or reorganizing the KSDS. To avoid further fragmentation by applications that delete and insert
records of different keys, activate CA reclaim. CA reclaim will reclaim empty CAs created after CA reclaim has been
activated, but will not reclaim preexistent ones. For data integrity, CA reclaim might temporarily leave some of the
newly empty CAs unreclaimed; they can be reclaimed by later ERASE requests or reused by reinserting records
belonging to the empty CAs. The CA with RBA 0 and the CA with the highest key of the KSDS are never reclaimed.
Source: DFSMSdfp
Detecting Module: IDCXM03, IDCXM05

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.
In the message text:
volser The volume serial number.
nnnnnn The control interval number of the record in the catalog.
System action: Processing continues.
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.

Chapter 20. IDC messages 525

IDC11015I • IDC11023I

System programmer response: Enter the access method services LISTCAT command to list catalog entries and
information about objects defined in the catalog.
Source: DFSMSdfp
Detecting Module: IDCRS06

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.
In the message text:
nnnnnn The control interval number of the record in the catalog.
System action: Processing continues.
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.
System programmer response: Enter the access method services LISTCAT command to list catalog entries and
information about objects defined in the catalog.
Source: DFSMSdfp
Detecting Module: IDCRS06

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.
In the message text:
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.
System action: Processing continues.
Application Programmer Response: See the following message (noted in the explanation) to determine what action
was taken.
Source: DFSMSdfp
Detecting Module: IDCRS02

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.
In the message text:
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.
System action: Processing continues.

526 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC11029I • IDC11036I

Application Programmer Response: See message IDC21026I.

Source: DFSMSdfp
Detecting Module: IDCRS02

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).
In the message text:
volser The volume serial number.
System action: Processing continues.
Application Programmer Response: This message 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
Detecting Module: IDCRS03

IDC11031I 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.
In the message text:
entryname The specified entry name.
System action: Processing continues.
Application Programmer Response: None.
Source: DFSMSdfp
Detecting Module: IDCRS03

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.
In the message text:
volser The volume serial number.
dsname The unique data set name.
System action: Processing continues.
Application Programmer Response: If the data set is no longer valid, then SCRATCH it.
Source: DFSMSdfp
Detecting Module: IDCRS03

IDC11036I entryname, type OUT-OF-SYNC ON volser

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.
In the message text:

Chapter 20. IDC messages 527

IDC11040I • IDC11042I

volser The volume serial number.

entryname The entry name indicated.
type The type specified. The values of type are defined under message IDC21045I.
System action: Processing continues.
Application Programmer Response: List the data set and ensure that it is correct and accessible.
Source: DFSMSdfp
Detecting Module: IDCRS03

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.
In the message text:
dsname The data set name.
System action: Processing continues.
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
Detecting Module: IDCRS03

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.
In the message text:
dsname The data set name.
System action: Processing continues.
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.
Source: DFSMSdfp
Detecting Module: IDCRS03

IDC11042I 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.
In the message text:
dsname The data set name.
System action: Processing continues.
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
Detecting Module: IDCRS03

528 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC11043I • IDC11217I

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.
In the message text:
volser The volume serial number.
System action: Processing continues.
Application Programmer Response: None.
Source: DFSMSdfp
Detecting Module: IDCRS03

IDC11044I dsname NOT SCRATCHED

Explanation: The attempt to scratch the data set for the reason stated in preceding message IDC11040I failed.
In the message text:
dsname The data set name.
System action: Processing continues.
Application Programmer Response: See IDC11040I.
Source: DFSMSdfp
Detecting Module: IDCRS03

IDC11216I INVALID R‘0/R‘1 STAGE ERROR RECORD PAIR: R‘0 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.
In the message text:
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: ICRD04

IDC11217I INVALID R‘0/R‘1 STAGE ERROR RECORD PAIR: R‘1 NOT FOUND (volsercchh) IN REPAIR WORK
FILE dsname
Explanation: The record following the specified R‘0 stage error record is not an R‘1 stage error record. If your
installation had D/T3350 support, ignore R0 (record 0). It is no longer flagged with stage error information.
In the message text:
volsercchh The indicated record.
dsname The indicated data set name.

Chapter 20. IDC messages 529

IDC11218I • IDC11219I

System action: REPAIRV DEBLOCK continues processing at the next valid stage 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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: ICRD04

IDC11218I THE R‘0/R‘1 (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 R‘0/R‘1 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.
In the message text:
volsercchh The indicated record.
dsname The indicated data set name.
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: ICRD04

IDC11219I DEBLOCK FAILED FOR R‘0/R‘1 (volsercchh) IN REPAIR WORK FILE 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.
In the message text:
volsercchh The indicated record.
dsname The indicated data set name.
System action: REPAIRV DEBLOCK continues with the next valid stage error record pair. The return code is 4.
Application Programmer Response: Display the 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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: ICRD04

530 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC11250I • IDC11367I

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.
Application Programmer Response: Correct the error, if necessary, and rerun the command.
Source: DFSMSdfp
Detecting Module: IDCMC01

IDC11361I 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 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
Detecting Module: IDCDA03

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.
Source: DFSMSdfp
Detecting Module: IDCDA03

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.

Chapter 20. IDC messages 531

IDC11373I • IDC11375I

System action: DIAGNOSE considers this an attention condition and processing continues.
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
Detecting Module: IDCDA03

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.
System action: DIAGNOSE considers this an attention condition and continues processing the catalog or VVDS.
Application Programmer Response: Check the 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
Detecting Module: IDCDA03

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.
System action: DIAGNOSE considers this an attention condition and processing continues.
Application Programmer Response: This message 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
Detecting Module: IDCDA03

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, processing continues.
Application Programmer Response: This message 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.

532 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC11441I • IDC11468I

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 the DELETE
VVR command.
Source: DFSMSdfp
Detecting Module: IDCDA03

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 entry’s remaining information normally.
Application Programmer Response: It may be desirable to run the access method services DIAGNOSE command.
See z/OS DFSMS Access Method Services for Catalogs for details on DIAGNOSE.
System 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 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
Detecting Module: IDCLC02

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.
System action: Job Completes condition code 4
User response: Correct the delimiters and resubmit.
Operator response: None
Application Programmer Response: None
System programmer response: None
Source: IDCAMS
Detecting Module: IDCRP01

IDC11468I 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. If the NVR/VVR
does not initially point to the source catalog, no change is made.
System action: The system continues processing.

Chapter 20. IDC messages 533

IDC11560I • IDC11614I

Source: DFSMSdfp
Detecting Module: IDCRP02

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.
v a SETCACHE DISCARDPINNED request to invalidate all cache fast write and DASD fast write data for the device.

In the message text:

volser The volume serial number specified in the LISTDATA/SETCACHE command.
System action: Processing continues.
Application Programmer Response: None.
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.
Application Programmer Response: None.
Source: DFSMSdfp

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.
System action: Processing continues.
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
System action: Processing continues.
Application Programmer Response: None.

534 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC11617I • IDC11659I

Source: DFSMSdfp
Detecting Module: IDCSS01

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 to continue ending the duplex pair.
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 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

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.
In the message text:
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
Detecting Module: IDCXP01

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.
Application Programmer Response: None.
Source: DFSMSdfp
Detecting Module: IDCXP01

IDC11659I INSUFFICIENT WORKAREA PROVIDED TO RETURN FULL VOLUME LIST

Explanation: A problem program issued a VOLLIST request, but didn't provide a large enough workarea to contain
the response to that request.
System action: The system continues processing.
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 z/OS DFSMS Access Method Services for Catalogs refer
to the section about invoking access method services from a problem program; that section describes VOLLIST
requirements.
Source: DFSMSdfp
Detecting Module: IDCMP02

Chapter 20. IDC messages 535

IDC11700I • IDC11705I

IDC11700I 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 processing continues.
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.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary 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.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11703I DUPLICATE KEYS IN INDEX

Explanation: The present and previous keys of the current index level are identical.
System action: The relevant control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11704I INDEX KEYS ARE NOT IN SEQUENCE

Explanation: The present key has a smaller value than the previously tested key.
System action: The relevant control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
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.
In the message text:
pointer-value
The value of the pointer, in hexadecimal.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

536 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC11706I • IDC11711I

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.
Application Programmer Response: See summary messages for final analysis.
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 dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
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.
Application Programmer Response: See summary messages for final analysis.
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.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

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.
System action: Supportive messages display pertinent data, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

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.
System action: Supportive messages display pertinent data, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

Chapter 20. IDC messages 537

IDC11712I • IDC11718I

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.
System action: Supportive messages display pertinent data, and processing continues.
Application Programmer Response: See summary messages for final analysis.
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.
System action: Supportive messages display pertinent data, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11715I 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.
System action: Supportive messages display pertinent data, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11716I 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.
System action: Supportive messages display pertinent data, and processing continues.
Application Programmer Response: See summary messages for final analysis.
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.
System action: Supportive message display pertinent data, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

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.
System action: Supportive messages display pertinent data, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

538 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC11719I • IDC11724I

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.
System action: Processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11720I NUMBER OF INDEX LEVELS IS ZERO

Explanation: The number of index levels in the index component of AMDSB is zero.
System action: Processing continues.
Application Programmer Response: See summary messages for final analysis.
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 dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11722I DUPLICATE INDEX BASE RBA FOUND

Explanation: Two sequence set control intervals have identical base relative byte addresses.
System action: Supportive messages are displayed, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11723I BASE RBA NOT ON CA BOUNDARY

Explanation: A sequence set base relative byte address is not an integral multiple of the control area size.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11724I DATA COMPONENT CA NOT KNOWN TO SEQUENCE SET

Explanation: Some abnormal situations, such as ABENDs or logical errors, can cause a control area (CA) split or CA
reclaim to be interrupted. A logical error results in VSAM backing out the CA split that is in progress and returning a
nonzero return code to the PUT that caused the CA split. When a CA split is aborted in an abnormal condition, an
unreachable new CA (commonly referred to as an orphan CA) can be left behind within the data set. This in itself
does not cause a data integrity problem and the data set is fully functional and accessible.
Orphan CAs might have an effect on other programs or functions:
v The VSAM data set may fill up prematurely when there are a large number of orphan CAs and this may require
the data set to be reorganized to reclaim the unusable DASD space.
v DFSMSdss will not complete a dump of the data set if the VALIDATE parameter is used and results in message
ADR970E. Manual intervention is required to create a backup of the data set.
v IDCAMS EXAMINE INDEXTEST DATATEST generates the IDC11724I message and sets the return code to 4 if
only the orphan CA condition is present and no data integrity problems are detected. However, if the EXAMINE

Chapter 20. IDC messages 539

IDC11724I

also detects data integrity problems, it will also display other messages and will return with return code = 8 (and
not 4). Because EXAMINE INDEXTEST DATATEST checks both the index and data components, its return code is
more accurate in reflecting the true severity of the situations it detects than that of EXAMINE DATATEST
NOINDEXTEST; it is also more thorough in detecting errors. Below are some output examples:
Example 1
EXAMINE NAME(xxxxxxxx) INDEXTEST DATATEST
IDC01700I INDEXTEST BEGINS
IDC11724I DATA COMPONENT CA NOT KNOWN TO
SEQUENCE SET
IDC21700I MINOR ERRORS FOUND BY INDEXTEST
IDC01701I DATATEST BEGINS
IDC11768I [CI SPLIT | CA RECLAIM] IN PROGRESS
IDC01713I DATA CONTROL INTERVAL DISPLAY AT RBA
yyy FOLLOWS
...
IDC01714I ERROR LOCATED AT OFFSET zzzzzzzz
IDC11724I DATA COMPONENT CA NOT KNOWN TO SEQUENCE SET
IDC21703I MINOR ERRORS FOUND BY DATATEST
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 4

Example 2
EXAMINE NAME(xxxxxxxx) INDEXTEST DATATEST
IDC01700I INDEXTEST BEGINS
IDC11718I DATA COMPONENT HIGH-USED RBA IS NOT EQUAL TO CA SIZE
IDC01702I HIGH-USED RBA/CI IS xx
IDC01705I CONTROL AREA SIZE IS xxxx
IDC11711I INDEX CONTROL INTERVAL COUNT ERROR
IDC01708I 1 CONTROL INTERVALS ENCOUNTERED
IDC01702I HIGH-USED RBA/CI IS xxx
IDC01704I CONTROL INTERVAL SIZE IS xxxx
IDC11708I HIGH-USED INDEX RBA DOES NOT EQUAL HIGHEST RBA FOUND
IDC01702I HIGH-USED RBA/CI IS xxx
IDC01706I RBA/CI IS xxx
IDC21701I MAJOR ERRORS FOUND BY INDEXTEST
IDC01701I DATATEST BEGINS
IDC11768I [CI SPLIT | CA RECLAIM] IN PROGRESS
IDC01713I DATA CONTROL INTERVAL DISPLAY AT RBA xxxx FOLLOWS
...
IDC01714I ERROR LOCATED AT OFFSET xxxxxxxx
IDC11724I DATA COMPONENT CA NOT KNOWN TO SEQUENCE SET
IDC21703I MAJOR ERRORS FOUND BY DATATEST
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8

Note: In cases where the High-used RBA does not equal the highest found RBA (as indicated by IDC11708I in the
example above), an IDCAMS VERIFY should be run first and the EXAMINE rerun.
Similarly, IDCAMS EXAMINE INDEXTEST NODATATEST issues the IDC11724I message and sets return code to 4,
or RC=8 if it detects data integrity problems.
v IDCAMS EXAMINE DATATEST NOINDEXTEST always gives a return code of 8 for message IDC11724I because it
does not review the entire index structure and cannot determine if the missing CAs present a data integrity issue
or not. EXAMINE DATATEST NOINDEXTEST is faster than DATATEST INDEXTEST, so is better suited to more
quickly determine whether or not there are orphan CAs or some other errors that can be found without searching
the whole index structure. If errors are found, issue EXAMINE DATATEST INDEXTEST to pinpoint the severity of
the situation and to find the complete set of errors. Below is an output example:
EXAMINE NAME(xxxxxxxx) DATATEST NOINDEXTEST
IDC01701I DATATEST BEGINS
IDC11768I [CI SPLIT | CA RECLAIM] IN PROGRESS
IDC01713I DATA CONTROL INTERVAL DISPLAY AT RBA
yyy FOLLOWS
...
IDC01714I ERROR LOCATED AT OFFSET zzzzzzzz
IDC11724I DATA COMPONENT CA NOT KNOWN TO SEQUENCE SET
IDC21703I MAJOR ERRORS FOUND BY DATATEST
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8

540 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC11725I • IDC11731I

System action: Supportive messages display pertinent data, and processing continues.
Application Programmer Response: The dataset has ownership of physical space on the volume that it will never
use. To clean up the orphaned CAs, a reorganization of the dataset will need to be done. This corrective action
applies to only the RC=4 situations. When RC=8, the data set might be broken and might need to be recovered with
a process beyond reorganization.
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.
Application Programmer Response: See summary messages for final analysis.
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.
System action: Supportive messages are displayed, and processing continues.
Application Programmer Response: See summary messages for final analysis.
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.
System action: Supportive messages are displayed, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11728I DATA FOUND IN EMPTY CI

Explanation: The free area of an empty control interval contains data.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11730I 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.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

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.
Application Programmer Response: See summary messages for final analysis.

Chapter 20. IDC messages 541

IDC11732I • IDC11737I

Source: DFSMSdfp

IDC11732I DATA FOUND IN FREE AREA OF DATA CI

Explanation: The free space of a data component control interval contains residual data.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11733I 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.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11734I 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
processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11735I 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.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

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.
System action: The relevant control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11737I A RIGHT RDF IS CODED AS CONTAINING THE NUMBER OF RECORDS IN CI

Explanation: A right record definition field is coded with the attributes of a left record definition field.
System action: The relevant control interval is dumped, processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

542 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC11738I • IDC11744I

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.
System action: The relevant control interval is dumped, processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

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.
System action: The relevant control interval is dumped, processing continues.
Application Programmer Response: See summary messages for final analysis.
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 control
interval definition field or overlaps the leftmost record definition field.
System action: The relevant control interval is dumped, processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11741I DUPLICATE CONSECUTIVE KEYS FOUND

Explanation: Two consecutive keys are identical.
System action: The current control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11742I MORE SEQUENCE SET CONTROL INTERVALS FOUND THAN EXPECTED

Explanation: The index contains too many sequence set control intervals.
System action: The relevant control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11743I SOFTWARE EOF FOUND IN INDEX SEQUENCE SET CI

Explanation: An index sequence set control interval contains a software end-of-file.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11744I SOFTWARE EOF NOT FOUND IN THE HIGH-USED RBA CI

Explanation: The last data control interval does not contain a software end-of-file.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.

Chapter 20. IDC messages 543

IDC11745I • IDC11758I

Source: DFSMSdfp

IDC11745I ERROR IN CIDF

Explanation: An error has been found in the control information definition field of the current control interval.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11751I 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.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
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.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11756I SOFTWARE EOF FOUND IN FREE CI

Explanation: A free data control interval contains a software end-of-file.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11757I SOFTWARE EOF FOUND IN DATA CI

Explanation: A data control interval contains a software end-of-file.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11758I SOFTWARE EOF FOUND IN INDEX CI

Explanation: An index control interval contains a software end-of-file.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

544 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC11760I • IDC11766I

IDC11760I 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, and processing continues.
Application Programmer Response: See summary messages for final analysis.
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.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11762I LENGTH OF VERTICAL POINTER INVALID

Explanation: The index vertical pointer length is not 1, 2, or 3 bytes.
System action: Processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11763I 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.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11764I NUMBER OF CONTROL INTERVALS IN CA NOT GREATER THAN ZERO

Explanation: The number of control intervals per control area found in AMDSB is zero.
System action: Processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11765I 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.
System action: Processing continues.
Application Programmer Response: See summary messages for final analysis.
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, and processing continues.
Application Programmer Response: See summary messages for final analysis.

Chapter 20. IDC messages 545

IDC11767I • IDC11770I

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.
System action: Processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11768I [CI SPLIT | CA RECLAIM] IN PROGRESS

Explanation: Some situations, such as an ABEND, CANCEL, or a system failure, can interrupt a control interval (CI)
split or a control area (CA) reclaim for an ERASE request.
An interrupted split results in VSAM backing out the CI split that is in progress and returning a nonzero return code
to the PUT request that caused the CI split. When a CI split is aborted under this condition, the copy of the new CI
or CA (commonly referred to as an orphan CI or CA) is left behind within the data set. This does not indicate there
is a data integrity problem.
A CA reclaim interrupted at this stage will not leave behind an orphan CI or CA and there are no data integrity
problems.
This message is generated when the interruption occurred at a different point of the CA reclaim processing than
message IDC11778I CA RECLAIM IN PROGRESS. The two messages are mutually exclusive.
System action: The condition is temporary. The data control interval is dumped in a subsequent IDC01720I message.
Processing continues.
Application Programmer Response: The condition is temporary.
For CA RECLAIM IN PROGRESS, this IDC11768I message indicates an interruption very early in the VSAM CA
reclaim process where no index CIs have been changed. For that reason, IDCAMS VERIFY RECOVER might not be
able to complete or back out the CA reclaim process. Subsequent VSAM or VSAM RLS requests that encounter the
data CI involved in the interrupted CA reclaim will back out the CA reclaim process, even if SETSMS
CA_RECLAIM(NONE) is issued.
Source: DFSMSdfp

IDC11769I MORE INDEX POINTERS THAN EXPECTED

Explanation: More vertical, horizontal, or base relative byte address pointers have been found while processing an
index level than should exist on that level.
System action: Processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11770I 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.
System action: The control interval is dumped, and processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

546 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC11771I • IDC11774I

IDC11771I INVALID RBA GENERATED

Explanation: An incorrect relative byte address has been generated from index component data.
System action: Processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11772I HORIZONTAL POINTER CHAIN LOOP

Explanation: A long loop has been discovered in the horizontal pointer chain in an index level.
System action: Processing continues.
Application Programmer Response: See summary messages for final analysis.
Source: DFSMSdfp

IDC11773I nnnn KEYS PROCESSED ON INDEX LEVEL y, AVERAGE KEY LENGTH: keylen
Explanation: This message lists the number of keys found on each index level and displays the average compressed
length of all of the keys on that index level.
In the message text:
nnnn
The number of keys found on this index level.
y The index level. Level 1 is the sequence set.
keylen
The average key length of the keys stored in the index record after compression has been performed.
System action: The program continues processing.
Source: DFSMSdfp

IDC11774I CURRENT INDEX CISIZE IS cisize, RECOMMENDED MINIMUM INDEX CISIZE IS newcisize
Explanation: This message indicates the current index CISIZE of the data set, and based on the average compression
of the keys in the sequence set it recommends a minimum index CISIZE value. This is a minimum size and may be
less than the current index CISIZE. Specifying a CISIZE which is smaller than the recommended minimum CI size is
expected to generate unreachable CIs. The minimum value is based on the average key compression and index
structure elements of the sequence set and is a value that should ensure that most of the keys for a data CA can be
described in an index CI record. The recommended minimum value also represents the current state of the sequence
set, the specified CISIZE should also consider future activities such as adding keys of different compression lengths
and key deletion which might result in unreachable data CIs in the future. Adding record keys of different
compression lengths in the future can require a index CISIZE which is larger than the recommended minimum. If the
current index size is smaller than the recommended minimum, a larger index CISIZE may be needed to reduce
unused data CIs that are unreachable because the index record becomes full before all data CIs in the CA are
represented. Unreachable data CIs describe empty and unused space within the data component which can
contribute to unexpected data growth and out of space conditions.This information is provided for CI sizes above
and below the recommended value and does not indicate an error.

Note: Because some keys in the sequence set records may compress better or worse than the average shown, the
recommended minimum index CISIZE may not necessarily eliminate all unreachable data CIs. The actual and
recommended sizes might also vary as keys are added or deleted. Since calculations are based on an averaged key
length, this message only indicates the possibility of an unreachable data CI. An unreachable data CI describes space
allocated in the data component to which there is no room in the index to reference the data location. The
unreachable space in the data component does not affect data or processing.
In the message text:
cisize
The current index CISIZE of the data set.

Chapter 20. IDC messages 547

IDC11775I • IDC11808I

newcisize
The recommended minimum index CISIZE of the data set.
System action: The program continues processing.
Source: DFSMSdfp

IDC11775I nnnn DATA COMPONENT CIS ARE ESTIMATED TO BE UNREACHABLE

Explanation: This message indicates that based on the current average key compression of the sequence set, the
sequence set records could not hold keys for all of the data CIs in a data CA.
The average key length is used to determine how many keys can be in a sequence set record, but some sequence set
records may have better or worse key compression than the average. Thus the number shown should be considered
an approximation and not an exact number.
In the message text:
nnnn
The estimated number of unreachable CIs because there are insufficient room in the sequence set records to
describe all of the data CIs for the data CAs. This number represents data CIs that cannot be assigned for use for
data records and represents unusable space in the data component.
System action: The program continues processing.
Source: DFSMSdfp

IDC11778I CA RECLAIM IN PROGRESS.

Explanation: Some situations, such as an ABEND, a CANCEL, or a system failure, can interrupt a control area (CA)
reclaim for an ERASE request. This message issued by EXAMINE INDEXTEST and DATATEST does not indicate a
data integrity problem.
This is a temporary condition. Other messages generated along with this one might just indicate interrupted CA
reclaim states with no data integrity problems either.
This message is generated when the interruption occurred at a different point of the CA reclaim processing than
message IDC11768I [CI SPLIT | CA RECLAIM] IN PROGRESS. The two messages are mutually exclusive.
System action: The condition is temporary. Index CI 2 is dumped. Processing continues.
Application Programmer Response: This message indicates that an index CI is in the middle of a CA reclaim. The
condition is temporary. If other messages generate condition code 8 results, issue IDCAMS VERIFY RECOVER to
complete or back out the CA reclaim process. Then issue EXAMINE again to detect any remaining errors. If IDCAMS
VERIFY RECOVER is not issued, subsequent VSAM or VSAM RLS requests might complete the CA reclaim process
even if SETSMS CA_RECLAIM(NONE) is issued.
Source: DFSMSdfp
Detecting Module: IDCXM02, IDCXM03, IDCXM04, IDCXM05

IDC11808I ERRORS WERE DETECTED FOR dsname ON VOLUME volser ERROR BYTE WAS X‘nn’
Explanation: During data collection for the specified data set, errors were detected.
In the message text:
dsname The data set name.
volser The volume serial number.
nn The hexadecimal error byte.
System action: Processing continues.
Application Programmer Response: See the field ‘DCDERROR’ in that data set's “D” record for the specific failure.
System 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 problem reporting data bases for a fix for the problem. If no fix exists, contact the

548 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC11812I • IDC11818I

IBM Support Center. Provide the JCL, the SYSOUT output for the job, and all printed output and output data sets
related to the problem.
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.
System action: Processing continues.
Application Programmer Response: If all error messages are required, increase the error limit or do not specify the
error limit parameter.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp

IDC11813I ERRORS WERE DETECTED FOR volser ERROR BYTE WAS X‘nn’
Explanation: During volume information processing, errors were detected for the specified volser.
In the message text:
volser The volume serial number.
nn The error byte.
System action: Processing continues.
Application Programmer Response: See the field ‘DCVERROR’ in that volser's V record for the specific error.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp

IDC11816I DYNAMIC ALLOCATION FAILED FOR VOLUME volser

Explanation: Volume volser could not be dynamically allocated by the system. Severity is 4.
System action: Processing continues with the next 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 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 printed output and output data sets
related to the problem.

IDC11818I type INFORMATION NOT FOUND

Explanation: This message indicates that a requested definition was not found or unavailable.
In the message text:
type
The type of definition not found:
v STORAGE CLASS CONSTRUCT
v MANAGEMENT CLASS CONSTRUCT
v STORAGE GROUP CONSTRUCT

Chapter 20. IDC messages 549

IDC11819I • IDC11861I

v SMS VOLUME
v BASE CONFIGURATION
v CACHE SET NAME
v AGGREGATE GROUP CONSTRUCT
v OPTICAL DRIVE
v OPTICAL LIBRARY
v ACS ROUTINE

Note: CACHE SET NAME in this context refers to a VSAM RLS cache set. See z/OS DFSMSdfp Storage
Administration.
System action: Processing continues.
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.
System action: The system continues processing with 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).
System action: Processing continues.
Application Programmer Response: This message 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

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.
In the message text:
number The record number.
offset The offset indicated.
System action: Processing continues.
Application Programmer Response: This message 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

550 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC11902I • IDC21024I

IDC11902I parameter-name SET TO DEFAULT OF default-value

Explanation: The system accepted a default value for the specified parameter.
System action: The system continues processing the command.
Source: DFSMSdfp
Detecting Module: IDCAL02

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.
In the message text:
volser The volume serial number.
entryname The specified entry name.
type The type of record. The values are defined under message IDC21045I.
System action: Processing continues.
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
Detecting Module: IDCRS01
IDCRS03

IDC21020I UNABLE TO ALLOCATE volser

Explanation: An attempt to allocate a volume for RESETCAT failed. See message IDC3905I.
In the message text:
volser The volume serial number.
System action: Processing continues.
Application Programmer Response: Make the volume indicated available to RESETCAT via CRAFILES and reissue
the command.
Source: DFSMSdfp
Detecting Module: IDCRS06

IDC21024I entryname, type CONTAINS AN INVALID ALIAS CHAIN

Explanation: The alias chain for a user catalog or non-VSAM entry is incorrect.
In the message text:
entryname
The specified entry name.
type The type of record. The values are defined under message IDC21045I.
System action: Processing continues.
Application Programmer Response: The alias chain will be corrected. A LISTCAT should be run to determine which
aliases may be lost.
System programmer response: Enter the access method services LISTCAT command to list catalog entries and
information about objects defined in the catalog.
Source: DFSMSdfp
Detecting Module: IDCRS02

Chapter 20. IDC messages 551

IDC21025I • IDC21030I

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.
In the message text:
entryname The specified entry name.
type The type of record. The values of type are defined under message IDC21045I.
System action: Processing continues.
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.
Source: DFSMSdfp
Detecting Module: IDCRS03

IDC21026I entryname, type DELETED

Explanation: A previous message indicates an error which resulted in this entry being deleted from the catalog.
In the message text:
entryname The specified entry name.
type The type of record. The values of type are defined under message IDC21045I.
System action: Processing continues.
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
Detecting Module: IDCRS02

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.
In the message text:
volser The volume serial number.
System action: Processing continues.
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
Detecting Module: IDCRS03

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.
In the message text:
entryname The specified entry name.
type The type of record. The values of type are defined under message IDC21045I.

552 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC21032I • IDC21045I

volser The volume serial number.

System action: Processing continues.
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.
System programmer response: Enter the access method services LISTCAT command to list catalog entries and
information about objects defined in the catalog.
Source: DFSMSdfp
Detecting Module: IDCRS03

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.
In the message text:
entryname The specified entry name.
type The type of record. The values of type are defined under message IDC21045I.
System action: Processing continues.
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.
In the message text:
volser The volume serial number.
System action: Processing continues.
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.
Source: DFSMSdfp
Detecting Module: IDCRS03

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

Chapter 20. IDC messages 553

IDC21046I • IDC21047I

X -- alias

In the message text:

entryname The specified entry name.
type The type of record. The values of type are defined under message IDC21045I.
avol The volume.
System action: Processing continues.
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
Detecting Module: IDCRS07

IDC21046I 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.
In the message text:
entryname The specified entry name.
type The type of record. The values of type are defined under message IDC21045I.
cravol The catalog recovery area (CRA) volume.
System action: Processing continues.
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
Detecting Module: IDCRS07

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.
In the message text:
entryname The specified entry name.
type The type of record. The values of type are defined under message IDC21045I.
cravol The catalog recovery area (CRA) volume.
System action: Processing continues.
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

554 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC21100I • IDC21104I

Detecting Module: IDCRS07

IDC21100I UNABLE TO DUMP MSC MAIN STORAGE

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.
System action: This dump request is bypassed. Remaining dump requests are processed.
Application Programmer Response: Take the action associated with the MSSC reason code in the preceding
message.
Source: DFSMSdfp
Detecting Module: IDCDU01

IDC21101I LOWSECTOR X'll' IS GREATER THAN HIGHSECTOR X'hh'.

Explanation: A sector range was specified incorrectly. The low sector value was greater than the high sector value.
In the message text:
ll The low sector value.
hh The high sector value.
System action: This dump request is bypassed. Remaining dump requests are processed.
Application Programmer Response: Correct the sector range, specifying a low sector value that is lower than the
high sector value. Resubmit the command.
Source: DFSMSdfp
Detecting Module: IDCDU01

IDC21103I INVALID SSID nnnn

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.
In the message text:
nnnn The SSID value.
System action: Requests for this SSID are bypassed. Remaining dump requests are processed.
Application Programmer Response: Correct the SSID and rerun the command.
Source: DFSMSdfp
Detecting Module: IDCDU01

IDC21104I 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.
In the message text:
nnnn The SSID value.
System action: This dump request is bypassed. Remaining dump requests are processed.
Application Programmer Response: Take the action associated with the MSSC reason code in the preceding
message.
Source: DFSMSdfp
Detecting Module: IDCDU01

Chapter 20. IDC messages 555

IDC21105I • IDC21127I

IDC21105I 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.
In the message text:
nnnn The SSID value.
System action: This dump request is bypassed. Remaining dump requests are processed.
Application Programmer Response: Take the action associated with the MSSC reason code in the preceding
message.
Source: DFSMSdfp
Detecting Module: IDCDU01

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.
Application Programmer Response: Correct the values for future dumps.
Source: DFSMSdfp
Detecting Module: IDCDU01

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.
Source: DFSMSdfp
Detecting Module: IDCCH01

IDC21127I 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.
Source: DFSMSdfp
Detecting Module: IDCCH01

556 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC21143I • IDC21276I

IDC21143I ** INCOMPLETE READ REPORT PRODUCED, ERROR AT X LOCATION xxx

Explanation: The AUDITMSS command is unable to read the labels of all the requested cartridges.
In the message text:
xxx The X coordinate of the cell where the error occurred.
System action: The command ends.
Application Programmer Response: Rerun the 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 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.
In the message text:
lowx The low range.
highx The high range.
System action: The incorrect XRANGE is ignored, and processing continues.
Application Programmer Response: Correctly specify the incorrect range and rerun the command.
Source: DFSMSdfp
Detecting Module: IDCCAU03

IDC21147I ** INCOMPLETE AUDIT REPORT PRODUCED, ERROR WITHIN X RANGE

Explanation: The AUDITMSS command is unable to 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.
System action: The command ends.
Application Programmer Response: Rerun the 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
Detecting Module: IDCAU03

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.
In the message text:
volser The volume serial number.
System action: The system ends with a message that indicates the severity of the error.
Operator response: None.
Application Programmer Response: Use the 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.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp

Chapter 20. IDC messages 557

IDC21363I • IDC21364I

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:

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.
Source: DFSMSdfp
Detecting Module: IDCDA03

IDC21364I ERROR DETECTED BY DIAGNOSE: {VVDS|ICFCAT} ENTRY: entry RECORD: rec OFFSET: offset
REASON: reason-code
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.
In the message text:
entry The entry name. The entry name is followed by a character which indicates the entry type. See z/OS
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 The reason code, as follows:
Code Explanation
1 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.
2 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.
3 RECORD TYPE NOT RECOGNIZED
Each record in a BCS or VVDS has an record type. The record named has an invalid type
for integrated catalog facility catalogs.
4 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.

558 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC21364I

5 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.
6 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.
7 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.
8 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.
9 RECORD LENGTH INCORRECT
The record length at the front of the record is not the same as the length stored by VSAM
record management.
10 INCOMPLETE EXTEND DETECTED
The EXTEND function did not execute to completion. The named entry was interrupted in
the middle of an EXTEND/EOV operation.
11 INCOMPLETE DELETE DETECTED
The DELETE function did not execute to completion. This may indicate existence of partial
record structures in the BCS.
12 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 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 VVDS AND VTOC STARTING CCHH UNEQUAL
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.

Chapter 20. IDC messages 559

IDC21364I

18 VVDS ENTRY NOT FOUND

There should be a VVDS entry for this BCS entry, but one could not be found.
19 CATLG ENTRY NOT FOUND
The BCS should have an entry for the VVDS record, but one could not be found.
20 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.
21 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 point back to the
non-VSAM data set record.
22 TRUENAME NOT FOUND
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.
23 TRUENAME LOOP FAILURE
The truename entry for a cluster did not point back to the cluster record.
24 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.
25 ALLOCATE OF COMPARE DATA SET FAILED
The BCS named in the VVDS record could not be allocated.
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
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 REL CELL ENTRY NOT FOUND
An entry in a REL (“relation”) cell in a cluster record does not represent an alternate index
entry.
31 OPEN OF COMPARE DATA SET FAILED
The BCS named in the VVDS record could not be opened.
32 WRONG RECORD TYPE

560 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC21364I

A BCS record which matches a VVDS record was found, but the BCS record is not a
cluster, truename, or non-VSAM record.
33 INCOMPLETE UPDATE DETECTED
The current entry was undergoing a subrecord update/move operation that did not
complete. This record or subrecord may be damaged.
34 VVDS AND VTOC ENDING CCHH UNEQUAL
The extent information kept in the VTOC and VVDS should agree, but do not.
35 VVDS AND VTOC EXTENT COUNTS UNEQUAL
The extent information kept in the VTOC and VVDS should agree, but do not.
36 LENGTH OF NAME INVALID
The length of a name cell should be from 1 to 45 characters long, but is not.
37 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.
38 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.
39 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.
40 COMPONENT CELL NOT FOUND
The component cell for a VSAM cluster could not be found within the cluster's sphere
record in the BCS.
41 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.
42 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.)
43 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.
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 VVDS ENTRY NOT FOUND. DATA SET OPEN ERROR.
An attempt to open the BCS named in the VVR failed.
48 VVDS ENTRY NOT FOUND. GET RECORD FAILED.
An attempt to get a VVR/NVR record that matches the BCS record failed.
49 VVDS ENTRY NOT FOUND. SCAN RECORD FAILED.

Chapter 20. IDC messages 561

IDC21364I

An attempt to get the specific VVR/NVR within the CI that matches the BCS record failed.
50 VVDS ENTRY NOT FOUND. GET VVDS FAILED.
An attempt to get the entire VVDS record that matches the BCS record failed.
51 VVDS ENTRY NOT FOUND. 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 RESERVED BITS SET IN CATALOG ALIAS ENTRY.
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:
For BCS Entries:
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.
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.
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.
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.
38 Delete the cluster entry with DELETE NOSCRATCH, and recatalog it with DEFINE RECATALOG. Then
rebuild the alternate index with DEFINE ALTERNATEINDEX and BLDINDEX.
41 Delete the data set. Then use DELETE VVR or NVR to delete the duplicate VVDS record. Recover the data
set from a backup copy.
42 Use REPRO MERGECAT to move the data set's catalog entry to the correct catalog.

562 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC21365I • IDC21372I

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 z/OS DFSMS Managing Catalogs for the
appropriate recovery procedures.
47 Determine if the BCS named in the VVR is valid. If necessary, see z/OS DFSMS Managing Catalogs for the
appropriate recovery procedures.
48 Determine whether the BCS entry or the VVR/NVR entry is in error. See z/OS DFSMS Managing Catalogs for
the appropriate recovery procedures.
49 Determine whether the BCS entry or the VVR/NVR entry is in error. See z/OS DFSMS Managing Catalogs for
the appropriate recovery procedures.
50 Determine whether the BCS entry or the VVR/NVR entry is in error. See z/OS DFSMS Managing Catalogs for
the appropriate recovery procedures.
51 Determine whether the BCS entry or the VVR/NVR entry is in error. See z/OS DFSMS Managing Catalogs for
the appropriate recovery procedures.
53 Delete and redefine the alias entry to correct the problem.
Source: DFSMSdfp
Detecting Module: IDCDA02

IDC21365I text RECORD DISPLAY: RECORD: rec

Explanation: text is one of the following:
ICFCATALOG
VVDS
VTOC

The record which follows was involved in an error detected by DIAGNOSE. A previous error message 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.

In the message text:

rec 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.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp
Detecting Module: IDCDA03

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.
In the message text:
xxxxxxxxxxxxxx The indicated DD name or data set name.
Application Programmer Response: Check for spelling error. Check for message IDC11373I to see if compare

Chapter 20. IDC messages 563

IDC21404I • IDC21410I

elements were not used during the DIAGNOSE run. Correct the statement and resubmit the job.
Source: DFSMSdfp
Detecting Module: IDCDA01

IDC21404I dsname IS AN INVALID ASSOCIATION FOR SPHERE TYPE

Explanation: The data set is not a valid association for its base object.
In the message text:
dsname The data set name.
System action: The base object and any of its associations already defined will be deleted from the target catalog
and the processing will continue with the next base object.
Application Programmer Response: Correct the problem and rerun the job.
System programmer response: Enter the access method services LISTCAT command to list catalog entries and
information about objects defined in the catalog. If the error recurs and the program is not in error, look at the
messages in the job log for more information. Search problem reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL, the SYSOUT output for the job, and all printed output and
output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCCC02

IDC21409I CONVERSION FAILED FOR SPHERE dsname

Explanation: The specified sphere base could not be converted to the target catalog.
In the message text:
dsname The data set name.
System action: Processing is continued with the next base object.
Application Programmer Response: Correct the problem indicated in a preceding message and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCCC01

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.
In the message text:
sph The indicated sphere.
System action: Processing of the sphere is ended and processing continues with the conversion of the next sphere’s
base.
Application Programmer Response: You can respond to one of the following conditions:
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.
System programmer response: Enter the access method services LISTCAT command to list catalog entries and
information about objects defined in the catalog.
Source: DFSMSdfp
Detecting Module: IDCCC01

564 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC21411I • IDC21608I

IDC21411I 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.
In the message text:
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.
Application Programmer Response: The data set can be recovered by using the REPRO command. Then reissue the
CNVTCAT command.
System programmer response: Enter the access method services LISTCAT command to list catalog entries and
information about objects defined in the catalog.
Source: DFSMSdfp
Detecting Module: IDCCC02

IDC21412I DEFINE FAILED FOR dsname

Explanation: The define failed for the specified data set.
In the message text:
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.
Application Programmer Response: Restore the catalog volume and all volumes owned by the catalog; correct the
problem and reissue the CNVTCAT command.
Source: DFSMSdfp
Detecting Module: IDCCC02

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
System action: Processing continues.
Application Programmer Response: Probable user 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
Detecting Module: IDCLA01

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.
System action: Processing continues.

Chapter 20. IDC messages 565

IDC21700I • IDC21803I

Application Programmer Response: None.

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

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).
Application Programmer Response: The data set 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.
In the message text:
name The storage group name.
System action: Processing continues with the next storage group.
Application Programmer Response: Verify validity of specified storage group.
System 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 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 output data sets
related to the problem.

566 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC21804I

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.
In the message text:
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.)
System action: Processing associated with the error return code is ended.
System 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 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 output data sets
related to the problem.
A list of the return and reason codes follow for each function affected:
Function
MIGRATION DATA COLLECTION SERVICE
Code Reason Explanation
04 Incorrect parameter list.
01 UPID not equal to UPIDNAME.
02 UPVERS incompatible with current version used by ARCUTIL.
03 Data control block (DCB) address not provided.
04 No functions to perform.
05 Incorrect combinations of options.
08 Error opening DFHSM control data set.
01 DFSMShsm MCDS could not be opened.
02 DFSMShsm BCDS could not be opened.
10 The VTOC for this volume is not an MVS VTOC. CVAF/DADSM will only work with
MVS VTOCs.
0C 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.
10 Error writing to the output data set.
The reason code contains the contents of register 1 received from the SYNADAF
macro.
14 An abnormal end occurred.
The reason code contains the system completion code.
Function
DEVICE INFORMATION SERVICE

Chapter 20. IDC messages 567

IDC21805I

Code Reason Explanation

00
10
04 Storage for the parameter list is not owned by the caller.
08 Size of parameter list is incorrect.
0C 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.
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.
14
04 The pointer in JESCT to the EDT is zero.
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 z/OS DFSMSdfp Diagnosis for more information about
the CVAF reason code.
0C 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.
In the message text:
volser The volume serial number.

568 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC21807I • IDC21814I

System action: Processing continues with the next volume.

Application Programmer Response: Ensure that the user control block (UCB) for this volume is valid.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp

IDC21807I FAILURE DURING function PROCESSING - RETURN CODE WAS return-code

Explanation: The return code was returned by the named function as a result of an exceptional condition.
In the message text:
function The function name can be one of the following:
v TRACK CALCULATION SERVICE
v LSPACE SERVICE (SVC 78)
v SMS CONFIGURATION SERVICE
return-code
The return code.
v See z/OS DFSMSdfp Storage Administration for the return codes to Track calculation services (TRKCALC)
and LSPACE SERVICE (LSPACE).
v See z/OS DFSMSdfp Diagnosis for the return code to SMS Configuration Services.
System action: Processing associated with the error return code ends.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp

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.
In the message text:
xx The type record.
dsname The data set name.
volser The volume serial number.
System action: Processing continues.
Application Programmer Response: Correct the problem. Run the utility again.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp

IDC21814I FAILURE DURING function PROCESSING FOR dsname - RETURN CODE WAS return-code
Explanation: The return code was returned with the named function as a result of an exceptional condition.
In the message text:
function The name of the function.

Chapter 20. IDC messages 569

IDC21815I

dsname The data set name.

return-code The return code.
System action: Processing associated with the error return code ends.
System 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 SMF and LOGREC records for information associated with the error. Verify that the
data set can be allocated and opened from the failing system. Verify the device is online and available. Increase the
job region size. Verify the results being returned by system installation exits associated with the failing function.
Search problem reporting data bases for a fix for the problem. If no fix exists, or the return-code indicates an internal
error, contact the IBM Support Center. Provide the JCL, the SYSOUT output for the job, and all printed output and
output data sets related to the problem.
See the following publications for more information:
v z/OS MVS Installation Exits
v DFSMSdfp Installation Exits in z/OS DFSMS Implementing System-Managed Storage
v z/OS DFSMSdfp Diagnosis.

A list of the return and reason codes follow for each function affected:
Function
DASD CALCULATION SERVICE
Code Reason Explanation
04 Information for this data set could not be calculated.
10 Internal Error.
14 Internal Error.
18 Error encountered while accessing the volume table of contents (VTOC).
1C Internal Error.
20 Storage unavailable.
24 Error encountered while accessing the volume table of contents (VTOC).
28 Error encountered while accessing device information.
2C Internal Error.
30 Error encountered during dynamic allocation.
34 Error encountered during PDSE File and Attribute Management Services.
Source: DFSMSdfp

IDC21815I ARCUTIL NOT CALLED. DATA CONTROL BLOCK ADDRESS IS INVALID

Explanation: The address of the output data set's 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 set's I/O is being controlled by the user. If "M", "B", "C", or "T" records are
required, IDCAMS must open the output data set so that the DCB can be passed to ARCUTIL.
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 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 printed output and output data sets
related to the problem.

570 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC21862I • IDC31004I

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.
In the message text:
offset The offset.
number The record number in the source data set.
System action: Processing continues. The return code is 8.
Application Programmer Response: Make sure the DBCS data meet the following criteria:
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

Explanation: The catalog specified for reset is not a recoverable catalog.
System action: The RESETCAT command is ended. No change has been made to the catalog or a Catalog Recovery
Area (CRA).
Application Programmer Response: Respecify the catalog to be reset.
Source: DFSMSdfp
Detecting Module: IDCRS02

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.
System action: The RESETCAT command is ended. No change has been made to the catalog or a Catalog Recovery
Area (CRA).
Application Programmer Response: Ensure that the catalog to be reset is not in use as a master catalog before
issuing RESETCAT.
Source: DFSMSdfp
Detecting Module: IDCRS01

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
Detecting Module: IDCRS06

Chapter 20. IDC messages 571

IDC31006I • IDC31010I

IDC31006I PHYSICAL I/O ERROR - VSAM ACTION CODE actcde

Explanation: A physical I/O error on the catalog was encountered while extending the catalog.
In the message text:
actcde The action code.
System action: The RESETCAT command is ended.
Application Programmer Response: Correct the physical error and reissue RESETCAT. The VSAM action code can
be found in the z/OS 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
Detecting Module: IDCRS07

IDC31007I LOGICAL I/O ERROR - VSAM ACTION CODE actcde

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.
In the message text:
actcde The action code.
System action: The operation is ended.
Application Programmer Response: Correct the logical error. The VSAM action code can be found in z/OS 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
Detecting Module: IDCRS07

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.
System action: The operation is ended.
Application Programmer Response: Correct the 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
Detecting Module: IDCRS01

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.
In the message text:
volser The volume serial number.
System action: The operation is ended.
Application Programmer Response: Respecify the correct volume to be reset and reissue the command.
Source: DFSMSdfp
Detecting Module: IDCRS01

572 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31012I • IDC31017I

IDC31012I MAXIMUM RELATIVE RECORD NUMBER EXCEEDED IN WORK FILE

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.
Application Programmer Response: Respecify subsets of the CRA volumes specified for reset and issue multiple
RESETCAT commands. The catalog entries have not been altered.
Source: DFSMSdfp
Detecting Module: IDCRS06

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)
System action: The operation is ended.
Application Programmer Response: Correct the error in the referenced message and reissue the command. The
catalog entries have not been altered.
Source: DFSMSdfp
Detecting Module: IDCRS01

IDC31014I DELETE OF WORK FILE FAILED

Explanation: DELETE failed for the work file. Message IDC3009I precedes this identifying the specific error.
System action: The operation is ended.
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
Detecting Module: IDCRS06

IDC31016I NO CRA SPECIFIED FOR RESET

Explanation: The CRAFILES parameter specified no CRA with the ALL option; hence, no volume was specified for
reset.
System action: The operation is ended.
Application Programmer Response: Specify the correct volumes for reset and issue the command.
Source: DFSMSdfp
Detecting Module: IDCRS01

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.
System action: The operation is ended.
Application Programmer Response: For the catalog being reset, specify DISP=(OLD,KEEP) on the DD statement, or
get exclusive use. Reissue the command.
Source: DFSMSdfp
Detecting Module: IDCRS01

Chapter 20. IDC messages 573

IDC31018I • IDC31038I

IDC31018I CRA UNAVAILABLE

Explanation: RESETCAT required a volume that could not be allocated.
System action: The operation is ended.
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
Detecting Module: IDCRS01

IDC31019I CRA volser SPECIFIED FOR RESET MORE THAN ONCE

Explanation: The CRAVOLS parameter specified the same volser more than once, or the CRAFILES parameter
specified the same volser more than once via ddnames.
In the message text:
volser The volume serial number.
System action: The operation is ended.
Application Programmer Response: Specify the correct volumes for reset and reissue the command.
Source: DFSMSdfp
Detecting Module: IDCRS01

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).
In the message text:
volser The volume serial number.
System action: The command may end (see Explanation).
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)
System action: The operation is ended.
Application Programmer Response: Correct the error in the referenced message and reissue the command. The
catalog entries have been updated but the CRA entries have not.
Source: DFSMSdfp
Detecting Module: IDCDA01, IDCRS01

574 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31126I • IDC31148I

IDC31126I UNABLE TO READ MSC MAIN STORAGE

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.
System action: The operation is ended.
Application Programmer Response: Perform the response indicated in the description of the message that identified
the MSSC reason code.
Source: DFSMSdfp
Detecting Module: IDCCH01

IDC31143I ** INCOMPLETE {CHECK|READ} REPORT PRODUCED, ERROR AT X LOCATION xxx

Explanation: The AUDITMSS command is unable to check the status of all the requested cells, or to read the labels
of all the requested cartridges.
In the message text:
xxx The X coordinate of the cell where the error occurred.
System action: The command ends.
Application Programmer Response: Reissue the command for the values not processed (all the cells with X
coordinate equal to or greater than xxx), after corrective action was taken as indicated in the primary message.
Source: DFSMSdfp
Detecting Module: IDCAU03

IDC31145I ** NO READ REPORT PRODUCED, ERROR AT X LOCATION xxx

Explanation: The AUDITMSS command is unable to read the labels of any of the requested cartridges.
In the message text:
xxx The X coordinate of the cell where the error occurred.
System action: The command ends.
Application Programmer Response: Reissue the command for the values not processed (all the cells with X
coordinate equal to or greater than xxx), after corrective action was taken as indicated in the primary message.
Source: DFSMSdfp
Detecting Module: IDCAU03

IDC31148I ** NOT AUDIT REPORT PRODUCED, ERROR WITHIN X RANGE n1 n2

Explanation: The AUDITMSS command is unable to check the status of any of the requested cells.
In the message text:
n1 n2 The X coordinates of the range of cells that could not be checked.
Application Programmer Response: Reissue the 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: IDCAU03

Chapter 20. IDC messages 575

IDC31160I • IDC31201I

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.
Application Programmer Response: Correctly 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.
System action: Processing of this command ends.
Application Programmer Response: Reissue the command after the problem with the Mass Storage Control has
been corrected.
Source: DFSMSdfp
Detecting Module: IDCST01

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.
System action: Processing of this command ends.
Application Programmer Response: Ensure that the work data set is allocated properly, and rerun the command.
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.
System action: Processing of this command ends.
Application Programmer Response: Ensure that the work data set is allocated properly, and rerun the command.
Source: DFSMSdfp
Detecting Module: IDCCP01, IDCEC01

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.
In the message text:
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data

576 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31202I • IDC31204I

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
Detecting Module: IDCRD02

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.
In the message text:
volser The volume serial number.
cchhr The five hexadecimal characters that identify the record address.
dsname The repair work file.
System action: REPAIRV DISPLAY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Correct 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.
System programmer response: Enter the access method services PRINT command to print the repair work data set.
If the error recurs and the program is not in error, search problem reporting data bases for a fix for the problem. If no
fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD02

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.
System action: REPAIRV DISPLAY/COPY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Either change the unit parameter in the JCL to a real unit or change
STAGINGRANGE to DATASETRANGE, as appropriate, and resubmit.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD07

IDC31204I 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.
In the message text:
volser The volume serial number.
System action: REPAIRV DISPLAY/COPY ends control returns to access method services. The return code is 12.
Application Programmer Response: Determine the correct volume serial number and correct either the job control
language or STAGINGRANGE, as appropriate, and resubmit.
System programmer response: If the error recurs and the program is not in error, search problem reporting data

Chapter 20. IDC messages 577

IDC31205I • IDC31207I

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
Detecting Module: IDCRD07

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.
In the message text:
cchhr Identify a record address.
System action: REPAIRV DISPLAY/COPY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Determine the 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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD07

IDC31206I AUTHORIZATION TO ACCESS TO STAGINGPACK VOL=SER=volser DENIED BY SYSTEM

OPERATOR
Explanation: The system operator has responded “N” to REPAIRV’s request (IDC499D) for access to the specified
volume.
In the message text:
volser The volume serial number.
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD07

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.
In the message text:
cchhr Identify a record in the track.
System action: REPAIRV DISPLAY/COPY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Correct STAGINGRANGE and resubmit.
System programmer response: If the error recurs and the program is not in error, search problem reporting data

578 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31208I • IDC31210I

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
Detecting Module: IDCRD07

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.
In the message text:
cchhr1 The first key specified. It indicates a record address.
cchhr2 The second key specified. It indicates a record address.
volser The volume serial number.
System action: The REPAIRV DISPLAY or the REPAIRV COPY command ends. Control returns to access method
services. The return code is 12.
Application Programmer Response: Correct STAGINGRANGE so that the second key (cchhr) is greater then or
equal to the first key (cchhr) and resubmit.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD07

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

In the message text:

volser The volume serial number.
parameter
The specified parameter.
ddname The specified DD name.
System action: REPAIRV DISPLAY/COPY/MODIFY ends. Control returns to access method services. The return
code is 12.
Application Programmer Response: Determine the correct volume serial number of the volume containing the data
set whose records are to be processed and correct either the JCL or parameter as appropriate, and resubmit.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD07

Chapter 20. IDC messages 579

IDC31211I • IDC31213I

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.
In the message text:
dsname The data set name.
System action: REPAIRV ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Either change the unit in the job control language to a virtual unit or change
the parameters as appropriate, and resubmit.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD07

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.
In the message text:
cchhr1 The first key of the range. It indicates a record address.
cchhr2 The second key of the range. It indicates a record address.
dsname The data set name.
System action: REPAIRV DISPLAY/COPY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Determine the actual extents of the data set. Correct the DATASETRANGE
parameters of the named data set and resubmit.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCRD07

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.
In the message text:
hh1 The first key.
hh2 The second key.
dsname The data set name.
System action: REPAIRV DEBLOCK/MODIFY ends. Control returns to access method services. The return 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 programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp

580 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31214I • IDC31221I

Detecting Module: IDCRD04

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.
In the message text:
volser The volume serial number.
cchh The address of a record.
dsname The data set name.
System action: REPAIRV DEBLOCK ends. Control returns to access method services. The return code is 12.
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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD04

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.
In the message text:
dsname The data set name.
System action: REPAIRV DEBLOCK ends. Control returns to access method services. The return code is 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.
System programmer response: Enter the access method services PRINT command to print the repair work data set.
If the error recurs and the program is not in error, search problem reporting data bases for a fix for the problem. If no
fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD06

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.
In the message text:
volser The volume serial number.
cchh The address of a record.
dsname The data set name.
System action: REPAIRV MODIFY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Determine the actual extents of the data set, then correct the
INDATASETADDRESS parameter and resubmit.
System programmer response: 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

Chapter 20. IDC messages 581

IDC31222I • IDC31224I

for the job, and all printed output and output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCRD05

IDC31222I RECORD IN INREPAIRKEY volsercchhr NOT FOUND FOR dsname

Explanation: The record specified in INREPAIRKEY is not in the referenced repair work file.
In the message text:
volser The volume serial number.
cchh The address of a record.
dsname The repair work file.
System action: REPAIRV MODIFY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Display the repair work file records. If necessary, recreate the repair work file
using REPAIRV COPY, or correct the INREPAIRKEY parameter, and rerun.
System programmer response: Enter the access method services PRINT command to print the repair work data set.
If the error recurs and the program is not in error, search problem reporting data bases for a fix for the problem. If no
fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD05

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).
In the message text:
volser The volume serial number.
cchh The address of a record.
dsname The output data set name.
parameter
The specified parameter.
System action: REPAIRV MODIFY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Determine the actual address of the record. Correct the
OUTDATASETADDRESS or VTOCHEADER parameter and resubmit.
System programmer response: 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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCRD05

IDC31224I RECORD IN OUTREPAIRKEY volsercchhr NOT FOUND FOR dsname

Explanation: The record specified in OUTREPAIRKEY is not in the referenced repair work file.
In the message text:
volser The volume serial number.
cchh The address of a record.
dsname The repair work file.

582 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31225I • IDC31226I

System action: REPAIRV MODIFY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Display the repair work file records. If necessary, recreate the repair work file
using REPAIRV COPY, or correct the OUTREPAIRKEY parameter, and resubmit.
System programmer response: Enter the access method services PRINT command to print the repair work data set.
If the error recurs and the program is not in error, search problem reporting data bases for a fix for the problem. If no
fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD05

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.
In the message text:
volser The volume serial number.
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
The specified parameter.
System action: REPAIRV MODIFY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Correct the address in OUTDATASETADDRESS or VTOCHEADERADDRESS
to ensure a 0 in the record field, and a match to the INREPAIRRANGE first address.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD05

IDC31226I NOT ALL TRACKS SPECIFIED IN INREPAIR RANGE ARE ALLOCATED TO OUTPUT text
Explanation: text is one of the following:
dsname
VTOCHEADER

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.

In the message text:

dsname The specified data set name.
System action: REPAIRV MODIFY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Determine the actual extents of the data set. Correct the INREPAIRRANGE
parameter to specify only allocated tracks and resubmit.
System programmer response: Enter the access method services PRINT command to print the repair work data set.
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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCRD05

Chapter 20. IDC messages 583

IDC31227I • IDC31229I

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.
In the message text:
volser The volume serial number.
cchh The address of a record.
dsname The repair work file.
System action: REPAIRV MODIFY ends after the entire range. Control returns to access method services. The return
code is 12.
Application Programmer Response: Display the repair work file records. If necessary, recreate the repair work file
using REPAIRV COPY. Correct INREPAIRRANGE and resubmit.
System programmer response: Enter the access method services PRINT command to print the repair work data set.
If the error recurs and the program is not in error, search problem reporting data bases for a fix for the problem. If no
fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD05

IDC31228I 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.
In the message text:
volser The volume serial number.
cchhr The address of a record.
dsname The repair work file.
System action: REPAIRV MODIFY ends after checking the entire range. Control returns to access method services.
The return code is 12.
Application Programmer Response: Correct INREPAIRRANGE and resubmit.
System programmer response: Enter the access method services PRINT command to print the repair work data set.
If the error recurs and the program is not in error, search problem reporting data bases for a fix for the problem. If no
fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD05

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.
In the message text:
cchh The address of a record.
dsname The specified data set name.
System action: REPAIRV MODIFY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Verify that your input is correct and will fit within the specified track.
System programmer response: Enter the access method services PRINT command to print the repair work data set.
If the error recurs and the program is not in error, search problem reporting data bases for a fix for the problem. If no

584 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31230I • IDC31232I

fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD05

IDC31230I OFFSET n OUTSIDE KEY OR DATA FIELD

Explanation: The offset specified for the key or data field is longer than the actual key or data field length.
In the message text:
n The offset.
System action: REPAIRV MODIFY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Correct the OFFSET parameter and resubmit.
System programmer response: Enter the access method services PRINT command to print the repair work data set.
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 output data sets related to the problem.
Source: DFSMSdfp
Detecting Module: IDCRD05

IDC31231I INPUT RECORD TOO LARGE {dsname|VTOCHEADER}

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.
In the message text:
dsname The output data set name.
System action: REPAIRV MODIFY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Ensure that the replacement record will fit in the output data set track.
System programmer response: Enter the access method services PRINT command to print the repair work data set.
If the error recurs and the program is not in error, search problem reporting data bases for a fix for the problem. If no
fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD05

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.
In the message text:
dsname The specified data set name or repair work file.
System action: REPAIRV MODIFY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Verify that the input string does not cause the modified record to exceed its
track boundary.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD05

Chapter 20. IDC messages 585

IDC31233I • IDC31235I

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.
In the message text:
parameter
The specified parameter.
cchh The address of a record.
dsname The repair work file.
System action: REPAIRV DISPLAY/COPY/MODIFY ends. Control returns to access method services. The return
code is 12.
Application Programmer Response: Correct parameters and resubmit.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD07

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.
In the message text:
cchhr The address of a record.
System action: REPAIRV DISPLAY/COPY/MODIFY ends. Control returns to access method services. The return
code is 12.
Application Programmer Response: Determine the 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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD07

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.
In the message text:
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 The repair work file.
System action: REPAIRV DISPLAY/COPY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Correct DATASETRANGE so that the second cchhr is greater then or equal to
the first cchhr and resubmit.
System programmer response: If the error recurs and the program is not in error, search problem reporting data

586 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31237I • IDC31239I

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
Detecting Module: IDCRD07

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.
System action: REPAIRV DEBLOCK ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Correct the key and data lengths specified in the LENGTH parameter are
correct: display the R‘0/R’1 records, correct, and rerun.
System programmer response: Enter the access method services PRINT command to print the repair work data set.
If the error recurs and the program is not in error, search problem reporting data bases for a fix for the problem. If no
fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD04

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.
In the message text:
dsname The specified data set name.
System action: REPAIRV COPY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Correct the condition causing the failure.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD03

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.
In the message text:
cchhr The address of a record.
System action: REPAIRV MODIFY ends, control returns to access method services. The return code is 12.
Application Programmer Response: Correct the condition causing the failure.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD07

Chapter 20. IDC messages 587

IDC31240I • IDC31243I

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.
In the message text:
cchhr The address of a record.
System action: REPAIRV MODIFY ends. Control returns to access method services. Return code is 12.
Application Programmer Response: Correct the condition causing the failure.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD07

IDC31241I NEWCOUNT MUST BE EIGHT BYTES LONG

Explanation: The length specified in the NEWCOUNT parameter is less than 8 bytes long.
System action: REPAIRV MODIFY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Correct the NEWCOUNT parameter to be exactly 8 bytes long.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD05

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.
In the message text:
volser The volume serial number.
cchh The address of a record.
dsname The repair work file.
System action: REPAIRV MODIFY ends. Control returns to access method services. The return code is 12.
Application Programmer Response: Rerun the job; the error should correct itself, that is, it either goes away or
becomes a destage error.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD05

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.
In the message text:
cchhr The address of a record.

588 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31244I • IDC31246I

System action: REPAIRV MODIFY ends. Control returns to access method services. The return 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.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD05

IDC31244I UNABLE TO DEBLOCK cchh

Explanation: The record pair (R‘0 or R‘1) that results from the stage error could not be deblocked because the R‘1
record contained a dummy data field length of 1. This condition is caused by the loss of the track descriptor during
staging.
In the message text:
cchh The address of a record.
System action: The command ends. The return code is 12.
Application Programmer Response: Verify that you specified the correct address in the command. The R‘1 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 R‘1 record can be restored by using the REPAIRV MODIFY
command.
System programmer response: Enter the access method services PRINT command to print the repair If the error
recurs and the program is not in error, search problem reporting data bases for a fix for the problem. If no fix exists,
contact the IBM Support Center. Provide the JCL and the SYSOUT output for the job. work data set.
Source: DFSMSdfp
Detecting Module: IDCRD04

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.
In the message text:
cchh The address of a record.
dsname The repair work file.
System action: REPAIRV MODIFY processing ends. Control returns to access method services. The return code is
12.
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
Detecting Module: IDCRD05

IDC31246I OBTAIN FAILED FOR dsname

Explanation: OBTAIN SVC failed for the specified data set name.
In the message text:
dsname The specified data set name.
System action: REPAIRV ends. Control returns to access method services. The return code is 12.
Application Programmer Response: If processing a VSAM data set, ensure that unit and volume information are

Chapter 20. IDC messages 589

IDC31247I • IDC31366I

not present on the DD statement for the specified data set name. Correct the condition causing the failure and
resubmit.
System programmer response: If the error recurs and the program is not in error, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT
output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD07

IDC31247I TRACK DOES NOT BEGIN WITH RECORD 1

Explanation: The data portion of record pair R‘0, which shows the original first record number, shows that record
number to be other than record 1.
System action: The command ends. The return code is 12.
Application Programmer Response: Issue REPAIRV DISPLAY to display the blocked stage error records R‘0 and
R‘1. If the records appear to be valid, usable records that you want to deblock, issue REPAIRV MODIFY to change
the R‘0 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.
System programmer response: Enter the access method services PRINT command to print the repair work data set.
If the error recurs and the program is not in error, search problem reporting data bases for a fix for the problem. If no
fix exists, contact the IBM Support Center. Provide the JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCRD04

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

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.
System action: The command ends.
Application Programmer Response: Rerun the COPYV command specifying NOT MOUNTED.
Source: DFSMSdfp
Detecting Module: IDCCO01

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.
Application Programmer Response: Correct the statement and resubmit the job.
Source: DFSMSdfp
Detecting Module: IDCDA01

590 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31368I • IDC31376I

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.
Application Programmer Response: Correct the 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
Detecting Module: IDCDA01

IDC31369I text PROCESSING TRUNCATED

Explanation: text is one of the following:
MAXIMUM ERROR LIMIT REACHED
I/O ERROR ON INPUT DATA SET

The number of errors encountered in the input or compared data sets has reached the error limit value. This message
may also result from I/O errors, if so, 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.
System action: DIAGNOSE considers this an error condition; processing ended.
Application Programmer Response: If the 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
Detecting Module: IDCDA01

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.
In the message text:
dsname The data set name.
ddname The DD name.
System action: DIAGNOSE considers this an error condition; processing may end or continue, depending on which
data set incurred the error.
Application Programmer Response: Check the 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
Detecting Module: IDCDA01

IDC31376I INPUT CATALOG HAS NO VVDS ENTRIES

Explanation: The ICF catalog that the system is currently diagnosing has no SYS1.VVDS.Vvolser entries. This
indicates BCS damage; there should be a VVDS entry for the volume.
System action: The system ends DIAGNOSE processing.
Application Programmer Response: Take the following actions.
v Import the BCS to restore it.
v Uplevel the BCS.

Chapter 20. IDC messages 591

IDC31377I • IDC31403I

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.
System action: The system ends processing.
Application Programmer Response: Take the following actions.
v Import the BCS to restore it.
v Uplevel the BCS.
v Re-run DIAGNOSE.
Source: DFSMSdfp

IDC31400I 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.
System action: The command is ended.
Application Programmer Response: Correct the specification of the catalog and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCCC01

IDC31401I 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.
In the message text:
dsname The data set name.
Application Programmer Response: Restore the catalog volume, and all volumes owned by the catalog, correct the
problem identified in the associated message and rerun the job.
System programmer response: Enter the access method services LISTCAT command to list catalog entries and
information about objects defined in the catalog.
Source: DFSMSdfp
Detecting Module: IDCCC01

IDC31403I UNABLE TO DETERMINE CATALOG TYPE FOR dsname

Explanation: A catalog management LOCATE failed and the catalog type could not be determined.
In the message text:
dsname The data set name.
System action: The command is ended.
Application Programmer Response: Correct the problem identified in the associated message and rerun the job.
System programmer response: Enter the access method services LISTCAT command to list catalog entries and
information about objects defined in the catalog.
Source: DFSMSdfp
Detecting Module: IDCCC01

592 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31405I • IDC31461I

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:
Source Target
OS CVOL VSAM
OS CVOL ICF
VSAM ICF
System action: Processing of this command is ended.
Application Programmer Response: Correct the source and/or target catalog specification and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCCC01

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.
System action: Processing of this command is ended.
Application Programmer Response: Verify the 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 converted.
Source: DFSMSdfp
Detecting Module: IDCCC01

IDC31440I 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.
System action: The command is ended.
Application Programmer Response: Check if the correct catalog has been specified to be listed. Check the LISTCAT
CATALOG parameter.
System programmer response: 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 SYSOUT output for the
job.
Source: DFSMSdfp
Detecting Module: IDCLC01

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.
System action: Processing of this command is ended.
Application Programmer Response: Verify the 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.
System 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 problem reporting data bases for a fix for the problem. If no fix exists, contact the

Chapter 20. IDC messages 593

IDC31466I • IDC31470I

IBM Support Center. Provide the JCL and the SYSOUT output for the job.
Source: DFSMSdfp
Detecting Module: IDCRP01

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.
In the message text:
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

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

IDC31469I MISMATCH OF FIRST OR THIRD QUALIFIERS FOR VOLCATS

Explanation: During a volume catalog REPRO request, it has been determined that either the first qualifiers'
matched or the third qualifiers' did not match.
REPRO NOMERGECAT allows the REPRO of a specific VOLCAT but ensures that all VOLUMEENTRIES copied are
of the same type. For example, you do not want VA entries to be copied into the VB catalog.
Source: DFSMSdfp
System action: The system stops processing the command.
System programmer response: Specify a valid combination of volume catalogs.

IDC31470I VGENERAL TO VGENERAL NOT ALLOWED

Explanation: During a volume catalog REPRO request, it has been determined that both volume catalogs are
VGENERAL's. Only one VGENERAL volume catalog is allowed on the system in any time.
Source: DFSMSdfp
Detecting Module: IDCRP01
System action: The system stops processing the command.
System programmer response: Specify a valid combination of volume catalogs.

594 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31474I • IDC31504I

| IDC31474I LOGREPLICATE CANNOT BE SPECIFIED WITHOUT LOGSTREAMID

| Explanation: The LOGREPLICATE specified on the IDCAMS DEFINE CLUSTER command is not valid, because the
| LOGSTREAMID parameter was not specified.
| System action: Processing of the command was stopped.
| Application Programmer Response: Specify the LOGSTREAMID parameter when the LOGREPLICATE parameter is
| specified. If there are no LOGSTREAMID values, remove the LOGREPLICATE parameter from the DEFINE
| CLUSTER command.
| System programmer response: If the error recurs and the program is not in error, refer to the messages in the job
| log for more information. Search problem reporting data bases for a fix for the problem. If no fix exists, contact the
| IBM Support Center with the JCL and the SYSOUT output for the job.
| Source: DFSMSdfp
| Detecting Module: IDCDE02

IDC31502I SPECIFIED cchh IS NOT IN BOUNDS OF THE 3380

Explanation: The record address has the value of LOWCCHH or HIGHCCHH. The value should be in range for the
device attached to the Model 13.
In the message text:
cchh The address of a record.
System action: The command is not processed.
Application Programmer Response: Correct the command and resubmit.
Source: DFSMSdfp
Detecting Module: IDCBD01, IDCSS04

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.
System action: The system does not process the 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.
System action: The system ends the command.
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
Detecting Module: IDCSS03

Chapter 20. IDC messages 595

IDC31550I • IDC31559I

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
Detecting Module: IDCLA01

IDC31559I ASYNCHRONOUS OPERATIONS MANAGER RC=return-code REASON=reason-code other

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.
In the message text:
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:
v 32 bytes of I/O sense data in the form:
SENSE BYTES 0-15 xxxxxxxx xxxxxxxx
xxxxxxxx xxxxxxxx
16-31 xxxxxxxx xxxxxxxx
xxxxxxxx xxxxxxxx

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

The Asynchronous Operations Manager return and reason codes are:

Return Codes
0 SUCCESSFUL
The request to the service completed without error.
4 REQUEST FAILED
The request to the service failed with the reason code specified below.
8 OPERATION FAILED
The request to the service failed with the reason code specified below.
12 ASYNCHRONOUS OPERATIONS MANAGER ERROR
The request to the service failed with the reason code specified below.

Return Code 4: Reason Codes

4 INSUFFICIENT STORAGE

596 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31559I

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.
8 INVALID PARAMETER LIST
Internal error. IDCAMS should have issued IDC31601I or IDC31550I for this error condition. Please refer to
this message for further details on the error.
12 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.
16 UNABLE TO ESTABLISH ESTAE
Internal error. IDCAMS should have issued IDC2391I for this error condition. Please refer to this message for
further details on the error condition.
20 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.
24 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.
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 UNABLE TO OBTAIN COMPLETE SSSCB ENTRY
Internal error.
52 DEVICE NUMBER INVALID
Internal error.
56 UCB ADDRESS OR DEVICE NUMBER NEEDED FOR RACF CHECK
Internal error.
60 INVALID RACF LEVEL
Internal error.
76 ONLY ONE ACCESS CODE AVAILABLE
Internal error.
80 INVALID EYE-CATCHER IN SERVL OR UNABLE TO ACCESS LAST BYTE IN SERVL
Internal error.
84 UCB ADDRESS OR DEVICE NUMBER POINTS AT NON-DASD DEVICE

Chapter 20. IDC messages 597

IDC31559I

Internal error.
88 SSDL MISSING
Internal error.
92 REQTYPE DRVR PARM(S) NOT ALLOWED
Internal error.
96 SSDP AND SSDL NOT ALLOWED
Internal error.
100 REQUEST BUFFER HAS ONLY ONE SUB-BUFFER
Internal error.
104 INDIRECT ADDRESS LISTS NOT ALLOWED IN DRVR CHANNEL PROGRAM
Internal error.
108 TIC MUST POINT AT *-8
Internal error.
112 UCB ADDRESS OR DEVICE NUMBER 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.
132 INVALID EYE-CATCHER IN INPUT BUFFER
Internal error.
136 SSDP POINTS AT AREA NOT OWNED BY CALLER
Internal error.
140 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.

Return Code 8: Reason Codes

4 I/O ERROR EXECUTING CALLER'S 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.
8 ASYNCHRONOUS OPERATION PENDING
The asynchronous operation is still in progress and IDCAMS should still be waiting for completion.
12 ASYNCHRONOUS OPERATION COMPLETED IN ERROR
IDCAMS should have issued IDC2391I for this error condition. Please refer to that message for details on
the error.
16 ASYNCHRONOUS OPERATION FAILED
IDCAMS should issue IDC31610I message for this error condition. Refer to that message for details on the
error.

598 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31561I

20 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.
24 REQUEST LOST BY SUBSYSTEM
The storage control lost knowledge of the asynchronous operation. Please refer to a merged LOGREC listing
for more details. 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.

Return Code 12: Reason Codes

4 INTERNAL QUEUE ERROR
Internal error.
8 ABNORMAL TERMINATION
Internal error.
System action: Processing continues.
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.
In the message text:
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.
System action: Processing continues.
Application Programmer Response: For MVS/ESA or MVS/XA, refer to z/OS DFSMSdfp Storage Administration for
the meanings of CVSTAT codes.
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.

Chapter 20. IDC messages 599

IDC31562I • IDC31564I

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.

In the message text:

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
System action: Processing continues.
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
Detecting Module: IDCSS01

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.

600 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31601I • IDC31606I

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.
In the message text:
volser The volume serial number.
System action: The system does not process the command with the FILE or VOLUME parameter.
Application Programmer Response: Probable user error, or the operator varied offline the device with the specified
volume.
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
Detecting Module: IDCSS02

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.
System 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 problem reporting data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center.
Source: DFSMSdfp
Detecting Module: IDCSS03

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. 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.
For a SETCACHE request, action and cause can be replaced with the following values:
Action Causes/Responses
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 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.

Chapter 20. IDC messages 601

IDC31606I

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

602 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31606I

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 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).
-NVS OFFLINE: Issue a SETCACHE NVS ON to activate NVS.
-CACHE OFFLINE: Issue a SETCACHE SUBSYSTEM ON to activate subsystem 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.

Chapter 20. IDC messages 603

IDC31606I

-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 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 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).
-NVS OFFLINE: Issue a SETCACHE NVS ON to activate NVS.
-CACHE OFFLINE: Issue a SETCACHE SUBSYSTEM ON to activate subsystem 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.
TERMINATE A DUPLEX PAIR
-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.
-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
-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.
-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.

604 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31607I • IDC31610I

In the message text:

volser The volume serial number.
action The specified action.
cause The cause of the error.
System action: Processing continues.
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.
In the message text:
devid The device identification.
Source: DFSMSdfp
Detecting Module: IDCSS01

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

In the message text:

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
System action: Processing continues.
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).
For the COMPLETED IN ERROR condition, the 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

Chapter 20. IDC messages 605

IDC31611I • IDC31615I

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.
v REESTABLISHDUPLEX (reestablish a duplex pair) requires the alternate volume to be offline.
System action: Processing continues.
Application Programmer Response: Vary the secondary/alternate device offline (in ALL hosts attached to the
subsystem) and rerun the command.
Source: DFSMSdfp

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.
System action: Processing continues.
Application Programmer Response: Vary the storage director online and issue a SETCACHE SUBSYSTEM ON.
Source: DFSMSdfp

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

In the message text:

606 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31616I • IDC31617I

device The device identifier.

System action: Processing continues.
Application Programmer Response: Resubmit the command using a device identifier (unit number) attached to a
supported subsystem for which the request is to be run.
Source: DFSMSdfp

IDC31616I REINITIALIZE FAILED device IS NOT OFFLINE

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.
In the message text:
device The device identifier (unit number) for one of the devices attached to the subsystem.
System action: Processing continues.
Application Programmer Response: Resubmit the command after all volumes have been varied offline.
Source: DFSMSdfp

IDC31617I THE COMMAND command IS COMPLETE FOR {THE SUBSYSTEM CONTAINING} volser | unitaddr
{SUBCHANNEL SET ID n}
Explanation: The I/O operation for the SETCACHE command completed successfully.
In the message text:
command
One of the following:
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 The volume serial number.
unitaddr
The unit address.
SUBCHANNEL SET ID n
The subchannel set number in which the unit address displayed in the message response resides.
System action: The system sets the return code to 0.
Application Programmer Response: None.
Source: DFSMSdfp

Chapter 20. IDC messages 607

IDC31620I • IDC31652I

IDC31620I NO SPACE EFFICIENT VOLUME FOUND

Explanation: No space efficient volume is found within the specified scope of the request.
System action: The system does not process the command.
Application Programmer Response: None.
System programmer response: The most likely cause of this message is that there are no volumes configured as
space efficient. Other reasons include that no space efficient volume is connected to the system, or space efficient
volumes are out of the search scope.
When ALL, SUBSYSTEM, or DEVICE is specified with FILE or VOLUME, the online volume configured as space
efficient is reported.
When DEVICE is specified with UNITNUMBER, the volume configured as space efficient is reported regardless of
volume online or offline.

Note: UNITNUMBER can't be specified with SUBSYSTEM or ALL.

If the search of offline space efficient volumes is needed, check the list of space efficient volume in Extent Pool
configuration status report by issuing LISTDATA with EXTENTPOOLCONFIG, EXTENTPOOLID and VOLMAP. If
Subsystem configuration column has the space efficient volume, but no MVS address in the host configuration
column of the table of mapping from device to volume bit map, then the space efficient volume has no connection to
the system. Ask the storage administrator to attach the space efficient volume to the system. Then issue the space
efficient volume status request again.
Source: DFSMSdfp

IDC31621I SPECIFIED EXTENT POOL ID IS NOT ACCESSIBLE BY SPECIFIED VOLUME

Explanation: The specified extent pool ID, on the LISTDATA EPC EPID query, is not accessible by the specified
volume.
System action: The system does not process the command.
Application Programmer Response: None.
System programmer response: Correct the FILE, VOLUME, or UNITNUMBER parameter values on the LISTDATA
EPC EPID query. A volume in an even-numbered LSS must be specified to generate a detailed report for an
even-numbered extent pool ID. A volume in an odd-numbered LSS must be specified to generate a detailed report
for an odd-numbered extent pool ID. Issue the command again.
Source: DFSMSdfp

IDC31622I ALLOCATED REPOSITORY SPACE INFORMATION NOT AVAILABLE

Explanation: The allocated repository space information about one or more devices is not available at the time of
the LISTDATA SEV or the LISTDATA EPC query.
System action: The system does not process the command.
Application Programmer Response: None.
System programmer response: The storage control unit indicates that the allocated repository space information
about one or more resources (devices or extent pools) is not available at the time of the LISTDATA SEV or the
LISTDATA EPC query. Retry the command. If the retried command fails, contact the storage administrator for further
analysis.
Source: DFSMSdfp

IDC31652I OBJECT NOT SUPPORTED IN CIMODE

Explanation: An attempt was made to import an object from a CIMODE portable data set, which is not supported
on this system. IMPORT CIMODE can only use ESDS base clusters that do not have an alternate index.
System action: The system ends processing.

608 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31655I • IDC31700I

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

IDC31655I ‘keywd’ PARAMETER INVALID WITH ENTRY TYPE

Explanation: The specified keyword is improper for the type of object being imported.
In the message text:
keywd The specified keyword.
System action: The command is ended.
Application Programmer Response: Specify the proper parameters for the type of object being imported and retry
the command.
Source: DFSMSdfp
Detecting Module: IDCMP01

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.
System action: The system ends processing of the 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.
Source: DFSMSdfp
Detecting Module: IDCMP01

IDC31660I 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.
System action: The system ends command processing.
Application Programmer Response: Correct the catalog name on the out data set or outfile. Run the job again.
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.
Application Programmer Response: Obtain APF authorization for the caller of access method services using the
problem program interface.
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 precedes this
message.
Source: DFSMSdfp

Chapter 20. IDC messages 609

IDC31701I • IDC31706I

IDC31701I INSUFFICIENT VIRTUAL STORAGE AVAILABLE

Explanation: Virtual storage is insufficient to continue processing.
System action: The data set is closed, and processing ends.
Application Programmer Response: Increase the region size and re-run.
Source: DFSMSdfp

IDC31702I 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.
System action: The data set is closed, and processing ends.
Application Programmer Response: Verify that you are using the correct data set name.
Source: DFSMSdfp

IDC31703I DATA SET REQUESTED FOUND TO BE IN CREATE MODE

Explanation: The data set is in create mode and, therefore, cannot be tested.
System action: The data set is closed, and processing ends.
Application Programmer Response: Verify that you 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.
System action: The data set is closed, and 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.
Source: DFSMSdfp

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.
System action: The data set is closed, and processing ends.
Application Programmer Response: You should 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

IDC31706I VSAM CONTROL BLOCK ERROR

Explanation: At least one field within a VSAM control block built by OPEN contains incorrect data.
System action: The data set is closed, and processing ends.
Application Programmer Response: You should attempt to determine the cause of the problem. See z/OS DFSMSdfp
Diagnosisfor information on dumps points.
Source: DFSMSdfp

610 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31707I • IDC31750I

IDC31707I ERROR OBTAINING TSO QUALIFIER

Explanation: The Time Sharing Option/Extensions (TSO/E) user id cannot be prefixed to the unqualified data set
name.
System action: Processing ends.
Application Programmer Response: You should attempt to determine the cause of the problem. See z/OS DFSMSdfp
Diagnosis 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.
System action: Processing ends.
Application Programmer Response: You should attempt to determine the cause of the problem. See z/OS DFSMSdfp
Diagnosisfor information on dump points.
Source: DFSMSdfp

IDC31709I ERROR OBTAINING VOLUME INFORMATION

Explanation: Volume information for the specified entry name cannot be obtained.
System action: Processing ends.
Application Programmer Response: You should attempt to determine the cause of the problem. Refer to z/OS
DFSMSdfp Diagnosisfor information on dump points.
Source: DFSMSdfp

IDC31710I CI ACCESS ERROR

Explanation: An I/O error has been encountered while attempting to read a control interval.
System action: Processing ends.
Application Programmer Response: You should attempt to determine the cause of the problem. See z/OS DFSMSdfp
Diagnosis for information on dump points.
Source: DFSMSdfp

IDC31713I THE CONTROL INTERVAL IN THE HIGHEST INDEX LEVEL HAS AN RBA OF ZERO
Explanation: The control interval in the highest index level is found to have RBA = 0. EXAMINE cannot continue.
System action: Supportive messages display pertinent data, and processing ends.
Application Programmer Response: See summary messages for final analysis.
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.
System action: The system ends processing of the 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

Chapter 20. IDC messages 611

IDC31751I • IDC31810I

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.
In the message text:
code The abend code.
System action: The system ends the command.
Application Programmer Response: None.
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.
In the message text:
name The data set name.
System action: The system ends the command.
Application Programmer Response: Ensure that the data set has a data set organization of physical sequential and a
record format of “V” or “VB”.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp

IDC31802I LOAD OF MODULE name WAS UNSUCCESSFUL. ABEND CODE IS xx - REASON CODE IS
reason-code
Explanation: The named module could not be loaded into system storage.
In the message text:
name The name of the module.
xx The abend code.
reason-code The reason code.
System action: Processing provided by the named module is not performed.
Application Programmer Response: Notify the system programmer.
System 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 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 output data sets
related to the problem.
Source: DFSMSdfp

IDC31810I INSUFFICIENT FACILITY CLASS AUTHORIZATION TO PERFORM FUNCTION

Explanation: An attempt was made to perform a function without proper authority to
‘STGADMIN.IDC.DCOLLECT’.
System action: The system ends the command.
Application Programmer Response: Obtain proper facility class authorization to ‘STGADMIN.IDC.DCOLLECT’.

612 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31863I • IDC31865I

System 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 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 output data sets
related to the problem.
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
4 One or more pairs have the offset missing.
8 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.

In the message text:

number The offset pair in which the error was detected.
reason-code The reason code.
System action: The command is ended. The return code is 12.
Application Programmer Response: Recheck the 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

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 that a set of offset pairs had overlapping ranges. This would
cause the data to fail during DBCS criteria checking.
In the message text:
number1 and number2
The offset pairs with overlapping values.
System action: The command is ended. The return code is 12.
Application Programmer Response: Recheck the offset pair specifications in the INSERTSHIFT keyword. You
should make sure that offset pair values do not overlap.
Source: DFSMSdfp

IDC31865I OFFSET offset IN OFFSET PAIR number EXCEEDS MAXIMUM RECORD LENGTH
Explanation: INSERTSHIFT was specified on an 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.
In the message text:
offset The offset.
number The offset pair.
System action: The command is ended. The return code is 12.
Application Programmer Response: Recheck the 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.

Chapter 20. IDC messages 613

IDC31880I • IDC31886I

Source: DFSMSdfp

IDC31880I RECOVERY NOT SET FOR dsname

Explanation: A SHCDS FRSETRR command failed for data set dsname. The explanation for the command failure
follows the message.
Source: DFSMSdfp
Detecting Module: IDCSH07

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
Detecting Module: IDCSH08

IDC31882I BIND NOT SET FOR dsname

Explanation: A SHCDS FRBIND command failed for data set dsname. The explanation for the command failure
follows the message.
Source: DFSMSdfp
Detecting Module: IDCSH09

IDC31883I IDC31883I RECOVERY NOT RESET FOR dsname

Explanation: A SHCDS FRRESETRR command failed for data set dsname. The explanation for the command failure
follows the message.
Source: DFSMSdfp
Detecting Module: IDCSH10

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
Detecting Module: IDCSH11

IDC31885I NON-RLS UPDATE NOT PERMITTED FOR dsname

Explanation: The data set that has been accessed in RLS mode has failed to be permitted access in non-RLS mode.
The explanation for the command failure follows the message.
Source: DFSMSdfp
Detecting Module: IDCSH12

IDC31886I NON-RLS UPDATE NOT DENIED FOR dsname

Explanation: The data set that has been accessed in non-RLS mode is not denied access in non-RLS mode.
Source: DFSMSdfp
Detecting Module: IDCSH13

614 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31887I • IDC31890I

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
Detecting Module: IDCSH14

IDC31888I UNEXPECTED ERROR FROM SMSVSAM SERVER

DIAGNOSTIC INFORMATION:
RC = rc
RS = rsnc
Explanation: The SMSVSAM address space returned the error indicated by the values of rc and rsnc.
In the message text:
rc The return code.
rsnc
The reason code.
Operator response: Contact the system programmer regarding procedures to start the SMSVSAM address space.
Application Programmer Response: Contact the system programmer regarding procedures to start the SMSVSAM
address space.
System programmer response: For documentation of the SMSVSAM problem, see z/OS DFSMSdfp Diagnosis.
Source: DFSMSdfp
Detecting Module: IDCSH01, IDCSH02, IDCSH03, IDCSH04, IDCSH05, IDCSH06, IDCSH07, IDCSH08, IDCSH09,
IDCSH10, IDCSH11, IDCSH12, IDCSH13, IDCSH14, IDCSH15

IDC31889I SMSVSAM SERVER NOT AVAILABLE

Explanation: The SMSVSAM address space is not available to handle the request.
Operator response: Contact the system programmer regarding procedures to start the SMSVSAM address space.
Application Programmer Response: Contact the system programmer regarding procedures to start the SMSVSAM
address space.
System programmer response: Make the SMSVSAM address space available. For requirements, see z/OS DFSMSdfp
Storage Administration.
Source: DFSMSdfp
Detecting Module: IDCSH01, IDCSH02, IDCSH03, IDCSH04, IDCSH05, IDCSH06, IDCSH07, IDCSH08, IDCSH09,
IDCSH10, IDCSH11, IDCSH12, IDCSH13, IDCSH14, IDCSH15

IDC31890I DATASET NOT LISTED

Explanation: The SMSVSAM address space did not contain information related to the data set requested. DFSMSdfp
can also issue this message in response to the SHCDS subcommand LISTDS, LISTSHUNTED, LISTSUBSYS, or
LISTSUBSYSDS. The list does not include the data set if it is not currently open in RLS mode or if related lock
information is not maintained in the SMSVSAM address space.
Application Programmer Response: Ensure that the data set name is specified correctly, and verify that the related
catalog has connectivity to the system on which the SHCDS command was issued. Contact the system programmer
for SMSVSAM diagnosis instructions.
System programmer response: For requirements, see z/OS DFSMSdfp Storage Administration.
Source: DFSMSdfp

Chapter 20. IDC messages 615

IDC31891I • IDC31894I

Detecting Module: IDCSH02, IDCSH04, IDCSH05, IDCSH06

IDC31891I SUBSYSTEM NOT LISTED

Explanation: The SMSVSAM address space did not contain information related to the subsystem requested. Can be
issued also in response to SHCDS sub-commands LISTDS, LISTSUBSYS, or 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.
System programmer response: See the z/OS DFSMSdfp Storage Administration for requirements.
Source: DFSMSdfp
Detecting Module: IDCSH02, IDCSH03, IDCSH04, IDCSH05, IDCSH06

IDC31892I 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, DENYNONRLSUPDATE, REMOVESUBSYS, CFREPAIR,
CFRESET, CRFREPAIRDS, and CFRESETDS subcommands.
For the CFREPAIR and CFRESET subcommands, ALTER authority is required to the specified catalog.
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, IDCSH21

IDC31893I NO SUBSYSTEM INFORMATION FOUND

Explanation: The SMSVSAM address space did not contain information related to the subsystem requested. Can be
issued also in response to SHCDS sub-commands LISTDS, LISTSUBSYS, or 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.
System programmer response: See the z/OS DFSMSdfp Storage Administration for requirements.
Source: DFSMSdfp
Detecting Module: IDCSH02, IDCSH03, IDCSH04, IDCSH05, IDCSH06

IDC31894I NO DATASET RECOVERY INFORMATION FOUND

Explanation: The SMSVSAM address space did not 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.
System programmer response: See the z/OS DFSMSdfp Storage Administration for requirements.

616 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31895I • IDC31900I

Source: DFSMSdfp
Detecting Module: IDCSH05

IDC31895I DATA SETS UNSUCCESSFULLY PROCESSED

Explanation: An SHCDS CFREPAIR, CFRESET, CFREPAIRDS, 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
Application Programmer Response: Examine the return and reason codes and determine if any further action needs
to be taken.
Source: DFSMSdfp
Detecting Module: IDCSH15, IDCSH16, IDCSH17, IDCSH21

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,
CFREPAIRDS, CFRESET, or CFRESETDS command.
Application Programmer Response: Obtain the proper authorization for the command.
System programmer response: Provide authorization for using the SHCDS command.
Source: DFSMSdfp
Detecting Module: IDCSH15, IDCSH16, IDCSH17, IDCSH21

IDC31897I CATALOG MUST BE ICF FOR SHCDS COMMAND

Explanation: An SHCDS CFREPAIR or CFRESET command was issued against a catalog that is not an ICF catalog.
Application Programmer Response: Specify the name of an ICF catalog as the parameter of the INDATASET option.
Source: DFSMSdfp
Detecting Module: IDCSH15, IDCSH16

IDC31898I SECURITY VERIFICATION FAILED FOR DATA SET

Explanation: The requestor does not have sufficient authorization to perform the function on the specified data set.
Application Programmer Response: Obtain the required authorization for the data set.
Source: DFSMSdfp
Detecting Module: IDCSH07, IDCSH08, IDCSH09, IDCSH10, IDCSH11

IDC31900I INCORRECT SPECIFICATION OF 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.
In the message text:
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

Chapter 20. IDC messages 617

 IDC31901I • IDC31903I

01 - 28 for February (not a leap year).

01 - 29 for February (leap year).
01 - 30 for April, June, September, and November
01 - 31 for January, March, May, July, August, October and December.
32 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.
System action: The system stops processing the command.
System programmer response: Correct the date and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCAL02

IDC31901I INCORRECT VALUE FOR parameter

Explanation: An invalid value was specified for the named parameter. See z/OS DFSMS Access Method Services for
Catalogs for more information about valid values.
In the message text:
parameter
The named parameter.
System action: The system stops processing the command.
System programmer response: Specify a valid value and rerun the job.
Source: DFSMSdfp
Detecting Module: IDCCR01

IDC31903I 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.
In the message text:
parameter1
Parameter value that should be lesser than or equal to parameter2.
parameter2
Parameter value that should be greater.
System action: The system stops processing the command.
System programmer response: Correct the appropriate parameter to ensure that the value of parameter2 is greater
than or equal to the value of parameter1.
| For example, lets say you get the following version of this message:
| IDC31903I NUMBERSCRATCHVOLUMES IS GREATER THAN AVAILABLE VOLUMES

| This message indicates that the following IDCAMS command was issued to specify the scratch threshold for a certain
| media, but the total slots defined are not high enough to support the specified scratch threshold:
| ALTER libname LIBENTRY SCRATCHTHRESHOLD(MEDIAx(num))

| Do the following to set the total slots higher than the scratch threshold:
| ALTER libname LIBENTRY NUMBERSLOTS(num+1)

| followed immediately by:

| ALTER libname LIBENTRY SCRATCHTHRESHOLD(MEDIAx(num))

618 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31950I • IDC31955I

Source: DFSMSdfp
Detecting Module: IDCAL02

IDC31950I NO LOCKS TO BIND/UNBIND

Explanation: There were no locks found for the FRBIND/FRUNBIND request for the data set.
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
Detecting Module: IDCSH08, IDCSH09

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
Detecting Module: IDCSH07, IDCSH08, IDCSH09, IDCSH10, IDCSH11, IDCSH12, IDCSH13

IDC31952I NOT SMS-MANAGED VSAM DATA SET

Explanation: The SHCDS subcommand requires that the object of the command be a VSAM data set that is
managed by the Storage Management Subsystem (SMS).
Application Programmer Response: Ensure that the data set is specified correctly.
Source: DFSMSdfp
Detecting Module: IDCSH07, IDCSH08, IDCSH09, IDCSH10, IDCSH11

IDC31953I NO UNBOUND LOCKS TO DELETE

Explanation: No unbound locks were found for the data set.
Application Programmer Response: Ensure that the data set is specified correctly.
Source: DFSMSdfp
Detecting Module: IDCSH11

IDC31954I DATA SET DOES NOT HAVE RETAINED OR LOST LOCKS

Explanation: No retained or lost locks were found for the data set. DFSMSdfp can issue this message in response to
the RESETLOCKS subcommand.
Application Programmer Response: Ensure that the data set is specified correctly.
Source: DFSMSdfp
Detecting Module: IDCSH12, IDCSH13

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.
Application Programmer Response: Ensure that the data set is specified correctly.
Source: DFSMSdfp
Detecting Module: IDCSH12, IDCSH13

Chapter 20. IDC messages 619

IDC31956I • IDC31960I

IDC31956I DATA SET NOT FOUND

Explanation: The catalog search failed, or the data set is not active within SMSVSAM.
Application Programmer Response: Ensure that the data set is specified correctly.
Source: DFSMSdfp
Detecting Module: IDCSH02, IDCSH04, IDCSH05, IDCSH06, IDCSH07, IDCSH08, IDCSH09, IDCSH10, IDCSH11,
IDCSH12, IDCSH13

IDC31957I SUBSYSTEM NOT FOUND

Explanation: The requested subsystem was not found.
Application Programmer Response: Ensure that the subsystem is specified correctly. Use the SHCDS LISTSUBSYS
or LISTSUBSYSDS subcommands to verify the subsystem status.
Source: DFSMSdfp
Detecting Module: IDCSH02, IDCSH03, IDCSH04, IDCSH05, IDCSH06, IDCSH11, IDCSH12, IDCSH13

IDC31958I SUBSYSTEM CURRENTLY ACTIVE

Explanation: The requested subsystem was active with the SMSVSAM address space.
Application Programmer Response: Ensure that the subsystem is specified correctly. Use the SHCDS LISTSUBSYS
or LISTSUBSYSDS subcommands to verify the subsystem status.
Source: DFSMSdfp
Detecting Module: IDCSH14

IDC31959I ERROR DATA:

X'diagnostic-error-data'
Explanation: The FR* command failed and diagnostic-error-data was returned.
In the message text:
diagnostic-error-data
Contains return-code and reason-code values.
Application Programmer Response: For causes of the failure, see z/OS DFSMSdfp Diagnosis.
System programmer response: For documentation of the SMSVSAM problem, see z/OS DFSMSdfp Diagnosis.
Source: DFSMSdfp
Detecting Module: IDCSH07, IDCSH08, IDCSH09, IDCSH10, IDCSH11

IDC31960I RECOVERY NOT FOUND FOR SPHERE dsn

Explanation: An SHCDS LISTSHUNTED, PURGE, or RETRY command was issued, and the requested sphere does
not exist or does not have shunted transactions.
In the message text:
dsn
A data set name.
System action: The system continues processing.
Operator response: None
System programmer response: Make sure that the data set name specified in the command is correct and that the
data set exists.
Problem determination: None

620 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31961I • IDC31963I

Source: DFSMSdfp
Detecting Module: IDCSH18, IDCSH19, IDCSH20

IDC31961I UNIT OF RECOVERY NOT FOUND

Explanation: An SHCDS LISTSHUNTED, PURGE, or RETRY command was issued and the requested unit of
recovery does not exist or does not have shunted transactions.
System action: The system continues processing.
Operator response: None
System programmer response: Make sure that the unit-of-recovery identifier specified in the command is correct
and that the unit of recovery exists.
Problem determination: None
Source: DFSMSdfp
Detecting Module: IDCSH18, IDCSH19, IDCSH20

IDC31962I TRANSACTIONAL VSAM IS NOT AVAILABLE

Explanation: The DFSMStvs service is not available. DFSMSdfp can issue this message in any of these cases:
v DFSMStvs is terminating.
v Initialization of DFSMStvs is incomplete.
v Restart processing is complete.
System action: The system continues processing.
Operator response: Contact the system programmer about starting DFSMStvs.
Application Programmer Response: Contact the system programmer about starting DFSMStvs.
System programmer response: Start the DFSMStvs service. If the DFSMStvs service has already been started, run
the requested function after initialization or restart processing is complete.
Problem determination: None
Source: DFSMSdfp
Detecting Module: IDCSH18, IDCSH19, IDCSH20

IDC31963I RETRY UNSUCCESSFUL FOR DATA SET dsn

URID STATUS CAUSE

xxx yyy zzz
DIAGNOSTIC REASON
rc rsnc
Explanation: An SHCDS RETRY command did not complete successfully. The values of zzz under CAUSE and the
return code (rc) and reason code (rsnc) under DIAGNOSTIC REASON indicate the reason for the failure.
In the message text:
dsn
The name of a data set.
xxx
The identifier of a unit of recovery.
yyy
The status of the unit of recovery.
zzz
The cause of the failure. For an explanation of possible entries in the CAUSE column, see the following table.

Chapter 20. IDC messages 621

IDC31963I

Cause Explanation Action

B-FAILED The backout failed. For information about the return and reason codes, see z/OS MVS Programming:
Resource Recovery.
C-FAILED The commit failed. For information about the return and reason codes, see z/OS MVS Programming:
Resource Recovery.
IO- An error occurred in issuing I/O. The diagnostic reason code contains a request parameter list (RPL). feedback word,
ERROR in rsnc.
DS-FULL The data set capacity was reached. The system was unable to extend the data set.
IX-FULL The alternate index capacity was A larger alternate index is needed.
reached.
LOCK A lock error occurred. A record lock could not be obtained during backout. Refer to the job log for
additional messages.
LOG An error occurred in accessing the Refer to the job log for messages that indicate logging errors.
DFSMStvs logs.
CACHE The system was unable to connect Verify that the coupling facility cache assigned to the data set is available. Refer to
to the cache structure assigned for message IGW454I to determine why the connect attempt to the DFSMS coupling
the data set. facility cache structure failed.
OPEN-ERR An error occurred in opening the Refer to the job log for messages that indicate errors related to opening the data set.
data set.
ALLO-ERR An error occurred in dynamically The diagnostic reason code contains the dynamic allocation failure code.
allocating the data set.
CLOS-ERR An error occurred in closing the Refer to the job log for messages that indicate errors related to closing the data set.
data set.
DEAL-ERR An error occurred in dynamically The diagnostic reason code contains the dynamic deallocation failure code.
deallocating the data set.
RST-ERR The unit of recovery is being DFSMStvs restart processing is currently processing this unit of recovery. Rerun the
processed by DFSMStvs restart command after restart has completed.
processing.
DSN-ERR An associated data set encountered One or more data sets for this unit of recovery received an error.
an error.
VRM-ERR An error was returned during The diagnostic reason code contains the RPL feedback word, in rsnc.
record processing.
INC-ERR An inconsistency error occurred. Log records for a unit of recovery were found. All other processing for the unit of
recovery was complete. Purge the unit of recovery.
QUI-ERR The data set was quiesced. The data set was closed before a syncpoint was done, and the data set was
quiesced.
RPL-ERR An RPL chain processing error Refer to the job log for messages that indicate errors related to RPL processing.
occurred.
RRS-LOGS An error occurred in processing the Backout encountered one or more errors while processing RRS logs.
resource recovery services (RRS)
logs.
FR-LOG An error occurred in writing to the Refer to the job log for messages that indicate errors related to the forward recovery
forward recovery log. log.
DISABLE Syncpoint processing failed because Enable DFSMStvs and retry the unit of recovery.
the DFSMStvs state is DISABLING
or DISABLED.

rc The return code.

rsnc
The reason code.
System action: The system continues processing.
Operator response: None
Application Programmer Response: Use the return code and reason code to determine the cause of the failure.
Correct the problem, and then reissue the command.
System programmer response: Retained locks for the data set remain held and log records are kept until a
successful retry or purge.
Problem determination: None
Source: DFSMSdfp

622 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31964I

Detecting Module: IDCSH19

IDC31964I RETRY UNSUCCESSFUL FOR UNIT OF RECOVERY urid

CLUSTER NAME/
ALTERNATE INDEX NAME
xxx
STATUS CAUSE
yyy zzz
DIAGNOSTIC REASON
rc rsnc
Explanation: An SHCDS RETRY command did not complete successfully. The value of zzz under CAUSE and the
return code (rc) and reason code (rsnc) under DIAGNOSTIC REASON indicate the reason for the failure.
In the message text:
urid
The identifier of a unit of recovery.
xxx
The name of a VSAM cluster or alternate index.
yyy
The status of the unit of recovery.
zzz
The cause of the failure. For an explanation of possible entries in the CAUSE column, refer to the following table.

Cause Explanation Action

B-FAILED The backout failed. For information about the return and reason codes, see z/OS MVS Programming:
Resource Recovery.
C-FAILED The commit failed. For information about the return and reason codes, see z/OS MVS Programming:
Resource Recovery.
IO- An error occurred in issuing I/O. The diagnostic reason code contains a request parameter list (RPL). feedback word,
ERROR in rsnc.
DS-FULL The data set capacity was reached. The system was unable to extend the data set.
IX-FULL The alternate index capacity was A larger alternate index is needed.
reached.
LOCK A lock error occurred. A record lock could not be obtained during backout. Refer to the job log for
additional messages.
LOG An error occurred in accessing the Refer to the job log for messages that indicate logging errors.
DFSMStvs logs.
CACHE The system was unable to connect Verify that the coupling facility cache assigned to the data set is available. Refer to
to the cache structure assigned for message IGW454I to determine why the connect attempt to the DFSMS coupling
the data set. facility cache structure failed.
OPEN-ERR An error occurred in opening the Refer to the job log for messages that indicate errors related to opening the data set.
data set.
ALLO-ERR An error occurred in dynamically The diagnostic reason code contains the dynamic allocation failure code.
allocating the data set.
CLOS-ERR An error occurred in closing the Refer to the job log for messages that indicate errors related to closing the data set.
data set.
DEAL-ERR An error occurred in dynamically The diagnostic reason code contains the dynamic deallocation failure code.
deallocating the data set.
RST-ERR The unit of recovery is being DFSMStvs restart processing is currently processing this unit of recovery. Rerun the
processed by DFSMStvs restart command after restart has completed.
processing.
DSN-ERR An associated data set encountered One or more data sets for this unit of recovery received an error.
an error.
VRM-ERR An error was returned during The diagnostic reason code contains the RPL feedback word, in rsnc.
record processing.
INC-ERR An inconsistency error occurred. Log records for a unit of recovery were found. All other processing for the unit of
recovery was complete. Purge the unit of recovery.

Chapter 20. IDC messages 623

IDC31965I

QUI-ERR The data set was quiesced. The data set was closed before a syncpoint was done, and the data set was
quiesced.
RPL-ERR An RPL chain processing error Refer to the job log for messages that indicate errors related to RPL processing.
occurred.
RRS-LOGS An error occurred in processing the Backout encountered one or more errors while processing RRS logs.
resource recovery services (RRS)
logs.
FR-LOG An error occurred in writing to the Refer to the job log for messages that indicate errors related to the forward recovery
forward recovery log. log.
DISABLE Syncpoint processing failed because Enable DFSMStvs and retry the unit of recovery.
the DFSMStvs state is DISABLING
or DISABLED.

rc The return code.

rsnc
The reason code.
System action: The system continues processing.
Operator response: Use the return and reason code to determine the cause of the failure. Correct the problem, and
then reissue the command.
Application Programmer Response: Use the return code and reason code to determine the cause of the failure.
Correct the problem, and then reissue the command.
System programmer response: Retained locks for the data set remain held and log records are kept until a
successful retry or purge.
Problem determination: None
Source: DFSMSdfp
Detecting Module: IDCSH19

IDC31965I PURGE UNSUCCESSFUL FOR DATA SET dsn

URID STATUS CAUSE

xxx yyy zzz
DIAGNOSTIC REASON
rc rsnc
Explanation: An SHCDS PURGE command did not complete successfully. The value of zzz under CAUSE and the
return code (rc) and reason code (rsnc) under DIAGNOSTIC REASON indicate the reason for the failure.
In the message text:
dsn
The name of a data set.
xxx
The identifier of a unit of recovery.
yyy
The status of the unit of recovery.
zzz
The cause of the failure. For an explanation of possible entries in the CAUSE column, refer to the following table.

Cause Explanation Action

B-FAILED The backout failed. For information about the return and reason codes, see z/OS MVS Programming:
Resource Recovery.
C-FAILED The commit failed. For information about the return and reason codes, see z/OS MVS Programming:
Resource Recovery.
IO- An error occurred in issuing I/O. The diagnostic reason code contains an request parameter list (RPL). feedback word,
ERROR in rsnc.
DS-FULL The data set capacity was reached. The system was unable to extend the data set.

624 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31966I

IX-FULL The alternate index capacity was A larger alternate index is needed.
reached.
LOCK A lock error occurred. A record lock could not be obtained during backout. Refer to the job log for
additional messages.
LOG An error occurred in accessing the Refer to the job log for messages that indicate logging errors.
DFSMStvs logs.
CACHE The system was unable to connect Verify that the coupling facility cache assigned to the data set is available. Refer to
to the cache structure assigned for message IGW454I to determine why the connect attempt to the DFSMS coupling
the data set. facility cache structure failed.
OPEN-ERR An error occurred in opening the Refer to the job log for messages that indicate errors related to opening the data set.
data set.
ALLO-ERR An error occurred in dynamically The diagnostic reason code contains the dynamic allocation failure code.
allocating the data set.
CLOS-ERR An error occurred in closing the Refer to the job log for messages that indicate errors related to closing the data set.
data set.
DEAL-ERR An error occurred in dynamically The diagnostic reason code contains the dynamic deallocation failure code.
deallocating the data set.
RST-ERR The unit of recovery is being DFSMStvs restart processing is currently processing this unit of recovery. Rerun the
processed by DFSMStvs restart command after restart has completed.
processing.
DSN-ERR An associated data set encountered One or more data sets for this unit of recovery received an error.
an error.
VRM-ERR An error was returned during The diagnostic reason code contains the RPL feedback word, in rsnc.
record processing.
INC-ERR An inconsistency error occurred. Log records for a unit of recovery were found. All other processing for the unit of
recovery was complete. Purge the unit of recovery.
QUI-ERR The data set was quiesced. The data set was closed before a syncpoint was done, and the data set was
quiesced.
RPL-ERR An RPL chain processing error Refer to the job log for messages that indicate errors related to RPL processing.
occurred.
RRS-LOGS An error occurred in processing the Backout encountered one or more errors while processing RRS logs.
resource recovery services (RRS)
logs.
FR-LOG An error occurred in writing to the Refer to the job log for messages that indicate errors related to the forward recovery
forward recovery log. log.
DISABLE Syncpoint processing failed because Enable DFSMStvs and retry the unit of recovery.
the DFSMStvs state is DISABLING
or DISABLED.

rc The return code.

rsnc
The reason code.
System action: The system continues processing.
Operator response: None
Application Programmer Response: Use the return and reason codes to determine the cause of the failure. Correct
the problem, and then reissue the command.
System programmer response: Retained locks for the unit of recovery remain held and log records are kept until a
successful purge.
Problem determination: None
Source: DFSMSdfp
Detecting Module: IDCSH20

IDC31966I PURGE UNSUCCESSFUL FOR UNIT OF RECOVERY urid

CLUSTER NAME/
ALTERNATE INDEX NAME
xxx

Chapter 20. IDC messages 625

IDC31966I

STATUS CAUSE
yyy zzz
DIAGNOSTIC REASON
rc rsnc
Explanation: An SHCDS PURGE command did not complete successfully. The value of zzz under CAUSE and the
return code (rc) and reason code (rsnc) under DIAGNOSTIC REASON indicate the reason for the failure.
In the message text:
urid
The identifier of a unit of recovery.
xxx
The name of a VSAM cluster or alternate index.
yyy
The status of the unit of recovery.
zzz
The cause of the failure. For an explanation of possible entries in the CAUSE column, refer to the following table.

Cause Explanation Action

B-FAILED The backout failed. For information about the return and reason codes, see z/OS MVS Programming:
Resource Recovery.
C-FAILED The commit failed. For information about the return and reason codes, see z/OS MVS Programming:
Resource Recovery.
IO- An error occurred in issuing I/O. The diagnostic reason code contains an request parameter list (RPL). feedback word,
ERROR in rsnc.
DS-FULL The data set capacity was reached. The system was unable to extend the data set.
IX-FULL The alternate index capacity was A larger alternate index is needed.
reached.
LOCK A lock error occurred. A record lock could not be obtained during backout. Refer to the job log for
additional messages.
LOG An error occurred in accessing the Refer to the job log for messages that indicate logging errors.
DFSMStvs logs.
CACHE The system was unable to connect Verify that the coupling facility cache assigned to the data set is available. Refer to
to the cache structure assigned for message IGW454I to determine why the connect attempt to the DFSMS coupling
the data set. facility cache structure failed.
OPEN-ERR An error occurred in opening the Refer to the job log for messages that indicate errors related to opening the data set.
data set.
ALLO-ERR An error occurred in dynamically The diagnostic reason code contains the dynamic allocation failure code.
allocating the data set.
CLOS-ERR An error occurred in closing the Refer to the job log for messages that indicate errors related to closing the data set.
data set.
DEAL-ERR An error occurred in dynamically The diagnostic reason code contains the dynamic deallocation failure code.
deallocating the data set.
RST-ERR The unit of recovery is being DFSMStvs restart processing is currently processing this unit of recovery. Rerun the
processed by DFSMStvs restart command after restart has completed.
processing.
DSN-ERR An associated data set encountered One or more data sets for this unit of recovery received an error.
an error.
VRM-ERR An error was returned during The diagnostic reason code contains the RPL feedback word, in rsnc.
record processing.
INC-ERR An inconsistency error occurred. Log records for a unit of recovery were found. All other processing for the unit of
recovery was complete. Purge the unit of recovery.
QUI-ERR The data set was quiesced. The data set was closed before a syncpoint was done, and the data set was
quiesced.
RPL-ERR An RPL chain processing error Refer to the job log for messages that indicate errors related to RPL processing.
occurred.
RRS-LOGS An error occurred in processing the Backout encountered one or more errors while processing RRS logs.
resource recovery services (RRS)
logs.
FR-LOG An error occurred in writing to the Refer to the job log for messages that indicate errors related to the forward recovery
forward recovery log. log.

626 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IDC31967I • IDC31968I

DISABLE Syncpoint processing failed because Enable DFSMStvs and retry the unit of recovery.
the DFSMStvs state is DISABLING
or DISABLED.

rc The return code.

rsnc
The reason code.
System action: The system continues processing.
Operator response: None
Application Programmer Response: Use the return and reason codes to determine the cause of the failure. Correct
the problem, and then reissue the command.
System programmer response: Retained locks for the unit of recovery remain held and log records are kept until a
successful purge.
Problem determination: None
Source: DFSMSdfp
Detecting Module: IDCSH20

IDC31967I TRANSACTIONAL VSAM BATCH OVERRIDE EXIT HAS FAILED AND IS BEING DISABLED
Explanation: The batch override exit (IGW8PNRU) has failed. The exit abnormally ended while overriding requests
to back out transaction requests. The exit is disabled and will not be called again until DFSMStvs is restarted.
System action: The system continues processing.
Operator response: None
System programmer response: Correct the problem and reinstall the exit. Restart DFSMStvs to activate a new
version.
Problem determination: None
Source: DFSMSdfp
Detecting Module: IDCSH19

IDC31968I RECOVERY REQUIRED FLAG NOT SET

Explanation: A SHCDS command was issued. The command failed because the recovery required flag was not
being set when it was expected to be set on.
System action: The SHCDS command fails.
Operator response: None.
System programmer response: The requested action could not be performed because the recovery required flag was
not set on in the catalog for the data set accessed. The recovery required flag is set by calling the IDCAMS SHCDS
FRSETRR function. This function is typically called by a forward recovery utility such as the CICS VSAM Recovery
Utility (CICS/VR). Check prior messages for the effected data set and recode the application to include a call the
IDCAMS SHCDS FRSETRR function.
Source: DFSMSdfp
Detecting Module: IDCSHFUN
Routing Code: 11

Chapter 20. IDC messages 627

628 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)
Chapter 21. IEA messages
Note: Notice that certain messages in this chapter contain two message identifiers.
The longer message number indicates the addition of subchannel set 1 to a device.

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.
In the message text:
xxx The low number in the range.
zzz The high number in the range.
System action: The system waits for the operator's 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.
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
Routing Code: 3/4/7/8/Note 4
Descriptor Code: 2

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.
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:
IEA000I dev,err,cm,stat,,,[ser],jjj
[,hh.mm.ss]
IEA000I dev,,,sens {,dcbctfd|,opxxterm|
,cylntrck}

© Copyright IBM Corp. 1988, 2012 629

IEA000I

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.

In the message text:

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 is zeros; the error was not caused by
a hardware error on the device, but was caused by the program issuing the I/O.
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 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 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 also contains 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 contains the 8 sense bytes for program errors or 24 sense bytes for
equipment and data checks. For the 3340, this field contains 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 is
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 indicates
the program in error.

630 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA000I

hh.mm.ss
Time that the message was received in hours, minutes, and seconds.
Operator response: For all values of err, probable hardware error. For magnetic tape devices, proceed with caution
in unconditionally accepting the results of 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
Routing Code: 3/4/7/8,10,11
Descriptor Code: 2,4,10

IEA000I dev,err......hh.mm.ss
Explanation: The processor's 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.
In the message text:
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, minutes, and seconds.
System action: The error recovery procedure continues 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
Detecting Module: ERPs
Routing Code: 1
Descriptor Code: 12

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.

Chapter 21. IEA messages 631

IEA002I

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 is 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, TCAM's
threshold support should be used.
Source: DFSMSdfp
Detecting Module: ERPs
Routing Code: 3/4/7/8,10,11
Descriptor Code: 2,4,10

IEA002I APAR aaaaaaa IS NOT INSTALLED ON sys1, SYSTEM sys2 IS BEING PARTITIONED.
Explanation: In the message text:
aaaaaaa indicates the APAR number or UNKNOWN.
During initialization of system sys2, a system in the sysplex has detected that there is missing compatibility or
toleration maintenance on system sys1. System sys2 is being partitioned to prevent data corruption. Note that system
sys1 may or may not be the same system as sys2.
System action: System sys2 is partitioned from the sysplex and enters wait state X'082'.
Operator response: Notify your system programmer.
Application Programmer Response: Install the APAR indicated by the message on system sys1. The APAR may
require an IPL to install. If system sys2 is different than sys1, then sys2 can be IPLed after the APAR is successfully
installed on sys1.
Source: Communications Task, Global Resource Serialization
Detecting Module: IEAVN703, IEAVG603, ISGNST, ISGXSIS, ISGXGX, ISGXGRPX
Routing Code: 1
Descriptor Code: 12

632 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA004W • IEA007I

IEA004W CHANNEL SUBSYSTEM IDENTIFIER IS NOT ZERO

Explanation: The system was IPLed into a partition that has a non-zero channel subsystem identifier (CSSID)
defined. The current level of z/OS does not support non-zero CSSIDs; the system must be at the z990 exploitation
support or above to support non-zero CSSIDs.
System action: The system enters nonrestartable disabled wait state X'07C' with reason code X'1'.
System programmer response: Either IPL the z/OS system in a logical partition with a CSSID of zero, or modify
your I/O configuration to define this partition in CSS zero.
Routing Code: Note 9.
Descriptor Code: 1

IEA005I DATE (AND CLOCK, IF SPECIFIED) REJECTED. DATE MUST BE SPECIFIED AS A 4-DIGIT
YEAR
Explanation: A 2 digit year was specified.

IEA006W LOGICAL PARTITION IDENTIFIER IS NOT IN THE RANGE OF 0-F

Explanation: The system was IPLed in a partition with an logical partition (LPAR) identifier greater than X'F'. The
current level of z/OS does not support LPAR identifiers greater than X'F'. The current level of z/OS does not support
non-zero CSSIDs; the system must be at the z990 exploitation support or above to support LPAR identifiers greater
then X'F'.
System action: The system enters nonrestartable disabled wait state X'07C' with reason code X'2'.
System programmer response: Change the LPAR identifier assigned to the partition in the LPAR image profile to a
number in the range of X'0 - F'
Source: Initial program load (IPL) and nucleus initialization program (NIP)
Routing Code: Note 9
Descriptor Code: 1.

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.

In the message text:

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

Chapter 21. IEA messages 633

IEA008I • IEA009I

&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.
System action: The system continues processing. The system uses the substitution texts that are displayed in the
message text.
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
Source: System initialization (IPL/NIP)
Detecting Module: IEAVESYM
Routing Code: 5,8,9
Descriptor Code: -

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.
In the message text:
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).
System action: The system continues processing. The system uses the system parameters specified in the IEASYSxx
members that are displayed in the message text.
System programmer response: Determine if the system parameters are appropriate for the system. If the list is not
correct, see the section on determining where to specify system parameters in z/OS MVS Initialization and Tuning
Reference for information about how to respecify IEASYSxx members.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPC4
Routing Code: -
Descriptor Code: 2

IEA009I SYMBOLIC DEFINITIONS is 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:

634 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA010I

v The operator specifies an initialization message suppression indicator (IMSI) that does not suppress informational
messages.
v The system programmer specifies the ,L parameter on the IEASYM statement in the LOADxx parmlib member.

In the message text:

xx The suffix of the first IEASYMxx parmlib member in the system parameter concatenation.
zz The suffix of the last IEASYMxx parmlib member in the system parameter concatenation.
System action: The system continues processing. 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.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPIL
Routing Code: -
Descriptor Code: -

IEA010I SYMBOLIC DEFINITION ALTERED:

SYMBOL = &symbol.-name
ORIGINAL VALUE = old-text
NEW VALUE = 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.
In the message text:
&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.
System action: The system continues processing. The system uses the new substitution text for the system symbols
displayed in the message text.
System programmer response: Determine if the new substitution text displayed in the message text is appropriate
for the associated system symbol. If not, see z/OS 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.
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.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVESYM
Routing Code: -
Descriptor Code: -

Chapter 21. IEA messages 635

IEA011A • IEA012E

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.
System programmer response: Do one of the 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.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPIL
Routing Code: -
Descriptor Code: 12

IEA012E CIRCULAR SYMBOLIC DEFINITION DETECTED

text
Explanation: Where text is:

UNRESOLVED STATIC SYMBOL

DEFINITIONS FOLLOW:
IEASYMxx:&symbol-name = symbol-text
.
.
.
IEASYMyy:&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.

In the message text:

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.

636 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA013E

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.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPCF
Routing Code: -
Descriptor Code: 12

IEA013E ERROR DETECTED PROCESSING IEASYMxx: text

Explanation: text is one of the following:
001 MEMBER NOT FOUND
002 RESERVED SYMBOLIC DEFINED : system-symbol-name
003 SYMBOL LENGTH ERROR : system-symbol-name
004 SYMBOL NAME ERROR: system-symbol-name
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

The system found an error in an IEASYMxx parmlib member.

In the message text:

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.
parameter-name
The name of a parameter in IEASYMxx that contained an error.
parameter-value
The value of a parameter in IEASYMxx that contained an error.

The reason code in the message text identifies the error:

Code Meaning and Action
001 Meaning: The system could not find the IEASYMxx parmlib member specified in the LOADxx parmlib
member.
System Programmer Response: Change the value on the IEASYM parameter in LOADxx so it specifies one
or more valid IEASYMxx parmlib members. Then respond to message IEA011A.
002 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 z/OS 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.
003 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 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 Meaning: A SYMDEF parameter in a IEASYMxx parmlib member did not begin with an ampersand (&)
followed by an alphanumeric or national character.

Chapter 21. IEA messages 637

IEA014W

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.
005 Meaning: The number of installation-defined system symbols exceeds the maximum for this system.
System Programmer Response: Reduce the number of installation-defined system symbols in the IEASYMxx
parmlib member so that the total length of the system table does not exceed 32512. Then re-IPL.
To calculate the total length of the system symbol table, use the following formula:
4 + the sum, for every symbol, of 16 + the size of
the symbol (including the leading "&" and the
trailing ".") + the size of the substitution text
006 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 Programmer Response: Change the 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.
007 Meaning: A parameter is specified in a IEASYMxx parmlib member. The undefined parameter is displayed
in the message text.
System Programmer Response: Correct the name of the parameter in IEASYMxx. Then respond to message
IEA011A.
008 Meaning: An undefined parameter in a IEASYMxx parmlib member specified a value. The parameter and
its value are displayed in the message text.
System Programmer Response: Correct the parameter and the value in IEASYMxx. Then respond to
message IEA011A.
System action: The system does 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 X'07D' with reason code X'0004'. 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.
Operator response: Contact the system programmer.
System programmer response: See the system programmer response in the list of reason codes in the message
explanation.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPIL, IEAVNPCF
Routing Code: -
Descriptor Code: 12

IEA014W NONRECOVERABLE ERROR IN IEASYMxx PROCESSING

Explanation: The system found an error in an IEASYMxx parmlib member from which it cannot recover.
In the message text:
xx The suffix of the IEASYMxx parmlib member in which the error occurred.

638 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA015A

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'.
Operator response: Contact the system programmer.
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'.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPCF
Routing Code: -
Descriptor Code: 12

IEA015A text
Explanation: In the message, text is:

THIS SYSTEM HAS LOST ALL

CONNECTION TO THE SYSPLEX TIMER.

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 is
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.
Operator response: Notify the system programmer.
System programmer response: Determine why the 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 is issues. You should first determine if a subset of the ETR
synchronized MVS images have issued IEA015A or whether ALL images have issued it.
If only a few MVS images issued IEA015A, 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 resumes. If the
problem was not resolved, the message is reissued until the problem is fixed or until you reply "ABORT". A reply of
"ABORT" results in a 0A2-114 wait state if the MVS image is a member of a multisystem sysplex. If it is not,
processing resumes in local TOD clock mode.

Chapter 21. IEA messages 639

IEA016W • IEA018A

Notes:
1. When all systems in the sysplex issue IEA015A there is no time limit for making the reply. However, after the first
response is given to IEA015A, the rest of the systems must be replied to within a minimum of four minutes.
When there are more than eight systems in the sysplex the time limit is calculated using (30 seconds * number of
systems).
2. If not all systems in the sysplex are affected, the systems that are still running can take action for "status update
missing" (SUM) on systems waiting for a reply to IEA015A. In this case, the four minute rule does not apply.

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 is possible to recover the dormant 9037 and then reply "RETRY" as previously described.

Note: When replying to IEA015A using the Hardware Management Console (HMC), you must select the priority
message box.
For more information about how to recognize this condition and how to recover from it, see IBM Redbooks
publication S/390® Time Management and IBM 9037 Sysplex Timer, SG24-2070. For detailed information, see the topic
about last Sysplex Timer lost and last Sysplex Timer lost - extended outage.

Also seez/OS MVS Setting Up a Sysplex for the topic on "Understanding PLEXCFG Configurations with a Sysplex
Timer". A Sysplex Timer failure can affect the sysplex in several ways, depending on how the sysplex is configured
with the PLEXCFG system parameter. This section provides additional information on PLEXCFG and describes
different conditions when this message might be issued (for example, with PLEXCFG=MULTISYSTEM and
PLEXCFG=ANY).
Source: Timer Supervision
Detecting Module: IEATSWLH

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.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPC4

IEA017E YOU HAVE INITIALIZED product_name WITH ARCHLVL 1. THIS PRODUCT IS INTENDED TO
BE RUN WITH ARCHLVL 2
Explanation: You have specified ARCHLVL 1 on the LOADxx parmlib member. This violates the Terms and
Conditions for running product product_name on this processor.
In the message text:
product_name
The name of the operating system from field ECVTPNAM in the ECVT control block.
System action: The system initializes in ESA/390 mode and issues operator action message IEA018A.
Operator response: Respond to message IEA018A, which is issued following this message.

IEA018A REPLY TO ACKNOWLEDGE MESSAGE IEA017E

Explanation: This message is issued to enable an operator response acknowledging message IEA017E.
System action: The system waits for the operator response. After the operator responds, the system initializes in
ESA/390 mode. Once IBM License Manager is in production mode, IBM License Manager identifies this as an
exception and logs the exception.
Operator response: Enter any character to acknowledge that message IEA017E has been issued and understood.

640 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA019I • IEA020W

IEA019I dev, volser, VOLUME CAPACITY CHANGE, OLD=xxxxxxxx, NEW=yyyyyyyy .

Explanation: In the message text:
dev
The device number of the device with the capacity change.
volser
The volume serial number of the device with the capacity change.
OLD=xxxxxxxx
The capacity (cylinders) of the device prior to the configuration change.
NEW=yyyyyyyy
The capacity (cylinders) of the device after the configuration change.
System action: The system continues processing.
Operator response: Invoke ICKDSF with REFORMAT/REFVTOC to update the VTOC and index to reflect the real
device capacity.
Source: DFSMSdfp
Detecting Module: IECCINIT

IEA020W AN FRR STACK POINTER FOR CPU x IS DAMAGED, THE ERROR MASK IS abcdefghijklmnopqrst.
Explanation: MVS 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.
If a is 1, PSACSTK is incorrect.
If b is 1, PSANSTK is incorrect.
If c is 1, PSASSTK is incorrect.
If d is 1, PSAMSTK is incorrect.
If e is 1, PSAPSTK is incorrect.
If f is 1, PSAESTK1 is incorrect.
If g is 1, PSAESTK2 is incorrect.
If h is 1, PSAESTK3 is incorrect.
If i is 1, PSARSTK is incorrect.
If j is 1, PSATSTK is incorrect.
If k is 1, PSAASTK is incorrect.
If l is 1, PSASSAV is incorrect.
If m is 1, PSAMSAV is incorrect.
If n is 1, PSAPSAV is incorrect.
If o is 1, PSAESAV1 is incorrect.
If p is 1, PSAESAV2 is incorrect.
If q is 1, PSAESAV3 is incorrect.
If r is 1, PSARSAV is incorrect.
If s is 1, PSATSAV is incorrect.
If t is 1, PSAASAV is incorrect.
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'.
Operator response: See the operator response for wait state X'084' in z/OS MVS System Codes.
System programmer response: See the system programmer response for wait state X'084' in z/OS MVS System Codes.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTRTV
Routing Code: 1
Descriptor Code: 1

Chapter 21. IEA messages 641

IEA021I • IEA023E

IEA021I ACTIVATING SYSTEM CONSOLE AUTOMATICALLY. NO CONSOLES IN AUTOACT GROUP

grpname ARE ACTIVE.
Explanation: All of the consoles in console group grpname are inactive. The system has automatically placed the
system console into PD mode.
System action: None.
Operator response: None.
System programmer response: None.
Source: Communications task (COMMTASK)
Detecting Module: IEAVSWSC
Routing Code: 2 (Also sent to system console)
Descriptor Code: 4

IEA022I DEACTIVATING SYSTEM CONSOLE AUTOMATICALLY. CONSOLE consname IN AUTOACT

GROUP grpname IS ACTIVE.
Explanation: The system console has been activated automatically. Now one of the consoles (consname) in the
AUTOACT group (grpname) has become active. The system is removing the system console from PD mode.
System action: None.
Operator response: None.
System programmer response: None.
Source: Communications task (COMMTASK)
Detecting Module: IEAVSWSC
Routing Code: 2 (Also sent to system console)
Descriptor Code: 4

IEA023E SYSCONS AUTOMATIC ACTIVATE/DEACTIVATE SUSPENDED–text.

Explanation: Text is one of the following three cases, referred to throughout this message as either Case 1, Case 2, or
Case 3.
v Case 1:
SYSTEM CONSOLE AUTOACT GROUP grpname IS NOT DEFINED.
v Case 2:
VARY CN(syscons_name),ACTIVATE ISSUED BY OPERATOR. ISSUE VARY CN(syscons_name),DEACTIVATE TO
RE-ENABLE AUTOACT PROCESSING.
v Case 3:
VARY CN(syscons_name),DEACTIVATE ISSUED BY OPERATOR. ISSUE VARY CN(syscons_name),ACTIVATE TO
RE_ENABLE AUTOACT PROCESSING.

Explanation for Case 1: The system console has an AUTOACT group specified, but the group is not defined in the
current CNGRPxx. The system console is not be automatically placed in PD mode; it is removed from PD mode.

Explanation for Case 2: The system console has an AUTOACT group active. The system console has been put into
PD mode manually. No automatic actions are taken until it is taken out of PD mode by command.

Explanation for Case 3: The system console has an AUTOACT group active. The system console has been taken out
of PD mode manually. No automatic actions are taken until it is put into PD mode by command.
System action: System Action for Case 1: None.
System Action for Case 2: There is no automatic activate or deactivate of the system console. This message is deleted

642 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA024I

when the system console is deactivated by a command, or when the AUTOACT attribute is removed from the system
console.
System Action for Case 3: There is no automatic activate or deactivate of the system console. This message is deleted
when the system console is activated by a command, or when the AUTOACT attribute is removed from the system
console.
Operator response: Operator Response for Case 1: Either issue the SET CNGRP= command to use a CNGRPxx
which has the group defined, or issue VARY CN(syscons_name),AUTOACT= to change the name of the AUTOACT
group. To remove the AUTOACT attribute, issue VARY CN(syscons_name),AUTOACT=*NONE*.
Operator Response for Case 2: When automatic activate/deactivate is wanted again, issue VARY
CN(syscons_name),DEACTIVATE. To remove the AUTOACT attribute, issue VARY
CN(syscons_name),AUTOACT=*NONE*.
Operator Response for Case 3: When automatic activate/deactivate is wanted again, issue VARY
CN(syscons_name),ACTIVATE from the system console. To remove the AUTOACT attribute is removed from the
system console.
System programmer response: System Programmer Response for Case 1: Correct the CONSOLxx and CNGRPxx
parmlib members so that the correct members are specified.
System Programmer Response for Case 2: None.
System Programmer Response for Case 3: None.
Source: Communications task (COMMTASK)
Detecting Module: IEAVSWSC,IEECB854
Routing Code: 1,2,10 (also sent to the system console)
Descriptor Code: 11

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.
In the message text:
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.

Note: If opt is SVC, SVC tracing continues.

System programmer response: Ensure that problem programs are not altering the GTF region.
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.
Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center.
Source: Generalized trace facility (GTF)

Chapter 21. IEA messages 643

IEA025I • IEA030I

IEA025I INVALID GTF RECORD FOLLOWS

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.
System action: Processing continues.
System programmer response: Ensure that problem programs are not altering the trace table.
Source: Generalized trace facility (GTF)
Detecting Module: IGC0F05A
Routing Code: Note 11
Descriptor Code: -

IEA026I A SYNCHRONOUS WTOR TIMED OUT ON THIS CONSOLE. WILL RETRY THE WTOR ON
ccccccccccccccc
Explanation: A synchronous WTOR was displayed on this console, but the reply was not received in the time
allotted.
In the message text:
ccccccccccccccc
Either the console name of the next console, or the system console.
System action: The system has attempted to display the WTOR on the indicated console. This would be the next
available console in the SYNCHDEST console group, or the system console.
Operator response: Go to the indicated console and reply to the WTOR.
Source: Communications task (COMMTASK)
Detecting Module: IEEVDCCA

IEA029D {IEASVC|ALLOC|SCHED} PARMLIB MEMBER HAS AN UNBALANCED COMMENT. REPLY YES

TO CONTINUE IPL OR NO TO RESPECIFY {SVC|ALLOC|SCHED} PARM
Explanation: Parmlib read processing detected an unbalanced comment in the parmlib member. Check message
IEE181I to determine what lines in the parmlib member were affected by the missing comment delimiter. Reply YES
to continue IPLing, or NO to re-specify the parameter in error.
System action: The system waits for the operator to reply.
Operator response: Do one of the following:
v Reply REPLY id,YES to continue the ipl and accepting the lines affected in message IEE181I.
v Reply REPLY id,NO produces another WTOR, message IEA341A that asks to re-specify a new parmlib member or
press ENTER to allow the system defaults for the parmlib member.
v If you reply something other than NO or YES, message IEA029D is issued again
Source: Supervisor, Allocation, Scheduler
Detecting Module: IEAVNP25, IEFAB4IR, IEAVNP18
Routing Code: 2, 10
Descriptor Code: 12

IEA030I OPEN FAILED FOR DUMP DATA SET FOR {JS|ST} [DUE TO {Scde|Ucde}]
Explanation: While failing a task, the system tried to open a SYSABEND, SYSMDUMP, or SYSUDUMP dump data
set, but failed.
In the message text:
JS A dump data set for the job step task could not be opened.

644 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA031I

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. If this message displays a completion code, continue diagnosis with that completion code.
2. This error is accompanied by other system messages, such as IEC150I or messages from your security product.
Use these 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.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTABD
Routing Code: 11
Descriptor Code: -

IEA031I STP ALERT RECEIVED. STP ALERT CODE = nn

Explanation: This message was received because a change occurred with respect to the external time source for the
Coordinated Timing Network (CTN).
In the message text:
nn A hex code which uniquely identifies the STP Alert condition. A list of these codes is given below.
Hex Code Meaning
01 ETS not in use - an External Time Source (ETS) has not been defined for the Coordinated Time Network
(CTN).
02 Dial-out time service is outside of allowable tracking range - the time provide by the ETS differs from
Coordinated Server Time (CST) by 60 seconds or more.
03 Dial-out time service within allowable tracking range - the difference between the time provided by the
ETS and CST is now less than 60 seconds.
04 Dial-out access failure - the CTN is configured for dial-out access but the console was not able to
perform a dial out.
05 Dial-out access successful after having recognized a dial-out access failure.
06 NTP server failure - the CTN is in NTP or PPS mode and the console was not able to access any usable
NTP server.
07 NTP server operational - the console is now able to successfully access an NTP server that is at stratum
level 1 or greater.
08 NTP servers unsynchronized - the CTN is in NTP or PPS mode with both PPS ports enabled and the
NTP-PRT offsets for the ports differ by one second or more.
09 NTP servers synchronized - the CTN is in NTP or PPS mode with both PPS ports enabled and the
NTP-PRT offsets for the ports now differ by less than one second.
0A NTP server switch to non-preferred NTP server- the CTN is in NTP mode with PPS ports disabled and
the console has switched to the non-preferred NTP server to provide NTP information to the STP server.
0B NTP server switch to preferred NTP server- the CTN is in NTP mode with PPS ports disabled and the
console has switched to the preferred NTP server to provide NTP information to the STP server.

Chapter 21. IEA messages 645

IEA031I

10 Preferred NTP server outside of allowable tracking range - the time provided by the preferred NTP
server differs from Coordinated Server Time (CST) by 60 seconds or more.
11 Preferred NTP server within allowable tracking range - the difference between the time provided by the
preferred NTP server and CST is now less than 60 seconds.
12 Preferred NTP server stratum level increase - the stratum level of the preferred NTP server has
increased (e.g., from stratum level 2 to stratum level 3).
13 Preferred NTP server stratum level decrease - the stratum level of the preferred NTP server has
decreased (e.g., from stratum level 3 to stratum level 2).
14 Preferred NTP server inaccessible - the preferred NTP server has transitioned from the accessible state
to the inaccessible state.
15 Preferred NTP server accessible- the preferred NTP server has transitioned from the inaccessible state to
the accessible state
16 Preferred NTP server stratum error - the preferred NTP server has reported a stratum level of 0 or an
invalid stratum level.
17 Preferred NTP server stratum valid - the preferred NTP server has now reported a valid stratum level.
18 Preferred NTP server reference identifier (REFID) change - the REFID for the preferred NTP server has
changed.
20 Non-preferred NTP server outside of allowable tracking range - the time provided by the non-preferred
NTP server differs from Coordinated Server Time (CST) by 60 seconds or more.
21 Non-preferred NTP server within allowable tracking range - the difference between the time provided
by the non-preferred NTP server and CST is now less than 60 seconds.
22 Non-preferred NTP server stratum level increase - the stratum level of the non-preferred NTP server has
increased (e.g., from stratum level 2 to stratum level 3).
23 Non-preferred NTP server stratum level decrease - the stratum level of the non-preferred NTP server
has decreased (e.g., from stratum level 3 to stratum level 2).
24 Non-preferred NTP server inaccessible - the non-preferred NTP server has transitioned from the
accessible state to the inaccessible state.
25 Non-preferred NTP server accessible- the non-preferred NTP server has transitioned from the
inaccessible state to the accessible state
26 Non-preferred NTP server stratum error - the non-preferred NTP server has reported a stratum level of
0 or an invalid stratum level.
27 Non-preferred NTP server stratum valid - the non-preferred NTP server has now reported a valid
stratum level.
28 Non-preferred NTP server reference identifier (REFID) change - the REFID for the non-preferred NTP
server has changed.
81 Switch to non-preferred Pulse Per Second (PPS) port - the STP facility has switched to the PPS port
specified as the non preferred PPS port. This alert is sent by both the active and inactive stratum-1
servers.
82 Switch to preferred PPS port - the STP facility has switched to the PPS port specified as the preferred
PPS port. This alert is sent by both the active and inactive stratum-1 servers.
83 PRT source ID change - the PRT source ID for the CTN has changed. The alert is sent by all servers
when the PRT source ID for the CTN changes.
84 No PPS Signal - the STP facility no longer has access to a PPS signal.
System action: The system continues processing.
Operator response: Notify the System Programmer. The same event might occur on all images in the Coordinated
Timing Network (CTN).
System programmer response: Based upon the alert code from the message, determine what condition change
caused the message. If appropriate to your installation, correct the condition. For more details on the alert code

646 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA035I • IEA040W

conditions, see Server Time Protocol Implementation guide, SG24-7281.

Source: Timer supervisor
Detecting Module: IEATEEIH
Routing Code: 10
Descriptor Code: 4

IEA035I EXTERNAL INTERRUPT KEY IS NO LONGER SUPPORTED

Explanation: The external interrupt key was pressed but the key is no longer supported by z/OS.
System action: The key is ignored.
Operator response: None.
System programmer response: None.
Source: Supervisor
Detecting Module: IEAVEEXT
Routing Code: 2,10
Descriptor Code: 4

IEA039I SLIP TRAP ID=xxxx REMOTE ACTION WAS NOT PERFORMED.

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.
In the message text:
ID=xxxx
The SLIP trap identifier specified on the SLIP command.
System action: The system performs the local SVCD or SYNCSVCD action, but not the remote action 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
Routing Code: 10
Descriptor Code: 4

IEA040W 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.
In the message text:
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:

Chapter 21. IEA messages 647

IEA041I • IEA042I

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.
Source: SLIP
Detecting Module: IEAVTSL5
Routing Code: 1
Descriptor Code: 1

IEA041I SDUMP SCHEDULED FOR REMOTE SLIP TRAP ID=xxxx FROM SYSTEM ssssssss
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.
In the message text:
ID=xxxx
The SLIP trap identifier specified on the SLIP command.
ssssssss
The system on which the SLIP trap matched.
System action: This system schedules an SVC dump and continues processing.
Source: SLIP
Detecting Module: IEAVTSL5
Routing Code: 10
Descriptor Code: 4

IEA042I SDUMP NOT SCHEDULED FOR REMOTE SLIP TRAP ID=xxxx FROM SYSTEM ssssssss. REASON
- text
Explanation: text is one of the following:
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.

In the message text:

ID=xxxx
The SLIP trap identifier specified on the SLIP command.
ssssssss
The system on which the SLIP trap matched.
text
The reason why the system could not write the SVC dump.
System action: The system processes the SLIP command, but the system does not write the requested SVC dump.
System programmer response: Determine why the remote system could not write an SVC dump. If the problem
cannot be corrected, search problem reporting data bases for a fix for the problem. If no fix exists, notify the IBM
Support Center.
Source: SLIP

648 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA043I • IEA045I

Detecting Module: IEAVTSL5

Routing Code: 10
Descriptor Code: 4

IEA043I 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.
In the message text:
xxxxxxxx
The amount of storage, in megabytes, specified on the MAXSPACE parameter of the CHNGDUMP operator
command at the time the limit was reached.
System action: SVC dump ends the capture of the current dump. This dump is written out to a dump data set, but
it is 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
Routing Code: 2
Descriptor Code: 4

IEA044E DUMPING SERVICES FUNCTION IS UNAVAILABLE

Explanation: SVC DUMP processing is hung. No further dumping services are available.
System action: A TDUMP is taken of the DUMPSRV address space. It includes system data
SDATA(Nuc,CSA,LPA,RGN,TRT,GRSQ,SQA) and DUMPSRV data spaces that might contain captured SVC Dumps.
These captured dumps can be extracted from the TDUMP with an IPCS COPYDUMP command. Message “IEA822I”
on page 830 is issued to the system operator to indicate that complete or partial TDUMP was written to the TDUMP
data sets if the request of TDUMP was successful. Message “IEA820I” on page 828 is issued to the system operator to
indicate that the TDUMP was requested but not taken if the TDUMP processing was not successful.
Operator response: None.
System programmer response: Determine where the TDUMP has been written to from message “IEA822I” on page
830. Use the TDUMP to diagnose the hung SDUMP problems or provide the TDUMP to IBM. Extract any capture
dumps from the TDUMP using the IPCS COPYDUMP command. Issue CANCEL DUMPSRV to recycle the dumping
services.
Source: SVC dump
Detecting Module: IEAVAD00, IEAVTSDX
Routing Code: 2, 10
Descriptor Code: 3

IEA045I AN SVC DUMP HAS STARTED AT TIME=hh:mm:ss DATE=mm/dd/yyyy FOR ASIDS(xx[,xx,...,xx])

ERRORID=SEQyyyyyy CPUzz ASIDasid TIMEhh:mm:ss.t
QUIESCE=YES|NO
Explanation: An SVC dump has been started. There might be some impact to the system while the dump is
processing.

Chapter 21. IEA messages 649

IEA046E

In the message text:

TIME=hh:mm:ss
The time when the SVC dump started.
DATE=mm/dd/yyyy
The date when the SVC dump started.
ASIDS(xx[,xx,...,xx])
The ASIDs of the address spaces that the SVC dump was requested. If there is only one address space that was
requested, only one ASID is shown.
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).
QUIESCE=YES|NO
Whether the system was set to be non-dispatchable.
YES
The system was set to be non-dispatchable.
NO The system was set to be dispatchable.
System action: None.
Operator response: None.
System programmer response: None.
Source: SVC dump
Detecting Module: IEAVTSDS
Routing Code: 2
Descriptor Code: 12

IEA046E SVC DUMP SERVICE PARTIALLY UNAVAILABLE. REASON CODE=reason-code

Explanation: Some SVC dump processing function is unavailable.
In the message text:
REASON CODE=reason-code
The reason code, which is the following:
04 SVC dump post-dump exit processing is unavailable, therefore exits in IEAVTSEL will not be called.
System action: The remaining functions of SVC dump processing should be operational.
Operator response: None.
System programmer response: For REASON=04, an error occurred that involved IEAVTDSV processing. For
problem determination purposes, check the system logs, and look for LOGREC records, and possible SVC dumps,
around the time of the message. If the error was not due to SVC dump processing, full functioning is restored by
recycling the DUMPSRV address space.
Source: SVC dump
Detecting Module: IEAVTDSV

650 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA050I • IEA059E

Routing Code: 2, 10
Descriptor Code: 3

IEA050I DUPLEX IS AN OBSOLETE KEYWORD. DUPLEXING NO LONGER SUPPORTED.

Explanation: Duplexing of PLPA and Common is no longer supported.
System action: The system continues processing. However, the DUPLEX keyword is ignored, and no duplexing
occurs.
Operator response: None.
Source: Auxiliary Storage Manager
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 12

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.
System action: The system continues processing. However, the swap parameter is ignored.
Operator response: None.
Source: Auxiliary Storage Manager
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 12

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.
System action: The system continues processing. However, the SWAP keyword is ignored, and the system will
continue without dedicated swap data sets.
Operator response: None.
Source: Auxiliary Storage Manager
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 12

IEA059E ASID SHORTAGE HAS BEEN DETECTED

Explanation: The number of ASIDs available for allocation to new address spaces has dropped below 5% of the
value specified in IEASYSxx with the MAXUSER specification.
System action: The first time MVS issues message IEA059E for the current IPL, MVS takes a system dump to aid in
diagnosing the situation. System Completion code AC7 with reason code 001B0000 is issued to permit MVS to take
the system dump.
Operator response: None.
System programmer response: Determine if the shortage is due to too many address spaces being started,
MAXUSER being specified too low, or ASIDs becoming non-reusable for cross-memory integrity reasons.
Source: Cross-memory services

Chapter 21. IEA messages 651

IEA060I • IEA062I

Detecting Module: IEAVXSRM

Routing Code: 1,10
Descriptor Code: 11

IEA060I ASID SHORTAGE HAS BEEN RELIEVED

Explanation: The number of ASIDs available for allocation to new address spaces has risen above 10% of the value
specified in IEASYSxx with MAXUSER specification.
System action: Message IEA059E is deleted.
Operator response: None.
System programmer response: None.
Source: Cross-memory services
Detecting Module: IEAVXSRM
Routing Code: 1,10
Descriptor Code: None.

IEA061E REPLACEMENT ASID SHORTAGE HAS BEEN DETECTED

Explanation: The number of ASIDs available for replacing non-reusable address spaces has dropped below 5% of
the value specified in IEASYSxx with the RSVNONR specification.
System action: None.
Operator response: None.
System programmer response: Determine if the shortage is due to RSVNONR being specified too low or an
application problem that is causing a large number of address spaces to become non-reusable.
Examine the ASVTNONR and ASVTANR field (representing the total and currently available RSVNONR entries) to
determine the depletion rate of RSVNONR entries. To calculate and verify the average ASID depletion rate, the
ASVTANR value should be collected multiple times over a period of several weeks before this message is issued.
When you know the historical average depletion rate and the expected interval between IPLs, the result +5% is the
minimum RSVNONR value that should be specified at IPL. For details about ASVT, see z/OS MVS Data Areas in
z/OS Internet Library at http://www.ibm.com/systems/z/os/zos/bkserv/.
If the depletion rate unexpectedly exceeds the average rate and causes this message to be displayed, an application
problem may exist. The cause of the change in the depletion rate should be determined.
For more information about RSVNONR, see z/OS MVS Initialization and Tuning Reference.
Source: Cross-memory services
Detecting Module: IEAVXSRM
Routing Code: 1,10
Descriptor Code: 11

IEA062I REPLACEMENT ASID SHORTAGE HAS BEEN RELIEVED

Explanation: The number of ASIDs available for replacing non-reusable address spaces has risen above 10% of the
value specified in IEASYSxx with the RSVNONR specification.
System action: Message IEA061E is deleted.
Operator response: None.
System programmer response: None.
Source: Cross-memory services
Detecting Module: IEAVXSRM

652 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA063E • IEA066I

Routing Code: 1,10

Descriptor Code: None.

IEA063E SYSTEM LX SHORTAGE HAS BEEN DETECTED

Explanation: The number of system LXs available for allocation has dropped below 15% of the value specified in
the IEASYSxx with the NSYSLX specification.
System action: None.
Operator response: None.
System programmer response: Determine if the number of defined system LXs is too small, or if an application
problem is causing system LXs to be orphaned. There is a limit of 2048 LXs, which includes both system and
non-system LXs. Increasing the number of system LXs will decrease the number of non-system LXs that are available,
and can cause message IEA065E to occur.
Source: Cross-memory services
Detecting Module: IEAVXSRM
Routing Code: 1,10
Descriptor Code: 11

IEA065E NON-SYSTEM LX SHORTAGE HAS BEEN DETECTED

Explanation: The number of non-system LXs available for allocation has dropped below 15% of the number
available for allocation. The number available for allocation is 2048 minus the value specified in IEASYSxx with the
NSYSLX specification and any LXs reserved by IBM for internal use.
System action: None.
Operator response: None.
System programmer response: Determine if the number of non-system LXs is too small, or if an application
problem is causing non-system LXs to be orphaned. There is a limit of 2048 LXs, which includes both system and
non-system LXs. Decreasing the number of system LXs will increase the number of non-system LXs that is available,
but may cause message IEA063E to occur.
Source: Cross-memory services
Detecting Module: IEAVXSRM
Routing Code: 1,10
Descriptor Code: 11

IEA066I NON-SYSTEM LX SHORTAGE HAS BEEN RELIEVED

Explanation: The number of non-system LXs available for reallocation has risen above 30% of the number available
for allocation.
System action: Message IEA065E is deleted.
Operator response: None.
System programmer response: None.
Source: Cross-memory services
Detecting Module: IEAVXSRM
Routing Code: 1,10
Descriptor Code: None.

Chapter 21. IEA messages 653

IEA067I • IEA072E

IEA067I CROSS-MEMORY RESOURCE MONITORING HAS FAILED

Explanation: A fatal error occurred in the cross-memory monitoring task. Cross-memory resource monitoring will
no longer occur until the system is re-IPLed.
System action: None.
Operator response: None.
System programmer response: None.
Source: Cross-memory services
Detecting Module: IEAVXSRM
Routing Code: 1,10
Descriptor Code: None.

IEA070E SYSTEM BIG LX SHORTAGE HAS BEEN DETECTED

Explanation: The system has detected a shortage of system extended LXs.
System action:
Operator response: Notify the system programmer.
System programmer response: Determine if the number of defined system extended LXs is too small, or if an
application problem is causing system LXs to be orphaned. There is a limit of 30,720 extended LXs, which includes
both system and non-system extended LXs. Increasing the number of system extended LXs will decrease the number
of non-system extended LXs that is available, and might cause message IEA072E to occur.
Source: Cross-memory services
Detecting Module: IEAVXSRM
Routing Code: 1,10
Descriptor Code: 11

IEA071I SYSTEM BIG LX SHORTAGE HAS BEEN RELIEVED

Explanation: The shortage of system extended LXs has been relieved.
System action:
Operator response: Notify the system programmer.
System programmer response: None.
Source: Cross-memory services
Detecting Module: IEAVXSRM
Routing Code: 1,10
Descriptor Code: None.

IEA072E NON-SYSTEM BIG LX SHORTAGE HAS BEEN DETECTED

Explanation: The system has detected a shortage of non-system extended LXs.
System action:
Operator response: Notify the system programmer.
System programmer response: Determine if the number of non-system extended LXs is too small, or if an
application problem is causing non-system extended LXs to be orphaned. There is a limit of 30,720 extended LXs,
which includes both system and non-system extended LXs. Decreasing the number of system extended LXs will
increase the number of non-system extended LXs that are available, but might cause message IEA070E to occur.
Source: Cross-memory services

654 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA073I • IEA074I

Detecting Module: IEAVXSRM

Routing Code: 1,10
Descriptor Code: 11

IEA073I NON-SYSTEM BIG LX SHORTAGE HAS BEEN RELIEVED

Explanation: The shortage of non-system extended LXs has been relieved.
System action:
Operator response: Notify the system programmer.
System programmer response: None.
Source: Cross-memory services
Detecting Module: IEAVXSRM
Routing Code: 1,10
Descriptor Code: None.

| IEA074I STORAGE CONTROLLER HEALTH,MC=cc,TOKEN=dddd,SSID=xxxx,

| DEVICE NED=tttt.mmm.ggg.pp.ssssssssssss.uuuu ,
| text
| Explanation: The storage control has detected a health condition that affects one or more devices.
| In the message text:
| MC=cc The message code indicating the health of the storage controller. cc is one of the following:
| 00-3F Moderate severity
| 40-BF Serious severity
| C0-FF Acute severity
| TOKEN=dddd
| The unique value for this logical storage subsystem (LSS).
| Note that the message issued for each LSS contains the same token.
| SSID=xxxx
| SSID for this subsystem.
| DEVICE NED=tttt.mmm.ggg.pp.ssssssssssssuuuu
| Node element descriptor from the device:
| tttt Machine type
| mmm Model
| ggg Manufacturer
| pp Plant of manufacture
| ssssssssssss
| Box sequence number
| uuuu Identifies one of the devices in the storage control that is affected. This value is the concatenation of
| LSS and CCA for the reporting device.
| text Displays the reason for the message code, which is one of the following:
| DEVICE PREEMPTIVE RECONSTRUCT MODE
| Corresponds to moderate severity message code MC = 01
| RAID ARRAY REBUILD IN PROGRESS
| Corresponds to moderate severity message code MC = 02

Chapter 21. IEA messages 655

 IEA075I

| RAID ARRAY REBUILD COMPLETE

| Corresponds to moderate severity message code MC = 03
| SERVER OFFLINE DUE TO ERROR
| Corresponds to moderate severity message code MC = 04
| SERVER OFFLINE DUE TO SERVICE
| Corresponds to moderate severity message code MC = 05
| DUAL SERVERS ONLINE
| Corresponds to moderate severity message code MC = 06
| DEVICE ADAPTER FENCED
| Corresponds to moderate severity message code MC = 07
| DEVICE ADAPTER UNFENCED
| Corresponds to moderate severity message code MC = 08
| PPRC PATH DEGRADED
| Corresponds to moderate severity message code MC = 10
| PRRC PATH NO LONGER DEGRADED
| Corresponds to moderate severity message code MC = 11
| PPRC SECONDARY CONTROLLER RECOVERY ACTION
| Corresponds to moderate severity message code MC = 20
| IO OPERATIONS TIMING OUT ON PPRC SECONDARY CONTROLLER
| Corresponds to serious severity message code MC = 40
| DATA ERROR DURING MEDIA SCRUB
| Corresponds to serious severity message code MC = 41
| SERVER MULTIPLE WARMSTARTS
| Corresponds to serious severity message code MC = 80
| PINNED NONRETRYABLE ERROR ON DEVICE
| Corresponds to acutes severity message code MC = C0
| ONE OR MORE DEVICES UNAVAILABLE DUE TO NVS HARDWARE FAILURE
| Corresponds to acute severity message code MC = C1
| ONE OR MORE DEVICES UNAVAILABLE DUE TO NVS HARDWARE OFFLINE
| Corresponds to acute severity message code MC = C2
| UNKNOWN
| For any message code not defined above.
| System action: The system logs a symptom record in the LOGREC data set and continues processing.
| Operator response: None.
| System programmer response: None.
| Source: DASD device initialization/re-initialization
| Detecting Module: IECCINIT
| Routing Code: 128,64
| Descriptor Code: 1

| IEA075I PPRC SUMMARY,SSID=xxxx,

| DEVICE NED=tttt.mmm.ggg.pp.ssssssssssss.uuuu,
| SUSPENDED=aaa,PPRC=bbb,TOTAL=ccc,
| {REASON=SUSPEND(rr),text | REASON=UNKNOWN(rr)}
| Explanation: This message displays summarizes the PPRC state for all the devices in a control unit.
| In the message text:

656 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA080D

| SSID=xxxx
| SSID for this subsystem.
| DEVICE NED=tttt.mmm.ggg.pp.ssssssssssss.uuuu
| Node element descriptor from the device:
| tttt Machine type
| mmm Model
| ggg Manufacturer
| pp Plant of manufacture
| ssssssssssss
| Box sequence number
| uuuu Unique identifier for device with the same serial number. This value is the concatenation of device
| logical storage subsystem (LSS) and device CCA. The device CCA reported is one of potentially
| multiple devices with a PPRC state transition.
| SUSPENDED=aaa
| The number of devices that are PPRC suspended devices in the LSS.
| PPRC=bbb
| The number of devices in a PPRC relationship in the LSS.
| REASON=SUSPEND(rr)
| Reason code for PPRC state transition. The accompanying text explains the reason code.
| text Displays the reason for the suspend, which is one of the following:
| v SUSPENDED, HOST COMMAND TO PRIMARY [rr = 03]
| v SUSPENDED, HOST COMMAND TO SECONDARY [rr = 04]
| v SUSPENDED, PRIMARY UPDATE SECONDARY DEVICE STATUS COMMAND [rr = 05]
| v SUSPENDED, CU INTERNAL CONDITIONS [rr = 06]
| v SUSPENDED, SECONDARY TRANSITION TO SIMPLEX STATE [rr = 07]
| v SUSPENDED, SECONDARY FAILURE INTERNAL CONDITIONS [rr = 08]
| v SUSPENDED, CU IML OR POWER RESTORED [rr = 09]
| v SUSPENDED, FREEZE COMMAND [rr = 0A]
| v SUSPENDED, EST FC [rr = 0C]
| REASON=UNKNOWN(rr)
| Reason code not recognized.
| System action: The system continues processing.
| Operator response: This message is intended for use by automation programs that monitor operator messages.
| Actions can be attempted by the operator, but an automation program is recommended.
| System programmer response: None.
| Source: DASD device initialization/re-initialization
| Detecting Module: IECCINIT
| Routing Code: 128,64
| Descriptor Code: 1

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.
System action: The system waits for the operator to respond. The system issues this message on the nucleus
initialization program (NIP) console.
Operator response: Reply with one of the following responses:

Chapter 21. IEA messages 657

IEA081I • IEA086I

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)
Routing Code: 1
Descriptor Code: 2

IEA081I ERROR - IECIOSxx RECORD nnnn I/O ERROR

Explanation: During system initialization, the system could not read a record from the IECIOSxx parmlib member.
This message appears on the nucleus initialization program (NIP) console. In the message text:
IECIOSxx
The parmlib member, with the suffix xx.
nnnn 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.
Source: Input/output supervisor (IOS)
Routing Code: 2
Descriptor Code: 12

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
v An incomplete I/O configuration
v Both an incomplete nucleus and an incomplete I/O configuration

In the message text:

entrypt The entry point address.
System action: The system enters nonrestartable disabled wait state X'035'.
Operator response: See the operator response for wait state X'035'.
System programmer response: See the system programmer response for wait state X'035'.
Source: Input/output supervisor (IOS)
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.

658 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA086W • IEA087W

In the message text:

memname
The missing member.
System action: The IPL proceeds.
Operator response: Notify the system programmer.
System programmer response: Either provide the missing member or update NUCLSTxx.
Source: System initialization (IPL/NIP)
Detecting Module: IEAIPL41
Routing Code: -
Descriptor Code: -

IEA086W memname NOT FOUND IN SYS1.NUCLEUS

Explanation: The initial program load (IPL) program was unable to locate a necessary member in the
SYS1.NUCLEUS data set.
In the message text:
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.
System action: The system enters 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.
Operator response: See the operator response for wait state X'055'
System programmer response: See the system programmer response for wait state X'055'.
Source: System initialization (IPL/NIP)
Detecting Module: IEAIPL02

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.)
In the message text:
entrypt The duplicate entry point name
mod1 The first module where the duplicate entry point name appears.
mod2 The second module where the duplicate entry point name appears.

This message accompanies wait state code X'025'.

System action: The system enters non-restartable 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.
Operator response: See the operator response for wait state code X'025'.
System programmer response: See the system programmer response for wait state X'025'.
Source: System initialization (IPL/NIP)
Detecting Module: IEAIPL41

Chapter 21. IEA messages 659

IEA088W • IEA091I

IEA088W NUCLEUS REQUIRES MORE STORAGE BELOW 16MB THAN IS AVAILABLE

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.)
System action: The system enters non-restartable wait state X'071'.
This message appears in the IPL WTO buffer.
System programmer response: See the system programmer response for wait state X'071'.
Source: Initial program load (IPL)
Detecting Module: IEAIPL41

IEA089W 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.
In the message text:
memname
The member of SYS1.NUCLEUS in error.
System action: The system enters non-restartable 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.
Operator response: See the operator response for wait state X'054'.
System programmer response: See the system programmer response for wait state X'054'.
Source: System initialization (IPL/NIP)
Detecting Module: IEAIPL02

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.
In the message text:
irimname
The IRIM that issued the failed instruction.
System action: The system enters non-restartable 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.
Operator response: See the operator response for wait state X'074'.
System programmer response: See the operator response for wait state X'074'.
Source: System initialization (IPL/NIP)
Detecting Module: IEAIPL02

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.
In the message text:
x The identifier for the nucleus module, IEANUC0x
System action: The initial program load (IPL) program loads IEANUC0x into the DAT-on nucleus region.

660 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA092I • IEA099A

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.
Source: System initialization (IPL/NIP)
Detecting Module: IEAIPL41

IEA092I WARNING: UNRESOLVED EXTERNAL REFERENCE symbol IN MODULE modname

Explanation: The initial program load (IPL) program 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.
In the message text:
symbol The unresolved external reference
modname
The nucleus module
System action: The IPL proceeds, but the success of the IPL or subsequent processing is unpredictable.
Operator response: Notify the system programmer.
System programmer response: If the module is IEANUC0x, link edit it again to determine which CSECT contains
the unresolved external reference.
If IBM supplied the module, search problem reporting data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center.
Source: System initialization (IPL/NIP)
Detecting Module: IEAIPL02

IEA093I MODULE modname CONTAINS UNRESOLVED WEAK EXTERNAL REFERENCE refname

Explanation: The initial program load (IPL) program 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.
In the message text:
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.
Source: System initialization (IPL/NIP)
Detecting Module: IEAIPL02

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.
System action: The system continues processing.
Operator response: Notify the system programmer.
System programmer response: Do one of the following:
v If the program is in a WTO loop, correct the program.
v Increase the value of the MLIM field in the CONSOLxx parmlib member.
v Automate the message to slow down or cancel the offending address space.
ATTENTION: Use caution when cancelling the address space because data can be lost.

Chapter 21. IEA messages 661

IEA100I • IEA101A

Source: Communications task (COMMTASK)

Detecting Module: IEAVH600
Routing Code: 2
Descriptor Code: 11

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.
In the message text:
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.
005 Unit recovered.
006 Control Link A operational.
007 Control Link B operational.
008 Communication established with console.
009 Communication established with standby console.
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 action: Processing continues.
Source: Timer supervision
Detecting Module: IEATEEIH
IEATESMR
Routing Code: Note 13
Descriptor Code: 4

IEA101A SPECIFY SYSTEM PARAMETERS FOR xx...x

Explanation: This message is issued during system initialization to allow the operator to change certain system
parameters.
In the message text:
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).
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 z/OS MVS System Commands.

662 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA102W • IEA111D

System programmer response: Tell the operator which responses to enter.

Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPC4
Routing Code: -
Descriptor Code: 12

IEA102W OPERATOR PROMPT NOT ALLOWED FOR A SYSPLEX TEST DATESOURCE LPAR
Explanation: In the CLOCKxx parmlib member, OPERATOR PROMPT is specified. This is not a valid specification
when IPLing a sysplex datesource LPAR.
System action: The system enters a non-restartable wait state.
Operator response: Notify the system programmer.
System programmer response: Modify the CLOCKxx parmlib member for the sysplex datesource LPAR to specify
OPERATOR NOPROMPT.
Source: Timer supervision
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
System programmer response: Make sure that the parameter was not restricted from operator changes in the
IEASYSxx parmlib member (OPI=NO option).
If IEASYSxx is correct and if the problem persists, search problem reporting data bases for a fix for the problem. If no
fix exists, contact the IBM Support Center. Provide a stand-alone dump.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNP03
Routing Code: -
Descriptor Code: -

IEA111D SPECIFY SUBCHANNEL SET TO BE USED FOR DEVICES THAT ARE ACCESSIBLE FROM
MULTIPLE SUBCHANNEL SETS – REPLY SCHSET=X
Explanation: During IPL the system needs to dynamically determine for PPRC pairs with the same device number
whether the subchannel in the primary subchannel set should be connected to the UCB or the subchannel in an
alternate subchannel set should be connected. The actions performed by IOS for a PPRC pair with the same device
number depend on the state of the device with respect to the copy services relationships and the SCHSET parameter
specified in LOADxx. If the parameter wasn’t specified in LOADxx or is not valid, and at least one PPRC pair exists
with the same device number, the operator is required to make a choice.
System action: Wait for a response.
Operator response: “SCHSET=n”, where n must be a subchannel set configured to the system
System programmer response: None.
Source: Input/Output Supervisor (IOS)
Detecting Module: IEAVNP02
Routing Code: 1

Chapter 21. IEA messages 663

IEA116A • IEA121I

Descriptor Code: 2

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.
System action: The system prompts the operator for a reply.
Operator response: Continue the reply to message IEA101A. Begin the continuation with REPLY 00.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPC4
Routing Code: -
Descriptor Code: -

IEA120D DEVICE dev VOLID NOT READ. REPLY ‘WAIT’ FOR I/O COMPLETION OR ‘CONT’ TO
CONTINUE WITH DEVICE OFFLINE
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.
v A hardware malfunction could be causing the device to appear busy.

In the message text:

dev
The device number.
System action: The system waits for the operator to reply.
Operator response: Contact the system programmer. 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.
System programmer response: Determine the 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)
Detecting Module: IEAVNP02
Routing Code: 1
Descriptor Code: 2

IEA121I UNABLE TO OBTAIN CHANNEL-SUBSYSTEM INFORMATION DUE TO A BUSY CONDITION.

IPL CONTINUES.
Explanation: During system initialization, the system returned a busy condition.
System action: System initialization continues.
Operator response: Contact hardware support.

664 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA122I • IEA125I

Source: Input/output supervisor (IOS)

IEA122I ERROR OBTAINING CHANNEL SUBSYSTEM INFORMATION DUE TO HARDWARE FAILURE.

IPL CONTINUES.
Explanation: During system initialization, the system tried to issue the channel-subsystem information command. A
hardware failure occurred.
System action: System initialization continues.
Operator response: Contact hardware support.
Source: Input/output supervisor (IOS)

IEA123I CONSOLE DELAYED SVC PROCESSING RESUMED. RESTART SUCCESSFUL

Explanation: The system previously issued message IEA554I or IEA555E. The system restart was successful after the
problems indicated by message IEA554I or IEA555E were resolved.
System action: The system continues processing.
Source: Communications task (COMMTASK)
Detecting Module: IEAVM613
Routing Code: -
Descriptor Code: 4

IEA124I SYSTEM CONSOLE consname QUEUING RESUMED

Explanation: After the system suspended message queuing to a console, the system resumed message queuing to
that console.
In the message text:
consname
The system console name.
System action: The system continues processing.
Source: Communications task (COMMTASK)
Detecting Module: IEAVM605
Routing Code: -
Descriptor Code: 12.

IEA125I SYSTEM CONSOLE consname QUEUING SUSPENDED, ERROR CODE = code

Explanation: The system suspended message queuing to the specified system console.
In the message text:
consname
The system console name.
code The error code, which is one of the following:
Code Explanation
8001 The service processor logical console is not available for output processing.
8002 The message queue limit for the system console was reached.
8003 The system found an internal queue error.
System action: Depending on the error code, one of the following:
Code System Action

Chapter 21. IEA messages 665

IEA126I • IEA127I

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.
Operator response: Notify the system programmer.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Source: Communications task (COMMTASK)
Detecting Module: IEAVM605
Routing Code: -
Descriptor Code: 12

IEA126I THE SYSTEM CONSOLE QUEUE IS 80% FULL

Explanation: The buffer that holds the messages on the system console queue is 80% full.
System action: The system continues processing.
Operator response: If desired, do one or more of the following:
v Reply to outstanding messages.
v Cancel any jobs that are currently issuing messages.
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.
Source: Communications task (COMMTASK)
Detecting Module: IEAVM605
Routing Code: -
Descriptor Code: 12

IEA127I SYSTEM CONSOLE NOT ACCEPTING [PRIORITY] OPERATOR INPUT

Explanation: The system could not initialize the system console input listener exit routine.
In the message text:
PRIORITY
The system is not accepting operator input from the screen that accepts priority commands.
System action: The system console does not process any other commands.
Operator response: Notify the system programmer.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN701
Routing Code: 2
Descriptor Code: 12

666 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA128I • IEA134I

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.
Operator response: Notify the system programmer.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN701
Routing Code: 2
Descriptor Code: 12

IEA129I MASTER CONSOLE REQUIRED.

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 CON is not specified on the system parameter.
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.
Source: Communications task (COMMTASK)
Detecting Module: IEAVNPA1
Routing Code: -
Descriptor Code: 12

IEA133E THE TRACE ADDRESS SPACE HAS TERMINATED

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.
Operator response: Enter a TRACE ST command to restart system tracing.
System programmer response: If the error recurs, 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 error record and the SVC dump, if
available.
Source: System trace
Detecting Module: IEAVETRM
Routing Code: 1
Descriptor Code: 11

IEA134I TRACE ERROR, REISSUE TRACE COMMAND IF STATUS NOT AS REQUESTED

Explanation: While processing a TRACE ST command, the system detected an error.
System action: The system continues processing. 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.

Chapter 21. IEA messages 667

IEA135I • IEA136I

System programmer response: If the error recurs, 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 error record and the SVC dump, if
available.
Source: System trace
Detecting Module: IEECB925
Routing Code: 2
Descriptor Code: 5

IEA135I REQUESTED TRACE BUFFER SIZE PER PROCESSOR EXCEEDS MAX OF scaled_value
Explanation: The storage requested by command TRACE ST, nnnK/nnnM/nG for the system trace buffer size of
each processor exceeded the maximum allowed.
In the message text:
scaled_value
The maximum system trace buffer size that was allowed at the time the command was issued. It is a
decimal number followed by a scaling suffix of M which indicates that the value is the decimal number
multiplied by 1048576.

Note: The value provided was the value available as of the time of the message but might not be available
when a subsequent command is issued.
System action: MVS cannot process the command.
Operator response: Enter the command again with smaller buffer size which is within the allowable limit.
Source: System Trace
Detecting Module: IEECB925
Routing Code: *
Descriptor Code: 5

IEA136I REQUESTED TRACE BUFFER SIZE EXCEEDS MAX OF scaled_value

Explanation: The storage requested by command TRACE ST,BUFSIZ= for the system trace buffer size exceeded the
maximum allowed.
In the message text:
scaled_value
The maximum system trace buffer size that was allowed at the time the command was issued. It is a
decimal number followed by a scaling suffix of M which indicates that the value is the decimal number
multiplied by 1048576.

Note: The value provided was the value available as of the time of the message but might not be available
when a subsequent command is issued.
System action: MVS cannot process the command.
Operator response: Enter the command again with smaller buffer size which is within the allowable limit.
Source: System Trace
Detecting Module: IEECB925
Routing Code: *
Descriptor Code: 5

668 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA139E • IEA145E

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'.
System programmer response: Do the following:
v Obtain the SVC dump for this message.
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'.
v If the message is not accompanied by abend X'053', search problem reporting data bases for a fix for the problem.
If no fix exists, contact the IBM Support Center. Provide the dump.
Source: Program Call/authorization (PC/AUTH)
Detecting Module: IEAVXPCR
Routing Code: 1
Descriptor Code: 11

IEA140W 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'.
Operator response: Notify the system programmer.
System programmer response: See the system programmer response for wait state X'0E3'.
Source: Virtual storage manager (VSM)
Detecting Module: IEAVNP08
Routing Code: Note 9
Descriptor Code: -

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 continues processing.
Operator response: If console sysplex integrity is critical, reIPL the system that issued the message to rejoin the
sysplex. Otherwise, none.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Source: Communications task (COMMTASK)
Detecting Module: IEAVR601
Routing Code: 1,2
Descriptor Code: 11

Chapter 21. IEA messages 669

IEA152I • 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.
Operator response: See the operator response for the accompanying message.
Source: Communications task (COMMTASK)
Detecting Module: IEAVNPA1

IEA153I HARDCPY CONSOLE UNAVAILABLE

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.
Operator response: See the operator response for the accompanying message.
Source: Communications task (COMMTASK)
Detecting Module: IEAVNPA1

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.
In the message text:
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.
Operator response: Notify the system programmer.
System programmer response: Before the next system initialization, check to see if the problem 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
Routing Code: Note 9
Descriptor Code: 12

IEA163E 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 action: System initialization continues.
Operator response: Notify the system programmer.
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.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM1
Routing Code: Note 9

670 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA164E • IEA167I

Descriptor Code: 12

IEA164E SMCS IS INOPERATIVE. CONTINUING WITHOUT SMCS

Explanation: The SMCS task could not be attached, or a non-recoverable SMCS error occurred.
System action: SMCS is not available during this IPL but it might be available on other systems in the sysplex.
Operator response: Notify your system programmer.
System programmer response: Search the problem reporting databases for a fix for this problem. If no fix is
available, contact the IBM Support Center.
Source: Communications Task
Detecting Module: IEAVN701
Routing Code: 2,10
Descriptor Code: 11

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.

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.
In the message text:
VATLSTxx
The parmlib member, with a suffix of xx.
volser The volume serial number.
devicetype
The type of device.
System action: The system continues processing with 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
Routing Code: 2
Descriptor Code: 4

IEA167I VATLSTxx: VATDEF charstring IGNORED. text

Explanation: text is one of the following:
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.
System programmer response: Correct the character string on the VATDEF statement.

Chapter 21. IEA messages 671

IEA168I • IEA170I

Source: Allocation/unallocation
Detecting Module: IEAVAP01
Routing Code: 2
Descriptor Code: 4.

IEA168I VATLSTxx: {VATLST|SYSTEM} DEFAULT USE ATTRIBUTE OF {PUBLIC|PRIVATE|STORAGE}

{USED.|ASSUMED.}
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:
VATLSTxx
The parmlib member, with a suffix of xx.
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.
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.
Source: Allocation/unallocation
Detecting Module: IEAVAP01
Routing Code: 2
Descriptor Code: 4

IEA169I VATLSTxx: DUPLICATE {SYSUSE|IPLUSE} SPECIFICATION IGNORED.

Explanation: During processing of the VATLSTxx parmlib member, the system found more than one SYSUSE or
IPLUSE keyword. In the message text:
VATLSTxx
The parmlib member, with a suffix of xx.
System action: VATLST processing ignores any additional SYSUSE or IPLUSE keywords specified on a VATDEF
statement.
System programmer response: Remove the duplicate SYSUSE or IPLUSE keyword from the VATDEF statement.
Source: Allocation/unallocation
Detecting Module: IEAVAP01
Routing Code: 2
Descriptor Code: 4

IEA170I VATLSTxx: DUPLICATE VATDEF SPECIFICATION IGNORED

Explanation: During processing of the VATLSTxx 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
The parmlib member, with a suffix of xx.
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.
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.

672 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA171I • IEA181I

Source: Allocation/unallocation
Detecting Module: IEAVAP01
Routing Code: 2
Descriptor Code: 4

IEA171I VATLSTxx: MISSING RIGHT PARENTHESIS ON VATDEF STATEMENT.

Explanation: The system issues this message during 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
The parmlib member, with a suffix of xx.
System action: VATLST processes the VATDEF statement and continues on to the next record.
System programmer response: Before the next IPL, add a right parenthesis to the VATDEF statement.
Source: Allocation/unallocation
Detecting Module: IEAVAP01
Routing Code: 2
Descriptor Code: 4

IEA180I USING IBM DEFAULT PFK DEFINITIONS. NO PFK TABLES REQUESTED.

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.
Source: Communications task (COMMTASK)
Detecting Module: IEAVC701
Routing Code: 2,10
Descriptor Code: 4

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.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Source: Communications task (COMMTASK)
Detecting Module: IEAVC701
Routing Code: 2,10
Descriptor Code: 4

Chapter 21. IEA messages 673

IEA182W • IEA186I

IEA182W RECONFIGURATION INITIALIZATION FAILED TO OBTAIN CHANNEL PATH INFORMATION

FROM THE SERVICE PROCESSOR.
Explanation: During reconfiguration initialization, the system requested channel path information, but the service
processor did not return channel path information. This is probably a hardware error.
System action: The system enters non-restartable wait state X'020' The system writes a logrec data set error record
about the failure.
Operator response: Notify the system programmer. ReIPL the system.
System programmer response: See the system programmer response for wait state X'020'.
Source: Reconfiguration
Detecting Module: IEAVNP27
Routing Code: 1,10
Descriptor Code: 1

IEA183W 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.
System action: The system enters non-restartable wait state X'020' The system writes a logrec data set error record
about the failure.
Operator response: Notify the system programmer. ReIPL the system.
System programmer response: See the system programmer response for wait state X'020'.
Source: Reconfiguration
Detecting Module: IEAVNP27
Routing Code: 1,10
Descriptor Code: 1

IEA184W RECONFIGURATION INITIALIZATION FAILED TO OBTAIN THE LENGTH OF THE SIDE

INFORMATION BLOCK
Explanation: During reconfiguration initialization, the system tried to obtain the length of the resource group
information block but failed.
System action: The system enters non-restartable wait state X'020'. The system writes a logrec data set error record
about the failure.
Operator response: Notify the system programmer. ReIPL the system.
System programmer response: See the system programmer response for wait state X'020'.
Source: Reconfiguration
Detecting Module: IEEVORGI
Routing Code: 1,10
Descriptor Code: 1

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.
Operator response: Notify the system programmer.

674 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA187I • IEA189I

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)
Source: Communications task (COMMTASK)
Detecting Module: IEAVNPB1
Routing Code: -
Descriptor Code: 4

IEA187I FORMAT OF THE CON SYSTEM PARAMETER IS NOT VALID.

Explanation: The CON parameter in the IEASYSxx parmlib member or the CON parameter in the reply to message
IEA101A is incorrect.
System action: The system issues message IEA332A and prompts the operator for a reply.
Operator response: See the operator response for message IEA332A.
System programmer response: If necessary update the CON system parameter in the IEASYSxx parmlib member.
Source: Consoles
Detecting Module: IEAVNPA1
Routing Code: -
Descriptor Code: 12

IEA188I CONSOLxx: NO MASTER CONSOLE SPECIFIED.

Explanation: The CONSOLE statement in the CONSOLxx parmlib member did not specify an MCS console with
master authority.
In the message text:
CONSOLxx
The parmlib member, with the suffix xx.
System action: If at least one MCS console is defined in CONSOLxx, the system selects an MCS console to have
master authority. Message IEA191I identifies the console that the system selected. If there are only SMCS consoles
defined in CONSOLxx, then a master authority SMCS console iscome the sysplex master console when it activates.
System programmer response: If there are MCS consoles defined in CONSOLxx, ensure that at least one is defined
with master authority. If only SMCS consoles are used, then a master authority SMCS console (if there is one) is
chosen to be the sysplex master console when the console activates.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN613
Routing Code: 2,10
Descriptor Code: 4

IEA189I CONSOLxx: dev IGNORED. text

Explanation: text is one of the following:
UNIT NOT SUPPORTED.
NO IODEVICE STATEMENT FOR dev.

The system does not support a specified console device.

In the message text:

Chapter 21. IEA messages 675

IEA190I • IEA191I

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.
System programmer response: Ensure that the device number and device type are specified in the IODF and in a
CONSOLE statement in the CONSOLxx parmlib member.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN610
Routing Code: 2,10
Descriptor Code: 4

IEA190I 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
The parmlib member, with a suffix of xx.
dev
The specified console device.
System action: The system issues message IEA191I and continues processing. Message IEA191I identifies the master
console.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN613
Routing Code: 2,10
Descriptor Code: 4

IEA191I CONSOLE dev (consname) text AS MASTER CONSOLE

Explanation: text is one of the following:
DEFINED
SELECTED

This message identifies the master console.

In the message text:

dev
The device number.
consname
The console name.
DEFINED
The CONSOLxx parmlib member defines the console as the master console.
SELECTED
The system selected the console as the master console. In this case, this message follows message IEA188I,
IEA189I, or IEA190I.

676 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA192I • IEA193I

System action: The system continues processing.

Operator response: Enter a VARY command to alter the master console if the current master console is
unacceptable.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN613
Routing Code: 2,10
Descriptor Code: 4

IEA192I CONSOLxx dev ALTERNATE DEFAULTED TO {consname|dev}. REASON=reason-code

Explanation: The system selected an alternate console.
In the message text:
dev
The device number in the CONSOLxx parmlib member.
consname
The default console name.
CONSOLxx
The parmlib member, with the suffix xx.
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.
2 The alternate console is not a valid console. The system uses the master console as the alternate console.
3 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.
4 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.
Operator response: Notify the system programmer.
System programmer response: Specify an alternate console with a CONSOLE statement in the CONSOLxx parmlib
member, if desired.
Source: Communications task (COMMTASK)
Detecting Module: IEAVG607, IEAVN613
Routing Code: 2,10
Descriptor Code: 4

IEA193I CONSOLxx NOT USABLE. text

Explanation: text is one of the following:
NO VALID CONSOLE STATEMENTS FOUND.
I/O ERROR OCCURRED.

The system found an error while processing a CONSOLxx parmlib member.

In the message text:

CONSOLxx
The parmlib member, with a suffix of xx.
NO VALID CONSOLE STATEMENTS FOUND.
No valid console statement is defined in the CONSOLxx parmlib member.

Chapter 21. IEA messages 677

IEA194I • IEA195I

I/O ERROR OCCURRED.

While the system was processing the CONSOLxx parmlib member, an error occurred.
System action: The system issues message CNZ4400D to ask the operator to specify a new CON system parameter.
System programmer response: Before the next system initialization, specify a valid CON parameter in the
CONSOLxx parmlib member.
Source: Communications task (COMMTASK)
Detecting Module: IEAVNPA1
Routing Code: -
Descriptor Code: 12

IEA194I CONSOLxx dev: HARDCOPY DEFAULTED TO SYSLOG. REASON=reason-code

Explanation: The hard-copy console specified in the CONSOLxx parmlib member is not valid.
In the message text:
CONSOLxx
The parmlib member, with a suffix of xx.
dev
The device number.
reason-code
The reason code, which is one of the following:
1 The console is not a specified console. There might not be a CONSOLE statement for the console.
2 The console is not valid.
3 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
continues processing.
System programmer response: Before the next 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.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN615
Routing Code: 2,10
Descriptor Code: 4

IEA195I CONSOLxx LINE lnnum: text

Explanation: text is one of the following:
UNRECOGNIZED STATEMENT TYPE IGNORED.
keywd IGNORED FOR SUBSYSTEM CONSOLE.
CONSOLE STATEMENT IGNORED. REASON=reason-code
ccc CONSOLES DEFINED. STATEMENT IGNORED.
MISPLACED num STATEMENT IGNORED.
SYSTEM ERROR mmmm-nnnn
keyword IGNORED FOR SYSTEM CONSOLE.
keyword IGNORED FOR SMCS CONSOLE.
keyword IGNORED - ONLY VALID FOR SYSCONS.

The system found an error on a statement in a CONSOLxx parmlib member.

In the message text:

678 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA195I

CONSOLxx
The parmlib member, with a suffix of xx.
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. A blank must immediately follow the statement types (INIT,
DEFAULT, HARDCOPY, and CONSOLE).
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.
2 The DEVNUM keyword value was not hexadecimal, did not fall in the range of X'000' to X'FFFF', or the
value was not SUBSYSTEM, SYSCONS, or SMCS.
4 **This reason code was deleted as of MVS/SP 4.2**
5 A CONSOLE statement named a console that was already defined as an extended class (EMCS) console.
6 The DEVNUM keyword specified a device number, but the console was previously defined as a SMCS
console, or the DEVNUM keyword specified a SMCS console, but the console was previously defined
with a device number.
7 Either the console is an MCS or SMCS console with the same name as an existing subsystem console, or
the console is a subsystem console with the same name as an existing MCS or SMCS console.
ccc CONSOLES DEFINED. STATEMENT IGNORED.
In the shared mode of console operation, the system issues this message for each CONSOLE statement it
encounters beyond the 99 console definition maximum for the sysplex. The system ignores consoles defined
beyond the 99th console. In the distributed mode of console operation, the system issues this message for each
CONSOLE statement it encounters beyond the 250 console definition maximum for the system. The system
ignores consoles defined beyond the 250th console. In both cases, the limit applies to the sum of the MCS, SMCS
and subsystem consoles that are defined.
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 AUTOACT, NAME, ROUTCODE,
LEVEL, MONITOR, MSCOPE, and CMDSYS.
keyword IGNORED FOR SMCS CONSOLE.
The specified keyword is not valid for a SMCS console. The keyword is ignored.
keyword IGNORED - ONLY VALID FOR SYSCONS.
The specified keyword is only valid for the system console. The keyword is ignored.
System action: If the message text is SYSTEM ERROR mmmm-nnnn, the system stops processing the CONSOLxx
member and issues message CNZ4400D.
For all other errors, the system continues processing the valid statements in the CONSOLxx parmlib member.

Chapter 21. IEA messages 679

IEA196I

Operator response: If the message text is SYSTEM ERROR mmmm-nnnn, see the operator response for message
CNZ4400D. 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 can be activated and used for console functions until
CONSOLxx members of SYS1.PARMLIB are correct.
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, use the IEARELCN utility to remove one or more console definitions. This allows
systems which subsequently join the sysplex to have a subset of consoles from their CONSOLxx parmlib member to
be defined and available. See z/OS MVS Planning: Operations and z/OS MVS Initialization and Tuning Reference for
details on the 99–console limit for CONSOLxx.
Source: Communications task (COMMTASK)
Detecting Module: CNZI1CDP, IEAVN600, IEAVN601, IEAVN602, IEAVN611, IEAVN612
Routing Code: 2,10
Descriptor Code: 12

IEA196I CONSOLxx stmt-type: text

Explanation: text is one of the following:
UNRECOGNIZED KEYWORD keywd IGNORED.
keywd NOT SPECIFIED FOR THIS CONSOLE.
keywd VALUE IGNORED. REASON=reason-code
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=reason-code
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
keywd REQUIRED FOR CONSOLE

The system found an error while processing a CONSOLE statement in a CONSOLxx parmlib member.

In the message text:

CONSOLxx
The parmlib member, with a suffix of xx.
stmt-type
One of the following:
cccccccc, specifying the console name.
dev, specifying the device number.
CONSOLE
DEFAULT
HARDCOPY
INIT
SUBSYS

680 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA196I

UNRECOGNIZED KEYWORD keywd IGNORED.

The system could not identify a keyword on the CONSOLE statement.
In the message text:
keywd The unidentified keyword.
keywd NOT SPECIFIED FOR THIS CONSOLE.
The keyword, although not required, is recommended for this console.
keywd VALUE IGNORED. REASON=rc
The system found a keyword value that is not valid.
keywd The incorrect keyword.
rc The reason code, which is one of the following:
1 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 console's device type.
2 The FORMAT or XWTR keyword values cannot be specified on a HARDCOPY statement that
does not have the system log (SYSLOG) as HARDCOPY.
3 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 DC command.
4 The specified keyword value differs from the current sysplex value.
5 The value of RMAX exceeds the subsystem limit. The system sets 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.
7 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.
8 The ROUTTIME value cannot be specified on a single system. A value of zero is used.
9 DEVNUM(SYSCONS) was specified, but the system console hardware has not been installed.
10 The LU keyword was specified, but the value was rejected for one of the following reasons:
v Another console definition, either on this system or on another system in the sysplex,
specified the same LU.
v Another console in the sysplex was active at the same LU during IPL of this system.
11 The VTAM APPLID specified was already in use by SMCS on another system in the sysplex.
12 The GENERIC keyword was specified, but a valid APPLID was not specified.
13 The GENERIC keyword was specified, but this system is in XCFLOCAL or MONOPLEX mode.
14 The CONSOLE statement specified LOGON(DEFAULT), but the DEFAULT statement did not
specify the LOGON keyword. The CONSOLE statement is processed using the appropriate
default for the LOGON keyword.
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 The device type specified on an IODEVICE statement is not consistent with the UNIT
specification on the CONSOLE statement.

Chapter 21. IEA messages 681

IEA196I

keywd IGNORED. REASON=reason-code

The system rejected a parameter in the CONSOLxx member.
In the message text:
keywd The rejected keyword.
reason-code
The reason code, which is one of the following:
1 The system ignores the keywords DEL, CON, SEG, RNUM, RTME, AREA, PFKTAB, LOGON,
CMDSYS, and RBUF. One or more of these keywords were specified for a UNIT of PRT.
2 The system ignores the AUTH parameter that was specified for a UNIT of PRT.
3 The AREA specification was not valid because the total out-of-line AREA exceeded the screen
size of the device.
4 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.
INCONSISTENT keywd VALUE IGNORED.
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).
In the message text:
keywd The ignored value.
MISSING RIGHT PARENTHESIS ASSUMED.
A right parenthesis is missing at the end of a statement. The system assumes it is present.
USE(xx) FORCED. REASON=rc
The console's operating mode was changed to maintain consistency with the AUTH, UNIT, or DEVNUM
keyword.
xx The new value of the USE parameter, which indicates the operating mode of the console.
reason-code
The reason code, which is one of 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 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).
3 An operating mode of message stream or status display was specified for a SMCS console. The
system forces USE(FC).
CONSOLE NOT ACTIVATED. RC=reason-code.
The system did not activate the console.
In the message text:
reason-code
The reason code, which is one of the following:
1 A console with the same name already exists in the sysplex and is currently active on another
system.
2 The console that is logically associated with this name was assigned to a system component.
4 An SMCS console did not have an APPLID defined. The SMCS console is.not activated.
DUPLICATE SPECIFICATION IGNORED.
The system ignored a duplicate HARDCOPY, DEFAULT, or INIT statement.
In the message text:

682 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA196I

stmt-type
The duplicate statement type.
DEVNUM ALREADY DEFINED. STATEMENT 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.
In the message text:
keywd The duplicate keyword.
DUPLICATE keywd VALUE IGNORED.
A keyword on the statement has a duplicate value.
UNBALANCED COMMENT FOUND. DATA IGNORED
The system found a slash asterisk (/*) indicating the 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.
In the message text:
keywd The ignored keyword.
keywd REQUIRED FOR CONSOLE
The required NAME parameter was not found on a CONSOLE statement within the identified CONSOLxx
member.
System action: Depending on the message text, the system does one of the following:
keywd NOT SPECIFIED FOR THIS CONSOLE.
The system will continue processing without the keyword, although it is suggested that the keyword be added.
keywd REQUIRED FOR SMCS CONSOLES.
The CONSOLE statement is ignored in this case.
keywd VALUE IGNORED. REASON=reason-code
The system ignores an incorrect keyword value and processes other valid data, except when the keywords
APPLID, NAME, and AREA are specified. When AREA is specified the bad value is ignored, but valid values are
still accepted (AREA takes multiple comma-delimited values, and only the bad ones are ignored.) When APPLID
is specified, APPLID is ignored and SMCS will not be active for the life of the system.
If keywd is NAME, and DEVNUM(SMCS) was also specified on the CONSOLE statement, the entire CONSOLE
statement is ignored. Otherwise, only the invalid keyword value is ignored, but other valid keywords can be
processed.
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.
INCONSISTENT keywd VALUE IGNORED.
The system accepts the first value.
MISSING RIGHT PARENTHESIS ASSUMED.
The system assumes the parenthesis is present.
USE(xx) FORCED. REASON=reason-code
The system's operating mode was changed to maintain consistency with the AUTH or UNIT keyword.

Chapter 21. IEA messages 683

IEA200I

CONSOLE NOT ACTIVATED. RC=rc.

The system does not activate the console.
DUPLICATE SPECIFICATION IGNORED.
The system ignores the duplicate HARDCOPY, DEFAULT, or INIT statement.
DEVNUM ALREADY DEFINED. STATEMENT
IGNORED.
The system ignored the device number because the same device number was specified in a previous CONSOLE
statement.
DUPLICATE keywd VALUE IGNORED.
A keyword requiring a unique value was not specified with a unique value.
In the message text:
keywd The keyword requiring a unique value.

In all cases, the system continues processing the statements in the CONSOLxx parmlib member.
System programmer response: Before the next system initialization, correct the statement(s) in the CONSOLxx
member.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN600, IEAVN601, IEAVN602, IEAVN610, IEAVN611, IEAVN612, IEAVN615, CNZI1CDP
Routing Code: 2,10
Descriptor Code: 12

IEA200I memberxx - text

Explanation: During system initialization, the system could not use a data set member that was to contain an
alternate version of the master scheduler JCL.
In the message text:
memberxx
The member of SYS1.LINKLIB or SYS1.PARMLIB that the system could not use.
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.
System action: The system prompts the operator to respecify the MSTRJCL system parameter.
Operator response: Do the following:
1. Contact the system programmer. Provide the message number and message text.
2. At the request of the system programmer, do one of the following in response to the prompt to respecify the
MSTRJCL system parameter:

684 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA208I • IEA210I

v Specify the MSTRJCL system parameter on the console; then press ENTER.
v Press ENTER on the console.
3. If the system prompts for the MSTRJCL system parameter again, ask the system programmer to correct the
specified member.
4. After the system programmer corrects the member, reIPL the system.
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
Detecting Module: IEAVNP13
Routing Code: –
Descriptor Code: 12

IEA208I func FUNCTION INOPERATIVE

Explanation: During system initialization, the system detected unrecoverable errors while initializing a function. The
function is now inoperative because of these errors. This is probably an installation error.
In the message text:
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
Detecting Module: IEAVNP13, IEAVNPC5
Routing Code: -
Descriptor Code: 12

IEA210I LPA PACKING FUNCTION NOT BEING USED

Explanation: During system initialization, PAK =xx was not specified and the system did not find parmlib member
IEAPAK00.
System action: System initialization continues without the LPA packing function being active.
Operator response: Notify the system programmer.
System programmer response: If the LPA packing function is not wanted, no response is needed.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPC5

Chapter 21. IEA messages 685

IEA211I • IEA214A

IEA211I OBTAIN FAILED FOR dsname DATA SET

Explanation: During system initialization, the system could not find a data set for one of the following reasons:
v The operator did not mount the volume containing the data set
v The data set control block (DSCB) was not in the volume table of contents (VTOC)
v A permanent I/O error occurred

In the message text:

dsname The specified data set name.
System action: System initialization continues.
Operator response: Do the following:
v If the volume that contains the data set is not mounted, mount it.
v If the volume is mounted, record the device number. Notify the system programmer.
System programmer response: Do the following:
v List the VTOC of the volume that is supposed to contain the data set.
v If the data set is not on the volume, create the data set.
Source: DFSMSdfp
Detecting Module: IEAVNPM3

IEA213A DUPLICATE VOLUME volname FOUND ON DEVICES dev1 AND dev2. REPLY DEVICE NUMBER
WHICH IS TO REMAIN OFFLINE
Explanation: During system initialization, the system found direct access storage devices (DASD) with the same
volume label.
In the message text:
volname
The name of the duplicate volume.
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.
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 can be online. Then the system
continues initialization.
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.
When specifying the device, you can optionally precede the device number with a slash (/).
Source: Input/output supervisor (IOS)
Detecting Module: IEAVNP02

IEA214A 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
Explanation: During system initialization, the system found a direct access storage device (DASD) with volume
label the same as the SYSRES device (IPL device).
In the message text:

686 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA230E • IEA231A

volname
The duplicate volume serial name.
dev
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.
Source: Input/output supervisor (IOS)
Detecting Module: IEAVNP02

IEA230E WTOR BUFFER SHORTAGE. 80% FULL

Explanation: The write to operator with reply (WTOR) message buffers are currently 80% full.
System action: The system continues processing. The system puts unauthorized tasks issuing WTOR macros in a
wait state.
Operator response: Enter a DISPLAY R,R command to see the accumulated WTOR messages. Do one or more of the
following:
v Reply to outstanding WTOR messages.
v Cancel any jobs that are currently issuing WTOR messages.
v Enter the CONTROL M,RLIM command to increase the value of the WTOR buffer limit.
System programmer response: If the shortage persists, increase the value of RLIM in the CONSOLxx parmlib
member.
Source: Communications task (COMMTASK)
Detecting Module: IEAVMQWR
Routing Code: 2,10
Descriptor Code: 11

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 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.
v Enter the CONTROL M,RLIM command to increase 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. 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.
System programmer response: If the shortage recurs, increase the value for RLIM or RMAX in the CONSOLxx
parmlib member.

Chapter 21. IEA messages 687

IEA232I • IEA235I

Source: Communications task (COMMTASK)

Detecting Module: IEAVMQWR
Routing Code: 2,10
Descriptor Code: 2

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.
System action: The system continues processing. The system deletes messages IEA230E and IEA231A, if they are
outstanding.
Source: Communications task (COMMTASK)
Detecting Module: IEAVMQWR
Routing Code: 2,10
Descriptor Code: 4

IEA233I LOAD COMMAND IMSI VALUE OF c NOT VALID. DEFAULTED TO BLANK

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.
System action: The system continues processing.
Source: Communications task (COMMTASK)
Detecting Module: IEAVNPC6
Routing Code: -
Descriptor Code: 12

IEA234I NO MCS CONSOLES DEFINED

Explanation: No multiple console support (MCS) consoles are currently defined to the system.
System action: System initialization continues.
Operator response: Perform all operator functions on extended MCS consoles, subsystem allocatable consoles, or the
system console.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN600
Routing Code: -
Descriptor Code: 12

IEA235I 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.
Operator response: Notify the system programmer.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.

688 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA236I • IEA240I

Source: Communications task (COMMTASK)

Detecting Module: IEAVG719
Routing Code: Note 13
Descriptor Code: 12

IEA236I SYSCON DOMLIST QUEUE PROCESSING RESUMED.

Explanation: The system resumed processing of the system console delete operator message (DOM) queue.
System action: The system continues processing.
Source: Communications task (COMMTASK)
Detecting Module: IEAVG719
Routing Code: Note 13
Descriptor Code: 12

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 can be lost.
In the message text:
PRIORITY
The system is not accepting operator input from the screen that accepts priority commands.
System action: The system continues processing.
Operator response: If the system did not process the previous command, enter the command again from the system
console.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN701
Routing Code: 2
Descriptor Code: 12

IEA239I INSUFFICIENT STORAGE FOR AMRF, RETAINED MESSAGES DELETED.

Explanation: An error occurred when creating the action message retention facility (AMRF) cellpool.
System action: AMRF is shutdown and is in an inactive state. An ABEND077-6C2 will occur.
Operator response: Attempt to restart AMRF by issuing a K M,AMRF=Y command.
System programmer response: Search problem reporting data bases for a fix. If no fix exists, contact the IBM
support center.
Source: Consoles (SC1CK)
Detecting Module: CNZQ1MTC
Routing Code: 2, 10
Descriptor Code: 3

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.

Chapter 21. IEA messages 689

IEA246I • IEA248I

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)
Detecting Module: IEAVNP05
Routing Code: -
Descriptor Code: -

IEA246I memname ID xx SELECTED

Explanation: For system initialization, the system selected the parmlib member memname.
In the message text:
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.
System action: System initialization continues.
Source: System initialization (IPL/NIP)
Detecting Module: IEAIPL50
Routing Code: -
Descriptor Code: -

IEA247I USING IEASYSxx FOR xx...x

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.
In the message text:
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).
System action: System initialization continues.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPC4
Routing Code: -
Descriptor Code: 2

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.
In the message text:
modname
The duplicated module name
IEANxdd1
The first nucleus module list

690 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA250I • IEA253I

IEANxdd2
The second nucleus module list
System action: System initialization continues. The system loads module modname as part of the system nucleus.
Operator response: Notify the system programmer.
System programmer response: Make sure that the 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.
Source: Initial program load (IPL)
Routing Code:
Descriptor Code:

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 action: Processing continues.
System programmer response: This is probably an installation error. Make sure that the RER or RDE parameter is
correct.

IEA251E {DEVSUPyy: | IGDDFPKG:} INVALID SYNTAX. MEMBER PROCESSING TERMINATED ON LINE

nnnn
Explanation: The IGDDFPKG or the DEVSUPyy parmlib member contains an incorrect keyword.
In the message text:
yy The member number
keyword The incorrect keyword.
System action: IPL continues.
System programmer response: Correct the keyword error on the identified line before next IPL.
Source: DFSMSdfp
Detecting Module: IEAVNP16

IEA252E {DEVSUPyy: | IGDDFPKG:} INVALID SYNTAX. MEMBER PROCESSING TERMINATED ON LINE

nnnn
Explanation: The DEVSUPyy or IGDDFPKG parmlib member contains a syntax error.
In the message text:
yy The number of the member being processed.
nnnn The line number, relative to the beginning of the member, where the error was found.
System action: IPL continues.
System programmer response: Correct the syntax error on the identified line before next IPL.
Source: DFSMSdfp
Detecting Module: IEAVNP16

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]
STORAGE LIMIT FOR TAPE DDR SWAP IS SET TO xxxxM

Chapter 21. IEA messages 691

 IEA253I

STORAGE LIMIT FOR TAPE DDR SWAP DEFAULTED TO 1000M

--or--

DEVSUP MTLSHARE=YES SPECIFIED

--or--

DEVSUP MTL SHARE IS IGNORED

--or--

DEVSUP TAPE LIBRARY CATEGORY CODE FOR MEDIAn | ERROR | PRIVATE=xxxx

--or--

ENFORCE SMS DATACLASS MEDIA FOR: ALLMEDIA | MEDIA5PLUS

--or--

MTL WORM MEDIA ACCEPTED WHEN NOT PREFERENCED

--or--

DEVSUPxx XTIOT FOR NON-VSAM IS SUPPORTED

--or--

| DEVSUP PPRCSUM ENABLED: VARY 1 DEVICE/LSS FOR UPDATE TO TAKE EFFECT

--or--

| DEVSUP PPRCSUM DISABLED: VARY 1 DEVICE/LSS FOR UPDATE TO TAKE EFFECT

--or--

| OCE_ABEND_DESCRIPT NO LONGER HAS AFFECT. USE MPFLSTXX MEMBER.

Explanation: This message is issued to show the ATL media categories that have been set for this system in the
DEVSUPxx parmlib member. The message is informational, and requires no action or response.
In the message text:
V3 Is ISO/ANSI Version 3
V4 Is ISO/ANSI Version 4
Forced V3
ISO/ANSI Version 3 is being forced
Forced V4
ISO/ANSI Version 4 is being forced
value Is a numeric value
n Is a numeric value
xxxx ATL category number to be used by the system

Note: For descriptions of forced and other DEVSUPxx parameters displayed in this message, see z/OS MVS
Initialization and Tuning Reference.
Many of the possible message text lines are self-explanatory, but the following require some explanation:

692 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA254I • IEA255I

v Text STORAGE LIMIT FOR TAPE DDR SWAP IS SET TO xxxxM is issued when DDRSIZELIM=[xxxx|xxxxM] is
specified in the active DEVSUPxx member of PARMLIB. The value xxxx is the number from 1 to 1000 MB of main
storage that is allowed to be used in a Tape DDR swap. The system stores this value in the data facilities area
(DFA), for use by the system and by application programs.
v Text STORAGE LIMIT FOR TAPE DDR SWAP DEFAULTED TO 1000M is issued when DDRSIZELIM keyword
is omitted in the active DEVSUPxx member of PARMLIB. The system default for storage usage limit during Tape
DDR swap is set to 1000 MB. The system stores this value in the data facilities area (DFA), for use by the system
and by application programs.
v Text 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.
v Text 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.
v Text DEVSUP TAPE LIBRARY CATEGORY CODE FOR MEDIAn |ERROR |PRIVATE=xxxx is issued when
MEDIAn |ERROR |PRIVATE = xxxx is specified in the active DEVSUPxx member of PARMLIB.
| v Text OCE_ABEND_DESCRIPT NO LONGER HAS AFFECT. USE MPFLSTXX MEMBER. is issued if
| OCE_ABEND_DESCRIPT is specified. Additionally, all OPEN,CLOSE,EOV abend messages are issued using a
| Message Buffer Manager service. Two lines are now used in issuing the IECxxxx abend message whether or not
| the VERBOSE option via parmlimb MPFLSTxx is active.
System action: IPL continues.
Source: DFSMSdfp
Detecting Module: IEAVNP16

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.
Detecting Module: IEAVN615
Routing Code: 2,10
Descriptor Code: 12

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.
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.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN703
Routing Code: 1
Descriptor Code: 12

Chapter 21. IEA messages 693

IEA256I • IEA259I

IEA256I 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.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN703
Routing Code: 1
Descriptor Code: 12

IEA257I CONSOLE PARTITION CLEANUP IN PROGRESS FOR SYSTEM sysname

Explanation: Console partition cleanup is in progress, after a system in the sysplex was partitioned.
In the message text:
sysname
The name of the system that was partitioned.
System action: The system continues processing.
Source: Communications task (COMMTASK)
Detecting Module: IEAVG608
Routing Code: Note 13
Descriptor Code:

IEA258I CONSOLE PARTITION CLEANUP COMPLETE FOR SYSTEM sysname

Explanation: Console partition cleanup completed after a system in the sysplex was partitioned.
In the message text:
sysname
The name of the system that was partitioned.
System action: The system continues processing.
Source: Communications task (COMMTASK)
Detecting Module: IEAVG608
Routing Code: 1 or Note 13
Descriptor Code: 12

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.
In the message text:
CLOCKxx
The parmlib member, with the suffix xx.
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.
v External Time Reference (ETR) synchronization mode. ETR is the MVS generic name for the IBM Sysplex Timer
(9037) or equivalent.

694 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA260I • IEA262I

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).
System programmer response: Specify the correct synchronization mode (ETRMODE) in the CLOCKxx parmlib
member.
If you specify ETRMODE NO, you cannot specify ETRZONE YES.
Source: Timer supervision
Detecting Module: IEAVNP20
Routing Code: 2
Descriptor Code: 12

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 Sysplex Timer (9037) or equivalent.
System action: Processing continues in ETR synchronization mode.
Source: Timer supervision
Detecting Module: IEATEEIH
Routing Code: 10
Descriptor Code: 4

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. Also check that the timer is in the
correct mode for its configuration. If necessary, refer to the hardware documentation.
Otherwise, contact 9037 hardware support. Note that the same event might occur on more than one of the processors
in a sysplex.
Source: Timer supervision
Detecting Module: IEAVNP21
Routing Code: 10
Descriptor Code: 11

IEA262I ETR PORT n IS NOT OPERATIONAL.

Explanation: The specified External Time Reference (ETR) port is not working. ETR is the MVS generic name for the
IBM Sysplex Timer (9037) or equivalent.
In the message text:
n The port number.
System action: The system continues processing. The system records the error in the logrec data set.
Operator response: One of the following:
v If an ETR is installed, 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.

Chapter 21. IEA messages 695

IEA263I • IEA265I

v If an ETR is not installed, ensure that the CLOCKxx member of SYS.PARMLIB contains ETRMODE NO and
ETRZONE NO.
Source: Timer supervision
Detecting Module: IEATPORT
Routing Code: 10
Descriptor Code: 11

IEA263I 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 generic name for the IBM Sysplex Timer (9037) or equivalent.
In the message text:
xx The ETR identifier.
System action: The system continues processing. 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.
Source: Timer supervision
Detecting Module: IEATPORT
Routing Code: 10
Descriptor Code: 11

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.
In the message text:
n The port number.
xx The ETR identifier. If a question mark appears, there was no ETR identifier available from the port.
System action: The system continues processing. 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.
Source: Timer supervision
Detecting Module: IEATPORT
Routing Code: 10
Descriptor Code: 11

IEA265I UNABLE TO SYNC TOD CLOCKS TO timesource. CPC CONTINUES IN LOCAL MODE.
Explanation: The central processing complex (CPC) could not synchronize with the time source. This can be an
External Time Reference (ETR) or Server Time Protocol (STP). This occurred for one of the following reasons:
v A hardware error occurred.
v The time difference between the time source (ETR or STP) and time-of-day (TOD) clocks exceeded the ETRDELTA
or TIMEDELTA value in a CLOCKxx parmlib member.
ETR is the MVS generic name for the IBM Sysplex Timer (9037) or equivalent.

In the message text:

696 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA266I • IEA267I

timesource
Can be one of the following:
v ETR, for a system in ETR timing mode.
v STP, for a system in STP timing mode.
System action: The system continues processing in local synchronization mode. The system records the error in the
logrec data set.
Operator response: While the system may continue to operate, the installation is running in a condition where a
single point of failure exposure exists; a primary and backup configuration does not exist and an additional failure
could result in a sysplex outage. Contact your configuration/cabling personnel and have the configuration error
corrected. If necessary, contact IBM if the condition cannot be cleared by your personnel. Check to ensure that the
single point of failure condition has been corrected by issuing DISPLAY ETR.
Source: Timer supervision
Detecting Module: IEATEEIH or IEATSSCH
Routing Code: 10
Descriptor Code: 11

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 IBM Sysplex Timer (9037) or
equivalent.
In the message text:
CLOCKxx
The parmlib member, with the suffix xx.
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) initialization.
v ETR synchronization mode.
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).
System programmer response: Specify the correct synchronization mode (ETRMODE) in the CLOCKxx parmlib
member.
If you specify ETRMODE NO, you cannot specify ETRZONE YES.
Source: Timer supervision
Detecting Module: IEAVNP20
Routing Code: 2
Descriptor Code: 12

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 IBM
Sysplex Timer (9037) or equivalent.
In the message text:
n The port number.
System action: The system continues processing.

Chapter 21. IEA messages 697

IEA268I • IEA270I

Source: Timer supervision

Detecting Module: IEATEEIH
Routing Code: Note 13
Descriptor Code: 4

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 name for the IBM Sysplex Timer (9037) or equivalent.
In the message text:
n The port number.
System action: The system disables the port.
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.
Source: Timer supervision
Detecting Module: IEATEEIH
Routing Code: 10
Descriptor Code: 11

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.
In the message text:
x, y The side identifiers.
System action: Processing continues.
Source: Timer supervision
Detecting Module: IEATESMR
Routing Code: 10
Descriptor Code: 4

IEA270I 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 generic name for
the IBM Sysplex Timer (9037) or equivalent.
System action: Processing continues in local mode.
Operator response: Contact your configuration/cabling personnel and have the configuration error corrected.
Provide the logrec data set error records.
Source: Timer supervision
Detecting Module: IEATEEIH
Routing Code: 10
Descriptor Code: 11

698 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA271I • IEA272I

IEA271I 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
ETR is the MVS generic name for the IBM Sysplex Timer (9037) or equivalent.
System action: Processing continues.
Source: Timer supervision
Detecting Module: IEATTOC
Routing Code: Note 13
Descriptor Code: 4

IEA272I ETR SERVICE IS REQUESTED. REASON CODE=reason-code

Explanation: The External Time Reference (ETR) requires service. ETR is the MVS generic name for the IBM Sysplex
Timer (9037) or equivalent.
In the message text:
reason-code
A reason code explaining the error follows. For more information about the reason codes, see Maintenance
Information for the 9037 Sysplex Timer.
002 Operation Failed. MODEM not responding. (No data was returned from MODEM.)
003 Time out waiting for a phone line connection. The MODEM responded with one of the following:
v No dial tone was detected.
v Call was answered but no carrier was detected.
v No answer.
004 Phone line data transfer failed. (A data or protocol error was detected.)
033 CLO Links cross-cabled.
034 CLO Link A wrapped.
035 CLO Link B wrapped.
036 CLO links jumpered.
037 Non-severe fan failure detected.
040 Communication lost with console.
041 Communication lost with standby console.
043 Phone line was busy.
044 The external time source is out of tracking range.
045 The external time source is not responding.
v If the external time source is a modem, message IEA272I with return code 045 is repeated each
time a dial failure occurs.
v If the external time source is a time-code generator or receiver, message IEA100I with return code
042 issues when the 9037 begins retracking the external time source.
046 The external time source reported a synchronization change.
047 The external time source is not synchronized.
065 Base card failed.
066 Port card in card location 2 failed.

Chapter 21. IEA messages 699

IEA272I

067 Port card in card location 3 failed.

068 Port card in card location 4 failed.
069 Port card in card location 5 failed.
074 Control link card failed.
075 Severe fan failure detected.
076 Other 9037 unit failed.
077 Control link A failed.
078 Control link B failed.
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.
099 Port card in slot 1 failed.
100 Port card in slot 2 failed.
101 Port card in slot 3 failed.
102 Port card in slot 4 failed.
103 Port card in slot 5 failed.
104 Port 0 failed.
105 Port 1 failed.
106 Port 2 failed.
107 Port 3 failed.
108 Port 4 failed.
109 Port 5 failed.
110 Port 6 failed.
111 Port 7 failed.
112 Port 8 failed.
113 Port 9 failed.
114 Port 10 failed.
115 Port 11 failed.
116 Port 12 failed.
117 Port 13 failed.
118 Port 14 failed.
119 Port 15 failed.
120 Port 16 failed.

700 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA273I • IEA275I

121 Port 17 failed.

122 Port 18 failed.
123 Port 19 failed.
124 Port 20 failed.
125 Port 21 failed.
126 Port 22 failed.
127 Port 23 failed.
System action: Processing continues.
Operator response: The reason code indicates that service is required. Check the system console associated with this
processor. If the system has 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.
Source: Timer supervision
Detecting Module: IEATEEIH, IEATESMR
Routing Code: 10
Descriptor Code: 11

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 generic name for the IBM Sysplex Timer (9037) or equivalent.
The channel path measurement facility (CPMF) stops or enters a restartable error state. The system restarts the CPMF.
System action: The system continues processing. Resynchronization may have created a gap in time stamps.
Source: Timer supervision
Detecting Module: IEATESCH
Routing Code: Note 13
Descriptor Code: 4

IEA274W THE ONLY ONLINE TOD CLOCK HAS FAILED.

Explanation: The last, or only, online time-of-day (TOD) clock failed.
System action: The system enters nonrestartable wait state X'A1E'.
Operator response: See the operator response for wait state X'A1E'.
System programmer response: See the system programmer response for wait state X'A1E'.
Source: Timer supervision
Detecting Module: IEATESCH, IEATESC2, IEAVRTOD, IEATTSCH, IEATTFDH
Routing Code: 1
Descriptor Code: 1

IEA275I PRIMARY SYNCHRONIZATION FACILITY DAMAGE WAS DETECTED.

Explanation: The system found that the primary synchronization facility was damaged.
System action: The system attempts to validate the damaged hardware. The system continues processing.
Source: Timer supervision
Detecting Module: IEATPSDH

Chapter 21. IEA messages 701

IEA276I • IEA279I

Routing Code: Note 13

Descriptor Code: 4

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.
Source: Timer supervision
Detecting Module: IEATEADH
Routing Code: Note 13
Descriptor Code: 4

IEA277I TIMING FACILITY DAMAGE WAS DETECTED.

Explanation: The system found that the time-of-day (TOD) clock or the TOD synchronization facility was damaged.
System action: The system attempts to validate the damaged hardware. The system continues processing.
Operator response: Contact your System Programmer.
System programmer response: Contact your hardware service representative to determine the cause of the failure.
Source: Timer supervision
Detecting Module: IEATTFDH
Routing Code: Note 13
Descriptor Code: 4

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.
In the message text:
n The port number.
System action: Processing continues.
Source: Timer supervision
Detecting Module: IEATEEIH, IEATESGR
Routing Code: 10
Descriptor Code: 12

IEA279I ALL CLOCK RELATED SET COMMANDS ARE IGNORED WHEN IN xxx MODE.
Explanation: The operator entered a SET command while the system was running in either External Time Reference
(ETR) or Server Time Protocol (STP) synchronization mode.
In the message text:
xxx
One of the following:
v ETR
v STP
System action: The system ignores the SET command.
Operator response: Do not issue the clock-related SET commands when in ETR timing mode (with ETRMODE YES

702 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA280I • IEA282I

and ETRZONE YES specified in CLOCKxx) or in STP timing mode (with STPMODE YES and STPZONE YES
specified in CLOCKxxx).
Source: Timer supervision
Detecting Module: IEE6503D
Routing Code: *
Descriptor Code: 5

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.
ETR is the MVS generic name for the IBM Sysplex Timer (9037) or equivalent.
System action: Processing continues in local synchronism mode.
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.
Source: Timer supervision
Detecting Module: IEATPORT
Routing Code: 10
Descriptor Code: 11

IEA281I ETR SYNC CHECK THRESHOLD HAS BEEN EXCEEDED. CPC CONTINUES IN LOCAL MODE.
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.
System action: Processing continues in local synchronization mode.
Operator response: Contact hardware support. Provide the logrec data set error records.
Source: Timer supervision
Detecting Module: IEATESCH
Routing Code: 10
Descriptor Code: 11

IEA282I 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 ETR FACILITY IS NOT INSTALLED.]

Chapter 21. IEA messages 703

IEA282I

[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]

Or
hh.mm.ss ETR STATUS ETR SIMULATION MODE,
SIMETRID=nn

Or
[THIS SERVER IS PART OF TIMING NETWORK ctnid]

All messages are in response to the DISPLAY ETR command.

ETR is the MVS generic name for the IBM Sysplex Timer (9037) or equivalent.

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.
mode
The current synchronization mode, as follows:
ETR The system time-of-day (TOD) clocks are synchronized to an External Time Reference (ETR).
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:
OPERATIONAL
The port is working.
NONOPERATIONAL
The port is not working.
enb
One of the following:
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.
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.

704 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA283I • IEA284I

The second message text is displayed if SIMETRID=nn in CLOCKxx is specified. In the second message text:
hh.mm.ss
The hour (00-23), minute (00-59), and second (00-59) that the system issued this message.
nn The simulated sysplex timer identifier ranging from X'00' to X'1F'.
System action: The system continues processing.
Operator response: None.
System programmer response: None.
Source: Timer supervision
Detecting Module: IEATDISP
Routing Code: *
Descriptor Code: 5

IEA283I ETR PORT n IS ENABLED.

Explanation: An External Time Reference (ETR) port is enabled. ETR is the MVS generic name for the IBM Sysplex
Timer (9037) or equivalent.
In the message text:
n The port number.
System action: The system continues processing.
Source: Timer supervision
Detecting Module: IEATCMD
Routing Code: *
Descriptor Code: 5

IEA284I ETR PORT n CANNOT BE ENABLED.

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.
v The ETR Facility is not installed.
v The system cannot communicate with the ETR.
ETR is the MVS generic name for the IBM Sysplex Timer (9037) or equivalent.

In the message text:

n The port number.
System action: The system continues processing.
Operator response: Do the following:
v Wait 30 seconds.
v Enter the SETETR command again.
If the system issues message IEA284I again, the port cannot be enabled.
v Enter the DISPLAY ETR command to display information about the port.
Source: Timer supervision
Detecting Module: IEATCMD
Routing Code: *
Descriptor Code: 5

Chapter 21. IEA messages 705

IEA285I • IEA298I

IEA285I THE LINK FROM PORT n TO THE ETR IS NOT TUNED.

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.
In the message text:
n 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.
Source: Timer supervision
Detecting Module: IEATEEIH, IEATESMR
Routing Code: 10
Descriptor Code: 12

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.
In the message text:
n The offering or feature value specified. For information about the offering or feature value, refer to the z/OS
MVS Initialization and Tuning Reference.
System action: Processing continues.
Source: DFSMS/MVS
Detecting Module: IEAVNP16, IGDSMSPK

IEA297W LSQA IS EXHAUSTED IN A NON-MEMTERMABLE ADDRESS SPACE: ASID=xxxx

JOBNAME=yyyyyyyy
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.
In the message text:
xxxx The address space ID, in hexadecimal, of the address space in which the problem occurred.
yyyyyyyy
The job name of the address space in which the problem occurred.
System action: The system enters a non-restartable 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 might 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.
Source: Supervisor Control

IEA298I MAXCAD VALUE, xxxxxx, NOT VALID. DEFAULT OF 50 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

In the message text:

xxxxxx The incorrect MAXCAD value

706 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA299I • IEA301I

System action: Initialization continues with the default MAXCAD value of 50.
Operator response: You can reIPL to enter a correct value, but is not required.
System programmer response: Specify the MAXCAD value again 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
Routing Code: 2,10
Descriptor Code: 4

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.
In the message text:
mod The missing optional RIM
System action: Nucleus initialization continues.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNIPM
Routing Code: -
Descriptor Code: -

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.
In the message text:
mem The member name
dsname
The data set containing the member
System action: If the missing member is a NIP module, the system enters a disabled wait state. If not, processing
continues.
Operator response: Record the address of the device where the I/O error occurred and contact hardware support.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNIPM, IEAVNP13, IEAVNPM4, IEAVNPM3
Routing Code: 1
Descriptor Code: 12

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.
In the message text:
mem NOT FOUND IN dsname
NIP could not find member mem of data set dsname.

Chapter 21. IEA messages 707

IEA303W

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 operator's 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.
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.
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 reporting data bases for a fix for the problem. If no fix exists,
contact the IBM Support Center. Note that the IBM Support Center might request a stand-alone dump if the problem
has recurred.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNIPM, IEAVNP13, IEAVNPC5, IEAVNPM4
Routing Code: 1
Descriptor Code: 12

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 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'.
Operator response: See the operator response for wait state X'040'.
System programmer response: See the system 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'.
Source: System initialization (IPL/NIP)

708 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA304W • IEA306I

Detecting Module: IEAVNIPM

Routing Code: 1
Descriptor Code: 12

IEA304W SYSTEM WAIT STATE - CODE cde DURING mod INITIALIZATION

Explanation: The nucleus initialization program (NIP) encountered an error and the system enters a wait state.
In the message text:
cde The last three digits identify the wait state code. See z/OS 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.
System action: The system enters a wait state.
Operator response: See the operator response for the wait state issued.
System programmer response: See the system programmer response for the wait state issued.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNIPM
Routing Code: 1
Descriptor Code: 12

IEA306I dev,chp,I/O ERROR,cm, stat,[sens],[ser]

Explanation: The nucleus initialization program (NIP) 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.
In the message text:
dev
The device number
chp
The channel path identifier
cm The I/O command that resulted in an unsuccessful I/O completion, if known; otherwise, this field is set to
asterisks.
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.
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.
Source: Nucleus initialization program (NIP)

Chapter 21. IEA messages 709

IEA307I • IEA308I

Detecting Module: IEAVNPM3

Routing Code: -
Descriptor Code: 12

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.
In the message text:
dev
The device number.
chp
The channel path identifier (CHPID)
cmd
The I/O command that caused the error.
stat
The subchannel status word (SCSW) status bytes.
text
A variable length text string that is one of the following:
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.
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 an I/O error also occurred while trying to read the resulting
sense data.

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.

System action: The system continues processing.
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.
Source: Input/output supervisor (IOS)
Detecting Module: IOSVVOLV
Routing Code: 2
Descriptor Code: 12

IEA308I MAXIMUM NUMBER OF PARMLIBS EXCEEDED

Explanation: More than 10 PARMLIB statements were specified in LOADxx.
System action: IPL continues.
System programmer response: Ensure that a maximum of 10 PARMLIB statements are specified in LOADxx.
Source: Initial program load (IPL)

710 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA309I • IEA312I

Detecting Module: IPXI50PS

IEA309I PARMLIB DATA SET IGNORED: dsname volser

Explanation: A data set in the PARMLIB concatenation is ignored because more than 10 (the maximum allowed)
data sets have been specified.
In the message text:
dsname The name of the data set that will not be used.
volser The volume where dsname resides.
System action: IPL continues.
System programmer response: Ensure that a maximum of 10 PARMLIB statements are specified in LOADxx.
Source: Initial program load (IPL)
Detecting Module: IPXI50PS

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 IEA120D, IEA213A, or IEA214A again.
Operator response: Enter the reply correctly.
Source: Input/output supervisor (IOS)
Detecting Module: IEAVNPM3, IEAVNP02, IEAVNP03, ILRASRIM
Routing Code: 1
Descriptor Code: 2

IEA311I UNLABELED DASD ON dev. UNIT PUT OFFLINE.

Explanation: The direct access storage device (DASD) mounted on a device is not formatted correctly.
In the message text:
dev
The device number.
System action: The system marks the device offline.
Operator response: Notify the system programmer.
System programmer response: Ensure that the volume mounted on the device was properly initialized by the
ICKDSF program.
Source: Input/output supervisor (IOS)
Detecting Module: IOSVVOLV
Routing Code: 2
Descriptor Code: 12

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.
System action: The system continues processing without the device.

Chapter 21. IEA messages 711

IEA313I • IEA315A

Operator response: Notify the system programmer.

System programmer response: Ensure that the system properly initialized the volume mounted on the device.
Source: DFSMSdfp

IEA313I DEVICE dev DISMOUNTED

Explanation: During nucleus initialization, the system dismounted a device in response to message IEA213A or
IEA214A.
In the message text:
dev
The device number.
System action: The system continues processing.
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.
Source: Input/output supervisor (IOS)
Routing Code: 2
Descriptor Code: 4

IEA314I CONFLICTING VOLUME ON dev

Explanation: During system initialization, the system 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.
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'.
Operator response: See the operator response for message IEA315A, IEA317A, or wait state code X'039'.
Source: DFSMSdfp
Detecting Module: IEAVNPM3

IEA315A M devname,[NL], dsname

Explanation: During system initialization, the system required one of the following:
v An unlabeled tape for a SYS1.DUMPnn data set
v The volume containing a data set to be mounted on a device

In the message text:

devname
The name of the device on which the volume should be mounted.
dsname The name of the data set in the volume to be mounted.
System action: The system waits for a volume to be mounted on the specified device.
Operator response: Mount one of the following:

712 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA316A • IEA317A

v The direct access volume containing the specified data set

v An unlabeled scratch tape
Source: DFSMSdfp
Detecting Module: IEAVNPM3

IEA316A D dev[,ser]
Explanation: During system initialization, the system 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.
In the message text:
dev The device number.
ser The serial number of the volume that was mounted incorrectly.
System action: The system issues message IEA315A.
Operator response: Do the following:
v Demount the specified volume.
v Ensure that the proper volume is mounted on the specified device.
v Ensure that the volume is initialized with the proper volume serial number.
Source: DFSMSdfp
Detecting Module: IEAVNPM3

IEA317A SPECIFY UNIT FOR dataset ON volser [OR CANCEL]

Explanation: During system initialization, the system 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.
[OR CANCEL]
The operator may cancel a request to mount the volume.
System action: The system waits for the operator to reply. If the operator replies R 00,xxx, the system may issue
messages IEA318I and IEA317A.
Operator response: Do the following:
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.
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 IOS120D with the ‘CONT’ command, reIPL the system.
8. Verify that the devices defined in the IODF are online.
Source: DFSMSdfp
Detecting Module: IEAVNPM3

Chapter 21. IEA messages 713

IEA318I • IEA321I

IEA318I UNIT UNACCEPTABLE

Explanation: During system initialization, the system found that the unit specified in the reply to message IEA317A
contained one of the following:
v An unacceptable device type for the data set volume to be mounted
v A volume that could not be demounted
System action: The system rejects the unit specification. The system issues message IEA317A again.
Operator response: See the operator response for 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
Detecting Module: IEAVNPM3

IEA319I dsname NOT FOUND ON volser

Explanation: During system initialization, the system could not find a data set on a volume. In the message text:
dsname The data set name.
volser The volume serial number.
System action: If the data set is logrec, SYS1.SVCLIB, SYS1.PARMLIB, or SYS1.LINKLIB, the system enters a
disabled wait state. Otherwise, the system continues processing.
Operator response: Remove the incorrect volume and mount the correct one. If the action does not correct the
problem, notify the system programmer.
System programmer response: Do the following:
v List the table of contents of the volume that should contain the data set.
v If the data set is not on the volume, create the data set.
v Tell the operator to restart the system.
Source: DFSMSdfp
Detecting Module: IEAVNPM3

IEA321I INVALID PARAMETER SYNTAX - prm - text

Explanation: text is one of the following:
INVALID OPI KEYWORD
IMPROPER DELIMITER
UNBALANCED PARENS
INVALID CONTINUATION
UNDEFINED KEYWORD

The specified parameter is not valid.

In the message text:

prm
The specified parameter.
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.

714 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA323I • IEA324I

UNBALANCED PARENS
The parameter included a different number of right and left parentheses.
INVALID CONTINUATION
The parameter continued across more than two successive lines of text.
UNDEFINED KEYWORD
The parameter is not valid for message IEA101A.
System action: The system prompts the operator for a reply by issuing message IEA324I, ,IEA332A, IEA336A, or
IEA906A, unless text is UNDEFINED KEYWORD and WARNUND is in effect, in which case the system ignores the
undefined keyword and continues processing the system parameters.
Operator response: See the operator response for the accompanying message.
Source: System Initialization (IPL/NIP)
Detecting Module: IEAVNP03
Routing Code: Note 9
Descriptor Code: 12

IEA323I OPI INVALID IN mem

Explanation: The nucleus initialization program (NIP) found an incorrect OPI parameter in a IEASYSxx parmlib
member. The OPI parameter must be specified as either OPI=YES or OPI=NO.
In the message text:
mem 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 cancelling the use of it
for this IPL. Parameters interpreted up to the point of the error remain in effect.
System programmer response: Make sure that the IEASYSxx parmlib member correctly specifies the SYSP
parameter. Ensure that the SYSP list of system parameters is specified correctly.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNP03

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.
In the message text:
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.
Operator response: Notify the system programmer. See the operator response for the message preceding IEA324I.
System programmer response: See the system programmer response for the message preceding IEA324I.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNP03

Chapter 21. IEA messages 715

IEA325I • IEA328E

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.
In the message text:
xx The identifier for the IEASYS parmlib member.
System action: The system lists the parameters and continues processing.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNP03

IEA326I LOCATE FAILED FOR dsname

Explanation: dsname is one of the following:
SYS1.DUMP
SYS1.CSSLIB
SYS1.LINKLIB
SYS1.LPALIB
SYS1.DSSVM
SYS1.MIGLIB
SYS1.SIEALNKE
SYS1.SIEAMIGE

During system initialization, the nucleus initialization program (NIP) could not find a data set in the system catalog.
System action: If the data set is SYS1.LINKLIB, SYS1.CSSLIB, SYS1.MIGLIB, SYS1.SIEALNKE or SYS1.SIEAMIGE
the system enters wait state X'00A'. For other data sets, the system provides additional diagnostic information in
message IEA208I, IEA351I, IEA354I, or IEA355A.
Operator response: Notify the system programmer.
System programmer response: See the system programmer response for accompanying messages or for wait state
X'00A' if the missing data set name is SYS1.LINKLIB,SYS1.MIGLIB, SYS1.SIEALNKE or SYS1.SIEAMIGE.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPC5, IEAVNPE5
Routing Code: -
Descriptor Code: 12

IEA328E LNKLSTxx INPUT TRUNCATED AT dsname

Explanation: Too many data set names were specified for inclusion in the LNKLST concatenation.
In the message text:
xx The identifier for the LNKLST or PROG parmlib member that defined the LNKLST concatenation.
dsname The name of the last data set in the parmlib member
System action: The system did one of the following:
v Accumulated data set names for the LNKLST until its work area filled up.
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.
Operator response: Notify the system programmer. Obtain a stand-alone dump.
System programmer response: Do one of the 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.

716 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA329I • IEA331I

To reopen the LNKLST concatenation, have the operator reIPL the system.

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.

If the problem recurs, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM
Support Center. Provide the stand-alone dump.
Source: Contents supervision (CSV)
Detecting Module: IEAVNPE5, CSVLLCRE
Routing Code: 1,10
Descriptor Code: 11,12

IEA329I RETRYABLE ERROR. RECENT COMMANDS MAY NEED TO BE REPEATED

Explanation: The current command to be processed is not valid. The system recovered from a previous abend.
System action: The system does not process the command and all subsequent commands in the queue.
Operator response: Retry the command, which might be a CONTROL, MONITOR, or STOPMN command. If the
problem persists, contact the system programmer.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Source: Communications task (COMMTASK)
Detecting Module: IEAVC700
Routing Code: 2,10
Descriptor Code: 4

IEA330A CONTINUE prm PARM

Explanation: This message permits the operator to continue entering information related to a parameter.
In the message text:
prm The parameter name.
System action: The system prompts for the operator for a reply.
Operator response: Continue entering information related to the parameter.
Source: System Initialization component (IPL/NIP)
Detecting Module: IEAVNP03
Routing Code: Note 9
Descriptor Code: -

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.
In the message text:
dsname The data set name of a data set concatenated to the SYS1.LINKLIB data set.
System action: The system continues processing.
Source: Contents supervision (CSV)
Detecting Module: IEAVNP03
Routing Code: Note 9

Chapter 21. IEA messages 717

IEA332A • IEA335I

Descriptor Code: -

IEA332A SPECIFY prm

Explanation: The nucleus initialization program (NIP) found that a function defined by a parameter in an IEASYSxx
parmlib member was omitted.
In the message text:
prm The parameter name of a required or optional function. If OR CANCEL appears in the message text, the
function is optional.
System action: The system prompts the operator for a reply.
Operator response: Contact the system programmer. If the function is required, reply to the message 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.
System programmer response: Tell the operator which responses to enter.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNP03
Routing Code: Note 9
Descriptor Code: -

IEA334A dsname(mem) HAS AN INVALID RECORD LENGTH - SPECIFY EOB TO CONTINUE

Explanation: The nucleus initialization program (NIP) read at least one record from a parmlib member. The member
has a physical record length (block size) that is 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.
In the message text:
dsname The data set containing the member
mem The member that has the incorrect physical record length
System action: Initialization processing waits for your response.
Operator response: Notify the system programmer. To continue the IPL, specify EOB (press ENTER). This action
requests processing of member mem, even though it has an incorrect record length.
System programmer response: Make sure that the physical record length of records in mem is a multiple of 80.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPM4

IEA335I dsname MODULE mod IN mem LIST IS text

Explanation: text is one of the following:

NOT EXECUTABLE
ALIAS OF ALIAS
NOT AUTHORIZED
A DUPLICATE

The system could not process a module a for data set in a parmlib member.

718 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA336A • IEA338A

In the message text:

dsname The name of the data set.
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.
A DUPLICATE
Module mod duplicates a module name that already appears in member mem.
mod 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.
mem 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.
Application Programmer Response: This is probably an installation error. Ensure that the module with the incorrect
alias is link edited properly.
Source: Contents supervision (CSV)
Detecting Module: IEAVNP05
Routing Code: -
Descriptor Code: -

IEA336A 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 is preceded by explanatory messages IEA301I and IEA324I.
Operator response: Do one of the following:
v Enter a reply specifying only the corrected parameter and subsequent parameters.
v Cancel further input by pressing ENTER. In this case, the parameters accepted by the system remain in effect.
You can specify a parameter again during 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 the IBM Support Center.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNP03

IEA338A INVALID prm PARM - RESPECIFY parm OR PRESS ENTER TO CANCEL

Explanation: One of the system parameters specified during system initialization was incorrect.
In the message text:
prm The incorrect parameter
System action: The system ignores the incorrect parameter and prompts the operator for a reply.

Chapter 21. IEA messages 719

IEA339A • IEA340I

Operator response: Respecify the parameter or press ENTER to cancel the use of the parameter for this IPL.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNP03

IEA339A dsname HAS AN INVALID BLOCKSIZE - PRESS ENTER TO CONTINUE

Explanation: The block size of the parmlib data set dsname is not a multiple of 80. The logical record length (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.
Operator response: Notify the system programmer of this message. To continue the IPL, press ENTER. This action
requests processing of the concatenated parmlib data set with the incorrect block size
System programmer response: Make sure that the LRECL of the data sets in the concatenated parmlib is 80 and
that the block size is a multiple of 80.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNP03

IEA340I REAL OR VIRTUAL STORAGE NOT AVAILABLE FOR func

Explanation: The nucleus initialization program (NIP) could not obtain storage for the function indicated.
In the message text:
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'.
Functions and system actions are as follows:
func System Action
PFT Wait state X'038'
LPA Device
Wait state X'03A'
Support
Modules
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.

720 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA341A • IEA343D

System programmer response: 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.
Source: Contents supervision (CSV)
Detecting Module: IEAVNP05
Routing Code: Note 9
Descriptor Code: 12

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.
In the message text:
prm The incorrect system parameter.
System action: The system prompts the operator for a reply.
Operator response: Enter the parameter correctly or press ENTER. If you press ENTER, any system defaults for the
parameter are used.
Examples:
SVC={aa }
{(aa,bb,...)}
ALLOC={aa }
{(aa,bb,...)}
SCH={(aa) }
{(aa,L) }
{(aa,bb..) }
{(aa,bb..,L)}
If prm is DUMP, ensure that TA was not specified in the SYS1.PARMLIB dump command.
Source: Nucleus initialization program (NIP)
Detecting Module: IEAVNP08

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.
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.
System programmer response: If the problem cannot be resolved, search problem reporting data bases for a fix for
the problem. If no fix exists, contact the IBM Support Center.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 2

Chapter 21. IEA messages 721

IEA345A • IEA347A

IEA345A dsname NOT USED (text) - PRESS ENTER TO CONTINUE

Explanation: The system cannot use the specified parmlib data set.
In the message text:
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.
Operator response: Notify the system programmer. 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.
Source: Nucleus initialization program (NIP)
Detecting Module: IEAVNPOP

IEA347A SPECIFY MASTER CATALOG PARAMETER

Explanation: During system initialization, the system 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. If the catalog name to be used has
been provided in the LOADxx member, but that member name cannot be found in SYS1.NUCLEUS, this message is
issued.
System action: The system waits for the operator to reply. The system generates the name of the SYS1.NUCLEUS
parmlib member that is used to find the master catalog. If the parmlib member cannot be found, the message is
reissued. If the SYSCAT statement is supplied in the LOADxx member and this message appears, either the name of
the catalog is spelled incorrectly in the SYSCAT statement, or LOADxx filtering parms (such as, HWNAME and
LPARNAME) might be incorrect, causing the system to attempt to use the wrong master catalog name.
Operator response: Do one of the following:
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
Detecting Module: IEAVNP11
Routing Code: Note 2
Descriptor Code: -

722 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA350I • IEA352I

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.
In the message text:
mem The specified parmlib member name.
System action: The system prints the list and processing continues.
Source: Contents supervision (CSV)
Detecting Module: IEAVNP05, IEAVNPC5
Routing Code: -
Descriptor Code: 12

IEA351I dsname REQUIRED FOR mem

Explanation: The nucleus initialization program (NIP) cannot find the data set dsname. The data set is required for
member mem in the parmlib.
In the message text:
dsname The specified data set name.
mem The specified member name.
System action: The system continues processing.
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.
System programmer response: 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.
Source: Contents supervision (CSV)
Detecting Module: IEAVNP05
Routing Code: -
Descriptor Code: 12

IEA352I LIST mem FOR prm INVALID text MODNAME mod

Explanation: text is one of the following:

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

The parmlib member specified for a parameter is incorrect.

In the message text:

mem
The name of the parmlib member.

Chapter 21. IEA messages 723

IEA353I

prm
The parameter.
MODNAME mod
mod identifies the name of the incorrect module specified.
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 volid's 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.
Operator response: This is probably an installation error. Respond to the prompt message and report this message
to the system programmer.
System programmer response: If the error recurs and the program is not in error, search problem reporting
databases for a fix for the problem. If no fix exists, contact the IBM Support Center.
Source: Contents supervision (CSV)
Detecting Module: IEAVNPA5, IEAVNPC5, IEAVNP05
Routing Code: -
Descriptor Code: 12

IEA353I prm INPUT TERMINATED AT mod

Explanation: The definition of the parameter failed for lack of storage as indicated by the preceding message.
In the message text:
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'.
Operator response: This is probably an installation 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.

724 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA354I • IEA355A

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.
Source: Contents supervision (CSV)
Detecting Module: IEAVNP05, IEAVNPC5
Routing Code: -
Descriptor Code: 12

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.
System action: The system enters non-restartable wait state X'03A'. If any modules were successfully loaded into the
LPA, the system issues message IEA353I.
Operator response: This is probably an installation error. Notify the system programmer.
System programmer response: 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.
Source: Contents supervision (CSV)
Detecting Module: IEAVNP05, IEAVNPC5
Routing Code: -
Descriptor Code: 12

IEA355A RESPECIFY prm [OR CANCEL]

Explanation: The nucleus initialization program (NIP) detected an error a parameter.
In the message text:
prm The parameter name.
OR CANCEL
CANCEL is a reply option.
System action: The system issues message 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.
System programmer response: See the system programmer response for message IEA101A.

Chapter 21. IEA messages 725

IEA356I • IEA357I

Source: Communications task (COMMTASK)

Detecting Module: IEAVNPA1
Routing Code: Note 9
Descriptor Code: -

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.
In the message text:
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.
Source: Contents supervision (CSV)
Detecting Module: IEAVNP05, IEAVNPC5
Routing Code: -
Descriptor Code: -

IEA357I ERRORS IN ‘IEAPAKxx’ LIST

text - sysact
Explanation: text is one of the following:
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.

In the message text:

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.

726 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA358A • IEA359E

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:
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.
Source: Contents supervision (CSV)
Detecting Module: IEAVNPC5
Routing Code: -
Descriptor Code: 12

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).
In the message text:
mod The specified module.
System action: The system prompts the operator for a reply. If the reply is ENTER, the system continues processing.
The system does not place the non-executable module into the LPA.
Operator response: Report this message to the 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.
Source: Contents supervision (CSV)
Detecting Module: IEAVNPC5

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

Chapter 21. IEA messages 727

IEA360A • IEA361I

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 z/OS 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.
Source: Console Services
Detecting Module: CNZQ1MTC
Routing Code: 2,10
Descriptor Code: 11

IEA360A SEVERE BUFFER SHORTAGE FOR RETAINED ACTION MESSAGES - 100% FULL
Explanation: The action message retention facility (AMRF) is active, and the buffer area for the following messages
is full:
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 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 z/OS 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.
Source: Console Services
Detecting Module: CNZQ1MTC
Routing Code: 2,10
Descriptor Code: 2

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.
System action: The system continues processing. The system deletes messages IEA359E and IEA360A.
Source: Communications task (COMMTASK)
Detecting Module: CNZQ1MTC
Routing Code: 2,10
Descriptor Code: 4

728 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA362E • IEA364E

IEA362E BUFFER EXTENSION FAILED FOR RETAINED ACTION MESSAGES

Explanation: The action message retention facility (AMRF) is active, the system could not obtain additional buffers,
and the buffer area for the following messages is full:
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)
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.
Source: Console Services
Detecting Module: CNZQ1MTC
Routing Code: 2,10
Descriptor Code: 11

IEA363I mod NOT FOUND IN LPA

Explanation: The nucleus initialization program (NIP) could not find the module in the link pack area (LPA).
In the message text:
mod The specified module.
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'.
Operator response: This is probably an installation error. Notify the system programmer.
Application Programmer Response: Ensure that the missing routine is in the LPA. If necessary, add the module to
the SYS1.LPALIB and have the operator run 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.
System programmer response: 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.
Source: Contents supervision (CSV)
Detecting Module: IEAVNPS5, IEAVNP05, IEAVNP07
Routing Code: 2,10
Descriptor Code: 4

IEA364E {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.

Chapter 21. IEA messages 729

IEA365E • IEA366W

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.
Operator response: If the AMRF failed and you want to restart it, enter the CONTROL M,AMRF=Y command.
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.
If either problem recurs, contact the system programmer.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Source: Communications task (COMMTASK)
Detecting Module: IEAVMQWR, CNZS1MPS, IEAVC702
Routing Code: 2,10
Descriptor Code: 3 or 11

IEA365E COMMAND SCHEDULER RESTART FAILED,

ABEND RECURSION
THE FOLLOWING COMMANDS
ARE INOPERATIVE:
D C D C,K D PFK D R REPLY D A
D OPDATA ROUTE MCS LOGON
MCS LOGOFF
Explanation: Command processing failed. The system tried to restart it, but the restart also failed.
This message follows message IEE481I, which identifies the system abend code of the original error.
System action: The system continues other processing.
Operator response: If necessary, reIPL the system to return the system to full processing.
System programmer response: See the system programmer response for the abend identified in message IEE481I.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN701
Routing Code: 2,10
Descriptor Code: 11

IEA366W MULTIPLE CONSOLE SUPPORT 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'.
Operator response: See the operator response for wait state X'201.'.
System programmer response: See the system programmer response for wait state X'201.'.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN700
Routing Code: Note 12
Descriptor Code: 1

730 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA367A • IEA368I

IEA367A MULTIPLE CONSOLE SUPPORT INOPERATIVE ERROR CODE = xxxx REPLY WITH ANY
CHARACTER TO CONTINUE WITHOUT MULTIPLE CONSOLE SUPPORT
Explanation: Because of an error, the communications task (COMMTASK) failed.
In the message text:
xxxx The reason code, which is one of the following:
8001 The system could not establish a recovery routine.
8002 The system could not attach a needed routine.
8004 The error occurred during a POST.
8005 The error occurred during an update to the command address space table.
8007 The error occurred during a POST.
8008 An error during system console output processing
8009 An error during system console output processing.
800C A failure in the timer task.
Fccc An error occurred; the system issued abend code ccc.
System action: The system prompts the operator for a reply.
Operator response: Do one of the following:
v To continue processing with MCS, reIPL the system with MCS.
v To request that processing continue without MCS, reply with any character. Note that in this case, all 3270 consoles
is non-functional, but programs that are processing that do not need to interact with a console operator are able to
continue.

When this message is issued, IT IS EXTREMELY IMPORTANT to respond promptly. This message is issued as a
synchronous WTOR, which will prevent the system from updating its status on the sysplex couple data set. This, in
turn, could lead to Sysplex Failure Management (SFM) deciding that the system is not responding normally, and
removing it from the sysplex.
System programmer response: If Fccc appears, see the system programmer response for the abend code ccc.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN701
Routing Code: Note 12
Descriptor Code: –

IEA368I INVALID RECORD IN memname. FIRST 17 BYTES ARE xxxxxxxxxxxxxxxxx

Explanation: During system initialization, the system found an incorrect record in the memname parmlib member.
The system cannot process the keyword.
In the message text:
memname 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.
System action: The system ignores the incorrect record and system initialization continues.
Operator response: Notify the system programmer. Provide the parmlib member name, memname, and the incorrect
record.
System programmer response: Correct the incorrect record in parmlib member memname.

Chapter 21. IEA messages 731

IEA370I • IEA376I

If the record is correct, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
Source: Initial program load (IPL)
Detecting Module: IEAIPL50

IEA370I MASTER CATALOG SELECTED IS MASTER CATALOG name

Explanation: The system issues this message during 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
Source: Nucleus initialization program (NIP)

IEA371I data-set ON DEVICE nnnn SELECTED FOR IPL PARAMETERS

Explanation: During system initialization, the system selected data set dataset containing the IPL parameters.
In the message text:
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)
Detecting Module: IEAIPL50
Routing Code: -
Descriptor Code: -

IEA372I module EXCLUDED FROM NUCLEUS

Explanation: An EXCLUDE statement in the NUCLSTxx parmlib member specified that module modname be
excluded from the nucleus.
In the message text:
module The module excluded from the nucleus.
System action: System initialization continues.
Source: Initial program load (IPL)
Detecting Module: IEAIPL42
Routing Code: -
Descriptor Code: -

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.

732 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA377D • IEA379I

Source: Auxiliary Storage Manager (ASM)

Detecting Module: ILRASRM2
Routing Code: Note 9
Descriptor Code: 4

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.
System action: The system waits for the operator to 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.

If VIO journaling is necessary, reIPL at the direction of the system programmer, specifying 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)
Detecting Module: ILRASRM2
Routing Code: Note 9
Descriptor Code: -

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.
System action: The IPL continues. The system will reject journaling requests for VIO data sets.
Operator response: If VIO journaling is necessary, re-IPL at the direction of the system programmer.
System programmer response: Ensure that VIO journaling is not required. If it is needed, specify VIODSN in
IEASYSxx.
Source: Auxiliary Storage Manager (ASM)
Detecting Module: ILRASRM2
Routing Code: Note 9
Descriptor Code: 4

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

Chapter 21. IEA messages 733

IEA380I • IEA382I

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.
Source: Auxiliary Storage Manager (ASM)
Detecting Module: ILRASRM2
Routing Code: Note 9
Descriptor Code: 4

IEA380I THIS SYSTEM IS NOW OPERATING IN STP TIMING MODE.

Explanation: This z/OS image is currently running in STP timing mode. It is a member of either a mixed CTN or
an STP-only CTN.
System action: The system continues processing.
Operator response: None.
User response: N/A
System programmer response: None.
Problem determination: N/A
Source: Timer supervision
Detecting Module: IEAVNP21, IEATCCCH, IEATSCSH
Routing Code: 10
Descriptor Code: 12
Automation: None.

IEA381I THE STP FACILITY IS NOT USABLE. SYSTEM CONTINUES IN LOCAL TIMING MODE
Explanation: Because the STP facility is not installed and enabled, the facility is not usable. The image continues in
Local timing mode.
System action: The system continues processing.
Operator response: Notify the System Programmer.
User response: N/A
System programmer response: Enable the STP facility on the server.
Problem determination: N/A
Source: Timer supervision
Detecting Module: IEAVNP21, IEATCCCH, IEATSCSH
Routing Code: 10
Descriptor Code: 12
Automation: None.

IEA382I THIS SERVER HAS ONLY A SINGLE LINK AVAILABLE FOR TIMING PURPOSES
Explanation: This server has a single link available to use for timing. This single link is a single point of failure.
System action: The system continues processing.
Operator response: Notify the System Programmer.

734 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA383I • IEA385I

User response: N/A

System programmer response: Provide an additional link or links to avoid a single point of failure.
Problem determination: N/A
Source: Timer supervision
Detecting Module: IEAVNP21, IEATEEIH
Routing Code: 10
Descriptor Code: 11
Automation: None.

IEA383I THIS SERVER RECEIVES TIMING SIGNALS FROM ONLY ONE OTHER NETWORK NODE.
Explanation: This server has timing links to only one other server. If the other server fails, this server will have no
source of timing and will lose its timing also.
System action: The system continues processing.
Operator response: Notify the System Programmer.
User response: N/A
System programmer response: Provide an additional link or links to avoid a single point of failure.
Problem determination: N/A
Source: Timer supervision
Detecting Module: IEAVNP21, IEATEEIH
Routing Code: 10
Descriptor Code: 12
Automation: None.

IEA384I SETETR COMMAND IS NOT VALID IN STP TIMING MODE.

Explanation: This command is not valid whe the z/OS image is in STP timing mode.
System action: The system ignores the command.
Operator response: None.
User response: N/A
System programmer response: None.
Problem determination: N/A
Source: Timer supervision
Detecting Module: IEATCMD
Routing Code:
Descriptor Code: 5
Automation: None.

IEA385I CLOCKxx ETRDELTA & TIMEDELTA BOTH SPECIFIED. yyyyyyy IGNORED.

Explanation: Both ETRDELTA and TIMEDELTA keywords were specified in the specified CLOCK member. Only
one and its value can be expected.
In the message text:
xx Identifier of the CLOCK parmlib member.

Chapter 21. IEA messages 735

IEA386I

yyyyyyy
One of the following:
v ETRDELTA
v TIMEDELTA
System action: The specified statement is ignored.
Operator response: Notify the System Programmer.
User response: N/A
System programmer response: Remove the ETRDELTA statement from the specified CLOCKxx parmlib member.
Problem determination: N/A
Source: Timer supervision
Detecting Module: IEAVNP20
Routing Code: 2
Descriptor Code: 12
Automation: None.

IEA386I

hh.mm.ss TIMING STATUS

SYNCHRONIZATION MODE=mode
THIS SERVER IS A STRATUM n
CTNID=ctnid
THE STRATUM 1 NODE ID=cpcid
NUMBER OF TIMING LINKS=ll
optional text
Explanation: In the message text:
hh.mm.ss
The hour (00-23), minute (00-59), and second (00-59) that the system issued this message.
mode
One of the following:
v STP
v ETR
v LOCAL
n
ctnid
cpcid
CPC node ID of the stratum 1 server (tttttt.mmm.nnn.pp.ssssssssssss)
ll The number of links, in decimal.
optional text
One or more of the following lines are issued:
v One of these optional lines can be issued, but only on the corresponding server type.
[THIS IS THE PREFERRED TIME SERVER]
[THIS IS THE BACKUP TIME SERVER]
[THIS IS THE ARBITER SERVER]
v If one of the three server type lines was issued, then one (or two) of the following lines might be issued.

736 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA387I

[THIS SERVER HAS NO LINK TO THE

BACKUP TIME SERVER]
[THIS SERVER HAS NO LINK TO THE
PREFERRED TIME SERVER]
[THIS SERVER HAS NO LINK TO THE
ARBITER SERVER]
v If one of the three server type line was issued, then one (or two) of these lines might be issued.
[THIS STP NETWORK HAS NO SERVER
TO ACT AS BACKUP]
[THIS STP NETWORK HAS NO SERVER
TO ACT AS ARBITER]
v The following two optional lines will never be issued on the active Primary Stratum 1 or active Alternate
Stratum 1 servers.
[THIS SERVER HAS ONLY A SINGLE SOURCE
OF TIMING SIGNALS]
[NUMBER OF USABLE TIMING LINKS = ll
v This optional line will only be issued on a Primary S1 or Alternate S1.
[THERE IS ONLY ONE LINK BETWEEN THE
PREFERRED AND BACKUP TIME SERVERS]
v One of these optional lines might be issued instead of any of the other optional lines.
[STP DATA NOT AVAILABLE AT THIS TIME.
TRY AGAIN LATER]
[THE STP FACILITY IS NOT AVAILABLE]
System action: The system continues processing.
Operator response: None.
User response: N/A
System programmer response: None.
Problem determination: N/A
Source: Timer supervision
Detecting Module: IEATDISP
Routing Code: *
Descriptor Code: 5
Automation: None.

IEA387I STP DATA CANNOT BE ACCESSED. SYSTEM CONTINUES IN yyyy TIMING MODE.
Explanation: Data from the STP facility is not available. The z/OS image continues in the specified timing mode.
In the message text:
yyyy
One of the following:
v STP
v ETR
v LOCAL

If the system continues in STP timing mode, it indicates that the I/O Configuration Control Authority (CCA) has
not been enabled for the LPAR.
System action: The system continues processing.
Operator response: None.
User response: N/A
System programmer response:

Chapter 21. IEA messages 737

IEA388I • IEA389I

Problem determination: N/A

Source: Timer supervision
Detecting Module: IEAVNP21, IEATEEIH, IEATCCCH, IEATSSCH
Routing Code: 10
Descriptor Code: 11
Automation: None.

IEA388I THIS SERVER HAS NO CONNECTION TO THE nnnnnnnnnn(The message text)

Explanation: The current server has no link to the specified special server. This reduces the ability of the timing
network to recover from certain failures.
In the message text:
nnnnnnnnnn
One of the following:
v BACKUP
v ARBITER
System action: The system continues processing.
Operator response: Notify the System Programmer.
User response: N/A
System programmer response: If possible, define the specified type of system to avoid single points of failure.
Problem determination: None.
Source: Timer supervision
Detecting Module: IEAVNP21, IEATCCCH
Routing Code: 10
Descriptor Code: 12
Automation: None.

IEA389I THIS STP NETWORK HAS NO SERVER TO ACT AS nnnnnnnnnn

Explanation: The STP-only CTN has had no server defined to be the specified special server. This reduces the ability
of the timing network to recover from certain failures.
In the message text:
nnnnnnnnnn
One of the following:
v BACKUP
v ARBITER
System action: The system continues processing.
Operator response: Notify the System Programmer.
User response: N/A
System programmer response: If possible, define the specified type of system to avoid single points of failure.
Problem determination: None.
Source: Timer supervision
Detecting Module: IEAVNP21, IEATCCCH
Routing Code: 10
Descriptor Code: 12

738 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA390I • IEA392I

Automation: None.

IEA390I TOD CLOCKS DYNAMICALLY ADJUSTED TO MAINTAIN STP SYNCHRONISM.

Explanation: The z/OS image has received an STP Synchronization check. The TOD clock has been adjusted to keep
it in synchronization with the rest of the timing network.
System action: The system continues processing.
Operator response: None.
User response: N/A
System programmer response: None.
Problem determination: None.
Source: Timer supervision
Detecting Module: IEATSSCH
Routing Code: 10
Descriptor Code: 4
Automation: None.

IEA391I TWO STP TIMING NETWORKS WITH THE SAME CTN ID HAVE BEEN DETECTED.
Explanation: The STP facility has detected that two timing networks with the same CTN ID have a connecting
timing link. These two networks do not have their clocks synchronized with each other.
System action: The link between the two networks is disabled.
Operator response: Notify the System Programmer.
User response: N/A
System programmer response: Remove the link which connects the two timing networks, or if there should be only
one timing network, correct the problem that caused two islands within the single network.
Problem determination: None.
Source: Timer supervision
Detecting Module: IEATSICH
Routing Code: 10
Descriptor Code: 11
Automation: None.

IEA392I STP TIME OFFSET CHANGES HAVE OCCURRED

Explanation: One or more of the time offset values has changed. These include leap seconds, local time, and
daylight savings time offsets.
System action: The system now uses the new offset(s).
Operator response: None.
User response: N/A
System programmer response: None.
Problem determination: N/A
Source: Timer supervision
Detecting Module: IEATEEIH
Routing Code: 10

Chapter 21. IEA messages 739

IEA393I • IEA394A

Descriptor Code: 11
Automation: None.

IEA393I ETR PORT n IS NOT OPERATIONAL. THIS MAY BE A CTN CONFIGURATION CHANGE.
Explanation: The specified External Time Reference (ETR) port is not working. This message is issued when the port
status changes and the port is found to be in a NON OPERATIONAL state regardless of whether the port is
ENABLED or DISABLED.
ETR is the generic name for the IBM Sysplex Timer (9037) or equivalent.
In the message text:
n is the port number
System action: The system continues processing. The system records the error in the logrec data set.
Operator response: One of the following:
v If a timing network configuration is underway, for example, a migration from a Mixed CTN to a STP-only CTN,
this message is expected and can be ignored.
v If an ETR is installed, check the hardware 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. The
same event might occur on more than one of the processors in a sysplex.
v If an ETR is not installed, ensure that the CLOCKxx member of SYS1.PARMLIB contains ETRMODE NO and
ETRZONE NO.
Source: Timer Supervision.
Detecting Module: IEATPORT
Routing Code: 10
Descriptor Code: 11

IEA394A THIS SERVER HAS LOST CONNECTION TO ITS SOURCE OF TIME. IF THIS EVENT
OCCURRED ON SOME, BUT NOT ALL NETWORK SERVERS, THE LIKELY CAUSE IS A LINK
FAILURE. TO FIX, ENSURE THAT EACH AFFECTED SERVER HAS AT LEAST ONE CORRECTLY
CONNECTED AND FUNCTIONAL LINK. IF THIS EVENT OCCURRED ON ALL NETWORK
SERVERS, THEN THE LIKELY CAUSE IA A TIMING NETWORK FAILURE. TO FIX, REFER TO
THE MESSAGE IEA394A DESCRIPTION IN MVS SYSTEM MESSAGES. AFTER FIXING THE
PROBLEM, REPLY "RETRY" FROM THE SERVICE CONSOLE (HMC). IF THE PROBLEM WAS
NOT CORRECTED, THIS MESSAGE is REISSUED AND YOU MAY TRY AGAIN. REPLY "ABORT"
TO EXIT THE MESSAGE LOOP. PROABLE RESULT: 0A2-158 WAITSTATE.
Explanation: The system no longer has access to the Current® Time Server. This may have happened because of the
loss of STP timing links or because there has been a failure of the Current Timer Server itself.
System action: The system waits for a reply to message IEA394A.
Operator response: Notify the system programmer.
System programmer response: Determine why the loss of the time source occurred, repair the problem and then
reply "RETRY" to the message on each system where it occurs. There are two basic scenarios for which this message
is issued.
It needs to be determined if a subset of the STP synchronized images have issued IEA394A or if ALL have issued it.
If only a few images issued message IEA394A, then it is likely that STP 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 is reissued until the problem is fixed or until it receives a
reply of "ABORT". A reply of "ABORT" will result in a 0A2-158 wait state if the image is a member of a multisystem
sysplex. If it is not, processing will resume in local TOD clock mode.

740 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA395I • IEA400I

Notes:
1. When all systems in the sysplex issue IEA394A there is no time limit for making the reply. However, after the first
response is given to IEA394A, the rest of the systems must be replied to within a minimum of four minutes.
When there are more than eight systems in the sysplex the time limit is calculated using (30 seconds * number of
systems).
2. If not all systems in the sysplex are affected, the systems that are still running can take action for "status update
missing" (SUM) on systems waiting for a reply to IEA394A. In this case, the four minute rule does not apply.

If all STP synchronized images issue message IEA94A, then there has been a failure of the Current Timer Server and
the Backup Timer Server has not been able to take over that function. In this case, it might be possible to manually
define the Backup as the Current Time Server from the HMC or to define a new Preferred Time Server and then
reply "RETRY" as previously described.

Note: When replying to IEA394A using the Hardware Management Console (HMC), you must select the priority
message box.
For more information, see the following IBM Redbooks publication:
v See the information about Current Time Server failure in Server Time Protocol Planning Guide, SG24-7280.
v See the information about recovery scenarios in Server Time Protocol Implementation Guide, SG24-7281

Also see the information about Understanding PLEXCFG Configurations with a Sysplex Timer in z/OS MVS Setting
Up a Sysplex. A Sysplex Timer failure can affect the sysplex in several ways, depending on how the sysplex is
configured with the PLEXCFG system parameter. This section provides additional information on PLEXCFG and
describes different conditions when this message might be issued (for example, with PLEXCFG=MULTISYSTEM and
PLEXCFG=ANY).
Source: Timer Supervision.
Detecting Module: IEATSCHSH

IEA395I THE CURRENT TIME SERVER HAS CHANGED TO THE cccccccccccc

Explanation: This message was received because the Current Time Server has changed from the Preferred Time
Server to the Backup Time Server or vice versa.
In the message text:
cccccccccccc
PREFERRED or BACKUP
System action: The system continues processing.
Operator response: Notify the System Programmer.
System programmer response: Determine what condition caused the switch. If appropriate to your installation,
correct the condition. For more details on the switch of time source, see Server Time Protocol Implementation guide,
SG24-7281.
Source: Timer Supervision.
Detecting Module: IEATCCCH
Routing Code: 10
Descriptor Code: 12

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:
v In the IEASYSxx parmlib member
v In the operator response to message IEA101A

In the message text:

value The incorrect NSYSLX value, which is less than 10 or greater than 512

Chapter 21. IEA messages 741

IEA401I • IEA402A

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 programmer response: Respecify the number of system linkage indexes 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
Routing Code: 2,10
Descriptor Code: 4

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.
In the message text:
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 system error occurred.
A STATUS STOP SRBS CONDITION WAS DETECTED
A system error occurred.
NO STORAGE AVAILABLE
The system could not acquire the storage needed to build the dump request; no dump was written.
UNKNOWN
A system error occurred.
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 programmer response: Determine why the 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 for the
problem. If no fix exists, contact the IBM Support Center.
Source: SVC dump
Detecting Module: IEAVTSIT
Routing Code: 10
Descriptor Code: 4

IEA402A REPLY ID PROCESSING ERROR. text

Explanation: Where text can be one of the following:
v XCF RETURN CODE xxxxxxxx, REASON CODE yyyyyyyy

742 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA403I • IEA404A

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.
v CDS IS UNAVAILABLE
During WTOR or DOM processing, the XCF sysplex couple data set became unavailable to access.
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.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center. If the problem is due to unexpected return codes from XCF, supply the XCF return and
reason codes.
Source: Master scheduler
Detecting Module: IEAVM616
Routing Code: 1
Descriptor Code: 2

IEA403I VALUE OF RMAX HAS BEEN CHANGED TO 99

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.
Operator response: Contact the system programmer.
System programmer response: Review the value of RMAX in CONSOLxx, and increase if necessary.
Detecting Module: IEAVM616
Routing Code: -
Descriptor Code: 4

IEA404A SEVERE WTO BUFFER SHORTAGE - 100% FULL

Explanation: The number of write to operator (WTO) messages is at the limit value specified in the MLIM
parameter of a CONSOLxx parmlib member.
System action: The system stops delivering informational messages to a console when there is a WTO buffer
shortage and/or when the console has a backlog of more than four screens of messages or 150 messages (whichever
is greater). During this condition, the backlogged consoles will receive only WTORs, action messages, and command
responses. Message CNZ3014I is issued to hardcopy to indicate that a console has become backlogged. Normal
message processing will resume when either the number of WTOs is reduced below the buffer limit or the console is
no longer backlogged.
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 clear the console’s message queue.
v Enter the CONTROL E,D command to delete a multiline message in an out of line area.
Note that messages already queued to a display area will not be deleted by a CONTROL Q.
v Enter CONTROL E,D to erase these messages if the CONTROL Q command does not relieve the shortage.
v Enter the CONTROL M,MLIM command to increase the value of the WTO buffer limit.
v Enter the CONTROL S,DEL=R command to 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.
v Use the D C,B command to determine which consoles are backlogged. Varying offline consoles that have a large
backlog of messages will release WTO buffers.

Chapter 21. IEA messages 743

IEA405E • IEA407I

System programmer response: Before the next system initialization, increase the value of MLIM in the CONSOLxx
parmlib member to increase the maximum number of WTO buffers that (S)MCS consoles can use.
Source: Communications task (COMMTASK)
Detecting Module: IEAVMQWR
Routing Code: 2,10
Descriptor Code: 2

IEA405E WTO BUFFER SHORTAGE - 80% FULL

Explanation: The number of write to operator (WTO) 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.
Operator response: Enter the DISPLAY CONSOLES command. If the console has accumulated a large number of
WTO messages, do one or more of the following:
v Enter the CONTROL Q command to purge 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.
v Respond to any messages requesting an operator action.
System programmer response: Before the next 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: Communications task (COMMTASK)
Detecting Module: IEAVMQWR
Routing Code: 2,10
Descriptor Code: 11

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.
System action: The system continues processing. The system resumes normal message processing.
Source: Communications task (COMMTASK)
Detecting Module: IEAVMQWR
Routing Code: 2,10
Descriptor Code: 4

IEA407I DIRECTORY ENTRY FOR MODULE mem INVALID IN SYS1.LPALIB

Explanation: The nucleus initialization program (NIP) found an incorrect directory entry for a member of
SYS1.LPALIB while attempting to build the link pack directory from SYS1.LPALIB.
In the message text:
mem A member of SYS1.LPALIB
System action: Processing continues with the next 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.

744 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA411I • IEA412I

Operator response: Notify the system programmer.

System programmer response: Determine the cause of the incorrect directory entry, and link-edit the member of
SYS1.LPALIB again, if necessary.
Source: System initialization (IPL/NIP)

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.
System action: The trap is disabled.
Source: SLIP
Detecting Module: IEAVTSLB
Routing Code: 10
Descriptor Code: 4

IEA412I 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.
– 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.
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.
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 z/OS MVS Programming: Authorized Assembler Services Reference LLA-SDU for details on the return and reason
codes.

In the message text:

xxxx The ID of the matching trap.
x The number of dumps that were not scheduled.
nn The return code from the first failing SDUMP 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 z/OS MVS Programming: Authorized
Assembler Services Reference LLA-SDU.
System action: The system continues processing, but does not write the requested SVC dumps.
Source: SLIP
Detecting Module: IEECB909

Chapter 21. IEA messages 745

IEA413I • IEA414I

Routing Code: 10
Descriptor Code: 4

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.

In the message text:

ID=xxxx
The SLIP trap identifier specified on the SLIP 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
Detecting Module: IEECB909
Routing Code: 10
Descriptor Code: 4

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.

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.
System programmer response: Do the following:
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.
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.

746 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA415I • IEA417I

3. 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 SVC dump. If an SVC dump is not produced with the abend, ask the operator to set
a SLIP to obtain an SVC dump.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTGLB, IEAVTPVT
Routing Code: 10
Descriptor Code: 4

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 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.
System programmer response: Do the following:
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 problem. If no fix
exists, report the problem to the IBM Support Center. Provide the SVC dump.
Source: SLIP
Detecting Module: IEAVTGLB
Routing Code: 10
Descriptor Code: 4

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.
System action: The system enters nonrestartable wait state X'023'.
Operator response: Notify the system programmer.
System programmer response: See the system programmer response for wait state X'023'.
Source: System Trace
Routing Code: 1
Descriptor Code: 2

IEA417I SLIP TRAP ID=xxxx ONE OR MORE SYSLIST ADDRESSES COULD NOT BE EVALUATED
Explanation: When processing the REMOTE keyword on a matched SLIP trap, one or more direct or indirect
addresses specified in the SYSLIST parameter could not be resolved. The reason could be that the address specified is
invalid, or points to storage that has not been allocated in the active or specified address space.

Chapter 21. IEA messages 747

IEA421E • IEA422I

Any addresses that could be evaluated were processed normally.

In the message text:
ID=xxxx
The SLIP trap identifier specified on the SLIP command.

This message is issued, at most, once per matched trap.

System action: The system continues SLIP trap processing. All addresses specified in the SYSLIST parameter are
considered, and any that evaluate successfully will still be processed.
Operator response: None.
Source: SLIP
Detecting Module: IEECB909
Routing Code: 10
Descriptor Code: 4

IEA421E START STOPPED PROCESSORS

Explanation: The system has recovered.
System action: The system continues processing. 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.
When this message is issued, IT IS EXTREMELY IMPORTANT to respond promptly. This message is issued as a
synchronous WTOR, which will prevent the system from updating its status on the sysplex couple data set. This, in
turn, could lead to Sysplex Failure Management (SFM) deciding that the system is not responding normally, and
removing it from the sysplex.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVNP51, IECVIRST, IECVFCHN
Routing Code: 1,10,Note 12
Descriptor Code: 11

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.
System programmer response: Do the following:
1. Enter the SLIP trap again, specifying either:
v ACTION=IGNORE ASID=NONE to ignore the address space on the SLIP trap.
v ASID=asid to trap the address space.
2. If the problem continues, 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 SVC dump, the logrec data set error records, and messages.
Source: SLIP
Detecting Module: IEAVTJBN
Routing Code: 10

748 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA423I • IEA425I

Descriptor Code: 4

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.
System programmer response: 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 logrec data set error record and messages.
Source: Recovery termination manager (RTM)
Detecting Module: IEECB915
Routing Code: 10
Descriptor Code: 4

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 are incorrect.
System action: The system issues messages about the problem.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, report
the problem to the IBM Support Center.
Source: SLIP
Detecting Module: IEAVTGLB
Routing Code: 10
Descriptor Code: 4

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-set-initiated 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 continues processing.
Operator response: Notify the system programmer.
System programmer response: Make sure the SLIP trap was specified correctly.
Source: SLIP
Detecting Module: IEECB909

Chapter 21. IEA messages 749

IEA426I • IEA430E

Routing Code: 4
Descriptor Code: 5

IEA426I SLIP TRAP ID=xxxx ACTION=SYNCSVCD CANNOT BE PERFORMED; ACTION=SVCD DONE.

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.

In the message text:

ID=xxxx
The SLIP trap identifier specified on the SLIP command.
System action: The system schedules an SVC dump. The interrupted unit of work regains control and the system
continues processing.
Operator response: Reset the SLIP trap, as specified by the system programmer.
System programmer response: Do one of the following:
v If the PER interrupt occurred for an incorrect event, ask the operator to reset the trap and specify additional
filtering keywords.
v Verify that the interrupt did not occur on an instruction that would result in disabled, locked, or SRB mode, such
as an SVC instruction. If it did, it needs to be reset to an instruction that does not cause disabled, locked, or SRB
mode.
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
Routing Code: 10
Descriptor Code: 4

IEA430E 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.
In the message text:
dev
The device number.
ac Action code X'5' or X'B'.
System action: The system continues processing.
Operator response: See the book for the device type for an explanation of the action code. Contact hardware
support, if needed.
Source: Input/output supervisor (IOS)
Detecting Module: IGE0002G
Routing Code: 7

750 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA431A • IEA434I

Descriptor Code: 4

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.
In the message text:
dev
The device number.
cc Action code X'2', X'6', or X'B'.
System action: The system issues the failing channel command word (CCW) again.
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.
Source: Input/output supervisor (IOS)
Detecting Module: IGE0002G
Routing Code: 7
Descriptor Code: 4

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.
In the message text:
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.
Source: Communications task (COMMTASK)
Detecting Module: IEAVG607
Routing Code: -
Descriptor Code: 12

IEA434I DEVICE ONLINE IS NOT ALLOWED, reason

Explanation: During VARY ONLINE command processing, the device service exit determined that the device was
not allowed to be online for the specified reason.
In the message text:
reason One of the following reasons:
v PPRC SECONDARY
v SPARE DEVICE
v DUAL COPY SECONDARY
v GREATER THAN 65520 CYL
v SW FUNCTION REQUESTED OFFLINE
v devcyls CYL (MAX IS maxcyls)
Where devcyls is the size of the target device in cylinders, and maxcyls is the maximum number of
cylinders supported by the installed version of z/OS. For non-EAV, maxcyls is 65520.
v SSCB TABLE ENTRIES EXCEEDED
System action: The device remains offline.

Chapter 21. IEA messages 751

IEA435I

Operator response: None

System programmer response: Check the system configuration to determine if the device number is correct.
Source: DFSMSdfp
Detecting Module: IECDINIT

IEA435I 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 the hardware configuration definition (HCD).
In the message text:
pdevtype
The physical device type.
ldevtype
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. Possible reasons follow.
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 attached to the system.
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.
System Programmer Response: Correct the HCD device definitions to match the device type of the device
physically attached to the system.
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, DFSMSdfp
issues this message.
System Programmer Response: Install the required maintenance.
3590–H DRIVE DETECTED BUT NOT ALL 3590–H SUPPORT IS PRESENT
Support for the 3590 Model H was shipped as program temporary fixes (PTFs) on DFSMS 1.4.0 and 1.5.0. If
these PTFs are not installed, DFSMSdfp issues this message.
System Programmer Response: Install the required maintenance.
3592-2 DRIVE DETECTED BUT NOT ALL 3592-2 SUPPORT IS PRESENT
Support for the 3592 Model E05 is introduced with z/OS V1R4. MEDIA9 and MEDIA10 support begins with
z/OS V1R5. If all the support code for these models is not installed, this message is issued.
System Programmer Response: Install the required maintenance.
3592-3E DRIVE DETECTED BUT NOT ALL 3592-3E SUPPORT IS PRESENT
Support for the 3592 Model E06 was shipped as program temporary fixes (PTFs) on z/OS DFSMS V1R7 and
later releases. If these PTFs are not installed, DFSMSdfp issues this message.
System Programmer Response: Install the required maintenance.

752 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA436I • IEA437I

| 3592-4E DRIVE DETECTED BUT NOT ALL 3592-4E SUPPORT IS PRESENT

| Support for the 3592 Model 4E was shipped as program temporary fixes (PTFs) on z/OS DFSMS V1R9 and
| later releases. If these PTFs are not installed, DFSMSdfp issues this message.
| System Programmer Response: Install the required maintenance.
3592-J DRIVE DETECTED BUT NOT ALL 3592-J SUPPORT IS PRESENT
Support for the 3592 Model J was shipped as program temporary fixes (PTFs) on OS/390 DFSMS 2.10 and
z/OS DFSMS 1.3 and later releases. If these PTFs are not installed, DFSMSdfp issues this message.
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.
System Programmer Response: 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 Programmer Response: Correct the HCD device definitions to match the device type of the device
physically attached to the system.
UNKNOWN DEVICE IN EMULATION MODE NOT BROUGHT ONLINE
Read Device Characteristic I/O was successfully issued to the device and the resulting information indicates
a device type that is not recognized by the system.
System Programmer Response: None. The device is not supported and cannot be brought online.
System action: The device 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.
In the message text:
dev The number of the failing ATLDS device
text One of the following:

Chapter 21. IEA messages 753

IEA437I

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
The hardware communication path between the tape control unit and the library manager has been
established, but the library manager returned an incorrect library-id (zeros) to the host.
Recovery Action: Contact your hardware 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).
Recovery Action: Contact your hardware service representative to determine the cause of the RDC
failure.
UNAVAILABLE TO LIBRARY MANAGER
The hardware communication path between the tape control unit and the library manager has been
established, but the library manager has 'marked' the device unavailable.
Recovery Action: Contact your hardware 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 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
34905434905400E0 1FD8808004000000 00000000 00000000
0BA0670100000000 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.

Recovery Action: Correct either the hardware or HCD. If the hardware was in 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.

754 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA437I

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 is a different device type than those
that were previously defined for the same string.
Recovery Action: Correct either the hardware or HCD. If the hardware was in error (or was incorrectly
attached to the system), correct the hardware and then vary the device online. Use the DS QT,dddd,RDC
command 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.
TAPE LIBRARY DEVICE aaaa (bbbbb-cc) EMULATING 3490 NOT ALLOWED ONLINE IN AN MTL.
The tape drive at address aaaa, with HCD defined LIBRARY-ID bbbbb and 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.
Recovery Action: Review the HCD 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.
The tape drive at address aaaa, with HCD defined LIBRARY-ID bbbbb and LIBPORT-ID cc, is attached to
a control unit different than that for devices already in the pool. The device is not allowed online.
Recovery Action: Review the HCD 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.
If you are replacing old or broken hardware with new hardware, all of the devices in the device pools
affected by the hardware change must be OFFLINE. If any of the devices fail to go OFFLINE or are in
PENDING OFFLINE, and the drives are not in use by the system, cause the devices to become
OFFLINE and BOXED by issuing the VARY OFFLINE,FORCE command. After all of the devices are offline,
you can replace the hardware.
TAPE LIBRARY DEVICE aaaa (bbbbb-cc) NOT ALLOWED ONLINE, UNABLE TO ADD LIBRARY TO CONTROL BLOCK.
| The tape drive at address aaaa, with HCD defined LIBRARY-ID bbbbb and LIBPORT-ID cc, cannot be
| added to the existing device pool because it is full (that is, it already has 16 devices defined) or because
| the number of device pool subsystems has reached the library limit of 128. The device is not allowed
| online. The MTL device pool subsystem limit remains at 32.
| Recovery Action: Review the HCD definition for the device, and other devices with the same
| LIBRARY-ID and LIBPORT-ID values. Ensure that MTL devices are not overgenned.
PROBLEM OBTAINING DISTRIBUTED LIBRARY DATA. LIBRARY MAY BE IN SERVICE MODE.
During initialization of a device in a Peer-to-Peer VTS or the TS7700 Virtualization Engine, the I/O
operation requesting configuration data for the distributed library either failed or returned invalid
information. Also, for a device associated with the TS7700 Virtualization Engine, it could also mean that
the library is in service mode. This message is issued when an RDC command returned data indicating
that the device is in a Peer-to-Peer VTS library or in a TS7700 Virtualization Engine. However, the
subsequent request to obtain configuration data failed or returned invalid data.
Recovery Action: Contact your hardware service representative to determine the cause of the failure.
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

Chapter 21. IEA messages 755

IEA438I • IEA439I

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]]
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 are listed in this message.
Devices that are displayed with an asterisk become available when the error has been corrected, without an IPL or
I/O activate request being required.
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 is 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 becomes 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

IEA439I TAPE LIBRARY (libid), text

Explanation: AOM Library Services (LIBSERV) has detected a tape library error condition.
In the message text:
libid The 5-digit library identifier (serial number).
text One of the following:
RETURNED INCORRECT AFFINITY DATA
Affinity data is only used for the 3494 and 3495 tape library. This error message indicates that an
installation error or microcode error has caused the 3494 or 3495 to report incorrect volume affinity data.
Volume affinity data is an ordered list of subsystem port ids that are used by host software to control
device allocation. The ordered list allows the library manager (LM) to direct host allocations to the most
appropriate subsystem. The error that has been detected is that the port ids in the affinity list do not
match those that are known to the host. Port ids that are known to the host are obtained from the
library during IPL or device VARY. As an example, if the library contains subsystems with port ids
01,02,03,04, those port ids would be known to the host, and an ordered list from the LM might correctly
contain 03,02,01,04. The correct list indicates that a device from subsystem 03 should be allocated if
possible, followed in preference by 02, 01 and 04. In the error case, the ordered list from the LM might
incorrectly contain 03,04,05,06. Because port-ids 05 and 06 are unknown to the host, they cannot be
used.
DEVICE(dev) FOUR MINUTE I/O TIMEOUT
A library request was issued to library (libid) using device (dev) and the I/O for the request did not
complete within 4 minutes. The system will attempt to recover the failed I/O by selecting another
device in the library. If the I/O is successfully recovered, no permanent error is posted. However, if a
second 4 minute timeout occurs, a second IEA439I message is issued and the library request is posted in
error.
DEVICE(dev) 6D STATE SAVE ISSUED
dev
The device number of the failing ATLDS device.

756 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA441I • IEA442E

To help diagnose the cause of the 6D DEMOUNT error, an X'87' CCW was issued to the device in order
to obtain a hardware state save. In order for an X'87' CCW to cause a state save, the hardware service
representative must have first prepared the hardware to take state save.

Recovery Action:
v For INCORRECT AFFINITY DATA, contact your hardware service representative to resolve the cause of the
incorrect volume affinity data. After the error condition is corrected, the host begins to use the corrected LM
affinity list (host IPL is not required).
v For FOUR MINUTE I/O TIMEOUT, if this condition persists, contact your hardware service representative to
resolve the cause of the 4 minute timeouts.
v For DEVICE(dev) 6D STATE SAVE ISSUED, in order to obtain diagnostic data, should more 6D demount errors
occur, have the hardware representative prepare the device to take state save.
System action:
v For INCORRECT AFFINITY DATA, allocations will not fail. Library allocations are made using a software
generated 'affinity' list. The generated list will contain all of the port ids available to the system, in the order that
they were initialized. Because the affinity list provides load balancing in the library, until the error is corrected,
library performance can be affected.
v For FOUR MINUTE I/O TIMEOUT, if the I/O is successfully recovered then there is no impact on the system
(other than the 4 minute delay). If the retry of a FOUR MINUTE I/O TIMEOUT receives another FOUR MINUTE
I/O TIMEOUT, the I/O request is posted in error. The impact of the error on the system depends on the library
request that failed and which component made the request. Refer to additional messages issued by the system
component that made the request.
v For DEVICE(dev) 6D STATE ISSUED, the system will continue to use the device. If a volume is found to be
mounted when the device is next used, the volume is demounted.
Source: AOM Tape Library Services(LIBSERV)
Detecting Module: IGX00044
Routing Code: 2
Descriptor Code: 4

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 installation's procedures for reporting this error.
Source: Asynchronous Operation Manager Attention Processing Routine for Tape Devices (AOMATTNT)

IEA442E dev REPORTS DISABLED INTERFACE ON nn -- FAULT CODE = cccc -- NOTIFY CE, SENSE=sense
Explanation: An I/O request failed because a storage director within a 3880 Storage Control Unit is disabled. In the
message text:
dev The address of the I/O device that reported the disabled status of storage director.
nn The disabled storage director identifier.
cccc The fault code that explains why the storage director is disabled.

Chapter 21. IEA messages 757

IEA447E • IEA448I

sense The 32 characters of sense data reported by the device.

xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
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.
Operator response: Do the following:
v Isolate the failing control unit. Contact hardware support to repair it.
v If only one unit remains, transfer critical applications to back-up.
v Identify and recover failing tasks.
Source: DFSMSdfp
Detecting Module: IECVDERP, IGGSNS01
Routing Code: 2,10
Descriptor Code: 11

IEA447E PATH chp TO DEVICE s-cc-d UNAVAILABLE

Explanation: The system cannot reach a device through a path. A hardware error occurred, or the data path switch
for the device is open.
In the message text:
chp The identifier (CHPID) of the unavailable channel path.
ss-cc-d The identifier of the storage director that found the problem.
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.
Operator response: If the data path switch is open, close it. Otherwise, do the following:
v Isolate the failing control unit. Contact hardware support to repair it.
v If only one unit remains, transfer critical applications to back-up.
v Identify and recover failing tasks.
Source: DFSMSdfp
Detecting Module: IGGSNS01

IEA448I 1,SENSE DATA LOGGED FOR DEVICE ss.p-xx-xx SENSE=sense

2,SENSE DATA LOGGED FOR

CONTROLLER ss.p-xx-xx
SENSE=sense
Explanation: The specified device or controller has returned environmental data. The data has been written to the
logrec data set. Message 1 is displayed when sense byte 28 = X'01' and byte 22 = X'00'. Message 2 is displayed when
sense byte 28 = X'02' and byte 22 = X'00'.
In the message text:
ss Subsystem ID (SSID)
ss.p SSID storage path
xx-xx Controller device
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: Processing continues.
Source: DFSMSdfp
Detecting Module: IGGSNS01

758 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA449A • IEA451I

Routing Code: 1,6

Descriptor Code: 4

IEA449A RESET WRITE INHIBIT SWITCH ON PAGING DEVICE - device-number SENSE=sense

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 0
1 or 9 1
2 or A 2
3 or B 3
4 or C 4
5 or D 5
6 or E 6
7 or F 7

In the message text:

device-number
The path ID of the path that reported the error.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
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.
This message can be followed by another IEA449A message after you have set the switch; reply ‘U’ to this second
IEA449A to continue processing.
Application Programmer Response: None.
Source: DFSMSdfp
Detecting Module: ERPs
Routing Code: 1,6
Descriptor Code: 2

IEA451I {MICROCODE LOGICAL|SUBSYSTEM PROCESSING} ERROR - FAULT CODE = cccc-ss.p-xx-xx

SENSE=sense
Explanation: An internal logic error occurred during a subsystem storage operation on a Storage Control device
with a cache.
In the message text:
cccc The fault symptom code from sense bytes 22 and 23.
ss.p-xx-xx
The physical identifier of the reporting storage director.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
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.

Chapter 21. IEA messages 759

IEA452I • IEA453I

Operator response: The system issues this message because of a microcode error. Follow installation procedures to
take corrective action.
Application Programmer Response: If the error 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
Routing Code: 1,6
Descriptor Code: 11

IEA452I SUBSYSTEM STORAGE EQUIPMENT CHECK - FAULT CODE = cccc-ss.p-xx-xx SENSE=sense

Explanation: An equipment check occurred during a subsystem storage operation on the 3880 Storage Control with
a cache.
In the message text:
cccc The fault symptom code from sense bytes 22 and 23.
ss.p-xx-xx
The physical identifier of the reporting storage director.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: The system ends I/O processing for this request.
Operator response: The system issues this message because of a hardware error. Follow installation procedures to
take corrective action.
Application Programmer Response: None.
Source: DFSMSdfp
Detecting Module: IGGSNS01
Routing Code: 1,6
Descriptor Code: 4

IEA453I {SUBSYSTEM|NVS} STORAGE AVAILABILITY THRESHOLD CROSSED -ss.p-xx-xx SENSE=sense

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.
In the message text:
ss.p-xx-xx
The physical identifier of the reporting storage director.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: The error recovery procedure (ERP) reissues the channel command words (CCW) that failed.
Operator response: The system issues this message 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.
Application Programmer Response: None.
Source: DFSMSdfp
Detecting Module: IGGSNS01
Routing Code: 1,6
Descriptor Code: 4

760 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA454E • IEA457I

IEA454E SUBSYSTEM STORAGE IS UNUSABLE - FAULT CODE = cccc-ss.p-xx-xx SENSE=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.
In the message text:
cccc The fault symptom code from sense bytes 22 and 23.
ss.p-xx-xx
The physical identifier of the reporting storage director.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: The system ends I/O processing for this request. If the problem 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 hardware error. Follow installation procedures to
take corrective action.
Application Programmer Response: If the problem 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
Detecting Module: IGGSNS01
Routing Code: 1,6
Descriptor Code: 11

IEA455E SUBSYSTEM STORAGE MUST BE INITIALIZED - FAULT CODE = cccc-ss.p-xx-xx SENSE=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.
In the message text:
cccc The fault symptom code from sense bytes 22 and 23.
ss.p-xx-xx
The physical identifier of the reporting storage director.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: The system ends I/O processing for this request.
Operator response: The system issues this message because of a hardware error. System IPL might be required to
continue operations. System IPL is required to reinitialize the storage for this subsystem. Follow installation
procedures to take corrective action.
Application Programmer Response: If the subsystem storage remains unusable following the system IPL,
reconfigure the system to move the paging data to another subsystem.
Source: DFSMSdfp
Detecting Module: IGGSNS01
Routing Code: 1,6
Descriptor Code: 11

IEA457I TRACK FORMAT NOT SUPPORTED FOR PAGING - ss.p-xx-xx SENSE=sense

Explanation: The 3880 Storage Control Model 11 or 21 detected an incorrect track format or no-record-found error.
In the message text:

Chapter 21. IEA messages 761

IEA458I • IEA459I

ss.p-xx-xx
The physical identifier of the reporting storage director.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: The error recovery procedure (ERP) reissues the channel command words (CCW) that failed.
Operator response: Notify the system programmer.
Application Programmer Response: Format the paging packs attached to the paging storage director of the 3880
Model 11 or 21.
System programmer response: 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.
Source: DFSMSdfp
Detecting Module: IGGSNS01
Routing Code: 1,6
Descriptor Code: 4

IEA458I STORAGE DIRECTOR COMMUNICATION FAILED - FAULT CODE = cccc-ss.p-xx-xx SENSE=sense

Explanation: The 3880 cache control unit storage directors cannot communicate.
In the message text:
cccc The fault symptom code from sense bytes 22 and 23.
ss.p-xx-xx
The physical identifier of the reporting storage director.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: The error recovery procedure (ERP) reissues the channel command words (CCW) that 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.
Application Programmer Response: None.
Source: DFSMSdfp
Detecting Module: IGGSNS01
Routing Code: 1,6
Descriptor Code: 4

IEA459I CACHING [RESET-REDEFINE BOUND AREAS/NON-CACHING DEVICES| REINITIATED] -

ss.p-xx-xx SENSE=sense
Explanation: Caching was automatically reinitialized by the 3880 Storage Control following a storage director
communication timeout or a subsystem storage control structure failure.
In the message text:
ss.p-xx-xx
The physical identifier of the reporting storage director.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: The error recovery procedure (ERP) reissues the channel command word (CCW) that received the
message.

762 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA460W • IEA461I

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.
Application Programmer Response: None.
Source: DFSMSdfp
Detecting Module: IGGSNS01

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.
In the message text:
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.
System action: The system enters a non-restartable wait state.
Operator response: Provide a stand-alone dump, if requested by the system programmer.
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 stand-alone dump.
Source: Supervisor Control
Detecting Module: IEAVEGR

IEA461I dev INCORRECT USE OF SUMMARY UNIT CHECK SUPPORT WITH z/OS GUESTS ON VM.
REFER TO MESSAGES AND CODES FOR MORE DETAIL,
SENSE=xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
Explanation: z/OS is a guest under z/VM and one or more devices are defined to z/VM as unsupported. The
control unit has been enabled for Summary Unit Check which will not be processed correctly by z/OS. This will
cause access problems to devices in the 2107 control unit.
In the message text:
dev
The device number
sense
The 32 characters of sense data reported by the device.
Operator response: Notify the system programmer.
System programmer response: Correction of the z/VM and z/OS configuration must occur to allow for proper
handling of the use of Summary Unit Check. To allow for proper handling of the Summary Unit Check, you have the
following options:
v Attach all unsupported devices to a single VM Guest.
v Attach unsupported devices to multiple z/OS guests with the maintenance introducing this message propagated to
all z/OS systems.
v Define All devices behind a Logical Control Unit as unsupported. Devices can not be defined to z/VM as some
supported and some unsupported.
Detecting Module: IGGSNS01

Chapter 21. IEA messages 763

IEA466I • IEA467E

IEA466I PATH(dev,chp) PERMANENT I/O ERROR {sense|yyyy, zz}

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.
yyyy The device and channel status at time of error.
zz The IOSCOD (completion code) for the IOS request.
System action: The system varies the path offline.
Operator response: Do the following:
v Isolate the failing control unit. Contact hardware support to repair it.
v If only one unit remains, transfer critical applications to back-up.
v Identify and recover failing tasks.
Source: DFSMSdfp
Detecting Module: IECVDERP
Routing Code: 1,4,6,8
Descriptor Code: 4

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.
In the message text:
dev The device number.
chp The channel path identifier (CHPID).
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:
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.
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.
v Vary online at least one path to the device.
v Vary the device online, making sure that no jobs allocate the pack.
v Enter an ICKDSF CONTROL WRITEALLOW command, directing it to one device attached to the failing
interface.
v Vary online all paths that the system varied offline.
4. If paths remain online, do the following:

764 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA468I • IEA469E

v Enter an ICKDSF CONTROL WRITEALLOW command, directing it to one device attached to the failing
interface.
v Vary online all paths that the system varied offline.
Source: DFSMSdfp
Detecting Module: IECVDERP
Routing Code: 1,6
Descriptor Code: 11

IEA468I WRITE INHIBITED PATH (dev,chp) ENCOUNTERED SENSE=sense

Explanation: The system tried to issue I/O to a device through a path that was write inhibited.
In the message text:
dev The device number.
chp The channel path identifier (CHPID).
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
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 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.
v Vary online at least one path to the device.
v Vary the device online, making sure that no jobs allocate the pack.
v Enter an ICKDSF CONTROL WRITEALLOW command, directing it to one device attached to the failing
interface.
v Vary online all paths that the system varied offline.
4. If paths remain online, do the following:
v Enter an ICKDSF CONTROL WRITEALLOW command, directing it to one device attached to the failing
interface.
v Vary online all paths that the system varied offline.
Source: DFSMSdfp

IEA469E {PATH (dev,chp) HAS BEEN VARIED OFFLINE| PATH (dev,chp) CANNOT BE VARIED OFFLINE}
SENSE=sense
Explanation: A hardware error occurred. Recovery for the direct access storage device (DASD) determined that a
path should be varied offline.
In the message text:
dev The device number.
chp The channel path identifier (CHPID).
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx

Chapter 21. IEA messages 765

IEA473I • IEA474E

System action: If the path is online, the system retries the failing channel command word (CCW) chain on another
path to the same device.
Depending on the message text, one of the following:
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
Detecting Module: IECVDERP
Routing Code: 1,6
Descriptor Code: 11

IEA473I vvvvvv FENCED FROM STORAGE PATH x - device-number/ssid.p-cc-nn SENSE=sense

Explanation: A device is unavailable through a storage path due to a hardware error.
In the message text:
vvvvvv The volume that failed.
x The storage path fenced.
device-number
The physical device address.
ssid The subsystem identifier.
p The storage path.
cc The controller address.
nn The device number.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: The subsystem attempts to recover the operation using an alternate path.
Operator response: The system issues this message because of a hardware error. Follow your installation's
procedures for reporting this error.
Source: DFSMSdfp
Detecting Module: IGGSNS01
Routing Code: 1,6
Descriptor Code: 4

IEA474E NONVOLATILE STORAGE UNUSABLE - ccu/ssid.p-xx-xx SENSE=sense

Explanation: The nonvolatile storage failed or could not be initialized.
In the message text:
device-number
The physical device address.
ssid The subsystem identifier.
p The storage path.
sense The 32 characters of sense data reported by the device.

766 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA475E • IEA476E

xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx

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.
Operator response: The system issues this message because of a hardware error. Follow your installation's
procedures for reporting this error.
Source: DFSMSdfp
Routing Code: 1,6
Descriptor Code: 4

IEA475E vvvvvv IS SUSPENDED DUPLEX {PRI|SEC} FAILED|INTERVENTION REQUIRED - ccu/ssid.p-cc-nn

SENSE=sense
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.
In the message text:
vvvvvv The volume that failed.
device-number
The physical device address.
ssid The subsystem identifier.
p The storage path.
cc The controller address.
nn The device number.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: Processing will continue in suspended duplex mode.
Operator response: The system issues this message because of a hardware error. Follow your installation's
procedures for reporting this error. If the device associated with this message is attached via the IBM 3990 Model 3 or
Model 6 Storage Control, see IBM 3990/9390 Operations and Recovery Guide for detailed recovery actions.
Source: DFSMSdfp
Detecting Module: IGGSNS01
Routing Code: 1,6
Descriptor Code: 11

IEA476E vvvvvv ACCESS PROHIBITED - RC=(reason-code) device-number/ssid.p-cc-nn SENSE=sense

Explanation: The status of the subsystem or a device cannot be determined. Access is not allowed until the problem
is corrected.
In the message text:
vvvvvv The volume that failed.
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
The physical device address.
ssid The subsystem identifier.
p The storage path.

Chapter 21. IEA messages 767

IEA477I • IEA478E

cc The controller address.

nn The device number.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: The system ends I/O processing for this request.
Operator response: The system issues this message because of a hardware error or configuration problem. Follow
your installation's 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.
Source: DFSMSdfp
Detecting Module: IGGSNS01
Routing Code: 1,6
Descriptor Code: 11

IEA477I vvvvvv PERMANENT DATA CHECK ON PRIMARY - RECOVERED ON SECONDARY

device-number/ssid.p-cc-nn SENSE=sense
Explanation: A permanent read data check on the primary device of a duplex pair was recovered by reading the
secondary device.
In the message text:
vvvvvv The volume that failed.
device-number
The physical device address.
ssid The subsystem identifier.
p The storage path.
cc The controller address.
nn The device number.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: Processing continues.
Operator response: Follow your installation's 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 detailed recovery actions information
in the IBM 3990/9390 Operations and Recovery Guide.
Source: DFSMSdfp
Detecting Module: IGGSNS01
Routing Code: 1,6
Descriptor Code: 4

IEA478E PINNED DATA FOR vvvvvv - device-number/ssid.p-cc-nn SENSE=sense

[CONTINUATION OF IEA478E
SNS=sense]
Explanation: A permanent hardware error occurred during a destage operation. The data is pinned in
cache/nonvolatile storage.
In the message text:
vvvvvv The volume that failed.

768 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA479E

device-number
The physical device address.
ssid The subsystem identifier.
p The storage path.
cc The controller address.
nn The device number.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: Processing continues.
Operator response: The system issues this message because of a hardware error. Follow your installation's
procedures for reporting this error. If the device associated with this message is attached via the IBM 3990 Model 3 or
Model 6 Storage Control, see IBM 3990/9390 Operations and Recovery Guide for detailed recovery actions.
Source: DFSMSdfp
Routing Code: 1,6.
Descriptor Code: 4

IEA479E vvvvvv =X'cccCCCC' NOT CORRECT FOR DESTAGE - RC=(rc) device-number/ssid.p-cc-nn

SENSE=sense
Explanation: An attempt to write data from cache to DASD encounters a DASD track format incompatible with the
operation.
In the message text:
vvvvvv The volume that failed.
cccCCCC:H
Normalized hexadecimal cylinder/head address of the failing track.
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
The physical device address.
ssid The subsystem identifier.
p The storage path.
cc The controller address.
nn The device number.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
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 installation's 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.
Source: DFSMSdfp
Detecting Module: IGGSNS01

Chapter 21. IEA messages 769

IEA480E (form 1 of 2)

IEA480E (form 1 of 2) 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, TRACK=x'cccc hhhh', REPEATED SENSE=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.
In the message text:
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.
DASD Storage device hardware.
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:
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 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.
cccCCCC:H
MEDIA ALERTs only. Normalized 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 The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: The system logs an alert in the LOGREC data set and continues processing.
Operator response: The system issues this message to indicate that operator or service attention is required. Follow
your installation's 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

770 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA480E (form 2 of 2)

Detecting Module: IGGSNS01

Routing Code: 1,6
Descriptor Code: 2,4

IEA480E (form 2 of 2) 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.
In the message text:
yyyy Address of unit that reported the SIM message.
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 might 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.
REPEATED
Indicates this SIM has already been presented at least once prior to this presentation.
System action: The system logs an alert in the LOGREC data set and continues processing.
Operator response: The system issues this message to indicate that operator or service attention is required. Follow
your installation's procedures for obtaining service. Consult your customer engineer, if applicable.
If the specified unit is TAPE and CLEAN is presented (or ES=89), then cleaning is required. Note that some 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.

Chapter 21. IEA messages 771

IEA481I • IEA482I

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 engineer for detailed recovery actions for the installed VTS
product.
If the specified unit is TCU, then consult your customer engineer for detailed recovery actions for the installed tape
control unit.
System programmer response: Run an EREP System Exception Report to obtain a Service Information Message
report for additional information.
Source: DFSMSdfp
Detecting Module: IGGSNS02
Routing Code: 1, 6
Descriptor Code: 2, 4 for ACUTE ALERT
4 for other ALERT

IEA481I CONTROLLER NOT OPERATIONAL WITH STORAGE PATH - device-number/ssid.p-cc-nn

SENSE=sense
Explanation: The specified DASD controller cannot be accessed through the specified storage path.
In the message text:
device-number
The physical device address.
ssid The subsystem identifier.
p The storage path.
cc The controller address.
nn The device number.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: Processing continues.
Operator response: The system issues this message because of a hardware error. Follow your installation's
procedures for reporting this error. If the device associated with this message is attached via the IBM 3990 Model 3 or
Model 6 Storage Control, see IBM 3990/9390 Operations and Recovery Guide for detailed recovery actions.
Source: DFSMSdfp
Detecting Module: IGGSNS01
Routing Code: 1,6
Descriptor Code: 4

IEA482I ser WAITING FOR CONTROL UNIT - dev, REASON CODE=(nn) SENSE=sense
Explanation: I/O was attempted to a DASD device whose control unit is in a long-busy condition. This busy
condition might last for several minutes; the additional messages may describe the reason code for the long-busy
condition and the appropriate Operator Response. Under normal recovery most of the reason codes listed below
should only last for a short period of time. If a long-busy condition has recovered then no message is issued.

772 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA482I

Note: Reason Code X'0F' may last for an extended period of time.
In the message text:
ser Volume serial number.
dev DASD device number.
nn Reason Codes and additional message text are:
Reason Code
Additional Message Text
00 NO REASON CODE DEFINED
No further information is provided by the hardware.
01 EMERGENCY DESTAGE IN PROGRESS
A possible hardware problem has occurred requiring an emergency destage of the data. Contact
hardware support for further assistance.
02 DIAGNOSTIC REINITIALIZATION
The control unit is performing a recovery function.
07 COMMIT ORDER WAS RECEIVED
The control unit is currently committing all writes in cache to the drive(s).
0C CONCURRENT COPY SIDEFILE EXCEEDING LIMITS
The control unit is transferring data from cache to the hardware because the storage cache
thresholds have been exceeded.
0D XRC SIDEFILE EXCEEDING LIMITS
The control unit is transferring data from cache to the hardware because the storage cache
thresholds have been exceeded.
0E PPRC QUIESCE ORDER ISSUED TO THE DEVICE
The control unit is busy until the PPRC Pair has been terminated.
0F RESERVE ISSUED TO XRC UTILITY DEVICE
A reserve is issued to a XRC utility device. XRC will not allow the reserve to be done until the XRC
volume establishes a new utility device. If there is only one utility device, XRC will not allow the
reserve CCW to be processed.
10 PINNED CACHE MEMORY EXCEEDING MAXIMUM ALLOWED
Pinned data is data that can not be destaged to the real device. IDCAMS LISTDATA PIN can be
issued to determine the pinned tracks. Contact your hardware support center.
11 PPRC SIDEFILE SIZE EXCEEDING LIMITS
The control unit is transferring data from cache to the hardware because the storage cache
thresholds have been exceeded.
12 PPRC SECONDARY SIGNALED PENDING TO PRIMARY
State change pending has been issued by a PPRC secondary to the PPRC primary.
13 PPRC DEVICE IN PROCESS OF GOING SUSPENDED
An operator has issued a command to suspend a PPRC pair or hardware is suspending the pair
because of a hardware problem.
14 PPRC DEVICE IN EXTENDED LONG BUSY STATE
The hardware is currently long-busy and will remain in that state until hardware clears the
condition causing the long-busy. This message is issued every 2 minutes or the control unit time
interval set by the customer.
15 PPRC DEVICE IN PROCESS OF TERMINATION

Chapter 21. IEA messages 773

IEA483I • IEA484I

16 UNFENCE IN PROGRESS
Hardware is in the process of clearing a fenced condition on the LSS.
17 WAITING FOR CONTROL UNIT RESOURCES
18 DESTAGE OR DISCARD IN PROGRESS FOR FLASHCOPY VOLUME
The control unit is either destaging or discarding data that is downlevel.
19 DEVICE ERROR RECOVERY IN PROGRESS
While the device is recovering, the device is long-busy. Contact your hardware support center to
determine device error.
1A PPRC DEVICE LONG BUSY DUE TO FREEZE
A freeze of the PPRC pairs has been issued by the operator.
xx NEW OR INVALID REASON CODE
Either hardware has created a new message code or the message code is invalid. Contact the
hardware support center to determine the meaning of this message code.
sense The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: The MIH Exit will periodically retry the queued I/O to the device until the control unit accepts the
request. Message IEA482I is displayed for each retry of the I/O request by the MIH Exit while the busy condition
exists.
Operator response: Respond according to the reason code provided in the message. Certain conditions have
occurred because of XRC, Flash Copy, and Concurrent Copy. If the messages persist contact your hardware support
center and follow your installation recovery processes.
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.
In the message text:
return-code
The return code.
System action: No log records are routed to the workstation NODE.USERID.
Operator response: Report this message to the system programmer. If return-code is 046C, an incorrect NODE was
specified on the START LOGROUTE command. Issue the MODIFY LOGROUTE,NODEID=nodevalue.useridvalue
command to correct the NODEID value.
Source: DFSMSdfp

IEA484I CACHING STATUS RESET TO DEFAULT - device-number/ssid.p-cc-nn SENSE=sense

Explanation: Retentive status of the subsystem, a fast write or dual copy has been reset.
In the message text:
device-number
The physical device address.
ssid The subsystem identifier.
p The storage path.
cc The controller address.
nn The device number.

774 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA486E • IEA488I

sense The 32 characters of sense data reported by the device.

xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: Processing continues.
Operator response: If the device associated with this message is attached using the IBM 3990 Model 3 or Model 6
Storage Control, see IBM 3990/9390 Operations and Recovery Guide for detailed recovery actions.
Source: DFSMSdfp

IEA486E 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 wessage (MIM) console message. The specified device has detected an
abnormal medium condition that requires storage administration attention.
In the message text:
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.
s Volid source.
mc Message code (to indicate MIM source).
e Exception code.
refc-med-fi
Error reference code - Media identifier - Format identifier.
REPEATED
Indicates this MIM has already been presented.
System action: The system logs an alert in the LOGREC data set and continues processing.
Operator response: The system issues this message 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 programmer response: Run an EREP System Exception Report to obtain a Media Information Message
report to obtain additional information.
Source: DFSMSdfp
Detecting Module: IGGSNS02
Routing Code: 1,6
Descriptor Code: 2,4

IEA488I INVALID SERVICE TASK LIMIT. DEFAULT OF 200 ASSUMED

Explanation: The value specified in the SYSCATxx member used at IPL contains an invalid decimal value for the
dynamic service task limit. A default value of 200 is used for this IPL.
System action: The default value of 200 is used for this IPL.
Operator response: Notify the system programmer.
System programmer response: Verify that the value specified for the dynamic task limit in the SYSCATxx member
are valid decimal digits. The minimum value that can be specified is 200, the maximum value is 999.
Source: DFSMSdfp
Detecting Module: IEAVNP11

Chapter 21. IEA messages 775

 IEA489I • IEA491E

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
Detecting Module: IEAVNP11
Routing Code: 2,4,10,11
Descriptor Code: -

IEA491E dev, [volser], PPRC SUSPENDED error-reason, (PRI)=aaaa-bbbbb,CCA=xx (SEC)=aaaa-bbbbb,CCA=xx

SENSE=sense
| Explanation: The peer-to-peer remote copy operation (PPRC) has been suspended at the time indicated for the error
| reason stated in the message. This message, IEA491E, is detected and issued by only one of the systems where the
| device is attached.

Note: The time indicated in the message is the time stamp 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.
dev
The device number.
volser
This is the volume serial number of the PPRC volume pair encountering the failure. Note that when a failure is
received by an alias device or an offline device, the volser is not available, so the message text does not have the
volser.
error-reason
The error reasons are:
v SUSPENDED, PRIMARY-DEVICE-WRITE- FAILURE
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 can select the RESYNC option to reestablish the
PPRC pair.
v SUSPENDED, SECONDARY-SUBSYSTEM- FAILURE
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-TO- SECONDARY-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 volume’s
storage control. The primary volume’s 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.

776 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA492I

v SUSPENDED, SECONDARY NOT READY, INTERVENTION_REQUIRED,

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.
v SUSPENDED, SECONDARY TRACK FORMAT NOT SAME AS PRIMARY
The format of a track on the secondary volume does not match the format of the corresponding primary track
when performing an update operation.
v SUSPENDED, ESTABLISH FLASHCOPY WITH PRESERVE MIRROR FAILURE
A request to establish a FlashCopy relationship with preserve mirror required encountered an error resulting
in the suspension of the target PPRC pair.
(PRI)=aaaa-bbbbb,CCA=xx
This is the primary PPRC volume storage control serial number followed by the primary volume’s 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)=aaaa-bbbbb,CCA=xx
This is the PPRC secondary volume’s storage control serial number followed by the secondary volume’s 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 is
found on the lower left-hand portion of the storage control operator panel.
v xx — The two-byte channel connection address.
sense
The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
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.
Operator response: The system issues this message because of a hardware error. Follow your installation’s
procedures for reporting this error.
Application Programmer Response: This is a hardware problem. Contact your hardware support personnel.

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 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.
In the message text:
subid
The subsystem identifier of the subsystem to which the device is configured.
partition
The partition identifier where the device is configured.

Chapter 21. IEA messages 777

IEA493I • IEA494I

text
One of the following:
v CAPACITY USAGE IS BELOW percent%
v CAPACITY USAGE IS ABOVE percent%
action
One of the following:
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 the IBM
Support Center.
Source: DFSMShsm

IEA493I NIP CONSOLE NOT FOUND

Explanation: No suitable nucleus initialization program (NIP) console, along with no system console hardware
installed, has been found.
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 programmer response for wait state X'007'.
Source: Communications task (COMMTASK)
Detecting Module: IEAVNPCA
Routing Code: Note 2
Descriptor Code: -

IEA494I dev, [volser], PPRC state, SSID=ssid, CCA=ca, optional-text SENSE=sense

Explanation: The state of the PPRC pair has changed.
In the message text:
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. Note that when a failure is received by an alias
device or an offline device, the volser is not available, so the message text will not have the volser.
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 in
the extended long busy state, the message will have the optional text EXTENDED LONG BUSY STATE
appended at the end.
SUSPENDED FREEZE
The PPRC pair has changed from PENDING or FULL DUPLEX state to SUSPENDED state. If the device in
the extended long busy state, the message will have the optional text EXTENDED LONG BUSY STATE
appended at the end. The FREEZE keyword has been added to denote a FREEZE command was issued to
the primary device of a PPRC pair.

778 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA495I

TERMINATED
The PPRC pair has terminated from the PENDING, FULL DUPLEX, or SUSPENDED state.
PAIR PENDING
A PPRC copy operation is starting. This might 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.
PPRC PAIR DUPLEX PENDING FC
A PPRC pair is DUPLEX PENDING due to a FC which specified a PPRC primary volume as a
FLASHCOPY (FC) target.
PPRC PAIR SUSPENDED FC
A PPRC pair is SUSPENDED because of a FC that specified a PPRC primary volume as a FLASHCOPY
(FC) target and preserve mirror required, and an error was encountered during the request.
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
Is one or more of the following:
v
EXTENDED LONG BUSY STATE.
v
CONTINUATION OF IEA494I SNS=sense
In the message text:
sense
Sense data.
sense
The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx

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 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) is 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 (776) for additional information related to this message. Message IEA494I is 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 can 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.
In the message text:

Chapter 21. IEA messages 779

IEA496I

dev
The device number of the primary device of a dual copy pair.
volser
The volume serial number of the primary device of 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.
ca The two-byte channel connection address of the primary device of the dual copy pair.
optional-text
The state of the original; one of the following:
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.

Note: The optional text is present if the state of the dual copy pair is FAILED or SUSPENDED.
System action: None.
Operator response: The various formats of the IEA495I message is broadcast to all systems where the primary
device of the dual copy pair is attached and online. Follow your installation's procedures for reporting this error.
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.
Source: DASD device initialization/re-initialization
Detecting Module: IECCINIT

IEA496I dev, volser, MIRRORING state, SSID=ssid, CCA=ca

Explanation: The state of the mirrored pair has changed.
In the message text:
dev
The device number of the primary device of a mirrored pair.
volser
The volume serial number of the primary device of a mirrored pair.

780 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA497I

state
The new state of the mirrored pair is one of the following:
OPERATIONAL
The copy of the primary of a mirrored pair to secondary is complete, and the primary to secondary devices
are synchronized.
PENDING
Mirrored operation is starting or restarting. The primary and secondary devices are not yet synchronized.
FAILED
The mirrored pair has been terminated from the PENDING or OPERATIONAL state.
ssid
The ssid of the primary of the mirrored pair.
ca The two-byte channel connection address or the primary device of the mirrored pair.
System action: None.
Operator response: The various formats of the IEA496I message is issued when the system detects a change of state
for an online primary device of a mirrored pair. Follow your installation's 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.
Source: DASD device initialization/re-initialization
Detecting Module: IECCINIT

IEA497I dev, error_reason ,volser,PPRC state,SSID=ssid, CCA=xx,yyyy,zz optional-text SENSE=sense

Explanation: An error has occurred on a PPRC primary device when the controller is undergoing excessive
recovery. This error would normally be posted to the controller or the device as described in the error-reasons.
In the message text:
dev
The device number of the primary device of a PPRC pair.
error_reason
The reason of the error, which is any of the following:
PERMANENT I/O ERROR
An error has occurred on a PPRC primary device. This error would normally be posted permanent, but the
device has been set to delay the error posting to allow automation software analysis and possible switch to
the secondary device.
EXCESSIVE CONTROL UNIT RECOVERY
The controller is undergoing excessive recovery, and a HyperSwap® has been triggered. The HyperSwap
trigger allows automation software to perform installation specific procedures, such as to switch to use the
secondary PPRC volumes. And there is no need to shut down applications.
HYPERSWAP NOT ACTIVE FOR DEVICE
The controller is undergoing excessive recovery, and a HyperSwap has not been triggered because it is
inactive. Installation specific procedures should be performed such as shutting down databases or shutting
down noncritical applications.
PPRC PRIMARY FAILURE
A write failure occurs during a write operation to the primary device indicated by the volume serial
number. A HyperSwap has also been triggered. The HyperSwap trigger allows automation software to
perform installation specific procedures to maintain data availability. If HyperSwap was not active, the
message IEA491E is issued instead.
volser
This is the volume serial number of the PPRC volume.
state
The status of PPRC for Device dev

Chapter 21. IEA messages 781

IEA498I

ssid
The ssid of the device in error.
xx The two-byte channel connection address of the device.
yyyy
The device and channel status at time of permanent error.
zz The IOSCOD (completion code) for the IOS request.
optional-text
CONTINUATION OF IEA497I SNS=sense
In the message text:
v The sense data if present for the device error.
sense
The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: If GDPS® is active in the system, the combination of the HyperSwap trigger and the error-reasons
will fully allow automation software to perform installation specific procedures to maintain data availability. If GDPS
is not active, some other additional procedures may have to be taken manually instead.
Operator response: This message is intended for automation software. Any actions should be controlled by that
software.
Source: DFSMSDFP
Detecting Module: IECVDERP

IEA498I dev,volser,PPRC-PATH variable-text SSID=ssid (PRI)=aaaa-bbbbb,CCA=cc optional-text SENSE=sense

Explanation: When one or more paths between peer subsystems are removed or established for any reason other
than online execution of Establish Peer-to-Peer Remote Copy Paths order or Remove Peer-to-Peer Remote Copy Paths
order, a unit check is generated to detect this action. This message is issued to alert the operator of the action so
appropriate action is taken.
In the message text:
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.
variable-text
One of the following:
v ONE OR MORE PPRC PATHS REMOVED UNEXPECTEDLY
v ONE OR MORE PPRC PATHS RESTORED
v ALL PPRC PATHS REMOVED UNEXPECTEDLY
v ONE OR MORE PPRC PATHS REMOVED BY CUIR
v ALL PPRC PATHS REMOVED BY CUIR
v ONE OR MORE PPRC PATHS ARE DEGRADED
v ONE OR MORE PPRC PATHS ARE NO LONGER DEGRADED
ssid
The ssid of the device in error.
aaaa-bbbbb
This is the primary PPRC volume storage control serial number. 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.

782 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA499E

cc The primary volume’s channel connection address.

optional-text
CONTINUATION OF IEA498I SNS=sense
In the message text:
v The sense data if present for the device error.
sense
The 32 characters of sense data reported by the device.
xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
System action: If other paths between peer subsystems are available performance can be affected by the loss or
addition of this path. If the last path between peer subsystems is removed, an IEA491E message will most likely be
generated and PPRC operation is suspended.
Operator response: Follow your installation's procedures for reporting this error.
Source: DFSMSDFP
Detecting Module: IGGSNS01

IEA499E dev, volser, epid, ssid, sfiid, pcnt, message text.

Explanation: Indicates that a space constraint threshold has been reached for a repository volume of a space efficient
extent pool.
In the message text:
dev
The MVS device number of the device that the notification was received on.
volser
The volser of the device that notification was received on.
epid
The ID of the extent pool that contains the repository volume associated with the notification.
ssid
The SSID of the logical subsystem containing the device that the notification was received on.
sfiid
The 26-byte storage facility image ID is displayed in the following format: aaaaaa.bbb.ccc.dd.eeeeeeeeeeee.
where:
aaaaaa
Is a 6-byte machine type.
bbb
Is a 3-byte facility model.
ccc
Is a 3-byte manufacturer ID.
dd Is a 2-byte manufacturer location.
eeeeeeeeeeee
Is a 12-byte Sequence Number.
pcnt
The amount of space left in the repository at the time of the notification. For example, a value of 15 indicates
that only 15% of the repository volume's capacity is still available.
message-text
One of the following:
v REPOSITORY VOLUME CAPACITY WARNING: AT pcnt% CAPACITY REMAINING
v REPOSITORY VOLUME CAPACITY EXHAUSTED
System action: No action is taken until the repository volume capacity becomes completely exhausted. Once the

Chapter 21. IEA messages 783

IEA500A

repository volume capacity becomes completely exhausted, all of the space efficient volumes in the extent pool
identified by epid is taken offline and I/O directed to those volumes will fail with Intervention Required. Any
FlashCopy® relation in which the target volume is a space efficient volume that resides in the extent pool identified
by epid is put in failed state invalidating the data on the target volume.
Operator response: Notify the system programmer.
System programmer response: Use the epid as input to the IDCAMS LISTDATA EXTENTPOOLCONFIG command
to get a list of the space efficient volumes residing in the extent pool. Use the device numbers returned by the
EXTENTPOOLCONFIG command as input to the IDCAMS LISTDATA SPACEEFFICIENTVOL command to get
information about how much repository space is consumed by each of the space efficient volumes in the extent pool.
Use the ICKDSF FLASHCPY QUERY RELATIONS command to get information about the FlashCopy relations that
the space efficient volumes are participating in. Finally, use the ICKDSF INIT command to initialize one or more of
the space efficient volumes that are consuming a significant amount of repository space and are currently the target
of a FlashCopy relation. The INIT command will withdraw the FlashCopy relation and release the repository space
consumed by the space efficient volume.
Descriptor Code: 3

IEA500A 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: 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.
In the message text:
jobname The name of the job that the system was currently processing.
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
PSW=psw
The 16-byte program status word (PSW) at the time of the restart interruption.
System action: The system prompts the operator for a reply.
Operator response: Reply one of the following:
RESUME
The job that was in progress continues at the next sequential instruction.
ABEND
The system ends the job with abend X'071'.

When this message is issued, IT IS EXTREMELY IMPORTANT to respond promptly. This message is issued as a
synchronous WTOR, which will prevent the system from updating its status on the sysplex couple data set. This, in
turn, could lead to Sysplex Failure Management (SFM) deciding that the system is not responding normally, and
removing it from the sysplex.
Source: Loadwait/Restart

784 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA501I • IEA502A

Detecting Module: IEAVEREX

Routing Code: Note 12
Descriptor Code: -

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.
In the message text:
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.
[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 can be started tasks in the system.
System action: The system issues message 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.
[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.

When this message is issued, IT IS EXTREMELY IMPORTANT to respond promptly. This message is issued as a
synchronous WTOR, which will prevent the system from updating its status on the sysplex couple data set. This, in
turn, could lead to Sysplex Failure Management (SFM) deciding that the system is not responding normally, and
removing it from the sysplex.
Source: Loadwait/Restart
Detecting Module: IEAVEREX
Routing Code: Note 12
Descriptor Code: -

IEA502A 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.
1 The system checks and repairs critical data areas.

Chapter 21. IEA messages 785

IEA503W • IEA504I

When this message is issued, IT IS EXTREMELY IMPORTANT to respond promptly. This message is issued as a
synchronous WTOR, which will prevent the system from updating its status on the sysplex couple data set. This, in
turn, could lead to Sysplex Failure Management (SFM) deciding that the system is not responding normally, and
removing it from the sysplex.
Source: Loadwait/Restart
Detecting Module: IEAVEREX
Routing Code: Note 12
Descriptor Code: -

IEA503W MULTIPLE CPUS FAILED DURING xxx SYNC-CHECK PROCESSING.

Explanation: At least two processors could not complete External Time Reference (ETR) or Server Time Protocol
(STP) synchronization check processing. A hardware failure occurred.
In the message text:
xxx
One of the following:
v ETR
v STP
System action: The system enters nonrestartable wait state X'0A4'.
Operator response: See the operator response for wait state X'0A4'.
System programmer response: See the system programmer response for wait state X'0A4'.
Source: Timer supervision
Detecting Module: IEATESCH, IEATESC2, IEATCCCH, IEATSSCH
Routing Code: 1
Descriptor Code: 1

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.
In the message text:
xx The suffix of the CONSOLxx parmlib member.
dddd The device number of the console.
reason-code
The reason code, as follows:
1 dddd is not a console. The CONSOLE statement defining the device as a console might be missing.
2 dddd is not a valid device number.
3 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 programmer response: Before the next 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 the
CONSOLxx parmlib member.
v The device type is the same in both the IODF and the CONSOLE statement in the CONSOLxx parmlib member.
v A hardcopy device is defined as a console (not a display console) in CONSOLxx.
Source: Master scheduler

786 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA510A • IEA513W

Detecting Module: IEAVN615

Routing Code: 2,10
Descriptor Code: 12

IEA510A LNKLST PROCESSING IS INOPERATIVE, HIT ENTER TO CONTINUE WITH THE DEFAULT
LNKLST OR RE-IPL THE SYSTEM
Explanation: The nucleus initialization program (NIP) 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.
Operator response: Notify the system programmer 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.
Source: Contents supervision (CSV)
Routing Code: -
Descriptor Code: -

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.
In the message text:
h 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'.
System programmer response: See the system programmer response for wait state X'0B1'.
Source: Input/output supervisor (IOS)
Detecting Module: IEAIPL43

IEA513W DATASET NOT FOUND ON DEVICE dev: dsname

Explanation: The system cannot find a data set name because one of the following conditions exists:
v The device number is incorrect
v The wrong LOADxx suffix was entered in the load frame parameter

In the message text:

dev
The device number.
dsname
The data set name. It is one of the following:
v SYS1.PARMLIB
v h.IODFxx, where h is the high level qualifier.
System action: The system ends initialization. The system enters nonrestartable wait state X'0B1' with reason code
X'001'.
Operator response: Do one of the following:
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.

Chapter 21. IEA messages 787

IEA514W • IEA516W

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.
System programmer response: See the system programmer response for wait state X'0B1' with reason code X'001'.
Source: Input/output supervisor (IOS)
Detecting Module: IOSIOFR

IEA514W MORE THAN ONE EXTENT FOR dsname

Explanation: A data set in the LOADxx parmlib member occupies more than one extent.
In the message text:
dsname The data set name.
System action: The system ends initialization. The system enters nonrestartable wait state X'0B1' with reason code
X'002'.
System programmer response: See the system programmer response for wait state X'0B1'.
Source: Input/output supervisor (IOS)
Detecting Module: IOSIOFR

IEA515W DEVICE NUMBER dev NOT DEFINED TO THE CHANNEL SUBSYSTEM

Explanation: During system initialization, the system could not find a subchannel for the device that contains the
parmlib member.
In the message text:
dev
The device number.
System action: The system ends initialization. The system enters nonrestartable wait state X'0B1' with reason code
X'003'.
System programmer response: See the system programmer response for wait state X'0B1'.
Source: Input/output supervisor (IOS)
Detecting Module: IOSIOFR

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.
In the message text:
dev
The device number.
System action: The system ends initialization. The system enters nonrestartable wait state X'0B1' with reason code
X'004'.
System programmer response: See the system programmer response for wait state X'0B1'.
Source: Input/output supervisor (IOS)
Detecting Module: IOSIOFR

788 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA517W • IEA520I

IEA517W IODF IS NOT VALID FOR AN IPL

Explanation: During system initialization, the system found an incorrect I/O definition file (IODF) data set name in
the LOADxx parmlib member.
System action: The system ends initialization. The system enters nonrestartable wait state X'0B1' with reason code
X'005' or X'00A'.
System programmer response: See the system programmer response for wait state X'0B1'.
Source: Input/output supervisor (IOS)
Detecting Module: IEAIPL43

IEA518W CONFIGURATION ID xxxxxxxx NOT FOUND IN IODF.

Explanation: During system initialization, the system could not find the configuration identifier from the LOADxx
parmlib member in the I/O definition file (IODF).
In the message text:
xxxxxxxx
The configuration identifier.
System action: The system ends initialization. The system enters nonrestartable wait state X'0B1' with reason code
X'006'.
System programmer response: See the system programmer response for wait state X'0B1'.
Source: Input/output supervisor (IOS)
Detecting Module: IEAIPL43

IEA519I IODF DSN = dsname

Explanation: This message identifies the I/O definition file (IODF) data set name.
In the message text:
dsname The data set name.
System action: System initialization continues.
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.
Source: Input/output supervisor (IOS)
Detecting Module: IEAIPL43

IEA520I CONFIGURATION ID = xxxxxxxx. IODF DEVICE NUMBER = dev

Explanation: This message identifies the configuration identifier and the I/O definition file (IODF) device number.
In the message text:
xxxxxxxx
The configuration identifier.
dev
The device number.
System action: System initialization continues.
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.
Source: Input/output supervisor (IOS)

Chapter 21. IEA messages 789

IEA521I • IEA524I

Detecting Module: IEAIPL43

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.
In the message text:
devtype
The device type.
num
The number of devices.
System action: System initialization continues. The system does not recognize any devices of the specified device
type.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Source: Input/output supervisor (IOS)
Detecting Module: IEAIPL71

IEA522I IEA1522I UIM modname DID NOT BUILD A DFT FOR DEVICE NUMBER s-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.
In the message text:
modname
The name of the UIM.
s-
dev
The device number. The device number is prefixed by the subchannel set identifier (s-) when appropriate.
System action: System initialization continues. The system does not recognize the device types defined by the UIM.
System programmer response: Search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Source: Input/output supervisor (IOS)
Detecting Module: IEAIPL71

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'.
System programmer response: See the system programmer response for wait state X'0B2'.
Source: Input/output supervisor (IOS)

IEA524I NO DEVICES DEFINED FOR SUBCHANNEL SET n

Explanation: The selected I/O definition file defines devices in subchannel set n but the system cannot define the
devices because the processor does not support that subchannel set.
In the message text:
n The subchannel set.

790 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA525W • IEA527A

System action: The devices defined in subchannel set n are ignored.

System programmer response: None.
Source: Input/output supervisor (IOS)
Detecting Module: IEAIPL71
Routing Code: -
Descriptor Code: 12

IEA525W IEA1525W UIM modname SPECIFIED UNDEFINED DEVICE NUMBER s-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 that device because of a logic error in the UIM.
In the message text:
modname
The unit information module (UIM).
s-
dev
The device number. The device number is prefixed by the subchannel set identifier (s-) when appropriate.
System action: System initialization ends. The system enters nonrestartable wait state X'0B4'.
System programmer response: See the system programmer response for wait state X'0B4'.
Source: Input/output supervisor (IOS)
Detecting Module: IOSIUCB

IEA526I SYSNAME SYSTEM PARAMETER INVALID

Explanation: During system initialization, the nucleus 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.
System action: The system issues message IEA527A to prompt the operator for a reply.
Operator response: Enter SYSNAME=sysname, where sysname is a valid system name, in reply to message IEA527A.
System programmer response: Correct the SYSNAME system parameter in the IEASYSxx or IEASYMxx parmlib
member used to IPL the system.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPCF
Routing Code: -
Descriptor Code: 12

IEA527A SPECIFY REQUIRED SYSNAME PARAMETER. SYSNAME=

Explanation: During system initialization, the system name in the SYSNAME parameter is incorrect or missing.
System action: The system prompts the operator for 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.
System programmer response: Add or correct the SYSNAME parameter in the IEASYSxx or IEASYMxx parmlib
member used to IPL the system.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVNPCF
Routing Code: Note 2

Chapter 21. IEA messages 791

IEA528I • IEA540I

Descriptor Code: -

IEA528I IPL IODF NAME DOES NOT MATCH IODF NAME IN HARDWARE TOKEN IODFdsname
Explanation: The system discovered a mismatch between the IODF data set selected for IPL and the IODF data set
name found in the HSA token.
Note that the mismatch does not impact dynamic changes.
In the message text:
IODFdsname
The IODF data set name found in the hardware token.
System action: System initialization continues using the selected IODF data set name for the IPL.
System programmer response: The IODF data set name in the HSA token was originally specified by the system
programmer in the Descriptor Field 1 and Descriptor Field 2 fields when building a production IODF.
Depending on the options specified in the LOADxx parmlib member, IOS may use the IODF data set name found in
the HSA token, or may use a specific algorithm to select an IODF for the IPL. If the IODF used for the IPL is not the
desired IODF, either correct the options in the LOADxx member and re-IPL the system or perform a dynamic activate
to the desired IODF.
For details on LOADxx options and the IODF search algorithm, see the z/OS MVS Initialization and Tuning Reference
and z/OS HCD Planning books.
Source: Input/output supervisor (IOS)
Detecting Module: IEAIPL43
Routing Code: -
Descriptor Code: 4

IEA540I taskname TASK FAILED - RESTART ATTEMPT IN PROGRESS.

Explanation: taskname is one of the following:
ADDRESS SPACE TERMINATION
DUMP
RECORD

One of the permanent tasks in the recovery termination manager (RTM) failed.

In the message text:

ADDRESS SPACE TERMINATION
The RTM address space failed.
DUMP
The RTM dump task failed.
RECORD
The RTM recording task failed.
System action: One of the following:
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.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTMS1
Routing Code: 2,10
Descriptor Code: 4

792 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA541E • IEA542I

IEA541E taskname TASK FAILED DURING RESTART ATTEMPT.

Explanation: taskname is one of the following:
ADDRESS SPACE TERMINATION
DUMP
RECORD

One of the permanent tasks in the recovery termination manager (RTM) failed. This task had failed previously and
was attempting to restart when a second error occurred.

In the message text:

ADDRESS SPACE TERMINATION
The RTM address space failed.
DUMP
The RTM dump task failed.
RECORD
The RTM recording task failed.
System action: The system does not try to restart the task. The task's function will not be available until the system
is initialized again.
Operator response: ReIPL the system.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTMSI
Routing Code: 2,10
Descriptor Code: 11

IEA542I taskname TASK RESTART COMPLETED SUCCESSFULLY.

Explanation: taskname is one of the following:
ADDRESS SPACE TERMINATION
DUMP
RECORD

One of the permanent tasks in the recovery termination manager (RTM) failed, but restarted itself.

In the message text:

ADDRESS SPACE TERMINATION
The RTM address space failed.
DUMP
The RTM dump task failed.
RECORD
The RTM recording task failed.
System action: The task is now available for processing.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTSDT, IEAVTMTC, IEAVTR2S, IEAVTRET
Routing Code: 2,10
Descriptor Code: 4

Chapter 21. IEA messages 793

IEA544I • IEA546E

IEA544I EXTERNAL INTERRUPT IGNORED. [NO FULL CAPABILITY CONSOLES DEFINED OR]
MASTER CONSOLE WAS VARIED OFFLINE.
Explanation: The system did not process an external interrupt.
In the message text:
NO FULL CAPABILITY CONSOLES DEFINED
No full capability consoles are defined in the CONSOLxx parmlib member.
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.
Source: Communications task (COMMTASK)
Detecting Module: IEAVMQWR
Routing Code: -
Descriptor Code: 12

IEA545W MULTIPLE CONSOLE SUPPORT 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.
In the message text:
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'.
Operator response: See the operator response for wait state X'202'.
When this message is issued, IT IS EXTREMELY IMPORTANT to respond promptly. This message is issued as a
synchronous WTOR, which will prevent the system from updating its status on the sysplex couple data set. This, in
turn, could lead to Sysplex Failure Management (SFM) deciding that the system is not responding normally, and
removing it from the sysplex.
System programmer response: See the system programmer response for wait state X'202'. See message IEA367A for
a description of error codes.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN701
Routing Code: Note 12
Descriptor Code: -

IEA546E text
Explanation: In the message text, text is:

NO FULL CAPABILITY MCS OR SMCS

CONSOLES, REASON=reason
TO RELIEVE THIS CONDITION:
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

794 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA548W

CAPABILITY CONSOLE

OR

LOG ON TO A FULL CAPABILITY

SMCS CONSOLE.

Console switch processing results in loss of all the full capability multiple console support (MCS or SMCS) consoles.
The failing console's undelivered (UD) messages is 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.

In the message text:

REASON=reason
Communications task (COMMTASK) lost all the full capability MCS or SMCS consoles.reason 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.
LOGOFF
The failing console was an SMCS console that was deactivated, either by a LOGOFF command or a
VARY command.

Note: This applies only to SMCS.

System action: The system continues processing. Consoles with the UD attribute or the system console receive the
failing console's undelivered messages. If there are no other consoles with the UD attribute (including the hard-copy
log), the system sends the failing console's UD messages to the system console. The system sends all other messages
to the hard-copy log.
Operator response: Activate a master authority MCS or SMCS console.
Source: Communications task (COMMTASK)
Detecting Module: IEAVSWCB, IEAVSWCR
Routing Code: 2,10
Descriptor Code: 3

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.
In the message text:
text The first 8 lines of the message which could not be delivered.
System action: The system enters nonrestartable wait state X'A70'.
Operator response: ReIPL when the system console is available.
System programmer response: See the system programmer response for wait state X'A70'.

Chapter 21. IEA messages 795

IEA549I • IEA555E

Source: Communications task (COMMTASK)

Detecting Module: IEAVG724
Routing Code: Note 12
Descriptor Code: _

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.
In the message text:
consname
The name the system assigns to the system console.
System action: The system assigns the specified name to the console. The system continues processing.
Source: Communications task (COMMTASK)
Detecting Module: IEAVM605
Routing Code: -
Descriptor Code: 12

IEA554I CONSOLE DELAYED SVC PROCESSING SUSPENDED. RESTART PENDING

Explanation: The Delayed SVC processor encountered an error which caused the Delayed SVC queue to be rebuilt.
The queue is currently being repaired.
In the message text:
PENDING
The restart is pending.
System action: The system tries to restart Delayed SVC processing. If successful, message IEA123I is issued.
Source: Communications task (COMMTASK)
Detecting Module: IEAVM613
Routing Code: *
Descriptor Code: 4

IEA555E CONSOLE DELAYED SVC PROCESSING ABORTED. RESTART UNSUCCESSFUL

Explanation: The Delayed SVC processor encountered an error which caused the Delayed SVC queue to be rebuilt.
The queue could not be rebuilt.
System action: The system does not display branch-entered write to operator with reply (WTOR) messages. The
system storage can become filled with messages waiting to be issued.
Operator response: ReIPL the system when it is convenient.
Source: Communications task (COMMTASK)
Detecting Module: IEAVM613
Routing Code: 1
Descriptor Code: 3

796 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA556I • IEA590I

IEA556I MESSAGE IEA367A ISSUED ON SYSTEM sysname, ERROR CODE= error code
Explanation: A system encountered a severe Communications Task (CommTask) error (that system will issue
IEA367A). This message is issued to notify the rest of the sysplex about that system's error.
In the message text:
sysname
The name of the system that had the CommTask error (and the system that issued IEA367A).
error code
The same error code in IEA367A.
System action: The system continues processing. This system is not having any problems. It is being notified that
another system in the sysplex has a CommTask failure.
Operator response: Check the status of the system that had the CommTask error.
System programmer response: On the system that had the error, check the error code in IEA367A to determine the
severity of the error.
Source: Communications task (COMMTASK)
Detecting Module: IEAVN701
Routing Code: 2
Descriptor Code: -

IEA557A MULTIPLE REQUESTORS FOR REPLY ID 0, REPLY TO ID 0 ON sysname

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. Critical messages may need to
be issued, so it is important to try to answer REPLY ID 0 WTORs.
In the message text:
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. Critical messages can be delayed from being issued.
System programmer response: Determine if increasing the RLIM/RMAX values in your CONSOLxx parmlib
member is necessary, especailly if your sysplex supports more than eight systems. The RLIM/RMAX values are
sysplex scope, therefore, a sysplex-wide IPL is required for the CONSOLxx parmlib member changes to take effect.
To have the updates to the RLIM/RMAX values in effect immediately, issue the CONTROL M system command with
either the RLIM or RMAX parameters.
Source: Communications task (COMMTASK)
Detecting Module: IEAVH705
Routing Code: 1
Descriptor Code: 2

IEA590I WTO USER EXIT text

Explanation: text is one of the following:
exit-name ABENDED - EXIT DEACTIVATED
IEAVMXIT NOT FOUND
IEAVMXIT NOT LOADED - NO STORAGE AVAILABLE

An error occurred during the initialization or running of a WTO installation exit routine.

In the message text:

Chapter 21. IEA messages 797

IEA598I

exit-name ABENDED - EXIT DEACTIVATED

The WTO installation exit abnormally ended. The system marked it as nonexecutable.
In the message text:
exit-name
The name of the installation exit, which can be IEAVMXIT or a user written WTO installation exit.
IEAVMXIT NOT FOUND
The system could not load installation exit routine IEAVMXIT from any system library.
IEAVMXIT NOT LOADED - NO STORAGE AVAILABLE
Storage was requested for the general WTO installation routine IEAVMXIT, but the storage was not available.
System action: The system action is one of the following:
exit-name ABENDED - EXIT DEACTIVATED
The system abnormally ends user exit exit-name.
IEAVMXIT NOT FOUND
The system does not process the CONTROL M command.
IEAVMXIT NOT LOADED - NO STORAGE AVAILABLE
The system does not process the CONTROL M command.
Operator response: Contact the system programmer.
System programmer response: Respond to the error messages as follows:
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.
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.
IEAVMXIT NOT LOADED - NO STORAGE 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.
Source: Communications task (COMMTASK)
Detecting Module: CNZS1MPF and IEEMB819
Routing Code: 2,10
Descriptor Code: 4

IEA598I 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).
In the message text:
d The location of the time zone in relation to GMT, as follows:
E A time zone east of GMT.
W 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 continues processing.
System programmer response: If the time zone value is unacceptable, specify a different value in the CLOCKxx
parmlib member.

798 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA599I • IEA600I

Source: Timer supervision

Detecting Module: IEAVNP20
Routing Code: 10
Descriptor Code: 12

IEA599I CLOCKxx LINE nnnn: text STMT IGNORED. UNRECOGNIZED PARM.

Explanation: A statement in a CLOCKxx parmlib member contains an incorrect parameter or statement type.
In the message text:
CLOCKxx
The parmlib member, with the suffix xx.
nnnn The line number in the CLOCKxx parmlib member that contains the ignored statement.
If the statement type is not recognized, nnn is the line number of the previous valid statement.
text The statement that contains the incorrect parameter.
If the statement type is not recognized, text is the previous valid statement type.
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 on the console, the system sets the
following defaults:
v The system does not prompt the operator during time-of-day (TOD) initialization.
v The system sets the local time equal to the Greenwich mean time (GMT).
System programmer response: Check for misspelled parameters in the CLOCKxx parmlib member from the
specified keyword to the end.
Source: Timer supervision
Detecting Module: IEAVNP20
Routing Code: 2
Descriptor Code: 12

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

In the message text:

CLOCKxx
The parmlib member, with the suffix xx.
nnnn The line number in the CLOCKxx parmlib member that contains the ignored statement.
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 on the console, the system sets the
following defaults:
v The system does not prompt the operator during time-of-day (TOD) initialization.
v The system sets the local time equal to the Greenwich mean time (GMT).
System programmer response: Check for misspelled parameters in the CLOCKxx parmlib member. Ensure that the
value for TIMEZONE is within the valid range (00:00:00 - 15:00:00).
Source: Timer supervision
Detecting Module: IEAVNP20
Routing Code: 2

Chapter 21. IEA messages 799

IEA601I • IEA603I

Descriptor Code: 12

IEA601I CLOCKxx LINE nnnn: DUPLICATE text STMT IGNORED

Explanation: A statement in the CLOCKxx parmlib member is a duplicate.
In the message text:
CLOCKxx
The parmlib member, with the suffix xx.
nnnn The line number in the CLOCKxx parmlib member that contains the duplicate statement.
text The duplicate statement.
System action: The system ignores the duplicate statement. The system continues processing.
System programmer response: Remove the duplicate statement from CLOCKxx
Source: Timer supervision
Detecting Module: IEAVNP20
Routing Code: 2
Descriptor Code: 12

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.
In the message text:
text
One of the following:
THE GETMAIN FOR THE ASCB FAILED
Storage could not be obtained from SQA for the new address space's ASCB or ASSB.
MAXUSERS WOULD HAVE BEEN EXCEEDED
The creation of a new address space would exceed the maximum number of allowable address spaces as
specified in the MAXUSER, RSVNONR, and RSVSTRT parameters in the IEASYSxx parmlib member.
ADDRESS SPACE SERVICES FAILED
Address space services suffered an error which prevented the address space creation.
A STORAGE SHORTAGE EXISTS
There is insufficient SQA, pageable storage, or auxiliary storage available.
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.
Source: Supervisor control
Detecting Module: IEAVEMRQ

IEA603I NO UCBS BUILT FOR nnnnn 4-DIGIT DEVICES FOUND IN THE IODF
Explanation: Initial program load (IPL) completed successfully but the system has encountered nnnnn 4-digit
devices.
In the message text:

800 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA607E • IEA611I

nnnnn The number of 4-digit devices encountered.

System action: Processing continues. No UCBs are built for the nnnnn 4-digit devices.
Detecting Module: IEAIPL71

IEA607E 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:
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.
System action: The system continues processing with no SVC dumping capability.
Operator response: ReIPL the system to reinitialize and restart the dumping services address space.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTSDR
Routing Code: 2,10
Descriptor Code: 3

IEA607I 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:
v Process a dump request
v Give control to the post dump installation exit routine
v Process a DUMPDS operator command
System action: The system restarts the dumping services address space. When the restart is complete, complete
dump processing is available again.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTSDR
Routing Code: 2,10
Descriptor Code: 3

IEA611I {COMPLETE|PARTIAL} DUMP ON dsname

text
Explanation: Where text is:
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]

Chapter 21. IEA messages 801

IEA611I

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:
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 affected, 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.
INCIDENT TOKEN: incident-token
The formatted incident token for the dump.
SDRSN = vvvvvvvv wwwwwwww xxxxxxxx zzzzzzzz
The system wrote a 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 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.
04000000
An error in summary dump processing caused recovery to receive control.
02000000
An error in summary dump processing or suspend summary dump processing caused recovery to
receive 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.

802 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA611I

00080000
While the system was writing a trace table, an error occurred. The trace table could not be written.
00008000
The dump of the data above the bar could not be written because the storage buffer was unavailable.
00004000
Option USERTOKEN is not accessible.
00002000
Some private storage above the bar was not collected because the extension range table is full.
00001000
Extended range table has filled while collecting ranges of private storage above the bar.
00000800
Extended range table has filled while collecting ranges of common storage above the bar.
wwwwwwww
Partial dump reason code. One of the following:
80000000 | 40000000
While processing SVC X'33', 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.
01000000
The started dump task failed.
00800000
A task abnormally ended, and SVC dump processing took a partial dump. The resource manager for
SVC dump processing receives control.
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.
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
During dump processing of a possibly hung address space, dump processing obtained only fixed
storage for the address space.
00010000
During dump processing of a possibly hung address space, the address space was found to be invalid.
The dump data may not be consistent.
xxxxxxxx
Partial dump reason code. One of the following:

Chapter 21. IEA messages 803

IEA611I

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 reached.
00008000
While processing the SQA SDATA option, the system filled the range table.
00004000
While processing the CSA SDATA option, the system filled the range table. Remaining entries could not
be added.
00002000
While processing global subpools, the system filled the range table. Remaining entries could not be
added.
00001000
While processing the LSQA SDATA option, the system filled the range table. Remaining entries could
not be added.

804 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA611I

00000800
While processing the RGN SDATA option, the system filled the range table. Remaining entries could not
be added.
00000400
While processing private subpools, the system filled the range table. Remaining entries could not be
added.
00000200
While processing the SWA SDATA option, the system filled the range table. Remaining entries could not
be added.
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 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
SVC dump processing truncated the dump because a critical shortage of auxiliary storage existed.
zzzzzzzz
Dump reason code. One of the following:
Bits in the first byte indicate a result that occurred because one or more of the following
conditions might exist
1. There is a shortage of central storage
2. There is a shortage of auxiliary storage
3. The DUMPSRV address space dispatching priority is too low.
80000000
Dump processing had to reset the system dispatchable. The data in some storage areas might have
changed before the dump capture completed.
40000000
Dump processing had reset the tasks dispatchable in one or more address spaces involved in the SVC
dump. The data in some storage areas might have changed before the dump capture completed.
20000000
Dump processing reset the caller's 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.

Chapter 21. IEA messages 805

IEA611I

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
is 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
reason-text
One of the following:
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
SVC dump processing truncated the dump because a critical shortage of auxiliary storage existed.
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 {SUMDUMP|GLOBAL|LOCAL|STRLIST}
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 z/OS 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.
SOME STORAGE COULD NOT BE DUMPED RC=rc
Storage could not be dumped. rc can be one of the following:

806 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA611I

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 might be missing, IEA611I COMPLETE DUMP is
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 caller's 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:
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.
System action: The system continues processing.
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:

Chapter 21. IEA messages 807

IEA630I

A CRITICAL AUXILIARY STORAGE SHORTAGE EXISTS

Ensure that enough DASD resource is available for accommodating captured SVC dumps. See the system
programmer response for message IRA201E to determine how to relieve the shortage. Then redrive the SVC
dump.
You can use the AUXMGMT and MAXSPACE parameters of the CHNGDUMP command to manage the use of
virtual and auxiliary storage by SVC dump processing. See z/OS MVS System Commands for more details about
the CHNGDUMP command.
DUMP DATA SET FULL - DUMP ENDED WHILE WRITING {SUMDUMP|GLOBAL|LOCAL|STRLIST}
Format the partial dump.
Automatic allocation is not functioning properly. If the problem persists, search the problem reporting data bases
for a fix for the problem. If no fix exists, contact the IBM Support Center. Be able to provide:
v Logrec error records
v CHNGDUMP option settings
v DUMPDS status
v The partial SVC Dump
v Dump data set information
I/O ERROR - NO EOF WRITTEN - DUMP ENDED WHILE WRITING {SUMDUMP|GLOBAL|LOCAL|STRLIST}
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.
ERROR OCCURRED IN SDUMP
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 is
displayed.
Source: SVC dump
Detecting Module: IEAVTSDC
Routing Code: 2
Descriptor Code: 12

IEA630I OPERATOR opername NOW ACTIVE, SYSTEM=sysname, LU=unitname

Explanation: An extended MCS (EMCS) console has been activated.
In the message text:
opername
The name of the EMCS console.
sysname
The name of the system to which the EMCS was activated on.
unitname
The terminal name or the VTAM LU name.
System action: The system continues processing.
Source: Communications task (COMMTASK)
Detecting Module: IEAVG712
Routing Code: Note 13
Descriptor Code: -

808 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA631I • IEA651E

IEA631I OPERATOR opername NOW INACTIVE, SYSTEM=sysname, LU=unitname

Explanation: An extended MCS (EMCS) console has been deactivated.
In the message text:
opername
The name of the EMCS console.
sysname
The name of the system to which the EMCS was activated on.
unitname
The terminal name or the VTAM LU name.
System action: The system continues processing.
Source: Communications task (COMMTASK)
Detecting Module: IEAVG712
Routing Code: Note 13
Descriptor Code: -

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.
Application Programmer Response: Check the 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 is created.
Application Programmer Response: Check the 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

Chapter 21. IEA messages 809

IEA652A • IEA653I

IEA652A WTO STORAGE EXHAUSTED - WTOS is DISCARDED

Explanation: Outstanding WTO messages have used all of the available buffer space. Some WTOs is 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.
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 purge 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.
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.
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.
Source: Communications Task (COMMTASK)
Detecting Module: IEAVMQWR
Routing Code: 1,2
Descriptor Code: 1

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.
In the message text:
jobname
The name of the job that is using a large percentage of the WTO message buffers.
asid
The ASID of the named job.
nn.
the percent of the maximum number of WTO buffers used by the specified job.
System action: The system continues processing.
Operator response: Contact the system programmer.
Application Programmer Response: If your program is in a WTO loop, correct the program.
System programmer response: Follow the response for message IEA099A.
Source: Communications Tack (COMMTASK)
Detecting Module: IEAVH600
Routing Code: 2

810 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA654A • IEA656I

Descriptor Code: 4

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.
In the message text:
sysname1
The name of the system that is experiencing a WTO buffer shortage.
sysname2
The name of the system that cannot sent messages to system sysname1.
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
Operator response: Try to relieve the WTO buffer shortage on system sysname1 as described in message IEA404A.
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)
Detecting Module: IEAVG610
Routing Code: 1,2
Descriptor Code: 2

IEA655I 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.
In the message text:
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.
Operator response: None.
Source: Communications Task (COMMTASK),
Detecting Module: IEAVMQWR
Routing Code: -
Descriptor Code: 4

IEA656I EXCESSIVE NUMBER OF UNLABELED DASD FOUND - IEA311I SUPPRESSED

Explanation: EA311I messages were issued for many direct access storage devices (DASD). IEA311I will not be
issued for any additional unlabeled DASD.
System action: The system continues to mark unlabeled DASD devices offline.
Operator response: Notify the system programmer.
Source: (IOS)
Detecting Module: IOSVVOLV
Routing Code: -

Chapter 21. IEA messages 811

 IEA660I • IEA663I

Descriptor Code: 4

IEA660I PROCESSING CONTINUES AFTER UNDEFINED KEYWORD DUE TO WARNUND

Explanation: An undefined system parameter was encountered, and identified in preceding message IEA321I.
Because of use of the WARNUND system parameter, the system ignores the undefined parameter and continues
processing the system parameters. The system will not re-prompt for new parameters for this keyword unless there is
a syntax error with the operand of that keyword. In that case, further error messages may be displayed and you may
be prompted with message IEA336A to re-specify the parameter.
System action: The system continues.
Operator response: None.
Source: System Initialization (IPL/NIP).
Detecting Module: IEAVNP03
Routing Code: Note 9
Descriptor Code: 12

| IEA661I MAXIMUM NUMBER OF MACHMIG STATEMENTS EXCEEDED

| Explanation: More than three MACHMIG statements were specified in LOADxx.
| System action: IPL continues.
| Operator response: None.
| Source: Initial Program Load (IPL).
| Detecting Module: IPXI50PS

| IEA662I MACHMIG STATEMENT IGNORED: stmt

| Explanation: The MACHMIG statement stmt will be ignored because more than three (the maximum allowed)
| MACHMIG statements were specified. In the message text:
| stmt Columns 10-72 of the MACHMIG statement that will not be used.
| System action: IPL continues.
| Operator response: None.
| Source: Initial Program Load (IPL).
| Detecting Module: IPXI50PS

| IEA663I LOADXX MACHMIG STATEMENT PARAMETER parm WAS NOT RECOGNIZED.

| INITIALIZATION CONTINUES
| Explanation: An error was detected within a MACHMIG statement from the LOADxx parmlib member. In the
| message text:
| parm The parameter that was not recognized. If the parameter is longer than 16 characters, only the first 16
| characters are shown.
| System action: IPL continues.
| Operator response: None.
| Source: Initial Program Load (IPL).
| Detecting Module: IEAIPL99

812 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA705I

IEA705I 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. n the
message text:
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 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 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:

cde rc w1 w2 w3 w4 w5 w6
1xx all a b c d f
2xx all a b c h
3xx all a b c d f g
4xx all a b c d f g
5xx all a b c e
6xx all a b c e
7xx all a b c h
8xx 4-14 a b c d f
18,20 a b c d f g
24,28 a b c d f i
9xx all a b c d f g
Axx all a b c d f g
Bxx 4-4C a b c d
50-54 a b c d f i
Dxx 04 a b c d f g
08 a b c d f

In the table:
a The current address space control block (ASCB) address.
b The dispatched task control block (TCB) address.
c The input TCB address.
d The first two bytes are the subpool identifier requested. The third byte contains request flags, as follows:
1... .... The access list entry table (ALET) was specified on the STORAGE macro.
.1.. .... Storage can be backed above or below 16 megabytes.

Chapter 21. IEA messages 813

IEA710A

..1. .... Virtual storage can be above 16 megabytes.

...1 .... Virtual storage can 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 contains request flags, as follows.

1... .... Reserved.
.1.. .... Storage Key was specified on the GETMAIN, FREEMAIN, or STORAGE macro. (This is not used by
SVC 4, 5, 10 branch entry of SVC 120 branch entry.)
..1. .... Access Register 15 (AR 15) is used.
...1 .... Indicates AMODE(,ANY64).
.... 1... CHECKZERO=YES was specified on STORAGE OBTAIN or GETMAIN.
.... .1.. TCBADDR was specified on STORAGE OBTAIN or RELEASE.
.... ..xx Owner information, as follows:
'00' OWNER=HOME
'01' OWNER=PRIMARY
'10' OWNER=SECONDARY
'11' OWNER=SYSTEM
e The address of the parameter list supplied by the caller.
f The length of the area requested for GETMAIN, FREEMAIN, or STORAGE.
g The starting address of the area to be freed.
h The address of the virtual storage manager (VSM) work area.
i The address specified on the INADDR parameter for the GETMAIN or STORAGE macro.
System action: The system abnormally ends the job step.
Operator response: See the operator response for the accompanying abend and reason codes.
System programmer response: See the system programmer response for the accompanying abend and reason codes.
Source: Virtual storage manager (VSM)
Routing Code: 11
Descriptor Code: 6

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.
Operator response: Notify the system programmer 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.
Source: Contents supervision (CSV)
Detecting Module: IEAVNP05

814 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA711E • IEA712I

Routing Code: -
Descriptor Code: -

IEA711E LPALSTxx INPUT TRUNCATED AFTER dsname

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.
In the message text:
xx Identifies the parmlib member of LPALST.
dsname The specified data set name.
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.
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 operator's screen.
Operator response: Notify the system programmer.
Application Programmer Response: This is probably 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).
Source: Contents supervision (CSV)
Detecting Module: IEAVNP05
CSVLLCRE
Routing Code: 1,10
Descriptor Code: 11,12

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.
In the message text:
dsname
The specified data set name.
text
One of the following:
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 is
accompanied by message IEA317A or IEA319I.
UNABLE TO OPEN
An error occurred while opening the data set. This condition is 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.
System action: The system continues processing.
Operator response: Notify the system programmer.

Chapter 21. IEA messages 815

IEA713I • IEA716I

System programmer response: This is probably an installation error. Correct the condition that caused the problem.
Source: Contents supervision (CSV)
Detecting Module: IEAVNP05
Routing Code: -
Descriptor Code: 12

IEA713I LPALST LIBRARY CONCATENATION (dsname) . . (dsname)

Explanation: This message lists the data sets, dsname, concatenated to SYS1.LPALIB.
In the message text:
dsname The specified data set name.
System action: Normal processing continues.
Source: Contents supervision (CSV)
Detecting Module: IEAVNP05
Routing Code: -
Descriptor Code: -

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
Explanation: The system could not process a library specified in a parmlib member.
In the message text:
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
v LNKLST
The Message content is "text- LNKLST DATA SET library", when library is any of the following values:
LINKLIB, MIGLIB, SVCLIB, LINKLIBE, or MIGLIBE.
Explanation: The system goes into a wait state rather than just ignoring the library as happens for all
other libraries.
library The name of the library data set specified in the parmlib member, member
System action: The system continues processing the 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.

816 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA738I • IEA740W

Operator response: If UNABLE TO MOUNT appears in the message text, mount the appropriate volume and reIPL
the system.
See the operator response for accompanying messages.
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 bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
Source: Contents supervision (CSV)
Detecting Module: CSVMLPRM
IEAVNPE5
Routing Code: -
Descriptor Code: 12

IEA738I MAXUSER=val1, RSVNONR=val2, RSVSTRT=val3 SUM EXCEEDS MAXIMUM OF 32767

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).
In the message text:
val1 The value of MAXUSER in IEASYSxx
val2 The value of RSVNONR in IEASYSxx
val3 The value of RSVSTRT in IEASYSxx
System action: The system prompts the operator to respecify the three parameters by issuing message IEA906A
three times: once each for MAXUSER, RSVNONR, and RSVSTRT.
Operator response: Respond to message IEA906A as the system programmer directs.
System programmer response: Do the following:
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.
Source: Supervisor control
Detecting Module: IEAVNP09
Routing Code: 2,10
Descriptor Code: 12

IEA740W SUPERVISOR UNABLE TO RECOVER FROM SVC D LOOP

Explanation: While the system was processing the Supervisor Call (SVC) instruction for an ABEND macro, a
program check occurred recursively.
System action: The system enters wait state X'104'.
Operator response: See the operator response for wait state X'104'.
System programmer response: See the system programmer response for wait state X'104'.
Source: Supervisor control
Detecting Module: IEAVESVR
Routing Code: 2,10

Chapter 21. IEA messages 817

IEA763I • IEA764I

Descriptor Code: 2

IEA763I OPTIONS FOR OPERATIONS COMPONENT TRACE ARE NOT VALID.

Explanation: One of the following occurred:
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 MCACHE
v RECOVERY
v SERIALIZ
v CONSDATA
v COMMAND
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) is initialized with the default tracing
options.
Operator response: Do one of the following:
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.
Source: Communications Task (COMMTASK)
Detecting Module: IEAVH703
Routing Code: Note 25
Descriptor Code: Note 25

IEA764I REQUEST TO CHANGE OPERATIONS COMPONENT TRACE BUFFER SIZE FAILED - reason
Explanation: The trace buffer size could not be changed. In the message text, reason can be:
STORAGE UNAVAILABLE
The system cannot obtain storage for the new trace buffer size.
TRACE ACTIVE
While the trace is active, the buffer size can not be changed.

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.

818 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA765I • IEA766I

System action: The TRACE CT command is rejected. The operations component trace buffer size is not changed.
Operator response: If "STORAGE UNAVAILABLE" appears in the message text, 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.
If "TRACE ACTIVE" appears in the message text, do the following:
1. Take note of the current trace options by issuing D TRACE,COMP=SYSOPS.
2. Turn tracing off by issuing TRACE CT,OFF,COMP=SYSOPS.
3. Change the trace buffer size and turn tracing back on by issuing TRACE CT,nnnnM,COMP=SYSOPS where nnnn
is the size of the trace buffer. You will also need to reply to the WTOR (ITT006A) specifying the options to be
traced.
Source: Console Services
Detecting Module: IEAVH703
Routing Code: -
Descriptor Code: 5

IEA765I CTRACE DEFINE FOR SYSOPS FAILED, TRACING is INITIALIZED {WITH DEFAULT PARMLIB
MEMBER | WITH NO PARMLIB MEMBER} , RETCODE=xx, RSNCODE=yy
Explanation: Component trace initialization by the operations (SYSOPS) 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 z/OS MVS
Programming: Authorized Assembler 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 is used to define OPS CTRACE. If CTIOPS00 was specified (or selected by default), OPS
CTRACE is 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.
Source: Communications Task (COMMTASK)
Detecting Module: IEAVN704
Routing Code: 2,10
Descriptor Code: 12

IEA766I CTRACE DEFINE FOR SYSOPS FAILED, TRACING WILL NOT BE INITIALIZED, RETCODE=xx,
RSNCODE=yy
Explanation: Component trace initialization by the operations (SYSOPS) 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 z/OS MVS
Programming: Authorized Assembler Services Reference ALE-DYN under "CTRACE Return and Reason Codes".
System action: OPS CTRACE is not initialized.
System programmer response: Search the problem reporting data bases for a fix for the problem. If no fix exists,
contact the IBM Support Center.
Source: Communications Task (COMMTASK)
Detecting Module: IEAVN704
Routing Code: 2,10

Chapter 21. IEA messages 819

IEA767A • IEA768I

Descriptor Code: 12

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:
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.
Source: Communications Task (COMMTASK)
Detecting Module: IEAVH704

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:
v Give control to the post dump installation exit routine
v Process a dump request
v Process a DUMPDS operator command

In the message text:

mc 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.
return-code
The return code placed in register 15 by the failing module.
reason-code
The reason code placed in register 0 by the failing module. When mc is 04, the system does not put a value
into register 0.
System action: The system continues processing, but cannot process dump requests. The system writes a logrec data
set error record.
Operator response: Notify the system programmer.
System programmer response: 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 logrec data set error record.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTSAI, IEAVTSAS
Routing Code: 2
Descriptor Code: 4

820 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA774I • IEA792I

IEA774I IEA17741

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.
In the message text:
nnnn
The subchannel identifier.
dev
The device number.
System action: The system continues subchannel initialization with the next sequential subchannel number.
Operator response: Contact hardware support.
Source: Input/output supervisor (IOS)
Detecting Module: IEAVNP02
Routing Code: 2
Descriptor Code: 12

| IEA775I INITIALIZATION FAILED FOR UTILITY SUBCHANNEL ssssssss CC xx

| Explanation: The system tried to initialize a subchannel for a non-device service such as storage-class memory
| (SCM). The subchannel was not operational or busy in a state that could not be cleared.
| In the message text:
| ssssssss
| The subchannel identifier.
| xx The failing condition code.
| System action: The system continues subchannel initialization with the next sequential subchannel number.
| Operator response: Contact hardware support.
| Source: Input/output supervisor (IOS)
| Detecting Module: IOSVUCOP
| Routing Code: 2
| Descriptor Code: 12

IEA792I ADDRESS SPACE asid CANNOT BE TERMINATED - JOB [jobname]

Explanation: The system was trying to end an address space when an error occurred.
In the message text:
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 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

Chapter 21. IEA messages 821

IEA793A • IEA794I

recording area (VRA) of the system diagnostic work area (SDWA).

Operator response: Notify the system programmer.
System programmer response: 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 logrec data set error record and messages.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTMTC
Routing Code: 2,10
Descriptor Code: 6

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 IEA799I message for details about the dump data set allocation failure.
In the message text:
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
v The operator replies D to delete the captured dump
v The interval specified by the MSGTIME parameter on the CHNGDUMP command expires
Operator response: Do one of the following:
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 is 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.
Source: SVC dump
Detecting Module: IEAVTSCD
Routing Code: 1
Descriptor Code: 2

IEA794I SVC DUMP HAS CAPTURED: DUMPID=dumpid REQUESTED BY JOB (*MASTER*) DUMP
TITLE=dump-title
Explanation: The system has captured the data for the SVC dump.
In the message text:
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: If the dumpid contains characters DCB, the dump capture is successful for a SDUMP(X) request to a

822 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA796E

DCB. The data is written to the data set associated with the specific DCB. Otherwise, the system writes the SVC
dump to the dump data set, if available, and issues message IEA611I or IEA911E. IEA611I and IEA911E indicate:
v Whether the system wrote a complete or partial dump
v Which dump data set contains the dump.

If no dump data set is available, the dump remains captured and the system issues message IEA793A. IEA793A
indicates:
v That a dump is captured but no dump data set is available
v The DUMPID to use on the DISPLAY DUMP command
v That the operator can use the DUMPDS command to clear or cancel the dump.
Source: SVC dump
Detecting Module: IEAVTSCC
Routing Code: 2
Descriptor Code: 4

IEA796E ACR PROCESSING HAS TAKEN CPU x [LOGICALLY] OFFLINE BECAUSE text
Explanation: Alternate CPU recovery (ACR) has successfully placed a failing processor (CPU) logically and
physically offline.
In the message text:
x The processor that was taken offline.
LOGICALLY
The processor was taken logically offline.
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
Clock comparator damage
PS Primary sync damage
AD External Time Reference (ETR) attachment damage
SL Switch to local
CC Clock comparator damage
text
One of the following:
v AN UNKNOWN ERROR OCCURRED.
v CPU x CHECKSTOPPED.
v CPU x REACHED ITS vv MACHINE-CHECK THRESHOLD.
v OF SPIN-LOOP RECOVERY PROCESSING.
v CPU x's TOD CLOCK COULD NOT BE SYNCHRONIZED.
v OF A MALFUNCTION IN THE DAT HARDWARE.
| v OF aaa (where aaa is the three-character reason code that indicates why ACR was performed).
v CPU x's CLOCK COULD NOT BE SYNCHRONIZED TO THE ETR.
v AN UNRECOVERABLE MACHINE ERROR OCCURRED.
v PHYSICAL VARY FOR THE CPU FAILED.

Chapter 21. IEA messages 823

 IEA797W • IEA798W

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.
PHYSICAL STATE OF THE CPU UNKNOWN
The service processor request was unable to complete. The failing processor is not physically offline.
THIS CPU SUPPORTED THE FOLLOWING: CRYPTO
The CRYPTO was taken offline.
System action: The system continues processing.
The system does not automatically remove this message from the display console. The operator must manually delete
the message.
The system writes a logrec data set error record.
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.
| If OF aaa appears in the message text, contact the IBM Support Center.
Source: Alternate CPU recovery (ACR)
Detecting Module: IEAVTACR, IEAVTCRE
Routing Code: 2,10
Descriptor Code: 11

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'.
Operator response: See the operator response for wait state X'084'.
System programmer response: See the system programmer response for wait state X'084'.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTRTV
Routing Code: 1
Descriptor Code: 1

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.
System action: The system enters non-restartable 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.

824 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA799I • IEA802W

Source: Recovery termination manager (RTM)

Routing Code: Note 4
Descriptor Code: 1

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.
In the message text:
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 z/OS 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 z/OS MVS Programming: Authorized Assembler Services 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 z/OS MVS Programming: Authorized Assembler Services 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 is issued.
Operator response: Notify the system programmer.
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.

Chapter 21. IEA messages 825

IEA806I • IEA809I

System action: The system enters wait state X'A00'.

Operator response: See the operator response for wait state X'A00'.
System programmer response: See the system programmer response for wait state X'A00'.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTRTM
Routing Code: -
Descriptor Code: 1

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'
In the message text:
jjj
The job name.
sss
The step name.
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.
System programmer response: If the problem recurs and if 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 messages in the job
log, the JCL for the job, and all printed output and output data sets related to the problem.
Routing Code: 1,10
Descriptor Code: 4

IEA808I GTF TERMINATED DURING TRACE FORMATTING

Explanation: During formatting of the generalized trace facility (GTF) trace buffers, GTF encountered a severe error.
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.
Source: Generalized trace facility (GTF)

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 reporting data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center.
Source: Generalized trace facility (GTF)
Detecting Module: IGC0F05A
Routing Code: Note 11
Descriptor Code: -

826 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA810E • IEA813E

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.
System action: The system abnormally ends the task which requested paging of the LPA page.
Operator response: On the next IPL, create a new LPA through the CLPA parameter when specification of system
parameters is requested.

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.
In the message text:
xxx The total number of page data sets.
System action: The system issues message IEA906A to prompt the operator to specify the PAGTOTL parameter
again, or to press the ENTER button on the console.
Operator response: Either specify the PAGTOTL values again or press the ENTER button, which specifies the
default values of (40,1).
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 12

IEA812E PAGTOTL VALUE INCREASED TO ppp

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.
In the message text:
ppp Specifies the value to which PAGTOTL was increased.
System action: The system continues processing using the new PAGTOTL value.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM1
Routing Code: Note 9
Descriptor Code: 12

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.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 12

Chapter 21. IEA messages 827

IEA814D • IEA820I

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.
In the message text:
dsname The name of the data set.
System action: The system waits for the operator to 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.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM1
Routing Code: Note 9
Descriptor Code: 2

IEA820I TRANSACTION DUMP REQUESTED BUT NOT TAKEN. reason

Explanation: The requested transaction dump was not taken reason is one of the following lists:
AN I/O ERROR OCCURRED
ANOTHER TRANSACTION DUMP WAS IN PROGRESS
AUTOMATIC ALLOCATION OF DUMP DATA SET FAILED
BOTH DCB AND DATA SET NAME SUPPLIED
CALLER AUTHORIZATION INSUFFICIENT FOR REQUESTED FUNCTIONS
COULD NOT ACCESS DATASPACE FOR AUTOMATIC ALLOCATION
DATA SET NAME ALET NOT VALID
DATA SET NAME NOT ACCESSIBLE
DATASPACE CREATION FAILED FOR AUTOMATIC ALLOCATION
DATASPACE LIST ALET NOT VALID
DATASPACE LIST DATA NOT ACCESSIBLE
DATASPACE LIST NOT VALID
DCB ALET NOT VALID
DCB NOT ACCESSIBLE
DUMP DATA SET NAME NOT VALID
DUMP DATA SET NAME SYMBOL SUBSTITUTION FAILED
DUMP DATA SET NAME TOO LONG
DUMP INDEX DSNAME ALET NOT VALID
DUMP INDEX DSNAME NOT ACCESSIBLE
DUMP INDEX DSNAME NOT VALID
ECB ALET NOT VALID
ECB DATA NOT ACCESSIBLE
ECB NOT VALID
HEADER ALET NOT VALID
HEADER DATA NOT ACCESSIBLE
HEADER LONGER THAN 100 CHARACTERS
INCIDENT TOKEN ALET NOT VALID
INCIDENT TOKEN DATA NOT ACCESSIBLE
INTERNAL PROCESSING ERROR DETECTED, REASON CODE=rsncode
NO DCB OR DATA SET NAME SUPPLIED
NO HEADER SUPPLIED
PARAMETER LIST ADDRESS ZERO
PARAMETER LIST ALET NOT VALID
PARAMETER LIST LENGTH NOT VALID FOR VERSION
PARAMETER LIST NOT ACCESSIBLE
PARAMETER LIST VERSION NOT VALID
PROBLEM DESCRIPTION AREA ALET NOT VALID
PROBLEM DESCRIPTION AREA DATA NOT ACCESSIBLE
PROBLEM DESCRIPTION AREA NOT VALID

828 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA821I

REMOTE AREA ALET NOT VALID

REMOTE AREA DATA NOT ACCESSIBLE
REMOTE 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
SYMPTOM RECORD ALET NOT VALID
SYMPTOM RECORD DATA NOT ACCESSIBLE
SYMPTOM RECORD NOT VALID
SYSMDUMP DUMP MODE SET TO NODUMP BY CHNGDUMP COMMAND
THE DUMP WAS SUPPRESSED BY DAE
THE DUMP WAS SUPPRESSED BY SLIP

In the message text:

rsncode Internal processing error reason code. is one of the following:
01 Unable to obtain storage for transaction dump from subpool 230 below the line.
02 Unable to establish recovery environment for IEAVTDMP.
03 Unable to obtain storage for transaction dump from subpool 239 above the line.
04 Unable to obtain storage for transaction dump from subpool 231 above the line.
05,06,07
Unable to obtain storage for transaction dump from subpool 239 above the line.
08 Unable to obtain storage for transaction dump from subpool 250 above the line.
FF IEAVTDMP's recovery received control.
System action: The system continues processing.
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
Routing Code: The routing code is either 11 or 2. It is 2 when the TDUMP is issued from DUMPSRV.

IEA821I SYNTAX ERROR IN “SVC=” PARAMETER

Explanation: Non-alphanumeric characters were specified in the SVC parameter in the IEASVCxx parmlib member.
System action: The system prompts the operator to 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.

Report the problem to the system programmer.

System programmer response: Check the statements in the IEASVCxx parmlib member for syntax problems.
Source: Supervisor control
Detecting Module: IEAVNP25
Routing Code: 2,10
Descriptor Code: 4

Chapter 21. IEA messages 829

IEA822I • IEA823I

IEA822I {COMPLETE∨PARTIAL} 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).
In the message text:
COMPLETE
The transaction dump was complete.
PARTIAL
The transaction dump was not complete.
dsname The dump was written to the dsname data set.
System action: The system continues processing.
System programmer response: Open the dump under IPCS to view diagnostic data.
Source: IEAVTDMP
Detecting Module: IEAVTDMP
Routing Code: The routing code is either 11 or 2. It is 2 when the TDUMP is issued from DUMPSRV.

IEA823I IEASVCxx: SVCnum: text

Explanation: text is one of the following:
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.

In the message text:

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.
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.
System programmer response: Check the statements in the IEASVCxx parmlib member for syntax problems.
Source: Supervisor control
Detecting Module: IEAVNP25
Routing Code: 2,10
Descriptor Code: 4

830 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA824I • IEA826I

IEA824I IEASVCxx: SVCnum: DUPLICATE parm KEYWORD.

Explanation: A keyword option appears more than once on a single statement in the IEASVCxx parmlib member for
an SVC number.
In the message text:
xx The suffix of the IEASVCxx parmlib member
num The SVC number
parm The parameter for which the keyword option was specified more than once
System action: The system ignores the statement.
System programmer response: Check the statements in the IEASVCxx parmlib member for syntax problems.
Source: Supervisor control
Detecting Module: IEAVNP25
Routing Code: 2,10
Descriptor Code: 4

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.
In the message text:
xx The suffix of the IEASVCxx parmlib member
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
System action: The system ignores the statement.
System programmer response: Check the statements in the IEASVCxx parmlib member for syntax problems.
Source: Supervisor control
Detecting Module: IEAVNP25
Routing Code: 2,10
Descriptor Code: 4

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).
In the message text:
xx The suffix of the IEASVCxx parmlib member
num The SVC number specified
t The user type specified
name The module name for which the entry point address could not be found
System action: The system ignores the statement.
System programmer response: Do one or both of the following:
v Check the statements in the IEASVCxx parmlib member for syntax problems.
v Determine why the load module is missing from the nucleus or the LPA.
Source: Supervisor control

Chapter 21. IEA messages 831

IEA827I • IEA829I

Detecting Module: IEAVNP25, IEAVNPS5

Routing Code: 2,10
Descriptor Code: 4

IEA827I {COMPLETEorPARTIAL} TRANSACTION DUMP WRITTEN TO number DATASETS STARTING

FROM dsname COMBINE USING COPYDUMP PRIOR TO VIEWING IN IPCS
Explanation: The system wrote a complete or partial transaction dump to one or more data sets on a direct access
storage device (DASD).
In the message text:
COMPLETE
The transaction dump is complete.
PARTIAL
The transaction dump is not complete.
number How many datasets are used by the dump.
dsname The first of the series of datasets that hold the dump.
System action: The system continues processing.
System programmer response: Combine the datasets into one using COPYDUMP and open in IPCS to view
diagnostic data.
Source: IEAVTDMP
Detecting Module: IEAVTDMP

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.
In the message text:
xx The suffix of the IEASVCxx parmlib member
nnnn The statement number in the IEASVCxx parmlib member where the system parser encountered an error
System action: The system ignores the statement.
System programmer response: Check statement number nnnn in the IEASVCxx parmlib member for syntax
problems.
Source: Supervisor control
Detecting Module: IEAVNP25
Routing Code: 2,10
Descriptor Code: 4

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).
In the message text:
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 One of the following:
LPA for the link pack area

832 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA830I • IEA833I

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.
Source: Supervisor control
Detecting Module: IEAVNPST
Routing Code: 2,10
Descriptor Code: 4

IEA830I IEASVCxx: DUPLICATE UPDATES TO SVCnum IGNORED.

Explanation: One or more IEASVCxx parmlib members contain two or more SVCPARM statements for the same
SVC number.
In the message text:
xx The suffix of the IEASVCxx parmlib member
num The SVC number for which there two or more statements
System action: The system uses the first correct SVCPARM statement and ignores any duplicate statements.
System programmer response: Remove duplicate SVCPARM statements for the same SVC number from the
IEASVCxx parmlib members.
Source: Supervisor control
Detecting Module: IEAVNP25
Routing Code: 2,10
Descriptor Code: 4

IEA832I IEASVCxx: SVCnum: pval IS NOT A VALID parm.

Explanation: A parameter specified on a statement in an IEASVCxx parmlib member is not valid.
In the message text:
xx The suffix of the IEASVCxx parmlib member
num The SVC number for which an incorrect parameter was specified
pval The incorrect value specified for the parameter
parm The parameter for which an incorrect value was specified
System action: The system ignores the statement.
System programmer response: Check the statements in the IEASVCxx parmlib member for syntax problems.
Source: Supervisor control
Detecting Module: IEAVNP25
Routing Code: 2,10
Descriptor Code: 4

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.
In the message text:

Chapter 21. IEA messages 833

IEA836I • IEA837I

xx The suffix of the IEASVCxx parmlib member

nnnn The statement number on which the incorrect SVC number was specified
num The incorrect SVC number
System action: The system ignores the statement.
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 statements in the
IEASVCxx parmlib member for syntax problems.
Source: Supervisor control
Detecting Module: IEAVNP25
Routing Code: 2,10
Descriptor Code: 4

IEA836I PAGE DATA SET dsname NOT ALLOCATED - ERROR CODE err INFORMATION CODE xxxx
Explanation: A request to allocate a page data set resulted in an error.
In the message text:
dsname The name of the data set.
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.
All other cases
The system issues message IEA922D to let the operator respecify the data set name before continuing paging
initialization.
Operator response: Notify the system programmer.
System programmer response: Respond according to the error code and information code in the message text.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM2
Routing Code: Note 9
Descriptor Code: 12

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.
In the message text:
dev The device number.

834 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA838I • IEA839I

System action: The system continues operation. If warm start data was lost, the system issues message ILR003A to
force a quick start.
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 bases for a
fix for the problem. If no fix exists, contact the IBM Support Center.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM2
Routing Code: Note 9
Descriptor Code: 12

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).
In the message text:
yyddd
The date, in years (00 through 99) and in days of the year (000 through 366)
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 The processor identifier
symptoms
The symptoms from the dump header record for the original abnormal end
System action: DAE suppresses the SYSMDUMP dump.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTSYS
Routing Code: 11
Descriptor Code: -

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.
Operator response: Notify the system programmer.
System programmer response: If the error cannot be resolved, search problem reporting data bases for a fix for the
problem. If no fix exists, contact the IBM Support Center.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 4

Chapter 21. IEA messages 835

IEA841E • IEA842E

IEA841E {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.
In the message text:
dsname The name of the data set.
dev The device number.
System action: The system does one of the following:
For a cold start: The system issues message IEA922D. In response, the operator may choose a new data set 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 IEA922D. In response, the operator may 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 is forced.
v For a COMMON data set, if PLPA pages did not overflow to the data set on the cold start associated with this
warm 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 warm 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. 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.
System programmer response: Contact hardware support.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM2
Routing Code: Note 9
Descriptor Code: 12

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.
In the message text:
dsname The name of the data set.
System programmer response: Contact hardware support.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM2

836 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA843I

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 overflow to the data set on the cold start associated with this
quick start, the system issues message IEA922D. In response, the 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, 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 is forced.
v For a COMMON data set, if PLPA pages did not overflow to the data set on the cold start associated with this
warm start, the system issues message IEA922D. In response, 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 warm start cannot continue. The system
forces a cold start, issues message IEA929I, 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.
Routing Code: Note 9
Descriptor Code: 12

IEA843I MODULE mmmmmmmm NOT FOUND

Explanation: During system initialization, a resource initialization module (RIM) cannot find a module needed for
SNAP and ABEND dumping.
In the message text:
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: One possible reason for the message is that the required aliases to an ABDUMP
module are missing. Ensure that the LPALIB modules and all their aliases have been accounted for by any updates.
Unfortunately, this problem cannot be corrected using the dynamic LPA facility. The system must be re-IPLed.
Source: ABEND dump
Detecting Module: IEAVTABI
Routing Code: 10
Descriptor Code: 4

Chapter 21. IEA messages 837

IEA846I • IEA848I

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.
In the message text:
x The processor.
yyyy
A hexadecimal reason code explaining the error. yyyy is one of the following:
0040 Service processor error.
03F0 Processor x is not installed.
04F0 Processor x is not in the configuration.
10F0 Processor x is powered off.
System action: The system continues processing.
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.
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.
System programmer response: Determine why the system was unable to signal the console. If necessary, contact
hardware support.
Source: Reconfiguration
Detecting Module: IEAVNP00
Routing Code: -
Descriptor Code: 5

IEA848I INSTALLATION PREDUMP EXIT, dumpexit, MODIFIED/SUPPRESSED THE DUMP REQUEST

--or--

NO DUMP WAS PRODUCED FOR THIS ABEND, DUE TO SYSTEM OR INSTALLATION

REQUEST

--or--

DUMP SUPPRESSED - USER NOT AUTHORIZED BY SAF

--or--

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:

838 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA848I

INSTALLATION PREDUMP EXIT, dumpexit, MODIFIED/SUPPRESSED THE DUMP REQUEST

The dump was suppressed by the installation predump exit.
In the message text:
dumpexit
The most recent exit that requested suppression.
NO DUMP WAS PRODUCED FOR THIS ABEND, DUE TO SYSTEM OR INSTALLATION REQUEST
The system or installation requested no dump for this abend.
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.
DUMP SUPPRESSED - ABDUMP SERIALIZATION DEADLOCK AVOIDED, SVC DUMP TAKEN INSTEAD
ABDUMP (SYSUDUMP, SYSMDUMP, or SYSABEND) processing could not produce a dump because another
task held a critical resource. The resource was held for an interval that was longer than the value set for the
TIMEENQ option of ABDUMP. An SVC dump was taken instead, capturing system data for later analysis. The
dump title includes the JOBNAME of the abending task. Processing continues, since the potential deadlock was
avoided.
DUMP SUPPRESSED - ABDUMP SERIALIZATION DEADLOCK AVOIDED, SVC DUMP FAILED RC=sscc
ABDUMP (SYSUDUMP, SYSMDUMP, or SYSABEND) processing could not produce a dump because another
task held a critical resource. The resource was held for an interval that was longer than the value set for the
TIMEENQ option of ABDUMP. Processing continues, since the potential deadlock was avoided. 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 are:
02 The capture phase of another SVC dump was in progress.
04 The SVC dump was suppressed by a SLIP NODUMP command.
0B The dump was suppressed by DAE.

Refer to z/OS MVS Programming: Authorized Assembler Services Reference LLA-SDU for a complete description of
the SDUMPX macro return reason codes.

In the message text:

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:
v Use the SDUMP macro to obtain a dump, or
v Use the SNAP macro to selectively dump data areas.

Alternately, a SLIP trap can 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 z/OS Security Server RACF Security Administrator's Guide.
System action: The system suppresses the ABDUMP. In the case of DEADLOCK AVOIDED, an SVC dump can be
generated, associated with ABEND X'333', reason codeX'30'. LOGREC data contains the name of the resource and the
JOBNAME that the dump was taken for.
Application Programmer Response: If a dump needed to diagnose a problem was suppressed, notify the system
programmer.
System programmer response:
v For INSTALLATION PREDUMP EXIT or NO DUMP WAS PRODUCED make sure that the system does not
suppress needed dumps.
v For USER NOT AUTHORIZED, the security authority can be changed to allow the application programmer to get
the necessary dump by permitting the user to have READ or UPDATE access to the IEAABD.DMPAUTH facility
as described in the z/OS Security Server RACF Security Administrator's Guide.

Chapter 21. IEA messages 839

IEA849I • IEA850I

v For ABDUMP MAY NOT DUMP, the security authority can be changed to allow the application programmer get
the necessary dump. Note that the dump can contain sensitive installation data since fetch protected storage is
included in this dump.
v For DEADLOCK AVOIDED several options are available:
– When an SVC dump is available, analysis of the potential hang condition can be done using the IPCS
VERBEXIT GRSTRACE or ANALYZE RESOURCE command against the dump. Search for the MAJOR names
SYSZTIOT and SYSIEA01. The resource, which ABDUMP detected the possible deadlock condition for, will have
multiple tasks (TCBs) listed for the same MINOR name. One of the following conditions may exist:
- The TCB holding the resource exclusively may have a programming error.
- Multiple ABDUMPs could be processing and the first one is holding the SYSIEA01 enqueue longer than the
TIMEENQ interval allowed.
– The detection interval can be changed if either SVC dumps are being generated too often for the installation, or
if hangs are not being detected quickly enough. The interval can be changed using the CHNGDUMP
SET,ABDUMP,TIMEENQ = nnnn command. Once a value is determined for the installation, the command
should be placed into a COMMNDxx member of PARMLIB. This ensures the setting as the installation default
when the system is IPLed.
– All associated dumps can be suppressed by using the following command:
SLIP SET,C=333,ID=X333,A=NOSVCD,REASON=30,END
Source: Dumping Services
Detecting Module: IEAVTABD
Routing Code: 11
Descriptor Code: 4

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.
In the message text:
dsname The data set to which the dump was to be written.
System action: The system continues processing.
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.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTABD
Routing Code: 1
Descriptor Code: -

IEA850I FOLLOWING is 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:
ser The serial number of the volume
devtyp The device type
ccc-ccc The characteristics requested for the volume, as follows:
P/R-PUB
Permanently resident, public

840 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA851A • IEA851I

P/R-PRV
Permanently resident, private
P/R-STR
Permanently resident, storage
RSV-PUB
Reserved, public
RSV-PRV
Reserved, private
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.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 4

IEA851A REPLY DEVICE ADDRESSES OR U

Explanation: This message prompts the operator for a reply to message IEA851I.
System action: The system waits for the operator to 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.
If no volumes are to be mounted, enter REPLY id,‘U’.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 4

IEA851I FOLLOWING MAY BE MOUNTED ser ON devtype

Explanation: During processing of the VATLSTxx parmlib member, the system found that all volumes in the
member were not mounted.
ser ON devtype appears once for each unmounted volume. In the message text:
ser
The serial number of a volume to be mounted.
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 might be required; the installation must select the device that has any
required special features.
System action: The system issues message IEA851A.
Operator response: See the operator response for message IEA851A.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2

Chapter 21. IEA messages 841

IEA852A • IEA853A

Descriptor Code: 12

IEA852A REPEAT REPLY

Explanation: This message prompts the operator for a reply to message IEA852I.
System action: The system waits for the operator to reply.
Operator response: Enter the reply again correctly or enter REPLY id,‘U’.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 4

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.
n The cause of the error, as follows:
n Meaning
1 The reply specified a duplicate device number.
2 The specified device number is unknown to the system.
3 The specified device contains a permanently resident or reserved volume.
4 The specified device is not direct access.
5 The reply specified a device type is not needed for mounting of the requested volumes.
6 The system could not check for a data path to the offline device.
7 No data path is available to the specified device.
8 No operational data path is available to the specified device.
9 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.
System action: The system issues message IEA852A.
Operator response: See the operator response for message IEA852A.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 12

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.
System action: The system waits for the operator to reply.
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.

842 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA854I • IEA855I

REPLY id,‘END’
If the reply is END, no more VATLST processing is done.
REPLY id,‘xx’
If the reply is xx, VATLSTxx is processed before processing the remaining VATLST members. nn is a new
VATLST member.

If necessary, reIPL the system.

Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 4

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:
v If message IEA306I precedes this message, an I/O error occurred when reading the label.
v The volume does not contain a standard label.
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.
System action: For an MSS volume, the VATDEF entry is ignored; processing continues with the remaining
VATLSTxx entries.
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.
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).
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 12

IEA855I INVALID VATLSTxx ENTRY

Explanation: During processing of a VATLSTxx parmlib member, the system found an incorrect entry.
System action: Processing continues with the remaining VATLSTxx entries.
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.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 4

Chapter 21. IEA messages 843

IEA856W • IEA858E

IEA856W ATTEMPTED ACR OF LAST CPU - SYSTEM TERMINATED

Explanation: Alternate CPU recovery (ACR) attempted to remove the last standard CP. There must be at least one
standard CP online in order for the system to run.
System action: The system issues wait state code 05A and enters a non-restartable wait state.
Operator response: Contact the system programmer.
System programmer response: The problem might be due to a hardware or software problem on the last standard
CP. If it is a hardware problem, you will need to reconfigure the partition, so that it contains at least 1 standard CP. If
it is a software problem, you probably want to take a stand alone dump and then reIPL the system.
Source: Alternate CPU recovery (ACR)
Detecting Module: IEAVTACR

IEA857W 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.
In the message text:
H ACR encountered a hardware error.
S ACR encountered a software error.
x An error code, which is one of the following:
1 The failure occurred prior to entering post processing.
2 The failure occurred during ACR post processing.
nn Recovery processor identifier.
dd Failed processor identifier.
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 response for wait state X'052'.
System programmer response: If S appears in the message text, see the system programmer response for wait state
X'051'.
If H appears in the message text, see the system programmer response for wait state X'052'.
Source: Alternate CPU recovery (ACR)
Detecting Module: IEAVTCR1
Routing Code: 1
Descriptor Code: 1

IEA858E ACR COMPLETE CPU NOW OFFLINE [PHYSICAL VARY FAILED]

Explanation: A failing processor was placed logically offline by alternate CPU recovery (ACR).
In the message text:
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.
System action: The system continues processing. The system writes a logrec data set error record.

844 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA859I • IEA860A

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.
Source: Alternate CPU recovery (ACR)
Detecting Module: IEAVTACR
Routing Code: 2,10
Descriptor Code: 4

IEA859I 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.
System action: The system unloads the volume.
Operator response: Mount a volume requested in message IEA851A on this unit. Reply ‘U’ to message IEA893A
when the device is ready.
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.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 12

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.
System action: The system waits for the operator to 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’.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 4

Chapter 21. IEA messages 845

IEA861A • IEA863I

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.
System action: The system waits for the operator to 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.
Source: Allocation/unallocation
Routing Code: 2
Descriptor Code: 4

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:
v RCT was unable to attach the dump task.
v RCT was unable to attach started task control (STC).
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.
System programmer response: Do the following:
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 bases for a fix for the problem. If no fix exists, contact 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
Routing Code: 10
Descriptor Code: 6

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.

846 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA864I • IEA865I

In the message text:

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.
System action: The system ignores the incorrect COM parameter and continues processing the parmlib member.
Operator response: Contact the system programmer.
System programmer response: Check the parameters in the parmlib member. Respecify any incorrect parameters in
the parmlib member before the next IPL.
Source: Master scheduler
Detecting Module: IEAVNP13
Routing Code: –
Descriptor Code: 12

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.
In the message text:
COMMNDxx
The COMMNDxx parmlib member in which the error occurred.
IEACMD00
The command was in the IEACMD00 parmlib member.
cmd
The command.
System action: Depending on the message text, the system does the following:
IEACMD00
The system tries to process the COMMNDxx parmlib members.
COMMNDxx
The system does not process any COMMNDxx parmlib members.
System programmer response: Do the following:
1. Make sure that sufficient SQA storage is available for system initialization.
2. If the problem continues, search problem reporting data bases for a fix for the problem. If no fix exists, contact the
IBM Support Center.
Source: Master scheduler
Detecting Module: IEAVNP13
Routing Code: –
Descriptor Code: 12

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.
In the message text:

Chapter 21. IEA messages 847

IEA866I • IEA867I

prm The parameter indicated.

System action: The system will enter disabled wait 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.
System programmer response: 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.
Source: Contents supervision (CSV)
Detecting Module: IEAVNP05, IEAVNPC5
Routing Code: 1
Descriptor Code: 1

IEA866I VOLUME ser ON dev REQUIRED ON A {devtyp|dev1}

Explanation: During processing of a VATLSTxx 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
The device number of the device on which the 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.
Operator response: If the volume is unloaded, mount the correct volume on the device type or device indicated.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 12

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
The device number of the device on which the volume was mounted.
System action: The system unloaded the volume on device dev.
Operator response: Mount a different volume on the 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.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2

848 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA874I • IEA883I

Descriptor Code: 12

IEA874I INVALID OPT IN IEAOPTxx

Explanation: Processing for system resources manager (SRM) initialization found an incorrect parameter value in
the IEAOPTxx parmlib member.
In the message text:
IEAOPTxx
The parmlib member, where xx is the suffix of 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 reporting data bases for a fix for the problem. If no fix exists,
contact the IBM Support Center. Provide a listing of the IEAOPTxx member.
Source: System resources manager (SRM)
Detecting Module: IEAVNP10
Routing Code: 2
Descriptor Code: 4

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. It is possible that the module is not in an APF-authorized
library, which will also prevent the system from loading the module into storage.
In the message text:
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.
IEAVTSSD
The system writes no summary dumps.
IEAVTSDR
The system does not process memory ends for SVC dump recovery.
IEAVTSSV
The system writes no suspend summary dumps.
IEAVTSXT
The system does not give control to the installation exits for SVC dumps.
ISGDSDMP
The system does not give control to the installation exits for SVC dump.
IEAVTSEP
The system does not give control to the installation exits after SVC dumps.
IARQDUMP
The system may dump excessive amounts of virtual storage.

Chapter 21. IEA messages 849

IEA884I • IEA885I

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.
Operator response: Notify the system programmer of this message. If requested by the system programmer, reIPL
the system.
System programmer response: Place the missing modules in the appropriate system library. In the case of LNKLST
or APF changes, dynamic LNKLST or APF changes might be accomplished using SET PROG commands. Otherwise,
reIPL the system to fully enable SVC dumping.
Source: SVC Dump (SDUMP)
Detecting Module: IEAVTSDI, IEAVTDSV
Routing Code: 10
Descriptor Code: 4

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.
In the message text:
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.
System action: One of the following:
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.
Operator response: Notify the system programmer.
System programmer response: Correct the parmlib member before the next system initialization.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTABI
Routing Code: 10
Descriptor Code: 4

IEA885I 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.
In the message text:
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.
Operator response: Notify the system programmer.

850 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA886A • IEA888A

System programmer response: Correct the parmlib member before the next system initialization.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTABI
Routing Code: 10
Descriptor Code: 4

IEA886A TOD CLOCK(S) MUST BE SET

Explanation: The operator did not set the time-of-day (TOD) clock(s).
System action: The system prompts the operator for 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).
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.
Source: Timer supervision
Detecting Module: IEAVRTOD
Routing Code: 1
Descriptor Code: 2

IEA888A [UTC DATE=yyyy.ddd,CLOCK=hh.mm.ss] LOCAL DATE=yyyy.ddd,CLOCK=hh.mm.ss

REPLY U, OR UTC/LOCAL TIME

Explanation: This message displays the following:
v The local time and date
v The Coordinated Universal Time (UTC) and date

In the message text:

yyyy.ddd
The year (4 digit year: 1900 - 2042) and the day (001-366).
hh.mm.ss
The hour (00-23), minute (00-59), and second (00-59).
System action: The system prompts the operator for a reply.

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 z/OS 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:

Chapter 21. IEA messages 851

IEA889A • IEA890I

R id,'[DATE=yyyy.ddd][,CLOCK=hh.mm.ss],UTC|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 'UTC|GMT', 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:
1. Resetting UTC or GMT time causes the TOD clock to be reset. It also affects the local time. Respecifying UTC or
GMT time causes the local time value to be recalculated using the new UTC or GMT and the system time zone
constant.
2. Resetting local time does not affect UTC or 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 UTC or GMT and local time values are incorrect, always reset the UTC or 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 UTC or 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 UTC or GMT before setting the local time and
date.
Source: Timer supervision
Detecting Module: IEAVRTOD
Routing Code: 1
Descriptor Code: 12,2

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.
System action: One of the following:
v If the operator acknowledges receipt of the message and presses the switch within 30 seconds, the system
continues processing.
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.
Operator response: Do the following:
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.
Source: Timer supervision
Detecting Module: IEAVRTOD
Routing Code: 1
Descriptor Code: 2

IEA890I comnd FAILED- MEMORY COULD NOT BE CREATED

Explanation: comnd is one of the following:
LOGON
MOUNT
START

852 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA891I • IEA892I

The system tried to create or initialize an address space for a command, but failed. The failure might be caused by
system overload or lack of paging space.

In the message text:

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.
Source: Supervisor control
Routing Code: 2
Descriptor Code: 4

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.
System action: The system continues processing.
Source: Supervisor control
Detecting Module: IEAVNP09
Routing Code: 2,10
Descriptor Code: 4

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:
v The sum of the MAXUSER, RSVNONR, and RSVSTRT values is too large.
v The SQA is too small.

In the message text:

val1 The value of MAXUSER in IEASYSxx
val2 The value of RSVNONR in IEASYSxx
val3 The value of RSVSTRT in IEASYSxx
System action: The system prompts the operator to respecify the three parameters by issuing message IEA906A
three times: once each for MAXUSER, RSVNONR, and RSVSTRT.
Operator response: Respond to message IEA906A as the system programmer directs.
System programmer response: Do the following:
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.

Chapter 21. IEA messages 853

IEA893A • IEA895A

v Correct the parameters in the IEASYSxx member so that this message will not be issued during every system
initialization using IEASYSxx.
Source: Supervisor control
Detecting Module: IEAVNP09
Routing Code: 2,10
Descriptor Code: 12

IEA893A 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
The device number of a device that is not ready.
System action: The system waits for the operator to ready the devices, then to respond.
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.
If any devices have not been readied, message IEA893A is 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’.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 4

IEA894I REQUESTED VOLUME ON UNREQUESTED UNIT. dev NOW UNLOADED.

Explanation: During processing of a VATLSTxx 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.
System action: The system unloads the volume.
Operator response: Mount the volume on a requested device if the attributes are to be processed.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 12

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’.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 4

854 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA896I • IEA907W

IEA896I 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.
System action: The system does not process recording requests. Requesters receive a return code indicating that
recording is no longer active.
Operator response: Notify the system programmer of this message. If requested by the system programmer, reIPL
the system.
System programmer response: If recording is needed, ask the operator to reIPL 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.
Source: Recovery termination manager (RTM)
Routing Code: 2
Descriptor Code: 4

IEA903A {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 and continues
processing.
Operator response: When the message reads 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.
Source: Timer supervision
Detecting Module: IEE6603D
Routing Code: 1
Descriptor Code: 2

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. Notify the system programmer.
System programmer response: Increase the amount of central storage available to the system, or decrease the
amount of virtual storage requested for the SQA, CSA or LPA.

Chapter 21. IEA messages 855

IEA908I • IEA911E

Source: Virtual storage manager (VSM)

Routing Code: Note 9
Descriptor Code: -

IEA908I 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
In the message text:
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.
Source: Virtual storage manager (VSM)
Detecting Module: IEAVNP08
Routing Code: Note 9
Descriptor Code: -

IEA909I {CSA|SQA} PARM SPECIFIED IS a,b. ONLY xxxxxxxx OF VIRTUAL STORAGE AVAILABLE FOR
{CSA|SQA|ECSA|ESQA}
Explanation: The storage area requested for the system queue area (SQA) or common service area (CSA) is too
large.
In the message text:
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
The amount of virtual storage available.
System action: The system issues message IEA906A.
Operator response: See the operator response for message IEA906A.
Source: Virtual storage manager (VSM)
Detecting Module: IEAVNP08
Routing Code: Note 9

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

856 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA911E

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.
In the message text:
COMPLETE
The SVC dump contains all of the virtual storage that was requested.
PARTIAL
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 to allow the debugging of the problem to
be successful. The codes in the SDRSN field can be used to determine what storage was affected, or
what problems were encountered while SVC dump processing was executing.
dumpid
The 3–character 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 dump was requested by sysname, which is another system in the sysplex.
INCIDENT TOKEN: incident-token
The formatted incident token for the dump.
SDRSN = vvvvvvvv wwwwwwww xxxxxxxx zzzzzzzz
The system wrote a 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 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.
04000000
An error in summary dump processing caused recovery to receive control.

Chapter 21. IEA messages 857

IEA911E

02000000
An error in summary dump processing or suspend summary dump processing caused recovery to
receive control.
00400000
An error caused the loss of 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 waiting for writing a trace table, an error occurred. The trace table could not be
written.
00008000
The dump of the data above the bar could not be written because the storage buffer was unavailable.
00004000
Option USERTOKEN is not accessible.
00002000
Some private storage above the bar was not collected because the extension range table is full.
00001000
Extended range table has filled while collecting ranges of private storage above the bar.
00000800
Extended range table has filled while collecting ranges of common storage above the bar.
wwwwwwww
Partial dump reason code. One of the 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.
00020000
During dump processing of a possibly hung address space, dump processing obtained only fixed
storage for the address space.
80000000|40000000
While processing SVC X'33', 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.
01000000
The started dump task failed.
00800000
A task abnormally ended, and SVC dump processing took a partial dump. The resource manager for
SVC dump processing receives control.
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.

858 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA911E

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.
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
During dump processing of a possibly hung address space, dump processing obtained only fixed
storage for the address space.
00010000
During dump processing of a possibly hung address space, the address space was found to be invalid.
The dump data may not be consistent.
xxxxxxxx
Partial dump reason code. One of the 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.

Chapter 21. IEA messages 859

IEA911E

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 reached.
00008000
While processing the SQA SDATA option, the system filled the range table.
00004000
While processing the CSA SDATA option, the system filled the range table. Remaining entries could not
be added.
00002000
While processing global subpools, the system filled the range table. Remaining entries could not be
added.
00001000
While processing the LSQA SDATA option, the system filled the range table. Remaining entries could
not be added.
00000800
While processing the RGN SDATA option, the system filled the range table. Remaining entries could not
be added.
00000400
While processing private subpools, the system filled the range table. Remaining entries could not be
added.
00000200
While processing the SWA SDATA option, the system filled the range table. Remaining entries could not
be added.
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 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.
00000002
Exit dataspace is full.
00000001
SVC dump processing truncated the dump because a critical shortage of auxiliary storage existed.
zzzzzzzz
Partial dump reason code. One of the 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

860 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA911E

v There is a shortage of auxiliary storage

v The DUMPSRV address space dispatching priority is too low.
80000000
Dump processing had to reset the system dispatchable. The data in some storage areas might have
changed before the dump capture was complete.
40000000
Dump processing reset the tasks dispatchable in one or more address spaces involved in the SVC dump.
The data in some storage areas might have changed before the dump capture was complete.
20000000
Dump processing reset the caller's 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 cannot 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. This can be because another dump request for a
structure in the STRLIST is in progress. Check that dump for relevant data.
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
might be because the operator deleted the structure dump with the SETXCF FORCE command. This
may also be because another dump request for a structure in the STRLIST is in progress. Check that
dump for relevant data.
00008000
Recovery received control while building the SDUMP signals for other systems in the sysplex
reason-text
One of the following:

Chapter 21. IEA messages 861

IEA911E

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
SVC dump processing truncated the dump because a critical shortage of auxiliary storage existed.
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 {SUMDUMP | GLOBAL | LOCAL | STRLIST}
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.
ERROR OCCURRED IN AN SDUMP EXIT
Dump processing encountered an unexpected error in the SDUMP exit.
ERROR OCCURRED IN AN SDUMP LOCAL EXIT
Dump processing encountered an unexpected error in the specific type of SDUMP exit.
ERROR OCCURRED IN AN SDUMP GLOBAL EXIT
Dump processing encountered an unexpected error in the specific type of SDUMP exit.
ERROR OCCURRED IN AN SDUMP EARLY GLOBAL EXIT
Dump processing encountered an unexpected error in the specific type of SDUMP exit.
ERROR OCCURRED IN AN SDUMP ONE-TIME-ONLY EXIT
Dump processing encountered an unexpected error in the specific type of SDUMP exit.
ERROR OCCURRED IN AN SDUMP DYNAMIC LOCAL EXIT
Dump processing encountered an unexpected error in the specific type of SDUMP exit.
ERROR OCCURRED IN AN SDUMP DYNAMIC GLOBAL EXIT
Dump processing encountered an unexpected error in the specific type of SDUMP exit.
EXIT DATASPACE IS FULL
Dump processing encountered a full dataspace.
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 might be missing, IEA911E COMPLETE DUMP
is 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.

862 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA911E

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 caller's 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:
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.
System action: The system continues processing.
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:
A CRITICAL AUXILIARY STORAGE SHORTAGE EXISTS
Ensure that enough DASD resource is available for accommodating captured SVC dumps. See the system
programmer response for message IRA201E to determine how to relieve the shortage. Then redrive the SVC
dump.
You can use the AUXMGMT and MAXSPACE parameters of the CHNGDUMP SET command to manage the use
of virtual and auxiliary storage by SVC dump processing. See z/OS MVS System Commands for more details
about the CHNGDUMP command.
DUMP DATA SET FULL - DUMP ENDED WHILE WRITING {SUMDUMP|GLOBAL|LOCAL|STRLIST}
Format the partial dump.
I/O ERROR - NO EOF WRITTEN - DUMP ENDED WHILE WRITING {SUMDUMP|GLOBAL|LOCAL|STRLIST}
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.
ERROR OCCURRED IN SDUMP
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.

Chapter 21. IEA messages 863

IEA912I • IEA913I

SOME STORAGE COULD NOT BE DUMPED RC=16

Refer to the description of the SDRSN bits that are set. Use the IPCS subcommand STRDATA to format the list of
structures that was requested to be dumped. IPCS displays the reason the structures did not completely process.
For more information, see z/OS MVS IPCS Commands.
Source: SVC dump
Detecting Module: IEAVTSDC
Routing Code: 2
Descriptor Code: 11

IEA912I RECOVERY/TERMINATION DUMP FAILED [DUE TO cde]

Explanation: During recovery from an error, the system requested an ABEND dump. The dump failed for one of the
following reasons:
v An unopened data control block (DCB) was referenced during validity checking.
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.
v The DCB type was not correct.

In the message text:

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.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTABD
Routing Code: 11
Descriptor Code: -

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.
In the message text:
xxxxK The number of kilobytes by which the size of the private area below 16 megabytes is reduced.
System action: The system continues processing.
Source: Virtual storage manager (VSM)
Detecting Module: IEAVNP08
Routing Code: Note 9
Descriptor Code: -

864 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA915E • IEA918I

IEA915E SYNTAX ERROR IN IEASYSxx CONTENTS, PROMPT FOLLOWS

Explanation: Paging data set names are incorrect in the PAGE parameter of the IEASYSxx parmlib member.
In the message text:
IEASYSxx
The parmlib member, with a suffix of xx.
System action: The system issues a message to ask the operator to respecify the PAGE parameter.
Operator response: Respond to the message. Notify the system programmer.
System programmer response: Before the next IPL, correct the contents of IEASYSxx according to the syntax for
specifying paging space data set names.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM2
Routing Code: Note 9
Descriptor Code: 12

IEA916E SYNTAX ERROR IN {PAGE=|PAGTOTL=| NONVIO=} SYSTEM PARAMETER, PROMPT

FOLLOWS
Explanation: A system parameter contains a syntax error.
System action: The system issues message IEA906A to prompt the operator to respecify the parameter, or to press
the ENTER button on the console.
Operator response: Reply to message IEA906A. Notify the system programmer.
System programmer response: Ensure that the system parameter has the correct syntax.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 12

IEA918I PAGE DATA SET dsname NOT 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.

In the message text:

dsname The name of the data set.
System action: The system continues initialization. If the data set is already in use, the system issues message
IEA922D.
Operator response: Do one of the following:
v If message IEA922D follows this message, the data set is already in use. Respecify a data set name.
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.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 12

Chapter 21. IEA messages 865

IEA920I • IEA921I

IEA920I PAGE DATA SET dsname NOT 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.

In the message text:

dsname The name of the data set.
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.
In all other cases, the system issues message IEA922D.
Operator response: Reply to message IEA922D, if issued. Notify the system programmer.
System programmer response: Before the next system initialization, verify that the page data set is cataloged in the
master catalog.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM2
Routing Code: Note 9
Descriptor Code: 1

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.
In the message text:
dsname The name of the data set.
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.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM2
Routing Code: Note 9
Descriptor Code: 1

866 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA921I • IEA923D

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.
In the message text:
dsname The name of the data set.
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 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.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM2
Routing Code: Note 9
Descriptor Code: 1

IEA922D REPLY ‘DSN=’ OR ‘IGNORE’

Explanation: This message allows the operator to respecify a page data set name.
System action: The system waits for the operator to 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.
Operator response: Do one of the following:
v Enter REPLY id,DSN= to specify the new data set name.
v Enter REPLY id,IGNORE to continue with the data set.

Notify the system programmer.

System programmer response: See the previously issued message.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM2
Routing Code: Note 9
Descriptor Code: 2

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.
In the message text:
ser The volume serial number.
System action: The system waits for the operator to reply.

Chapter 21. IEA messages 867

IEA924D • IEA925D

If the volume is to be provided (GO), initialization continues. The system issues a mount message. The data set is
used.
If the volume is to be ignored (IGNORE), initialization continues without the data set.
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: 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.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM1
Routing Code: Note 9
Descriptor Code: 2

IEA924D VOLUME ser NEEDED FOR PAGE DATA 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.
In the message text:
ser The volume serial number.
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.
System action: The system waits for the operator to 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.
Operator response: Either enter REPLY id,GO and prepare to mount the requested volume, or enter 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.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 2

IEA925D VOLUME ser NEEDED FOR PAGE DATA 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 are required for recovery of one or more VIO data sets.
In the message text:
ser The volume serial number.
System action: The system waits for the operator to reply.

868 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA926I • IEA927I

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 is in effect, causing all VIO data sets from previous IPLs to be unrecoverable.
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 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 is used. Consider asking the operator to enter the PAGEADD command.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM1
Routing Code: Note 9
Descriptor Code: 2

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 data bases for a fix for the problem. If no fix exists, contact the IBM
Support Center.
Source: System resources manager (SRM)
Detecting Module: IEAVNP1F
Routing Code: Note 9
Descriptor Code: -

IEA927I 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.
Operator response: Notify the system programmer.
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.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 4

Chapter 21. IEA messages 869

IEA928I • IEA930I

IEA928I MODULE AT LOCATION xxxxxx IN PLPA CONTAINS HOLES

Explanation: One of the following occurred:
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.

In the message text:

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'.
Operator response: Notify the system programmer.
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.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRQSRIT
Routing Code: Note 9
Descriptor Code: 4

IEA929I 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.
Operator response: Notify the system programmer.
System programmer response: Look for the messages that preceded this message.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 4

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.
Operator response: Notify the system programmer.
System programmer response: Look for the messages that preceded this message.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 4

870 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA931I • IEA934I

IEA931I ESTAE REQUEST FOR GTF TRACE FORMATTING FUNCTION UNSUCCESSFUL

Explanation: The recovery environment requested by the generalized trace facility (GTF) was not established.
System action: The system does not format any GTF buffers.
System programmer response: Obtain the SYSOUT output for the job.
Collect all printed output and output data sets related to the problem. Search problem reporting data bases for a fix
for the problem. If no fix exists, contact the IBM Support Center.
Source: Generalized trace facility (GTF)
Detecting Module: IGC0F05A
Routing Code: Note 11
Descriptor Code: -

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.
System programmer response: Obtain the SYSOUT output for the job.
Collect all printed output and output data sets related to the problem. Search problem reporting data bases for a fix
for the problem. If no fix exists, contact the IBM Support Center.
Source: Generalized trace facility (GTF)
Detecting Module: IGC0F05A
Routing Code: Note 11
Descriptor Code: -

IEA933I UNABLE TO LOAD FORMAT APPENDAGE xxx. FURTHER RCDS REQUIRING THIS MOD is
DUMPED IN HEX
Explanation: Generalized trace facility (GTF) formatting module was unable to load a format appendage.
In the message text:
xxx 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 output and output data sets related to the problem. Search
problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center.
Source: Generalized trace facility (GTF)
Detecting Module: IGC0F05A
Routing Code: Note 11
Descriptor Code: -

IEA934I INVALID RETURN CODE RECEIVED FROM mod. FURTHER RCDS REQUIRING THIS MOD is
DUMPED IN HEX
Explanation: The system detected an incorrect return code on return from a module.
In the message text:
mod The name of the module.
System action: The system continues formatting GTF buffers, dumping in hexadecimal any record that requires this
module for editing.

Chapter 21. IEA messages 871

IEA935W • IEA937I

System programmer response: Collect all printed output and output data sets related to the problem. Search
problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center.
Source: Generalized trace facility (GTF)
Detecting Module: IGC0F05A
Routing Code: Note 11
Descriptor Code: -

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 action: System initialization stops. The system enters a wait state.
Operator response: See the operator response for the wait state.
System programmer response: See the system programmer response for the wait state.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 1

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 is accessible to a
future initialization. The problem was caused by one of the following:
v Slot availability problem: There were no available slots on the PLPA data set
v Storage availability problem: There was no storage available in order to perform the I/O operation
v I/O error: An I/O error occurred while the system was writing to the PLPA data set
System action: The system waits for the operator to reply.
Operator response: Notify the system programmer. Enter REPLY id,GO to continue with the cold start, or reIPL at
the system programmer's request.
System programmer response: Do one of the following, depending on the problem experienced:
v Slot availability problem: Verify that the PLPA data set is large enough to hold the quick start records.
v Storage availability problem: Look for other messages and abends indicating a storage shortage.
v I/O error: Examine the system log for any messages that may indicate a problem performing I/O to the PLPA data
set. Verify that the volume containing the PLPA data set is defined and configured correctly.

When using this PLPA page data set again, ask the operator to perform an IPL with the CLPA option.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRQSRIT
Routing Code: Note 9
Descriptor Code: 2

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,

872 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA938W • IEA939D

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.
Operator response: Notify the system programmer.
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.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 4

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 action: System initialization stops. The system enters a wait state.
Operator response: Notify the system programmer.
System programmer response: Ensure that enough SQA is requested. If not, increase the SQA maximum size.
Otherwise, the system configuration can be too small.
Possibly, an error occurred in the system. Search problem reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM2
Routing Code: Note 9
Descriptor Code: 1

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), and must not be *NONE*.
v If the same data set was being used, then the system could not read the necessary information.
System action: The system waits for the operator to 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.
System programmer response: Verify that the correct IEASYSxx parmlib member is being used. Also, verify the
previous use of the PLPA paging data set.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 2

Chapter 21. IEA messages 873

IEA940I • IEA942I

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.
In the message text:
dsname The name of the data set.
System action: Initialization continues.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM1
Routing Code: Note 9
Descriptor Code: 4

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.
In the message text:
ser The volume serial number.
System action: The system waits for the operator to 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.
Operator response: Either enter REPLY id,GO and prepare to mount the requested volume, or enter REPLY
id,IGNORE.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 2

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.
In the message text:
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.

874 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA943W • IEA945W

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.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 12

IEA943W 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'.
Operator response: Notify the system programmer. ReIPL with the CLPA option.
System programmer response: See the operator response for wait state X'061'.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRIM
Routing Code: Note 9
Descriptor Code: 1

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.
Operator response: Notify the system programmer. 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 programmer’s 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.
Source: Auxiliary storage manager (ASM)
Detecting Module: ILRASRM1
Routing Code: Note 9
Descriptor Code: 12

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'.
Operator response: See the operator response for wait state X'061'.

Chapter 21. IEA messages 875

IEA946W • IEA948I

Source: Auxiliary storage manager (ASM)

Detecting Module: ILRASRM1
Routing Code: Note 9
Descriptor Code: 1

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
Operator response: Restart the system. If the system displays this message frequently, contact the system
programmer.
System programmer response: See installation procedures to increase the space allowed for the SQA. If the system
displays this message frequently, see installation procedures to increase the central storage requirements.
Source: Virtual storage manager (VSM)
Detecting Module: IGVVSCEL
Routing Code: 1
Descriptor Code: 1

IEA947A REPLY U TO CONTINUE, OR RE IPL.

Explanation: During processing of a VATLSTxx 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.
System action: The system waits for the operator to 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.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 4

IEA948I dev NOW UNLOADED.

Explanation: During processing of a VATLSTxx parmlib member, the system unloaded a volume. In the message
text:
dev
The device number of the device from which the volume was unloaded.
System action: The system unloads the volume.
Operator response: See the operator response for preceding message, either message IEA854I or IEA866I.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 12

876 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA949I • IEA958I

IEA949I I/O ERROR READING VATLSTxx.

Explanation: During processing of a 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: If message IEA949A appears, see the operator response for that message.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 12

IEA949A REPLY YES FOR LIST OF ENTRIES THAT is PROCESSED, OR U FOR NO LIST.
Explanation: This message prompts the operator for a reply to message IEA949I.
System action: The system waits for the operator to reply.
Operator response: REPLY ‘YES’ for a list of entries (encountered before the error occurred) that is processed, or ‘U’
if you do not want a list.
Source: Allocation/unallocation
Detecting Module: IEAVAP00
Routing Code: 2
Descriptor Code: 4

IEA950I MODULE mod NOT FOUND; MC ROUTING INACTIVE

Explanation: A module was not found in the link pack area (LPA). The system is unable to initialize the generalized
trace facility (GTF).
In the message text:
mod The name of the module.
System action: Processing continues.
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.
Source: Generalized trace facility (GTF)
Detecting Module: IEAVNP17
Routing Code: Note 9
Descriptor Code: -

IEA958I EXCP APPENDAGE NAME TABLE NOT BUILT

Explanation: During system initialization, the nucleus initialization program (NIP) accessed the IEAAPP00 parmlib
member to build a table of valid modules that can 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'.

Chapter 21. IEA messages 877

IEA959I • IEA964I

Operator response: Notify to the system programmer.

System programmer response: Rebuild IEAAPP00 prior to the next IPL for.
Source: DFSMSdfp
Detecting Module: IEAVNP16

IEA959I ERROR CAUSED ACTIVE LPA TO BE TRUNCATED, MODULE CONTROL MAY BE LOST
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.
System action: The system continues processing. The system writes a logrec data set error record.
Operator response: Report this message to the system programmer. If frequent abnormal endings occur, reIPL might
be necessary. Obtain a stand-alone dump if the system programmer requests one.
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 error record and the stand-alone dump, if available.
Source: Contents supervision (CSV)
Routing Code: Note 4
Descriptor Code: 2

IEA964I HARDCOPY SUSPENDED, REASON=xxxx, NO HARDCOPY DEVICE AVAILABLE

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.
In the message text:
xxxx The reason code, as follows:
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. You can
specify an actual hardcopy printer device or use SYSLOG if you want the system log to be the hardcopy log.

878 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA966I • IEA989I

Source: Communications task (COMMTASK)

Detecting Module: IEAVSWCB
Routing Code: 2,10
Descriptor Code: 4

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.
System action: The system continues processing with 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.
System programmer response: Verify that the REAL, SQA, and CSA parameters are properly defined in the
IEASYSxx parmlib member.
If the parameters are correct, search problem reporting data bases for a fix for the problem. If no fix exists, contact
the IBM Support Center.
Source: System resources manager (SRM)
Detecting Module: IEAVNP1F
Routing Code: Note 9
Descriptor Code: -

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'.
Operator response: See the operator response for wait state X'01C'.
System programmer response: See the system programmer response for wait state X'01C'.
Source: Supervisor control
Detecting Module: IEAVESPR
Routing Code: 2,10
Descriptor Code: 2

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.
In the message text:
ID=xxxx
The SLIP trap identifier specified on the SLIP command.
text
One of the following:
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.

Chapter 21. IEA messages 879

IEA990I • IEA991I

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 and continues processing.
Source: SLIP
Detecting Module: IEAVTSL2
Routing Code: -
Descriptor Code: -

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 action: Depending on the message text, the system does the following:
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.
System programmer response: Ensure that the 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.
Source: System resources manager (SRM)
Detecting Module: IEAVNP1F
Routing Code: Note 9
Descriptor Code: -

IEA991I SRM CHANNEL DATA NO LONGER AVAILABLE FOR I/O SERVICE

Explanation: One of the following problems occurred:
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: Notify the system programmer.
System programmer response: Determine the reason for the lack of storage. Search problem reporting databases for
a fix for the problem. If no fix exists, contact the IBM Support Center.
Source: System resources manager (SRM)
Detecting Module: IEAVNP1F
Routing Code: Note 9
Descriptor Code: -

880 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA992I • IEA994I

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.
In the message text:
ID=xxxx
The SLIP trap identifier specified on the SLIP command.
text
One of the following:
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.
System action: The system continues processing.
For ACTION=TRACE, this message is only issued the first time the SLIP trap matches.
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.
Operator response: Notify the system programmer.
System programmer response: If a wait state occurs, look at the data in message IEE844W.
Source: SLIP
Detecting Module: IEAVTSL2
Routing Code: 1
Descriptor Code: 4

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.
In the message text:
dsname The data set name.
System action: The system continues processing.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTABD
Routing Code: 11
Descriptor Code: 6

IEA994I STATIC SYSTEM SYMBOL INFO

SYMBOLS DEFINED: n
CURRENT TABLE SIZE: cts BYTES
MAX TABLE SIZE: mts BYTES
Explanation: In response to
DISPLAY SYMBOLS,SUMMARY, this message provides information about the current use of static system symbols.
In the message text:

Chapter 21. IEA messages 881

IEA995I

n The number of static system symbols currently defined, either implicitly (such as &SYSNAME) or explicitly.
cts Current size of the symbol table in (decimal) bytes. This covers the name, value, and associated control
information for every symbol.
mts Maximum size of the symbol table in (decimal) bytes.
System action: The system continues processing.
Operator response: None.
System programmer response: None.
Problem determination: None.
Source: System initialization (IPL/NIP)
Detecting Module: IEAVESYM
Routing Code: None.
Descriptor Code: 5

IEA995I SYMPTOM DUMP OUTPUT

text
Explanation: Where text is:
{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 |
PSW AT TIME OF ERROR xxxxxxxx xxxxxxxx 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.

In the message text:

SYSTEM COMPLETION CODE=cde
The system completion code from the ABEND macro.
USER COMPLETION CODE=cde
The user completion code from the ABEND macro.
REASON CODE=reason-code
The reason code, if specified in the ABEND macro.

882 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA995I

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 ILC x INTC xx
- OR -
PSW AT TIME OF ERROR xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
ILC x INTC xx
The 16-byte program status word (PSW) at the time of the restart interruption. The format of the PSW may
appear on one or two lines. If the error address is located below 2G, the information appears on one line; if the
error address is located above 2G, the PSW information appears on two lines.
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 one of the following:
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: gggggggg 1: gggggggg
2: gggggggg 3: gggggggg
4: gggggggg 5: gggggggg
6: gggggggg 7: gggggggg
8: gggggggg 9: gggggggg
A: gggggggg B: gggggggg
C: gggggggg D: gggggggg
E: gggggggg F: gggggggg

Chapter 21. IEA messages 883

IEA996I

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: aaaaaaaa/gggggggg 1: aaaaaaaa/gggggggg
2: aaaaaaaa/gggggggg 3: aaaaaaaa/gggggggg
4: aaaaaaaa/gggggggg 5: aaaaaaaa/gggggggg
6: aaaaaaaa/gggggggg 7: aaaaaaaa/gggggggg
8: aaaaaaaa/gggggggg 9: aaaaaaaa/gggggggg
A: aaaaaaaa/gggggggg B: aaaaaaaa/gggggggg
C: aaaaaaaa/gggggggg D: aaaaaaaa/gggggggg
E: aaaaaaaa/gggggggg F: 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
6: gggggggg_gggggggg 7: gggggggg_gggggggg
8: gggggggg_gggggggg 9: gggggggg_gggggggg
A: gggggggg_gggggggg B: gggggggg_gggggggg
C: gggggggg_gggggggg D: gggggggg_gggggggg
E: 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: aaaaaaaa/gggggggg_gggggggg 1: aaaaaaaa/gggggggg_gggggggg
2: aaaaaaaa/gggggggg_gggggggg 3: aaaaaaaa/gggggggg_gggggggg
4: aaaaaaaa/gggggggg_gggggggg 5: aaaaaaaa/gggggggg_gggggggg
6: aaaaaaaa/gggggggg_gggggggg 7: aaaaaaaa/gggggggg_gggggggg
8: aaaaaaaa/gggggggg_gggggggg 9: aaaaaaaa/gggggggg_gggggggg
A: aaaaaaaa/gggggggg_gggggggg B: aaaaaaaa/gggggggg_gggggggg
C: aaaaaaaa/gggggggg_gggggggg D: aaaaaaaa/gggggggg_gggggggg
E: aaaaaaaa/gggggggg_gggggggg F: aaaaaaaa/gggggggg_gggggggg
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTSYM
Routing Code: 11
Descriptor Code: 6

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 continues
processing.
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.
System programmer response: Do the following:
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.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVTABD, IEAVAD01
Routing Code: 11
Descriptor Code: -

884 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEA997I • IEA998I

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.
System programmer response: Do the following:
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.
Source: Recovery termination manager (RTM)
Detecting Module: IEAVAD01
Routing Code: 11
Descriptor Code: -

IEA998I PARTIAL SYSMDUMP TAKEN TO dsname REASON CODE=rsn

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.
In the message text:
dsname The data set specified on the SYSMDUMP DD statement.
rsn Specific codes to identify what caused the dump to be considered partial.

An error occurred as indicated by the reason code. The explanation of the hex reason code is as follows:

Reason Code Explanation

00 A potential lockout was detected (timeout). Tasks in the address space were prematurely reset
dispatchable before all data could be put into the dump. The resulting SYSMDUMP is likely
still usable for analysis.
04 Data spaces were requested, but were not available.
08 The coredump byte limit was exceeded for a z/OS UNIX System Services task.
0C SDUMP returned a return code of 4. The most likely reason is that the dump data set was
filled before the system finished writing all dump data. But it could also be due to other
reasons such as unexpected abends in SDUMP, or an I/O error occurred while the system was
writing the dump to the dump data set. Other messages were probably also issued.

System action: The system continues processing.

Application Programmer Response:
1. For problems other than those relating to I/O, use the SYSMDUMP data set. While not all of the virtual storage
requested was collected, enough may have been dumped to diagnose the problem that caused the dump.
2. I/O errors or, running out of space, result in other messages being issued. For the space problem, increase the
size of the DASD data set specified on the SYSMDUMP DD statement.
System programmer response: Involvement is only needed for I/Oerror cases and unexpected abends. The device
may need servicing or defragging. LOGREC should have records for the unexpected abends.
Source: SVC Dump (SCDMP)
Detecting Module: IEAVTSYS

Chapter 21. IEA messages 885

IEA999W

Routing Code: 11
Descriptor Code: 6

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'.
Operator response: See the operator response for wait state X'014'. ReIPL the system.
System programmer response: See the system programmer response for wait state X'014'.
Source: Supervisor control
Detecting Module: IEAVEPC
Routing Code: 2
Descriptor Code: 1

886 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Chapter 22. IEAH messages
IEAH700I Build Level yyyy.ddd hh:mm:ss:tt
Explanation: Provides the date and time that the SDUMP check was compiled.
System action: Processing continues.
Operator response: none
System programmer response: none
Problem determination: n/a
Source: SDUMP (SCDMP)
Reference Documentation: n/a
Automation: n/a
Detecting Module: IEAVTSHG
Routing Code: n/a
Descriptor Code: n/a

IEAH701I The recommended automatic allocation of SVC DUMP data sets is not being used
Explanation: The installation is not taking advantage of allowing SDUMP to automatically allocate its dump data
sets.
System action: SDUMP will either use an available pre-allocated SYS1.DUMPxx dump data set or leave the dump
captured in virtual storage. This use of virtual storage can negatively impact the paging subsystem.
Operator response: Report this information to the system programmer.
System programmer response: IBM Suggestion: See the "Using Automatically Allocated Dump Data Sets" section of
z/OS MVS Diagnosis: Tools and Service Aids for setup information. One advantage is the efficiency of using a system
determined blocksize to write the dump to DASD. Another benefit is the dump will always fit into the space
allocated for the data set.
Problem determination: n/a
Source: SDUMP (SCDMP)
Reference Documentation: ieav100t
Automation: n/a
Detecting Module: IEAVTSHG
Routing Code: n/a
Descriptor Code: n/a

IEAH702I SDUMP is using automatic allocation, as per the IBM recommendation.

Explanation: Automatic allocation of SVC dump data sets is enabled.
System action: n/a
Operator response: n/a
System programmer response: n/a
Problem determination: n/a
Source: SDUMP (SCDMP)

© Copyright IBM Corp. 1988, 2012 887

IEAH703E • IEAH704I

Reference Documentation: n/a

Automation: n/a
Detecting Module: IEAVTSHG
Routing Code: n/a
Descriptor Code: n/a

IEAH703E The SVC dump facility has been disabled by the CHNGDUMP

command.
Explanation: The SVC dump collection function has been disabled by the CHNGDUMP SET,SDUMP,NODUMP
command. The system will not be able to generate SVC dumps that gather problem information.
System action: SVC dumps are not generated.
Operator response: Report this situation to the system programmer.
System programmer response: Action: Restore the dump options using the CHNGDUMP SET options found in
your installation's COMMNDxx member (or defaulted in IEACMD00) to re-establish the ability of the system to
collect SVC dumps. SVC dumps may have been disabled due to resource constraints. However, once those
constraints were dealt with, it is advantageous to re-enable this serviceability function.
IBM Suggestion: Always keep the ability of the system to take SVC Dumps enabled. A couple dire circumstances
where the taking of SVC dumps may need to be disabled are: when an application appears to be generating an
endless stream of SVC dumps; or when paging resources are running low due to a number of SVC dumps being
captured.
Problem determination: n/a
Source: SDUMP (SCDMP)
Reference Documentation: z/OS MVS System Commands
Automation: n/a
Detecting Module: IEAVTSHG
Routing Code: n/a
Descriptor Code: n/a

IEAH704I The SVC dump facility is available to collect dumps.

Explanation: When a system program experiences a condition requiring a snapshot of virtual storage, it can request
an SVC dump.
System action: n/a
Operator response: n/a
System programmer response: n/a
Problem determination: n/a
Source: SDUMP (SCDMP)
Reference Documentation: n/a
Automation: n/a
Detecting Module: IEAVTSHG
Routing Code: n/a
Descriptor Code: n/a

888 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Chapter 23. IEATH messages
IEATH001I Time Procotol is not applicable to this level of the server.
Explanation: CHECK(IBMTIMER, ZOSMIGREC_SUP_TIMER_INUSE) ran successfully and found no exceptions.
The migration action to migrate from a Sysplex Timer to Server Time Protocol is not applicable to this system
because the system is running on a z800 or z900 server. Server Time Procotol is not offered on this level of the server.
The servers and coupling facilities that are capable of supporting STP are the z10, z9, z990, and z890.
After migrating to a higher server level, this migration action might become appropriate.
System action: Processing continues.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Timer Supervisor (TIMER)
Automation: N/A
Detecting Module: IEATCMSG
Routing Code: N/A
Descriptor Code: N/A

IEATH002I A Sysplex Timer is not in use on this system.

Explanation: CHECK(IBMTIMER, ZOSMIGREC_SUP_TIMER_INUSE) ran successfully and found no exceptions.
The migration action to migrate from a Sysplex Timer to Server Time Protocol is not applicable to this system.
System action: Processing continues.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Timer Supervisor (TIMER)
Automation: N/A
Detecting Module: IEATCMSG
Routing Code: N/A
Descriptor Code: N/A

IEATH003I The timer synchronization mode in use on this system is Server Time Protocol.
Explanation: CHECK(IBMTIMER, ZOSMIGREC_SUP_TIMER_INUSE) ran successfully and found no exceptions.
The migration action to migrate from a Sysplex Timer to Server Time Protocol is not applicable to this system.
System action: Processing continues.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Timer Supervisor (TIMER)
Automation: N/A

© Copyright IBM Corp. 1988, 2012 889

IEATH004I • IEATH006E

Detecting Module: IEATCMSG

Routing Code: N/A
Descriptor Code: N/A

IEATH004I The timer synchronization mode in use on this system is SIMETRID.

Explanation: CHECK(IBMTIMER, ZOSMIGREC_SUP_TIMER_INUSE) ran successfully and found no exceptions.
SIMETRID does not require the use of a Sysplex Timer. The migration action to migrate from a Sysplex Timer to
Server Time Protocol is not applicable to this system.
System action: Processing continues.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Timer Supervisor (TIMER)
Automation: N/A
Detecting Module: IEATCMSG
Routing Code: N/A
Descriptor Code: N/A

IEATH005E The timer synchronization mode in use on this system is ETR.

A migration action is recommended.
Explanation: CHECK(IBMTIMER, ZOSMIGREC_SUP_TIMER_INUSE) found that the timing synchronization mode
in use on this system was ETR (which uses the Sysplex Timer). Server Time Protocol is recommended because the
Sysplex Timer (9037-002) has been withdrawn from marketing and STP is planned to be its replacement. The
migration action to migrate from a Sysplex Timer to Server Time Protocol is applicable to this system.
The servers and coupling facilities that are capable of supporting STP are the z10, z9, z990, and z890. The STP feature
number is 1021. STP is a server-wide facility that is implemented in the Licensed Internal Code (LIC) of z10, z9,
z990s, z890s, and coupling facilities, and presents a single view of time to PR/SM.
System action: Processing continues.
Operator response: Notify the system programmer.
System programmer response: See the z/OS Migration book for information about migrating from a Sysplex Timer
to Server Time Protocol. The Server Time Protocol website is http://www.ibm.com/systems/z/pso/stp.html.
Problem determination: N/A
Source: Timer Supervisor (TIMER)
Reference Documentation: For more information about this migration action, see the z/OS Migration book.
Automation: N/A
Detecting Module: IEATCMSG
Routing Code: N/A
Descriptor Code: 12 is the default set by this check

IEATH006E The timer synchronization mode could not be determined.

Explanation: CHECK(IBMTIMER, ZOSMIGREC_SUP_TIMER_INUSE) could not determine the timer
synchronization mode in use on this system. This check cannot verify if STP is in use, and therefore the check is not
successful.
System action: Processing terminates
Operator response: N/A

890 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEATH009E • IEATH010I

System programmer response: Report this problem to IBM.

Problem determination: N/A
Source: N/A
Reference Documentation: N/A
Automation: N/A
Detecting Module: N/A
Routing Code: N/A
Descriptor Code: 12 is the default set by this check .

IEATH009E The hardware server type for this system could not be determined for STP feature applicability.
Explanation: CHECK(IBMTIMER, ZOSMIGREC_SUP_TIMER_INUSE) could not determine the hardware server
level of this system. This check tries to determine the hardware server level to determine if STP is eligible to run on
that hardware server level.
System action: Processing terminates
Operator response: N/A
System programmer response: Report this problem to IBM.
Problem determination: N/A
Source: N/A
Reference Documentation: N/A
Automation: N/A
Detecting Module: N/A
Routing Code: N/A
Descriptor Code: 12 is the default set by this check .

IEATH010I This system is running on hardware server type processor_name. This server is not eligible to run the
STP feature.
Explanation: CHECK(IBMTIMER, ZOSMIGREC_SUP_TIMER_INUSE) determined that the hardware server level of
this system was either z800 or z900. z800 and z900 are not eligible to have the STP feature. The check succeeds, since
migration to STP is not applicable to this level hardware server.
System action: Processing continues.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: N/A
Automation: N/A
Detecting Module: N/A
Routing Code: N/A
Descriptor Code: 12 is the default set by this check .

Chapter 23. IEATH messages 891

892 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)
Chapter 24. IEAVEH messages
IEAVEH001I Permanently non-reusable ASIDs by ASID

ASID: asid Jobname: jobname

Explanation: Check IEA_ASIDS found permanently non-reusable ASIDs. This is a list of those ASIDs.
In the message text:
asid
The ASID
jobname
The name of the job that was associated with that ASID
System action: The system continues processing.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Supervisor control
Reference Documentation: N/A
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: N/A
Descriptor Code: N/A

IEAVEH003I There are no permanently non-reusable ASIDs

Explanation: Check IEA_ASIDS found no permanently non-reusable ASIDs.
System action: The system continues processing.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Supervisor control
Reference Documentation: N/A
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: N/A
Descriptor Code: N/A

IEAVEH004I Potentially reusable ASIDs

ASID: asid Jobname: jobname

Connection from ASID: asidC Jobname: jobnameC
Connection from ASID: asidC Jobname: jobnameC
ASID: asid Jobname: jobname
Connection from ASID: asidC Jobname: jobnameC

© Copyright IBM Corp. 1988, 2012 893

IEAVEH008I

Connection from ASID: asidC Jobname: jobnameC

-or-

There are no connections to this ASID

Explanation: Check IEA_ASIDS found ASIDs that are currently not reusable but potentially could become reusable.
This is a list of those ASIDs.
In the message text:
asid
The ASID
jobname
The name of the job that was associated with that ASID
asidC
The ASID connected to this ASID. Only upon termination of this ASID can the potentially reusable ASID become
reusable.
jobnameC
The name of the job associated with the connected-from ASID
System action: The system continues processing.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Supervisor control
Reference Documentation: N/A
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: N/A
Descriptor Code: N/A

IEAVEH008I There are no potentially reusable ASIDs

Explanation: Check IEA_ASIDS found no potentially reusable ASIDs.
System action: The system continues processing.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Supervisor control
Reference Documentation: N/A
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: N/A
Descriptor Code: N/A

894 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEAVEH010I • IEAVEH012I

IEAVEH010I

Summary of ASID availability

ASIDs Limit Avail InUse Total

Normal limit avail inuse total

Replacement limit avail inuse total
Explanation: Check IEA_ASIDS provides a summary of ASID availability.
In the message text:
Normal
The line refers to "Normal" ASIDs
Replacement
The line refers to "Replacement" ASIDs
limit
The limit which will trigger an exception when reached
avail
The number available
inuse
The number that are in use
total
The total of available plus inuse
System action: The system continues processing.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Supervisor control
Reference Documentation: N/A
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: N/A
Descriptor Code: N/A

IEAVEH012I Permanently non-reusable ASIDs by jobname

jobname (num)
Explanation: Check IEA_ASIDS lists jobs that have terminated resulting in permanently non-reusable ASIDs.
In the message text:
jobname
The name of the job
num
The number of jobs of this name that have so terminated
System action: The system continues processing.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A

Chapter 24. IEAVEH messages 895

IEAVEH014I • IEAVEH020E

Source: Supervisor control

Reference Documentation: N/A
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: N/A
Descriptor Code: N/A

IEAVEH014I Connectors to potentially reusable ASIDs

jobname (num)
Explanation: Check IEA_ASIDS lists connectors to potentially reusable ASIDs.
In the message text:
jobname
The name of the job
num
The number of potentially reusable ASIDs to which this job is connected
System action: The system continues processing.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Supervisor control
Reference Documentation: N/A
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: N/A
Descriptor Code: N/A

IEAVEH020E There are n remaining available ASIDs.

This is below the limit

Explanation: Check IEA_ASIDs found an exception condition.
The current number of available ASIDs is less than the checkowner_or_installation specified limit of specified.
System action: The system continues processing. However, if more ASIDs are needed, a re-IPL may be necessary.
Operator response: Report this problem to the system programmer.
System programmer response: Run the check with the VERBOSE option. Look at the report output to see what
address spaces are permanently non-reusable and which are potentially reusable. For those in the latter category, it
may be possible to recycle one of the jobs that is identified as being connected to this address space and thereby
allow the address space to be re-used.
Check the maximum number of ASIDs and replacement ASIDs specified in your IPL parameters by keywords
MAXUSER and RSVNONR.
Problem determination: N/A
Source: Supervisor Control
Reference Documentation: z/OS MVS Initialization and Tuning Reference
Automation: N/A

896 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEAVEH021E • IEAVEH031I

Detecting Module: IEAVEHCK,IEAVEHMS

Routing Code: See note 35.
Descriptor Code: 12 is the default set by this check. See note 1.

IEAVEH021E There are n remaining available replacement ASIDs.

This is below the limit

Explanation: Check IEA_ASIDs found an exception condition.
The current number of available replacement ASIDs is less than the checkowner_or_installation specified limit of
specified.
System action: The system continues processing. However, if more ASIDs are needed, a re-IPL may be necessary.
Operator response: Report this problem to the system programmer.
System programmer response: Run the check with the VERBOSE option. Look at the report output to see what
address spaces are permanently non-reusable and which are potentially reusable. For those in the latter category, it
may be possible to recycle one of the jobs that is identified as being connected to this address space and thereby
allow the address space to be re-used.
Check the maximum number of ASIDs and replacement ASIDs specified in your IPL parameters by keywords
MAXUSER and RSVNONR.
Problem determination: N/A
Source: Supervisor Control
Reference Documentation: z/OS MVS Initialization and Tuning Reference
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: See note 35.
Descriptor Code: 12 is the default set by this check. See note 1.

IEAVEH031I

Non-system LX/ELXs LX: lx ASID: asid Jobname: jobname dormant

System LX/ELXs LX: lx ASID: asid Jobname: jobname dormant
Explanation: Check IEA_LXs reports on in-use LXs.
In the message text:
Non-system LX/ELXs
The line describes non-system LXs and ELXs
System LX/ELXs
The line describes system LXs and ELXs
LX The LX number
The number of system LXs displayed will be greater than the number reported in the System LX ’inuse’ field as
displayed in message IEAVEH040I. This is because the VERBOSE=YES report includes System LXs defined at
early IPL time for System PC Services. See z/OS MVS Diagnosis: Reference, GA22-7588, Chapter 5 for a description
of these PC Services.
asid
The ASID that owns the LX
jobname
The name of the job that owns the LX
dormant
The string "(Dormant)" if the LX is currently dormant. Otherwise blank.

Chapter 24. IEAVEH messages 897

IEAVEH033I • IEAVEH040I

System action: The system continues processing.

Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: N/A
Reference Documentation: N/A
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: N/A
Descriptor Code: N/A

IEAVEH033I There are no non-system LXs in use

Explanation: Check IEA_LXs determined that there were no non-system LXs in use.
System action: The system continues processing.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Supervisor control
Reference Documentation: N/A
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: N/A
Descriptor Code: N/A

IEAVEH040I

Summary of LX usage
Limit Avail InUse Total

LXs limit avail inuse total

ELXs limit avail inuse total
System LXs limit avail inuse total
System ELXs limit avail inuse total
Explanation: Check IEA_LXs provides a summary of the LX usage within the system, according to the LX type.
In the message text:
LXs
The line refers to non-system LXs
ELXs
The line refers to non-system ELXs
System LXs
The line refers to system LXs
System ELXs
The line refers to system ELXs
limit
The lower limit of the number of available LXs, such that when avail is less than limit, an exception occurs.

898 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEAVEH050E • IEAVEH060E

avail
The number available
inuse
The number that are in use
total
The total of available plus inuse
System action: The system continues processing.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Supervisor control
Reference Documentation: N/A
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: N/A
Descriptor Code: N/A

IEAVEH050E There are n remaining available LxTypes.

This is below the limit

Explanation: The current number of available LxTypes is not greater than the checkowner_or_installation specified limit
of specified.
System action: The system continues processing. However, if more LXs of the identified type are needed, a re-IPL
may be necessary.
Operator response: Report this problem to the system programmer.
System programmer response: Run the check with the VERBOSE option. Look at the report output to see what LXs
are in use. It may be possible to cancel one of the jobs that is identified and thereby allow the non-system LXs used
by that job to be re-used.
Check the maximum number of system LXs specified in your IPL parameters by the NSYSLX parameter.
Problem determination: N/A
Source: Supervisor Control
Reference Documentation: z/OS MVS Initialization and Tuning Reference
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: See note 35.
Descriptor Code: 12 is the default set by this check. See note 1.

IEAVEH060E At the current rate of depletion, the system will run out of

ASIDs in
n
days.
This is below the limit
Explanation: The number of days before which the system is anticipated to run out of ASIDs is not greater than the
checkowner_or_installation-specified limit of specified.
System action: The system continues processing. The value is based on current data. The average depletion rate

Chapter 24. IEAVEH messages 899

 IEAVEH061I • IEAVEH070I

might change and should be watched. If the current rate is maintained, a re-IPL will be necessary.
Operator response: Report this problem to the system programmer.
System programmer response: Continue to monitor the depletion rate and schedule a re-IPL as necessary.
Problem determination: N/A
Source: Supervisor Control
Reference Documentation: z/OS MVS Initialization and Tuning Reference
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: See note 35.
Descriptor Code: 12 is the default set by this check. See note 1.

IEAVEH061I The system has been IPLed for between lowbound and highbound days. On the average depletion
ASIDs have become non-reusable per day. At the current rate of depletion, the system will run out
of ASIDs in n days.
Explanation: Check IEA_ASIDs has found that over the life of the IPL, ASIDs have become non-reusable at the
indicated rate. If the trend continues, eventually insufficient ASIDs will remain available and a re-IPL will have to be
scheduled.
The average depletion rate is based on current data. The rate might change and should be watched. If depletion
continues at the current rate, a re-IPL will be necessary.
In the message text:
lowbound
The number of days rounded down
highbound
The number of days rounded up
depletion
The number of ASIDs that have become non-reusable per day, rounded up
System action: The system continues processing.
Operator response: N/A
System programmer response: Continue to monitor the depletion rate and schedule a re-IPL as necessary.
Problem determination: N/A
Source: Supervisor Control
Reference Documentation: z/OS MVS Initialization and Tuning Reference
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: N/A
Descriptor Code: N/A

| IEAVEH070I HiperDispatch is state and in the expected state

| Explanation: Check SUP_HIPERDISPATCH determined the check's expected HiperDispatch state matches the actual
| HiperDispatch state of the system. This system supports enabling HiperDispatch to increase system performance.
| With HiperDispatch enabled, the system cache is utilized more efficiently and the system performance is improved in
| many configurations. The performance gain HiperDispatch provides typically increases with a newer hardware
| generation and can improve with newer releases of z/OS.
| With HiperDispatch disabled, the system cache is utilized less efficiently and does not receive the performance
| benefits provided by HiperDispatch.

900 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEAVEH071E

| On any z/OS release running on IBM System z10 hardware, HiperDispatch disabled is the default. On IBM System
| z10, customers are encouraged to try running with HiperDispatch enabled.
| Beginning with z/OS V1R13 on zEnterprise 196 hardware, HiperDispatch enabled is the default. With zEnterprise 196
| hardware, z/OS partitions with share greater than two physical processors will typically experience improved
| processor efficiency with HiperDispatch enabled.
| IBM recommends that all partitions that see improved or equivalent processor efficiency with HiperDispatch enabled
| run with HiperDispatch enabled.
| In the message text:
| state
| HiperDispatch's current state (enabled or disabled)
| System action: The system continues to run in its current HiperDispatch state.
| Operator response: N/A
| System programmer response: Prior to enabling HiperDispatch for the first time, review the "Planning
| Considerations for HiperDispatch Mode" White Paper located on IBM Techdocs at http://www-03.ibm.com/
| support/techdocs/atsmastr.nsf/WebIndex/WP101229.
| If HiperDispatch is enabled, none.
| If HiperDispatch is disabled, consider migrating the partition to HiperDispatch enabled in the future.
| Problem determination: N/A
| Source: Supervisor Control
| Reference Documentation: "IEAOPTxx (OPT) Parameters" in z/OS MVS Initialization and Tuning Reference .
| "SET Command" in z/OS MVS System Commands.
| "Planning Considerations for HiperDispatch Mode" White Paper located on IBM Techdocs at http://www-
| 03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101229
| Automation: N/A
| Detecting Module: IEAVEHCK,IEAVEHMS
| Routing Code: N/A
| Descriptor Code: N/A

| IEAVEH071E HiperDispatch is expected to be expected but it is actual

| Explanation: Check SUP_HIPERDISPATCH determined the check's expected HiperDispatch state does not match the
| actual HiperDispatch state of the system. This system supports enabling HiperDispatch to increase system
| performance.
| With HiperDispatch enabled, the system cache is utilized more efficiently and the system performance is improved in
| many configurations. The performance gain HiperDispatch provides typically increases with a newer hardware
| generation and can improve with newer releases of z/OS.
| With HiperDispatch disabled, the system cache is utilized less efficiently and does not receive the performance
| benefits provided by HiperDispatch.
| On any z/OS release running on IBM System z10 hardware, HiperDispatch disabled is the default. On IBM System
| z10, customers are encouraged to try running with HiperDispatch enabled.
| Beginning with z/OS V1R13 on zEnterprise 196 hardware, HiperDispatch enabled is the default. With zEnterprise 196
| hardware, z/OS partitions with share greater than two physical processors will typically experience improved
| processor efficiency with HiperDispatch enabled.
| IBM recommends that all partitions that see improved or equivalent processor efficiency with HiperDispatch enabled
| run with HiperDispatch enabled.
| In the message text:

Chapter 24. IEAVEH messages 901

 IEAVEH080I

| expected
| HiperDispatch's expected state (enabled or disabled)
| actual
| HiperDispatch's actual state (enabled or disabled)
| System action: The system continues to run in its current HiperDispatch state.
| Operator response: Report this problem to the system programmer.
| System programmer response: Prior to enabling HiperDispatch for the first time, review the "Planning
| Considerations for HiperDispatch Mode" White Paper located on IBM Techdocs at http://www-03.ibm.com/
| support/techdocs/atsmastr.nsf/WebIndex/WP101229.
| To address the exception from IEAVEH071E, do one of the following:
| 1. Make the actual machine's HiperDispatch state equivalent to the check's expected HiperDispatch state by enabling
| or disabling HiperDispatch on the machine. Do this by updating the IEAOPTxx parmlib member to specify
| HIPERDISPATCH=YES or HIPERDISPATCH=NO.
| 2. Update the check's expected HiperDispatch state to be consistent with the actual HiperDispatch state of the
| machine by supplying a check parameter of HIPERDISPATCH(YES) or HIPERDISPATCH(NO).
| 2A. When the machine is not a IBM System z10 and HIPERDISPATCH(NO) is specified, make sure that the
| MachTypes list includes the machine type where the partition runs.
| Then rerun this Health Check.
| Problem determination: N/A
| Source: Supervisor Control
| Reference Documentation: "IEAOPTxx (OPT) Parameters" in z/OS MVS Initialization and Tuning Reference .
| "SET Command" in z/OS MVS System Commands.
| "Planning Considerations for HiperDispatch Mode" White Paper located on IBM Techdocs at http://www-
| 03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101229
| Automation: N/A
| Detecting Module: IEAVEHCK,IEAVEHMS
| Routing Code: See note 35.
| Descriptor Code: 12 is the default set by this check. See note 1.

IEAVEH080I CPU CONFIGURATION SUPPORTED WITH HIPERDISPATCH curstate

Explanation: The CPU configuration is supported with the current HiperDispatch state.
In the message text:
curstate
The current state of HiperDispatch (enabled or disabled)
System action: The system continues processing.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: z/OS
Automation: N/A
Detecting Module: IEAVEHCK
Routing Code: N/A
Descriptor Code: N/A

902 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEAVEH081E • IEAVEH091E

IEAVEH081E CPU CONFIGURATION VALID WITH HIPERDISPATCH DISABLED. numcpus MORE CPU(S) CAN
BE ADDED WITH HIPERDISPATCH DISABLED.
Explanation: While HiperDispatch mode is disabled, less than CpusLeftB4NeedHd(n) CPUs can be installed and
used. You can currently install and use numcpus more CPUs. CPU ID 3Fx is the last CPU ID that can be installed and
used.
System action: The system continues processing.
Operator response: Notify the system programmer.
System programmer response: Enable HiperDispatch or adjust CpusLeftB4NeedHd to make this check succeed.
Problem determination: N/A
Source: z/OS
Automation: N/A
Detecting Module: IEAVEHCK
Routing Code: See note 35.
Descriptor Code: 12 is the default set by this check. See note 1.

IEAVEH090I The residency mode (RMODE) of the LCCA control block (macro IHALCCA) is actual which
matches what is expected.
Explanation: CHECK(IBMSUP,SUP_LCCA_ABOVE_16M) determined that the LCCA control blocks have the correct
residency mode (RMODE).
In the message text:
actual
The residency mode. "31" indicates RMODE 31, above 16M. "24" indicates RMODE 24, below 16M.
System action: The system continues processing.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Supervisor Control
Reference Documentation: CBLOC parameter of the DIAGxx parmlib member" in z/OS MVS Initialization and
Tuning Reference.
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: N/A
Descriptor Code: N/A

IEAVEH091E The residency mode (RMODE) of the LCCA control block (macro
IHALCCA) is expected to be expected but is actual
Explanation: CHECK(IBMSUP,SUP_LCCA_ABOVE_16M) determined that the LCCA control blocks do not have the
correct residency mode (RMODE).
In the message text:
expected
The expected residency mode. "31" indicates RMODE 31, above 16M. "24" indicates RMODE 24, below 16M.
actual
The actual residency mode. "31" indicates RMODE 31, above 16M. "24" indicates RMODE 24, below 16M.
System action: The system continues processing.

Chapter 24. IEAVEH messages 903

IEAVEH100I • IEAVEH101E

Operator response: Report this problem to the system programmer.

System programmer response: Use the CBLOC option of the DIAGxx parmlib member to specify the desired
RMODE to take effect on the next IPL. Alternately, update the expected RMODE to be consistent with the current
RMODE by supplying a check parameter of CBLOC(24) or CBLOC(31). Then rerun this Health Check.
Problem determination: N/A
Source: Supervisor Control
Reference Documentation: CBLOC parameter of the DIAGxx parmlib member" in z/OS MVS Initialization and
Tuning Reference.
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: See note 35.
Descriptor Code: 12 is the default set by this check. See note 1.

IEAVEH100I The residency mode (RMODE) of the PCCA control block (macro IHAPCCA) is actual which
matches what is expected.
Explanation: CHECK(IBMRCF,RCF_PCCA_ABOVE_16M) determined that the PCCA control blocks have the correct
residency mode (RMODE).
In the message text:
actual
The residency mode. "31" indicates RMODE 31, above 16M. "24" indicates RMODE 24, below 16M.
System action: The system continues processing.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Reconfiguration
Reference Documentation: CBLOC parameter of the DIAGxx parmlib member" in z/OS MVS Initialization and
Tuning Reference.
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: N/A
Descriptor Code: N/A

IEAVEH101E The residency mode (RMODE) of the PCCA control block (macro
IHAPCCA) is expected to be expected but is actual
Explanation: CHECK(IBMRCF,RCF_PCCA_ABOVE_16M) determined that the PCCA control blocks do not have the
correct residency mode (RMODE).
In the message text:
expected
The expected residency mode. "31" indicates RMODE 31, above 16M. "24" indicates RMODE 24, below 16M.
actual
The actual residency mode. "31" indicates RMODE 31, above 16M. "24" indicates RMODE 24, below 16M.
System action: The system continues processing.
Operator response: Report this problem to the system programmer.
System programmer response: Use the CBLOC option of the DIAGxx parmlib member to specify the desired
RMODE to take effect on the next IPL. Alternately, update the expected RMODE to be consistent with the current

904 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

RMODE by supplying a check parameter of CBLOC(24) or CBLOC(31). Then rerun this Health Check.
Problem determination: N/A
Source: Reconfiguration
Reference Documentation: CBLOC parameter of the DIAGxx parmlib member" in z/OS MVS Initialization and
Tuning Reference.
Automation: N/A
Detecting Module: IEAVEHCK,IEAVEHMS
Routing Code: See note 35.
Descriptor Code: 12 is the default set by this check. See note 1.

Chapter 24. IEAVEH messages 905

906 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)
Chapter 25. IEAVTRH messages
IEAVTRH01I CHECK(IBMRTM,RTM_IEAVTRML) was successful. IEAVTRML contains no module names.
Explanation: RTM_IEAVTRML ran successfully and found no exceptions. The best practice method for defining End
of Task and End of Memory resource managers to the system is by the RESMGR service. This check found no
resource managers defined by the old method of inserting their names into CSECT IEAVTRML in load module
IGC0001C.
System action: The system continues processing.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Recovery Termination Manager (RTM)
Reference Documentation: For additional information about defining and End of Task and/or End of Memory
resource manager to the system, see

Using Resource Managers in z/OS MVS Programming: Authorized Assembler Services Guide.
Automation: N/A
Detecting Module: IEAVTRHC
Routing Code: N/A
Descriptor Code: N/A

IEAVTRH02I CHECK(IBMRTM,RTM_IEAVTRML) was successful. IEAVTRML contains no new module names.

Explanation: RTM_IEAVTRML ran successfully and found no exceptions. The best practice method for defining End
of Task and End of Memory resource managers to the system is by the RESMGR service. This check found at least
one resource manager defined by the old method of inserting their names into CSECT IEAVTRML in load module
IGC0001C but the names have been marked as acceptable by the 'NEW(value)' parameter.
System action: The system continues processing.
Operator response: N/A
System programmer response: N/A
Problem determination: N/A
Source: Recovery Termination Manager (RTM)
Reference Documentation: For additional information about defining an End of Task and End of Memory resource
manager to the system, see

Using Resource Managers in z/OS MVS Programming: Authorized Assembler Services Guide.
Automation: N/A
Detecting Module: IEAVTRHC
Routing Code: N/A
Descriptor Code: N/A

© Copyright IBM Corp. 1988, 2012 907

IEAVTRH03I • IEAVTRH04E

IEAVTRH03I The following module names in IEAVTRML caused an exception:

Explanation: CHECK(IBMRTM,RTM_IEAVTRML) has found resource manager names in CSECT IEAVTRML of load
module IGC0001C. This message lists the resource manager names found. When a check parameter of 'NEW(value)'
has been specified and VERBOSE(YES) has not beenspecified, this message lists only the names found since the
current 'NEW(value)' parameter was implemented. The message text is followed by a list of up to 16 of these module
names.
System action: The system continues processing.
Operator response: N/A
System programmer response: See IEAVTRH04E.
Problem determination: N/A
Source: Recovery Termination Manager (RTM)
Reference Documentation: See IEAVTRH04E.
Automation: N/A
Detecting Module: IEAVTRHC
Routing Code: N/A
Descriptor Code: N/A

IEAVTRH04E IEAVTRML contains module names

Explanation: CHECK(IBMRTM,RTM_IEAVTRML) has found at least one resourcemanager name in CSECT
IEAVTRML in load module IGC0001C. The best practice method for defining End of Task and End of Memory
resource managers to the system is by the RESMGR service, and the names found in IEAVTRML have not been
declared to be acceptable by a check parm of 'NEW(value)'.
Message IEAVTRH03I has been placed in the message buffer to list the module names that were found.
System action: The system continues processing.
Operator response: Report this problem to the system programmer.
System programmer response: Resource managers specified to the system by IEAVTRML run for every task
termination and every address space termination in the system and can thus impact system performance. For that
reason the best practice method of defining a resource manager is by the RESMGR service, which allows resource
managers to be defined for specific tasks or address spaces as well as for all tasks or address spaces.
If this check finds resource manager names in IEAVTRML, investigate to determine whether they are still
appropriate. In most cases, they will be found to have been superseded (by the use of RESMGR) and can be removed
from IEAVTRML. Examples of this type of resource manager name include:

DFSMRCL0 -- no longer required as of IMS Version 9

MVPTTRML -- no longer required in any supported release
BNJMTERM -- no longer required in any supported release

If a resource manager module name is still required in IEAVTRML, use check parameter 'NEW(value)' to set the check
to accept any current module names and to only flag future additions to IEAVTRML as exceptions. The 'NEW(value)'
parameter and the resource manager module names that it specifies as acceptable persist across restarts of this check
including across IPLs.
Problem determination: N/A
Source: Recovery Termination Manager (RTM)
Reference Documentation: For additional information about defining an End of Task and End of Memory resource
manager to the system, see

Using Resource Managers in z/OS MVS Programming: Authorized Assembler Services Guide.
Automation: N/A

908 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

 IEAVTRH05I • IEAVTRH06I

Detecting Module: IEAVTRHC

Routing Code: N/A
Descriptor Code: 12 is the default set by this check.

IEAVTRH05I The parameter NEW is missing its value. A unique value is required each time NEW is specified:

PARM('NEW(value)')
Explanation: A value was not provided when the NEW keyword was specified.
Message IEAVTRH07I is also issued to provide information about the valid parameters for this check.
System action: The check is stopped.
Operator response: N/A
System programmer response: Use the MODIFY hzsproc command to specify a unique value for the parameter
NEW.

F hzsproc,UPDATE,CHECK(IBMRTM,RTM_IEAVTRML),PARM('NEW(value)')
Problem determination: Look for additional messages in the message buffer.
Source: Recovery Termination Manager (RTM)
Reference Documentation: For addtional information about syntax for HZSPRMxx commands, see

Syntax and Parameters for HZSPRMxx and MODIFY hzsproc command in IBM Health Checker for z/OS: User's Guide.
Automation: N/A
Detecting Module: IEAVTRHC
Routing Code: N/A
Descriptor Code: N/A

IEAVTRH06I Valid parameters are 'ALL' and 'NEW(value)'.

Explanation: An error was detected in the PARM parameter for CHECK(RTM,RTM_IEAVTRML).
Message IEAVTRH07I is also issued to provide information about the valid parameters for this check.
System action: The check is stopped.
Operator response: N/A
System programmer response: Use the MODIFY hzsproc command to correct the error.

F hzsproc,UPDATE,CHECK(IBMRTM,RTM_IEAVTRML), PARM('NEW(value)')

The NEW parameter causes RTM_IEAVTRML to suppress an exception condition until a new error is found.

F hzsproc,UPDATE,CHECK(IBMRTM,RTM_IEAVTRML),PARM('ALL')

The ALL parameter will report an exception condition if any error is detected by RTM_IEAVTRML.
Problem determination: Look for additional messages in the message buffer.
Source: Recovery Termination Manager (RTM)
Reference Documentation: For additional information about syntax for HZSPRMxx commands, see

Syntax and Parameters for HZSPRMxx and MODIFY hzsproc command in IBM Health Checker for z/OS: User's Guide.
Automation: N/A

Chapter 25. IEAVTRH messages 909

IEAVTRH07I • IEAVTRH11I

Detecting Module: IEAVTRHC

Routing Code: N/A
Descriptor Code: N/A

IEAVTRH07I Update PARM to control the reporting of exceptionsby CHECK(IBMRTM,RTM_IEAVTRML).

PARM('NEW(value)'): Use the NEW parameter to indicate that any module names currently in
IEAVTRML are acceptable and that exceptions should only be issued when new module names are
added to IEAVTRML. The value supplied with the NEW parameter must be different than the last
time that the parameters were changed. IBM suggests that you supply the date and time as the
value, in order to make the parameter self-document when you accepted the current list of module
names in IEAVTRML.The 'NEW(value)' parameter and the resource manager module names that it
specifies as acceptable persist across restarts of this check including across IPLs.

PARM('ALL'): Use the ALL parameter to indicate that an exception should be issued if any module
names are found in IEAVTRML.

Examples of PARM specifications: PARM('NEW(yyyy/mm/dd hh:mm)') PARM('ALL')

Explanation: The PARM for check RTM_IEAVTRML has an error.
System action: The system continues processing.
Operator response: N/A
System programmer response: If you want to suppress exceptions for the module names currently found in
IEAVTRML issue update check parameters using the NEW keyword. Use the following command:

F hzsproc,UPDATE,CHECK(IBMRTM,RTM_IEAVTRML), PARM('NEW(value)')
Problem determination: N/A
Source: Recovery Termination Manager (RTM)
Reference Documentation: For additional information about syntax for HZSPRMxx commands, see

Syntax and Parameters for HZSPRMxx and MODIFY hzsproc command in IBM Health Checker for z/OS: User's Guide.
Automation: N/A
Detecting Module: IEAVTRHC
Routing Code: N/A
Descriptor Code: N/A

IEAVTRH11I IEAVTRML contains the following module names:

Explanation: VERBOSE was requested for CHECK(IBMRTM,RTM_IEAVTRML) when a parameter of 'NEW(value)'
was in effect. This message lists the resource manager module names found in CSECT IEAVTRML of load module
IGC0001C whether they caused an exception or not. The message text is followed by a list of up to 16 of these
module names.
System action: The system continues processing.
Operator response: N/A
System programmer response: See IEAVTRH04E.
Problem determination: N/A
Source: Recovery Termination Manager (RTM)
Reference Documentation: See IEAVTRH04E.
Automation: N/A
Detecting Module: IEAVTRHC

910 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)

Routing Code: N/A
Descriptor Code: N/A

Chapter 25. IEAVTRH messages 911

912 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)
Accessibility
Publications for this product are offered in Adobe Portable Document Format
(PDF) and should be compliant with accessibility standards. If you experience
difficulties when using PDF files, you may view the information through the z/OS
Internet Library web site or the z/OS Information Center. If you continue to
experience problems, send an email to [email protected] or write to:
IBM Corporation
Attention: MHVRCFS Reader Comments
Department H6MA, Building 707
2455 South Road
Poughkeepsie, NY 12601-5400
USA
Accessibility features help a user who has a physical disability, such as restricted
mobility or limited vision, to use software products successfully. The major
accessibility features in z/OS enable users to:
v Use assistive technologies such as screen readers and screen magnifier software
v Operate specific or equivalent features using only the keyboard
v Customize display attributes such as color, contrast, and font size.

Using assistive technologies

Assistive technology products, such as screen readers, function with the user
interfaces found in z/OS. Consult the assistive technology documentation for
specific information when using such products to access z/OS interfaces.

Keyboard navigation of the user interface

Users can access z/OS user interfaces using TSO/E or ISPF. Refer to z/OS TSO/E
Primer, z/OS TSO/E User's Guide, and z/OS ISPF User's Guide Vol I for information
about accessing TSO/E and ISPF interfaces. These guides describe how to use
TSO/E and ISPF, including the use of keyboard shortcuts or function keys (PF
keys). Each guide includes the default settings for the PF keys and explains how to
modify their functions.

z/OS information
z/OS information is accessible using screen readers with the Library Server
versions of z/OS books in the Internet library at:
http://www.ibm.com/systems/z/os/zos/bkserv/

© Copyright IBM Corp. 1988, 2012 913

914 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)
Notices
This information was developed for products and services offered in the U.S.A. or
elsewhere.

IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A

For license inquiries regarding double-byte character set (DBCS) information,

contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 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.

© Copyright IBM Corp. 1988, 2012 915

 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:
Site Counsel
IBM Corporation
2455 South Road
Poughkeepsie, NY 12601-5400
USA

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.

If you are viewing this information softcopy, the photographs and color
illustrations may not appear.

Policy for unsupported hardware

Various z/OS elements, such as DFSMS, HCD, JES2, JES3, and MVS, contain code
that supports specific hardware servers or devices. In some cases, this
device-related element support remains in the product even after the hardware
devices pass their announced End of Service date. z/OS may continue to service
element code; however, it will not provide service related to unsupported
hardware devices. Software problems related to these devices will not be accepted
for service, and current service activity will cease if a problem is determined to be
associated with out-of-support devices. In such cases, fixes will not be issued.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at “Copyright and
trademark information” at www.ibm.com/legal/copytrade.shtml.

Microsoft and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.

916 z/OS V1R13.0 MVS System Messages, Vol 6 (GOS-IEA)




Product Number: 5694-A01

Printed in USA

SA22-7636-24