Professional Documents
Culture Documents
Ief - Igd
Ief - Igd
SA22-7638-12
z/OS
SA22-7638-12
Note
Before using this information and the product it supports, be sure to read the general information under Notices on page
577.
Contents
About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Who should use these MVS System Messages documents . . . . . . . . . . . . . . . . . vi
How to use these documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Using LookAt to look up message explanations . . . . . . . . . . . . . . . . . . . . . . vi
Using IBM Health Checker for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Where to find the most current message information . . . . . . . . . . . . . . . . . . . . vii
Where to find more information . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Information updates on the web . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Subsystem, product, and hardware documents . . . . . . . . . . . . . . . . . . . . viii
Message library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Message directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Message translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . .
Locations . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console . . . . . . . . . . . . . . . . . . . . . . . . . .
OPERLOG . . . . . . . . . . . . . . . . . . . . . . . . .
System Log . . . . . . . . . . . . . . . . . . . . . . . . .
Job Log . . . . . . . . . . . . . . . . . . . . . . . . . .
SYSOUT Data Set . . . . . . . . . . . . . . . . . . . . . .
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message Format . . . . . . . . . . . . . . . . . . . . . . .
How Messages are Explained in this Book. . . . . . . . . . . . . .
Messages Sent to MCS/SMCS Consoles . . . . . . . . . . . . . .
Messages Sent to Hard-Copy Log in JES2 System . . . . . . . . . .
Messages Sent to Hard-Copy Log in JES3 System . . . . . . . . . .
Messages Sent to the Job Log, to Other Data Sets, and to Display Terminals
Truncated Data in Multi-line Messages. . . . . . . . . . . . . . .
Routing Codes . . . . . . . . . . . . . . . . . . . . . . . .
Specification . . . . . . . . . . . . . . . . . . . . . . . .
Routing Code Meaning . . . . . . . . . . . . . . . . . . . .
Routing Codes in this Book . . . . . . . . . . . . . . . . . . .
Descriptor Codes . . . . . . . . . . . . . . . . . . . . . . .
Association with Message Type Code . . . . . . . . . . . . . . .
Valid combinations and restrictions for descriptor codes . . . . . . . .
Message Deletion . . . . . . . . . . . . . . . . . . . . . .
Message Color . . . . . . . . . . . . . . . . . . . . . . .
Descriptor Code Meaning . . . . . . . . . . . . . . . . . . .
Descriptor Codes in this Book . . . . . . . . . . . . . . . . . .
A Method for Finding Changes to MVS and TSO/E Message Texts . . . . .
Using SYS1.MSGENU to Find Message Text Changes . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 1
. 1
. 1
. 1
. 1
. 2
. 2
. 2
. 2
. 5
. 6
. 6
. 8
. 10
. 10
. 11
. 11
. 11
. 13
. 15
. 15
. 15
. 16
. 16
. 16
. 17
. 18
. 18
iii
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
267
267
290
297
380
383
386
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
575
575
575
575
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
iv
z/OS
z/OS
z/OS
z/OS
z/OS
z/OS
z/OS
z/OS
z/OS
MVS
MVS
MVS
MVS
MVS
MVS
MVS
MVS
MVS
System
System
System
System
System
System
System
System
System
Messages,
Messages,
Messages,
Messages,
Messages,
Messages,
Messages,
Messages,
Messages,
Vol
Vol
Vol
Vol
Vol
Vol
Vol
Vol
Vol
2 (ARC-ASA), SA22-7632
3 (ASB-BPX), SA22-7633
4 (CBD-DMO), SA22-7634
5 (EDG-GFS), SA22-7635
6 (GOS-IEA), SA22-7636
7 (IEB-IEE), SA22-7637
8 (IEF-IGD), SA22-7638
9 (IGF-IWM), SA22-7639
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 vi). Here are some of the documents on that bookshelf:
v The MVS System Messages documents
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 x.
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 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 (see Message Color on page 16).
vi
You can obtain code to install LookAt on your host system or Microsoft Windows workstation from:
v A CD-ROM in the z/OS Collection (SK3T-4269).
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.
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.
vii
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.
The following tables list documents that contain information related to the information contained in the
MVS System Messages documents. For the titles and order numbers of documents not in the tables, see
z/OS Information Roadmap.
Use the appropriate Principles of Operation document for the hardware you have installed.
When the MVS System Messages documents reference information in other documents, the shortened
version of the document title is used. The following tables show the complete titles and order numbers of
the documents that you might need while you are using the MVS System Messages documents.
This document is updated weekly and lists documentation changes before they are incorporated into z/OS
publications.
Order Number
SC30-3132
N/A
N/A
N/A
SC34-6246
SA22-7204
SC26-4399
SC26-4293
SC26-4081
GC26-4073
SC23-0592
SC26-4113
SC26-4379
SC33-0143
SA24-4350
PN9000102
SR23-6155
GA32-0253
GA32-0100
GA32-0099
GC26-4647
N/A
viii
Title
Order Number
LASERDRIVE** 1200 Intelligent Digital Optical Disk Drive with SCSI Engineering
Specification
N/A
GC26-4495
SY27-2605
GC26-4495
Z91F-9269
N/A
SC23-2424
S544-3100
SA22-7832
SC35-0169
N/A
N/A
SY27-2605
SC24-5519
SC24-5433
Message library
The message library is designed so that operators and programmers in an installation can build their own
libraries of the message and code information that fits their specific needs. Each person can place into
binders the chapters and documents containing only the messages and codes he or she could 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 your specific systems options, 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.
CD-ROM collection
A comprehensive source of messages for IBM products is contained in the IBM Online Library Productivity
Edition: Messages and Codes Collection, SK2T-2068.
ix
Message directory
To use a message prefix to locate the document containing a specific message, see the following table.
Prefix
Component
ABA
DFSMShsm
ACP
LANRES
ADF
ADM
ADR
DFDSS
ADRY
DFDSS
ADY
Dump analysis and elimination z/OS MVS System Messages, Vol 1 (ABA-AOM), SA22-7631
(DAE)
AEM
AFB
VSFORTRAN
AHL
AMA
AMB
AMD
Stand-alone dump
AMS
Availability manager
ANT
Remote Copy
ANF
AOF
AOM
Administrative operations
manager
AOP
Infoprint server
API
APS
ARC
DFSMShsm
ARRP
ASA
MVS Reuse
ASB
Advanced
Program-to-Program
Communications/MVS
(APPC/MVS)
Prefix
Component
ASD
LANRES
ASM
ASMA
ASR
ATB
Advanced
Program-to-Program
Communications/MVS
(APPC/MVS)
ATR
|
|
ATRH
AVM
Availability manager
BFS
BLG
Information System,
Information Management
BLM
Information System,
Information Management
BLS
BLX
Information System,
Information Management
BLW
Loadwait/Restart
BNH
Network Problem
Determination Application
(NPDA)
BPX
CBDA
Hardware configuration
definition (HCD)
CBR
CEE
Language Environment
CHS
CIM
Managed System
Infrastructure for Setup (msys
for Setup)
CMP
Compression management
services
CLB
xi
Prefix
Component
CNL
CNZ
Console Services
COF
|
|
CRG
Context Services
CRU
CSQ
MQSeries
CSR
CSV
CSY
CSZ
CTX
Context Services
DFH
|
|
|
|
|
|
|
DFQ
Interactive storage
management facility (ISMF)
|
|
|
|
|
|
|
DGT
Interactive storage
management facility (ISMF)
DLX
DMO
Device Manager
DQD
DRK
xii
Prefix
Component
DSI
NetView
DSM
DSM
DSN
Database 2
DZI
DZJ
EDC
EDG
DFSMSrmm
ELM
EQQ
OPC/ESA
ERB
Resource Measurement
Facility (RMF)
ERX
EWX
LANRES
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 UNIX
System
EZY
EZZ
FAN(G)
REXX/370 compiler
IBM Compiler and Library for SAA REXX/370 Users Guide and
Reference , SH19-8160
FDBX
FLM
FOMC
FOMF
FOMI
FOMM
FOMO
FOMOA
FOMOG
FOMOH
xiii
Prefix
Component
FSUM
FSUMA
FSUMB
FSUMF
FOR
LE FORTRAN Library
GDE
Distributed FileManager/MVS
(DFM/MVS)
GFSA
|
|
GFSC
GIM
SMP/E
GQD
GQF
HASP
HZS
IAR
|
|
IARH
IAT
JES3
IAZ
JES Common
ICE
ICH
ICK
ICN
NCP/SSP/EP
ICP
Input/Output Configuration
Program (IOCP)
ICQA
ICQC
ICT
Programmed Cryptographic
Facility
ICU
IDA
Virtual storage access method z/OS MVS System Messages, Vol 6 (GOS-IEA), SA22-7636
(VSAM) control block
expansion
IDC
xiv
Prefix
Component
IEA
v Allocation/unallocation
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)
IEB
IEC
xv
Prefix
Component
IEE
v Communications task
(COMMTASK)
v Allocation/unallocation
v Converter/interpreter
Converter
IEFI
Converter/interpreter
IEH
IEV
Assembler H
xvi
Prefix
Component
IEW
v DFSMS
v Linkage editor
v Binder
v Transport utility
v Loader
IFA
IFB
Input/output environment
recording routines: OBR and
SVC 76
IFC
IFD
IFL
3704 and 3705 Control Program Generation and Utilities Guide and
Reference Manual, GC30-3008
Advanced Communications
Function (ACF) for Network
Control Program (NCP)
IFO
MVS Assembler
IGD
Storage management
subsystem (SMS) of Data
Facility Product (DFP)
IGF
Dynamic device
z/OS MVS System Messages, Vol 9 (IGF-IWM), SA22-7639
reconfiguration (DDR) Machine
check handler (MCH)
IGGN
IGV
IGW
IGY
VS COBOL II
IGZ
VS COBOL II
IKF
VS COBOL II
IKJ
IKM
Programming Language/I
(PL/I) syntax checker
xvii
Prefix
Component
IKT
ILR
ILX
VS FORTRAN Compiler
IHV
System Automation for OS/390 IBM Tivoli System Automation for z/OS Messages and Codes
ING
System Automation for OS/390 IBM Tivoli System Automation for z/OS Messages and Codes,
SC33-8264
INM
IOAC
Open Systems
Adapter-Express
(OSA-Express)
IOP
Input/output configuration
program (IOCP)
IOS
IPD
IRA
IRD
IRR
IRX
ISG
ISN
ISP
ISQ
System Automation for OS/390 IBM Tivoli System Automation for z/OS Messages and Codes
ISRB
ISRL
IST
ISU
xviii
Prefix
Component
ITA
ITT
Component trace
ITV
Data-in-virtual
ITZ
Transaction trace
IST
IVT
IWM
IXC
IXG
IXL
IXP
IXZ
Input/output configuration
program (IOCP)
IZP
Input/output configuration
program (IOCP)
Input/output configuration
program (IOCP)
ES/9000 IOCP Users 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
Message translation
Through the MVS message service (MMS), you can translate MVS system messages into other
languages. Messages that cannot be translated include the following:
v Initialization messages
v DFSMS/MVS messages
v JES3 messages
About this document
xix
xx
Summary of changes
New, changed, or deleted messages can affect your systems automation routines. To ensure that your
installations 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-4269 and in the z/OS Internet library at:
http://www.ibm.com/servers/eserver/zseries/zos/bkserv/
Summary of changes
for SA22-7640-12
z/OS Version 1 Release 8
as updated April 2007
The document contains information previously presented in z/OS MVS System Messages, Vol 8 (IEF-IGD),
SA22-7638-11, which supports z/OS Version 1 Release 8.
You may notice changes in the style and structure of some content in this documentfor example,
headings that use uppercase for the first letter of initial words only, and procedures that have a different
look and format. The changes are ongoing improvements to the consistency and retrievability of
information in our documents.
This document contains terminology, maintenance, and editorial changes. Technical changes or additions
to the text and illustrations are indicated by a vertical line to the left of the change.
Summary of changes
for SA22-7640-11
z/OS Version 1 Release 8
The document contains information previously presented in z/OS MVS System Messages, Vol 8 (IEF-IGD),
SA22-7638-10, which supports z/OS Version 1 Release 7.
This document contains terminology, maintenance, and editorial changes, including changes to improve
consistency and retrievability.
Summary of changes
for SA22-7638-10
z/OS Version 1 Release 7
as updated April 2006
The document contains information previously presented in z/OS MVS System Messages, Vol 8 (IEF-IGD),
SA22-7638-09, which supports z/OS Version 1 Release 7
This document contains terminology, maintenance, and editorial changes, including changes to improve
consistency and retrievability.
Summary of changes
for SA22-7638-09
z/OS Version 1 Release 7
The document contains information previously presented in z/OS MVS System Messages, Vol 8 (IEF-IGD),
SA22-7638-08, which supports z/OS Version 1 Release 6.
References to OpenEdition have been replaced with z/OS UNIX System Services or z/OS UNIX.
xxi
This document contains terminology, maintenance, and editorial changes, including changes to improve
consistency and retrievability.
Summary of changes
for SA22-7638-08
z/OS Version 1 Release 6
as updated December 2004
The document contains information previously presented in z/OS MVS System Messages, Vol 8 (IEF-IGD),
SA22-7638-07, which supports z/OS Version 1 Release 6.
This document contains terminology, maintenance, and editorial changes, including changes to improve
consistency and retrievability.
Summary of changes
for SA22-7638-07
z/OS Version 1 Release 6
The document contains information previously presented in z/OS MVS System Messages, Vol 8 (IEF-IGD),
SA22-7638-06, which supports z/OS Version 1 Release 5.
Messages now contain the appropriate routing and descriptor codes. z/OS MVS Routing and Descriptor
Codes is no longer being published.
This document contains terminology, maintenance, and editorial changes, including changes to improve
consistency and retrievability.
Summary of changes
for SA22-7638-06
z/OS Version 1 Release 5
This document contains information previously presented in z/OS MVS System Messages, Vol 8
(IEF-IGD), SA22-7638-05, which supports z/OS Version 1 Release 4.
This document contains terminology, maintenance, and editorial changes, including changes to improve
consistency and retrievability.
xxii
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 Most messages are issued through WTO and WTOR macros to one of the following locations:
Console
Hard-copy log
Job log
SYSOUT data set
Routing codes determine where the messages are displayed or printed. The routing codes for
messages issued by the operating system are included with each message.
v Other messages are issued through the WTL macro or the LOG operator command to the system log
(SYSLOG).
v Dump messages are issued through the dumping services routines and can appear in:
SVC dumps, stand-alone dumps, or SYSMDUMP ABEND dumps formatted by the interactive
problem control system (IPCS)
Trace data sets formatted by the interactive problem control system (IPCS)
ABEND dumps or SNAP dumps produced by the dumping services
In dump or trace data sets formatted by IPCS, the messages appear interactively on a terminal or in a
printed dump.
v Some messages are issued through DFSMS/MVS access methods directly to one of the following
locations:
Output data set
Display terminal
Locations
Console
Messages sent to a multiple console support (MCS) console, 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.
OPERLOG
|
|
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
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
Copyright IBM Corp. 1988, 2007
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.
Messages
A displayed or printed message can appear by itself or with other information, such as a time stamp. The
following topic shows the format of the message. Then the topics show the information accompanying the
message on the MCS console and on the hard-copy log in a JES2 system and a JES3 system.
Message Format
id
id
id
id
id
CCCnnn text
CCCnnns text
CCCnnnns text
CCCnnnnns text
CCCSnnns text
id Reply identifier: It is optional. It appears if an operator reply is required. The operator specifies it in the
reply.
CCCnnn, CCCnnns, CCCnnnns, CCCnnnnns, CCCSnnns
Message identifier.
CCC
A prefix to identify the component, subsystem, or product that produced the message. The prefix is
three characters.
S
The subcomponent identifier, which is an optional addition to the prefix to identify the
subcomponent that produced the message. The subcomponent identifier is one character.
Eventual action: The operator must perform action when time is available.
For messages with the prefix ADR, the type codes depend on whether the message is issued to
the operator console or to SYSPRINT. For console messages, the type codes indicate the operator
action:
Informational message.
Error message. The particular task might end or might continue without completing all
requests.
For messages with the prefix BFS, the type codes indicate the severity of the detected error and
are:
E
Information
Attention
For messages with the EWX prefix, an 11-character message exists of the form EWXfffnnnns:
EWX
fff
nnnn
Message number
Function
Sending Command
ADM
Administration
EWXADMIN commands
COM
Host communications
All commands
DSK
Disk serving
DST
Distribution
EWXDS commands
PHL
Host-to-LAN print
EWXHLSRV
PLH
LAN-to-host print
EWXLHSRV
RES
EWXCONN
SRV
NetWare service
EWXNWSRV
Note: When the term MMC is used in the messages, it is also referring to the System/370
Parallel Channel Adapter feature of the IBM 3172-3 interconnect controller.
Chapter 1. Introduction
For messages with the prefix CNLC, the type codes indicate the severity of the detected error and
are:
E
Error
Information
Severe
Attention
Messages with the prefix IEW and numbered in the range 2000 through 2999 have the following
format:
<message number> <internal code> <message text>
The internal codes are not documented because they are used for diagnostic purposes.
The following type codes indicate the severity of the detected error:
E
Error: Severity 8
Information: Severity 0
Attention: Severity 4
For messages with the prefix IGW01, the type codes indicate the severity of the detected error
and are:
E
text
Text: The text provides information, describes an error, or requests an operator action.
Messages with the prefix IDA are preceded by a 2-digit severity code:
04
08
12
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.
Chapter 1. Introduction
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.
Descriptor Code
For WTO or WTOR messages, the descriptor code of the message.
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.
Data line of a multiple-line message; this line may be the last line of the message.
A log entry that did not originate with a LOG command or a system message.
The second character on the line indicates whether the line was generated because of a command:
C
Command input.
Command response.
Command issued internally. The job identifier contains the name of the internal issuer.
Chapter 1. Introduction
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
INSTREAM
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, Vol 2 (DCCB-ITZYRETC).
message
Reply identifier, message identifier, and text. The reply identifier and message identifier appear only on
the first line of a multiple-line message.
Messages sent to the MLOG/DLOG hard-copy log in a JES3 system appear as follows:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
C3E0SY1
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
05311
0841114 +I O
0841114 IAT8589 CONSOLE DISPLAY
0841114 NAME
COUNT
SWITCH
LL
AUTH
SAVEMSG
0841114 SPC74
00000001
0120
15
YES
0841114
ROUTE CODE=(BROADCAST)
0841114
DEST CLASS=(ALL)
0841114 WS77S
00000000
0120
10
YES
0841114
ROUTE CODE=(NONE)
0841114
DEST CLASS=(NONE)
0841114 S8100
00000000
0120
15
YES
0841114
ROUTE CODE=(NONE)
0841114
DEST CLASS=(NONE)
0841114 S0400
00000000
0120
15
YES
0841114
ROUTE CODE=(NONE)
0841114
DEST CLASS=(NONE)
0841114 W8100
00000000
0120
15
YES
0841114
ROUTE CODE=(NONE)
0841114
DEST CLASS=(NONE)
0841114 W0400
00000000
0120
15
YES
0841114
ROUTE CODE=(NONE)
0841114
DEST CLASS=(NONE)
0841114 W3774
00000000
0120
15
YES
0841114
ROUTE CODE=(NONE)
0841114
DEST CLASS=(NONE)
0841114 B0001
00000000
0120
15
YES
0841114
ROUTE CODE=(NONE)
0841114
DEST CLASS=(NONE)
0841114 T0001
00000002
0120
15
YES
0841114
ROUTE CODE=(BROADCAST,HARDCOPY,3,7-10,41-128)
0841114
DEST CLASS=(TOTAL)
0841114 T0002
00000000
0120
15
YES
0841114
ROUTE CODE=(NONE)
0841114
DEST CLASS=(NONE)
0841114 T0003
00000000
0120
15
YES
0841114
ROUTE CODE=(NONE)
0841114
DEST CLASS=(NONE)
0841114 T0004
00000002
0120
15
YES
0841114
ROUTE CODE=(BROADCAST,HARDCOPY,3,7-10,41-128)
0841114
DEST CLASS=(TOTAL)
dest
JES3 destination class, which corresponds to the MVS routing code.
|
console
JES3 or MVS console name, as follows:
blank
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
NETWORK
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.
Chapter 1. Introduction
hhmmsst
Time stamp, given as the hour (00-23), minute (00-59), second (00-59), and tenth of a second (0-9).
i
<
Note: The above four symbols can be changed by a CONSTD statement in the JES3 initialization
stream.
a
Normal message.
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.
10
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
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
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 books:
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.
Meaning
Operator Action
Chapter 1. Introduction
11
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.
Tape Library
The message gives tape library information, such as a request by volume serial numbers
for tapes for system or problem program use.
Disk Library
The message gives disk library information, such as a request by volume serial numbers
for volumes for system or problem program use.
Teleprocessing Control
The message gives the status or disposition of teleprocessing equipment, such as a
message that describes line errors.
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.
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
21-28
12
29
Disaster recovery.
30-40
41
42
43-64
65-96
97-128
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.
N/A
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
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.
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
Note 11
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
Chapter 1. Introduction
13
Note 14
The message is routed back to the console that initiated the request and to all associated
consoles.
Note 16
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
Note 23
This message is issued by the device controller. The routing code will vary according to
the device controllers task.
Note 24
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 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
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
Note 33
Note 34
This message is only displayed on the SMCS Console Selection screen, and is not issued
via WTO support.
| Note 35
14
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:
Users Guide for more information.
|
|
|
|
Note 36
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.
Type Code
W (wait)
A (action) or D (decision)
E (eventual action)
4 through 10
I (information)
11
12 and 13
I (information)
Descriptor codes are specified in the DESC parameter of the WTO or WTOR macro. The following
restrictions apply when specifying descriptor codes:
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
Chapter 1. Introduction
15
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.
Meaning
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.
|
2
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
System Status
The message indicates the status of a system task or of a hardware unit.
Job Status
The message indicates the status of a job or job step.
16
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.
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.
Operators Request
The message is written in response to an operators request for information by a
DEVSERV, DISPLAY, or MONITOR command.
|
|
10
Not defined
Descriptor code 10 is not currently in use.
11
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.
End of Programming Interface information
14-16
|
|
|
|
|
|
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.
N/A
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: Users 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:
Chapter 1. Introduction
17
|
|
|
For messages whose text has changed, the output might show both an I and a D, indicating that a record
in the message file has been replaced:
I - IEE162I 46
D - IEE162I 46
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.
18
procstep
stepname
ddname
+xxx
|
|
IEF002W
|
|
|
|
|
|
|
|
|
Descriptor Code: 6
|
|
IEF004I
|
|
Routing Code: 1
Descriptor Code: 1
IEF003I
Source: Allocation
Detecting Module: The detecting module is
IEFAB422.
The containing module is IEFBB4M6.
Routing Code: Hardcopy only
procstep
stepname
ddname
+xxx
19
IEF005I IEF006I
System action: The system ends the job.
Application Programmer Response: Check that the
step name on the refer back is unique. Check the
spelling of the names on the refer back and the unit
affinity request on the referenced statement. After
correcting the error, submit the job again.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
that case, preserve the Job and Console logs for the
failed Job and contact the IBM Support Center for
further assistance.
Source: Allocation
Detecting Module: The detecting module is
IEFAB421.
The containing module is IEFBB4M5.
Routing Code: Hardcopy only
Descriptor Code: 6
IEF006I
Source: Allocation
IEF005I
jobname
xxxxxxxx
yyyyyyyy
aaaaaaaa
bbbbbbbb
jobname
procstep
stepname
ddname
+xxx
Routing Code: 2
devtype
20
Descriptor Code: 6
IEF007I
IEF007I
reason-code
034
A DD statement is missing
for the restarted step.
038
An uncorrectable input/output
error occurred when the
system read the checkpoint
data set.
230
231
232
233
235
In a partitioned checkpoint
data set, the system could
not find the specified entry.
The system encountered a
checkpoint entry record of an
undetermined type, or did not
find an END record when
expected.
237
238
239
260
261
262
263
266
267
280
281
282
283
300
301
320
321
340
21
IEF008I
that represents a dynamically
allocated step input output
table (SIOT).
341
232
233, 237
Verify the accuracy of CHECKID for the
checkpoint entry in the RESTART parameter of
the JOB statement. Submit the job again.
235
238
239
260
400
263
420
440
For reason code 261, 262, 266, 267, 280, 281, 282,
283, 300, 320, 321, 340, 341, 380, 400 or 420
resubmit the job. 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.
441
An incorrect type of
scheduler work block (SWB)
data set descriptor record
(DSDR) was issued.
Descriptor Code: 6
380
442
443
IEF008I
031
034
038
devnum
230
231
22
IEF009I IEF011I
v The VARY online command, select another device.
Source: Allocation
code
Descriptor Code: /
IEF009I
Descriptor Code: 6
IEF011I
23
IEF013I IEF016I
stepname
The name of the job step.
procstep
ddname
stepname
ddname
+xxx
dev
| IEF013I
|
|
|
|
|
Source: Allocation
| jobname
Name of the job which could not be cancelled.
|
|
|
|
|
IEF016I
jobname
The name of the job that made the request.
24
procstep
The name of the step in the procedure.
stepname
The name of the step.
ddname
The name of the DD.
+xxx
IEF017I IEF019I
System action: The Allocation request is failed.
Source: Allocation
Source: Allocation
volser
|
|
|
|
|
| jobname
|
The name of the job.
| IEF019I
|
|
|
devnum
text
| procstep
|
The name of the step in the procedure.
| stepname
|
The name of the job step.
| ddname
|
The name of the DD statement.
| +xxx
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
25
IEF020I IEF083I
| Descriptor Code: 6
IEF020I
Source: Allocation
jobname
procstep
The name of the step in the procedure.
stepname
The name of the job step.
System action: The system fails the dynamic
allocation or dynamic concatenation request with
dynamic allocation error reason code X'04FC'.
Application Programmer Response: If the job that
received the message has JCL DD statements which
specify a high volume count or the job that received the
message uses dynamic allocation to allocate data sets
and specifies a high volume count, reduce the volume
count and rerun the job. If the volume count is derived
from the Data Class, use a Data Class which has a
lower volume count and dynamic volume count, or
contact the Storage Administrator.
Storage Administrator Response: Reduce the
volume count or dynamic volume count specified in the
DATACLAS.
Source: Allocation
Detecting Module: IEFDB4F8 and IEFDB4F9
IEF030I
reqvol
26
IEF085I IEF086I
Source: Converter/interpreter
Detecting Module: IEFVJDTI
IEF085I
16
Descriptor Code: -
24
IEF086I
10
27
IEF087I IEF091I
recurs, contact the IBM Support Center and provide the
internal reason code.
Descriptor Code: 6
IEF090E
Routing Code: 1
Descriptor Code: 3
Routing Code: 11
IEF091I
Descriptor Code: 6
IEF089I
28
IEF092I IEF094A
exists, contact the appropriate group at the IBM Support
Center.
Routing Code: 2
Descriptor Code: 6
Source: Initiator/terminator
Detecting Module: IEFSD161
IEF093I
Routing Code: 2
Descriptor Code: 4
IEF092I
procstep
stepname
xxxK
Source: Initiator/Terminator
Descriptor Code: 6
IEF094A
29
IEF097I IEF100I
Operator response: Restart the initiator that ended.
IEF099I
Source: Initiator/Terminator
Detecting Module: IEFSD166
jobname
Descriptor Code: 11
IEF097I
jobname
Source: Initiator/terminator
userid
Descriptor Code: 2
IEF100I
num
| ERROR
|
The error occurred in allocation processing.
FAILED
The error causes the system to end the allocation
address space.
Source: Initiator/terminator
CREATE
The error occurred while the system was creating
the allocation address space.
30
INITIALIZATION
The error occurred while the system was initializing
the allocation address space.
IEF101I IEF102I
PROCESSING
The error occurred during allocation processing:
|
|
|
|
REASON=rrrrr
Appears if the value for cde is 05C. Report this
reason code to the IBM Support Center. See z/OS
MVS System Codes for more information on the
abend and reason codes.
System action: If ERROR appears in the message
text, allocation processing continues. If FAILED
appears, the running unit of work is terminated. If
DURING INITIALIZATION appears, the system ends the
allocation address space and cannot allocate tape
devices or run the DISPLAY U,,ALLOC command,
which will likely require the system to be reIPLed. In
either case, the system writes an SVC dump and a
logrec data set error record.
Operator response: Notify the system programmer.
System programmer response: If the system ended
the allocation address space, that address space does
not restart until system reIPL.
Source: Allocation
Detecting Module: IEFAB4E6
Routing Code: 2,10
Descriptor Code: 4
IEF101I
procstep
stepname
ddname
+ xxx
Source: Allocation
procstep
stepname
The name of the step.
Routing Code: 11
Descriptor Code: -
reason-code
One of the following:
31
IEF103I IEF106I
IEF103I
Source: Allocation/unallocation
Detecting Module: IEFAB488
Routing Code: 2,3/4,7
Descriptor Code: IEF105I
jobname
procstep
stepname
ddname
+ xxx
jobname
The name of the job.
nnnn
32
procstep
The name of the step in the procedure.
stepname
The name of the job step.
ddname
The name of the DD statement.
callername
The name of the program or process that issued
IEFPRMLB.
System action: The logical parmlib service returns to
its caller without performing the requested function.
Application Programmer Response: Contact the
system programmer.
System programmer response: Examine the system
log to determine if there are messages that might assist
in diagnosing the problem. If necessary, contact IBM
Software Support and provide any diagnostic messages
found in the system log.
Source: Allocation/Unallocation
Detecting Module: IEFPIS01
Routing Code: 11,Note 13
Descriptor Code: 4
IEF106I
IEF107I IEF109I
jobname
The name of the job that is bringing the device
online.
dev
The device number of the unit.
name
A 1- to 8-character name
code
An 8-digit number that, in conjunction with the
name, uniquely identifies the condition
text
A set of messages that further describe the device
status. If the device is not usable, these details may
suggest remedial action.
System action: The system brings the device online,
but conditions may exist that make the device unusable.
Operator response: Check the additional information
to determine if the device is usable. If the device is not
usable in its current state, check the message text for a
suggested remedial action and follow that procedure.
Source: Allocation
Descriptor Code: 4
IEF109I
Descriptor Code: 6
IEF107I
loadxx
The name of the LOADxx parmlib member used to
dynamically change the parmlib concatenation.
reason
One of the following:
v INSUFFICIENT STORAGE AVAILABLE
There was insufficient storage space to
process the request
v THE LIMIT OF DATA SETS WAS EXCEEDED
WHEN PROCESSING DATA SET dsname
The LOADxx parmlib member specified more
than 10 data sets. dsname is the name of the
data set being processed when the limit was
exceeded.
v IEFPRMLB RETURN CODE=return-code
REASON=reason
An unexpected error occurred. The return and
reason codes are from the IEFPRMLB
service. A message issued by the IEFPRMLB
service accompanies this message.
System action: The system continues to use the
33
IEF110I IEF111I
parmlib concatenation that existed before the SETLOAD
command was issued.
Descriptor Code: 5
IEF110I
34
jobname
The name of the job.
procstep
The name of the step in the cataloged procedure.
stepname
The name of the job step.
ddname
The name of the DD statement.
+ xxx
The relative position of a data set within a
concatenation of data sets, including all data sets
implicitly concatenated (through GDG ALL or
IEF112I IEF113I
OPTCD=B requests). See z/OS MVS JCL Users
Guide for more information on GDG ALL or
OPTCD=B requests when used within a set of
concatenated data sets. The first data set of a
concatenation would be +000, but the value +000 is
never shown.
ddd1
The number of tape devices requested.
dev
library
The name of the library containing the volume to be
allocated.
System action: The system fails the allocation
request.
ddd2
The number of tape devices still required.
generic
A generic unit name that is eligible for the request.
Source: Allocation/Unallocation
Source: Allocation/Unallocation
Routing Code: 11
Routing Code: 11
Descriptor Code: 6
Descriptor Code: 2
IEF112I
IEF113I
jobname
The name of the job.
jobname
The name of the job.
procstep
The name of the step in the cataloged procedure.
procstep
The name of the step in the cataloged procedure.
stepname
The name of the job step.
stepname
The name of the job step.
ddname
The name of the dd statement.
ddname
The name of the DD statement.
+ xxx
The relative position of a data set within a
concatenation of data sets, including all data sets
implicitly concatenated (through GDG ALL or
OPTCD=B requests). See z/OS MVS JCL Users
Guide for more information on GDG ALL or
OPTCD=B requests when used within a set of
concatenated data sets. The first data set of a
concatenation would be +000, but the value +000 is
never shown.
+ xxx
The relative position of a data set within a
concatenation of data sets, including all data sets
implicitly concatenated (through GDG ALL or
OPTCD=B requests). See z/OS MVS JCL Users
Guide for more information on GDG ALL or
OPTCD=B requests when used within a set of
concatenated data sets. The first data set of a
concatenation would be +000, but the value +000 is
never shown.
dev
The device number of the device specified for
allocation.
Chapter 2. IEF Messages
35
IEF114I IEF116I
System action: The system fails the allocation
request.
ddname
The name of the DD statement.
+ xxx
The relative position of a data set within a
concatenation of data sets, including all data sets
implicitly concatenated (through GDG ALL or
OPTCD=B requests). See z/OS MVS JCL Users
Guide for more information on GDG ALL or
OPTCD=B requests when used within a set of
concatenated data sets. The first data set of a
concatenation would be +000, but the value +000 is
never shown.
Source: Allocation/Unallocation
Detecting Module: IEFAB424
Routing Code: 11
Descriptor Code: 6
IEF114I
ddd
The number of tape devices required.
System action: The system fails the allocation
request.
Application Programmer Response: Reduce the
number of tape devices required by this DD statement
and then resubmit the job. If this is not possible, notify
the system programmer.
Routing Code: 11
Source: Allocation
Descriptor Code: 6
Routing Code: 11
IEF115I
36
Descriptor Code: 6
IEF116I
IEF117I IEF119I
dev
The device number of the device where the tape
volume was to be mounted.
System action: The system fails the job and unloads
the tape volume. Other error messages explaining the
cause of the failure accompany this message.
Operator response: See the operator response for
the accompanying message.
System programmer response: See the system
programmer response for the accompanying message.
Source: Allocation
Detecting Module: IEFAB49D
Routing Code: 11
Descriptor Code: 6
IEF117I
dev
The device number of a tape device that is defined
in both a system-managed tape library and the
specified esoteric unit name.
System action: The system does not consider
allocating tape devices from the specified esoteric unit
name. The system only considers allocating a device
from the system-managed tape library associated with
that device.
Operator response: Notify the system programmer
and provide the system log containing this message.
System programmer response: Remove the listed
devices from the specified esoteric unit name to
37
IEF120I IEF121A
In the message text:
Source: Allocation
Descriptor Code: 6
| IEF121I
|
Source: Allocation/Unallocation
IEF120I
38
|
|
|
|
|
|
|
|
|
|
IEF122I IEF124I
|
|
|
|
|
|
|
|
Source: Allocation
Descriptor Code: 2
procstep
The name of the step in the procedure.
IEF122I
stepname
The name of the job step.
IEF123I
ddname
The name of the DD statement.
+ xxx
The relative position of a data set within a
concatenation of data sets, including all data sets
implicitly concatenated (through GDG ALL or
OPTCD=B requests). See z/OS MVS JCL Users
Guide for more information on GDG ALL or
OPTCD=B requests when used within a set of
concatenated data sets. The first data set of a
concatenation would be +000, but the value +000 is
never shown.
stepname
The name of the job step.
ddname
The name of the DD statement.
+ xxx
The relative position of a data set within a
concatenation of data sets, including all data sets
implicitly concatenated (through GDG ALL or
OPTCD=B requests). See z/OS MVS JCL Users
Guide for more information on GDG ALL or
OPTCD=B requests when used within a set of
concatenated data sets. The first data set of a
concatenation would be +000, but the value +000 is
never shown.
Source: Allocation
Detecting Module: IEFAB42B
IEF124I
39
IEF125I IEF127I
jobname
The name of the job being processed.
Descriptor Code: 4
procstep
The name of the step in the procedure.
IEF126I
stepname
The name of the job step.
ddname
The name of the DD statement.
+ xxx
The relative position of a data set within a
concatenation of data sets, including all data sets
implicitly concatenated (through GDG ALL or
OPTCD=B requests). See z/OS MVS JCL Users
Guide for more information on GDG ALL or
OPTCD=B requests when used within a set of
concatenated data sets. The first data set of a
concatenation would be +000, but the value +000 is
never shown.
dpoolnam
The name of the Device Pool that could not be
found in the active EDT for this allocation.
hh.mm.ss
The time given as the hour (00-23), the minute
(00-59), and the second (00-59).
System action: The session ends.
Source: Allocation
Detecting Module: IEFBB401
Routing Code: Note 7
Descriptor Code: 4
IEF127I
IEF125I
userid-LOGGED ON [-TIME=hh.mm.ss]
hh.mm.ss
The time given as the hour (00-23), the minute
(00-59), and the second (00-59).
System action: The session enters allocation.
Operator response: None. However, if the user
should not be logged on at this time, enter the CANCEL
U=userid command and the session will be ended.
Source: Allocation
Detecting Module: IEFBB401
Routing Code: Note 7
jobname
The name of the job.
procstep
The name of the step in the procedure.
stepname
The name of the job step.
ddname
The name of the DD statement.
+ xxx
40
IEF128I IEF130I
not new, correct the DISP parameter by specifying OLD,
SHR, or MOD. If the data set is new, add a SPACE
parameter. Then rerun the job.
Source: Allocation
Detecting Module: IEFAB431
Routing Code: 11
Descriptor Code: IEF128I
procstep
The name of the step in the procedure.
stepname
The name of the job step.
ddname
+ xxx
Routing Code: 11
stepname
The name of the job step.
Routing Code: 11
ddname
The name of the DD statement.
Chapter 2. IEF Messages
41
IEF131I IEF132I
+ xxx
Routing Code: 11
Descriptor Code: -
Source: Allocation
Detecting Module: IEFAB431
Routing Code: 11
Descriptor Code: -
IEF132I
jobname
The name of the job.
IEF131I
42
procstep
IEF133I IEF135I
IEF133I
jobname
The name of the job.
procstep
The name of the step in the procedure.
stepname
The name of the job step.
ddname
The name of the DD statement.
+ xxx
Source: Allocation
Routing Code: 11
jobname
Descriptor Code: -
IEF134I
stepname
The name of the job step.
ddname
The name of the DD statement.
+ xxx
43
IEF136I IEF141I
or OPTCD=B requests when used within a set
of concatenated data sets. The first data set of
a concatenation would be +000, but the value
+000 is never shown.
System action: The system ends the job.
Application Programmer Response: Change the
primary space request to a nonzero positive value, then
rerun the job.
Source: Allocation
Detecting Module: IEFAB431
IEF140I
Routing Code: 11
Descriptor Code: IEF136I
+ xxx
jobname
The name of the job.
procstep
The name of the step in the procedure.
stepname
The name of the job step.
ddname
+ xxx
44
IEF141I
IEF142I IEF143I
containing DSNAME=name(INDEX).
stepname
The name of the job step.
cde
ddname
The name of the DD statement.
+ xxx
|
|
|
Routing Code: 11
Source: Initiator/terminator
Descriptor Code: -
IEF142I
|
|
|
|
|
|
45
IEF145I IEF147I
ddname
46
procstep
+ xxx
jobname
The name of the job.
procstep
The name of the step in the cataloged procedure.
stepname
The name of the job step.
ddnamexx
The name of the DD statement.
+ xxx
The relative position of a data set within a
concatenation of data sets, including all data sets
implicitly concatenated (through GDG ALL or
OPTCD=B requests). See z/OS MVS JCL Users
IEF150I IEF151I
Guide for more information on GDG ALL or
OPTCD=B requests when used within a set of
concatenated data sets. The first data set of a
concatenation would be +000, but the value +000 is
never shown.
Source: Allocation/Unallocation
Detecting Module: IEFAB424
Routing Code: 11
Descriptor Code: 6
IEF151I
47
IEF152I IEF154I
IEF152I
Source: Allocation/Unallocation
Routing Code: 11
Routing Code: 11
Descriptor Code: 6
Descriptor Code: 6
IEF154I
IEF153I
48
jobname stepname
CANNOT BRING DEVICES ONLINE
IN LIBRARY libname
BECAUSE LIBRARY IS OFFLINE
Explanation: The allocated/offline installation exit
requested that the system bring a device online, but the
IEF155I IEF156I
device is in an offline system-managed tape library.
Bringing the device online requires that the device
reside in a system-managed tape library that is online.
In the message text:
jobname
The name of the job.
stepname
The name of the job step.
libname
Tape library name.
System action: Instead of bringing the tape devices
online as indicated by the installation exit, the system
takes the action specified by the system default policy.
Source: Allocation
Detecting Module: IEFAB48A
Routing Code: 2
Descriptor Code: 4
IEF155I
49
IEF157E IEF168I
OFFLINE
Tape library is currently offline. A library is
offline if a VARY LIBRARY offline command
has been issued and completed.
IEF157E
jobname [procstep] stepname
ddname [
+ xxx ] NEEDS ddd UNIT(S)
[[FOR VOLUME(S): ser, [ser, [,...,ser]]
[SCRTCH-nnn]
[PRIVAT-nnn]]
| [LIBRARY: libname
LIBRARY STATUS: status]]
ALL ELIGIBLE UNITS ARE
CURRENTLY ALLOCATED
Explanation: A DD statement for a job needs more
tape devices than are currently available to continue
processing.
PENDING OFFLINE
Tape library is currently pending offline. A
library is pending offline if a VARY LIBRARY
command has been issued and has not yet
completed.
ddd
The number of tape devices required.
System action: Processing continues.
Operator response: See the operator response for
accompanying message IEF238D.
Source: Allocation
jobname
The name of the job.
procstep
The name of the step in the cataloged procedure.
Descriptor Code: 3
stepname
The name of the job step.
IEF167I
ddnamexx
The name of the DD statement.
+ xxx
The relative position of a data set within a
concatenation of data sets, including all data sets
implicitly concatenated (through GDG ALL or
OPTCD=B requests). See z/OS MVS JCL Users
Guide for more information on GDG ALL or
OPTCD=B requests when used within a set of
concatenated data sets. The first data set of a
concatenation would be +000, but the value +000 is
never shown.
Routing Code: 11
SCRTCH-nnn
The number of scratch volumes requested.
SCRTCH is used when the dataset being created
on the non-specific volume is temporary
[DISP=(NEW,DELETE) or DSN=&&tempname].
Descriptor Code: 6
IEF168I
PRIVAT-nn
The number of private volumes requested. PRIVAT
is used for all other cases of non-specific volumes.
LIBRARY: libname
The tape library name.
50
IEF169I IEF173I
Descriptor Code: 6
IEF169I
IEF172E
Descriptor Code: 6
IEF170I
Routing Code: 2
n jobname message
jobname
The name of the job or the name of the system
task that requested the WTP operation.
message
53 bytes of the message passed to WTP.
System action: The system issues this message. The
system continues processing.
51
IEF174I IEF177I
x
Descriptor Code: 6
Routing Code: 2
Descriptor Code: 4
IEF175I
IEF177I
keyword
jobname
The duplicate or conflicting keyword.
Source: Initiator/terminator
52
IEF179I IEF187I
IEF179I
16
20
24
procstep
stepname
Routing Code: 11
Descriptor Code: -
IEF187I
IEF186I
53
IEF188I IEF192I
The system writes a logrec data set error record, unless
the ABEND was an OPEN failure. After a program
check or a restart, the system writes a dump to the
SYS1.DUMP data set.
Application Programmer Response: Resubmit the
job.
Source: Initiator/terminator
IEF192I
Descriptor Code: 6
IEF188I
procstep
stepname
ddname
+ xxx
Descriptor Code: -
IEF191I
54
IEF193I IEF195I
IEF193I
procstep
stepname
ddname
+ xxx
procstep
stepname
ddname
+ xxx
Routing Code: 11
Source: Allocation
Descriptor Code: -
IEF195I
Routing Code: 11
Descriptor Code: IEF194I
procstep
stepname
ddname
+ xxx
55
IEF196I IEF197I
OPTCD=B requests). See z/OS MVS
JCL Users Guide for more information
on GDG ALL or OPTCD=B requests
when used within a set of
concatenated data sets. The first data
set of a concatenation would be +000,
but the value +000 is never shown.
System action: The system ends the job.
Application Programmer Response: If possible,
change the program so that fewer volumes need to be
mounted at the same time.
Source: Allocation
Detecting Module: IEFAB42B, IEFAB423, IEFAB426,
IEFAB442, IEFAB464
Routing Code: 11
Descriptor Code: IEF196I
text
56
IEF197I
IEF198I IEF202I
IEF198I
procstep
stepname
procstep
stepname
ddname
+ xxx
IEF201I
procstep
stepname
Source: Allocation
Source: Allocation
Routing Code: 11
Descriptor Code: -
Routing Code: 11
Descriptor Code: -
IEF199I
IEF202I
57
IEF206I IEF209I
CONDITION CODES
A problem program ended by issuing a RETURN
macro that specified a completion code. This
completion code satisfied a condition test in the
COND parameter of an EXEC statement.
IEF206I
COND=ONLY
The COND parameter of an EXEC statement
specified ONLY, but no previous job steps had
abnormally ended.
jobname
jobname
procstep
procstep
stepname
xxxx
stepname
System action: The system does not run the job step
specified by the succeeding EXEC statement. The
system does or does not run the remainder of the job,
depending on the condition tests specified in the EXEC
statement for each step.
Application Programmer Response: If you intended
for the job to end, no action is needed.
System action: The system does not run the job step
specified by stepname. Following steps may or may not
be run depending upon subsequent conditional
expression evaluations.
Application Programmer Response: If you intended
for the job to end, no action is needed.
If not, do one of the following:
v Correct the error that caused the conditional
expression to be evaluated so that the job step is
prevented from running. Rerun the job.
v Change the conditional parameter specified in the
IF/THEN/ELSE/ENDIF clause of the statement
number that is preventing the job step from running.
Rerun the job.
Source: Initiator/terminator
Detecting Module: IEFINCND
Routing Code: 11
Descriptor Code: 6
IEF209I
58
IEF210I IEF211I
jobname
procstep
stepname
Source: Allocation
Detecting Module: IEFAB424, IEFAB464, IEFAB469,
IEFAB470
Routing Code: 11
Descriptor Code: -
IEF211I
jobname
procstep
jobname
procstep
stepname
ddname
stepname
+ xxx
ddname
+ xxx
59
IEF212I IEF213I
impacting the availability of critical system resources.
Routing Code: 11
IEF213I
procstep
stepname
ddname
+ xxx
60
jobname
procstep
stepname
ddname
+ xxx
IEF217I IEF218I
concatenated (through GDG ALL or
OPTCD=B requests). See z/OS MVS
JCL Users Guide for more information
on GDG ALL or OPTCD=B requests
when used within a set of
concatenated data sets. The first data
set of a concatenation would be +000,
but the value +000 is never shown.
System action: The system ends the job.
Application Programmer Response: If a generation
data group (GDG) level of index was coded for a
non-GDG data set, remove the level of index and
resubmit the job. Otherwise, this is probably a system
error. Report this message to the system programmer.
System programmer response: If the problem
recurs, search problem reporting data bases for a fix for
the problem. If no fix exists, contact the IBM Support
Center.
Source: Allocation
Routing Code: 11
jobname
Descriptor Code: -
procstep
IEF217I
stepname
ddname
+ xxx
procstep
stepname
ddname
+ xxx
61
IEF219I IEF222I
IEF219I
procstep
stepname
ddname
+ xxx
procstep
stepname
yyyy
tttt
Routing Code: 11
kkkk
Descriptor Code: -
reason-code
Source: Allocation
IEF221I
62
01
Unrecognized keyword
02
03
Incorrect value
04
Duplicate keyword
05
06
07
No operands specified
08
No keywords specified.
09
No values specified.
10
IEF223I IEF230I
System action: The system ignores the keyword and
its corresponding value. Processing continues on the
next keyword. System defaults will be used for the
absent or incorrect parameters.
System programmer response: Edit the
SYS1.PARMLIB member to correct the error indicated in
the message.
Source: Allocation
Routing Code: 2,Note 13
Descriptor Code: IEF223I
SHOULD jobname.procstep.stepname
[checkidd] RESTART
procstep
stepname
checkidd
63
IEF233A IEF233D
IEF233A
Explanation:
Note: For Automated Tape Library dataservers
(including Virtual Tape Servers), message
IEF233A is not issued to any operator console. It
is only issued to the System Log.
The message asks the operator to mount a volume.
This message is issued by allocation for batch
allocations (that is, JCL) which do not specify DEFER.
(For mounts with DEFER coded, see message
IEC501A.)
In the message text:
dev
ser
labtyp
mediatype
storgrp
|
|
|
|
|
jobname
stepname
dsname
dev
ser
64
IEF234E
v SCRTCH: A scratch volume is to be
mounted. SCRTCH is used when
the dataset being created on the
non-specific volume is temporary
[DISP=(NEW,DELETE) or
DSN=&&tempname].
v PRIVAT: A private volume is to be
mounted. PRIVAT is used for all
other cases of non-specific
volumes.
v A number beginning with L: The
volume to be mounted is unlabeled.
The number is an internal serial
number assigned by the system to
the unlabeled volume. It is of the
form xxxyy, where xxx is the data
set number and yy is the volume
sequence number for the data set.
labtyp
jobname
stepname
dsname
mediatype
storgrp
|
|
|
|
|
Source: Allocation
Detecting Module: IEFAB495
Routing Code: 3/4,5/6
Descriptor Code: 3
IEF234E
Explanation:
Note: For Automated Tape Library dataservers
(including Virtual Tape Servers), message
IEF234E is not issued to any operator console. It
is only issued to the System Log.
text1 is one of the following:
K
D
R
text2 is one of the following:
PVT
PUB
STR
This message asks the operator to demount a volume.
This message can also mean that a volume does not
have enough available space to meet an allocation
request or that a data set already on the volume has
the same name as the data set for which space is to be
allocated.
In the message text:
K
dev
The device number.
ser The volume to be mounted as follows:
v A 6-digit serial number. The volume with that
serial number is to be mounted on device dev.
v A number beginning with L: The volume to be
demounted is unlabeled. The number is an
internal serial number assigned by the system to
the unlabeled volume. It is of the form xxxyy,
where xxx is the data set number and yy is the
volume sequence number for the data set.
65
IEF235D
v If ser is absent from the message text, the
volume is unlabeled and is not being passed
between job steps.
PVT
PUB
A public volume was used.
STR
A storage volume was used.
jobname
The name of the job.
stepname
The name of the job step.
If a MONITOR SPACE command is active, the field
SPACE=cpcc,tttt,aaaa/yyyy,zzzz is specified where:
cpcc
tttt
aaaa
yyyy
zzzz
66
stepname
IEF236I IEF238D
the wait. If a DD statement requested the data set, the
system ends the job. If the allocation was requested
dynamically, a return code will indicate that the request
failed.
Source: Allocation
Detecting Module: IEFAB421
Routing Code: 2
Descriptor Code: 6
IEF236I
procstep
stepname
| 4. is offline
5. is pending offline
DEVICE NAME
Descriptor Code: 6
IEF237I
| WAIT
|
|
|
67
IEF238D
device in an esoteric group named CARTNY
(UNIT=CARTNY), then no devices in that esoteric
group would be allocated until this message is
satisfied.
3. While this message remains outstanding or if the
reply to this message is WAIT, no other allocations,
unallocations, OPENs, CLOSEs, Catalog LOCATEs,
data set OBTAINs, or End-of-Volume (EOV or
FEOV) processing will be able to take place within
this address space until this message is replied to
and the wait is fulfilled. This is because the address
spaces SYSZTIOT resource is held EXCLusive by
this allocation. This statement is true even if an
unallocation would free up the device required by
this allocation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reply of WAIT
Requests device allocation for this job to wait until
the required units and/or volumes are released or
are brought online; that is, no other allocations for
any device(s) will be able to be done within the
address space which issued the message until the
wait is satisfied. Further, no services which require
the SYSZTIOT resource within that address space
will be able to proceed until the wait is satisfied.
This includes services such as OPEN, OPENJ,
CLOSE, LOCATE, OBTAIN, CATALOG and
SCRATCH. The wait does not take effect, however,
until all DD statements that require devices for case
two above have been processed and the operator
has responded to message IEF433D. The system
issues message IEF877E OR IEF878I for any
remaining DD statements and this message.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
68
|
|
|
IEF240I IEF244I
IEF240I
procstep
stepname
xxxxK
procstep
stepname
procstep
stepname
69
IEF245I IEF246I
nnn
stepname
ddname
+ xxx
Source: Allocation
Detecting Module: IEFAB487
Routing Code: 2,3,4,
Descriptor Code: 6
IEF245I
procstep
70
| IEFAB432,IEFAB435,IEFAB441,IEFAB452,IEFAB472
Routing Code: 11
Descriptor Code: IEF246I
procstep
stepname
ddname
+ xxx
IEF251I IEF253I
Application Programmer Response: Check the track
quantity of the SPACE parameter for validity. If it is
incorrect, change it. Then submit the job again.
Source: Allocation
Source: Allocation
Routing Code: 11
Descriptor Code: 6
IEF251I
Routing Code: 2
Descriptor Code: 6
IEF253I
procstep
stepname
ddname
+ xxx
v a volume to be mounted
v an allocated or offline device
and:
v either any of the following are specified in the
ALLOCxx member of the parmlib data set:
VOLUME_ENQ POLICY (CANCEL)
VOLUME_MNT POLICY (CANCEL)
SPEC_WAIT POLICY (CANCEL)
ALLC_OFFLN POLICY (CANCEL)
v or any of the following Installation exits requests that
the job be cancelled:
IEF_VOLUME_ENQ (Volume ENQ Installation
Exit)
IEF_VOLUME_MNT (Volume Mount Installation
Exit)
IEF_SPEC_WAIT (Specification Waits Installation
Exit)
IEF_ALLC_OFFLN (Allocation/Offline Device
Installation Exit)
procstep
stepname
Routing Code: 11
Descriptor Code: -
71
IEF254I IEF257I
IEF254I
+ xxx
procstep
stepname
ddname
+ xxx
procstep
stepname
ddname
72
procstep
stepname
ddname
+ xxx
IEF258I IEF260I
Descriptor Code: IEF258I
procstep
stepname
ddname
+ xxx
procstep
stepname
ddname
+ xxx
Routing Code: 11
Descriptor Code: IEF259I
73
IEF261I IEF263I
Source: Allocation
procstep
stepname
ddname
+ xxx
procstep
stepname
ddname
+ xxx
IEF263I
Source: Allocation
Detecting Module: IEFAB431
Routing Code: 11
74
jobname
procstep
stepname
ddname
+ xxx
IEF264I IEF267I
JCL Users Guide for more information
on GDG ALL or OPTCD=B requests
when used within a set of
concatenated data sets. The first data
set of a concatenation would be +000,
but the value +000 is never shown.
System action: The system ends the job.
Application Programmer Response: Correct the
absolute track subparameter. List the volume table of
contents (VTOC) of each volume that will contain the
data set using the LISTCAT command. If the name of
this data set appears in any VTOC, remove it using the
DEFINE and DELETE commands. Then rerun the job.
Routing Code: 11
Descriptor Code: IEF266I
procstep
Source: Allocation
stepname
ddname
Routing Code: 11
+ xxx
procstep
stepname
ddname
Routing Code: 11
+ xxx
Descriptor Code: -
IEF267I
procstep
stepname
ddname
+ xxx
75
IEF272I IEF273I
JCL Users Guide for more information
on GDG ALL or OPTCD=B requests
when used within a set of
concatenated data sets. The first data
set of a concatenation would be +000,
but the value +000 is never shown.
System action: The system ends the job.
Application Programmer Response: Reduce the
directory quantity subparameter, or increase the primary
quantity subparameter. Then rerun the job.
Source: Allocation
Routing Code: 11
Descriptor Code: -
Routing Code: 11
Descriptor Code: IEF272I
IEF273I
jobname
The name of the job.
procstep
The name of the step in the procedure.
stepname
The name of the job step.
ddname
The name of the DD statement.
+ xxx
The relative position of a data set within a
concatenation of data sets, including all data sets
implicitly concatenated (through GDG ALL or
OPTCD=B requests). See z/OS MVS JCL Users
Guide for more information on GDG ALL or
OPTCD=B requests when used within a set of
concatenated data sets. The first data set of a
concatenation would be +000, but the value +000 is
never shown.
System action: The system ends the job.
Application Programmer Response: In the first case,
specify PS or DA in the DSORG subparameter of the
DCB parameter. In the second case, delete the directory
quantity subparameter of the SPACE parameter. Then
resubmit the job.
Source: Allocation
Detecting Module: IEFAB431
Routing Code: 11
76
IEF274I IEF278I
Descriptor Code: -
procstep
IEF274I
stepname
ddname
+ xxx
nnnn
Source: Allocation
jobname
The name of the job that requested unit affinity.
Routing Code: 11
Descriptor Code: -
procstep
The name of the step in the procedure.
IEF275I
stepname
The name of the step.
ddname
The name of the DD statement.
+ xxx
The relative position of a data set within a
concatenation of data sets, including all data sets
implicitly concatenated (through GDG ALL or
OPTCD=B requests). See z/OS MVS JCL Users
Chapter 2. IEF Messages
77
IEF280I IEF281I
Guide for more information on GDG ALL or
OPTCD=B requests when used within a set of
concatenated data sets. The first data set of a
concatenation would be +000, but the value +000 is
never shown.
reason-code
The reason code, as follows:
1
procstep
The name of the step in the procedure.
stepname
The name of the step.
ddname1
The DD name that the system determined is part of
a data set collection, but for which an inconsistent
device category was specified as compared with
ddname2.
ddname2
The DD name that the system determined is part of
a data set collection, but for which an inconsistent
device category was specified as compared with
ddname1.
unitname
The unit name chosen by the system to replace the
unit affinity specification.
IEF281I
dev
Source: Allocation
Detecting Module: IEFAB42B
Routing Code: 11
Descriptor Code: 6
IEF280I
78
|
|
|
|
|
|
|
|
|
|
|
|
DEVICE IS BOXED
The device was boxed because of a hardware
I/O error, or VARY dev,OFFLINE,FORCE
command processing.
When the system boxes a device, these events
occur:
v I/O on the device ends.
v Any new I/O requests result in permanent
I/O errors.
v No new allocations are done for the device.
v If the device was online, it is marked
pending offline. The device goes offline
when these conditions occur, in this order:
IEF282I
|
|
|
|
|
|
|
|
|
|
|
79
IEF283I
Descriptor Code: 5
IEF283I
10
11
dsname
The data set name. If the data set name is
...PATH=.SPECIFIED..., the problem was with
an HFS file.
rc
80
ser
UNCATALOGED
The data set was not found on all the volumes
listed in the catalog. It was deleted from the
volumes listed in message IEF285I and was
uncataloged.
IEF284I
6
Action
10
11
devnum
The device number.
System action: The system fails the job step or
dynamic allocation request.
Operator response: Determine which system has the
device assigned. Issue the DISPLAY U,,, command
from each system that could vary the device online. In
response, message IEE457I identifies devices assigned
to the system with the letter R, meaning reserved.
If message IEE457I does not also identify the device
with the letter A, meaning allocated, or one of the
other status codes for message IEE457I meaning either
SYS, allocated to system, BOX, hardware error,
BSY, device busy, or other code indicating the
device is unavailable, and you want to make the device
available to the system on which the job (or application)
was running, do the following:
v Vary the device OFFLINE from the system to which it
is currently assigned.
v Vary the device ONLINE to the system the job or
application was running on at the time of error.
v Rerun the job or restart the application that
encountered the error.
Otherwise, CANCEL the job or application and try again
later when the device becomes available.
Source: Allocation
Source: Allocation
81
IEF285I
Routing Code: 11
Descriptor Code: -
IEF285I
rc
ser
Explanation
10
11
82
IEF286I IEF287I
RECATALOGED
The catalog entry for this data set has been
updated (for example, additional volumes for a
multi-volume data set).
SUBSYS
A subsystem data set was allocated.
SYSIN
A system input data set was allocated.
Descriptor Code: -
SYSOUT
A system output data set was allocated.
IEF287I
UNCATALOGED
The data set was uncataloged.
Source: Allocation
Detecting Module: IEFAB4A2
Routing Code: 11
Descriptor Code: -
IEF286I
procstep
stepname
ddname
+ xxx
Explanation
83
IEF287I
data group) generation. This is not
supported by the ICF catalog.
10
11
Density
For dual density tape
requests only
Recording mode
For requests where
compaction information is
required
9
84
ser
IEF288I IEF291I
higher. Uncatalog the data sets using the original
data set names, then catalog the data sets using
the new names.
If dsname is not G0000V00, correct the DSNAME
parameter of the DD statement and submit the job step
again.
If w is 9, resubmit the job, or catalog the data set using
some alternate method, such as the IDCAMS utility.
If w is A, either scratch or move the split cylinder data
set that is creating the error, and run the job again.
If w is 10 or 11, use the access method services
command ALTER ROLLIN to roll in the generation data
set. Generation data sets in a deferred roll-in state can
be referred to by their absolute generation numbers.
Source: Allocation
Routing Code: 2
Routing Code: 11
Descriptor Code: 3
dsname SYSOUT
stepname
xxx
yyy
Source: Allocation
jobname
stepname
Routing Code: 3
Descriptor Code: 4
85
IEF292I IEF300I
IEF292I
stepname
The name of the job step containing the DD
statement
ddname
The DD statement that requires a volume
mount to satisfy the DD request.
+ xxx
devnum
The device number.
System action: The system removes the device from
consideration for allocation until the device can be
successfully assigned to this system.
Source: Allocation
Routing Code: 3
Descriptor Code: 4
IEF294I
devnum
The device number.
System action: The device is now eligible for
allocation on this system.
Source: Allocation
Detecting Module: IEFAB4FX
Routing Code: 11
Descriptor Code: IEF295I
86
IEF300I
IEF301I IEF303I
v If yyyy = FF00, the IEFSSREQ macro instruction
was issued, and xxxx is the value of the
SSOBRETN field in the subsystems option block
(SSOB). See the description of the SSOB in
z/OS MVS Data Areas, Vol 5 (SSAG-XTLST) for
the explanation of the return codes in
SSOBRETN. These codes are listed under
Process SYSOUT Data Sets Return Codes.
v If yyyy is any value except 0000 or FF00, SVC
99 was issued; yyyy is the error reason code
(S99ERROR), and xxxx is the return code in
register 15 from SVC 99 processing. See z/OS
MVS Programming: Authorized Assembler
Services Guide for the explanation of the SVC
99 error reason codes and return codes.
System action: The external writer closed the output
data set on device dev and ends.
Application Programmer Response: Respond as
required for the error code that appears in the message.
When the problem is corrected, enter the START XWTR
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
and the SYSOUT output for the job.
IEF303I
jobname
System action: The external writer is no longer active.
Source: JES2
IEF302A
Source: JES2
87
IEF307I IEF316I
IEF307I
88
Descriptor Code: 6
IEF314I
SYSIO
CCBAD
IEF318I IEF323I
Source: JES2
Routing Code: Note 11
Descriptor Code: IEF318I
procstep
stepname
ddname
+ xxx
INVALID SEGMENT
89
IEF324I IEF327I
specify MSGLEVEL=(1,1), specify it and run the job
again.
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.
Source: JES2
Routing Code: Descriptor Code: IEF324I
90
IEF328I IEF330I
System action: The external writer closes its
SYSOUT data set on device dev and stops itself.
Operator response: Enter another START XWTR
command, specifying the selection criteria of the data
that was being written.
System programmer response: Save the associated
output from the XWTR.
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.
Source: JES2
Routing Code: 2,7,10,11
Descriptor Code: 4
IEF328I
dev
The device number.
jobname
procstep
stepname
ddname
+ xxx
IEF329I
Source: Allocation
Detecting Module: IEFAB459
Routing Code: 11
91
IEF331I IEF336I
Descriptor Code: IEF331I
+ xxx
The relative position of a data set within a
concatenation of data sets, including all data sets
implicitly concatenated (through GDG ALL or
OPTCD=B requests). See z/OS MVS JCL Users
Guide for more information on GDG ALL or
OPTCD=B requests when used within a set of
concatenated data sets. The first data set of a
concatenation would be +000, but the value +000 is
never shown.
ddd1
The number of tape devices requested.
ddd2
The number of tape devices still required.
libname
A system-managed tape library that was eligible to
the request.
IEF333I
IEF336I
jobname
The name of the job.
jobname
procstep
stepname
ddname
+ xxx
procstep
The name of the step in the cataloged procedure.
stepname
The name of the job step.
ddnamexx
The name of the DD statement.
92
IEF337I IEF343I
OPTCD=B requests). See z/OS MVS
JCL Users Guide for more information
on GDG ALL or OPTCD=B requests
when used within a set of
concatenated data sets. The first data
set of a concatenation would be +000,
but the value +000 is never shown.
VOLUME_MNT
An allocation request requires a volume to be
mounted.
IEF343I
SPEC_WAIT
An allocation request must wait for a specific
volume or unit.
ALLC_OFFLN
An allocation request needs an allocated or offline
device.
jobname
procstep
stepname
ddname
+ xxx
procstep
stepname
93
IEF344I IEF347I
Application Programmer Response: Do the
following:
1. Determine whether the data set currently resides on
or is to reside on an SMS-managed volume.
2. Change the UNIT, VOLUME, or STORCLAS
requirements on the allocation request to specify an
eligible volume.
Source: Allocation
Detecting Module: For NOT ENOUGH SYSTEM
MANAGED VOLUMES ELIGBLE, the detecting module
is IEFAB424.
For NOT ENOUGH NON-SYSTEM MANAGED
VOLUMES ELIGIBLE, the detecting module is
IEFAB424.
For REQUIRED STORAGE MANAGER IS NOT
AVAILABLE, the detecting modules are IEFAB42A,
IEFAB42B, IEFAB431, IEFAB434, IEFAB457,
IEFAB464, IEFAB469, IEFAB490, IEFAB492, and
IEFDB413.
Routing Code: 11
Descriptor Code: 6
IEF344I
procstep
stepname
ddname
+ xxx
procstep
stepname
ddname
+ xxx
94
jobname
IEF348I IEF351I
procstep
stepname
ddname
+ xxx
dev
IEF350I
stepname
procstep
Sabn
rrc
Routing Code: 3
dddd
Descriptor Code: 4
95
IEF352I IEF354I
|
|
|
|
|
|
|
|
|
IEF353A
Descriptor Code: 4
IEF352I
Routing Code: 3
96
Descriptor Code: 11
IEF354I
IEF355A IEF357I
IEF355A
97
IEF358I IEF361I
IEF358I
jobname
procstep
stepname
ddname
+ xxx
Routing Code: *
DISPLAY U,,OFFLINE,dev,1
dev
Descriptor Code: 4
IEF360I
Source: Allocation
Detecting Module: IEFAB425
Routing Code: 11
Descriptor Code: IEF359I
98
IEF362I IEF365I
v The system could not allocate or open a required
private catalog.
jobname
jobname
procstep
procstep
stepname
stepname
Source: Allocation
Source: Allocation
Routing Code: 11
Descriptor Code: -
Routing Code: 11
Descriptor Code: IEF362I
IEF364I
procstep
stepname
jobname
procstep
stepname
Source: Allocation
Routing Code: 11
Descriptor Code: -
Source: Allocation
IEF365I
IEF363I
jobname
procstep
stepname
ddname
99
IEF366I IEF369D
+ xxx
Routing Code: 11
Source: Allocation
Detecting Module: IEFAB4FD
Routing Code: 11
Descriptor Code: IEF366I
procstep
stepname
Descriptor Code: -
Routing Code: 11
IEF369D
jobname
jobname
procstep
stepname
stepname
ddname
+ xxx
100
IEF371I IEF374I
Descriptor Code: 2,6
IEF371I
procstep
stepname
ddname
+ xxx
jobname
procstep
stepname
ddname
+ xxx
Source: Allocation
Detecting Module: IEFAB4FD
Routing Code: 11
Descriptor Code: IEF373I
STEP/stepname/START yyyyddd.hhmm
IEF372I
STEP/stepname/STOP yyyyddd.hhmm
CPU xxxx MIN xx.xx SEC
SRB xxxx MIN xx.xx SEC
REAL/VIRT xxxxK SYS xxxxK
EXT xxxxK SYS xxxxK
Chapter 2. IEF Messages
101
IEF375I IEF377I
Explanation: At step ending, system management
facilities (SMF) issues this message to give information
about the step.
yyyyddd.hhmm
The date and time given as the year (using the
4-digit year number, such as 1996 or 2150), and
the day of the year (001-366), the hour (00-23), and
the minute (00-59).
IEF376I
Routing Code: 11
Descriptor Code: JOB/jobname/STOP yyyyddd.hhmm CPU
xxxx MIN xx.xx SEC SRB xxxx MIN xx.xx
SEC
Routing Code: 11
Descriptor Code: -
Routing Code: 11
Descriptor Code: -
IEF377I
IEF375I
JOB/jobname/START yyyyddd.hhmm
jobname
yyyyddd.hhmm
102
IEF378I
v Inability to roll a storage management subsystem
(SMS)-managed generation data set (GDS) into the
generation data group (GDG) base.
Source: Allocation
IEF378I
jobname
procstep
stepname
dsname
disp
procstep
stepname
hh.mm.ss
Source: Allocation
Detecting Module: IEFBB410
103
IEF379I IEF382A
IEF379I
procstep
stepname
IEF381I
dddddddd
The specified device type.
System action: The system used a unit name of
00000000 and continues processing.
Application Programmer Response: Provide the job
log to the system programmer.
System programmer response: Verify that the device
is properly defined to the system.
Source: Allocation
Routing Code: Descriptor Code: IEF382A
jobname
procstep
stepname
ddname
+ xxx
104
jobname
The jobname assigned to the external writer that is
waiting.
Operator response: Perform any desired actions on
IEF383A IEF396I
device dev; then enter REPLY xx,y where y is any
single character. This reply causes the writer to begin
processing the data set.
relpos
Source: JES2
yyyy
Source: JES2
zzzzzzzz
Descriptor Code: 2
IEF391I
Routing Code: 7
Meaning
APPC/MVS
Meaning
Meaning
stepname
The stepname.
procname
The procedure name.
Source: Initiator/Terminator
ddname
The name of the DD statement or dynamic
allocation request.
Chapter 2. IEF Messages
105
IEF402I IEF405I
IEF402I
{jobname|cm| stc_procname.identifier}
FAILED IN ADDRESS SPACE asid
SYSTEM ABEND Scde - REASON
CODE rc
IEF404I
jobname
The command.
jobname-ENDED [-TIME=hh.mm.ss]
hh.mm.ss
stc_procname.identifier
The STC procname and identifier.
asid
cde
rc
Source: Allocation
IEF403I
jobname-STARTED [-TIME=hh.mm.ss]
jjobname
procstep
stepname
hh.mm.ss
ddname
dsname
106
IEF406I IEF420I
System programmer response: Notify the application
programmer who is responsible for the failed Dynamic
Allocation.
Application Programmer Response: Change the
dynamic allocation request to use the 4-digit year format
(yyyyddd) on the expiration date text unit DALEXPDT.
Source: Dynamic allocation
Detecting Module: IEFDB414
Routing Code: 2,11
Descriptor Code: 4
IEF406I
procstep
stepname
ddname
dsname
Source: Allocation
Routing Code: *
Descriptor Code: 5
IEF420I
107
IEF428I IEF433D
Detecting Module: IEFAUSRV
IEF428I
jobname
The job with the incorrect step name.
System action: The system ends the restart for the
job.
Application Programmer Response: Check the
spelling of the step name specified on the RESTART
parameter. Make sure the step name exists.
Source: Interpreter
Routing Code: 2
Descriptor Code: 4
IEF431E
IEF429I
108
IEF433D
operator to respond, based on the following:
v For a batch job, the system can either:
Release the devices that have already been
allocated to the job and cannot be shared with
other jobs.
Leave the devices allocated until the job can be
completely allocated.
v
If the allocation is dynamic, the system can either:
Release only the devices requested by that
particular SVC 99
Leave the devices allocated until the jobs
outstanding requests can be completely allocated.
v
If no online devices are available, then pending
offline devices may be allocated to satisfy the
request.
In the message text:
jobname
109
IEF434D IEF450I
IEF434D
IEF448I
jobname
keywd
val
The keyword.
procstep
stepname
Scde
Ucde
Source: Allocation
110
IEF451I IEF453I
message text, the user program
ended the job step.
xxxxxxxx
hh.mm.ss
IEF452I
jobname
Source: Interpreter/Allocation
procstep
stepname
cde
hh.mm.ss
In response to a MONITOR
JOBNAMES,T command, the time
appears as the hour (00-23), the
minute (00-59), and the second
(00-59).
111
IEF455D IEF458D
This message is routed to any console that issued a
MONITOR JOBNAMES command. If the T operand was
specified in the command, the time appears in the
message.
In the message text:
jobname
hh.mm.ss
Source: Allocation
Detecting Module: IEFBB410
IEF456I
procstep
stepname
dev
Routing Code: 11
|
|
|
|
|
|
|
|
|
112
stepname
IEF464I IEF466I
Operator response: None. However, if you do not
want the job to wait for the data set, reply NO.
Descriptor Code: -
Source: Allocation
IEF465I
Routing Code: 2
Descriptor Code: 6
IEF464I
jobname
procstep
stepname
jobname
procstep
stepname
ddname
Source: Allocation
+ xxx
Source: Allocation
Routing Code: 11
jobname
113
IEF467I IEF469I
procstep
stepname
ddname
+ xxx
procstep
stepname
Source: Allocation
Routing Code: 11
Descriptor Code: -
procstep
stepname
ddname
+ xxx
114
IEF469I
procstep
stepname
IEF470I IEF473I
Detecting Module: IEFAB4FD
jobname
Routing Code: 11
ser
Descriptor Code: -
IEF470I
procstep
stepname
Source: Allocation
Detecting Module: IEFBB416
Routing Code: 11
Descriptor Code: IEF472I
Routing Code: 11
Descriptor Code: -
jobname
procstep
stepname
scde
ucde
xxxxxxxx
Source: Allocation
IEF471E
115
IEF474I IEF476I
procstep
stepname
IEF475I
|
|
|
|
|
|
|
Source: Allocation
jobname
procstep
stepname
ddname
+ xxx
Routing Code: 11
Descriptor Code: IEF474I
procstep
stepname
ddname
+ xxx
116
procstep
stepname
IEF477I IEF478I
ddname
+ xxx
procstep
stepname
ddname
+ xxx
procstep
stepname
ddname
+ xxx
117
IEF479I IEF481I
IEF479I
+ xxx
jobname
procstep
stepname
ddname
Routing Code: 11
+ xxx
Descriptor Code: -
IEF481I
Source: Allocation
jobname
Routing Code: 11
procstep
stepname
ddname
+ xxx
procstep
stepname
ddname
118
IEF482I IEF484I
Application Programmer Response: For different
volume serial numbers, do one of the following:
Source: Allocation
procstep
Source: Allocation
stepname
ddname
Routing Code: 11
+ xxx
jobname
procstep
Source: Allocation
stepname
ddname
+ xxx
119
IEF485I IEF488I
jobname
Routing Code: 11
procstep
Descriptor Code: -
stepname
IEF488I
ddname
+ xxx
Source: Allocation
Detecting Module: IEFAB4FD
Routing Code: 11
Descriptor Code: -
ddname
The name of the DD statement.
IEF485I
+nnn
The relative position of a concatenated DD
statement in relation to the first DD in the
concatenated group.
procstep
stepname
ddname
dev
The device number of the unit.
ser The volume serial.
System action: The system repeats this message for
each DD statement requiring a specific unit or volume
that is allocated and not shareable. The last of these
messages will be followed by message IEF238D,
requesting that the operator decide if the allocation
should wait for the devices to be released or if the job
should be cancelled.
Operator response: Respond to message IEF238D
when it is issued.
Source: Allocation
Source: Allocation
Detecting Module: IEFAB421
120
Descriptor Code: 6
IEF490I IEF491I
IEF490I
121
IEF492I IEF493I
why this problem occurred may be one of the following:
Source: Allocation
jobname
procstep
Routing Code: 11
stepname
Descriptor Code: -
xxxxK
IEF493I
Routing Code: 11
Descriptor Code: -
IEF492I
procstep
stepname
ddname
jobname
+ xxx
procstep
stepname
ddname
+ xxx
122
IEF500I IEF503I
Source: Allocation
Detecting Module: IEFAB4FD
Routing Code: 11
Descriptor Code: IEF500I
ddname
text
dev1 or dev2
The device number of the unit.
123
IEF506I IEF524I
v The system detected a volume serial number that
was not valid on a direct access storage device
(DASD).
jobname
procstep
stepname
dev
ddname
+ xxx
v
Refresh the volume label and try to vary the device
online so that the system can attempt to verify the
volume serial number.
v If the device is mountable, you also can replace the
volume with one having a standard label.
Try to vary the device online so that the system can
attempt to verify the volume serial. Further errors can
indicate that the device experienced a hardware failure;
in this case, contact hardware support.
Source: Allocation
Detecting Module: IEFAB473
Routing Code: */3/4
Descriptor Code: 4/5
Routing Code: 11
Descriptor Code: IEF510I
IEF506I
124
IEF525E IEF572I
dev
The device number.
reason-code
One of the following:
Descriptor Code: 3
IEF550I
[jobname.stepname] VOLUME
VERIFICATION ERROR ON ser
ser
125
IEF602I
System action: The system cancels the job if, during
allocation, the label read was not as expected or an I/O
error occurred while reading the volume label.
Otherwise, the system issues a message and does not
process the volume.
Operator response: Report this error condition to the
system programmer.
System programmer response: If this message is
preceded by message ICB194E for the same volume
with restart code X'80' (incorrect cell location), follow the
recovery actions.
If this message is preceded by message IEA000I (with
28 bytes of sense data), the volume verification error is
due to an I/O error.
If the failure was due to an I/O error and ser was not
SCRTCH, you have two options:
v Option 1: if you want to avoid getting an ICB096I
message for another virtual volume, and this is a
convenient time to assign an alternate track, do the
following:
1. Use the PURGE command with the VOLID
parameter equal to ser to demount the volume.
Vary offline the SSID shown in the previous
IEA000I message.
2. If the SSID is that of the drive with the primary or
secondary tables pack, it is necessary to free the
pack from tables use before processing. If the
SSID is that of the drive with the secondary
tables pack, run the COPYT command. If the
SSID is that of the drive with the primary tables
pack, run the SWAPT command to make the
pack secondary tables pack, and then run the
COPYT command. The pack with the error no
longer contains the primary or secondary tables.
3. Mount the staging pack on a read drive. Use the
DFSMSdss utility to assign an alternate track.
Remount the pack on an offline staging drive.
Vary the SSID for the staging drive online. Restart
the failing job step.
v Option 2: If you can specify the mount on another
staging drive group to avoid the failing SSID, use the
PURGE command with the VOLID parameter equal
to ser to demount the volume. Restart the failing step
with the changed job control language.
If an I/O error occurred and ser is SCRTCH, do the
following:
1. Vary the virtual unit address offline. The device is
in the previous 28-byte IEA000I message.
2. Restart the failing step.
3. At a convenient time, reassign the track in error.
To do this, mount the staging pack on a real
drive, and use the DFSMSdss utility to assign an
alternate track. Remount the pack on an offline
staging drive and vary the SSID of the staging
drive online.
126
IEF604I IEF619I
IEF604I
MISPLACED DD STATEMENT
IEF617I
127
IEF623I IEF624I
Detecting Module: IEFVDA
Descriptor Code: 4
IEF623I
Explanation:
text is one of the following:
IN THE parameter FIELD
ON THE cntr STATEMENT
IN THE parameter1 SUBPARAMETER OF THE
parameter2 FIELD
IN THE SYMBOLIC PARAMETER
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
IN THE parameter OVERRIDE FIELD
The system found one or more incorrect characters in a
JCL statement. All characters in a JCL statement must
belong to the character sets defined in z/OS MVS JCL
Users Guide.
In the message text:
IN THE parameter FIELD
The keyword must be followed by an equal sign to
be considered correctly specified.
In the message text:
parameter
The last correctly specified keyword
parameter preceding the error.
ON THE cntr STATEMENT
The error was detected before any keyword
parameters were processed. For example, an error
was detected in the name field of a statement.
In the message text:
cntr
128
IEF625I IEF632I
System action: The system ends the job. The
remaining job control statements for the job are
scanned for syntax errors.
System programmer response: Probable user error.
Correct the parameter or field. Then submit the job
again.
Source: Interpreter
Detecting Module: IEFVDA
Routing Code: Note 19
Descriptor Code: IEF625I
Explanation:
text is one of the following:
IN THE parameter FIELD
ON THE cntr STATEMENT
IN THE parameter1 SUBPARAMETER OF THE
parameter2 FIELD
129
IEF633I
parameter1
The minor keyword parameter associated
with a major keyword parameter.
parameter2
The major keyword parameter.
System action: The system ends the job and scans
the remaining job control statements for syntax errors.
The system issues messages about the job to the job
log.
Application Programmer Response: Check that the
parameters are specified according to the format that is
documented in the z/OS MVS JCL Reference.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Interpreter
Detecting Module: IEFVDA
Routing Code: 2,10
Descriptor Code: 4
IEF633I
Explanation:
text is one of the following:
IN THE parameter FIELD
ON THE cntr STATEMENT
IN THE parameter1 SUBPARAMETER OF THE
parameter2 FIELD
IN THE SYMBOLIC PARAMETER
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
IN THE parameter OVERRIDE FIELD
The system did not find the programmers name in the
JOB statement. The programmers name is established
as an installation requirement in the PARM parameter of
the reader procedure.
In the message text:
IN THE parameter FIELD
The keyword must be followed by an equal sign to
be considered correctly specified.
In the message text:
parameter
The last correctly specified keyword
parameter preceding the error.
ON THE cntr STATEMENT
The error was detected before any keyword
parameters were processed. For example, an error
was detected in the name field of a statement.
130
parameter
An override keyword parameter on an
EXEC statement.
System action: The system ends the job. The system
scans the remaining job control statements for syntax
errors. The system issues messages about the job to
the job log.
Application Programmer Response: Specify a
programmers name. If a programmers name had been
specified, correct the order of the positional parameters.
Then submit the job again.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Interpreter
Detecting Module: IEFVJA
Routing Code: 2,10
Descriptor Code: 4
IEF634I IEF635I
IEF634I
Explanation:
text is one of the following:
IN THE parameter FIELD
ON THE cntr STATEMENT
IN THE parameter1 SUBPARAMETER OF THE
parameter2 FIELD
IN THE SYMBOLIC PARAMETER
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
IN THE parameter OVERRIDE FIELD
The system could not find the account number on the
JOB statement. The account number was established
as an installation requirement in the PARM parameter of
the reader procedure.
In the message text:
IN THE parameter FIELD
The keyword must be followed by an equal sign to
be considered correctly specified.
In the message text:
parameter
The last correctly specified keyword
parameter preceding the error.
ON THE cntr STATEMENT
The error was detected before any keyword
parameters were processed. For example, an error
was detected in the name field of a statement.
In the message text:
cntr
Explanation:
text is one of the following:
IN THE parameter FIELD
ON THE cntr STATEMENT
IN THE parameter1 SUBPARAMETER OF THE
parameter2 FIELD
IN THE SYMBOLIC PARAMETER
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
IN THE parameter OVERRIDE FIELD
The system could not find the job name. It must appear
in the name field of a JOB statement.
In the message text:
IN THE parameter FIELD
The keyword must be followed by an equal sign to
be considered correctly specified.
In the message text:
parameter
The last correctly specified keyword
parameter preceding the error.
ON THE cntr STATEMENT
The error was detected before any keyword
parameters were processed. For example, an error
was detected in the name field of a statement.
131
IEF636I IEF637I
In the message text:
cntr
132
Explanation:
text is one of the following:
IN THE parameter FIELD
ON THE cntr STATEMENT
IN THE parameter1 SUBPARAMETER OF THE
parameter2 FIELD
IN THE SYMBOLIC PARAMETER
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
IN THE parameter OVERRIDE FIELD
The system found the accounting information in a JOB
or EXEC statement to be longer than the 142
characters permitted.
In the message text:
IN THE parameter FIELD
The keyword must be followed by an equal sign to
be considered correctly specified.
In the message text:
parameter
The last correctly specified keyword
parameter preceding the error.
IEF638I
ON THE cntr STATEMENT
The error was detected before any keyword
parameters were processed. For example, an error
was detected in the name field of a statement.
In the message text:
cntr
IEF638I
Explanation:
text is one of the following:
IN THE parameter FIELD
ON THE cntr STATEMENT
IN THE parameter1 SUBPARAMETER OF THE
parameter2 FIELD
IN THE SYMBOLIC PARAMETER
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
IN THE parameter OVERRIDE FIELD
In a JCL statement, the system found that a parameter
or subparameter value contains a valid number of digits,
but exceeds the maximum numeric limit.
For example, when using ISO, ANSI, or FIPS tape
labels, this message will occur if the user specified a
value larger than 16383 kilobytes on the DD statement
LRECL parameter.
In the message text:
IN THE parameter FIELD
The keyword must be followed by an equal sign to
be considered correctly specified.
In the message text:
parameter
The last correctly specified keyword
parameter preceding the error.
ON THE cntr STATEMENT
The error was detected before any keyword
parameters were processed. For example, an error
was detected in the name field of a statement.
In the message text:
cntr
133
IEF639I
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
The error was detected in the field that assigns a
value to a symbolic parameter.
IN THE parameter OVERRIDE FIELD
The error was detected in an override field.
In the message text:
parameter
An override keyword parameter on an
EXEC statement.
System action: The system ends the job. The system
scans the remaining job control statements for syntax
errors and issues messages about the job to the job
log.
Application Programmer Response: Correct the
parameter or subparameter value. Submit the job again.
For ISO/ANSI/FIPS tape labels, specify the DD LRECL
value as nnnnn kilobytes (where nnnnn=1 to 16383).
This requires the problem program DCB macro to
include the LRECL=OK or LRECL=nnnnnK format.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Interpreter
Detecting Module: IEFVEA
IEFVDA
parameter
The last correctly specified keyword
parameter preceding the error.
ON THE cntr STATEMENT
The error was detected before any keyword
parameters were processed. For example, an error
was detected in the name field of a statement.
In the message text:
cntr
IEF639I
Explanation:
text is one of the following:
IN THE parameter FIELD
ON THE cntr STATEMENT
IN THE parameter1 SUBPARAMETER OF THE
parameter2 FIELD
IN THE SYMBOLIC PARAMETER
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
IN THE parameter OVERRIDE FIELD
In a JCL statement, the system found that the class
name specified as the operand of a parameter or
subparameter was not one of a set of names or values
acceptable for that parameter or subparameter.
In the message text:
IN THE parameter FIELD
The keyword must be followed by an equal sign to
be considered correctly specified.
In the message text:
134
parameter
An override keyword parameter on an
EXEC statement.
System action: The system ends the job. The system
scans the remaining job control statements for syntax
errors and issues messages about the job to the job
log.
Application Programmer Response: Correct the
class name and submit the job again.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Interpreter
Detecting Module: IEFVGT
IEF640I IEF641I
IEF640I
Explanation:
text is one of the following:
IN THE parameter FIELD
ON THE cntr STATEMENT
IN THE parameter1 SUBPARAMETER OF THE
parameter2 FIELD
IN THE SYMBOLIC PARAMETER
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
IN THE parameter OVERRIDE FIELD
The system found too many positional parameters in a
JCL statement. A misplaced comma, a duplication, or a
null operand field could cause such an error.
In the message text:
IN THE parameter FIELD
The keyword must be followed by an equal sign to
be considered correctly specified.
parameter
An override keyword parameter on an
EXEC statement.
System action: The system ends the job. The system
scans the remaining job control statements for syntax
errors and issues messages about the job to the job
log.
Application Programmer Response: Check for
duplicate positional parameters or misplaced commas.
Submit the job again.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Interpreter
Detecting Module: IEFNB901, IEFVGT
Routing Code: 2,10
Descriptor Code: 4
parameter
The last correctly specified keyword
parameter preceding the error.
IEF641I
135
IEF642I IEF643I
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
The system found the error in the field that assigns
a value to a symbolic parameter.
IN THE prm OVERRIDE FIELD
prm is an override keyword parameter on an EXEC
statement.
System action: The system ends the job. The system
scans the remaining job control statements for the job
for syntax errors.
Application Programmer Response: Correct the
parameter. Resubmit the job.
Source: Interpreter
Routing Code: 2,10
Descriptor Code: 4
IEF642I
parameter
An override keyword parameter on an
EXEC statement.
Explanation:
text is one of the following:
IN THE parameter FIELD
ON THE cntr STATEMENT
IN THE parameter1 SUBPARAMETER OF THE
parameter2 FIELD
IN THE SYMBOLIC PARAMETER
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
IN THE parameter OVERRIDE FIELD
In a JCL statement, the system found a parameter that
was longer than permitted.
In the message text:
IN THE parameter FIELD
The keyword must be followed by an equal sign to
be considered correctly specified.
parameter
The last correctly specified keyword
parameter preceding the error.
Descriptor Code: 4
136
IEF643I
UNIDENTIFIED POSITIONAL
PARAMETER text
IEF644I
In the message text:
IN THE parameter FIELD
The keyword must be followed by an equal sign to
be considered correctly specified.
In the message text:
parameter
The last correctly specified keyword
parameter preceding the error.
ON THE cntr STATEMENT
The error was detected before any keyword
parameters were processed. For example, an error
was detected in the name field of a statement.
In the message text:
cntr
Explanation:
text is one of the following:
IN THE parameter FIELD
ON THE cntr STATEMENT
IN THE parameter1 SUBPARAMETER OF THE
parameter2 FIELD
IN THE SYMBOLIC PARAMETER
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
IN THE parameter OVERRIDE FIELD
In a JCL statement, the system found an alphabetic or
special character in a parameter that can contain only
numeric characters.
In the message text:
IN THE parameter FIELD
The keyword must be followed by an equal sign to
be considered correctly specified.
In the message text:
parameter
The last correctly specified keyword
parameter preceding the error.
ON THE cntr STATEMENT
The error was detected before any keyword
parameters were processed. For example, an error
was detected in the name field of a statement.
In the message text:
cntr
137
IEF645I
IN THE SYMBOLIC PARAMETER
The error was detected in the symbolic parameter.
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
The error was detected in the field that assigns a
value to a symbolic parameter.
IN THE parameter OVERRIDE FIELD
The error was detected in an override field.
In the message text:
parameter
An override keyword parameter on an
EXEC statement.
System action: The system ends the job. The system
scans the remaining job control statements for syntax
errors and issues messages about the job to the job
log.
Application Programmer Response: Correct the
erroneous parameter. Submit the job again.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Interpreter
Detecting Module: IEFVGT
Routing Code: 2,10
Descriptor Code: 4
IEF645I
Explanation:
text is one of the following:
IN THE parameter FIELD
ON THE cntr STATEMENT
IN THE parameter1 SUBPARAMETER OF THE
parameter2 FIELD
IN THE SYMBOLIC PARAMETER
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
IN THE parameter OVERRIDE FIELD
In a JCL statement, the system found a parameter that
specified the name of a previous statement. However, a
statement with that name was not found, or the
statement contained the DYNAM parameter.
In the message text:
IN THE parameter FIELD
The keyword must be followed by an equal sign to
be considered correctly specified.
In the message text:
138
parameter
The last correctly specified keyword
parameter preceding the error.
ON THE cntr STATEMENT
The error was detected before any keyword
parameters were processed. For example, an error
was detected in the name field of a statement.
In the message text:
cntr
IEF646I IEF647I
Source: Interpreter
Detecting Module: IEFVEA
Routing Code: 2,10
Descriptor Code: 4
IEF646I
Source: Interpreter
parameter
The last correctly specified keyword
parameter preceding the error.
139
IEF648I IEF649I
IN THE parameter FIELD
The keyword must be followed by an equal sign to
be considered correctly specified.
In the message text:
parameter
The last correctly specified keyword
parameter preceding the error.
ON THE cntr STATEMENT
The error was detected before any keyword
parameters were processed. For example, an error
was detected in the name field of a statement.
IEF648I
PASS
parameter2
The major keyword parameter.
IN THE SYMBOLIC PARAMETER
The error was detected in the symbolic parameter.
Note: A symbolic parameter consists of a single
ampersand (&) followed by a maximum of
seven alphanumeric (A through Z and 0
through 9) and national (@, #, $) characters.
The first character after the ampersand must
be alphabetic or national, that is, it cannot
be a number.
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
The error was detected in the field that assigns a
value to a symbolic parameter.
IN THE parameter OVERRIDE FIELD
The error was detected in an override field.
In the message text:
parameter
An override keyword parameter on an
EXEC statement.
System action: The system ends the job. The system
scans the remaining job control statements for syntax
errors and issues messages about the job to the job
log.
Application Programmer Response: Correct the
name field and submit the job again.
140
EXCESSIVE NUMBER OF DD
STATEMENTS
IEF650I IEF655I
the remaining job control statements for syntax errors.
The system issues this message with each DD
statement that exceeds the permitted limit.
Application Programmer Response: Either remove
the excess DD statement(s) or add a missing EXEC
statement. Submit the job again. If you need more than
the permitted number of DD statements in a job, see
the system programmer.
System programmer response: If you want to
increase the permitted number of DD statements in a
job statement, modify the size of the task input/output
table (TIOT). See z/OS MVS Using the Subsystem
Interface for information about the DD statement.
If the JOB statement did not specify MSGLEVEL=(1,1),
specify it and run the job again. 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 the SYSOUT output for the job.
Source: Interpreter
Detecting Module: IEFVDA
Routing Code: 2,10
Descriptor Code: 4
IEF650I
Descriptor Code: 4
IEF654I
IEF655I
Source: Interpreter
Descriptor Code: 4
Routing Code: 2
Chapter 2. IEF Messages
141
IEF656I IEF670I
IEF656I
IEF667E
Source: Interpreter
Detecting Module: IEFVDA
Routing Code: 2,10
Descriptor Code: 4
IEF661I
IEF669I
Source: Interpreter
Descriptor Code: 4
IEF670I
142
IEF671I IEF674I
the PROC statement of the procedure. The symbol has
no default value, and is therefore undefined.
Note: The symbolic parameter in question may have
the same spelling as some valid EXEC statement
keyword, such as REGION.
System action: The system ends the job and issues
messages about the job to the job log.
Application Programmer Response: Correct the
error by doing one of the following:
v Give the symbolic parameter a default value on the
PROC statement.
v Make a value assignment for it on the EXEC
statement.
v Change the name of the symbolic parameter.
Resubmit the job.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Interpreter
Detecting Module: IEFVEA
Routing Code: 2,10
Descriptor Code: 4
IEF671I
IEF673I
Source: Interpreter
143
IEF675I IEF680I
continues processing the job. The system issues
messages about the job to the job log.
Application Programmer Response: Correct the
value and resubmit the job if necessary.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Interpreter
Detecting Module: IEFVEA
Routing Code: 2,10
Descriptor Code: 4
IEF679I
IEF675I
144
IEF681I IEF684I
again. 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 the SYSOUT
output for the job.
Descriptor Code: 4
IEF683I
Source: Interpreter
Detecting Module: IEFVHE
Routing Code: 2,10
Descriptor Code: 4
IEF681I
{CONVERTER | INTERPRETER}
TERMINATED DUE TO abendcde
ABEND REASON=reason-code
145
IEF685I IEF687I
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: Interpreter
Detecting Module: IEFVDA
Routing Code: 2,10
Descriptor Code: 4
IEF685I
procstep
stepname
Descriptor Code: 4
ddname
IEF686I
+ xxx
Source: Interpreter
Detecting Module: IEFVHH
146
IEF688I IEF691I
name of a JES3-managed unit. Resubmit the job.
Source: Allocation
jobname
Routing Code: 11
Source: Initiator/terminator
Descriptor Code: -
Routing Code: 11
IEF688I
procstep
stepname
ddname
+ xxx
stepname
ser
Routing Code: 2
IEF691I
Descriptor Code: 6
Source: Allocation
Detecting Module: IEFAB490
IEF689I
procstep
stepname
ddname
147
IEF692I IEF696I
+ xxx
DDNAME REFERENCE TO DD
CONCATENATION REFERS ONLY TO
FIRST DD
IEF692I
INVALID REFERENCE TO
HIERARCHICAL FILE [text]
148
IEF695I
IEF700I IEF702I
v The device may have been marked NOT READY.
Source: Allocation
procstep
stepname
ddname
+ xxx
DISPLAY U,,OFFLINE,dev,1
In the response, message IEE457I, look for an R in the
STATUS field. If present, the device is reserved. Run
the program that uses the device later when the device
is no longer reserved.
If the device cannot be readied through operator action
or is not reserved, contact hardware support to
determine why the device is not accepting I/O requests.
Source: Allocation/unallocation
Detecting Module: IEFAB4E0
Routing Code: 2,3 or 2,4
Descriptor Code: 4
IEF700I
IEF702I
jobname
procstep
stepname
149
IEF703I IEF704I
v Any devices in the collection that are boxed are
unavailable.
procstep
stepname
ddname
+ xxx
150
procstep
stepname
ddname
+ xxx
IEF705I IEF706I
set of a concatenation would be +000,
but the value +000 is never shown.
ALLOC: nnn
AVAIL: nnn
u1-u5
flg1 flg2
Descriptor Code: 7
date
time
module
instance
jobname
stepname
procstep
|
|
|
|
|
|
ddname
+zzz srelpos
unitname
TOTAL: nnn
OFFN: nnn
| IEF706I
|
|
|
|
|
|
|
|
|
| Source: Allocation
| Detecting Module: IEFIBER4
151
IEF713I IEF716I
| Routing Code: 2
| Descriptor Code: 12
Source: Allocation
Detecting Module: IEFAB4FD
IEF713I
procstep
stepname
jobname
procstep
stepname
Routing Code: 11
Source: Allocation
Descriptor Code: -
Routing Code: 11
IEF714I
procstep
stepname
152
procstep
stepname
IEF717I IEF720I
after the system programmer has corrected the error
indicated in IEF710I or IEF712I.
Descriptor Code: -
Source: Allocation
IEF719I
procstep
stepname
ddname
jobname
+ xxx
procstep
stepname
Routing Code: 11
Source: Allocation
Detecting Module: IEFAB4FD
Routing Code: 11
Descriptor Code: 6
procstep
stepname
IEF720I
Source: Allocation
procstep
stepname
ddname
153
IEF721I IEF722I
+ xxx
IEF722I
Source: Allocation
Detecting Module: IEFAB4FD
Routing Code: 11
Descriptor Code: 6
IEF721I
procstep
stepname
ddname
+ xxx
154
FAILED BY INSTALLATION
The system ended the job at job initiation.
USER ACCESS IS REVOKED
The system revoked the users access.
OIDCARD IS REQUIRED
The user must supply an operator identifier
magnetic stripe card when logging on to the
system.
GROUP ACCESS REVOKED
The system revoked the users access to a group.
IEF723E IEF725I
RETURN CODE NOT VALID
The security product found an error while checking
user access.
System action: The system abnormally ends the job.
Application Programmer Response: Depending on
the message text, do one of the following:
USERID IS REQUIRED
Enter a valid userid on the JCL JOB statement.
INVALID PASSWORD GIVEN
EXPIRED PASSWORD GIVEN
NEW PASSWORD NOT VALID
USER NOT PART OF GROUP
Enter the correct value for PASSWORD or GROUP.
Run the job again.
procstep
stepname
Routing Code: 11
procstep
stepname
ddname
+ xxx
rc
155
IEF726I IEF731I
IEF726I
IEF730I
jobname
procstep
stepname
ddname
+ xxx
Routing Code: 11
num
name
kw
Source: Allocation
Detecting Module: IEFAB4FD
Identifier
Keyword
01
NO KEYWORD CAN BE
DETERMINED
02
PGMNAME
03
KEY
04
CANCEL
05
NOCANCEL
06
SWAP
07
NOSWAP
stmt
08
PRIV
09
NOPRIV
156
IEF732I IEF734I
rc
10
DSI
11
NODSI
12
SYST
13
NOSYST
14
PASS
15
NOPASS
16
AFF
17
SPREF
xx
18
LPREF
num
19
NOPREF
name
Reason Code
Explanation
04
A delimiter between
keywords is either missing or
misplaced.
IEF732I
08
Source: Initiator/terminator
12
16
Descriptor Code: 6
20
A duplicate keyword is
specified.
IEF734I
24
28
32
36
40
44
Routing Code: 10
SCHEDxx LINE
num:[RESTART|NORESTART] [CODE
cde|STATEMENT]
[IGNORED|ACCEPTED]. REASON=kyrc
xx
num
STATEMENT
RESTART
NORESTART
cde
kyrc
157
IEF735I IEF737I
0108
0128
0144
0148
02rc
0216
0252
0256
0260
IEFSSNzz
The second parmlib member
System action: The system continues processing.
System programmer response: Check the
SYS1.PARMLIB concatenation. Remove the duplicate
entry.
Source: Subsystem interface (SSI)
Detecting Module: IEFJSIMW
Routing Code: 2,10
Descriptor Code: 4
IEF736A
keyword
The incorrect keyword in the parmlib member
System action: The system continues processing.
System programmer response: Correct the incorrect
keyword in the IEFSSNxx member.
Source: Subsystem interface (SSI)
IEF735I
158
IEF738I IEF740I
IEF738I
mem LINE
num:[RESTART|NORESTART] STMT
IGNORED. NO OPERANDS SPECIFIED.
num
RESTART
NORESTART
IEF740I
procstep
stepname
ddname
+ xxx
Routing Code: 11
Chapter 2. IEF Messages
159
IEF741I IEF743I
Descriptor Code: 6
IEF741I
IEF742I
procstep
stepname
Descriptor Code: -
jobname
procstep
IEF743I
stepname
ddname
+ xxx
jobname
cm
The command.
asid
Source: Allocation
Source: Initiator/terminator
Routing Code: 11
Descriptor Code: 6
Routing Code: 2
Descriptor Code: 4,5,6
160
IEF751I IEF754I
IEF751I
procstep
stepname
procstep
stepname
ddname
+ xxx
procstep
stepname
ddname
+ xxx
161
IEF755I IEF757I
jobname
procstep
stepname
ddname
Routing Code: 11
+ xxx
Descriptor Code: _
IEF756I
procstep
Source: Allocation
stepname
ddname
Routing Code: 11
+ xxx
jobname
procstep
stepname
ddname
+ xxx
162
Source: Allocation
Detecting Module: IEFAB427
Routing Code: 11
Descriptor Code: _
IEF757I
IEF758I IEF759I
Application Programmer Response: Correct the data
set name. Use other system functions to access the
data set. For example, code an authorized program to
read the job file control block (JFCB). Change the data
set name in the JFCB to the data set name containing
the 12-4-9 multipunch, be sure that JFCBNWRT is off in
the JFCB, and issue an OPEN (TYPE=J) macro using
the modified JFCB.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Interpreter
Detecting Module: IEFVDA
Routing Code: 2,10
Descriptor Code: 4
IEF758I
163
IEF760I
storage to build the SHAS. The
subsystems are available, but the SHAS is
not. In this case, the xxxx field is blank.
4
IEF760I
rc
Explanation
01
A delimiter is missing.
02
03
04
05
06
07
08
09
0A
0B
Records conflict.
0C
A keyword is incorrect.
0D
incorrect-record
The first 70 characters of the record containing
the error.
System action: The system issues this message for
the first incorrect parameter on a record. The system
does not check the rest of the record. The system
ignores the erroneous record and continues with the
next record.
System programmer response: Correct the
parameter in error. If the information on the record is
crucial to system processing, enter the command again.
Then ask the operator to reIPL the system.
Descriptor Code: 4
164
IEF761I IEF765I
Routing Code: 2,10
Descriptor Code: 4
IEF761I
Source: Allocation/Unallocation
jobname
The name of the job.
IEF764I
procstep
The name of the step in the procedure.
stepname
The name of the job step.
ddname
The name of the DD statement.
callername
The name of the program or process that issued
IEFPRMLB.
procstep
The name of the step in the procedure.
membername
The name of the parmlib member.
stepname
The name of the job step.
ddname
The name of the DD statement.
callername
The name of the program or process that issued
IEFPRMLB.
membername
The name of the parmlib member.
System action: The logical parmlib service stops
165
IEF766I IEF768I
Hardware Support and provide any diagnostic
messages found in the system log or LOGREC records.
IEF767I
Source: Allocation/Unallocation
Detecting Module: IEFPIS01
Routing Code: 11,Note 13
Descriptor Code: 4
IEF766I
Source: Allocation/Unallocation
jobname
The name of the job.
procstep
The name of the step in the procedure.
stepname
The name of the job step.
ddname
The name of the DD statement.
166
IEF769I IEF771I
callername
The name of the program or process that issued
IEFPRMLB.
System action: The logical parmlib service
unallocates the logical parmlib concatenation.
Application Programmer Response: Contact the
system programmer.
System programmer response: Examine the system
log to determine if there are any messages that might
assist in diagnosing the problem. If necessary, contact
IBM Software Support and provide any diagnostic
messages found in the system log.
Source: Allocation/Unallocation
Detecting Module: IEFPIS01
Routing Code: 11,Note 13
Descriptor Code: 4
IEF769I
IEF770I
callername
The name of the program or process that issued
IEFPRMLB.
Descriptor Code: 4
IEF771I
167
IEF772I IEF776I
ASSIGN FAILED, RETURN CODE=return-code
The device could not be assigned because of an
I/O error, as indicated by return code return-code.
Possible values for return-code are:
16
20
zzzzzzzz
The number of DD statements per job step.
System action: The system continues processing.
Source: Allocation
Routing Code: 2
Descriptor Code: IEF775I
IEFAB4CB
Routing Code: -
Source: Allocation/Unallocation
Descriptor Code: 5
Source: Allocation
Detecting Module: IEFAB429
IEF773I
168
IEF777I IEF779I
In the message text:
jobname
The name of the job.
procstep
The name of the step in the procedure.
stepname
The name of the job step.
ddname
The name of the DD statement.
callername
The name of the program or process which invoked
the Logical Parmlib Service.
Source: Allocation/Unallocation
Detecting Module: IEFPIS01
| IEF778I
|
|
|
|
|
|
|
| ssnm
|
The name of the subsystem.
Descriptor Code: 4
|
|
|
|
IEF777I
| Source: Allocation
| Detecting Module: IEFAB427
| Routing Code: Note 36
| Descriptor Code: IEF779I
169
IEF781I IEF786I
callerid
The caller ID that requested the device be varied
offline.
System action: The system will continue to try to take
the device offline.
Operator response: Verify that this device should be
taken offline. If not, vary the device online.
Source: Allocation
Detecting Module: IEFAB429
Routing Code: *,2,3,4,7,8,HRDCPY
Descriptor Code: 4
IEF781I
170
jobname
The name of the job.
procstep
The name of the step in the procedure.
stepname
The name of the job step.
callername
The name of the program or process that issues
IEFPRMLB.
System action: The call to the logical parmlib service
fails.
Application Programmer Response: If the calling
program is an installation program, change the program
so its input read buffer is properly accessible to the
logical parmlib service. Otherwise, contact the system
programmer.
System programmer response: Contact the owner of
the calling program.
Source: Allocation/Unallocation
Detecting Module: IEFPIS01
Routing Code: 11,Note 13
Descriptor Code: 4
IEF786I
IEF787I IEF790I
IEF787I
stepname
The name of the job step.
ser The volume serial number of the tape volume for
which the verify attempt failed.
dev
The device number of the tape device where ser is
mounted.
System action: The system unloads the tape volume,
places the volume in an error category (if it is a
system-managed tape library volume), and then fails the
allocation.
System programmer response: Ensure that the tape
is properly labeled.
Source: Allocation
dev
IEF790I
171
IEF791I IEF815I
dev
Descriptor Code: 5
IEF791I
Source: Interpreter
stepname
The name of the job step.
Descriptor Code: 4
IEF812I
dev
The device number of the tape device where ser is
mounted.
System action: The system unloads the tape volume
and requests an SVC dump.
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
SVC dump.
Routing Code: -
Descriptor Code: 5
Source: Interpreter
Source: Allocation
Detecting Module: IEFAB49B
IEF811I
Explanation:
text is one of the following:
PRIOR TO THE FIRST EXEC
WITHIN A STEP
In a JCL statement, the system found a verb and label
that were duplicates of a verb and label on a previously
specified JCL statement. Verb and label specification
must be unique prior to the first EXEC statement and
within steps.
172
IEF817I IEF819I
parameter
The last correctly specified keyword preceding
the error.
System action: The system ends the job and scans
the remaining JCL statements for syntax errors. The
system issues messages about the job to the job log.
Application Programmer Response: Change the
incorrect parameter value and submit the job again.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Interpreter
Detecting Module: IEFVJDTI
Routing Code: 2,10
Descriptor Code: 4
IEF817I
IEF818E
STORAGE UNAVAILABLE
The system could not obtain enough virtual storage.
UNABLE TO SET UP RECOVERY ENVIRONMENT
The system could not establish a recovery routine.
SYSTEM ERROR IN JCL INITIALIZATION
An abend occurred when the system tried to
initialize the JCL definition tables for the system.
System action: System initialization continues. The
system may write an SVC dump. Some JCL jobs could
fail because of unrecognized keywords or verbs, even
though the keywords and verbs are correct.
Operator response: Do the following:
v Notify the system programmer.
v After the system programmer fixes the problem, reIPL
the system.
System programmer response: If MODULE name
NOT FOUND appears in the message, check
SYS1.LINKLIB for the module. Correct the problem. Ask
the operator to reIPL the system.
If STORAGE UNAVAILABLE appears in the message,
enlarge the storage for the system. Then ask the
operator to reIPL.
Otherwise, search problem reporting data bases for a fix
for the problem. If no fix exists, contact the IBM Support
Center.
Source: Scheduler JCL facility (SJF)
Detecting Module: IEFSJINT
Source: Interpreter
Routing Code: 1
Descriptor Code: 11
IEF819I
173
IEF820I IEF824I
misplaced comma, a duplication, or a null operand field
could cause such an error.
In the message text:
parameter
The last correctly specified keyword preceding
the error. Note that a keyword must be
followed by an equal sign to be considered
correctly specified.
System action: The system ends the job. The system
scans the remaining job control statements for syntax
errors. The system issues messages about the job to
the job log.
Application Programmer Response: Correct the
error and submit the job again.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Interpreter
Detecting Module: IEFVJDTI
Routing Code: 2,10
Descriptor Code: 4
IEF820I
IEF824I
parameter
The last correctly specified keyword preceding
the error.
174
xx
yy
IEF825I IEF874I
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
IEFGB4DC
Source: Interpreter
Routing Code: 11
Descriptor Code: IEF863I
jobname
| returncode
|
|
|
|
|
Source: Interpreter
IEF452I
IEF458D
Descriptor Code: 4
IEF861I
Routing Code: 11
Descriptor Code: 6
IEF874I
175
IEF875I IEF877E
jjj
proc
sss
VOLUME_ENQ
An allocation request has to wait for a volume or a
series of volumes.
ddname
The name of the DD statement.
System action: The allocation request fails.
Application Programmer Response: Correct the
ALLC_OFFLN exit to specify device numbers when you
specify the BRING DEVICE ONLINE option. See z/OS
MVS Installation Exits for details on how to specify
device numbers for devices that are to be varied online.
Source: Allocation
Routing Code: 11
Descriptor Code: -
Routing Code: 11
Descriptor Code: 6
IEF875I
IEF877E
state1
[dev[dev ... dev]]
.
.
.
state2
[dev[dev ... dev]]
.
.
.
staten
[dev[dev ... dev]]
.
.
.
proc
sss
ddname
176
IEF877E
SCRTCH-nnn
The number of scratch volumes requested.
SCRTCH is used when the dataset being created
on the non-specific volume is temporary
[DISP=(NEW,DELETE) or DSN=&&tempname].
PRIVAT-nn
The number of private volumes requested. PRIVAT
is used for all other cases of non-specific volumes.
libname
The tape library name.
status
The tape library status. It can be one of the
following:
ONLINE
Tape library is currently online.
OFFLINE
Tape library is currently offline. A library is
offline if a VARY LIBRARY offline command
has been issued and completed.
PENDING OFFLINE
Tape library is currently pending offline. A
library is pending offline if a VARY LIBRARY
command has been issued and has not yet
completed.
dev
A list of the device numbers. If dev is preceded by
an asterisk (*), the device is pending offline. Device
numbers may be represented as single devices
(either offline or pending offline) (for example, 0274
or *0274) or as ranges of devices (either offline or
pending offline) (for example, 0274-0279 or
*0274-*0279).
state1, state2, ... state2
Describes the state of all the listed devices. The
possible states are: are:
OFFLINE
Eligible devices that are currently offline or
pending offline because the operator issued a
VARY offline command for the devices.
OFFLINE, LIBRARY OFFLINE
Eligible devices that are currently offline or
pending offline because the operator issued a
VARY offline command for the devices and
because the tape library in which the devices
reside is offline or pending offline.
LIBRARY OFFLINE
Eligible tape devices that are currently offline
or pending offline only because the tape library
in which the devices reside is offline or pending
offline.
CONFIGURATION OFFLINE
Eligible devices that are currently offline or
pending offline to the installation configuration
because the configuration manager issued a
VARY OFFLINE.
177
IEF877E
|
|
|
|
178
LIBRARY OFFLINE
Enter a VARY SMS library command to bring
the library online. Reply to IEF238D with the
device number.
CONFIGURATION OFFLINE
Reply to IEF238D with the device number.
CONFIGURATION OFFLINE, LIBRARY OFFLINE
Enter a VARY SMS library command to bring
the library online. Reply to IEF238D with the
device number.
NOT ACCESSIBLE
Enter a VARY command to bring the path to
the device online. Reply to IEF238D with the
device number.
OFFLINE, NOT ACCESSIBLE
Enter a VARY command to bring the path to
the device online. Reply to IEF238D with the
device number.
LIBRARY OFFLINE, NOT ACCESSIBLE
Enter a VARY command to bring the path to
the device online. Enter a VARY SMS library
command to bring the library online. Reply to
IEF238D with the device number.
OFFLINE, LIBRARY OFFLINE, NOT ACCESSIBLE
Enter a VARY command to bring the path to
the device online. Enter a VARY SMS library
command to bring the library online. Reply to
IEF238D with the device number.
CONFIGURATION OFFLINE, NOT ACCESSIBLE
Enter a VARY command to bring the path to
the device online. Reply to IEF238D with the
device number.
CONFIGURATION OFFLINE, LIBRARY OFFLINE, NOT
ACCESSIBLE
Enter a VARY command to bring the path to
the device online. Enter a VARY SMS library
command to bring the library online. Reply to
IEF238D with the device number.
Note: If a device listed as NOT ACCESSIBLE has no
physical paths, it cannot be made usable by
entering a VARY PATH command.
Application Programmer Response: If the system
failed the job, make any changes indicated by other
messages. Submit the job again.
Source: Allocation
Detecting Module: IEFAB48A
Routing Code: 2
Descriptor Code: 3
IEF878I IEF880I
IEF878I
IEF880I
ddname
The name of the DD statement.
+zzz
The relative position of a concatenated DD
statement in relation to the first DD in the
concatenated group.
Descriptor Code: 4
Chapter 2. IEF Messages
179
IEF881I IEF893I
For a boxed, allocated device, these actions are
the preferred method for bringing the device
online, as it allows the device to be taken offline
before it is brought back online. This causes the
operating system to perform VOLSER
verification and path validation.
devn
The device number to be unloaded, varied offline
and varied online.
rsn
abcd
The system abend code.
The abend reason code.
System action: The system continues processing.
Operator response: Notify the system programmer.
System programmer response: Obtain the system
log and the abend dump, then contact the IBM Support
Center.
Source: Allocation
|
|
|
VARY ONLINE
Allocation was processing a \VARY
ONLINE command.
VARY OFFLINE
Allocation was processing a pending
VARY OFFLINE command.
|
|
UNLOAD
Allocation was processing a pending
UNLOAD command.
180
IEF894I IEF897I
the S99TIOEX indicator in the SVC 99 Request Block
(S99RB).
Source: Allocation
Detecting Module: IEFDB450
IEF896I
Routing Code: 2
Descriptor Code: 4
IEF894I
Descriptor Code: 4
IEF895I
|
|
|
|
181
Source: Allocation
Detecting Module: IEFCTIT
Routing Code: Descriptor Code: 4
182
nnnn
dsname
The data set name from which the procedures
procname was retrieved.
System action: The system processes the procedure.
Application Programmer Response: If the system
finds the procedure in an incorrect data set, check the
data set specified on the JCLLIB statement. Resubmit
the job.
Source: Converter
Detecting Module: IEFCNEXP
Routing Code: Descriptor Code: 4
nnnn
dsname
IEFC002I
text
183
IEFC004I IEFC006I
v The data set exists.
v The data set is cataloged.
v Change the JES2 JOBDEF parameter, CNVT_ENQ,
to WAIT.
When the error is for a PROC statement, record the
error messages and report them to your system
programmer.
System programmer response: When the error is for
a JCLLIB statement on systems in which all data sets
are not available to all processors, check that the job
has affinity to a system that can allocate the data set
during converter processing. Resubmit the job.
If the failing task is a Started Task, ensure that it is not
being started under the master subsystem. Note that
once a task is in the Subsystem Names table (either
because it was in the IEFSSNxx member of Parmlib or
because it was dynamically added), the system will
always attempt to start that task under the master
subsystem, even if SUB=MSTR is not specified on the
start command. If the task name is now in the
subsystems name table, the task can be forced not to
start under the master subsystem by specifying in the
start command to start it under the JES (SUB=JES2 or
SUB=JES3).
When the error is for a PROC statement:
v If the procedure being executed is an in-stream
PROC, which was started by a start command
specifying SUB=MSTR, change the procedure to
ensure that in-stream JCL is not used.
v If the procedure being executed is an in-stream
PROC, ensure that there is either:
at least one unitname eligible to receive VIO
datasets, or
at least one real DASD volume in unitname
SYSALLDA which is mounted STORAGE and has
available space.
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: Converter
Descriptor Code: 4
Descriptor Code: 4
IEFC006I
IEFC004I
184
IEFC007I IEFC011I
after keyword parameters. Resubmit the job.
Source: Converter
Detecting Module: IEFCNJOB
Routing Code: 2,10
Descriptor Code: 4
IEFC007I
statement
The name of the statement containing the
mutually exclusive keywords.
System action: The system ends the job, but scans
the remaining JCL statements for syntax errors.
Application Programmer Response: Determine
which of the mutually exclusive keywords is not needed
and remove it. Resubmit the job.
Source: Converter
Detecting Module: IEFCNEXC
Routing Code: 2,10
Descriptor Code: 4
IEFC010I
Source: Converter
field
Descriptor Code: 4
statement
The statement with the syntax error.
IEFC008I
IEFC009I
statement
The statement with the nesting error.
key1
key2
185
IEFC012I IEFC017I
If no loop exists, restructure the job so that it has fewer
levels of nesting. Resubmit the job.
Source: Converter
Detecting Module: IEFCNEXC
Routing Code: 2,10
Descriptor Code: 4
IEFC012I
Descriptor Code: 4
IEFC015I
ERROR IN IF STATEMENT:
INCOMPATIBLE TYPES IN A
COMPARISON
ERROR IN IF STATEMENT
Source: Converter
Descriptor Code: 4
Descriptor Code: 4
IEFC017I
IEFC014I
ERROR IN IF STATEMENT:
EXPRESSION MUST BE EVALUATED
TO TRUE OR FALSE
186
IEFC018I IEFC021I
the remaining statements for syntax errors.
Application Programmer Response: Correct the
member name specified on the INCLUDE statement.
Resubmit the job.
Source: Converter
Detecting Module: IEFCNEXP
Routing Code: 2,10
Descriptor Code: 4
statement
The name of the duplicate statement.
System action: The system ends the job, but scans
the remaining JCL statements for syntax errors.
Application Programmer Response: Check that the
job follows JCL statement rules. Resubmit the job.
Source: Converter
Detecting Module: IEFCNSOR
Routing Code: 2,10
IEFC018I
Descriptor Code: 4
IEFC021I
Source: Converter
Detecting Module: IEFCNSOR
Routing Code: 2,10
Descriptor Code: 4
IEFC019I
EXTRANEOUS PARAMETERS
SPECIFIED text
187
IEFC022I IEFC025I
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
The error was detected in the field that assigns
a value to a symbolic parameter.
Descriptor Code: 4
Source: Converter
Detecting Module: IEFCNINC
Routing Code: 2,10
IEFC024I
Explanation:
text is one of the following:
Descriptor Code: 4
ON THE cntr STATEMENT
IEFC022I
188
IEFC026I IEFC030I
remaining JCL statement for syntax errors.
Operator response: None.
Source: Converter
Routing Code: 2,10
Descriptor Code: 4
IEFC026I
Source: Converter
Routing Code: 2,10
Descriptor Code: 4
IEFC027I
Descriptor Code: 4
IEFC030I
key2
Descriptor Code: 4
statement
The name of the statement where the system
found missing keywords.
Source: Converter
IEFC028I
189
IEFC031I IEFC038I
IEFC031I
IEFC034I
Descriptor Code: 4
IEFC037I
cntr
Source: Converter
Descriptor Code: 4
IEFC033I
ERROR IN IF STATEMENT: RC
GREATER THAN MAXIMUM max
190
Descriptor Code: 4
IEFC038I
IEFC039I IEFC043I
return-code
The non-zero hexadecimal value returned from
the recall processor. For information about the
return codes, see ARCHRCAL in z/OS
DFSMShsm Managing Your Own Data.
reason-code
The management work element (MWE)
hexadecimal reason code returned from the
recall processor.
System action: None.
Source: Converter
Detecting Module: IEFCNJLI
Routing Code: 2,10
Descriptor Code: 4
IEFC039I
191
IEFC044I IEFC452I
IEFC044I
DATA SET dsname UNAVAILABLE JOB job-name WILL WAIT FOR THE
DATA SET
Descriptor Code: 4
IEFC417I
IEFC045D
Descriptor Code: 4
IEFC165I
cmd
Source: Converter
cmd
Descriptor Code: 4
Source: Converter
JOBFAIL
The error was detected on a JOB statement.
192
IEFC452I
IEFC601I IEFC605I
jobname
Descriptor Code: 4
IEFC602I
procstep
The procedure was specified in the first
operand of a START command. In this case,
either the procedure was not found in
SYS1.PROCLIB or, if found, the procedure had
an error in a JCL statement. Message IEE122I
or IEE132I will always follow this message.
The error message appears in the SYSOUT data set.
Source: Converter
Detecting Module: IEFVFA
Descriptor Code: 4
IEFC603I
Source: Converter
Descriptor Code: 4
Source: Converter
Descriptor Code: 4
IEFC605I
193
IEFC607I IEFC611I
again. 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 the SYSOUT
output for the job.
Source: Converter
Detecting Module: IEFCNGST
Routing Code: 2,10
Descriptor Code: 4
IEFC607I
Source: Converter
Detecting Module: IEFCNSOR
Routing Code: 2,10
Descriptor Code: 4
IEFC610I
194
IEFC612I IEFC616I
IEFC612I
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
procname
The name of the procedure that the system
could not find.
195
IEFC618I IEFC620I
In the message text:
parameter1
The minor keyword parameter
associated with a major keyword
parameter.
parameter2
The major keyword parameter.
IN THE SYMBOLIC PARAMETER
The error was detected in the symbolic
parameter.
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
The error was detected in the field that assigns
a value to a symbolic parameter.
IN THE parameter OVERRIDE FIELD
The error was detected in an override field.
In the message text:
parameter
An override keyword parameter on an
EXEC statement.
System action: The system ends the job, issues
messages about the job, and scans the remaining JCL
statements for syntax errors.
Application Programmer Response: Correct the
subparameter and submit the job again.
System programmer response: Obtain the SYSOUT
output for the job. Look at the messages in the job log.
If the JOB statement did not specify MSGLEVEL=(1,1),
specify it and run the job again.
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: Converter
Detecting Module: IEFCNEXC
Routing Code: 2,10
Descriptor Code: 4
text
IEFC618I
196
IEFC621I IEFC622I
parameter2
The major keyword
parameter.
IN THE SYMBOLIC PARAMETER
The error was detected in the
symbolic parameter.
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
The error was detected in the field
that assigns a value to a symbolic
parameter.
IN THE parameter OVERRIDE FIELD
The error was detected in an override
field. In the message text:
parameter
An override keyword
parameter on an EXEC
statement.
System action: The system ends the job. The system
scans the remaining job control statements for syntax
errors. The system issues messages about the job to
the job log.
Application Programmer Response: Change any
incorrect characters, and submit the job again.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Converter
Detecting Module: IEFCNEXC
Routing Code: 2,10
Descriptor Code: 4
IEFC621I
197
IEFC624I
parameter1
The minor keyword parameter
associated with a major keyword
parameter.
parameter2
The major keyword parameter.
IN THE SYMBOLIC PARAMETER
The error was detected in the symbolic
parameter.
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
The error was detected in the field that assigns
a value to a symbolic parameter.
IN THE parameter OVERRIDE FIELD
The error was detected in an override field.
In the message text:
parameter
An override keyword parameter on an
EXEC statement.
System action: The system ends the job. The system
scans the remaining job control statements for syntax
errors. The system issues messages about the job to
the job log.
Application Programmer Response: Correct the
error and submit the job again.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Converter
Detecting Module: IEFCNGST
Routing Code: 2,10
Descriptor Code: 4
IEFC624I
198
IEFC625I IEFC626I
Descriptor Code: 4
IEFC625I
Source: Converter
parameter
The last correctly specified keyword
parameter preceding the error.
199
IEFC627I
IN THE SYMBOLIC PARAMETER
The error was detected in the symbolic
parameter.
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
The error was detected in the field that assigns
a value to a symbolic parameter.
IN THE parameter OVERRIDE FIELD
The error was detected in an override field.
In the message text:
parameter
An override keyword parameter on an
EXEC statement.
System action: The system ends the job. The system
scans the remaining job control statements for syntax
errors. The system issues messages about the job to
the job log.
Application Programmer Response: If the statement
contains any incorrect characters, correct it. Submit the
job again.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Converter
Detecting Module: IEFCNEXC
Routing Code: 2,10
Descriptor Code: 4
IEFC627I
200
cntr
IEFC628I IEFC629I
IEFC628I
201
IEFC630I
parameter2
The major keyword parameter.
IN THE SYMBOLIC PARAMETER
The error was detected in the symbolic
parameter.
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
The error was detected in the field that assigns
a value to a symbolic parameter.
IN THE parameter OVERRIDE FIELD
The error was detected in an override field.
In the message text:
parameter
An override keyword parameter on an
EXEC statement.
System action: The system ends the job. The system
scans the remaining job control statements for syntax
errors. The system issues messages about the job to
the job log.
Application Programmer Response: If the statement
contains any incorrect characters, correct it. Submit the
job again.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Converter
Detecting Module: IEFCNCMD
Routing Code: 2,10
Descriptor Code: 4
IEFC630I
202
IEFC632I IEFC640I
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: Converter
Source: Converter
Detecting Module: IEFCNGST
IEFC640I
parameter
The last correctly specified keyword
parameter preceding the error.
203
IEFC641I IEFC642I
IN THE parameter OVERRIDE FIELD
The error was detected in an override field.
In the message text:
parameter
An override keyword parameter on an
EXEC statement.
parameter1
The minor keyword parameter
associated with a major keyword
parameter.
parameter2
The major keyword parameter.
IN THE SYMBOLIC PARAMETER
The error was detected in the symbolic
parameter.
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
The error was detected in the field that assigns
a value to a symbolic parameter.
IN THE parameter OVERRIDE FIELD
The error was detected in an override field.
In the message text:
parameter
An override keyword parameter on an
EXEC statement.
System action: The system ends the job. The system
scans the remaining job control statements for syntax
errors and issues messages about the job to the job
log.
Application Programmer Response: Correct the
parameter and submit the job again.
System programmer response: Look at the
messages in the job log. If the JOB statement did not
specify MSGLEVEL=(1,1), specify it and run the job
again. 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 the SYSOUT
output for the job.
Source: Converter
parameter
The last correctly specified keyword
parameter preceding the error.
204
IEFC646I
parameter
The last correctly specified keyword
parameter preceding the error.
ON THE cntr STATEMENT
The error was detected before any keyword
parameters were processed. For example, an
error was detected in the name field of a
statement.
cntr
205
IEFC647I IEFC650I
System action: The system ends the job. The system
scans the remaining job control statements for syntax
errors and issues messages about the job to the job
log.
parameter1
The minor keyword parameter
associated with a major keyword
parameter.
parameter2
The major keyword parameter.
206
IEFC651I
IN THE parameter FIELD
The keyword must be followed by an equal
sign to be considered correctly specified.
In the message text:
parameter
The last correctly specified keyword
parameter preceding the error.
ON THE cntr STATEMENT
The error was detected before any keyword
parameters were processed. For example, an
error was detected in the name field of a
statement.
cntr
Descriptor Code: 4
IEFC651I
parameter1
The minor keyword parameter
associated with a major keyword
parameter.
parameter2
The major keyword parameter.
IN THE SYMBOLIC PARAMETER
The error was detected in the symbolic
parameter.
Note: A symbolic parameter consists of a
single ampersand (&) followed by a
maximum of seven alphanumeric (A
through Z and 0 through 9) and national
(@, #, $) characters. The first character
after the ampersand must be alphabetic
or national, that is, it cannot be a
number.
IN THE VALUE FIELD OF THE SYMBOLIC
PARAMETER
The error was detected in the field that assigns
a value to a symbolic parameter.
IN THE parameter OVERRIDE FIELD
The error was detected in an override field.
In the message text:
parameter
An override keyword parameter on an
EXEC statement.
System action: The system ends the job. The system
scans the remaining job control statements for syntax
207
IEFC652I IEFC654I
IN THE SYMBOLIC PARAMETER
The error was detected in the symbolic
parameter.
IEFC653I
parameter
An override keyword parameter on an
EXEC statement.
Source: Converter
Detecting Module: IEFCNJOB
Routing Code: 2,10
Descriptor Code: 4
IEFC652I
Source: Converter
Detecting Module: IEFCNGST
Routing Code: 2,10
Descriptor Code: 4
| IEFC654I
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source: Converter
| Detecting Module: IEFCNDD
| Routing Code: 2,10
| Descriptor Code: 4
208
IEFC657I IEFC663I
IEFC657I
INVALID LABEL
Source: Converter
Detecting Module: IEFCNGST
Routing Code: 2,10
Descriptor Code: 4
IEFC663I
Descriptor Code: 4
IEFC660I
209
IEFC665I IEFC678I
contact the IBM Support Center. Provide the SYSOUT
output for the job.
Source: Converter
Source: Converter
Descriptor Code: 4
IEFC665I
IEFC677I
Source: Converter
Detecting Module: IEFCNISP
Routing Code: 2,10
Descriptor Code: 4
jobname
The name of the job.
IEFC668I
Descriptor Code: 4
IEFC678I
210
IEFC679I IEFC690I
contact the IBM Support Center. Provide the SYSOUT
output for the job.
IEFC683I
Source: Converter
Detecting Module: IEFCNGST
Routing Code: 2,10
Descriptor Code: 4
IEFC679I
{CONVERTER | INTERPRETER ]
TERMINATED DUE TO abendcde
ABEND REASON=reason-code
SCHEDULING ENVIRONMENT
schenvname DOES NOT EXIST IN THE
WLM SERVICE DEFINITION
schenvname
The name of the scheduling environment.
System action: The system ends the job.
Source: Converter
Source: Converter
Descriptor Code: 4
211
IEFC691I IEFC746I
IEFC691I
Source: Converter
ssysname
The name of the subsystem.
IEFC745I
212
IEFC747I IEFC822I
IEFC747I
Descriptor Code: 4
ssysname
The name of the subsystem.
IEFC750I
Descriptor Code: 4
IEFC822I
IEFC748I
BEFORE
The keyword came before the first EXEC
statement.
keyword
The incorrectly specified keyword.
213
214
RECOVERY FAILURE
The system was unable to establish recovery
to protect the processing required to initialize
the sysplex-wide notification function.
SYSTEM ERROR
A system error other than those described
above prevented the initialization of the
IEFSCHAS address space.
System action: The system continues processing.
However:
Routing Code: 2
Descriptor Code: 4
IEFE002I
215
216
Source: Converter/Interpreter
Detecting Module: IEFITRL
Routing Code: 11
Descriptor Code: 6
IEFI001
217
218
IEFJ002I
line-number
line-number
219
IEFJ003I IEFJ006I
or more keyword format subsystem definitions, convert
all the subsystem definitions to the same format or
move all the definitions of one type of format to another
IEFSSNxx member. IBM recommends that you convert
all subsystem definitions to the keyword format.
Source: Subsystem Interface (SSI)
Detecting Module: IEFJSIN2
Descriptor Code: 4
IEFJ005I
subname
The subsystem name.
System action: The system ignores the duplicate
subsystem name. The system does not build a
subsystem communication vector table (SSCVT) for the
duplicate subsystem name.
System programmer response: Determine why the
same subsystem name subname was used more than
once.
If the subsystem subname is not properly initialized and
is needed for system processing, correct the error so
that the error does not occur again during subsequent
IPLs.
Source: Subsystem Interface (SSI)
Detecting Module: IEFJPACT, IEFJSINT, IEFJSIN2
subname
The subsystem
name.
initialization-routine
Descriptor Code: 4
Descriptor Code: 4
SUBSYSTEM subname NOT
INITIALIZED - initialization-routine NOT
FOUND
IEFJ006I
The subsystem
name.
initialization-routine
220
Descriptor Code: 5
IEFJ004I
Routing Code: -
IEFJ003I
IEFJ007I IEFJ023I
Descriptor Code: 4
IEFJ007I
IEFJ022I
subname
The subsystem name.
System action: The system continues processing.
Operator response: None.
System programmer response: None.
Source: Subsystem Interface (SSI)
Detecting Module: IEFJPACT
Routing Code: Descriptor Code: 5
IEFJ023I
memname
subcmd
pri-memname
221
IEFJ024I IEFJ027I
Operator response: Check the other message that
accompanies this message and take the appropriate
action.
Routing Code: -
Routing Code: -
Descriptor Code: 5
Descriptor Code: 5
IEFJ024I
IEFJ026I
subname
The subsystem name.
subname
The subsystem name.
Descriptor Code: 5
IEFJ025I
Routing Code: -
222
IEFJ028I IEFJ031I
v The module was found, but it was not
APF-authorized.
INSUFFICIENT STORAGE
IEFJ029I
subname
The subsystem name.
Routing Code: -
Descriptor Code: 5
IEFJ028I
subname
The subsystem name.
223
IEFJ032I IEFJ037I
SETSSI DEACTIVATE command specifying the correct
subsystem name.
IEFJ035I
subname
The subsystem name.
System action: The system does not process the
command.
Operator response: Notify the system programmer.
System programmer response: Provide a vector
table using the IEFSSVT create service.
Source: Subsystem Interface (SSI)
Routing Code: -
Descriptor Code: 5
IEFJ034I
Routing Code: -
subname
The subsystem name.
Descriptor Code: 5
224
IEFJ051I IEFJ100I
System programmer response: Use the IEFSSVT
macro to create the subsystems vector tables. This
enables the SSI to locate an eligible vector table that
can reactivate the subsystem following deactivation by
the SETSSI command.
Routing Code: -
Routing Code: -
Descriptor Code: 5
Descriptor Code: 5
IEFJ100I
IEFJ051I
Explanation:
SUBSYS=subsysname[(PRIMARY)]
DYNAMIC=ddd
STATUS=ssssssss
[FUNC=function-code-list]
[function-code-list]
This message displays information about all subsystems
defined to the system when the operator enters the
DISPLAY SSI command. The information is displayed in
broadcast order; that is, the information for the
subsystem which is first in the broadcast order (the
order in which broadcast requests are processed)
appears first in the display.
The first line of the message always appears.
In the first line of the message text:
hh.mm.ss
The hour, minute, and second at which the
system processed the display command.
00.00.00 appears in this field if the time-of-day
(TOD) clock is not working.
id
225
IEFJ200I
added using one of the dynamic SSI services.
ddd is one of the following:
YES
NO
STATUS=ssssssss
The status of the subsystem. ddd is one of the
following:
ACTIVE
The subsystem is active. It accepts
function requests directed to it by the
SSI.
INACTIVE
The subsystem is inactive. It does not
accept function requests directed to it
by the SSI.
COMMANDS=cccccc
Indication of whether or not the subsystem
accepts dynamic SSI commands. A dynamic
subsystem is given the option of enabling or
disabling the dynamic SSI commands (with the
exception of the ADD command). cccccc is one
of the following:
ACCEPT
The subsystem accepts dynamic SSI
commands.
REJECT
The subsystem rejects dynamic SSI
commands (with the exception of the
ADD command).
N/A
226
xxx
IEH102I
dsname
The data set name.
System action: The request is ignored. The return
code is 8.
Application Programmer Response: Probable user
error. Ensure that the data set name specified is correct.
If the name is correct, insert a LISTVTOC FORMAT
statement specifying the data set name and volume; the
true data set information will then 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
and all printed output and output data sets related to
the problem.
Source: DFSMSdfp
IEH105I
227
IEH106I IEH110I
Application Programmer Response: Ensure that the
node point specified in the LISTCTLG statement is
correct, or that no inconsistencies occur in the catalog
structure.
Do not define devices containing CVOLs as dynamic
devices.
System programmer response: Run Data Facility
Data Set Services (dump to printer) for the catalog data
set, and save the output. 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
program listing for the job.
Source: DFSMSdfp
IEH106I
228
Source: DFSMSdfp
IEH108I
IEH112I IEH115I
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 all printed output and output data sets related to
the problem.
Source: DFSMSdfp
IEH112I
IEH114I
229
IEH117I IEH204I
IEH117I
xxxx
Source: DFSMSdfp
yyyy
IEH203I
Source: DFSMSdfp
IEH201I
230
IEH205I IEH209I
IEH205I
INFORMATION IN CONTROL
STATEMENT IS {REDUNDANT|NOT
SUFFICIENT}
xxxx
yyyy
The condition.
Source: DFSMSdfp
IEH207I
yyyy
The condition.
dsname
ser
231
IEH210I IEH214I
reporting data bases for a fix for the problem. If no fix
exists, contact the IBM Support Center. Provide the JCL
and the program listing for the job.
IEH212I
Source: DFSMSdfp
IEH210I
Source: DFSMSdfp
IEH211I
232
CONTINUATION STATEMENT
EXPECTED - REQUESTS CANNOT BE
SERVICED.
IEH215I IEH219I
Source: DFSMSdfp
IEH215I
Source: DFSMSdfp
IEH218I
233
IEH220A IEH223I
IEH220A
IEH222I
Source: DFSMSdfp
IEH221I
Source: DFSMSdfp
IEH223I
234
IEH224I IEH228I
Application Programmer Response: Probable user
error. Allocate a PASSWORD data set, and resubmit the
job. Run IEHLIST to list the VTOC (FORMAT mode) of
the system residence volume. Have the resulting listing
available.
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 program listing for the job.
Source: DFSMSdfp
IEH224I
Source: DFSMSdfp
IEH226I
235
IEH229I IEH301I
incorrectly specified in the utility control statement.
System action: The request is ignored. The return
code is 8.
Application Programmer Response: Probable user
error. Resubmit the ignored request and supply a valid
password.
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 program listing for the job. If attempting to add,
delete, or replace an entry in the PASSWORD data set,
use the LIST utility statement to list the entry in the
PASSWORD data set.
Source: DFSMSdfp
IEH229I
236
IEH302I IEH307I
IEH302I
IEH305I
SUBORDINATE REQ-SKIPPED
237
IEH308I IEH315I
problem and the source input for the job.
Source: DFSMSdfp
IEH308I
SYNTAX ERROR
LENGTH ERROR
238
INCOMPLETE REQUEST
IEH316I IEH322I
System action: The request is ignored. The return
code is 8.
Application Programmer Response: If the data set is
not cataloged, ensure that the FROM keyword is
included on the MOVE or COPY statement. Also, make
sure that a DD statement for the FROM device exists
and is compatible with the utility control information.
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 all
printed output and output data sets related to the
problem and the source input for the job.
Source: DFSMSdfp
IEH316I
IEH320I
dsname
The data set name.
System action: The request is ignored. The return
code is 8.
Application Programmer Response: Probable user
error. Correct the error and resubmit 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 all
printed output and output data sets related to the
problem and the source input for the job.
Source: DFSMSdfp
IEH321I
Source: DFSMSdfp
IEH319I
239
IEH323I IEH327I
dsname
The data set name.
System action: The request is ignored. The return
code is 8.
Operator response: If requested by the system
programmer, obtain a stand-alone dump.
Application Programmer Response: Ensure that the
input data set 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
source input for the job.
Source: DFSMSdfp
IEH323I
dsname
The data set name.
System action: The request is ignored. The return
code is 8.
Application Programmer Response: Retry the
operation. If the operation fails a second time If the
operation fails a second time with this same error
message, in all probability the failure is due to a
hardware error. Ensure the quality of the hardware
medium on which the dataset resides. Resubmit 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 all
printed output and output data sets related to the
problem and the source input for the job.
Source: DFSMSdfp
dsname
The data set name.
System action: The request is ignored. The return
code is 8.
Application Programmer Response: Retry the
operation. If the operation fails a second time If the
operation fails a second time with this same error
message, in all probability the failure is due to a
hardware error. Ensure the quality of the hardware
medium on which the dataset resides. Resubmit 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 all
printed output and output data sets related to the
problem and the source input for the job.
Source: DFSMSdfp
IEH327I
IEH325I
240
IEH328I IEH332I
that the source member be re-created and recopied.
Check for an end-of-file record embedded within the
source member.
Submit IEHLIST for both the source and receiving data
sets with the LISTPDS option specified. Submit IEHLIST
for both the source and receiving data sets with the
LISTVTOC option specified (DUMP format). Submit
Data Facility Data Set Services to dump the source data
set to SYSPRINT or to tape.
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 all
printed output and output data sets related to the
problem and the source input for the job.
Source: DFSMSdfp
IEH328I
Source: DFSMSdfp
IEH329I
Source: DFSMSdfp
Chapter 7. IEH Messages
241
IEH333I IEH346I
IEH333I
Source: DFSMSdfp
IEH336I
AN UNCORRECTABLE ERROR
OCCURRED WHILE READING DATA
SET dsname
dsname
Source: DFSMSdfp
IEH334I
242
IEH348I IEH354I
control volumes are correctly connected to each other.
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 all
printed output and output data sets related to the
problem and the source input for the job.
Source: DFSMSdfp
IEH348I
Source: DFSMSdfp
IEH349I
Source: DFSMSdfp
IEH354I
xxxx
ser
243
IEH356I IEH362I
return-code
The return code for VSAM catalog
management.
System action: The request is ignored. Return code is
4.
Application Programmer Response: Probable user
error. To interpret the return code, refer to the
explanation of message IDC3009. Correct any errors
and resubmit 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 program listing for the job.
Source: DFSMSdfp
IEH356I
IEH358I
Source: DFSMSdfp
244
IEH363I IEH366I
dsname
The data set name.
System action: Processing continues with the next
function to be performed. The return code is 4.
Application Programmer Response: 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. 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 source input for the job.
Source: DFSMSdfp
IEH363I
dsname
The data set name.
System action: Processing continues with the next
function to be performed. The return code is 4.
Application Programmer Response: Scratch the
data set, if required.
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 all
printed output and output data sets related to the
problem and the source input for the job.
Source: DFSMSdfp
IEH366I
245
IEH367I IEH374I
IEH367I
Source: DFSMSdfp
IEH368I
Source: DFSMSdfp
IEH374I
246
IEH375I IEH381I
IEH375I
dsname
The data set name.
IEH376I
xxxx
Source: DFSMSdfp
IEH381I
ERROR ENCOUNTERED IN
SCRATCHING WORK FILES
247
IEH383I IEH390I
printed output and output data sets related to the
problem and the source input for the job.
Source: DFSMSdfp
Source: DFSMSdfp
IEH388I
IEH383I
Source: DFSMSdfp
IEH389I
Source: DFSMSdfp
IEH385I
IEH390I
248
IEH401I IEH405I
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 all
printed output and output data sets related to the
problem and the source input for the job.
Source: DFSMSdfp
IEH403I
IEH401I
xxxx
IEH402I
xxxx
Source: DFSMSdfp
Chapter 7. IEH Messages
249
IEH406I IEH409I
dsname
The data set name.
xxxx
Source: DFSMSdfp
Source: DFSMSdfp
IEH408I
dsname
IEH406I
Source: DFSMSdfp
Source: DFSMSdfp
IEH409I
dsname
IEH407I
250
IEH410I IEH414I
printed output and output data sets related to the
problem and the source input for the job.
Source: DFSMSdfp
IEH410I
IEH412I
251
IEH415I IEH418I
dsname
The data set name.
xxxx
Source: DFSMSdfp
Source: DFSMSdfp
IEH417I
dsname
IEH415I
Source: DFSMSdfp
Source: DFSMSdfp
IEH418I
dsname
IEH416I
252
IEH419I IEH423I
printed output and output data sets related to the
problem and the source input for the job.
Source: DFSMSdfp
IEH419I
IEH421I
253
IEH424I IEH427I
dsname
The data set name.
xxxx
Source: DFSMSdfp
Source: DFSMSdfp
IEH426I
dsname
IEH424I
Source: DFSMSdfp
Source: DFSMSdfp
IEH427I
dsname
IEH425I
254
IEH428I IEH432I
printed output and output data sets related to the
problem and the source input for the job.
Source: DFSMSdfp
IEH428I
IEH430I
255
IEH433I IEH440I
dsname
xxxx
Source: DFSMSdfp
IEH440I
IEH435I
256
257
IEH460I IEH471I
printed output and output data sets related to the
problem and the source input for the job.
Source: DFSMSdfp
IEH460I
dsname
Source: DFSMSdfp
IEH462I
258
IEH472I IEH476I
IEH472I
259
IEH477I IEH602I
IEH477I
yy
nnnK
12
INVALID KEYWORD
Source: DFSMSdfp
IEH479I
260
Explanation
IEH603I IEH607I
and all printed output and output data sets related to
the problem.
IEH605I
Source: DFSMSdfp
IEH603I
261
IEH608I IEH613I
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 all printed output and output data sets related to
the problem.
Source: DFSMSdfp
IEH608I
Source: DFSMSdfp
IEH613I
IEH610I
262
IEH614I IEH620I
Application Programmer Response: Probable user
error. Either specify LABTYPE=AL or remove
ACCESS=xxx.
Source: DFSMSdfp
IEH614I
IEH617I
Source: IEHINITT
IEH619I
Source: DFSMSdfp
IEH616I
dddddddd
The DDNAME.
System action: None.
User response: Record the return code and supply it
to the appropriate IBM support personnel.
Source: IEHINITT
IEH620I
263
IEH621I IEH627I
In the message text:
func
return_code
reason_code
Source: IEHINITT
IEH621I
return-code
reason-code
Source: DFSMSdfp
IEH626I
X'80'
Error on call to CSVDYNEX.
X'40'
An exit routine abended.
Source: IEHINITT
X'20'
Invalid return code from exit routine (not 0, 4,
8).
IEH623E
264
X'10'
Invalid reason code from exit routine (not 0, 4).
X'08'
A previous exit indicated that the volume is not
to be labeled.
IEH628I IEH629I
X'04'
Conflicts in the results from calls to exits have
been encountered.
X'10'
Failure in internal processing not related to
dynamic exits services.
X'02'
At least one exit routine returned rc=0 with a
modified volser and either other exit routines
returned rc=0 without modifying the volser, or
the modified volsers didnt match.
X'08'
Operator replied to skip labeling the volume.
X'01'
Two or more exits requested that the volser be
changed, but the changed volsers dont match.
Byte 2 xx
X'80'
An exit routine requested no OWNERID
change, but another exit requested an
OWNERID change.
X'40'
Two or more exits requested that the
OWNERID be changed, but the changed
OWNERIDs dont match.
X'20'
An exit routine requested no ACCODE change,
but another exit requested ACCODE change.
X'10'
Two or more exits requested that the ACCODE
be changed, but the changed ACCODEs dont
match.
X'08'
A conflict in the return codes returned by the
exit routines was detected. One routine
returned a 0 and another returned an 8.
X'04'
Invalid volser character supplied by an exit
routine.
X'02'
Invalid OWNERID character supplied by an exit
routine.
X'01'
Invalid ACCODE character supplied by an exit
routine.
Byte 3 yy
X'80'
There is a conflict in rc=8 reason code
processing. An exit routine returned rsn=4,
requesting remount and another returned
rsn=0, indicating dont label the tape at all.
X'40'
An exit routine requested remount but no new
volser was provided.
X'20'
Conflict in remount volser value. New volser
values dont match.
X'04'
Mounted volume is file protected.
X'02'
Reserved.
X'01'
Reserved.
Byte 4 zz
X'FF'
Reserved.
System action: Processing will continue with next
INITT control card, if possible. Conditions such as
failures in the CSVDYNEX facility will prevent
continuation.
Operator response: None.
System programmer response: A System
Programmer may need to investigate some failures,
particularly those associated with the CSVDYNEX
facility itself. Other failures that may require such
attention would be those associated with conflicts
between exit routines.
Source: DFSMSdfp
IEH628I
265
IEH924I
failed. The return code and reason code from the call
are displayed.
System action: Processing terminates.
Operator response: None.
System programmer response: The cause of the
failure in CSVDYNEX must be determined and resolved.
Source: DFSMSdfp
IEH924I
266
(ctlstte)
Source: DFSMSdfp
Detecting Module: HEWLFSCN
Routing Code: Note 11
Descriptor Code: -
IEW0012
267
IEW0053 IEW0083
Explanation: END card is probably mispunched.
System action: The incorrect item is ignored.
Application Programmer Response: Probable user
error. Check the input object modules for completeness
and proper sequence. If necessary, either (1) recreate
any module that has been in card form, or (2) isolate
the incorrect module by running the linkage editor with
the NCAL option specified, using the NAME control
statement for each input module. Diagnostic IEW0043
should recur and isolate the incorrect module. Recreate
the module, and rerun the step.
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
output used to isolate the module.
Source: DFSMSdfp
Detecting Module: HEWLFENT
Routing Code: Note 11
Descriptor Code: IEW0053
268
IEW0093 IEW0123
was used to place the control section containing the
entry point in another segment, or (2) the symbol
specified on the END statement is incorrect.
Source: DFSMSdfp
Descriptor Code: -
Source: DFSMSdfp
IEW0093
Source: DFSMSdfp
Source: DFSMSdfp
Descriptor Code: -
IEW0102
IEW0123
269
IEW0132 IEW0152
Application Programmer Response: Probable user
error. Check other messages issued for cause of error
(that is, incorrect input from object module). Ensure that
at least one control section appears in the input and is
not deleted by the REPLACE control 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 source input, the source program listing for the
job, and all printed output and output data sets related
to the problem.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: IEW0132
IEW0143
ERROR - NO TEXT.
Descriptor Code: -
IEW0152
Descriptor Code: -
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: HEWLFADA
270
IEW0161 IEW0212
IEW0161
IEW0182
Source: DFSMSdfp
Detecting Module: HEWLFENS
Routing Code: Note 11
Descriptor Code: -
Source: DFSMSdfp
Detecting Module: HEWLFENS
Routing Code: Note 11
Descriptor Code: -
IEW0172
IEW0201
271
IEW0222 IEW0234
System action: The card is not processed as a
continuation, but as normal input.
Application Programmer Response: Probable user
error. Either remove the nonblank character in column
72 or insert the necessary continuation 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 all
printed output and output data sets related to the
problem.
Source: DFSMSdfp
Detecting Module: HEWLFINP
Routing Code: Note 11
Descriptor Code: IEW0222
Source: DFSMSdfp
v Make sure that the failing job step ran with the XREF
and LIST options.
272
IEW0241 IEW0264
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: HEWLFRAT, HEWLFINP,
HEWLFESD
Routing Code: Note 11
Descriptor Code: -
Similarly, the order table for this link edit overflows for
one of the following reasons:
v the table has reached its design limit of 32768 bytes;
v the table has reached the maximum number of bytes
set by the linkage editor; or
v the number of operands on the ORDER control
statement exceeds one third of either the design limit
or the limit set by the linkage editor. (Each operand
on the ORDER statement requires three bytes in the
order table.)
System action: Processing ends.
IEW0241
Source: DFSMSdfp
Descriptor Code: -
IEW0264
273
IEW0272 IEW0294
v Break down any large input module into a number of
smaller modules so that the ESD table will not reach
its design limit
v Reset the linkage editors table space by doing one
or both of the following:
Increase value1 (or decrease value2) of the SIZE
parameter (if SIZE is specified in the JCL)
Increase the region size if necessary
v Check that the input object modules are complete
and valid.
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
Routing Code: Note 11
Descriptor Code: IEW0272
274
IEW0302 IEW0342
Routing Code: Note 11
Descriptor Code: IEW0302
Source: DFSMSdfp
Descriptor Code: -
IEW0332
Descriptor Code: -
IEW0324
275
IEW0354 IEW0364
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 all printed output and output data sets related to
the problem.
Source: DFSMSdfp
Detecting Module: HEWLFINC
Routing Code: Note 11
Descriptor Code: -
IEW0354
276
IEW0374 IEW0404
and all printed output and output data sets related to
the problem.
Source: DFSMSdfp
Detecting Module: HEWLFRAT, HEWLFOUT,
HEWLFADA
Routing Code: Note 11
Descriptor Code: IEW0374
IEW0394
Source: DFSMSdfp
Source: DFSMSdfp
Descriptor Code: -
IEW0382
277
IEW0412 IEW0432
a new library; when the original library is used as input,
concatenate the new one with it; or (2) use a utility
program to copy the library, allowing for more directory
entries. Edit the member into the new library. Run the
IEHLIST utility program, using the LISTVTOC and
LISTPDS statements to print out the data set control
block and directory entries for the SYSLMOD 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 all printed output and output data sets related to
the problem.
Source: DFSMSdfp
Detecting Module: HEWLFFNL
Routing Code: Note 11
Descriptor Code: IEW0412
IEW0421
278
IEW0444 IEW0461
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 all printed output and output data sets related to
the problem.
Source: DFSMSdfp
Routing Code: Note 11
Descriptor Code: IEW0444
279
IEW0472 IEW0502
IEW0472
280
IEW0512 IEW0543
Detecting Module: HEWLFFNL
Descriptor Code: -
Descriptor Code: -
IEW0512
IEW0532
281
IEW0552 IEW0581
Source: DFSMSdfp
Detecting Module: HEWLFFNL
Routing Code: Note 11
Descriptor Code: IEW0552
IEW0564
282
IEW0594 IEW0614
Application Programmer Response: Correct the
member name on the SYSLMOD DD statement to
conform to the rules for a name on the NAME control
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 the linkage
editor output.
Source: DFSMSdfp
Detecting Module: HEWLFFNL
Routing Code: Note 11
Descriptor Code: IEW0594
283
IEW0622 IEW0642
Recreate the module, and rerun the step.
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 source input, the source program listing for the
job, and all printed output and output data sets related
to the problem.
Descriptor Code: -
Source: DFSMSdfp
Source: DFSMSdfp
Detecting Module: HEWLFRAT
IEW0622
Descriptor Code: -
284
IEW0652 IEW0682
IEW0652
Descriptor Code: -
IEW0670
Source: DFSMSdfp
Chapter 8. IEW Messages
285
IEW0694 IEW0722
IEW0694
286
IEW0731 IEW0761
Application Programmer Response: Correct the
incorrect character(s) in the ALIAS name according to
the rules above, and rerun the link edit job step.
Source: DFSMSdfp
Detecting Module: HEWLFSCN
Routing Code: Note 11
Descriptor Code: IEW0731
Descriptor Code: -
IEW0761
Source: DFSMSdfp
Detecting Module: HEWLFFNL
Routing Code: Note 11
Descriptor Code: IEW0740
Source: DFSMSdfp
Descriptor Code: -
Descriptor Code: -
287
IEW0771 IEW0801
IEW0771
IEW0791
IEW0781
288
IEW0813 IEW0984
IEW0813
Source: DFSMSdfp
IEW0844
Source: DFSMSdfp
Descriptor Code: -
Source: DFSMSdfp
IEW0824
IEW0984
289
IEW0994
Descriptor Code: IEW0994
IEW1001 - 1999
IEW1001
290
IEW1072
Source: DFSMSdfp
291
292
IEW1123
IEW1132
Descriptor Code: -
IEW1141
293
Source: DFSMSdfp
Detecting Module: HEWLLIBR
Routing Code: Note 11
IEW1204
Descriptor Code: -
IEW1182
Source: DFSMSdfp
Descriptor Code: -
294
Descriptor Code: -
IEW1214
IEW1232
Descriptor Code: -
Source: DFSMSdfp
IEW1224
295
IEW1251
296
IEW2001S IEW2012S
end, include a SYSUDUMP DD statement for the
loaded program and rerun the job.
Source: DFSMSdfp
Detecting Module: HEWLCTRL
IEW2001 - 2999
All binder messages are in the following format:
<message number> <internal code> <message text>
The internal codes are not documented because they are used for diagnostic purposes.
IEW2001S
Source: Binder
Source: Binder
IEW2008I
IEW2012S
Source: Binder
Source: Binder
297
IEW2013I IEW2105I
Detecting Module: IEWBACTL
IEW2013I
IEW2103I
Source: Binder
Detecting Module: IEWBACTL
IEW2100I
IEW2102I
298
IEW2106I IEW2112I
IEW2106I
IEW2109I
Source: Binder
Source: Binder
IEW2107I
IEW2110I
299
IEW2113I IEW2118I
Workmod-id is a number which identifies the workmod
associated with the call. Call-sequence is a
binder-generated number incremented after each API
call to the binder.
IEW2116I
Source: Binder
Detecting Module: IEWBDCTL
IEW2113I
Source: Binder
Detecting Module: IEWBDCTL
IEW2114I
300
IEW2119 IEW2124I
|
|
|
|
|
IEW2119
|
|
|
|
|
|
Source: Binder
IEW2119I
Source: Binder
Source: Binder
IEW2120I
Source: Binder
Source: Binder
Detecting Module: IEWBDCTL
301
IEW2125I IEW2131I
IEW2125I
Source: Binder
Source: Binder
IEW2130S
IEW2131I
302
IEW2132S IEW2141E
Detecting Module: IEWBDCTL
IEW2132S
INCORRECT NUMBER OF
PARAMETERS PASSED FOR
FUNCTION CALL function name .
Source: Binder
IEW2137S
Source: Binder
Source: Binder
Detecting Module: IEWBDCTL
| IEW2139I
|
|
|
|
|
|
|
Source: Binder
| Source: Binder
IEW2134S
IEW2141E
symbol-type BEGINNING
truncated_symbol IS TOO LONG. IT
CONTAINS MORE THAN number
CHARACTERS.
Description
SYMBOL
303
IEW2142E IEW2147S
SECTION
IEW2144T
SYMBOL or SECTION
The name of a control section or a
symbol within a control section.
MEMBER or ALIAS
Either a member name or an alias
name.
CLASS
LOADW LNAME
When using the Binder API, an
LNAME=parameter on an IEWBIND
FUNC=LOADW call.
STARTS ORIGIN
When using the Binder API, an
ORIGIN=parameter on an IEWBIND
FUNC=STATS call.
System action: Current request will not be processed.
User response: Correct the input.
Source: Binder
Detecting Module: IEWBDSYM, IEWBDVAL,
IEWBOLST, IEWBOVAL
IEW2142E
IEW2145S
IEW2143S
304
IEW2149S IEW2160S
using the binder application programming interface,
including the acceptable values for the indicated
parameter, and correct the calling program.
Source: Binder
Source: Binder
Detecting Module: IEWBDCAL
IEW2155S
IEW2159S
Source: Binder
Detecting Module: IEWBDCAL
IEW2154S
305
IEW2166S IEW2178S
Detecting Module: IEWBDVAL
IEW2166S
IEW2174S
Source: Binder
Source: Binder
IEW2172S
IEW2176S
Source: Binder
Detecting Module: IEWBDVAL
Source: Binder
IEW2173S
306
IEW2185S IEW2202W
Source: Binder
IEW2192E
Source: Binder
Source: Binder
IEW2186S
IEW2200W
IEW2189E
307
IEW2203E IEW2212S
IEW2203E
Source: Binder
Detecting Module: IEWBDADD
IEW2209E
Source: Binder
Source: Binder
Detecting Module: IEWBDADD
IEW2205W
IEW2210S
IEW2211S
Source: Binder
IEW2207E
IEW2212S
Source: Binder
IEW2208S
308
IEW2213S IEW2229E
IEW2213S
IEW2220S
Source: Binder
Source: Binder
IEW2217S
IEW2221S
Source: Binder
Source: Binder
Detecting Module: IEWBDCAL
IEW2219S
IEW2229E
309
IEW2230S IEW2240S
issued during the processing of the module and correct
the indicated problems.
Source: Binder
Detecting Module: IEWBDCAL
Source: Binder
Detecting Module: IEWBDCAL
IEW2230S
IEW2235S
Source: Binder
IEW2232S
Source: Binder
Detecting Module: IEWBDCAL
IEW2238W
Source: Binder
Detecting Module: IEWBDCAL
IEW2234S
310
Source: Binder
Detecting Module: IEWBDCAL
IEW2240S
IEW2241E IEW2254S
System action: The PUTD request will not be
processed.
User response: Correct section name or change
NEWSECT to YES.
Source: Binder
Detecting Module: IEWBDCAL
|
|
IEW2241E
|
|
|
|
Source: Binder
IEW2252W
IEW2250I
Source: Binder
Source: Binder
Detecting Module: IEWBDINT
IEW2251S
IEW2254S
Source: Binder
Source: Binder
Detecting Module: IEWBDINT
311
IEW2255S IEW2274E
IEW2255S
IEW2270E
SPECIFICATION OF OPTION
option-name IS NOT ALLOWED WHEN
WORKMOD INTENT IS ACCESS.
Source: Binder
Source: Binder
IEW2257E
IEW2273E
Source: Binder
Source: Binder
IEW2258S
IEW2274E
PARAMETER NUMBER
parameter-number, SPECIFIED IN THE
exit-name EXIT, IS INCORRECT.
312
IEW2275E IEW2293W
IEW2275E
IEW2290E
IEW2291E
Source: Binder
Source: Binder
Detecting Module: IEWBOLST
IEW2277E
IEW2292E
Explanation: Either:
v An option name which requires a value was used, but
no value was given.
v The option specification used syntax indicating that a
value would be supplied, but none was given.
v In the case of a few options whose value is never
passed to IEWBIND, the value supplied is invalid for
this option. Examples: FETCHOPT or FETCHOPT=()
or NOCALL= or OPTIONS(INVALIDDD)
v The option specified is a valid option, but is not valid
as an option supplied in the options list in an API call.
For this last possibility, the option probably can be
supplied in the PARMS parameter.
System action: The option specification is ignored.
Processing continues.
User response: Correct the input.
Source: Binder
Detecting Module: IEWBOLST
IEW2293W
313
IEW2294E IEW2304S
Source: Binder
IEW2294E
IEW2301E
Source: Binder
Source: Binder
IEW2295E
Source: Binder
IEW2296W
IEW2300S
IEW2304S
Source: Binder
Detecting Module: IEWBINCL
314
IEW2305E IEW2312E
Source: Binder
Source: Binder
Detecting Module: IEWBIMOD
IEW2305E
IEW2309E
Source: Binder
IEW2310E
315
IEW2313E IEW2327E
System action: The current input module will be
discarded.
IEW2322I
sequence-number record
Source: Binder
Source: Binder
Detecting Module: IEWBICSI
IEW2325E
Source: Binder
Source: Binder
Detecting Module: IEWBICSI
IEW2321E
316
IEW2327E
INVALID control-statement-operand
VALUE value FOUND IN statement-name
CONTROL STATEMENT.
IEW2328E IEW2342E
IEW2328E
IEW2335E
IEW2332E
Source: Binder
Detecting Module: IEWBICPA, IEWBICPB
IEW2339S
Source: Binder
IEW2333E
Source: Binder
317
IEW2343E IEW2349E
compile unit list parameter, one record of each of all
compile units will be returned.
Source: Binder
Source: Binder
IEW2343E
IEW2346E
IEW2344E
IEW2347E
318
IEW2350E IEW2353E
references could not be relocated.
System action: The contents of these adcons in the
output data buffer will be set to hexadecimal Fs.
User response: To avoid the error message, remove
the cross-segment references in the source code from
which the target module was generated.
Source: Binder
Detecting Module: IEWBFGIT
IEW2350E
IEW2351E
Source: Binder
IEW2352E
319
IEW2354E IEW2358E
v 250012 - The ER ESD record for an imported symbol
indicates that it is a reference to a linkage descriptor,
but the PR ESD record that represents the descriptor
was not found.
v 250013 - The target of a relative immediate
instruction is a weak external reference.
v 250014 - The target of a relative immediate
instruction is a reference that is marked as
dynamically resolved (it is resolved from a DLL during
execution).
System action: The input load module or program
object containing this section will not be added to
workmod.
User response: The input load module or program
object containing this section is invalid. Either obtain a
valid copy or rebuild the module.
Source: Binder
Detecting Module: IEWBFVER
IEW2354E
IEW2356E
Source: Binder
IEW2358E
320
IEW2359E IEW2366W
object containing this section is invalid. Either obtain a
valid copy or recreate the module from the source code.
Source: Binder
IEW2359E
Source: Binder
Source: Binder
Source: Binder
IEW2361E
IEW2365W
Source: Binder
Source: Binder
IEW2366W
321
IEW2367W IEW2374E
Detecting Module: IEWBFESD
IEW2367W
IEW2371W
Source: Binder
Source: Binder
IEW2372E
IEW2369W
IEW2373E
IEW2374E
322
IEW2375S IEW2384E
Source: Binder
IEW2380E
IEW2378W
IEW2384E
323
IEW2385E IEW2392E
IEW2385E
Source: Binder
Source: Binder
Detecting Module: IEWBFCP2
IEW2386E
IEW2390E
IEW2387E
IEW2388E
Source: Binder
324
IEW2393E IEW2399W
Source: Binder
IEW2396E
IEW2397W
Source: Binder
Detecting Module: IEWBFESD
IEW2394E
A REQUEST TO CHANGE OR
REPLACE LABEL old-name TO
new-name WAS RECEIVED, AND
new-name WAS AN EXISTING LABEL.
A REQUEST TO CHANGE OR
REPLACE SECTION old-section-name
TO new-section-name WAS RECEIVED,
AND new-section-name WAS AN
EXISTING SECTION.
IEW2395E
Source: Binder
Detecting Module: IEWBEREN
IEW2399W
A REQUEST TO CHANGE OR
REPLACE LABEL old-name TO
new-name WAS RECEIVED, AND
new-name WAS AN EXISTING
SECTION.
325
IEW2400I IEW2407E
deleted. Label old name is changed to new name.
User response: Check that the result of the system
action is what was desired.
IEW2404E
Source: Binder
IEW2400I
Source: Binder
Detecting Module: IEWBEEXP
IEW2405E
IEW2401W
A REQUEST TO CHANGE OR
REPLACE SECTION old-section-name
TO new-section-name WAS RECEIVED,
AND new-section-name WAS AN
EXISTING LABEL.
Source: Binder
Detecting Module: IEWBEEXP
IEW2406W
Source: Binder
Detecting Module: IEWBEREN
IEW2403W
IEW2407E
Source: Binder
Source: Binder
326
IEW2408E IEW2438E
IEW2408E
Source: Binder
Source: Binder
IEW2410W
Source: Binder
327
IEW2439E IEW2448W
correct the source code by changing the resident class
of the part.
Source: Binder
Detecting Module: IEWBBIPT
IEW2441I
IEW2439E
328
IEW2449E IEW2454W
unpredictable. Therefore the requests have been
discarded.
Source: Binder
Source: Binder
IEW2449E
IEW2452E
Source: Binder
IEW2453E
Source: Binder
ERRORS ENCOUNTERED
ATTEMPTING TO INCLUDE MEMBER
member-name DURING AUTOCALL.
Source: Binder
| IEW2454W
|
|
Source: Binder
|
|
|
|
|
329
IEW2455W IEW2459W
| 3. Variables and linkage blocks in merge classes such
as the Writable Static Area (WSA)
|
|
|
Source: Binder
Source: Binder
IEW2456E
IEW2458W
Source: Binder
3.
330
IEW2460E IEW2467E
IEW2460E
Source: Binder
Detecting Module: IEWBBCDS
IEW2464E
Source: Binder
Source: Binder
Detecting Module: IEWBBIND
IEW2461I
IEW2465E
331
IEW2468E IEW2473E
System action: The symbol is unresolved. Processing
continues.
Source: Binder
Detecting Module: IEWBBARN, IEWBBCAD
IEW2470E
Source: Binder
IEW2471E
Source: Binder
332
IEW2474I IEW2480W
V-type address constants in an overlay program.
IEW2477W
Source: Binder
Detecting Module: IEWBBCOV
IEW2474I
IEW2475W
Source: Binder
Detecting Module: IEWBBCOV
IEW2476E
Source: Binder
333
IEW2481E IEW2487W
User response: Check input source.
Source: Binder
Detecting Module: IEWBNAME
IEW2481E
IEW2485E
334
IEW2488E IEW2493E
IEW2488E
IEW2491E
IEW2489E
IEW2492E
IEW2490E
335
IEW2500E IEW2506E
IEW2500E
IEW2501E
Source: Binder
Detecting Module: IEWBXWRD, IEWBXCOF
IEW2505E
Source: Binder
IEW2502E
336
Source: Binder
Detecting Module: IEWBXCRW
IEW2506E
IEW2507W IEW2513E
IEW2507W
IEW2510W
Source: Binder
Source: Binder
337
IEW2515W IEW2521W
System action: The first fill character found for this
class will be used.
User response: Correct the fill character.
Source: Binder
Detecting Module: IEWBBIND
IEW2515W
IEW2518W
IEW2517W
338
Source: Binder
Detecting Module: IEWBXCRW
IEW2521W
IEW2522E IEW2528E
User response: Check the sym records in the input
load module.
Source: Binder
Detecting Module: IEWBXCRW
Source: Binder
Detecting Module: IEWBXCRW
IEW2522E
IEW2525E
Source: Binder
Detecting Module: IEWBXCRW
IEW2523E
Source: Binder
IEW2524E
IEW2528E
339
IEW2529S IEW2535E
System action: Attributes will not be copied from the
input load module. Default attributes will be used.
User response: Specify the module as a member of a
program library. INCLUDE control statement should
read INCLUDE ddname (MEMBER membername).
Member name should not appear on the DD statement.
Source: Binder
Detecting Module: IEWBXROO
IEW2532E
IEW2529S
IEW2533S
Source: Binder
Detecting Module: IEWBXROO
IEW2530E
340
IEW2537W IEW2543W
IEW2537W
Source: Binder
Chapter 8. IEW Messages
341
IEW2544E IEW2555E
User response: Check the return and reason codes
and correct the problem if user controlled.
IEW2552E
Source: Binder
Detecting Module: IEWBXCRW
IEW2544E
Source: Binder
IEW2550E
342
IEW2556W IEW2604W
Source: Binder
IEW2559S
21
22
23
24
12
IEW2558W
13
Source: Binder
IEW2604W
343
IEW2605W IEW2610I
v A COMPAT value is specified that will force
compatibility with a version earlier than z/OS V2R7.
IEW2607E
Source: Binder
344
IEW2611E IEW2616W
IEW2611E
IEW2616W
345
IEW2617I IEW2628E
IEW2617I
IEW2625I
Source: Binder
Source: Binder
Source: Binder
Source: Binder
Source: Binder
Source: Binder
IEW2621E
346
| IEW2628E
|
|
|
|
|
|
|
|
|
|
|
IEW2629W IEW2636S
|
|
|
|
|
Source: Binder
Source: Binder
Detecting Module: IEWBXCRL
IEW2633W
IEW2635I
Source: Binder
Detecting Module: IEWBXCRL
IEW2630E
IEW2636S
Source: Binder
Detecting Module: IEWBXCRL
IEW2632T
347
IEW2637E IEW2643E
| IEW2637E
|
|
|
|
|
|
|
IEW2640E
| Source: Binder
| Detecting Module: IEWBXCTR
IEW2638S
Source: Binder
Detecting Module: IEWBXCWR, IEWBXCWL,
IEWBXCWP
AN EXECUTABLE VERSION OF
MODULE member EXISTS AND
CANNOT BE REPLACED BY THE
NON-EXECUTABLE MODULE JUST
CREATED.
IEW2641S
Source: Binder
Detecting Module: IEWBXCWR, IEWBXCWL,
IEWBXCWP
Source: Binder
IEW2639S
| IEW2642E
|
|
|
|
|
|
|
Source: Binder
Detecting Module: IEWBXCWL, IEWBXCWP,
IEWBXPNM, IEWBXCDR
348
IEW2643E
IEW2645W IEW2650I
System action: Module is saved is a PDS load library,
but the QCON offset information will not be preserved.
User response: Re-bind module and save it in a
PDSE program library.
Source: Binder
Detecting Module: IEWBXCWR
IEW2645W
1543
1544
IEW2646W
349
IEW2651W IEW2656W
function call when using the call interface. The binder
defaults the entry point to the first section in the module
that is not a common area.
System action: Module is saved using the first section
as the module entry point.
User response: Rebind requesting the correct entry
point for the module if the result was not desired.
Source: Binder
Detecting Module: IEWBXCEP
IEW2651W
350
IEW2657E IEW2662E
User response: If the module is to be bound in
overlay format, do not specify RMODE. It will default to
RMODE(24).
Source: Binder
Source: Binder
Detecting Module: IEWBXCEP
IEW2660W
Source: Binder
Source: Binder
Detecting Module: IEWBXCEP
IEW2658E
IEW2661E
351
IEW2663E IEW2670S
IEW2663E
Source: Binder
Detecting Module: IEWBXCWI
IEW2667W
IEW2664I
Source: Binder
Detecting Module: IEWBXCWI
IEW2668W
Source: Binder
Source: Binder
Detecting Module: IEWBXCWI
| IEW2665
|
|
|
|
|
|
|
|
|
MODULE modname IS
NON-EXECUTABLE AND WAS NOT
SAVED BECAUSE STORENX=NEVER.
| Source: Binder
IEW2666W
352
IEW2669S
IEW2671S IEW2676W
User response: Increase the region size on the JCL
and rerun the job.
IEW2674S
Source: Binder
Detecting Module: IEWBXCWM
IEW2671S
Source: Binder
353
IEW2677S IEW2683S
Source: Binder
IEW2678S
Source: Binder
Source: Binder
354
IEW2684S IEW2690E
PDSE, change the target library to PDS, or specify
COMPAT=PM1.
Source: Binder
IEW2688E
Source: Binder
Detecting Module: IEWBXROO
IEW2685I
Source: Binder
IEW2689W
IEW2687E
IEW2690E
355
IEW2691W
Explanation: An error was encountered while
processing a Generalized Object File Format (GOFF).
One of the following has occurred, as indicated by
error-id. Note that the terms SD, LD, ER, UR, and PR
are ESD record types, and P-pointer and R-pointer refer
to the RLD position and relocation pointers, respectively.
Note also that any ESD entries referred to in one ESD
record must have been defined by another ESD record
appearing earlier in the file; otherwise, the ESDID is
considered undefined.
0024
0025
0026
0027
0028
0029
Error-id Description
0001
0002
0030
0003
0031
0004
0032
0005
0033
0034
0006
0035
0007
0036
0008
0037
Unsupported AMODE.
0009
0038
0010
0039
0011
0040
Unsupported RMODE.
0041
0012
0042
0013
0043
0014
0015
0016
0017
0018
0019
0020
0021
0022
0023
356
IEW2692E IEW2696E
IEW2692E
0521
0522
0524
0525
0526
0527
0528
0529
0530
Source: Binder
0534
0536
IEW2695W
0537
0538
IEW2694E
357
IEW2697E IEW2698S
0558
1535
0560
1538
0561
1539
0562
1542
0566
1545
IEW2697E
1502
1503
Error-id Description
0002
Out of storage.
0003
Out of storage.
0550
Out of storage.
0551
Out of storage.
0552
0553
0554
0555
0556
0557
0563
0564
0565
0567
0668
1538
1550
Out of storage.
1532
1533
358
Out of storage.
1504,1505
The R-pointer in the initialization subfile is not
defined. There must be an ESD record of the
same name in the definition subfile.
1531
0001
Error-id Description
1501
IEW2698S
IEW2699E IEW2703S
3031
IEW2701S
359
IEW2704S IEW2708S
User response: Check to ensure that the data set is a
PDSE with a valid directory. You may need to contact
the IBM Support Center.
IEW2707S
Source: Binder
Detecting Module: IEWBXIGD
IEW2704S
IEW2705S
IEW2708S
IEW2706S
360
IEW2709S IEW2715S
IEW2709S
IEW2712S
IEW2715S
361
IEW2716S IEW2723S
System action: Processing for the data set
terminates.
Source: Binder
Source: Binder
Detecting Module: IEWBXIPI, IEWBXIPO, IEWBXISI
IEW2716S
IEW2719S
Source: Binder
Detecting Module: IEWBXIPO
Source: Binder
Detecting Module: IEWBXIPI
IEW2718S
synad-message
362
IEW2723S
IEW2724S IEW2730S
for Data Sets for STOW return and reason codes.
Source: Binder
Detecting Module: IEWBXIPO
IEW2724S
IEW2728S
Source: Binder
Detecting Module: IEWBXIPO
IEW2727S
IEW2730S
363
IEW2731S IEW2740S
User response: Correct data set or DD statement.
Source: Binder
Detecting Module: IEWBXISI, IEWBXIDO
IEW2731S
Source: Binder
Detecting Module: IEWBXIPO
IEW2736S
364
IEW2739S
IEW2741S IEW2747S
System action: Processing for the member
terminates.
IEW2744S
IEW2746S
365
IEW2748I IEW2754E
an explanation of this abend code.
Source: Binder
Detecting Module: IEWBXISI
IEW2748I
Source: Binder
Detecting Module: IEWBXIPD
IEW2750S
366
IEW2755S IEW2760S
User response: Recreate the PDS allocating more
directory space.
IEW2758S
Source: Binder
Detecting Module: IEWBXIPO
IEW2755S
Source: Binder
Detecting Module: IEWBXIPD
IEW2756S
IEW2759S
Source: Binder
Source: Binder
367
IEW2761S IEW2766S
IEW2761S
IEW2764S
368
IEW2767S IEW2772E
IEW2767S
IEW2770E
IEW2768S
Source: Binder
Source: Binder
369
IEW2773S IEW2779E
IEW2773S
IEW2777S
Source: Binder
Detecting Module: IEWBXIXI
IEW2774S
Source: Binder
Detecting Module: IEWBXIXI
IEW2779E
IEW2776S
370
IEW2780E IEW2786S
Source: Binder
IEW2783E
Source: Binder
Source: Binder
IEW2781E
IEW2784I
Source: Binder
Source: Binder
IEW2782S
IEW2785S
371
IEW2787E IEW2789I
following has occurred, as indicated by error-id.
IEW2788S
Error-id Description
0001
0002
Error-id Description
The first entry is missing a member name of
__.SYMDEF. This member name indicates
that the archive file contains valid data (object
modules or control cards) to process.
0501
0502
0503
0504
0505
0506
0004
0005
0006
0007
0008
0010
0201
0003
0009
Source: Binder
Detecting Module: IEWBXIOP, IEWBXIGD
Source: Binder
Detecting Module: IEWBXIXI
IEW2787E
IEW2789I
Source: Binder
372
IEW2790S IEW2796S
User response: Refer to the appropriate appendix in
z/OS UNIX System Services Messages and Codes for
an explanation of the indicated return code for the HFS
chattr() function.
Source: Binder
Source: Binder
IEW2794S
Source: Binder
Detecting Module: IEWBXIXO
IEW2791S
Source: Binder
IEW2795S
373
IEW2797S IEW2803S
System action: Processing for the file ends.
User response: For further information on the write()
function reason and return codes, refer to the
appropriate appendix in z/OS UNIX System Services
Messages and Codes.
Source: Binder
Detecting Module: IEWBXIXO, IEWBRSDM
IEW2797S
IEW2800S
IEW2798S
Source: Binder
IEW2802S
374
IEW2804S IEW2809E
opened and passed as a parameter to the BINDER.
Source: Binder
IEW2807S
Source: Binder
Detecting Module: IEWBXIPI
IEW2804S
Source: Binder
Source: Binder
Detecting Module: IEWBXIPI
IEW2806S
IEW2809E
375
IEW2810E IEW2815E
other product. Remove the program or library from the
linklist or LLFs extended library list.
IEW2813I
IEW2811I
IEW2814E
Source: Binder
Detecting Module: IEWBXIXO
IEW2812S
376
IEW2815E
IEW2816E IEW2822W
IEW2816E
Source: Binder
IEW2820W
Source: Binder
IEW2821W
Source: Binder
Detecting Module: IEWBXIXO
IEW2818W
377
IEW2823I IEW2910T
Source: Binder
Source: Binder
IEW2823I
IEW2889E
378
IEW2911T IEW2985W
IEW2911T
Source: Binder
Source: Binder
IEW2971T
IEW2974T
Source: Binder
IEW2972W
379
IEW2986E IEW3020E
Source: Binder
Detecting Module: IEWBRCRE, IEWBRSDM
IEW2986E
IEW2993I
| IEW2987W
|
IEW2995I
| Source: Binder
| Detecting Module: IEWBDINT
IEW2992S
Source: Binder
Detecting Module: IEWBRSDM
IEW3000 - 3999
IEW3000I
380
IEW3020E
IEW3025E IEW3036T
dataset SYSUT1 at the invocation of PMTPORT.
Processing continues with the next member if the user
specified an entire program object library in the input
dataset SYSUT1 at the invocation of PMTPORT.
User response: Verify the indicated program object
library member. Ensure that the program object you
wish to convert to a transportable program is not an
overlay program object.
Source: PMTPORT
Source: PMTPORT
Source: PMTPORT
Detecting Module: IEWTPORT
381
IEW3037T IEW3090T
Source: PMTPORT
Source: PMTPORT
IEW3037T
IEW3051T
IEW3038S
IEW3052T
Source: PMTPORT
Source: PMTPORT
Detecting Module: IEWTSYSD
Source: PMTPORT
382
IEW4000I IEW4005I
Detecting Module: IEWTPRNT
IEW4000 - 4999
IEW4000I
Routing Code: 11
Descriptor Code: IEW4003I
IEW4002I
383
IEW4006I IEW4008I
Return
Code
Error Description
00
0B
Program check.
0C
0D
0E
Invalid address.
Reason Code Error Description
20
Error converting TTR
24
Block outside of module
28
ADCON location invalid
0F
384
IEW4006I
IEW4009I IEW4012I
DCB is closed and reopened to cause the DEB to
reflect the new extents.
To resolve the error, you need to create and activate a
LNKLST set that is the same as the LNKLST set that
was being used when the error occurred. You can
determine which LNKLST set a job was using with the
DISPLAY PROG,LNKLST,JOB=jjjjjjjj command. You can
create a LNKLST set using SETPROG
LNKLST,DEFINE,NAME=nnn,COPYFROM=mmm,
where mmm is the name of the LNKLST set shown in
the DISPLAY. Then, you can activate the LNKLST set
using SETPROG LNKLST,ACTIVATE,NAME=nnn.
IEW4010I
Routing Code: 11
Descriptor Code: -
Source: IEWLDR00
Detecting Module: IEWLFINX
IEW4009I
Routing Code: 11
Descriptor Code: IEW4012I
Routing Code: 11
Descriptor Code: -
Source: Loader
Detecting Module: IEWLSFTO, IEWLTRLC
Routing Code: 11
Descriptor Code: Chapter 8. IEW Messages
385
IEW4013I IEW4014I
IEW4013I
IEW5000 - 5057
IEW5001
System action:
User response: Reenter the ld command and include
a library directory pathname after the -L option. For
example:
ld -L mylib myprog.o -l mine
Source: Binder
Detecting Module: IEWULMAI
IEW5003
IEW5002
Source: Binder
386
IEW5006
Source: Binder
ld "//MYPROJ.OBJ(MYPROG1)"
Source: Binder
Detecting Module: IEWULMAI
IEW5012
387
IEW5014
BLKLGTH
PRIMARY-QTY
SECONDARY-QTY
DIRECTORY
388
Source: Binder
Detecting Module: IEWULMAI
IEW5019
389
ld "//myuser.myproj.c(myprog1)"
Source: Binder
Detecting Module: IEWULMAI
If the source data set and object data set types are not
the same, you need to delete (and optionally
preallocate) the object data sets so the organizations
are the same before reentering the ld command.
Source: Binder
IEW5024
Source: Binder
IEW5028
ld "//myproj.c(myprog1)"
390
Source: Binder
Detecting Module: IEWULMAI
IEW5031
ld "//myprog.o"
If the source data set and object data set organizations
are not the same, you need to delete (and optionally
preallocate) the object data set so the organizations are
the same before reissuing the ld command.
Source: Binder
Detecting Module: IEWULMAI
IEW5029
IEW5030
391
IEW5036
392
Source: Binder
Detecting Module: IEWULMAI
IEW5039
393
IEW5050
Fork failed: %s
IEW5054
Source: Binder
ld myprog.o -S"//MYPROJ.LINKLIB"
Source: Binder
IEW5052
394
inddname
outddname
cde
rcode
rc
fc
ec
The option.
val
orig
395
IFA012I IFA015I
Descriptor Code: IFA012I
inddname
The ddname of an input data set specified in a
SYSIN INDD parameter.
System action: SMF dump processing continues. The
clear request is ignored.
System programmer response: None. It is not
necessary to clear a QSAM data set that is used later
as an output data set for SMF dump processing. If you
want to clear the data set, use the standard system
utilities.
Source: System Management Facilities (SMF)
Detecting Module: IFASMFDP
Routing Code: Descriptor Code: IFA014I
inddname
The ddname of an input data set specified in a
SYSIN INDD parameter.
cde
rcode
rcode
Routing Code: -
Descriptor Code: -
396
IFA016I IFA019I
System action: The system ends SMF dump
processing.
IFA017I
Routing Code: 2
IFA016I
rcode
Routing Code: -
exitname
The name of the installation exit routine.
Descriptor Code: -
cde
IFA018I
rcode
IFA019I
397
IFA020I IFA024I
Note: APF authorization is not required to invoke the
DUMP function or to obtain a summary activity
report.
IFA022I
ddname dsname
rcode
Routing Code: -
ddname
dsname
IFA023I
The name of the data set.
398
IFA024I
IFA100I IFA101I
are printed in the Summary Activity Report. Subsequent
records in error are not printed, but are still counted in
the total number of records in error.
In the message text:
inddname
The DD name of the specified SMF recording data
set.
prodid
ENABLED
DISABLED
Routing Code: -
Descriptor Code: 5
IFA101I
IN PARMLIB MEMBER=memname ON
LINE line-number PRODUCTS WITH
OWNER=prodown NAME=prodname
FEATURE=featurename
VERSION=vv.rr.mm ID=prodid COULD
NOT BE {ENABLED|DISABLED}. NO
STORAGE AVAILABLE.
Routing Code: -
memname
line-number
prodown
prodname
featurename
vv
rr
mm
IN PARMLIB MEMBER=memname ON
LINE line-number PRODUCTS WITH
OWNER=prodown NAME=prodname
FEATURE=featurename
VERSION=vv.rr.mm ID=prodid HAVE
BEEN {ENABLED|DISABLED}.
line-number
prodid
prodown
ENABLED
prodname
DISABLED
featurename
vv
rr
mm
399
IFA102I IFA104I
Routing Code: -
memname
line-number
prodown
prodname
featurename
vv
rr
mm
prodid
Descriptor Code: 5
IFA102I
IN PARMLIB MEMBER=memname ON
LINE line-number PRODUCTS WITH
OWNER=prodown NAME=prodname
FEATURE=featurename
VERSION=vv.rr.mm ID=prodid HAVE
BEEN REMOVED FROM THE
PRODUCT POLICY.
line-number
prodown
prodname
featurename
vv
rr
mm
prodid
Routing Code: -
Descriptor Code: 5
IFA104I
Descriptor Code: 5
IFA103I
IN PARMLIB MEMBER=memname ON
LINE line-number PRODUCTS WITH
OWNER=prodown NAME=prodname
FEATURE=featurename
VERSION=vv.rr.mm ID=prodid WERE
NOT REMOVED FROM THE POLICY.
NO MATCH WAS FOUND.
400
prodname
featurename
IFA110I IFA111I
vv
rr
mm
prodid
IFA111I
owner
The owner of the product.
name
The name of the product.
featname
The feature name of the product.
vv The version of the product.
rr
mm
The modification level of the product.
id
401
IFA112I IFA202W
IFA112I
IFA201W
IFA200W
http://www.ibm.com/servers/eserver/zseries/zose/
Source: IEAVNPIL
Source: IEAVNPED
Descriptor Code: -
402
IFA301E IFA306I
|
|
IFA301E
|
|
|
|
|
|
| IFA305S
|
|
|
|
Source: SMF
Routing Code: -
Descriptor Code: -
IFA303S
|
|
|
|
|
Source: SMF
Routing Code: -
Descriptor Code: -
|
|
|
IFA304S
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source: SMF
| Detecting Module: IFAURP
| Routing Code: | Descriptor Code: | IFA306I
|
403
IFA307I IFA311S
| IFA307I
|
| IFA310E
|
keyword TRUNCATED TO nn
CHARACTERS.
| Source: SMF
| Descriptor Code: -
| Routing Code: -
| IFA311S
404
IFA312S IFA314E
|
|
|
|
|
|
2.
3.
4.
5.
6.
7.
PROCESSOR MODEL
PROCESSOR SERIAL NUMBER
CLUSTER TYPE
CLUSTER MODEL
CLUSTER SERIAL NUMBER
CUSTOMER NAME
|
|
Source: SMF
Routing Code: -
| yyyy
Descriptor Code: -
| mm
|
|
|
IFA312S
| dd
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Notes:
1. symbol is any keyword, keyword
value, or special symbol such as
( or ,, used in the control
statements.
2. Error types 3 and 4 above are
always preceded by message
IFA312S, error type 1, or error
type 2.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Source: SMF
| Source: SMF
Routing Code: -
| Routing Code: -
405
IFA320I IFA325I
| Descriptor Code: | IFA320I
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source: SMF
| Detecting Module: IFAURP
| Routing Code: | Descriptor Code: | IFA323S
| IFA321S
| Source: SMF
| Detecting Module: IFAURP
| Routing Code: | Descriptor Code: -
| IFA322E
|
|
|
|
|
|
|
|
406
IFA326I IFA330I
|
|
Source: SMF
Routing Code: -
Descriptor Code: -
|
|
IFA326I
|
|
|
|
Source: SMF
Routing Code: -
Descriptor Code: -
IFA327E
|
|
|
|
Source: SMF
Routing Code: -
Descriptor Code: -
|
|
|
|
|
IFA328S
|
|
|
|
|
|
|
|
|
|
|
|
| version
|
|
| model
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source: SMF
| Detecting Module: IFAURP
| Routing Code: | Descriptor Code: | IFA330I
|
|
|
|
|
|
407
IFA331E IFA334E
| Routing Code: | Descriptor Code: | IFA331E
|
|
|
|
|
|
|
| Source: SMF
| Detecting Module: IFAURP
| Routing Code: | Descriptor Code: | IFA332S
|
408
|
|
|
|
|
{PROCESSOR type,model,serial |
CLUSTER
cluster_type,cluster_model,cluster_serial |
SYSPLEX sysplex id} HAS BEEN
DUPLICATELY SPECIFIED.
IFA335E IFA339E
|
Routing Code: -
Descriptor Code: -
|
|
IFA335E
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source: SMF
Source: SMF
Routing Code: -
Descriptor Code: -
|
|
|
|
IFA336S
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Source: SMF
Routing Code: -
Descriptor Code: -
{PROCESSOR type,model,serial|
CLUSTER
cluster_type,cluster_model,cluster_serial}
NOT VALID.
| IFA337E
|
|
|
|
|
|
|
|
|
|
409
IFA340E IFA344I
| Source: SMF
| Detecting Module: IFAURP
| Routing Code: | Descriptor Code: -
| IFA340E
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
410
| Source: SMF
| Detecting Module: IFAURP
| Routing Code: | Descriptor Code: | IFA343E
|
IFA345E IFA347E
|
|
|
|
Source: SMF
Routing Code: -
Descriptor Code: -
|
|
|
IFA345E
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source: SMF
VENDOR EXIT modname REQUIRES
IFAURP VERSION xx RELEASE yy MOD
zz.
Source: SMF
Routing Code: -
Descriptor Code: -
|
|
|
IFA346E
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
411
IFA348E IFA352E
| IFA348E
|
|
|
|
|
| Source: SMF
| Detecting Module: IFAURP
| Routing Code: -
| IFA351E
|
| Descriptor Code: -
| IFA349E
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source: SMF
| Detecting Module: IFAURP
| Routing Code: | Descriptor Code: | IFA350E
|
|
412
IFA353E IFA356E
|
|
Source: SMF
Routing Code: -
Descriptor Code: -
|
|
|
IFA353E
|
|
|
|
|
| IFA355E
|
|
|
|
|
|
|
|
|
Source: SMF
| Source: SMF
Routing Code: -
| Routing Code: -
Descriptor Code: -
| Descriptor Code: -
|
|
IFA354E
| IFA356E
|
|
|
|
|
|
Source: SMF
Routing Code: -
Descriptor Code: -
|
|
|
|
|
|
|
|
|
|
| Source: SMF
| Detecting Module: IFAURP
| Routing Code: | Descriptor Code: -
413
IFA358I IFA363E
|
|
|
|
|
|
|
| Source: SMF
| Source: SMF
| Routing Code: -
| Routing Code: -
| Descriptor Code: -
| Descriptor Code: -
| IFA359I
| IFA362I
|
| IFA358I
|
|
|
|
| Source: SMF
| Detecting Module: IFAURP
| Routing Code: -
| Descriptor Code: -
| Source: SMF
| Detecting Module: IFAURP
| Routing Code: | Descriptor Code: | IFA361E
|
|
|
|
|
414
| IFA363E
|
|
|
|
|
|
|
|
|
|
|
|
|
|
IFA364I
|
|
|
|
|
|
Source: SMF
Routing Code: -
Descriptor Code: -
|
|
IFA364I
|
|
|
|
|
|
|
|
Source: SMF
Routing Code: -
Descriptor Code: -
415
416
Descriptor Code: 11
IFB081I
hh.mm.ss
The time in hours (00-23), minutes (00-59),
and seconds (00-59).
Routing Code: 1
Descriptor Code: 2
dsname
IFB020I
stat
417
IFB083I IFB086I
hh.mm.ss
The time in hours (00-23), minutes (00-59),
and seconds (00-59).
dsname
The name of the logrec data set.
System action: The system does not retry the I/O
operation that encountered the error. If the access
attempt was to write the record, the record is lost.
Attempts to read and write records to the logrec data
set will continue.
System programmer response: Run the
Environmental Recording, Editing, and Printing program
(EREP) to dump the logrec data set and save its
contents. Then run the IFCDIP00 service aid program to
reinitialize the logrec data set. If this does not resolve
the problem, then an IPL will be necessary for the
system to be able to update its pointers to the new
SYS1.LOGREC data set.
Source: System Environmental Recording (LOGREC)
Detecting Module: IFBSVC76
Routing Code: 1
Descriptor Code: 4
IFB083I
dsname
The name of the logrec data set.
System action: The system continues processing but
does not write any more records to the logrec data set
until the device is mounted and the data set is available.
System programmer response: Verify that the device
on which the logrec data set resides is available and
mounted.
Source: System Environmental Recording (LOGREC)
Detecting Module: IFBSVC76
Routing Code: 1
Descriptor Code: 4
IFB085I
Routing Code: 1
Descriptor Code: 4
Descriptor Code: 4
IFB084I
IFB086I
418
IFB087I IFB090I
System action: The system continues system
initialization.
Source: System Environmental Recording (LOGREC)
419
IFB091I IFB094I
connected and active. All logrec error
records are being sent to the system
logger for management.
NOT CONNECTED
The logrec log stream
(SYSPLEX.LOGREC.ALLRECS) is not
connected. The system logger is not
currently available. The system records the
logrec error records in an internal buffer
until the system logger is available.
LOGGER DISABLED FOR THIS IPL
The system logger services will not be
available for the life of the current IPL. The
system records the logrec error records in
an internal buffer. If the recording medium
remains LOGSTREAM under these
circumstances, an overflow condition will
occur. IBM recommends changing the
logrec recording medium using the
SETLOGRC command.
Note: Only a limited amount of logrec error records
will be buffered. If the system logger
problem is not corrected, logrec error
records can be lost.
If the operator included the DSN option, line 5 appears.
Line 5 displays information pertaining to a data set
recording medium.
DATASET MEDIUM=[data set name | NOT DEFINED]
The data set name that was defined for logrec error
recording during IPL. The data set might be the
current recording medium. The current recording
medium can be obtained by entering the DISPLAY
command with the CURR option. If a data set was
never defined via SYS1.PARMLIB during IPL, then
instead of a data set name being displayed, the
text NOT DEFINED will be displayed.
The system will not be able to change the recording
medium to data set in this case unless a system
IPL is performed, defining a data set as the
recording medium.
IFB091I
IFB094I
420
IFB095I IFB099I
IFB095I
IFB098E
0001,yyyy
A non-zero return code was returned from the
STORAGE macro. The macro return code is
yyyy. See z/OS MVS Programming: Assembler
Services Reference ABE-HSP for a description
of the STORAGE macro return codes.
IFB099I
421
IFB100E
Operator response: Notify your system programmer.
System programmer response: If the problem was
that system logger services will not be available for the
life of the IPL, check your system configuration. It may
not be appropriate to go to a log stream under your
particular circumstances.
Source: System Environmental Recording (Logrec)
Detecting Module: IFBSETLG
Routing Code: 2,10
Descriptor Code: 5
IFB100E
422
IFB100E
STRUCTURE IS FULL
The system logger was unable to process the
write request because the structure associated
with the logrec log stream is full. This error
corresponds to IXGWRITE return code 8,
reason code 860.
LOG STREAM IS NOT AVAILABLE
The system logger was unable to access the
logrec log stream. The primary reason is
because the structure associated with the
logrec log stream is being rebuilt. This error
corresponds to IXGWRITE return code 8,
reason codes 861 through 88F.
LOG STREAM DIRECTORY IS FULL
The system logger was unable to process the
write request because the coupling facility
structure space allocated for the logrec log
stream is full. Attempts to offload the coupling
facility data to DASD have failed because the
log streams data set directory is full. No further
write requests can be processed until enough
log data is deleted from the log stream to free
up space in the data set directory. This error
corresponds to IXGWRITE return code 8,
reason code 85C.
SYSTEM LOGGER NOT AVAILABLE
The system logger services are currently
unavailable. This error corresponds to
IXGWRITE return code 8, reason code 890 or
891.
diagfld1,diagfld2,diagfld3,diagfld4
Contains the system logger answer area
diagnostic fields when the return and reason
codes cannot be interpreted.
DISCONNECT ERROR - discreason
Indicates the error occurred after the IXGCONN
macro was issued in an attempt to disconnect from
the logrec log stream.
discreason is the following:
diagfld1,diagfld2,diagfld3,diagfld4
Contains the system logger answer area
diagnostic fields when the return and reason
codes cannot be interpreted.
LOG STREAM NAME: log-stream-name
Identifies the name of the logrec log stream that
had the error.
STRUCTURE NAME: structure-name
Identifies the structure name associated with the
logrec log stream that had the error.
System action: No recording will occur in the logrec
log stream on the named system until the condition is
corrected. The system continues processing.
Operator response: Notify the system programmer.
When the problem with the logrec log stream has been
resolved, you might need to enter the SETLOGRC
423
IFB101I
IFB101I
424
track1
track2
recd
IFC021I
Descriptor Code: 6
Copyright IBM Corp. 1988, 2007
425
IFC156I
Routing Code: 1
Descriptor Code: 6
IFC156I
426
v QUIESCED/NEW
v DISABLED
v DISABLED/NEW
rc
dev
A device number.
dtdtxx
volser
A volume serial.
volstat
427
IGD002I
Operator response: If the display line DEVICE
INFORMATION SERVICES INFORMATION
TRUNCATED. RETURN CODE rc appears, tell your
programming support personnel.
hh.mm.ss
The time in hours (00-23), minutes (00-59),
and seconds (00-59). If the time of day clock is
not working, hh.mm.ss will appear as 00.00.00.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 5,8,9
IGD002I
id
SCDSdsname
ACDS dsname
hh.mm.ss
The time in hours (00-23), minutes (00-59),
and seconds (00-59). If the time of day clock is
not working, hh.mm.ss will appear as 00.00.00.
id
COMMDS dsname
The communications data set
(COMMDS).
DINTERVAL int The decimal number from 1 to 999
that specifies the number of seconds
that should pass before SMS attempts
to read statistics for 3990 Model 3 or
Model 6 control units with
SMS-managed volumes attached.
REVERIFY {YES|NO}
An indication of when the storage
management subsystem verifies a
users authority to allocate a new data
set, use a storage class, or use a
management class.
YES
NO
428
ACSDEFAULTS {YES|NO}
An indication of whether the storage
management subsystem will retrieve
certain ACS routine variables from
RACF; the default is NO.
SYSTEM sysname
The systems and system groups in
the SMS complex. Up to 32 systems
may be displayed.
IGD002I
CONFIGURATION LEVEL year/mo/dy hh.mm
The current level of the system
configuration. The configuration level
is expressed as a date/time stamp of
the last configuration update. This
update is performed every nnn
number of seconds. The variables for
the date stamp are:
year
mo
dy
Routing Code: 2
Source: DFSMSdfp
Routing Code: 2
IGD002I
NO SYSTEMS EXIST
Explanation: The operator entered the DISPLAY
SMS,ACTIVE command, and the storage management
subsystem (SMS) configuration contains no systems.
IGD002I
hh.mm.ss
The time displayed in hours (00-23), minutes
(00-59), and seconds (00-59). If the time of day
clock is not working, hh.mm.ss will appear as
00.00.00.
id
429
IGD002I
READ =
IGD002I
NO INFORMATION AVAILABLE
WRITE =
PERCENT OF DATA ON MANAGED DEVICES
ELIGIBLE FOR FAST WRITE
HIT RATIO =
PERCENT OF READS WITH CACHE HITS
FW BYPASSES =
NUMBER OF FAST WRITE BYPASSES DUE
TO NVS OVERLOAD
The operator entered a DISPLAY SMS,CACHE
command. In response, this message shows the control
variables and measured CACHE status for the
subsystems that have SMS devices attached.
id
nn
rr
ww
hr
fbb
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 5,8,9
IGD002I
Source: DFSMSdfp
Routing Code: 2
ssid
|
|
VOLSELMSG = {ON|OFF},{nnnn|ALL}
TYPE = stat JOBNAME = stat
ASID = {asid|*}
STEPNAME = {stepname|*}
DSNAME = {dsname|*}
FAST_VOLSEL= {ON|OFF}
DEBUG= {ON|OFF}
Explanation: The operator entered the DISPLAY
SMS,TRACE or DISPLAY SMS,OPTIONS command.
430
IGD002I
This command displays the storage management
subsystem (SMS) trace parameters. When the operator
enters the DISPLAY SMS,OPTIONS command, this
message is displayed after message IGD002I, which
displays the other PARMLIB parameters.
In the message text:
hh.mm.ss
The time in hours (0023), minutes (0059),
and seconds (0059). If the time-of-day clock
is not working, hh.mm.ss appears as 00:00:00.
TRACE {ON|OFF}
Specifies one of the following trace options for
SMS is to use. The default trace option is ON.
ON
Turn on tracing.
OFF
Discontinue all tracing.
SIZE = {nnnnnn[K]|nnnM}
Specifies the size of the trace table. The
default value is 128K. The default unit is
kilobytes. You can specify the size of the trace
table as follows:
nnnnnn
The size of the trace table in kilobytes,
ranging from 0 to 255000. This value is
rounded up to the nearest 4 KB unit.
asid
nnnnnnK
The size of the trace table in kilobytes,
ranging from 0K to 255000K. This value is
rounded up to the nearest 4 KB unit.
CONFS = stat
Configuration services.
nnnM
The size of the trace table in megabytes,
ranging from 0M to 255M. This value is
stored in kilobytes.
ERR = stat
Error recovery and recording services.
TYPE = {ERROR|ALL}
Specifies the type of trace entries to be traced.
The default value is ERROR. Descriptions of the
TYPE values follow:
ERROR
Trace error type of trace entries.
ALL
JOBNAME = {jjj|*}
Specifies the tracing scope in relation to jobs.
The default is *. Descriptions of the JOBNAME
values follow:
jjj
ASID = {asid|*}
Specifies the tracing scope in relation to the
address spaces. The default is *. Descriptions
of the ASID values follow:
MSG = stat
Message services.
CONFR = stat
Return data from an active configuration.
CONFA = stat
Activate a new configuration.
ACSPRO = stat
Perform ACS processing.
IDAX = stat
The SMS interpreter and dynamic allocation.
DISP = stat
A disposition processing exit.
CATG = stat
SMS catalog services.
VOLREF = stat
SMS VOLREF services.
SCHEDP = stat
Scheduling services, prelocate catalog orientation.
SCHEDS = stat
Scheduling services, system select.
431
IGD002I
VTOCL = stat
VTOC and data set services, allocate an existing
data set.
VTOCD = stat
VTOC and data set services, delete an existing
data set.
|
|
|
|
|
TYPE = {ERROR|ALL}
This parameter is described earlier in this message
description. It applies to both tracing and the
issuance of volume selection messages. It will be
displayed here as it applies to the issuance of
volume selection messages.
VTOCR = stat
VTOC and data set services, rename an existing
data set.
VTOCC = stat
VTOC and data set services, create a new data
set.
JOBNAME = {jjj|*}
This parameter is described earlier in this message
description. It applies to both tracing and the
issuance of volume selection messages. It will be
displayed here as it applies to the issuance of
volume selection messages
VTOCA = stat
VTOC and data set services, add a volume to a
data set.
RCD = stat
SMS recording services or SMS fast VTOC and
VVDS access.
ASID = {asid|*}
This parameter is described earlier in this message
description. It applies to both tracing and the
issuance of volume selection messages. It will be
displayed here as it applies to the issuance of
volume selection messages
DCF = stat
The device control facility.
DPN = stat
The device pool select.
STEPNAME = {stepname|*}
specifies the scope of the issuance of volume
selection analysis messages in relation to a job
step.
TVR = stat
A tape volume record update.
DSTACK = stat
Data set stacking SSI.
stepname
limits the scope volume selection analysis
messages to the named job step.
UAFF = stat
Unit affinity.
| DEBUG=stat
Debug service.
|
| VOLSELMSG = (ON|OFF, nnnn)
controls the issuance of summarized and detailed
|
volume selection analysis messages where:
|
|
|
|
|
ON
|
|
|
|
OFF
turns off the issuance of summarized and
detailed analysis messages for volume
selection. This is the default value.
|
|
|
|
|
|
nnnn
is the number of volumes to be included in the
detailed analysis messages. The range of this
value is 065535. The default is 0 which
indicates that no detailed analysis messages
will be issued.
|
|
|
|
ALL
DSNAME = {dsname|*}
specifies the scope of the issuance of volume
selection analysis messages in relation to a data
set.
dsname
limits the scope volume selection analysis
messages to the named data set.
*
| FAST_VOLSEL
|
|
ON
|
|
OFF
Fast volume selection function is off.
432
IGD002I
Source: Storage management subsystem (SMS)
|
|
|
{YES | NO}
Rls_MaxCfFeatureLevel =
{cache feature | Z}
PDSE_MONITOR =
(YES|NO,interval,duration) |
PDSE1_MONITOR =
(YES|NO,interval,duration)
PDSE_DIRECTORY_STORAGE
= nnnnM |
PDSE1_DIRECTORY_STORAGE
= nnnnM
PDSE_BUFFER_BEYOND_CLOSE
= YES | NO |
PDSE1_BUFFER_BEYOND_CLOSE
= YES | NO
GDS_RECLAIM = {YES | NO}
DSSTIMEOUT = nnnn
BLOCKTOKENSIZE =
{REQUIRE | NOREQUIRE}
FAST_VOLSEL = {ON | OFF},
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
433
IGD002I
id
YES
DFSMSdfp listens for the SMF
event-notification signal and create the
specified SMF records.
ACDS = dsname
Specifies the name of the active control data set,
dsname.
COMMDS = dsname
Specifies the name of the communications data set,
dsname.
INTERVAL = nnn
Specifies the synchronization interval, nnn, which is
the number of seconds between system checks of
the COMMDS for information about SMS
configuration changes from other systems in the
SMS complex. The default is 15 seconds.
DINTERVAL = nnn
Specifies the number of seconds, nnn, that SMS
waits between reading device statistics from the
3990-3 control unit. The default is 150 seconds.
| PDSE_LRUTIME = nn | PDSE1_LRUTIME = nn
Specifies the number of seconds, nn, that the buffer
|
management facility(BMF) waits between calls to
|
the BMF data space cache LRU (least recently
|
used) routine in SMSPDSE Or SMSPDSE1 address
|
space. The value of nn is in the range of 5-60. The
|
default is 15 seconds.
|
| PDSE_LRUCYCLE = nnn | PDSE1_LRUCYCLE = nnn
Specified the maximum number of times, nnn, that
|
the buffer manager facility (BMF) least Recently
|
used (LRU) routine passes over inactive buffers
|
before making them available for reuse in
|
SMSPDSE or SMSPDSE1 address space. The
|
value of nn in the range of 5-240. The default is
|
240 cycles.
|
SMF_TIME = {YES|NO}
Determines whether DFSMSdfp creates SMF
type-42 records at the expiration of the SMF time
434
NO
DFSMSdfp does not create any SMF type-42
records.
CF_TIME = nnnnn
Specifies the interval, in seconds, nnnnn, between
recording SMF record 42 (subtypes 15, 16, 17, 18)
for use of the coupling facility by the SMSVSAM
address space. The SMF_TIME keyword, if set to
YES, overrides the CF_TIME keyword. The value of
nnnnn is in the range 086399. The default value is
3600.
LOCAL_DEADLOCK = nnnn
Specifies the length in seconds, nnnn, of the local
deadlock detection interval. The value of nnnn is in
the range 19999. The default is 15 seconds.
GLOBAL_DEADLOCK = nnnn
Specifies the number of local deadlock cycles,
nnnn, that must expire before global deadlock
detection is to be performed. The value of nnnn is
in the range 19999. The default is 4 cycles.
REVERIFY = {YES|NO}
Determines whether SMS verifies a users authority
to allocate a new data set and use a storage or
management class at both job interpretation time
and run time or only at job interpretation time. The
default value is NO.
YES
SMS verifies a users authority at both job
interpretation time and run time.
NO
SMS verifies a users authority only at
interpretation time.
ACSDEFAULTS = {YES|NO}
Determines whether SMS initializes the following
automatic class selection (ACS) routine variables
from an additional call to RACF, a component of the
Security Server for z/OS. The default value is NO.
&APPLIC
&DEF_DATACLAS
&DEF_MGMTCLAS
&DEF_STORCLAS
YES
SMS retrieves these ACS routine variables
from RACF.
NO
SMS does not retrieve any ACS routine
variables from RACF.
DSNTYPE = {LIBRARY|PDS}
Determines the system default value of the
IGD002I
DSNTYPE parameter for new SMS-managed data
sets. The default value is PDS.
LIBRARY
A new SMS-managed data set is allocated as
a partitioned data set extended (PDSE) if the
value of DSNTYPE is not specified in the job
control language (JCL) data definition (DD)
statement or in the data class.
PDS
A new SMS-managed data set is allocated as
a partitioned data set (PDS) if the value of
DSNTYPE is not specified in the JCL DD
statement or in the data class.
PDSESHARING = {NORMAL|EXTENDED}
Specifies how PDSEs are shared across systems in
a sysplex. The default value is NORMAL.
NORMAL
Users share read access to PDSEs across
systems in the sysplex.
EXTENDED
Users share read and write access to PDSEs
across systems in the sysplex.
OVRD_EXPDT = {YES|NO}
Determines whether an expiration date or retention
period for SMS-managed DASD data sets is
overridden when deletion is requested through JCL,
SVC 99, IEHPROGM, or ISPF or PDF. The default
value is NO.
YES
Data sets are deleted whether or not the
expiration date or retention period has passed.
NO
Any expiration date or retention period is
honored.
SYSTEMS = {8|32}
Specifies the maximum number of unique system
names and system group names that you can
specify in the SMS configuration.
HSP_SIZE = nnnMB
Specifies the size of the Hiperspace that controls
the amount of expanded storage that the PDSE
allocates. The value of nnn is in the range 0512.
The default is 256 MB.
USE_RESOWNER = {YES|NO}
Specifies whether SMS determines the owner (user
or group defined by RACF) of an SMS-managed
data set protected by the profile. The default value
is YES.
YES
SMS extracts the owner of an SMS-managed
data set from the owner profile.
NO
The owner of an SMS-managed data set is the
user ID.
RLS_MAX_POOL_SIZE = nnnn MB
Specifies the maximum size in megabytes of the
SMSVSAM local buffer pool. SMSVSAM attempts
to limit the size of the buffer pool to this value, but
might exceed this storage amount temporarily.
Because SMSVSAM manages buffer pool space
dynamically, this value does not set a static size for
the buffer pool.
RLSINIT = {YES|NO}
Determines whether the SMSVSAM address space
is started, to bring up VSAM record-level sharing
(RLS), as part of the system initialization. The
default value is NO.
YES
SMSVSAM server is initialized at IPL time.
NO
SMSVSAM server is not active after IPL.
RLSTMOUT = nnnn
Specifies the maximum time, in seconds, that a
VSAM RLS or DFSMStvs request is to wait for a
required lock before the request is assumed to be
in deadlock and abnormally ended with return code
8 and reason code 22. The value is in the range
09999. The default is 0 seconds (no time out).
COMPRESS = {GENERIC|TAILORED}
Specifies the method to compress a SAM data set.
The default value is GENERIC.
GENERIC
The compression management service uses
the original dictionary-building-block (DBB)
solution to compress the data set.
TAILORED
The compression management service uses
the tailored dictionaries, which are built by
scanning up to 500K of user data. The
dictionaries are imbedded in the SAM data set.
LOG_OF_LOGS = logstreamid
Specifies the log stream for DFSMStvs to use as its
log of logs. This log contains copies of the tie-up
records and file-close records written to forward
recovery logs, which forward recovery products
use. The default is to use no log of logs. The
logstreamid value can be up to 26 characters long.
QTIMEOUT = nnnn
Specifies the quiesce exit timeout value in seconds;
that is, the amount of time that the DFSMStvs
quiesce exits allow to elapse before concluding that
a quiesce cannot be completed successfully. The
value is in the range 603600. The default is 300
seconds.
TVSNAME = nnn
Specifies the identifier that uniquely identifies the
instance of DFSMStvs running on the system. The
value is in the range 0255. There is no default
value.
435
IGD002I
AKP = nnn
Specifies the activity-keypoint trigger value, which is
the number of logging operations between the
taking of keypoints. The value is in the range
20065535. The default is 1000.
TV_START_TYPE = {WARM|COLD}
Specifies the type of start that DFSMStvs is to
perform. The default is WARM.
WARM
DFSMStvs reads its undo log and processes
the information it finds in accordance with the
information that resource recovery services
(RRS) has about any outstanding units of
recovery.
COLD
DFSMStvs deletes any information that
remains in the undo log and starts as if the log
were empty.
MAXLOCKS = (max,incr)
Specifies two values: the maximum number of locks
that a single unit of recovery can hold before the
warning message IGW859I is issued to the system
console, and an increment value. After the
maximum is reached, the warning message is
issued every time the number of locks held over
and above the maximum is the multiple of the
increment. The max and incr values are in the
range 0999999. The default value for both is 0. It
is invalid for max to be 0 and incr to be greater
than 0.
CICSVR_INIT = {YES|NO}
Determines whether the CICSVR address space is
started as part of the system initialization. The
default value is NO.
YES
The CICSVR address space is active after IPL.
NO
The CICSVR address space is not active after
IPL.
CICSVR_DSNAME_PREFIX = {user prefix|DWW.}
Specifies the prefix for all CICSVR data set names
that CICSVR creates. The default value is DWW..
| CICSVR_RCDS_PREFIX = cicsvr_rcds_prefix
|
Specifies a prefix of CICSVR Recovery Control
Data Set (RCDS) names that CICSVR server
|
address space will use to allocate the RCDSs to
|
the CICSVR server.
|
| CICSVR_GRPNAME_SUFFIX = cicsvr_grpname_suffix
Specifies the suffix of CICSVR XCF group names
|
that the CICSVR address space use to recreate a
|
unique XCF group name per the sysplex and
|
connect to the sysplex. The specified suffix is
|
activated when the CICSVR server address space
|
is next started.
|
436
| CICSVR_ZZVALUE_PARM = zzvalue_string
|
Specifies the ZZVALUE string which is a pair of
|
name and value, or one control ZZVALUE value
|
that specifies an action to take. And this value
|
maintains the ZZVALUE table and the diagnostic
|
data set.
| CICSVR_UNDOLOG_CONTROL = undo log string
|
Specifies the parameters and service functions to
|
control CICSVR UNDO logging. The CICSVR
|
address space will decode the logging control
|
string, and activate the parameters and execute the
|
service function. It is a string of 17 characters long.
|
The default string is a blank string.
| CICSVR_UNDOLOG_PREFIX = undo log prefix
|
Specifies the CICSVR UNDO log name prefix that
|
CICSVR server address space will use to
|
determine the log stream name which should be
|
written to by CICSVR UNDO logging. It is a string
|
of 8 characters long. The default string is DWW.
| CICSVR_BACKOUT_CONTROL = backout control
| string
|
Specifies the parameters and service functions to
|
control CICSVR batch backout logging. The
|
CICSVR address space will decode the logging
|
control string, and activate the parameters and
|
execute the service function. It is a string of 17
|
characters long. The default string is a blank string.
| CICSVR_GENERAL_CONTROL = general control
| string
|
Specifies the parameters and service functions that
|
relate to various CICSVR functions. The CICSVR
|
general control string and service functions can be
|
used to invoke a CICSVR scavenger or to display
|
the current setting of all CICSVR control strings. It
|
is a string of 17 characters long. The default string
|
is a blank string.
Rls_DynamicCfCacheReassign = {YES|NO}
Determines whether the dynamic cache can be
reassigned during SMSVAM processing. The
default value is NO.
Rls_MaxCfFeatureLevel = {cache feature | Z}
Specifies the cache feature level. The default value
is Z.
IGD002I
|
|
|
|
|
|
|
|
|
|
|
|
|
|
FAST_VOLSEL = ON | OFF
Specifies whether the summarized and detail
volume selection analysis messages will be issued
or not. Nnnn or ALL is the number of volumes or all
volumes which are included in the scope of
issuance of the detailed volume selection analysis
messages. The range is 0-65535. The default
values is (OFF,0).
TRACE {ON | OFF}
Specifies one of the following trace options for SMS
is to use. The default trace option is ON.
ON
Turn on tracing.
OFF
Discontinue all tracing.
SIZE = {nnnnnn[K] | nnnM}
Specifies the size of the trace table. The default
value is 128K. The default unit is kilobytes. You can
specify the size of the trace table as follows:
nnnnnn
The size of the trace table in kilobytes, ranging
from 0 to 255000. This value is rounded up to
the nearest 4 KB unit.
nnnnnnK
The size of the trace table in kilobytes, ranging
from 0K to 255000K. This value is rounded up to
the nearest 4 KB unit.
nnnM
The size of the trace table in megabytes,
ranging from 0M to 255M. This value is stored in
kilobytes.
TYPE = {ERROR | ALL}
Specifies the type of trace entries to be traced. The
default value is ERROR. Descriptions of the TYPE
values follow:
ERROR
Trace error type of trace entries.
ALL
JOBNAME = {jjj|*}
Specifies the tracing scope in relation to jobs. The
default is *. Descriptions of the JOBNAME values
follow:
jjj
ASID = {asid|*}
Specifies the tracing scope in relation to the
address spaces. The default is *. Descriptions of
the ASID values follow:
asid
437
IGD002I
CONFS = stat
Configuration services.
| DEBUG = stat
|
Debug Service
MSG = stat
Message services.
ERR = stat
Error recovery and recording services.
CONFR = stat
Return data from an active configuration.
CONFA = stat
Activate a new configuration.
ACSPRO = stat
Perform ACS processing.
IDAX = stat
The SMS interpreter and dynamic allocation.
DISP = stat
A disposition processing exit.
CATG = stat
SMS catalog services.
VOLREF = stat
SMS VOLREF services.
SCHEDP = stat
Scheduling services, prelocate catalog orientation.
SCHEDS = stat
Scheduling services, system select.
VTOCL = stat
VTOC and data set services, allocate an existing
data set.
VTOCD = stat
VTOC and data set services, delete an existing
data set.
VTOCR = stat
VTOC and data set services, rename an existing
data set.
VTOCC = stat
VTOC and data set services, create a new data
set.
VTOCA = stat
VTOC and data set services, add a volume to a
data set.
RCD = stat
SMS recording services or SMS fast VTOC and
VVDS access.
DPN = stat
The device pool select.
TVR = stat
A tape volume record update.
DSTACK = stat
Data set stacking SSI.
| UAFF=stat
Unit Affinity.
|
438
OFF
turns off the issuance of summarized and
detailed analysis messages for volume
selection. This is the default value.
nnnn
is the number of volumes to be included in the
detailed analysis messages. The range of this
value is 065535. The default is 0 which
indicates that no detailed analysis messages
will be issued.
ALL
indiactes that all of the volumes that were used
by volume selection are included in the
detailed analysis messages.
Note: When VOLSELMSG(ON,nnnn|ALL) is
specified, where nnnn is greater than zero
and TYPE(ALL) is also specified then one of
JOBNAME, ASID, DSNAME, or STEPNAME
must also be specified.
TYPE = {ERROR|ALL}
This parameter is described earlier in this message
description. It applies to both tracing and the
issuance of volume selection messages. It will be
displayed here as it applies to the issuance of
volume selection messages.
JOBNAME = {jjj|*}
This parameter is described earlier in this message
description. It applies to both tracing and the
issuance of volume selection messages. It will be
displayed here as it applies to the issuance of
volume selection messages
ASID = {asid|*}
This parameter is described earlier in this message
description. It applies to both tracing and the
issuance of volume selection messages. It will be
displayed here as it applies to the issuance of
volume selection messages
STEPNAME = {stepname|*}
specifies the scope of the issuance of volume
selection analysis messages in relation to a job
step.
stepname
limits the scope volume selection analysis
messages to the named job step.
IGD002I
*
DSNAME = {dsname|*}
specifies the scope of the issuance of volume
selection analysis messages in relation to a data
set.
dsname
limits the scope volume selection analysis
messages to the named data set.
*
1 =
4 =
7 =
10=
13=
16=
19=
22=
25=
28=
31=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
2 =
5 =
8 =
11=
14=
17=
20=
23=
26=
29=
32=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
3 =
6 =
9 =
12=
15=
18=
21=
24=
27=
30=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
uuuu
STORGRP
enabled
disabled
quiesced
sysname
The systems or system groups in the SMS
complex.
System action: The system continues processing.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 5,8,9
439
IGD002I
IGD002I
COPYTARG
Copy target
DUMMY
STORGRP TYPE SYSTEM= 12345678
sgname
type ssssssss
Explanation:
.
D
Q
1 =
4 =
7 =
10=
13=
16=
19=
22=
25=
28=
31=
Object
OBJECTB
Object backup
POOL
Pool
TAPE
Tape
VIO
Virtual I/O
Enabled
Disabled
Quiesced
OBJECT
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
2 =
5 =
8 =
11=
14=
17=
20=
23=
26=
29=
32=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
3 =
6 =
9 =
12=
15=
18=
21=
24=
27=
30=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
hh.mm.ss
The time in hours (0023), minutes (0059),
and seconds (0059). If the time-of-day clock
is not working, hh.mm.ss appears as 00:00:00.
id
440
TYPE
type
SYSTEM=12345678
ssssssss
sgname
type
Unknown type
UNIT
dev
SYSTEM= 12345678
ssssssss
STORGRP NAME
sgname
IGD002I
The following may appear:
OBJECTB
object backup
POOL
pool
TAPE
tape
enabled
disabled
quiesced
1 =
4 =
7 =
10=
13=
16=
19=
22=
25=
28=
31=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
2 =
5 =
8 =
11=
14=
17=
20=
23=
26=
29=
32=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
3 =
6 =
9 =
12=
15=
18=
21=
24=
27=
30=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sgname
A storage group.
type
volser
dev
enabled
disabled
quiesced
sysname
The systems and system groups in the SMS
complex.
If the operator entered the DISPLAY
SMS,STORGRP(sgname),LISTVOL command and:
v storage group sgname is not defined to the active
configuration, message IGD004I COMMAND
REJECTED STORAGE GROUP sgname IS NOT
DEFINED appears instead of this message display.
v storage group sgname is defined to the active
configuration but contains no volumes, then the
display line THE ABOVE STORAGE GROUP(S)
CONTAIN(S) NO VOLUMES appears.
v storage group is defined to the active configuration,
but is an object or object backup storage group, then
the display line LISTVOL IS IGNORED FOR
OBJECT AND OBJECT BACKUP STORAGE
GROUPS appears.
object
Chapter 12. IGD Messages
441
IGD002I
System action: System continues processing.
1 =
4 =
7 =
10=
13=
16=
19=
22=
25=
28=
31=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
2 =
5 =
8 =
11=
14=
17=
20=
23=
26=
29=
32=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
3 =
6 =
9 =
12=
15=
18=
21=
24=
27=
30=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
hh.mm.ss
The time in hours (00-23), minutes (00-59),
and seconds (00-59). If the time of day clock is
not working, hh.mm.ss will appear as 00.00.00.
hh.mm.ss
The time in hours (00-23), minutes (00-59),
and seconds (00-59). If the time of day clock is
not working, hh.mm.ss will appear as 00.00.00.
id
id
libname
The library.
Source: DFSMSdfp
class
Routing Code: 2
TAPE
SYSTEM=12345678
442
Tape
enabled
disabled
Pending offline
sysname
The systems or system groups in the SMS
complex.
If the operator entered the DISPLAY
SMS,LIBRARY(libname),LISTDRI command and
libname is the name of a pseudo library, then the
IGD002I
message IGD004I THE SPECIFIED OPTICAL
LIBRARY IS NOT A REAL LIBRARY appears instead of
this message display. No pseudo library can be
displayed.
If issuing a DISPLAY SMS,LIB(ALL) command and
there is a pseudo library in the configuration, then the
message libname OPTICAL LIBRARY IS NOT A REAL
LIBRARY appears. No pseudo libraries can be
displayed.
System action: System continues processing.
Source: Storage Management Subsystem (SMS)
Routing Code: 2
hh.mm.ss
The time in hours (00-23), minutes (00-59),
and seconds (00-59). If the time of day clock is
not working, hh.mm.ss will appear as 00.00.00.
id
IGD002I
Explanation:
LIBRARY
libname
CLASS
class
SYSTEM= 1 2 3 4 5 6 7 8
s s s s s s s s
libname
A library.
OPTICAL
Optical
LIBRARY SYSTEM= 1 2 3 4 5 6 7 8
libname
s s s s s s s s
TAPE
s
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
2 =
5 =
8 =
11=
14=
17=
20=
23=
26=
29=
32=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
3 =
6 =
9 =
12=
15=
18=
21=
24=
27=
30=
Tape
enabled
disabled
Pending offline
drvname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
A drive.
libname
The library in which drvname resides.
s
sysname
The systems or system groups in the SMS
complex.
If the operator entered either the DISPLAY
SMS,LIBRARY(libname), LISTDRI or the DISPLAY
SMS,LIBRARY(ALL),LISTDRI command and no drives
Chapter 12. IGD Messages
443
IGD002I
were defined to the library, then THE ABOVE
LIBRARY(S) CONTAIN(S) NO DRIVES appears.
If the operator entered either the DISPLAY
SMS,LIBRARY(libname), LISTDRI or the DISPLAY
SMS,LIBRARY(ALL),LISTDRI command and no drives
were defined to the active configuration, then NO
DRIVES DEFINED IN SMS ACDS appears.
The LISTDRI keyword and processing is ignored for
pseudo libraries. If the operator entered the DISPLAY
SMS,LIBRARY(ALL),LISTDRI command and there are
pseudo libraries in the configuration, then LISTDRI IS
IGNORED FOR PSEUDO AND TAPE LIBRARIES will
appear.
The LISTDRI keyword and processing is ignored for
tape libraries. If the operator entered the DISPLAY
SMS,LIBRARY(libname),LISTDRI command and
libname is a tape library, or if the operator entered the
DISPLAY SMS,LIBRARY(ALL),LISTDRI command and
there are tape libraries in the configuration, then
LISTDRI IS IGNORED FOR PSEUDO AND TAPE
LIBRARIES appears.
LIBRARY SYSTEM=12345678
lib
ssssssss
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
2 =
5 =
8 =
11=
14=
17=
20=
23=
26=
29=
32=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
Online
Offline
sysname
The systems or system groups in the SMS
complex.
System action: The system continues processing.
Source: DFSMSdfp
Routing Code: 2
IGD002I
3 =
6 =
9 =
12=
15=
18=
21=
24=
27=
30=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
444
NO LIBRARIES DEFINED IN
THE SMS ACDS.
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
IGD002I
v being displayed inline (in other words, not in
a display area) on a display console.
System action: The system rejects the command.
IGD002I
Routing Code: 2
Source: DFSMSdfp
IGD002I
hh.mm.ss
The time in hours (00-23), minutes (00-59),
and seconds (00-59). If the time of day clock is
not working, hh.mm.ss will appear as 00.00.00.
id
IGD002I
hh.mm.ss
The time in hours (0023), minutes (0059), and
seconds (0059). If the time-of-day clock is not
working, hh.mm.ss appears as 00:00:00.
id
VOLSELMSG = ({ON|OFF},{nnnn|ALL})
Controls the issuance of summarized and detailed
analysis messages where:
ON turns on the issuance of the summarized
and detailed analysis messages for volume
selection
OFF turns off the issuance of the summarized
and detailed analysis messages for volume
selection. This is the default
445
IGD004I
nnnn is the number of volumes to be included
in the detailed analysis messages. The range of
values is 065535. The default is 0 which
indicates that only summarized analysis will be
issued
ALL indicates that all of the volumes that were
used by volume selection are included in the
detailed analysis messages
Note: When VOLSELMSG(ON,nnnnn|ALL) is
specified, nnnnn is greater than zero and
TYPE(ALL) parameter is also specified then
one of JOBNAME, ASID, DSNAME, or
STEPNAME must be specified.
TYPE = {ERROR|ALL}
Specifies whether SMS issues volume selection
messages on failed allocations only or on both
successful and failed allocations and whether SMS
traces all events or only errors. The default is
ERROR.
ERROR indicates to trace error type of trace
entries and issue volume selection analysis
messages for failed allocations only.
ALL indicates to trace all trace entries and
issue volume selection analysis messages for
both successful and failed allocations.
JOBNAME = {jjj|*}
specifies the scope of both tracing and the
issuance of volume selection analysis messages in
relation to jobs.
jjj is the name of a job and scope is limited to
that job
* indicates that scope covers all jobs
ON switches tracing on
OFF discontinues tracing
SIZE = nnnK|M
specifies the size nnn of the trace table. The
increment can be specified in either kilobytes (K) or
megabytes (M). The default is 128K.
nnnK is the size of the trace table in kilobytes.
The value can range from 0K to 255000K. The
value is rounded up to the nearest 4K unit
nnnM is the size of the trace table in
megabytes. The value can range from 0M to
255M. The value will be stored as kilobytes
System action: The system continues processing.
Operator response: None
Application Programmer Response: None.
System programmer response: None.
Problem determination: None
Source: Storage management subsystem (SMS)
Detecting Module: IGDOPCDT
IGD004I
COMMAND REJECTED
STORAGE GROUP sgname
IS NOT DEFINED
ASID = {asid|*}
specifies the scope of both tracing and the
issuance of volume selection analysis messages in
relation to address space. It is activated by
TRACE(ON) or VOLSELMSG(ON). The default is *.
asis is the identifier of an address space and
scope is limited to that address space
* indicates that scope covers all asids
sgname
DSNAME = {dsname|*}
specifies the scope of both tracing and the
issuance of volume selection analysis messages in
relation to data set name.
dsname is the name of a data set and scope is
limited to that data set
* indicates that scope covers all data sets
Source: DFSMSdfp
STEPNAME = {stepname|*}
specifies the scope of both tracing and the
issuance of volume selection analysis messages in
relation to job step.
stepname is the name of a job step and scope
is limited to that step
* indicates that scope covers all job steps
TRACE = stat
specifies one of the following options to enable
tracing. The default is ON.
446
Routing Code: 2
Descriptor Code: 5,8,9
IGD004I
COMMAND REJECTED
{LIBRARY libname | DRIVE drvname}
IS NOT DEFINED IN THE SMS ACDS
IGD004I
drvname
The specified drive name.
IGD004I
COMMAND REJECTED
COMMAND REJECTED
REQUESTED STATUS IS INVALID
FOR OBJECT, OBJECT BACKUP,
AND TAPE STORAGE GROUPS
COMMAND REJECTED
IGD004I
COMMAND REJECTED
OAM EXECUTION FAILED
IGD004I
COMMAND REJECTED
{LIBRARY libname |
DRIVE drvname}
IS NOT CONNECTED TO
ANY SYSTEM.
Routing Code: 2
Source: DFSMSdfp
libname
The specified library name.
Chapter 12. IGD Messages
447
IGD004I IGD007I
drvname
The specified drive name.
IGD005I
COMMAND REJECTED
text
COMMAND REJECTED
volser
448
COMMAND REJECTED
TARGET CONSOLE (DEFAULT IS
MASTER CONSOLE) IS NOT ACTIVE
IGD008I IGD011I
the L=cc/cca/name/name-a parameter is not specified
on the D SMS command, then the target console is the
master console.
System action: The system rejects the command.
Operator response: Make the target console active,
and reissue the command.
Source: DFSMSdfp
Routing Code: 2
sgname
The storage group name.
sysname
The system or system group for which the
command was issued.
state
dsname
Routing Code: 2
Descriptor Code: 5
IGD011I
Routing Code: 2
Descriptor Code: 4
IGD009I
{ACDS|COMMDS} SWITCHED TO
dsname
dsname
The data set name.
System action: The system continues processing with
the a ACDS or COMMDS data set name.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 5
IGD010I
449
IGD012I IGD016I
Routing Code: 2,10
IGD014I
Descriptor Code: 4
IGD012I
COMMAND REJECTED
SMS IS NOT ACTIVE
Source: DFSMSdfp
Routing Code: 2
cde
Descriptor Code: 4
IGD015I
COMMAND REJECTED
VSAM CF EXECUTION FAILED
450
IGD017I IGD022I
Detecting Module: IGDOPCDS
Routing Code: 2
IGD017I
|
|
IGD019I
|
|
|
|
|
Dsn-1
SCDS data set name
|
|
Dsn-2
ACDS data set name
Source: DFSMSdfp
rc
rsnc
IGD020I
Descriptor Code: 4
IGD022I
451
IGD023I IGD027I
Source: DFSMSdfp
Routing Code: 2,10
Descriptor Code: 4
IGD023I
rsnc
Source: DFSMSdfp
Routing Code: 2,10
IGD026I
Descriptor Code: 4
| IGD024I
|
|
|
|
|
|
| Source: DFSMSdfp
Descriptor Code: 4
| Descriptor Code: 4
IGD025I
452
IGD027I
IGD028I IGD029I
v ERROR IS DUPLICATE KEYWORD : keywd
v DEVSERV SMS
v SETSMS
v VARY SMS
v SET SMS
syntax
The incorrect syntax.
Source: DFSMSdfp
IGD028I
Descriptor Code: 4
value
The value for the keyword.
IGD029I
dsname
The name of a data set.
nnnnn
number of volumes to be included in the detailed
analysis messages
System action: The system rejects the command.
v DISPLAY SMS
Chapter 12. IGD Messages
453
IGD030I IGD031I
Operator response: Correct the syntax error and
reissue the command.
nnnnn
number of volumes to be included in the detailed
analysis messages
Source: DFSMSdfp
IGD031I
454
|
|
|
|
|
|
IGD031I
In the message text:
id
ASID = {asid | *}
Specifies the scope of tracing and the issuance of
volume selection analysis messages in relation to
address space. It is activated by TRACE(ON) or
VOLSELMSG(ON). The default is *.
asid
Scope is limited to the specified address
space.
*
455
IGD031I
SCHEDS = stat
Scheduling services, system select.
ALL
indicates that detailed volume selection
analysis messages will be issued for all
volumes that were used by volume selection.
VTOCL = stat
VTOC and data set services, allocate an existing
data set.
DSNAME
specifies the scope for volume selection analysis
messages in relation to a data set.
VTOCD = stat
VTOC and data set services, delete an existing
data set.
dsname
indicates that scope is limited to the specified
data set name.
VTOCR = stat
VTOC and data set services, rename an existing
data set.
VTOCC = stat
VTOC and data set services, create a new data
set.
STEPNAME
specifies the scope for volume selection analysis
messages in relation to job step.
VTOCA = stat
VTOC and data set services, add a volume to a
data set.
stepname
indicates that scope is limited to the specified
job step.
RCD = stat
SMS recording services or SMS fast VTOC and
VVDS access.
DCF = stat
The device control facility.
DPN = stat
The device pool select.
TVR = stat
A tape volume record update.
DSTACK = stat
Data set stacking SSI.
Routing Code: 2
Descriptor Code: 5,8,9
UAFF = stat
Unit affinity.
IGD031I
| DEBUG= stat
Debug service.
|
The following will be a display of the parameters in
SYS1.PARMLIB member IGDSMSxx at IPL time and
SET SMS=xx.
VOLSELMSG
ON
summarized and detailed volume selection
analysis messages will be issued.
OFF
summarized and detailed volume selection
analysis messages will not be issued. This is
the default value.
nnnnn
is the number of volumes which are included in
the scope of the issuance of detailed volume
selection analysis messages. The range of
value is 065535. The default is 0 which
indicates that only summarized volume
selection analysis messages will be issued.
456
|
|
|
|
|
|
|
SMS PARAMETERS id
ACDS = acdsname
COMMDS = cmdsname
INTERVAL = nnn
DINTERVAL = nnn
PDSE_BMFTIME = nnnn |
PDSE1_BMFTIME = nnnn
CACHETIME = nnnnn
PDSE_LRUTIME = nn |
PDSE1_LRUTIME = nn
PDSE_LRUCYCLE = nnn |
PDSE1_LRUCYCLE = nnn
SMF_TIME = {YES|NO}
CF_TIME = nnnnn
LOCAL_DEADLOCK = nnnn
GLOBAL_DEADLOCK = nnnn
REVERIFY = {YES|NO}
ACSDEFAULTS = {YES|NO}
DSNTYPE = {LIBRARY|PDS}
USE_RESOWNER = {YES|NO}
PDSESHARING =
{NORMAL|EXTENDED}
OVRD_EXPDT = {YES|NO}
RLS_MAX_POOL_SIZE = nnnnMB
IGD031I
SYSTEMS = {8 | 32}
RLSINIT = {YES | NO}
PDSE_HSP_SIZE = nnnMB |
PDSE1_HSP_SIZE = nnnMB
COMPRESS =
{GENERIC | TAILORED}
LOG_OF_LOGS = logstreamid
QTIMEOUT = nnn
RLSTMOUT = nnnn
TVSNAME = nnn AKP = nnn
TV_START_TYPE = {WARM | COLD}
MAXLOCKS = (max,incr)
GDS_RECLAIM = {YES | NO}
DSSTIMEOUT = nnnn
FAST_VOLSEL = {ON | OFF}
CICSVR_RCDS_PREFIX =
{rcds_prefix | DWW}
CICSVR_GRPNAME_SUFFIX =
{grpname_suffix | PROD}
CICSVR_ZZVALUE_PARM =
{zzvalue | blank string}
CICSVR_UNDOLOG_CONTROL =
{undo log string | blank string}
CICSVR_UNDOLOG_PREFIX =
{undo log prefix | DWW}
CICSVR_BACKOUT_CONTROL =
{back out control string | blank string}
CICSVR_GENERAL_CONTROL =
{general control string | blank string}
RlsAboveTheBarMaxPoolSize =
nnnnnnnnMB
RlsFixedPoolSize =
nnnnnnnnMB
PDSE_MONITOR =
(YES | NO,interval,duration) |
PDSE1_MONITOR =
(YES | NO,interval,duration)
PDSE_DIRECTORY_STORAGE =
nnnnM |
PDSE1_DIRECTORY_STORAGE =
PDSE_BUFFER_BEYOND_CLOSE =
{YES | NO} |
PDSE1_BUFFER_BEYOND_CLOSE =
{YES | NO} nnnnM
BLOCKTOKENSIZE =
{REQUIRE | NOREQUIRE}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| PDSE_LRUTIME = nn | PDSE1_LRUTIME = nn
|
Specifies the number of seconds, nn, that the buffer
|
managerment facility(BMF) waits Between calls to
|
the BMF data space cache LRU (least recently
|
used) routine in SMSPDSE Or SMSPDSE1 address
|
space. The value of nn is in the range of 5-60. The
|
default is 15 seconds.
PDSE_LRUCYCLE = nnn | PDSE1_LRUCYCLE = nnn
Specified the maximum number of times, nnn, that
the buffer manager facility (BMF) least Recently
used (LRU) routine passes over inactive buffers
before making them available for Reuse in
SMSPDSE or SMSPDSE1 address space. The
value of nn in the range of 5-240. The default is
240 cycles.
SMF_TIME = {YES|NO}
Indicates whether DFSMSdfp creates SMF type-42
records at the expiration of the SMF time interval,
synchronized with SMF and RMF data intervals.
The default value is YES.
457
IGD031I
YES
DFSMSdfp listens for the SMF
event-notification signal and creates the
specified SMF records.
NO
DFSMSdfp does not create any SMF type-42
records.
CF_TIME = nnnnn
Displays the interval in seconds, nnnnn, between
recording SMF record 42 (subtypes 15, 16, 17, 18)
for use of the coupling facility by the SMSVSAM
address space. The default is 3600 seconds. If
SMF_TIME is YES, the CF_TIME parameter is
ignored and recording is based solely on the
issuance of the SMF ENF signal.
LOCAL_DEADLOCK = nnnn
Displays the length in seconds, nnnn, of the local
deadlock detection interval. The default is 15
seconds.
GLOBAL_DEADLOCK = nnnn
Displays the number of local deadlock cycles, nnnn,
that must expire before global deadlock detection is
to be performed. The default is 4 cycles.
REVERIFY = {YES|NO}
Indicates whether SMS verifies a users authority to
allocate a new data set and use a storage or
management class at both job interpretation time
and run time or only at job interpretation time. The
default value is NO.
YES
SMS verifies a users authority at both job
interpretation time and run time.
NO
SMS verifies a users authority only at
interpretation time.
ACSDEFAULTS = {YES|NO}
Indicates whether SMS initializes the following
automatic class selection (ACS) routine variables
from an additional call to RACF, a component of the
Security Server for z/OS. The default value is NO.
&APPLIC
&DEF_DATACLAS
&DEF_MGMTCLAS
&DEF_STORCLAS
YES
SMS retrieves these ACS routine variables
from RACF.
NO
SMS does not retrieve any ACS routine
variables from RACF.
DSNTYPE = {LIBRARY|PDS}
Indicates whether newly created SMS-managed
data sets are to be PDSEs (LIBRARY) or non-PDSE
data sets (PDS). The default value is PDS.
458
LIBRARY
Newly created SMS-managed data sets default
to PDSEs.
PDS
Newly created SMS-managed data sets default
to non-PDSEs.
USE_RESOWNER = {YES|NO}
Indicates whether SMS determines the owner (user
or group defined by RACF) of an SMS-managed
data set protected by the profile. The default value
is YES.
YES
SMS extracts the owner of an SMS-managed
data set from the owner profile.
NO
The owner of an SMS-managed data set is the
user ID.
PDSESHARING = {NORMAL|EXTENDED}
Indicates how PDSEs are shared across systems in
a sysplex. The default value is NORMAL.
NORMAL
Users share read access to PDSEs across
systems in the sysplex.
EXTENDED
Users share read and write access to PDSEs
across systems in the sysplex.
OVRD_EXPDT = {YES|NO}
Indicates whether an expiration date or retention
period for SMS-managed DASD data sets is
overridden when deletion is requested through job
control language (JCL), supervisor call instruction
(SVC 99), the IEHPROGM utility, or interactive
system productivity facility (ISPF) or PDF. The
default value is NO.
YES
Data sets are deleted whether or not the
expiration date or retention period has passed.
NO
Any expiration date or retention period is
honored.
RLS_MAX_POOL_SIZE = nnnn MB
Displays the maximum size, in megabytes, of the
SMSVSAM local buffer pool. SMSVSAM attempts
not to use more storage for buffers than this limit. If
nnnn is less than 10, the maximum size is 10 MB,
and if nnnn is greater than 1500, the maximum size
is 9999 MB; otherwise, the actual maximum size is
displayed.
SYSTEMS = {8|32}
Displays the maximum number of unique system
names and system group names that you can
specify in the SMS configuration.
IGD031I
RLSINIT = {YES|NO}
Indicates whether the SMSVSAM address space is
started as part of the system initialization. The
default value is NO.
YES
SMSVSAM SERVER is initialized at IPL time.
NO
SMSVSAM SERVER is not active after IPL.
AKP = nnn
Specifies the activity-keypoint trigger value, which is
the number of logging operations between the
taking of keypoints. The value is in the range
20065535. The default is 1000.
TV_START_TYPE = {WARM | COLD}
Specifies the type of start that DFSMStvs is to
perform. The default is WARM.
WARM
DFSMStvs reads its undo log and processes
the information it finds in accordance with the
information that resource recovery services
(RRS) has about any outstanding units of
recovery.
COLD
DFSMStvs deletes any information that
remains in the undo log and starts as if the log
were empty.
MAXLOCKS = (max,incr)
Specifies two values: the maximum number of locks
that a single unit of recovery can hold before the
warning message IGW859I is issued to the system
console, and an increment value. After the
maximum is reached, the warning message is
issued every time the number of locks held over
and above the maximum is the multiple of the
increment. The max and incr values are in the
range 0999999. The default value for both is 0. It
is invalid for max to be 0 and incr to be greater
than 0.
CICSVR_INIT = {YES|NO}
Indicates whether the CICSVR address space is
started as part of the system initialization. The
default value is NO.
YES
The CICSVR address space is active after IPL.
NO
The CICSVR address space is not active after
IPL.
CICSVR_DSNAME_PREFIX = {user prefix|DWW.}
Displays the prefix for all CICSVR data set names
that CICSVR creates. The default value is DWW..
Rls_DynamicCfCacheReassign = {YES|NO}
Indicates whether the dynamic cache can be
reassigned during SMSVSAM processing. The
default value is NO.
Rls_MaxCfFeatureLevel = {cache feature|Z}
Indicates the cache feature level. The default value
is Z.
GDS_RECLAIM = {YES|NO}
Indicates whether generation data set (GDS)
reclaim processing is applied. The default value is
YES.
YES
GDS reclaim processing is done.
Chapter 12. IGD Messages
459
IGD031I
NO
GDS reclaim processing is not done.
DSSTIMEOUT = nnn
Specifies the number of seconds that the dss
component of DFMSMS will wait during backup
processing for quiesce data set requests to
complete.
| FAST_VOLSEL = ON | OFF
Specifies whether the summarized and detail
|
volume selection analysis messages will be issued
|
or not. Nnnn or ALL is the number of volumes or all
|
volumes which are included in the scope of
|
issuance of the detailed volume selection analysis
|
messages. The range is 0-65535. The default
|
values is (OFF,0).
|
| CICSVR_RCDS_PREFIX = rcds_prefix | DWW
Specifies a prefix of CICSVR Recovery Control
|
Data Set (RCDS) names that CICSVR server
|
address space will use to allocate the RCDSs to
|
the CICSVR server.
|
| CICSVR_GRPNAME_SUFFIX = cicsvr_grpname_suffix
Specifies the suffix of CICSVR XCF group names
|
that the CICSVR address space use to recreate a
|
unique XCF group name per the sysplex and
|
connect to the sysplex. The specified suffix is
|
activated when the CICSVR server address space
|
is next started.
|
| CICSVR_ZZVALUE_PARM = zzvalue_string
Specifies the ZZVALUE string which is a pair of
|
name and value, or one control ZZVALUE value
|
that specifies an action to take. And this value
|
maintains the ZZVALUE table and the diagnostic
|
data set.
|
| CICSVR_UNDOLOG_CONTROL = undo log string
Specifies the parameters and service functions to
|
control CICSVR UNDO logging. The CICSVR
|
address space will decode the logging control
|
string, and activate the parameters and execute the
|
service function. It is a string of 17 characters long.
|
The default string is a blank string.
|
| CICSVR_UNDOLOG_PREFIX = undolog prefix | DWW
Specifies the CICSVR UNDO log name prefix that
|
CICSVR server address space will use to
|
determine the log stream name which should be
|
written to by CICSVR UNDO logging. It is a string
|
of 8 characters long. The default string is DWW.
|
| CICSVR_BACKOUT_CONTROL = backout control
| string
Specifies the parameters and service functions to
|
control CICSVR batch backout logging. The
|
CICSVR address space will decode the logging
|
control string, and activate the parameters and
|
execute the service function. It is a string of 17
|
characters long. The default string is a blank string.
|
460
IGD032D IGD035I
an informational message only.
System programmer response: Verify the values of
the parameters. Take action if needed.
Problem determination: None
Source: Storage management subsystem (SMS)
Detecting Module: IGDSSIPO, IGDSSIDI
Routing Code: 2
Descriptor Code: 5,8,9
IGD032D
461
IGD036I IGD040D
IGD036I
JES3 IS ACTIVE
Explanation: An attempt was made to start storage
management subsystem (SMS) using the SET SMS
command when SMS was inactive and JES3 was
active.
System action: The system does not start SMS. The
system continues processing.
Operator response: Notify the system programmer.
System programmer response: JES3 must be
inactive before SMS can be started. Deactivate JES3,
then start SMS using the SET SMS command. Restart
JES3 using a hot start.
Source: DFSMSdfp
IGD037I
IGD040D
UNABLE TO COMPLETE
CONFIGURATION REQUEST: text REPLY U TO RETRY OR C TO
PURGE REQUEST
IGD038E
sysname
The current system.
system-group
The current system group.
System action: The system continues processing but
462
IGD041I IGD044I
request to update the active configuration failed. Then
tell the operator which response to enter for this
message.
Source: DFSMSdfp
Routing Code: 1
Descriptor Code: 2
IGD041I
Routing Code: 9
dsname
Descriptor Code: 2
The data set name.
IGD044I
Descriptor Code: 4
In the message text:
IGD042I
dsname
The SCDS, ACDS, or COMMDS being
accessed
System action: Access to the control data set fails.
User response: Contact the storage administrator.
Operator response: Contact the storage
administrator.
Application Programmer Response: The storage
administrator must not attempt to access a configuration
or communications data set which supports more than
eight systems on a down-level DFSMS/MVS or DFP
system or on a DFSMS/MVS 1.3.0 system running in
compatibility mode. Do one of the following:
1. Locate a configuration or communications data set
which has not been converted to support more than
eight systems and activate it
2. If the system is running DFSMS/MVS 1.3.0 and the
configuration must be activated, restart SMS using
Chapter 12. IGD Messages
463
IGD045I IGD049I
the SET SMS command and an IGDSMSxx member
of SYS1.PARMLIB with SYSTEMS(32) specified
Source: Storage Management Subsystem (SMS)
IGD045I
Descriptor Code: 4
IGD047I
IGD048I
Descriptor Code: 4
IGD049I
sgname
The storage group name.
volser
libname
drvname
The specified drive name.
System action: The system ignores the request.
Operator response: Verify the storage group name,
volume serial number, library name, or drive name with
464
IGD050I IGD052I
v In error
Routing Code: 2
v Empty
Descriptor Code: 4
IGD051I
Descriptor Code: 4
IGD050I
sgname
The storage group name.
sysname
The system or system group name.
libname
drvname
System action: The system ignores the request.
Source: DFSMSdfp
Descriptor Code: 4
465
IGD053I IGD056I
IGD053I
Source: DFSMSdfp
IGD055I
system-group
The system group to which the current system
belongs.
sysname
The current system.
Descriptor Code: 4
IGD056I
IGD054I
dsname
The data set name.
dsname
The data set name.
466
|
|
|
|
|
|
IGD057I IGD058I
about this message, and ask how you should respond
to the IGD040D, IGD070D, or IGD072A message that
follows.
{SCDS|ACDS|COMMDS} dsname
RESOURCE UNAVAILABLE - RETURN
CODE rc REASON CODE rsnc
dsname
The data set name.
rc
rsnc
rsnc
zzz
|
|
|
|
|
|
Descriptor Code: 4
Source: DFSMSdfp
Descriptor Code:
467
IGD059I IGD064I
IGD059I
mmmmmm
468
Descriptor Code: 4
IGD062I
IGD065I IGD067D
In the message text:
IGD066I
dsname
The SCDS, ACDS, or COMMDS being
accessed
System action: The system issue message IGD067D
and waits for a reply.
User response: Contact the storage administrator.
Operator response: Contact the storage
administrator.
IGD065I
dsname
The SCDS, ACDS, or COMMDS being saved
469
IGD068I IGD070D
Note: If the data set is not saved (for example, the
update operation is cancelled), then the
configuration or communications data set is not
reformatted.
System action: The system waits for a reply. If the
reply is Y access to the SCDS, ACDS, or COMMDS is
allowed and processing continues. If the reply is N
access to the SCDS, ACDS, or COMMDS is denied and
message IGD065I is issued.
User response: Contact the storage administrator.
Operator response: Contact the storage
administrator.
Application Programmer Response: The storage
administrator must determine whether or not the
configuration or communications data set should be
converted to a format which supports more than eight
systems. If this is allowable, the storage administrator
should reply Y. If not, the storage administrator should
reply N and do one of the following:
1. reissue the requested operation specifying the name
of an SCDS, ACDS, or COMMDS which has already
been converted
2. restart SMS using the SET SMS command and an
IGDSMSxx member of SYS1.PARMLIB with
SYSTEMS(8) specified
Source: Storage Management Subsystem (SMS)
IGD068I
470
IGD071I IGD073I
about this message and the message that preceded it,
and ask which reply to enter.
Application Programmer Response: Examine the
message that preceded IGD070D to determine the
reason for the error, and to decide which reply the
operator should enter. Keep in mind the systems
response to a particular operator reply and the existing
conditions under which the reply is entered:
v If the operator specifies U to retry, the system
reinitiates the failing operation.
v If the operator specifies C to cancel during storage
management subsystem initialization, the system
allows that initialization to complete. However,
communication between systems in the storage
management subsystem complex is suspended until
the operator specifies a new COMMDS or INTERVAL
via the SETSMS command.
v If the operator specifies C to cancel during SETSMS
command processing, the system ignores the failing
operation, and continues processing with the current
COMMDS.
v If the operator specifies C to cancel during interval
processing: communication between systems in the
storage management subsystem complex is
suspended until the operator specifies a new
COMMDS or INTERVAL via the SETSMS command.
Source: DFSMSdfp
Source: DFSMSdfp
Routing Code: 1
Routing Code: 1
Descriptor Code: 2
Descriptor Code: 2
IGD071I
IGD073I
dsname
rsnc
Source: DFSMSdfp
Chapter 12. IGD Messages
471
IGD074D IGD075D
Operator response: Tell the system programmer
about this message.
System programmer response: Use the reason code
rsnc from intersystem communication and the logrec
data set to determine why the COMMDS contains
incorrect information. z/OS DFSMSdfp Diagnosis
contains explanations of SMS intersystem
communication reason codes.
Source: DFSMSdfp
Descriptor Code: 4
Source: DFSMSdfp
Routing Code: 1
IGD074D
value
472
Descriptor Code: 2
IGD075D
value
IGD076D IGD079D
IGD076D
Descriptor Code: 4
IGD078D
value
Detecting Module: 1
IGD079D
Source: DFSMSdfp
Routing Code: 2
SPECIFY IGDSMSxx SUFFIX OR C TO
CANCEL
Source: DFSMSdfp
473
IGD080I IGD082D
new IGDSMSxx suffix. If the operator specifies a new
suffix, SMS initialization will try to read that IGDSMSxx
member. If the operator specifies C to cancel, then
SMS initialization will fail.
Operator response: Specify a new IGDSMSxx suffix
or C to cancel.
Source: DFSMSdfp
Routing Code: 1
Descriptor Code: 2
IGD080I
cde
REPLY keyword(value), OR D TO
DEFAULT THE VALUE, OR C TO
CANCEL ALL TRANSACTIONAL VSAM
VALUES
keyword
One of the following keywords:
474
IGD083D IGD084D
v LOG_OF_LOGS
IGD083D
v QTIMEOUT
v AKP
v TV_START_TYPE
value
A parameter value for a keyword.
System action: The system waits for the operator to
reply.
Operator response: Correct the error by replying with
the keyword and value, or reply with D to use the default
value; if the reply is one of these, the system continues
to process the other DFSMStvs parameter specified in
the PARMLIB member. If the reply is C, the system
ignores all other DFSMStvs parameters specified in the
PARMLIB member and keeps the previous DFSMStvs
values. Tell the system programmer about this error.
System programmer response: Fix the error in the
PARMLIB member.
Problem determination: None
Source: DFSMSdfp
Detecting Module: IGDSSIPO, IGDSSITV
IGD083D
IGD084D
value
The value of the TVSNAME parameter.
System action: The system waits for the operator to
reply.
Operator response: Correct the error by replying with
TVSNAME(value), and the system continues to process
the other DFSMStvs parameters specified in the
PARMLIB member. If the reply is C, the system ignores
all other DFSMStvs parameters specified in the
PARMLIB member and keeps the previous DFSMStvs
parameter values. Tell the system programmer about
this error.
System programmer response: Fix the error in the
PARMLIB member.
Problem determination: None
Source: DFSMSdfp
Detecting Module: IGDSSIPO, IGDSSITV
475
IGD085D IGD086I
IGD085D
REPLY keyword(value,value), OR D TO
DEFAULT THE VALUE, OR C TO
CANCEL ALL TRANSACTIONAL VSAM
VALUES
Source: DFSMSdfp
keyword
A keyword that specifies a parameter, such as
MAXLOCKS.
value
A parameter value.
System action: The system waits for the operator to
reply.
Operator response: Reply keyword(value,value) to
correct the error, or reply with D to use the default value;
if the reply is one of these, the system continues to
process the other DFSMStvs parameter specified in the
PARMLIB member. If the reply is C, the system ignores
all other DFSMStvs parameters specified in the
PARMLIB member and keeps the previous DFSMStvs
values. Tell the system programmer about this error.
System programmer response: Fix the error in the
PARMLIB member
Problem determination: None
Source: DFSMSdfp
Detecting Module: IGDSSIPO, IGDSSITV
IGD085D
476
IGD086I
IGD100I IGD101I
IGD100I
Routing Code: 2
Descriptor Code: 4
IGD100I
dev
ddname
The specified DDNAME.
Routing Code: 2
dev
Descriptor Code: 4
IGD101I
ddname
scname
The specified storage class.
mcname
The specified management class.
dcname
The specified data class.
blank
Blank characters.
ddname
The specified DDNAME.
scname
The specified storage class.
dcname
The specified data class.
mcname
The specified management class.
dcname
The specified data class.
477
IGD103I IGD106I
volid
IGD105I
ddname
The specified DDNAME.
Source: DFSMSdfp
Source: DFSMSdfp
Routing Code: 2
Routing Code: 2
Descriptor Code: 4
Descriptor Code: 4
IGD106I
IGD104I
478
IGD107I IGD300I
Routing Code: 2
COMPONENT NAME=SMS
COMPONENT ID=28462
ACTIVE LOAD MODULE
NAME={IGDZILLA|UNKNOWN}
ADDRESS=adr1
CSECT IN ERROR
DESCRIPTION=description
NAME=name ADDRESS=adr2
OFFSET=offset
ASSEMBLY DATE=mmddyy
PTF LEVEL=ptf
PSW AT TIME OF ERROR
pppppppp pppppppp
DATA AT PSW
adr3-dddddddd dddddddd dddddddd
Descriptor Code: 4
IGD107I
GPR
GPR
GPR
GPR
00-03
04-07
08-11
12-15
gpr00
gpr04
gpr08
gpr12
gpr01
gpr05
gpr09
gpr13
gpr02
gpr06
gpr10
gpr14
gpr03
gpr07
gpr11
gpr15
Source: DFSMSdfp
Routing Code: 2
cde
asid
adr1
description
name
adr2
dsname
The data set name
offset
mmddyy
ptf
pppppppp
adr3
dddddddd
gprnn
ddname
The specified DDNAME.
Descriptor Code: 4
IGD108I
dsname CATALOGED,
DDNAME=ddnamexx VOLUME SERIAL
NUMBERS = ser[,ser...]
ddnamexx
The specified DDNAME
ser The volume serial number.
System action: The system continues processing.
Routing Code: 2
Descriptor Code: 4
IGD300I
479
IGD301I IGD303I
System action: The request fails.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD302I
Source: DFSMSdfp
Routing Code: 2,10
Descriptor Code: 4
IGD301I
dsname
volser
dsname
The data set name.
System action: The allocation fails.
Application Programmer Response: If the data set
does not need to be SMS-managed, specify a non-SMS
managed volume and resubmit the allocation request.
If the data set is to be SMS-managed, either modify the
data set type so that the data set can be managed by
by SMS, or determine an appropriate storage class and
resubmit the allocation request. If the storage class
selection routine should have selected a storage class
for this data set allocation, it may need to be corrected.
Contact your storage administrator for assistance.
If the data set is not eligible to be SMS-managed,
specify a non-SMS managed volume and resubmit the
allocation request. Not all data sets can be
SMS-managed. The following data sets do NOT qualify:
v Unmovable data sets
v Data sets with absolute track allocations
v ISAM data sets
v CVOLs
dsname
480
IGD304I IGD306I
Application Programmer Response: If the data set is
supposed to be SMS managed, specify a storage class
or determine why a storage class was not derived for
the data set.
Source: DFSMSdfp
dsn2
The referenced data set.
System action: Allocation of the data set fails.
User response: Do one of the following:
Routing Code: 2
Descriptor Code: 4
IGD304I
dsn2
rc
Descriptor Code: 4
rsnc
IGD305I
callernm
mtb
probid
dsn1
The referencing data set.
481
IGD307I IGD309I
the logrec data set for information about the error that
occurred. Depending on the ERRMODNM value, the
return and reason code can be found in one of the
following locations:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Source: DFSMSdfp
Routing Code: 11
Descriptor Code: 4
IGD308I
dsname
Source: DFSMSdfp
userid
func
Descriptor Code: 4
rc
rsnc
IGD307I
Source: DFSMSdfp
Descriptor Code: 4
exitname
The installation exit.
IGD309I
rc
482
Routing Code: 2
IGD310I IGD312I
Explanation: The creation of SMS managed data sets
is not allowed within the scope of a JOBCAT or
STEPCAT.
IGD311I
rc1
rsnc1
Routing Code: 2
callernm
Descriptor Code: 4
mtb
rc2
rsnc2
probid
IGD310I
scname
mcname
dsname
The data set name.
System action: The allocation fails.
Application Programmer Response: If the data set
does not have to be SMS managed, resubmit the
allocation request without using the STORCLAS and
MGMTCLAS parameters. If the data set should be SMS
managed, modify that data set so that it becomes
eligible to be SMS managed.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
483
IGD313I IGD317I
SMS error recovery took place.
Source: DFSMSdfp
Routing Code: 2
Source: DFSMSdfp
Descriptor Code: 4
IGD315I
dsname
The data set name.
IGD316I
Source: DFSMSdfp
Routing Code: 2
Source: DFSMSdfp
Descriptor Code: 4
IGD317I
IGD314I
dsname
The data set name.
System action: The allocation fails.
Application Programmer Response: If the data class
was explicitly specified, it should be removed from the
request. The data class selection routine may be in
error if it should have selected a different data class for
this data set.
484
Routing Code: 2
Descriptor Code: 4
IGD318I IGD501I
IGD318I
IGD330I
Source: DFSMSdfp
Descriptor Code: 6
Descriptor Code: 4
IGD501I
IGD320I
Descriptor Code: 4
485
IGD502I IGD604I
IGD502I
dsname
The data set name.
rc
rsnc
rc
Source: DFSMSdfp
Routing Code: 2,10
Descriptor Code: 4
IGD603I
Source: DFSMSdfp
Routing Code: 10,11
Descriptor Code: 6
IGD601I
rsnc
rsnc
rsnc
486
IGD605I IGD703D
Routing Code: 2,10
Descriptor Code: 4
IGD605I
dsname
The data set name.
rc
rsnc
rsnc
dev
rc
rsnc
Descriptor Code: 4
IGD701I
487
IGD704D IGD706D
v Enter U to retry that particular AOMSERV request.
Source: DFSMSdfp
Descriptor Code: 2
IGD705D
Descriptor Code: 2
Source: DFSMSdfp
id
IGD704D
488
IGD800I IGD01001I
to determine the appropriate response.
Application Programmer Response: Examine any
preceding messages to determine the reason for the
error. Then have the operator do one of the following:
v Enter U to retry the particular AOMSERV request.
v Enter C to cancel the particular AOMSERV request.
v Enter S to suspend the record SMF statistics task.
The task will wait for the operator to enter the
SETSMS CACHETIME command. The message will
be repeated every xx minutes depending on what
INTVAL(xx) value was set in the SMFPRMxx
member.
v Enter T to end the record SMF statistics task. This
causes the task to go into an infinite wait state. The
task will not be restarted until the SMS address
space is restarted.
v Enter F to force the specified SSID off. The record
SMF statistics task will no longer attempt to obtain
statistics for this subsystem.
Source: DFSMSdfp
IGD800I
Descriptor Code: 4
IGD900I
IGD903I
489
IGD01004I IGD01010I
specified and the reason code specified. If an ACS
routine failed the allocation request, the reason code is
the value that was in the EXIT CODE statement of that
ACS routine. If an ACS installation exit failed the
allocation request, then the reason code is the contents
of GPR 0, which were returned by that installation exit.
IGD01007I
rsnc
text
Descriptor Code: 4
IGD01008I
IGD01004I
text
text
Descriptor Code: 4
IGD01009I
IGD01005I
text
text
Descriptor Code: 4
IGD01010I
IGD01006I
text
490
text
IGD01011I IGD01015I
Source: DFSMSdfp
IGD01013I
Routing Code: 11
Descriptor Code: 4
IGD01011I
dcname
The data class.
IGD01014I
scname
The storage class.
mcname
The management class.
System action: The request fails.
Application Programmer Response: Modify the ACS
routine or installation exit to return an SMS data class,
storage class, or management class that exists. For an
ACS routine, verify the use of and values for RACF
defaults.
Source: DFSMSdfp
Routing Code: 11
Descriptor Code: 4
mcname
The management class.
IGD01012I
IGD01015I
491
IGD01016I IGD01020I
groups: OBJECT, OBJECT BACKUP, VIO, or TAPE.
These types of assignment are not allowed.
System action: The request is failed.
Application Programmer Response: Contact your
storage administrator.
System programmer response: Modify your storage
group ACS routine to insure that the list of storage
groups for PDSE data sets contain at least one POOL
type storage group.
Source: Storage Management Subsystem (SMS)
Detecting Module: IGDACS01
Routing Code: 11
Descriptor Code: 4
IGD01016I
IGD01018I
Source: DFSMSdfp
Routing Code: 11
Descriptor Code: 4
IGD01017I
Routing Code: 11
Descriptor Code: 4
492
IGD01021I IGD03114I
Detecting Module: IGDACS01
Routing Code: 11
Descriptor Code: 4
IGD01021I
modname
The module in which the error occurred.
event
493
IGD03115I IGD03119I
System action: The system notes the error in the
output listing, and continues checking the syntax of the
ACS routine. However, the system will not produce the
object table, so the translation will fail.
Application Programmer Response: Correct the
ACS routine source statement so that the number of left
parentheses is the same as the number of right
parentheses.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD03115I
494
IGD03117I
IGD03120I IGD03134I
Source: DFSMSdfp
Routing Code: 2
Source: DFSMSdfp
Descriptor Code: 4
Routing Code: 2
Descriptor Code: 4
IGD03120I
IGD03132I
Source: DFSMSdfp
Routing Code: 2
Source: DFSMSdfp
Descriptor Code: 4
Routing Code: 2
Descriptor Code: 4
IGD03121I
IGD03133I
nnn
name
495
IGD03135I IGD03140I
literals for each INCLUDE and EXCLUDE.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD03135I
IGD03136I
Routing Code: 2
Descriptor Code: 4
IGD03139I
Source: DFSMSdfp
Routing Code: 2
Source: DFSMSdfp
Descriptor Code: 4
Routing Code: 2
IGD03137I
496
Descriptor Code: 4
IGD03140I
IGD03141I IGD03151I
nnn
mmm
INVALID SUBSCRIPT
IGD03143I
Descriptor Code: 4
IGD03142I
Routing Code: 2
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD03151I
497
IGD03152I IGD03158I
Routing Code: 2
Descriptor Code: 4
IGD03152I
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD03157I
IGD03155I
498
Routing Code: 2
Descriptor Code: 4
IGD03158I
IGD03160I IGD03174I
IGD03160I
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD03161I
Descriptor Code: 4
Source: DFSMSdfp
IGD03172I
Routing Code: 2
Descriptor Code: 4
IGD03162I
499
IGD03175I IGD03202I
OTHERWISE keyword has a matching clause, and
correct the ACS routine source statement.
Routing Code: 2
Descriptor Code: 4
Source: DFSMSdfp
Routing Code: 2
IGD03200I
Descriptor Code: 4
IGD03175I
Source: DFSMSdfp
Source: DFSMSdfp
Routing Code: 2
Routing Code: 2
Descriptor Code: 4
Descriptor Code: 4
IGD03180I
IGD03201I
Routing Code: 2
Descriptor Code: 4
Source: DFSMSdfp
Routing Code: 2
IGD03190I
500
Descriptor Code: 4
IGD03202I
IGD03210I IGD03215I
Application Programmer Response: Correct the
WRITE statement in the ACS routine source.
Descriptor Code: 4
Source: DFSMSdfp
IGD03213I
Routing Code: 2
Descriptor Code: 4
IGD03210I
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD03211I
IGD03214I
501
IGD03220I IGD03225I
IGD03220I
IGD03222I
502
Routing Code: 2
Descriptor Code: 4
IGD03225I
IGD03226I IGD04001I
System action: The system notes the error in the
output listing, and continues checking the syntax of the
ACS routine. However, the system will not produce the
object table, so the translation will fail.
Application Programmer Response: Change the
SET statement so that only 15 values are assigned.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD03229I
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD03226I
rsnc
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD03228I
503
IGD04002I IGD04008I
IGD04002I
Descriptor Code: 4
IGD04007I
Source: DFSMSdfp
Routing Code: 2
Routing Code: 2
Descriptor Code: 4
Descriptor Code: 4
IGD04008I
IGD04004I
504
IGD04009I IGD04011I
the volume online, then resubmit the job.
Source: Storage Management Subsystem (SMS)
Detecting Module: IGDCAT01
Routing Code: 2
Descriptor Code: 4
ser2
IGD04009I
ser1
A volume serial specified for the data set
Descriptor Code: 4
IGD04011I
ser2
dsname
The data set name
System action: If the first volume is in a tape library,
the allocation might be successful, if the Volume not in
Library installation exit can resolve the inconsistency.
Otherwise, the system fails the allocation.
User response: If the allocation is successful, ignore
the message. Otherwise, if the volume serials are
specified incorrectly, then correct the specification. If the
volume serials are correct, then contact the tape
librarian to either eject the library resident tape
volume(s) from the library or enter the non-library
resident volume(s) in the library.
Source: Storage Management Subsystem (SMS)
Detecting Module: IGDCAT01
Routing Code: 2
Descriptor Code: 4
IGD04010I
505
IGD04100I IGD06022I
IGD04100I
IGD04901I
NO PATHNAME SPECIFIED.
ALLOCATION FAILED FOR DDNAME
ddname
IGD04900I
506
scname
The storage class.
mcname
The management class.
dcname
The data class.
System action: The system continues processing.
Application Programmer Response: If this condition
is intentional, take no corrective action.
Otherwise, check the IF statement test expressions in
the ACS routine. If one of the expressions is incorrect,
modify it. If not, add a definition for the undefined
storage class, management class, or data class. Refer
to z/OS DFSMS OAM Planning, Installation, and
Storage Administration Guide for Tape Libraries for
more information.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD06023I IGD06027I
IGD06023I
Descriptor Code: 4
IGD06025I
dcname
Source: DFSMSdfp
Source: DFSMSdfp
Routing Code: 2
Routing Code: 2
Descriptor Code: 4
Descriptor Code: 4
IGD06024I
IGD06026I
sgname
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD06027I
507
IGD06028I IGD06031I
System action: The system continues processing.
Routing Code: 2
Descriptor Code: 4
Source: DFSMSdfp
IGD06030I
Routing Code: 2
Descriptor Code: 4
IGD06028I
VIO
POOL
OBJECT
TAPE
508
IGD06120I IGD06125I
Detecting Module: IGDCSVAL
IGD06120I
NO BASE CONFIGURATION
INFORMATION EXISTS IN THE
CONFIGURATION
IGD06124I
Routing Code: 2
Descriptor Code: 4
sgname
Source: DFSMSdfp
IGD06121I
509
IGD06126I IGD06129I
System action: The system marks the control data set
(CDS) as incorrect. This CDS cannot be activated until
the problem is corrected.
Operator response: Contact the storage
administrator.
Application Programmer Response: The storage
administrator should do one of the following:
v If the specified storage group was meant to be
connected only to real libraries, then use the
interactive storage management facility (ISMF) panels
to delete the pseudo library from that storage group.
v If the pseudo library does not belong in the save
control data set (SCDS), then delete the pseudo
library definition from that storage group.
v If the specified storage group was meant to be
connected only to the pseudo library, then delete the
real libraries from that storage group.
v If one or more of the real libraries does not belong in
the SCDS, then delete the real library definition(s).
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD06126I
IGD06128I
Source: DFSMSdfp
Source: DFSMSdfp
Routing Code: 2
Routing Code: 2
Descriptor Code: 4
Descriptor Code: 4
IGD06127I
IGD06129I
510
IGD06132I IGD06135I
System action: The system marks the control data set
(CDS) as incorrect. This CDS cannot be activated until
the problem is corrected.
Operator response: Contact the storage
administrator.
Application Programmer Response: The storage
administrator should correct the system connectivity for
the storage group through the interactive storage
management facility (ISMF) application. Ensure that the
storage group is connected only to a single system.
libname
The specified library name.
System action: The system marks the control data set
(CDS) as incorrect. This CDS cannot be activated until
the problem is corrected.
Operator response: Contact the storage
administrator.
Source: DFSMSdfp
Routing Code: 2
Source: DFSMSdfp
Descriptor Code: 4
Routing Code: 2
Descriptor Code: 4
IGD06132I
IGD06134I
sgname
The specified object, object backup or tape
storage group name.
sgname
The specified storage group.
511
IGD06136I IGD06140I
Application Programmer Response: The storage
administrator should do the following:
1. Identify the object backup storage groups in the
CDS, and identify which system each one is
attached to.
Source: DFSMSdfp
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD06136I
Routing Code: 2
Descriptor Code: 4
IGD06139I
class_name
The management class specified.
sgname
dest_name
The destination definition.
libname
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
Routing Code: 2
IGD06137I
512
Descriptor Code: 4
IGD06140I
IGD06200I IGD06203I
System action: The system marks the CDS as not
valid. You must correct the problem before this CDS can
be activated.
Operator response: Contact the storage
administrator.
System programmer response: The storage
administrator should do one of the following:
1. If the specified tape storage group should be
associated with one or more libraries, then use
Interactive Storage Management Facility (ISMF)
panels to make the association.
2. If the storage group is not valid, then delete it from
the CDS by using ISMF panels.
Source: Storage Management Subsystem (SMS)
Detecting Module: IGDCSOAM
Routing Code: 2
Descriptor Code: 4
IGD06200I
IGD06202I
IGD06203I
513
IGD06204I IGD06206I
sg1
The name of the pool storage group that contains
the error.
IGD06205I
sg2
The name of the referenced storage group.
System action: The SCDS is invalid. Processing
continues.
Operator response: None
Application Programmer Response: Correct the
name of the copy pool backup storage group in the
failing pool storage group and revalidate the SMS
SCDS.
Routing Code: 2
Descriptor Code: 4
sg1
Routing Code: 2
Descriptor Code: 4
514
IGD06207I IGD07002I
Detecting Module: IGDCSVAL
Routing Code: 2
Descriptor Code: 4
IGD06207I
IGD07001I
The name of the copy pool definition that contains
the error.
sg1
The name of the referenced storage group.
System action: The SCDS is invalid. Processing
continues.
rc
rsnc
modname
The module that returned the error.
IGD06208I
Routing Code: 2
Descriptor Code: 4
IGD07002I
volser
515
IGD07003I IGD07902I
Application Programmer Response: Either modify
the configuration to include the volume, or make sure
the volume is online.
IGD07900I
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD07003I
ddname
The specified DDNAME.
Descriptor Code: 4
IGD07901I
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD07004I
Routing Code: 2
Descriptor Code: 4
516
IGD11100I IGD14000I
IGD11100I
Descriptor Code: 4
IGD14000I
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD11100I
NO SYSTEM IS ELIGIBLE TO
PERFORM LOCATES:
VOLUME S17 S18 S19 S20 S21 S22 S23 S24 S25 S26 S27 S28 S29 S30 S31 S32
1 =
4 =
7 =
10=
13=
16=
19=
22=
25=
28=
31=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
2 =
5 =
8 =
11=
14=
17=
20=
23=
26=
29=
32=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
3 =
6 =
9 =
12=
15=
18=
21=
24=
27=
30=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
sysname
A system in the current active configuration.
IGD11101I
volser
517
IGD14001I
management subsystem status of ENABLE,
QUIESCED, QUIESCE (NEW), DISABLE,
or DISABLE (NEW).
v N if the system is not eligible to access the
SMS managed volume. In this case, volser
is not defined to the system.
lin
sysname
A system in the current active configuration. Up
to 32 systems may appear in the display, each
represented by its own system name.
Source: DFSMSdfp
volser
Routing Code: 2
Descriptor Code: 4
IGD14001I
SEQ TYPE RESNAME S13 S14 S15 S16 S17 S18 S19 S20 S21 S22 S23 S24 SEQ
SEQ TYPE RESNAME S25 S26 S27 S28 S29 S30 S31 S32 SEQ
1 =
4 =
7 =
10=
13=
16=
19=
22=
25=
28=
31=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
2 =
5 =
8 =
11=
14=
17=
20=
23=
26=
29=
32=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
3 =
6 =
9 =
12=
15=
18=
21=
24=
27=
30=
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sysname
sgname
text
lin
lin
lin
lin
A line number.
518
IGD16001I IGD17001I
Routing Code: 2
IGD16003I
Descriptor Code: 4
IGD16001I
dsn1
dsname
dsn2
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD16002I
IGD16004I
dsn2
Routing Code: 2
Descriptor Code: 4
519
IGD17002I IGD17012I
dsname
cde
The data set name.
Diagnostic information.
Routing Code: 2
Descriptor Code: 4
IGD17002I
dsname
Routing Code: 2
Descriptor Code: 4
IGD17012I
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17003I
dsname
rc
volser
cde
Diagnostic information.
dsname
rc
520
IGD17014I IGD17039I
information. If the return code and the diagnostic
information indicate that the user is unauthorized to
create the data set, then alter the users RACF profile to
grant authorization. Otherwise, remove the automatic
data set protection characteristic from the users profile.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17014I
dsname
dsname
The data set name.
System action: Although the volume was not
selected, volume selection continues.
Application Programmer Response: Determine why
the volume was rejected by the DADSM installation exit;
you may need to modify the exit.
Source: DFSMSdfp
Routing Code: 2
IGD17036I
Descriptor Code: 4
IGD17039I
dsname
The data set name.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17037I
521
IGD17040I IGD17046I
Source: DFSMSdfp
dsname
The data set name
IGD17040I
dsname
The data set name.
rc
cde
Diagnostic information.
IGD17044I
Source: DFSMSdfp
Source: DFSMSdfp
Routing Code: 2
IGD17045I
Descriptor Code: 4
IGD17042I
522
IGD17051I IGD17054I
System action: The request fails, and the system
writes a record describing the error to the logrec data
set.
Application Programmer Response: Use the record
in the logrec data set to determine the exact nature of
the problem.
Source: DFSMSdfp
Routing Code: 2
IGD17053I
Descriptor Code: 4
IGD17051I
rc
cde
Diagnostic information.
Descriptor Code: 4
IGD17054I
v PDSE
v VSAM
dsname
The data set name.
volser
523
IGD17055I IGD17058I
IGD17055I
IGD17057I
dsname
The data set name.
dsname
The data set name.
rc
cde
Diagnostic information.
DELETE/RENAME FAILED,
APPROPRIATE UCB UNAVAILABLE
FOR VOLUME volser DATA SET IS
dsname HISTORIC RETURN CODE IS rc
DIAGNOSTIC INFORMATION IS cde
dsname
The data set name.
rc
cde
Diagnostic information.
volser
dsname
The data set name.
System action: The rename request fails.
Application Programmer Response: Either delete
the existing data set, or change the new name to a
name other than the indicated data set.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
524
IGD17059I IGD17062I
IGD17059I
IGD17061I
INSUFFICIENT SECURITY
AUTHORIZATION FOR DATA SET
dsname ON VOLUME volser HISTORIC
RETURN CODE IS rc DIAGNOSTIC
INFORMATION IS cde
volser
volser
dsname
dsname
The data set name.
rc
rc
cde
Diagnostic information.
cde
Diagnostic information.
Source: DFSMSdfp
Source: DFSMSdfp
Routing Code: 2
Routing Code: 2
Descriptor Code: 4
Descriptor Code: 4
IGD17060I
IGD17062I
DELETE/RENAME FAILED,
UNRECOGNIZED DADSM STATUS
CODE OF rc DIAGNOSTIC
INFORMATION IS cde VOLUME IS
volser DATA SET IS dsname
dsname
The data set name.
System action: The delete or rename request fails.
Application Programmer Response: Resubmit the
request later.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
volser
dsname
The data set name.
rc
cde
Diagnostic information.
525
IGD17065I IGD17068I
Source: DFSMSdfp
IGD17067I
Routing Code: 2
Descriptor Code: 4
IGD17065I
cde
Diagnostic information.
Source: DFSMSdfp
Routing Code: 2
Routing Code: 2
Descriptor Code: 4
Descriptor Code: 4
IGD17068I
IGD17066I
dsname
volser
dsname
The data set name.
cde
volume serial
Diagnostic information.
diaginfo
DADSM diagnostic information
System action: The allocation fails.
Application Programmer Response: Probable
system error. Determine the meaning of the DADSM
diagnostic information and contact your programming
support personnel.
System programmer response: Contact the IBM
support center.
Source: Storage Management Subsystem (SMS)
Source: DFSMSdfp
Routing Code: 2
Routing Code: 2
Descriptor Code: 4
Descriptor Code: 4
526
IGD17070I IGD17075I
IGD17070I
Descriptor Code: 4
IGD17073I
ALLOCATION AS A NON-EXTENDED
SEQUENTIAL DATASET WILL BE
ATTEMPTED
dsname
The data set name
Explanation: DSNTYPE=(EXTENDED,PREFERRED)
was specified, but SMS could not allocate an extended
sequential data set.
Routing Code: 2
Source: DFSMSdfp
Descriptor Code: 4
Source: DFSMSdfp
Routing Code: 2
IGD17071I
Descriptor Code: 4
IGD17074I
Routing Code: 2
Descriptor Code: 4
Source: DFSMSdfp
Detecting Module: IGDVTSTR
IGD17072I
Explanation: DSNTYPE=(EXTENDED,REQUIRED)
was specified, but SMS could not allocate an extended
sequential data set.
System action: The system fails the allocation
request.
Application Programmer Response: See any
accompanying IGD1707x messages for more
information.
Source: DFSMSdfp
Detecting Module: IGDVTSTR
Routing Code: 2
Routing Code: 2
Descriptor Code: 4
IGD17075I
527
IGD17076I IGD17101I
the system attempts to allocate the data set as
non-extended sequential.
Application Programmer Response: Ensure that the
data set organization either specified or derived for the
data set is physical sequential.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17076I
IGD17100I
Routing Code: 2
rc
Descriptor Code: 4
rsnc
IGD17077I
Routing Code: 2
Descriptor Code: 4
dsname
Source: DFSMSdfp
528
rc
rsnc
IGD17102I IGD17105I
Application Programmer Response: Either rename
the data set in the catalog, or specify a different name
for the data set being defined. Then rerun the job.
See system message IDC3009I for an explanation of
the catalog return and reason codes. Use the error
record from the logrec data set for more information to
correct the error.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17104I
IGD17102I
rsnc
rsnc
rsnc
rc
rsnc
dsname
529
IGD17106I IGD17116I
IDC3009I for an explanation of the catalog return and
reason codes. Use the record in the logrec data set if
you still cannot correct the error.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17106I
IGD17110I
dsname
dsname
The data set name.
rc
rsnc
Routing Code: 2
dsname
Descriptor Code: 4
Source: DFSMSdfp
rsnc
530
IGD17116I
IGD17118I IGD17162I
In the message text:
dsname
The data set name.
System action: The SMS VTOC data set services
request fails. Also, the system writes the catalog
parameter list and its associated field parameter to the
logrec data set.
Application Programmer Response: Use the
information in the logrec data set to determine the error.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17118I
rsnc
dsname
The specified data set.
System action: The system ignores the compression
request and continues processing.
Application Programmer Response: Contact your
programming support personnel to determine
compression services availability.
Source: Storage management subsystem (SMS)
Routing Code: 2
Descriptor Code: 4
IGD17162I
dsname
The data set name.
System action: The SMS VTOC data set services
request fails.
Application Programmer Response: Correct the
LIKE specification and rerun the job.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17160I
rsnc
dsname
The specified data set.
System action: The system ignores the compression
request and continues processing.
Application Programmer Response: Correct the data
set so that the characteristics match those required for
compression.
Source: Storage management subsystem (SMS)
Routing Code: 2
Descriptor Code: 4
531
IGD17163I IGD17172I
IGD17163I
EXTENDED ADDRESSABILITY
REQUEST NOT HONORED FOR DATA
SET dsn BECAUSE DATA SET IS NOT
ELIGIBLE FOR EXTENDED FORMAT.
ALLOCATION CONTINUES.
rc
Routing Code: 2
rsnc
Descriptor Code: 4
IGD17172I
532
IGD17200I IGD17203I
dsname
The data set name
scname
sgname
volser
dsn
Routing Code: 2
Descriptor Code: 4
IGD17200I
dsname
The data set name.
System action: The extend request fails, and the
system writes a record describing the error to the logrec
data set.
Application Programmer Response: Use the
information in the logrec data set to determine the error.
Source: DFSMSdfp
Routing Code: 2
IGD17202I
Descriptor Code: 4
rc
IGD17201I
533
IGD17204I IGD17206I
dsname
The data set name.
ddname
The specified DDNAME.
System action: The SMS VTOC data set services
allocation request fails. Also, the system writes to the
logrec data set a record containing the volume list that
SMS VTOC data set services passed to SMS construct
access services. The IGD306I message that follows
contains the ID of that record.
Application Programmer Response: If a volume list
was explicitly specified for the DDNAME, then correct
the volume list and rerun the job. If you did not explicitly
specify the volume list, then contact your programming
support personnel.
Source: DFSMSdfp
Routing Code: 2
Routing Code: 2
Descriptor Code: 4
Descriptor Code: 4
IGD17206I
IGD17204I
rsnc
534
IGD17207I IGD17210I
Source: DFSMSdfp
IGD17209I
Routing Code: 2
Descriptor Code: 4
IGD17207I
dsname
The data set.
dsname
Descriptor Code: 4
IGD17210I
IGD17208I
DYNAMIC UNALLOCATION OF
VOLUME volser DURING CREATE OF
DATA SET dsname HAS FAILED DYNAMIC ALLOCATION RETURN
CODE IS rc REASON CODE IS rsnc
dsname
volser
The data set name.
rc
dsname
The data set name.
rc
rsnc
535
IGD17211I IGD17214I
IGD17211I
IGD17213I
UNABLE TO DYNAMICALLY
ALLOCATE VOLUME volser DURING
CREATION OF DATA SET dsname
DYNAMIC ALLOCATION RETURN
CODE IS rc REASON CODE IS rsnc
dsname
volser
The data set name.
dsname
The data set name.
rc
rsnc
IGD17212I
Routing Code: 2
Descriptor Code: 4
IGD17214I
rsnc
UNABLE TO DYNAMICALLY
ALLOCATE DATA SET dsname DURING
CREATION OF THE DATA SET DYNAMIC ALLOCATION RETURN
CODE IS rc REASON CODE IS rsnc
rsnc
536
IGD17215I IGD17218I
IGD17215I
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17216I
volser
The volume serial number
dsname
The data set name
System action: The SMS VTOC Data Set Services
request fails.
Application Programmer Response: Do one of the
following:
v specify another volume when you resubmit the
request.
v make sure the volume is online, enabled, and has
adequate space for the data set. Then resubmit the
request.
v make sure the status of the storage group containing
the volume is either enabled, quiesced, or quiesced
new. Then resubmit the request.
v make sure the volume meets the Extended Format,
Availability and Accessibility specification in the
storage class. Then resubmit the request.
Source: Data Facility Product (DFSMS)
Routing Code: 2
Descriptor Code: 4
IGD17218I
537
IGD17219I IGD17223I
define VSAM request fails. Also, the system writes a
record describing the error to the logrec data set.
Application Programmer Response: Use the logrec
data set to determine the error.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17219I
dsname
The data set name
Descriptor Code: 4
IGD17220I
IGD17223I
The data set name.
538
IGD17224I IGD17227I
ofsg
Source: DFSMSdfp
Routing Code: 2
Source: DFSMSdfp
Descriptor Code: 4
Routing Code: 2
IGD17225I
dsname
The data set name.
System action: The SMS VTOC data set services
request fails.
Application Programmer Response: Do one of the
following:
v Specify another volume when you resubmit the
request.
v Determine which storage group contains volser, and
which storage classes that map that storage group.
Descriptor Code: 4
IGD17227I
539
IGD17230I IGD17234I
ddname
The data definition (DD) name of the data set that
was allocated
dsn
The name of the data set that was allocated
sg1
The storage group to which the data set was
allocated
sg2, sg3...
The multitiered storage group selection order that
the job requested
Descriptor Code: 4
IGD17230I
Routing Code: 2
Descriptor Code: 4
IGD17234I
540
IGD17235I IGD17241I
IGD17235I
IGD17240I
volser
The volume serial number
dsname
The data set name
541
IGD17242I IGD17261I
IGD17242I
dsname
The data set name
System action: The SMS VTOC Data Set Services
request fails.
Application Programmer Response: This is a
system error. Contact your system programmer.
Source: Data Facility Product (DFSMS)
IGD17260I
dsname
The data set name
System action: The SMS VTOC Data Set Services
request fails.
Application Programmer Response: This is a
system error. Contact your system programmer.
Source: Data Facility Product (DFSMS)
IGD17249I
dsname
The data set name
volser
The volume serial number
Source: DFSMSdfp
542
Routing Code: 2
Descriptor Code: 4
IGD17261I
IGD17262I IGD17264I
dsname
*0
The data set name.
dsname
The data set name.
rc
rsnc
Explanation
Request successful.
12
16
20
Reason Code
Explanation
UCB is eligible.
dsname
The data set name
12
543
IGD17267I IGD17268I
IGD17267I
text
Blank or RF-ELIGIBLE
reason1
Reason why these n volumes were rejected.
The possible reasons are:
v THE SMS VOLUME STATUS WAS
DISABLED
v THEY WERE NOT ONLINE
sg1,sg2,...
The list of Storage Groups. Up to 4 lines will
be printed.
544
|
|
|
IGD17269I
reason2
Where:
diagdata
is the DADSM diagnostic code or OTHERS after 10
diagnostic codes have been displayed for a failure
reason.
IGD17269I
|
|
|
Where:
diagdata
is the DADSM diagnostic code or OTHERS after 10
diagnostic codes have been displayed for a failure
reason.
545
IGD17271I IGD17273I
System programmer response: This message may
provide some information as to why this data set could
not be allocated on fast replication volumes. You may
need to modify the ACS routines or take other action to
make additional fast replication volumes available. This
message is issued in summarized volume selection
analysis messages when creation or extension of an
SMS-managed data set is successful.
Source: Data Facility Product (DFSMS)
IGD17271I
dsn
jobname
stepname
progname
ddname
nnnn
dsname
The specified data set.
System action: The system continues the allocation
process.
Application Programmer Response: If a
multi-volume data set is required, either request that
volumes be added to the storage group to which this
volume belongs, or re-allocate this data set such that
the storage group selected has a sufficient number of
available online volumes.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17272I
546
dsname
The data set name.
System action: The SMS VTOC data set services
request fails. DADSM may reject the volume because it
was not initialized or because there was not enough
space.
Application Programmer Response: If DADSM could
not find enough space, put additional volumes online in
one of the eligible storage groups, and resubmit the
request. Otherwise, refer to any preceding messages to
determine the error.
If the problem cannot be determined, run the job again
and request a dump immediately after the failure.
Contact the IBM Support Center and provide the dump.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17274I IGD17277I
IGD17274I
IGD17276I
dsname
dsname
The data set name.
dsname
Source: DFSMSdfp
Routing Code: 2
Routing Code: 2
Descriptor Code: 4
Descriptor Code: 4
547
IGD17278I IGD17279I
IGD17278I
|
|
dsname
The data set name.
rc
rsnc
|
|
|
|
|
|
|
|
548
|
|
|
|
|
|
|
|
|
Where:
diagdata
is the DADSM diagnostic code or OTHERS after 10
diagnostic codes have been displayed for a failure
reason.
System action: Processing stops.
Operator response: None
Application Programmer Response: See reason and
responses below.
IGD17279I
System programmer response: Correct the problem
indicated by the reason in the message and resubmit
the request.
Reason
Response
OF A DADSM FAILURE
|
|
|
|
|
|
|
|
|
|
|
|
|
|
549
IGD17280I IGD17284I
IGD17280I
dsname
The The data set name
System action: The SMS VTOC Data Set Services
request fails.
Application Programmer Response: Correcting this
situation may require that the ACS routines be modified
to select an appropriate Storage Group, in other words,
one that meets the track size criterion.
Source: Data Facility Product (DFSMS)
IGD17284I
550
dsname
The The data set name
System action: The SMS VTOC Data Set Services
request fails.
Application Programmer Response: Application
Programmer Response: Correcting this situation may
require that the ACS routines be modified to select
IGD17285I IGD17288I
different Storage Groups or make more space available
on the Storage Groups that were selected.
var3
SPACE WAS REDUCED BY y%, where y is a
percentage from 1 - 99.
IGD17286I
v the data set was spread over more than one volume
v the requested primary space amount was reduced by
the percentage specified in the DATA CLASS
v more than 5 extents were used to allocate the
requested space
The text corresponding to var1, var2, and var3 is shown
below and depending on the actions taken by SMS, one
or more of these variants will be printed out on the
second line of this message.
var1
DATA WAS SPREAD OVER MULTIPLE VOLUME
dsname
The data set name
var2
var1
SINGLE VOLUME DATA SET, or GUARANTEED
Chapter 12. IGD Messages
551
IGD17289I IGD17292I
SPACE DATA SET, or PARTITIONED DATA SET,
or KSDS WITH IMBED ATTRIBUTE
System action: Processing continues
Application Programmer Response: This is an
informational message. No action is required.
Source: Data Facility Product (DFSMS)
IGD17289I
dsname
The data set name
System action: Processing continues
Application Programmer Response: This is an
informational message. No action is required.
Source: Data Facility Product (DFSMS)
sg1,sg2
The list of storage groups. Up to 4 lines will be
printed.
System action: The SMS VTOC Data Set Services
request fails.
552
IGD17293I IGD17303I
IGD17293I
dsname
The data set name
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
|
|
IGD17294I
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
rsnc
Dsn
|
|
|
|
|
|
|
553
IGD17304I IGD17307I
rsnc
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17304I
dsname
dsname
The data set name.
System action: The SMS VTOC data set services
delete or rename request fails. Also, the system writes a
record describing the error to the logrec data set.
Application Programmer Response: To delete or
rename the data set, you must give the data set a
storage class in its catalog entry.
rsnc
Source: DFSMSdfp
Routing Code: 2
IGD17307I
Descriptor Code: 4
IGD17305I
554
IGD17308I IGD17314I
IGD17308I
Routing Code: 2
Descriptor Code: 4
IGD17309I
rsnc
Routing Code: 2
Descriptor Code: 4
IGD17311I
IGD17314I
Source: DFSMSdfp
555
IGD17315I IGD17331I
Explanation: This is an informational message that is
issued by SMS during the allocation of a data set that is
intended to be the target of a fast replication operation.
The caller indicated that selection of fast replication
eligible volumes was preferred. Since ANTRQST
QFRVOLS detected an error, SMS will continue the
allocation request while ignoring the fast replication
preference. Refer to the ANTRQST section in z/OS
DFSMSdfp Advanced Services for information on the
QFRVOLS return code, reason code and RETINFO.
IGD17330I
dsn
rc
rsn
retinfo
dsn
IGD17315I
dsn
rc
dsn
rsn
retinfo
variable text
REQUIRED|PREFERRED
556
IGD17332I IGD17334I
Source: Data Facility Product (DFSMS)
IGD17332I
variable text
REQUIRED|PREFERRED
IGD17334I
var1
var2
var1
var2
557
IGD17335I IGD17351I
IGD17335I
var2
dsn
rsnc
IGD17345I
dsname
The data set name
rc
558
IGD17352I IGD17357I
IGD17352I
dsname
The data set name.
rsnc
Descriptor Code: 4
IGD17355I
IGD17353I
dsname
The data set name.
Routing Code: 2
Descriptor Code: 4
IGD17356I
Source: DFSMSdfp
IGD17354I
rsnc
dsname
The data set name.
System action: The system continues processing.
Source: DFSMSdfp
IGD17357I
559
IGD17358I IGD17362I
dsname
Routing Code: 2
The data set name.
Descriptor Code: 4
IGD17360I
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
dsname
The data set name.
IGD17358I
NON-SMS-MANAGED VOLUMES
SPECIFIED FOR SMS-MANAGED DATA
SET dsn
Source: DFSMSdfp
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
Routing Code: 2
IGD17362I
Descriptor Code: 4
IGD17359I
560
UNABLE TO LOCATE AN
SMS-MANAGED DATA SET OR A VSAM
DATA SET DURING EOV PROCESSING
DATA SET NAME IS dsname
IGD17364I IGD17367I
Application Programmer Response: Refer to any
preceding messages to determine why the locate
request failed.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17366I
IGD17364I
rsnc
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17365I
IGD17367I
561
IGD17368I IGD17371I
IGD17368I
rsnc
rsnc
IGD17370I
rsnc
Source: DFSMSdfp
Routing Code: 2
Routing Code: 2
Descriptor Code: 4
Descriptor Code: 4
562
IGD17372I IGD17380I
IGD17372I
rc
rsn
mm
IGD17380I
563
IGD17381I IGD17386I
IGD17381I
===== {SUMMARIZED|DETAILED}
ANALYSIS MESSAGES ON
{DEFINING|EXTENDING} DATASET dsn
=====
VOLSELMSG({ON|OFF},{0|nnnnn|ALL})
TYPE({ALL|ERROR})
JOBNAME(jobname) ASID(asid)
STEPNAME(stepname)
DSNAME(dsname)
564
IGD17387I IGD17389I
IGD17387I
=={POOL|OVERFLOW|EXTEND} SGsg
IGD17389I
volser
({S|N|R},preference,fail_flags,diagdata)
...
preference
is a four byte flag field, where:
bytes 1 and 2 indicate:
1....... ........ meet data set separation criteria
if specified
.1...... ........ meet volume count criteria for
non-VSAM data set
..1..... ........ below 120% of high threshold
...1.... ........ below high threshold (always set
for best fit)
....1... ........ enabled SMS status
.....111 1....... multi-tiered storage group
ranking if specified
........ .1...... non-extend storage group
........ ..1..... non-overflow storage group
........ ...1.... mountable volume
........ ....1... preferred volume for fast
replication
........ .....11. meet PREFERRED |
STANDARD accessibility criteria
........ .......1 meet PREFERRED |
STANDARD PAV criteria
Chapter 12. IGD Messages
565
IGD17400I IGD17401I
bytes 3 and 4 indicate:
1....... ........ meet PREFERRED |
STANDARD availability criteria
.1...... ........ meet PREFERRED Extent
Format criteria
..111111 ........ not used
........ 11111111 MSR band rank
|
|
fail_flags
is a four byte flag field that indicates why the
volume was rejected, where:
bytes 1 and 2 indicate:
1....... ........ SMS status DISABLED
.1...... ........ MVS status NOT ONLINE
..1..... ........ no UCB available
...1.... ........ not meet continuous availability
....1... ........ not meet standard. pref, or
no-pref availability
.....1.. ........ not meet accessibility
......1. ........ not meet data set separation
criteria
.......1 ........ rejected for insufficient space for
best-fit
........ 1....... rejected by DADSM for duplicate
data set name
........ .1...... rejected by DADSM for no room
in VTOC or index
........ ..1..... rejected by DADSM for I/O or
CVAF error
........ ...1.... rejected by DADSM installation
exit
........ ...1.... rejected for insuff total space
........ ....1... rejected by DADSM because not
initialized
........ ....1... rejected for insuff free space
........ .....1.. rejected by DADSM because
EOF mark write failed
........ ......1. rejected by DADSM for
insufficient space
........ .......1 rejected by other DADSM failure
bytes 3 and 4 indicate:
1....... ........ not meet striping criteria
.1...... ........ not an unmountable volume
..1..... ........ no DPCT available
...1.... ........ not on include list
....1... ........ on exclude list
.....1.. ........ not correct device type
......1. ........ could not be allocated
.......1 ........ insufficient space for striping
........ 1....... failed by IGWSSEOV during
extend processing
........ .1...... not meet fast replication criteria
........ ..1..... not meet PAV criteria
........ ...11111 not used
diagdata
is the DADSM diagnostic code.
System action: The system continues processing.
Operator response: None
Application Programmer Response: Review the
566
IGD17403I IGD17409I
Source: DFSMSdfp
Routing Code: 2
dsname
The data set name.
Descriptor Code: 4
rc
IGD17403I
UNABLE TO ENQUEUE ON
REFERENCED DATA SET dsname
ENQUEUE RETURN CODE IS rc
Descriptor Code: 4
Source: DFSMSdfp
Routing Code: 2
dsname
The data set name.
rc
IGD17407I
Source: DFSMSdfp
Routing Code: 2
dsname
The data set name.
Descriptor Code: 4
IGD17404I
dsname
The data set name.
IGD17409I
IGD17406I
567
IGD17410I IGD17432I
Source: DFSMSdfp
dsname
The specified data set.
Routing Code: 2
Descriptor Code: 4
IGD17410I
dsname
The data set name.
Source: DFSMSdfp
IGD17430I
dsname
The data set name.
Application Programmer Response: Correct the
reference or remove the LIKE= parameter.
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17431I
568
IGD17433I IGD17504I
IGD17433I
Source: DFSMSdfp
Routing Code: 2
dsname
Descriptor Code: 4
IGD17503I
Routing Code: 2
rc
Descriptor Code: 4
rsn
filename
IGD17502I
569
IGD17510I IGD17803I
IGD17510I
NO PATHNAME SPECIFIED.
ALLOCATION FAILED FOR
DDNAME=ddname
IGD17800I
Descriptor Code: 4
IGD17802I
Source: DFSMSdfp
dsname
The data set name
Routing Code: 2
Descriptor Code: 4
IGD17803I
570
IGD17804I IGD17807I
v No accessible volumes had sufficient space to satisfy
the single-volume request; or
v Not enough accessible volumes had sufficient space
to satisfy the multi-volume request.
IGD17806I
dsname
dsname
Source: DFSMSdfp
Routing Code: 2
Routing Code: 2
Descriptor Code: 4
Descriptor Code: 4
IGD17807I
IGD17804I
Routing Code: 2
Descriptor Code: 4
571
IGD17808I IGD21002I
determine why the request failed.
IGD21002I
Source: DFSMSdfp
Routing Code: 2
Descriptor Code: 4
IGD17808I
rc
rs
Routing Code: 11
Descriptor Code: 6
Routing Code: 11
Descriptor Code: 6
572
IGD23100I IGD23102I
IGD23100I
573
574
Appendix. Accessibility
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
z/OS information
z/OS information is accessible using screen readers with the BookServer/Library Server versions of z/OS
books in the Internet library at:
www.ibm.com/servers/eserver/zseries/zos/bkserv/
575
576
Notices
This information was developed for products and services offered in the USA.
IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that only
that IBM product, program, or service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may be used instead. However, it is the
users responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document.
The furnishing of this document does not give you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
USA
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer
of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of
the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this one)
and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
Mail Station P300
2455 South Road
Poughkeepsie, NY 12601-5400
USA
Copyright IBM Corp. 1988, 2007
577
Such information may be available, subject to appropriate terms and conditions, including in some cases,
payment of a fee.
The licensed program described in this information and all licensed material available for it are provided by
IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any
equivalent agreement between us.
If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Trademarks
The following terms are trademarks of the IBM Corporation in the United States or other countries or both:
v ACF/VTAM
v AIX
v C/370
v CICS
v CICS/ESA
v Database 2
v DB2
v DB2 Universal Database
v DFSMS/MVS
v DFSMSdfp
v DFSMSdss
v DFSMShsm
v DFSMSrmm
v DFSORT
v Enterprise System/9000
v ES/3090
v ES/9000
v ESCON
v Extended Services
v GDDM
v IBM
v Infoprint
v Language Environment
v Macro Assembler/2
v MQSeries
v MVS
v MVS/DFP
v OS/2
v OS/2 WARP
v OS/390
v Print Services Facility
v RACF
v RMF
v Sysplex Timer
v System/370
v VM/ESA
v VTAM
v zSeries
v z/Architecture
v z/OS
v z/OS.e
v z/VM
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
578
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, and service names may be trademarks or service marks of others.
Notices
579
580
Name
Address
Company or Organization
Phone No.
E-mail address
SA22-7638-12
___________________________________________________________________________________________________
Cut or Fold
Along Line
_ _ _ _ _ _ _Fold
_ _ _and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
PERMIT NO. 40
IBM Corporation
Department 55JA, Mail Station P181
2455 South Road
Poughkeepsie, NY
12601-5400
_________________________________________________________________________________________
Please do not staple
Fold and Tape
Fold and Tape
SA22-7638-12
Cut or Fold
Along Line
Printed in USA
SA22-7638-12