GC38 1015 0_OS_VS2_System_Messages_Rel_3.7_Jul76 0 OS VS2 System Messages Rel 3.7 Jul76
User Manual: GC38-1015-0_OS_VS2_System_Messages_Rel_3.7_Jul76
Open the PDF directly: View PDF 
.
Page Count: 458
| Download | |
| Open PDF In Browser | View PDF |
GC38-1015-0
File No. S370-40
Systems
I
OS/VS Message Library:
VS2 System Messages
VS2.03.801
VS2.03.803
VS2.03.804
VS2.03.807
VS2.03.808
VS2.03.810
VS2.03.813
This minor revision incorporates the following Selectable Units:
VTAM2
JES2 Release 4.0
Scheduler Improvements
Supervisor Performance #2
Data Management
IBM 3800 Printing Subsystem
TSO/VTAM
VS2.03.801
VS2.03.803
VS2.03~804
VS2.03.807
VS2.03.808
VS2.03.810
VS2.03.813
First Edition (July, 1976)
This is a reprint of Ge38. '} 002-4 incorporating ,changes released in the following
Selectable Unit Newsletters:
GN28-2632
GN28-2649
GN28-2714
GN28-2706
GN28-2721
GN28-2717
GN28-2658
(dated January 16, 1976)
(dated May 28, 1976)
(dated May 28,1976)
(dated May 28, 1976)
(dated July 30, 1976)
(dated May 28,1976)
(dated May 28,1976)
This edition applies to Release 3.7 of OS/VS2 and to all subsequent releases of OS/VS2 until
otherwise indicated in new editions or Technical Newsletters. Changes are continually made to
the information herein; before using this publication in connection with the operation of IBM
systems, consult the latest IBM System/370 Bibliography, GC20"()001, for the editions that are
applicable and current.
..
Requests for copies of IBM publications should be made to your IBM representative or to the
IBM branch office serving your locality..
•
..
.
A form for readers' comments is provided at the back of this publication. If the form has bqin
removed, comments may be addressed to IBM Corporation, fublications Development,
Department D58, Building 706-2, PO Box 390, Poughkeepsie, N. Y. 12602. Comments become
the property of IBM.
.
© Copyright International Business Machines Corporation\ 1972, 1974, 1975, 1976
Preface
This publication lists the system messages produced by IBM-supplied components of the
operating system. The causes of the message are explained, the accompanying actions by the
operating system are described, and appropriate responses are suggested. The messages are
presented in alphameric order.
Associated PubllcatiORIi
This publications contains some messages that appear in other publications and are duplicated in
this publication, and some messages that appear in this publication only. Those publications that
contain messages or that serve as references to specific messages are listed at the beginning of
their appropriate message sections in this publication.
Those publications that introduce concepts and terminology relevant to all messages are:
os /VS
Data Management Services Guide, GC26..;3783
OS/VS2 Supervisor Services and Macro Instructions, GC28-0683
Operator's Library: OS/VS2 Reference (JES2), GC38-0210
OS/VS2 System Programming Library: Debugging Handbook, GC28-0632
OS /VS2 Jel, GC28-0692
OS/VS2 System Programming Library: Service Aids, GC28-0674
I
s Utilities,
GC35-0005
t of the books belonging to the OS/VS Message Library is contained in figure 2 of this
ation.
Preface
3
4
VS2Sy.tem Me..a.e. (VS2 Release 3.7)
Contents
Summary of Amendments
9
Introduction
11
Section
1:
HASP JES2 Messages .
Section
2:
ICF
Power Warning Feature Messages
2-1
Section
3:
IDA
Virtual Storage Access Method Messages .
3-1
Section
4:
IDC
Access Method Services Messages
4-1
Section
5:
lEA
Supervisor Messages
5-1
Section
6:
IEC
Data Management Messages
6-1
Section
7:
lED
Telecommunications Access Method (TCAM) Messages
7-1
Section
8:
lEE
Master Scheduler Messages
8-1
Section
9:
IEF
Job Scheduler Messages .
9-1
Section
10: lEI
System Generation Messages
10-1
Section
11: IFA
SMF Dump Program Messages
11-1
Section
12: IFB
Environment Recording Messages
12-1
Section
13: IGF
Machine-Check Handler, Dynamic Device Reconfiguration, Channel Check
Handler and Missing Interrupt Handler Messages
13-1
Section
14: IHJ
Checkpoint/Restart Messages
14-1
Section
15: IKJ
TSO Messages
TSO Programmer and Operator Messages
TSO Terminal Messages.
15-1
15-1
15-9
Section
16: IKM
PL/l Syntax Checker Messages
16-1
1-1
Section 16A: IKT
TSO/VTAM (VS2.03.813)
16A-l
Section
17: ILR
Auxiliary Storage Management
17-1
Section
18: IPD
FORTRAN Syntax Checker Messages .
18-1
Section
19: IQA
Dynamic Support System Messages
19-1
Section
20:
IRA
System Resources Manager Messages
20-1
Section
21:
IRB
MF /1 Messages
21-1
Section
22:
1ST
VTAM Messages
22-1
Section
23:
Problem Determination Tables I and II
23-1
Contents
5
Figures
Figure
Figure
Figure
Figure
Figure
6
1.
2.
3.
4.
5.
Customizing Your Message Library
OS/VS Message Library . .
OS/VS2 Message Directory . . .
Variable Data . . . . . . . . .
Problem Determination (Tables I and II)
VS2 System Messages (VS2.03.813)
12
13
14
16
23-1
Contents Directory
7
8
VS2 System Messages (VS2 Release 3.7)
VS2.03.813
TSO/VTAM----------j~~
Contents Directory
8.1
•
8.2
VS2 System Messages (VS2.03.813)
Summary of Amendments
for GC38-1002-4
OS/VS2 Release 3.7
Changes have been made throughout this publication to
reflect a Service Update - OS/VS2 Release 3.7.
In addition, pertinent technical and editorial changes
have been made.
The following new messages have been added:
IDC394I, IDCOlO2I, IDCOlO5I, IDCOI06I, IDCOlO7I,
mCOI12I, IDC0361I, IDC0362I, IDC0363I, IDC08lOI,
IDC08111, IDC0812I, IDC0813I, IDC0814I, IDC0815I,
IDC0816I, IDC0817I, IDC0832I, IDC2074I, IDC2103I,
IDC2lO8I, IDC2109I, IDC21lOI, IDC21111, IDC2360I,
IDC2364I, IDC2375I, IDC2399I, IDC2833I, IDC2834I,
IDC2916I, IDC2972I, IDC3113I, IDC3190I, IDC3380I,
IDC3584I, IDCOl120I, IDCOl121I, IDCOI122I,
IDCOl123I, IDCOl1241 IDCOlI46I, IDCOl190I,
IDC21100I, IDC21 1011, IDC21102I, IDC2IlO3I,
IDC21104I, IDC21 1051, IDC21106I, IDC21 1071,
IDC21108I, IDC21141I, IDC21144I, IDC31140I,
IDC31142I, IDC31143I, IDC31145I, IDC31160I,
IDC31170I, IDC31180I, IDC31181I, - IEA983I IEC305I, IEC702I - IEF688I.
The following system messages have been changed:
$HASP096, $HASP098, $HASP165, $HASP260,
$HASP310, $HASP311, $HASP352, $HASP353,
$HASP355, $HASP375, $HASP376, $HASP403,
$HASP419, $HASP420, $HASP431, $HASP433,
$HASP434, $HASP435, $HASP986 - IDC0063I,
IDC0733I, IDC2065I, IDC2095I, IDC2100I, IDC2096I,
IDC2650I, IDC3009I, IDC3062I, IDC3732I, IDC3734I,
IDC3905I, IDC4999I - IEAOOOI, IEAOOlI, IEA700I,
IEA877A - IEC036I, IECl40I, IEC141I, IEC151I,
IEC156I, IEC161I, IEC331I, IEC403A, IEC701DIED460I, IED464I - IEE143I, IEE250I, IEE301I,
IEE328I, IEE349I, IEE380I, IEE450I, IEE600I, IEE713I,
IEE930I - IEF197I, IEF260I, IEF453I, IEF612I, IEF624I
- IFBOIOD - IHJOOOI, IHJOO7I - IST025I, ISTl06I,
ISTl08I, ISTl09I, ISTllOI, ISTll11, ISTl13I, ISTl23I,
IST13OI, ISTl31I, ISTl51I, ISTl63I, ISTl64I, IST285I,
IST286I, IST288I, IST289I, IST300I, IST514I, ISTSI5I,
IST625I, IST626I, IST627I, IST653I, IST657I.
The following system messages have been deleted:
IDC3074I, IDC3560I, IDC messages without enhanced
VSAM - IEC3031 - IEE323I, IEE348I, IEE377I, IEE390I,
IEE391I, IEE415I, IEE475I, IEE514I, IEE907I, IEE9121 IEF298I, IEF312I, IEF409I, IEF415I, IEC3311 - IKJ TSO
terminal messages.
Summary of Amendments
9
Summary of Amendments
for GC38-1002-3
as Updated by GN28-2608
VS2 Release 3
Message Id
Reason
Message Id
Reason
$HASP260
IDC33511
IDC37441
IDC37451
IDC3905
IEC0201
IECl321
IEC1451
IEC2501
IEC2531
Corrections.
Additional information.
Correction.
Additional information.
Additional information.
Corrections.
New message.
Additional information.
New message.
New message.
IEDOl2
IED0641
IED0981
IED4601
IED4641
IEE0701
IEE07l1
IEF6571
ILROO8W
ILROO9I
Additional information.
Correction.
Additional information.
Additional information.
Additional information.
Correction.
Correction.
Correction.
New message.
New message.
Summary of Amendments
for GC38-1002-3
as Updated by GN28-2590
VS2 Release 3
Message Id
Reason
Message Id
Reason
IDAOO5
IDAOl8
IDAOl9
IDA021
IDA021
IDA024
IDA025
IEA858
IEA9771
IEC145I
IEC3021
IEC3031
IEC5121
IEC513D
IED0151
lED 1991
IED2171
IED2221
IED235D
IED2571
IED2581
IED309D
IED4601
IEE094D
IEE3131
IEF0851
IEF2871
IEF655
IEF6761
IEF7021
IGF5131
IHJOOll
IHJOO71
IHJOO9I
IHJ0111
IHJ0121
Additional information.
Corrections.
Corrections.
Typographical error.
Corrections.
New message.
New message.
Additional information.
New message.
Additional information.
New message.
New message.
Additional information.
New message.
Additional information.
Deleted.
Deleted.
Deleted.
Deleted.
Deleted.
Deleted.
Deleted.
Additional information.
Corrections.
Additional information.
Additional information.
Additional information.
Corrections.
Corrections.
Additional information.
Additional information.
Additional information.
Additional information.
Deleted.
Deleted.
Deleted.
IHJ0131
ISTOOll
ISTOO6I
ISTOO81
ISTOO9I
IST0121
IST0161
IST0251
IST0461
IST047I
IST0481
IST0591
IST064I
IST0681
IST0921
1ST 1021
ISTt041
IST1501
IST1511
IST1551
1ST 1601
IST1651
IST166I
IST2211
IST2221
IST3031
IST3401
IST5141
IST5921
IST6081
IST6091
IST6291
IST6301
IST6311
IST6461
IST8511
Deleted.
Corrections.
Corrections.
Deleted.
Corrections.
~om.
ections.
ections.
ections.
Corrections.
Corrections.
Corrections.
Deleted.
Additional information.
Deleted.
Corrections.
Corrections.
Deleted.
Corrections.
Deleted.
Deleted.
Deleted.
Deleted.
Deleted.
Deleted.
Corrections.
New message.
Corrections.
Corrections.
Additional information.
Additional information.
New message.
New message.
New message.
New message.
Deleted.
The IDC section has been updated to include the enhanced VSAM and Mass Storage System function messages.
10
VS2 System Messages (VS2 Release 3.7)
Introduction
The OS/VS Message Library is designed so that you can have
the messages and codes documentation that fits your specific
needs. You no longer have to maintain an enormous manual.
especially operations personnel, will require access to these
books; it may not be necessary for applications oriented
personnel to have their own copies.
If you are a system programmer or installation manager, you
may want to have all the books in the Message Library in a
consolidated document.
Each installation will require at least one copy of VS 1 System
Codes or VS2 System Codes which contain the system
completion codes and wait state codes produced by all the
components of OS/VSl or OS/VS2. All programming
personnel, especially operations personnel, will require access
to one of these books, .although applications oriented
personnel may not need to have their own copies.
If you are an operator, you may want to include System
Messages and System Codes in your Operator's Library.
If you are an assembler language programmer, you may want
to have System Messages, System Codes, Linkage Editor and
Loader Messages, and the message section from the Assembler
Language Programmer's Guide in a consolidated document.
If you are a COBOL programmer, you may want to add Utilities
Messages to your COBOL programmer's guide.
In any case, you can select the appropriate books to build a
Message Library to meet your needs.
Basic Books
Each installation will require at least one copy of VSl System
Messages or VS2 System Messages. You will receive at the
console or in your output listings, some subset of the
messages in these books no matter which options have been
included in your operating system. All programming personnel,
Optional Books
Routing and Descriptor Codes contains routing and descriptor
codes for all messages that have these codes. Your
installation's system programmer will need this book, especially
if your operating systems have multiple console support
(MCS).
Depending on your requirements, you may want to have copies
of Utilities Messages, Service Aids and OLTEP Messages, or
Linkage Editor and Loader Messages. Select the books that you
need and keep them either in the appropriate System Library
Manual or in your customized Message Library.
Introduction
11
VS1 System Codes
GC38·1003
Customizing Your OS/VS Message Library
VS1 System Messages
GC38·1001
Mass Storage
System Messages
GC38·1000
Utilities Messages
GC38·1005
Service Aids and
OLTEP Messages
GC38·1006
Account Messages
GC38·1010
Routing and
Descriptor Codes
GC38·1004
Linkage Editor and
Loader Messages
GC38·1007
Subsystem Support
Services Messages
GC38·1011
YourOSNS
Message Library
VS2 System Codes
GC38·10OS
VS2 Routing and
Descriptor Codes
GC38·1102
CD
®
o
CD
Select the VS 1 publications that are compatible with your system.
Select the VS2 publications that are compatible with your system.
Select the shared, supplementary messages publications that fit the
needs of your installation.
If your installation uses a particular compiler or application program,
you may want to append the program's messages to your message
library. These messages are located in the associated programmer's
reference guides.
Figure 1. Customizing Your OS/VS Message Library
12
VS2 System Messages (VS2 Release 3.7)
Programmer's
Reference
Guides
VS2.03.813
OS/VS Message Library
Publication
Order Number
Contents
Mass Storage System Messages
GC38-1000
ICB, ICG messages
VS 1 System Messages
GC38-1001
lEA, IEC, lED, lEE, IEF, lEI, IFA, IFB, IGF, IHB,
IHJ, IHK messages
VS2 System Messages
GC38-1002
HASP, ICF, IDA, IDC, lEA, IEC, lED, lEE, IEF, lEI,
IFA, IFB, IGF, IHJ, IKJ, IKM, IKT, ILR, IPD, lOA, IRA,
IRB, 1ST messages
VS1 System Codes
GC38-1003
all VS1 completion and wait state codes
Routing and Descriptor Codes
GC38-1004
all VS1 routing and descriptor codes
Utilities Messages
GC38-1005
IBC, IEB, IEH messages
Service Aids and OL TEP Messages
GC3B-1006
A/HHL, A/HMA, A/HMB, A/HMO, IFC, IFD, IMC,
ISDA messages
Linkage Editor and Loader Messages
GC38-1007
I EW messages
VS2 System Codes
VS1 RES RTAM and Account Messages
-
"GC38-100S),
~GC38-1010
"
all VS2 completion and wait state codes
IFS and IKJ m.......
.~
---
G-c~8-
Subsystem Support Services Messages
GC38-1011
BOB messages
JES3 Messages
GC38-1012
IAT messages
VS2 Routing and Descriptor Codes
GC38-1102
all VS2 routing and descriptor codes
See:
emulator messages
--B>
Je)
In other publications:
Emulator publications
IBM System/370
8ibilography,
GC20-0001
IBM 3790 Communication System:
Programmer's Reference
GC27-0016
BOI messages
Problem Determination Aids and Messages and
Codes for Graphic Programming Services (GPS)
and Graphic Subroutine Package (GSP)
GC27-6974
IFF messages
DOS/VS and OS/VS TOL TEP for VTAM
GC28-0663
IT A messages
OS/VS System Modification Program (SMP)
GC2S-0673
HMA messages
OS/VS - VM/370 Assembler Programmer's
Guide
GC33-4021
IFO messages
VS2 TSO Terminal Messages Directory
SY28-0654
I KJ messages
Figure 2_ OS/VS Message Library
Introduction
13
Prefix
Component
Publication Title
Order Number
AHL
Generalized Trace Facility
Service Aids and OLTEP Messages
GC38-100B
AMA
AMAPTFLE
AMASPZAP
Service Aids and OLTEP Messages
GC38-100B
AMB
AMBLIST
Service Aids and OLTEP Messages
GC38-100B
AMD
AMDPRDMP
AMDSADMP
Service Aids and OL TEP Messages
GC38-100B
BOB
Subsystem Support Services
Subsystem Support Services
Messages
GC38-1011
BOI
3790 Communication
IBM 3790 Communication
System: Programmer's Reference
GC27-001B
HASP
JES2
VS2 System Messages
GC38-1002
HHL
Generalized Trace Facility
Service Ai~ and OLTEP Messages
GC38-100B
~~
HMA
HMAPTFLE
HMASPZA'P
HMASMP
Service Aids and OLTEP Messages
GC38-100B
System Modification Program
GC28-0B73
HMB
HMBLIST
Service Aids and OLTEP Messages
GC38-100B
HMD
HMDPRDMP
HMDSADMP
Service Aids and OLTEP Messages
GC38-100B
IAT
JES3
JES3 Messages
GC38-1012
IBC
Independent Utility
Utilities Messages
GC38-1005
ICB
Mass Storage System Communicator
Mass Storage System (MSS)
Messages
GC38-1000
ICF
Power Warning Feature
VSl System Messages
VS2 System Messages
GC38-1001
GC38-1002
ICG
Mass Storage Control Table Create
Mass Storage System (MSS)
Messages
GC38-1000
IDA
VSAM Control Block Expansion
VSl System Messages
VS2 System Messages
GC38-1001
GC38-1002
IDC
Access Method Services
VSl System Messages
VS2 System Messages
GC38-1001
GC38-1002
lEA
Supervisor
VS 1 System Messages
VS2 System Messages
GC38-1001
GC38-1002
IEB
Data Set Utility
Utilities Messages
GC38-1005
IEC
Data Management
VSl System Messages
VS2 System Messages
GC38-1001
GC38-1002
lED
Telecommunications Access Method
VSl System Messages
VS2 System Messages
GC38-1001
GC3B-l002
lEE
Master Scheduler
VSl Sys~em Messages
VS2 System Messages
GC38-1001
GC38-1002
IEF
Job Scheduler
VSl System Messages
VS2 System Messages
GC38-1001
GC38-1002
Figure 3. Message Directory (Part 1 of 2)
14
VS2 System Messages (VS2.03.813)
VS2.03.813
Prefix
Component
Publication Title
Order Number
IEH
System Utility
Utilities Messages
GC38-1005
lEI
System Generation
VSl System Messages
VS2 System Messages
GC38-1001
GC38-1002
lEW
Loader and Linkage Editor
Linkage Editor and Loader Messages
GC38-1007
IFA
SMF Dump Program
VSl System Messages
VS2 System Messages
GC38-1001
GC38-1002
IFB
Environment Recording
VSl System Messages
VS2 System Messages
GC38-1001
GC38-1002
IFC
IFCEREPO
IFCDIPOO
Service Aids and OLTEP Messages
GC38-1006
IFD
Online Test Executive
Service Aids and OlTEP Messages
GC38-1006
IFF
Graphic Programming Services
Problem Determination Aids and
Messages and Codes for
GPS and GSP
GC27-6974
IFO
Assembler
O~VS - VM/370 Assembler
GC33-4021
Programmer's Guide
IFS
RTAM
VSl RES RTAM and Account
Messages
GC38-1010
IGF
Recovery Management
VSl System Messages
VS2 System Messages
GC38-1001
GC38-1002
IHB
Macro Expansion
VSl System Messages
GC38-1001
IHJ
Checkpoint/ Restart
VSl System Messages
VS2 System Messages
GC38-1001
GC38-1002
IHK
CRJE
VSl System Messages
GC38-1001
IKJ
Time Sharing Option
VS2 System Messages
OS/VS2 TSO Terminal Messages
Directory
VSl RES RTAM and Account
Messages
GC38-1002
SY28-0654
Account Facility
GC38-1010
IKM
PL/ I Syntax Checker
VS2 System Messages
GC38-1002
IKT
TSO/VTAM
VS2 System Messages
OS!VS2 TSO Terminal Messages
Directory
GC38-1002
SY28-0654
ILR
Auxiliary Storage Management
VSl System Messages
VS2 System Messages
GC38-1001
GC38-1002
IMC
IMCJOBQD
IMCOSJCD
Service Aids and OlTEP Messages
GC38-1006
IPD
FORTRAN Syntax Checker
VS2 System Messages
GC38-1002
IQA
Dynamic Support System
VSl System Messages
VS2 System Messages
OS/VS Dynamic Support System
GC38-1001
GC38-1002
GC28-0640
IRA
Resource Management
VS2 System Messages
GC38-1002
IRB
MF/1
VS2 System Messages
GC38-1002
ISDA
ISDASDAO
Service Aids and OLTEP Messages
GC38-1006
1ST
VTAM
VS1 System Messages
VS2 System Messages
GC38-1001
GC38-1002
ITA
DOS/VS and OS/VS TOlTEP
TOlTEP for VTAM
GC28-0663
Figure 3. Message Directory (Part 2 of 2)
Introduction
15
Variable data within message texts will be indicated where it appears by a small letter representation of the item as follows:
address
adr
operand name
op
opt
code
cde
option name
operation name
opr
cm
command name
parameter name
prm
dsn
data set name
path
pth
ddn
DDname
procedure name
ppp
ddd
device address
pgm
program name
devname
device name
return code
devtyp
rc
device type
sens
sense information
err
error description
serial number
ser
func
function name
station name
station
init
initiator name
jjj
status
stat
job name
j
step name
sss
job id (JES2)
subcommand name
keywd
subcm
keyword name
ttt
task name
lab
label name
uuuuuuuu
unit (OLTEP)
labtyp
label type
userid name
uSEuid
library name
lib
val
value
Ina
line address
volume serial
vol
macro name
mac
non-specific data
xxx
member name
mem
yyy (appearing in the same message as
mod
module name
xxx)
nnn
number
Optional field--may not appear in
message text when printed.
Indicates a choice of one of the items
included within.
Figure 4. Variable Data
16
VS2 System Messages (VS2.03.813)
VS2.03.803
Section 1: JES2 Messages ($HASP)
Component Name
HASP
Program Producing Message
JES2
Audience and Where Produced
For operator: console.
For programmer: SYSOUT listing.
•
Message Format
[hh.mm.ss) j
{;.,
} $HASPnnn text
f> [+1
hh.mm.ss
Time stamp (optional).
j
JES2 job identification (optional).
*
Indicates a request for operator action.
@
Indicates a request for operator action by JES2 generation modules or RMTGEN.
fI Blank, if no operator action is required.
+
Indicates the message is issued by JES2 generation or RMTGEN when no action is
required.
nnn
Message serial number
text
Message text.
Comments
Each message is assigned an importance level, indicated in the message explanation. The operator can
control the messages printed on a given console (via the $T command) by eliminating messages with
importance levels below a certain value. See Operator's Library: OS/VS2 Reference (JES2).
Associated Publications
OS/VS2 ~tem Programming Library: JES2, GC38-0002
Operator's Library~OS/VS2 MVS JES2 Commands, GC23-0007-0
OS/VS2 JCL, GC28-0692
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
$HASPOOO
response to a JES2 command
Explanation: The JES2 command processor has received a
command and has issued a direct response to the console of
entry or associated console. The response indicates
acceptance, rejection, or the action taken in response to the
command entered. The JES2-assigned job identification, if
present in the response, appears as the first text characters of
the response line as shown.
• Responses to out-of-line areas of a console contain a
control line, followed by responses to the individual
command entry. The control line contains up to 34
characters made up of the message identifier, time of the
response, and the edited version of the command entered.
• Responses to in-line areas of a console do not contain a
control line, but individual responses,· each appropriately
identified as a command response. The JES2-assigned job
identification, if present in the response, appears in the
operator-controlled job identification field of the message.
If the message is routed by route code, the importance level is
7, if routed by console id, the importance level is 15.
The command responses may be one of the following:
AUTOMATIC COMMAND LIMIT REACHED - The operator
entered a $TA command and all the installation-specified
automatic command elements were found to be in use.
System Action: Processing continues.
Operator Response: Delete some of the current elements or
wait until elements are no longer needed. Inform the system
programmer of the need for additional elements.
AUTOMATIC COMMANDS HALTED - The operator entered a
$TA command and the system found that either the
operator has halted issuance of automatic commands via a
$ZA command, or the system automatically issued the $ZA
command. (See message $HASP002.)
System Action: The command is ignored. Processing
continues.
Operator Response: Verify that the current automatic
command elements are correct and, if desired, enter a $SA
command to begin automatic command issuance.
CON ee A = cca F = cca I = cca J = cca N = cca 0 = cca
Q = cca U = cca - The operator entered a $TM command.
The automatic redirected response settings for the entry
console specified by ee are set for the display operands as
listed. For example, if the response for A = cca is A = 2B,
the response of a $DA entered from console ee will be
displayed on console 2, out-of-line area B if that area is
Section 1: $HASP Messages - JES2
1-1
VSi.Ol.803
available for the displaying of JES2 messages.· The following
list indicates which display commands are affected by the
above display items:
item command(s)
A $DA
$DF
I $01
J $DJ(job), $DS(system task control job), $DT(time
sharing user job), $D'jjj' where jjj is the jobname.
N $DN
$00
o
o
Q $DQ
U $DU
System Action: Processing continues.
Operator Response: None~
ENTRY CONSOLE NOT SUPPORTED - The operator entered
a $TM command specifying a response console that is
unknown to JES2.
System Action: The command is ignored and processing
continues.
Operator Response: Enter the $TM command for the proper
console.
(For example, to create an automatic command element a
text operand was not accompanied by an I == or T ==
operand.)
System Action: The command is ignored and processing
continues.
Operator Response: Enter the corrected command.
JES2 NOT DORMANT - - SYSTEM DRAINING - The operator
entered a $P JES2 command to withdraw JES2 from the
system, but not all of JES2's functions have completed.
System Action: JES2 is not withdrawn and no new functions
will. be started; however, jobs may continue to be entered.
Operator Response: Reenter the command when all JES2
functions are complete.
rl;~~}
j j j j jobname
} c == classes
DRAINED
monitor name
ACTIVE
INACTIVE
- The operator entered a $DU or a $T devicename
command. The specified initiator is in the status indicated:
HALTING The initiator is currently processing a job but will
not select new work.
HALTED The initiator is not processing work and will not
do so.
DRAINING The initiator is currently processing a job but will
not select new work. Upon completion of the job
the initiator itself will end execution.
DRAINED The initiator has ended or is in the process of
ending execution.
ACTIVE
The initiator is currently processing a job and will
continue to select eligible work.
INACTIVE The initiator is not processing work, but would
do so if work were available to it.
If the initiator is selecting execution batch monitor jobs,
XB will be displayed prior to the INIT portion.
Initiator status is followed by the job identifier if the
initiator is currently processing a batch job, eight asterisks
if the initiator is not currently active, or the batch monitor
name if the initiator is processing batch monitor jobs and no
batch monitor job is currently active.
The classes are the job classes, in priority order, that the
initiator will use to select jobs when the next job is to be
selected.
System Action: Processing continues.
Operator Response: None.
EXECUTION
til
OUTPUT
PRT {
10 xxx T = hh.mm.ss T == ssss text - The operator entered a
$TA command and the response indicates the contents of
the command element being created, displayed, modified, or
deleted. If the operator is attempting to alter or create an
automatic command element and a diagnostic preceeds this
message, the element will be deleted.
System Action: Processing continues.
{:}~:::~{~~f~~:Gl{~~;~j;jU
AWAITING
TSU
~~
LOCAL
name
}
PUN
{~~ 1
LOCAL
name
PURGE
EXECUTING
{;:l
)
ON devicename
PRIO pp
HOLD
}
DUPLICATE
{Sid, sid ... }
CANCEL
ANY
{
PURGE
j IND
I
t
)
fifi
INSUFFICIENT OPERANDS - The operator entered a $TA
command without specifying all of the required operands.
1-2
VS2 System Messages (YS2.03.803)
Explanation: The operator entered a $D N command to
display job queue information.
JOB
The JES2-assigned identification of the
batch job.
The JES2-assigned identification of the
STC
system task.
TSU
The JES2-assigned identification of the
time-sharing user.
jjjj
The job number.
The jobname appearing on the job card or
jobname
in the start procedure operand.
The execution class (A-Z,O-g)
c
The job is awaiting conversion.
The job is a system task.
$
@
The job is a time-sharing user.
Rn
The number of a remote device.
The number of a specific local device.
Un
LOCAL
Any local device.
name
A destination represented by a symbolic
name defined by the installation.
The JES2 scheduling priority.
pp
devname
The JES2 name of the device performing a
function for the job.
HOLD
The job is currently held or will be held at
the end of the current phase.
DUPLICATE The job is awaiting execution because
another job with the same job name is
currently executing.
CANCEL
The job will be canceled at the end of the
current phase.
PURGE
The job will be purged at the end of the
current phase.
VS2.03.803
sid ...
IND
The name of the system (up to six
systems) on which this job is executing or
may execute. ANY indicates the job is
eligible for any system in the shared JES2
configuration.
Indicates that the job is eligible only for a
system that is in independent mode.
System Action: Processing continues.
Operator Response: None.
JOB}NUMBER SET TO j
STC
{ TSU
- The operator entered a $TJ, $TS, or $TT command with
only the first operand indicating that the job number base is
to be reset to the indicated value.
System Action: The base value for assigning job
identification numbers is set to the value indicated. The next
job entering the system will be assigned that value
(assuming no other job currently has the value) and the
base will be incremented by 1.
Operator Response: None.
JOB(S) NOT FOUND - The operator has entered a job list
command and no jobs were found that· met the selection
criteria.
System Action: Processing continues.
Operator Response: None.
~\
~
LIST INCOMPLETE - The system was overloaded with
console activity at the time of job queue searching and the
last job displayed was purged from the system while the
JES2 command processor was waiting for system resources
to display the message.
System Action: Processing continues.
Operator Response: Reenter the command when console
activity is not high. The command entry should be modified
to limit responses to only required information.
NO ACTIVE JOBS - The operator entered a $DA command.
The JES2 system found that no active jobs in the queues
met the specifications given in the $DA command.
System Action: Processing continues.
Operator Response: None.
NO AUTOMATIC COMMAND FOUND - The operator entered
a $TA command specifying no operands beyond operand
one. No automatic command element was found with the id,
if specified, or if one was found, the console has no
authority to display it.
System Action: Processing continues.
Operator Response: Enter the request on a sufficiently
authorized console, (one at least as authorized as the
console creating the element).
NO DATA SETS RE-ROUTED - The operator has entered a
$R command and JES2 is unable to re-route the requested
data sets.
System Action: JES2 continues processing.
Operator Response: Insure that the job, device, or remote
whose output is to be re-routed is correctly specified and
reenter the $R command.
NO JOBS RELEASED - The operator entered a $AA
command telling the system to release all jobs held by the
$HA command and no jobs were found to be held by that
command.
System Action: Processing continues.
Operator Response: If jobs are known to be held, use
explicit release commands: $A •
$AJ, $AS, or $AT as
appropriate to release the jobs.
jjj:
NO OPERATOR REQUESTS - The operator entered a $DO
command and JES2 found no outstanding operator requests.
System Action: Processing continues.
Operator Response: None.
•
NO OUTPUT QUEUED - The operator entered a $DF
command and there was no work in the output forms queue
for the operands given in the $DF command.
System Action: Processing continues.
Operator Response: None.
OK - The command has been accepted for action. The
appropriate action has been taken or has been scheduled.
The OK response is an indication that the JES2 command
processor found no fault in the command; however, actions
such as an attempt to initiate a function already scheduled
or in progress may be ignored.
System Action: Processing continues.
Operator Response: None.
OUT R=
Rn
}
Un
{ LOCAL
name
[O=overlay name]
{ (NONE)
F=ffff C=cccc T=tttt W=
wwwwwwww
}
[B=Y] CLASS C1=nn1.C2=nn2 •...
Explanation: The operator entered a $0 F command to
display the output forms queue. There is work in the output
forms queue for destination R (where Rn is a remote
device, Un is a local device with special routing, LOCAL is
any local device with normal routing, and name is the
symbolic name for a destination specified in the DESTID
initialization parameter), requiring forms ffff, carriage
control tape (or FCB image) cccc, printer train (or UCS
image) tttt, writer ID wwwwwwww (NONE if a writer ID is
not specified), 3800 forms overlay name (if indicated), and
the 3800 burster B (if indicated). There are nnl work
elements for class CI, nn2 work elements for class C2, and
so on. An nn value of *'II for a class indicates that there are
more than 99 work elements queued in that class.
System Action: Processing continues.
Operator Response: None.
RESPONSE LOCATION L = cca UNAVAILABLE - The
operator entered a command for which an output display
area had not been previously defined.
System Action: Processing continues.
Operator Response: Either enter the proper area or
establish the area and re-enter the command.
SYSTEM DRAINING - The operator entered a $P command
and the system will discontinue scheduling of work. Jobs
that would normally be selectable for processing will not be
selected for new work.
System Action: No new functions are started; however, jobs
may continue to be entered.
Operator Response: Enter the $S command when it is
desired to resume JES2 processing.
$cm'jjj' MULTIPLE JOBS FOUND - The operator entered the
indicated command. The system found more than one job in
the system with the jobname and no action was taken. The
response lines will indicate what jobs were found.
System Action: Messages listing information about all jobs
found will be displayed following this response.
Operator Response: If the action taken for the command is
desired, reenter the command with the JES2 job id (j).
Section 1: $HASP Messages - JES2
1-3
VS2.03.803
Warning: If the console has not been set up to display the
job id (j), it will not be displayed; only the jobname (jjj) will
appear.
devname IN USE - The operator entered a $S or $T
command for the indicated device. The system found the
device but could not take the indicated action for one of
the following reasons:
• If the command was a $T, the device is currently active
and the operands T = , F = , and C = cannot be used
until the device is idle or has been halted for a forms,
carriage or train setup.
• If the command was a $S 1) the device was already
allocated to a non-JES2 function or, 2) the system
programmer has caused more than one deivce to be
assigned to more than one logical device and JES2 is
currently using the deivce for another function.
System Action: The command is ignored and processing
continues.
Operator Response: Determine the use of the device and, in
the case of .the $T command, wait until the device is idle or
JES2 has stopped the device for operator assistance. In the
case of the $S command, wait for the jobs or the JES2
function to unallocate the device before reentering the $S
command for the device. (JES2 unallocates devices when
they go into DRAINED status.)
devname NOT AVAILABLE - The operator entered a $S
command for the indicated device. The device was already
allocated to a non-JES2 function, the system programmer
has assigned the device to more than one physical unit and
JES2 is currently using the unit for a different device
function, or the unit is offline and is not allocatable.
System Action: The command is ignored and processing
continues.
Operator Response: Determine the use of the unit assigned
to the device. If the unit is offline, place it online and use
the VARY command to make it ayailable for allocation
before reentering the $S command. If the unit is busy with
a JES2 function, wait for it to complete, enter $P for the
owning device, and enter the $S command to activate the
new function. If the unit is allocated to a non-JES2 function,
wait until it becomes available before reentering the $S
command.
{CUU}
devname
settings***
I
SNA
DRAINED
DRAINING
ACTIVE
INACTIVE
HALTED
PAUSED
JOB}
STC
{ TSU
j jjj device
- The operator entered a $DU or $T dev command. If the
device is an SNA (systems network architecture) device,
SNA is displayed. If the device is a BSC (binary synchronous
communication) device, cuu is that device's address.
The status of the device is indicated as follows:
DRAINED JES2 is not using the device and will not do so
until the device is started via a $S command.
DRAINING JES2 is currently using the device for the
processing of jobs, but will discontinue its use
upon completion of the current function.
INACTIVE JES2 is not using the device but would do so if
jobs were available and eligible for that device.
ACTIVE
JES2 is using the device for job processing and
will continue to do so as long as there are jobs
available and eligible for that device.
HALTED
JES2 has either requested operator assistance or
the operator has halted the device ($Z) and is
1-4
VS2 System Messages (VS2.03.803)
waiting for the device to be started via a $S
command.
PAUSED JES2 has paused between jobs and the device
will not be used until it is started via a $S
command or the device is brought out of READY
and then back into READY status.
If the operator has used operands when entering the $DU
command, a detailed status of the device will be displayed.
If the operator requested display information about lines,
remotes, or the JES2/VTAM interface, the status displayed
includes the status of the session on any logical (SNA) line.
(See the description of session status below.) If JES2 is
using the device, the job identification portion of the
messages will be displayed. The operator-controllable
settings for the device will be displayed following the status
or job identification portion of the message. Settings for the
various devices are as follows:
RJE line
E=YChannel end logging is in effect.
Channel end logging is not in effect.
E= N The line password has been set.
P = SET Remote reader
C=cDefault execution class for jobs read by
the reader.
Default message class for jobs read by
Q=qthe reader.
Jobs read by the reader will either be
H=Y/N
held (Y) or not held (N).
S = sid,sid, ...
IND
ANY
The default system affinity for jobs read
by the reader is sid,sid ... or ANY (for
any system in the Shared JES2 complex.
IND indicates that jobs read by the
reader will only be eligible for execution
on a system that is in independent
mode.
The default printer destination for jobs
P = dest read on the reader.
U = dest The default punch destination for jobs
read on the reader.
Local reader
Default execution class for jobs read by
C=cthe reader.
Default message class for jobs read by
Q=qthe reader.
Jobs read by the reader will either be
H=Y/N
held (Y) or not held (N).
A = DISPLAY - The reader has display command
authority only A = O.
The reader has system command
A = SYS authority A = 1.
The reader has device command
A = DEV authority A = 2.
The reader has job command authority
A = JOB A=4.
The reader has authority as indicated,
A = x+x+x (combination of above).
S = sid,sid ...
ANY
IND
The default system affinity for jobs read
by the reader is either sid,sid ... can be
specified a maximum of six times or
ANY (indicating any system). IND
indicates that jobs read by the reader
will only be eligible for a system in
independent mode.
VS2.03.803
P == dest U == dest -
The default printer destination for jobs
read on the reader.
The default punch destination for jobs
read on the reader.
Punch
F == ffff {,AUTO}
,OPER
- The punch is or will process forms
indicated. AUTO indicates that JES2 is free
to select output of different forms when
necessary to keep the device busy. OPER
indicates that the operator is controlling
the forms changing.
P == Y The punch (local punches only) will pause
between units of work and wait for the
operator to either enter a $S device
command or cause the unit to go "not
ready" and then "ready".
P == N The punch will. not pause between units of
work.
S == Y The punch will provide separator cards.
S == N The punch will not provide separator cards.
Q == classes - The punch will process output of the
classes indicated.
R == dest The current routing of the device.
Printer
F == ffff {,AUTO}
,OPER
- The printer is or will process forms
indicated. AUTO indicates that JES2 is free
to select output of different forms when
necessary to keep the device busy. OPER
indicates that the operator i~ controlling
the forms changing.
The printer (local printers only) will pause
P == Y between units of work and wait for the
operator to either enter a $S device
command or cause the unit to go "not
ready" and then "ready".
P == N The printer will not pause between units of
work.
C =={~~CC}[,STD]
- The printer is or will use carriage control
(FCB image if supported) as specified
(ccce). Or, if • is specified, the 3800
printer constructs the FCB based on the
current forms length. STD indicates that
the FCB image has been specified to be a
standard image.
T == tttt [,STD]
- The printer is or will use printer train (UCS
image if supported) as specified. Or, the
3800 ·printer is using or will use the default
character arrangement table as specified.
STD indicates that the UCS image has
been specified to be a standard image.
The printer is ignoring any
K == n program-supplied carriage control
information and is spacing n lines between
print lines, where n is 1, 2 or 3.
S == Y The printer will provide separator pages at
the beginning and end of work units. If the
printer is a remote, it will also print any
operator messages destined for the device.
S == N The printer will not provide separator
pages.
Q == classes - The printer will process output of the
classes indicated.
R == dest The current routing of the device .
B == Y The printed output from the 3800 printer
will be burst into separate sheets.
B == N The printed output from the 3800 printer
will be in continuous, fanfold mode.
M == Y The edge of the separator page in the
printed output from the 3800 printer will
be marked.
M= N The edge of the separator page in the
printed output from the 3800 printer will
not be marked.
o = name - The 3800 printer is using or will use the
forms overlay frame specified (name).
XI == id The 3800 printer is using or will use the
specified table as its first character
arrangement table.
X2 = id The 3800 printer is using or will use the
specified table as its second character
arrangement table.
X3 = id The 3800 printer is using or will use the
specified table as its third character
arrangement table.
X4 = id The 3800 printer is using or will use the
specified table as its fourth character
arrangement table.
The 3800 printer is using the copy
Y = id modification module as specified by id.
Session
lunameli~Ee
SUSPENDED
IDLE
" CLOSING
SUSPENDED -The data being transmitted on the session
has been temporarily interrupted so that
other data may flow.
IDLE No data is being transmitted on this
session.
CLOSING The session is attempting to disconnect,
but is currently waiting for VTAM activity
on its behalf to terminate ($DU LGNI was
entered).
Explanations of other possible session status (DRAINED,
DRAINING, ACTIVE, and INACTIVE) are given above.
System Action: Processing continues.
Operator Response: None.
{ ~~~}j
NOT FOUND
TSU
- The operator entered a $T job command attempting to
set the job's priority and/or execution class. The system did
not find the job.
System Action: Processing continues.
Operator Response: Enter the correct job identification for
the desired job.
jjj JOB NOT FOUND - The operator has entered a job
command with a jobname as operand and that job was not
found.
System Action: Processing continues.
Operator Response: None.
Section 1: $HASP Messages - JES2
1-5
•
VS2.03.803
It~su5
f~~~l
j jjj DATA SETS CANCELED
RELEASED TO {LOCAL }
RTMnnn
- The operator entered a $0 command to either cancel or
release any held sysout data sets for that job. If the data
sets are released to a destination other than the default
routing associated with that data set, then the new routing
is displayed.
System Action: Processing continues.
Operator Response: None.
{
{
JOB}
STC j jjj NO HELD DATA SETS
TSU
- The operator entered a $0 command to either cancel or
release any held sysout data sets for a job. However, the
job has no held sysout data sets.
System Action: Processing continues.
Operator Response: None.
JOB}
STC jjjj jobname NO READY DATA SETS
TSU
- The operator entered a $L command to list the ready
queued output for the designated job, but the job has no
ready data sets.
System Action: Processing continues.
Operator Response: None.
JOB}
STC jjjj jobname NO HELD DATA SETS
{ TSU
- The operator entered a $L command with the
HOLD operand to list the held queued output for the
designated job. However, the job has no held data sets.
System Action: Processing continues.
Operator Response: None
JOB}
STC j jjj NOT HELD
{ TSU
- The operator commanded the system to release the job
indicated explicitly and the job was not in an operator
releaseable status.
System Action: Processing continues.
Operator Response: None.
{
JOB}
STC j jjj NOT RESTARTABLE
TSU
- The operator entered a $E job command and the specified
job was found not to be in execution or not a normal batch
job.
System Action: The command is ignored and processing
continues.
Operator Response: None.
JOB}
STC jjjj jobname READY ql = ml q2 = m2
{ TSU
- The operator entered a $L command to list the ready
queued output for the designated job. Following 'READY' are
the class(es) and the count in each class of the ready
output. If the number of queued data sets for a sysout class
exceeds 99, U will appear in place of the number.
System Action: Processing continues.
{
~f:;}ator Response: None.
STC jjjj jobname HELD ql
TSU
1-6
= ml q2 = m2
YS2 System Messages (YS2.03.803)
- The operator entered a $L command with the HOLD
operand to list the held queued output for the designated
job. Following 'HELD' are the class(es) and the count in
each class of the held output.
System Action: Processing continues
Operator Response: None
{ ~~~}j
jjj RELEASED
TSU
- The operator commanded the system to release the
indicated job explicitly and the job was released for further
processing.
System Action: Processing continues.
Operator Response: None.
nnn HOLD sid - The operator entered a $DQ command. This
response indicates that there afe nnn jobs held in the
system. (Both active and queued jobs will be included.)
nnn PPU rrr ANY - The operator entered a $DQ command.
This response indicates that there are nnn jobs awaiting
print/punch processing with normal print or punch routing
indicated by rrr.
nnn OUT sid - The operator entered a $DQ command. This
response indicates that there are nnn jobs awaiting output
processing.
System Action: Processing continues.
Operator Response: None.
nnn OUT r - The operator entered a $DQ command. This
response indicates that there are nnn jobs awaiting output
with normal print or punch routing indicated by r.
System Action: Processing continues.
Operator Response: None.
nnn PERCENT SPOOL UTILIZATION - The operator entered
a $DQ or $DN command. This response is the last response
of those commands and should be used to gauge the
quantity of work the output devices have backlogged. A high
percentage of utilization normally indicates that the output
devices are behind and more devices should be made active
to decrease the backlog. If large numbers of jobs or data
sets are awaiting output, every effort should be made to
output that work. Large percentages of utilization tend to
increase overhead in handling SYSIN/SYSOUT data. 100%
utilization will cause execution and input of jobs to stop and
generally undesirable results will follow.
System Action: Processing continues.
Operator Response: If the utilization appears high as a
general rule, inform the installation management so that
appropriate action can be taken. Such action would depend
on the reasons for high utilization. If the percentage
approaches 100%, stop all readers and initiators, make
sure that all available output devices are busy (route output
to idle devices when possible), and inform time sharing
users to output or delete their data sets.
[HOLD]}
class
STC
sid
TSU
- The operator entered a $DQ command. This response
indicates that there are nnn jobs awaiting execution with
execution class (class) in the rang A-Z or 0-9. If the class
is an asterisk, the job(s) are waiting conversion. If HOLD
appears in the message text, the execution class is being
held by the $HQ command. If STC or TSU appears, the
class is the system task or time-sharing user class.
System Action: Processing continues.
Operator Response: None.
nnn XEQ
{
VS2.03.803
'It'i
1
~~:~i~:S~~S d7s~~:::~ :c~~nin~O;::::~~h~e~::~a~:: entered
a $00 command and JES2 found an outstanding action
request. JES2 requests are normally requests to load forms,
carriage tapes, and UCS trains on output devices.
System Action: Processing continues.
Operator Response: Perform the action as indicated or
cause the system to abort the function. In the case of setup
of devices the operator may override the request by one of
the following techniques:
• Misinform the system by issuing a $S command. JES2
will assume the setup as requested and output on the
forms, carriage control tape (or image), and UCS image.
• Enter $H j and $E device commands. JES2 will requeue
the output, hold it for later, and select other work for
output. This technique is extremely useful when the
deivce is a remote workstation that has been left
unattended and the central operator desires to free up
resources in the system.
text INVALID COMMAND - The command has been
identified as a JES2 command; however, the command has
been rejected for one of the following reasons:
• The verb was not recognized as a JES2 command verb.
• The first character of the first operand was not
recognized to be a legal qualifier of the verb.
• The entry source was not authorized to enter the
command.
• The operator directed that the response to this command
be displayed on a supported console and area, but that
console or area was not currently available to JES2. The
system will attempt to display this response in the normal
message area of the requested console.
System Action: The command is ignored and processing
~I\ continues.
/ Operator Response: Check the Operator's Reference Manual
for legal verbs, formats, and authority required and reenter
the desired command from an authorized console. Reenter
the command correctly.
text INVALID OPERAND - The. operand starting with the first
text character displayed was not recognized as a valid
operand for one of the following reasons:
• The operand was not recognized.
• The operand was recognized but the entry source was
not authorized to enter the operand.
• An identification range was invalid.
System Action: Normally, if one operand is invalid, no
action is taken. However, commands that perform actions
sequentially as operands are validated, will terminate action
upon encountering the invalid operand or character, leaving
the action partially complete. These commands are: $AQ,
$HQ, $C ddd, $E ddd, $F ddd, $1 ddd, $N ddd, $P ddd, $S
ddd, $T ddd, $TM, $DU and $VS.
Operator Response: Check the Operator's Reference Manual
for legal verbs, formats, and authority required and reenter
the desired command from an authorized console. Reenter
the command correctly.
text INVALID SPECIFICATION - The operator entered a $TA
command with an invalid operand specification. The
automatic command being created or altered (if any) will be
displayed and deleted.
System Action: If the first operand is incorrect, no action is
taken. If an operand following the first is incorrect, the
automatic command element will be deleted and a response
displaying the contents of the element before deletion will
follow.
Operator Response: Check the Operator's Reference Manual
for legal verbs, formats, and authority required and reenter
the desired command from an authorized console. Reenter
the command correctly.
NO DATA SET(S) CANCELLED - The operator entered a
$PQ command, but no data sets were found that could be
canceled.
System Action: Processing continues.
Operator Response: Verify that the proper operands were
used with the $PQ command or that the output that is to be
canceled does exist ($L).
DATA SETS
CANCELLED } {LOCAL }
{
RELEASED TO RnTnnn
- The operator ented a $OQ command to either cancel or
release held output in the system. If the data sets are
released to a destination other than the default routing
associated with that data set, then the new routing is
displayed.
System Action: Processing continues.
Operator Response: None
NO HELD DATA SETS - The operator has entered a $OQ
command to either cancel or release held output in the
system. However, there is no held output meeting the
criteria of the command.
System Action: Processing continues.
Operator Response: None
NO STORAGE AVAILABLE - The operator has entered an
$OQ or $0 command but no storage is available to service
the request. The request is ignored.
System Action: Processing continues.
Operator Response: Notify the system programmer that this
condition has occurred.
{;~~}jjjj
jobname DATA SETS CANCELLED
TSU
- The operator has entered a $P command with the Q
operand. The ready data sets of the specified class that
belong to the designated job have been canceled.
System Action: Processing continues.
Operator Response: None
{ ~~~}jjjj
jobname NO DATA SETS CANCELLED
TSU
- The operator has entered a $P command with the Q
operand for the designated job, but no ready data sets of
the desired class were found.
System Action: Processing continues.
Operator Presponse: Check the class(es) of ready data sets
for the designated job with the $L command and reenter
the $P command for the desired class(es).
{ ;~~}
jjjj jobname NOT EXECUTING ON sid
TSU
-The operator has entered the $E command for the
designated job. However, the job, although in execution, is
not executing on the system from which the $E command
was entered.
System Action: Processing continues.
Operator Response: Reenter the $E command on a console
attached to system on which the designated job is
executing.
Section 1: $HASP Messages - JES2
1-7
•
VS2.03.803
devicename NOT ACTIVE ON sid - The operator has
entered a $B, $C, $E, $F; $1, $N, or $Z device command,
but the specified device is not actively processing a unit of
work on the indicated system.
System Action: Processing continues.
Operator Response: None
TASK BUSY RE-STARTING sid - The operator has entered a
$ESYS command, but the system is currently busy restarting
the designated system.
System Action: Processing continues.
Operator Response: Using the $LSYS command, determine
when the system is available to restart another system and
reenter the $ESYS command.
AC.TIVE
}
INDEPENDENT MODE
RE-STARTING
INACTIVE
.
- The operator has entered a $ LSYS command.
INDEPENDENT MODE will only be displayed if the system in
independent mode is the one to which the entering console
is attached.
System Action: Processing continues.
Operator Response: None
sid
{
sid IS ACTIVE AND CANNOT BE RE-STARTED - The
operator has entered a $ESYS command for the designated
system (sid), but that system is currently active.
System Action: Processing continues.
Operator Response: None
NO JOB(S) RE-ROUTED - The operator has entered a
$TALL command, but no jobs were found whose system
affinity could be changed as specified.
System Action: Processing continues.
Operator Response: None
sid IS NO LONGER IN INDEPENDENT MODE - The operator
has used the $TSYS command to remove his system from
independent mode.
System Action: Processing continues and the system is now
available to accept all work that is routed to it.
Operator Response: None
sid IS NOW IN INDEPENDENT MODE - The operator has
used the $TSYS command to place his system in
independent mode.
System Action: The system will only begin new jobs that
are both routed to it and are designated to execute in
independent mode.'
Operator Response: None
NO JOB(S) FOUND - The operator has entered a $OQ,
$TALL, or $R command, but there were no jobs in the
system upon which the specified action could be taken.
System Action: Processing continues.
Operator Response: None
INVALID OPERAND(S) DETECTED - The operator entered a
$DU command in which one or more operands were found
to be invalid. Displays requested by any valid operands
have been displayed.
System Action: Processing continues.
Operator Response: Reenter the command with the correct
operands.
RESPONSE LOCATION L == eca UNAVAILABLE [ident] - The
operator entered a command. directing the response to a
console area (L == cca) that was not available to JES2. If the
console itself is not available, this message appears on the
master console. The comand entered will be displayed
immediately preceding this message. If the command
1-8
VS2 System Messages (VS2.03.803)
causing this message is an automtic command, the identifier
of the automatic command is displayed.
System Action: Processing continues.
Operator Response: Check the condition of the consoles
and reenter the command if desired or required.
$HASPOO 1
r, text
Explanation: The operator at a central console (r - 0) or at a
remote terminal identified by the value r has entered the
displayed message, via the $DM (display message) command.
(The importance level is 7.)
System Action: Processing continues.
Operator Response: Perform the appropriate action in
accordance with installation procedures.
$HASP002
AUTOMATIC COMMANDS HALTED
Explanation: The operator has commanded the system to
automatically issue commands via the $TA command. The
system has detected a potentially undesirable situation as
follows:
1. The time and date are inconsistant with a previously
recorded time and date. This results from leaving the
automatic command feature halted for greater than 24
hours or altering the time and date greater than 24 hours
forward or backing the date up to a previous day. Lowering
the time is considered consistant but will s~op interval
displays until the time reaches the previously set value.
2. The system was congested with activity, preventing
automatic issuance of. commands for an extended period of
time.
(The importance level is 7.)
System Action: The system performs a $ZA command action
and records the new time so that a $SA command will allow
continuation of automatic command processing.
Operator Response: Display the automatic command queue
using the $TA command to determine if. time values should be
altered or entries should be deleted. Because the $TA
command only displays elements consistant with the operator
console authority, a fully authorized console shOUld be used for
queue examination.
.
$HASP092
API ERROR ON LOGONI ACB rrrr,VTAM,ssss
Explanation: The interface between VTAM and JES2 has failed.
rrrr indicates the VTAM service that was requested; the first
two characters of ssss indicate the setting of the ACBERFLG
field; and the last two characters i.ndicate the return code in
register 15 after the ACB request.
System Action: The ACB is closed, and the connection
between VTAM and JES2 is terminated.
Operator Response; Check to see if VTAM has been started,
and then try to log on again. If the attempt to logon fails,
contact the system programmer.
Programmer Response: Refer to VTAM Macro Language
Reference, GC27 -6995, for an explanation of the ACBERFLG .
setting and return code, and correct the problem.
$HASP093
nnn % .SPOOL UTILIZATION
Explanation: JES2 has detected the space used to store SYSIN
and SYSOUT data on the SPOOL data sets has reached an
excessive amount. (The importance level is 7.)
System Action: Processing continues.
Operator Response:. Increase the rate of job output by starting
more JES2 output devices, routing data sets to available
devices, and releasing HELD jobs and data sets. Reduce the
input rate by draining reader devices and stopping initiators.
(
\
VS2.03.803
)
Report the occurence of frequently high spool utilization to the
system programmer.
.
Programmer Response: If frequent high utilization is
experienced, provide larger data sets for JES2 spooling. Take
steps to reduce the amount of output backlog.
Note: Reaching 100% spool utilization is considered a serious
operational problem and generally undesirable conditions will
result. This may include forced canceling of job output and
consequently loss of data.
$HASP094
I/O ERROR ON ser ddd,cde,stat,sens,bbcchhr
Explanation: An input! output error has occurred on the
indicated JES2 device where:
ser = JES2 device name, or volume serial if direct access
ddd = hardware address
cde = CCW op code used at the time of error
stat = CSW status code
sens = sense information
bb
= bin, as appropriate
cc
= cylinder, as appropriate
hh
= head, as appropriate
= record, as appropriate
r
Associated error messages may be displayed as a result of the
error. For direct access,· the following could be causes of the
error:
1. The channel, control unit, or device is malfunctioning. This
may be determined by moving the volume (if moveable) to
a new drive, control unit, or channel and by restarting JES2.
2. The recording surface is bad, possibly indicated by the
nature and the distribution of the bbcchhr information. (A
reinitialization with assignment of alternate tracks, followed
by a JES2 format start, may be desirable.)
~3. The data set SYS1.HASPACE may have been overwritten by
~
improper data set assignment and protection procedures.
This may be indicated by wrong length record indicators. (A
JES2 format start is required.)
(The importance level is 7.)
System Action: JES2 continues job processing and submits
additional error messages, indicating the severity of the error
to the system.
Operator Response: Determine the cause of the error, and
take appropriate action.
$HASP094
I/O ERROR ON LlNElna adr,cde,stat,sensrr,xyee
Explanation: An error has been detected on the indicated JES2
RJE line, or on a device attached to that line, where:
Ina
= JES2 RJE line number
adr = line adapter address
cde = CCW op code used at the time of error
stat = CSW status code if no block sequence check
= 0000 - indicator for normal channel end, with a
block sequence check at the central CPU
= FFFF -
indicator for normal channel end, with a
block sequence check at the remote site
sens = sense information, if stat = OEOO
= last character received, if stat = OCOO and xy == 94
or B4
rr
= remote device first response character
= JES2 CCW internal sequence identification
x
y
= JES2 CCS internal sequence command type
ee
= expected response
Notes:
1. This message may also occur as an informational message
when maintenance personnel have set JES2 internal flags to
log all channel ends of the line device.
2. The appropriate IBM component description manual (System
Reference Library) describes the status and sense
information in detail.
(The importance level is 7.)
System Action: JES2 will, for most line errors, attempt to
recover and continue processing, using the line.
Operator Response: The console log should be saved for
maintenance personnel (even if recovery is successful).
Additional responses depend on the nature of the problem.
$HASP094
I/O ERROR ON LlNElna adr,02,OOOO,OOrr,
{::} ee
Explanation: A block sequence error has been detected by
JES2, while communicating with a MULTI-LEAVING terminal.
This indicates that one or more transmission blocks have been
lost. rr indicates the count received, and ee indicates the
count expected. (The importance level is 7.)
System Action: Any job reading in is deleted and must be
resubmitted.
Operator Repsonse: This represents a very serious error.
Control records may have been lost, which could cause partial
loss of terminal function. The line should be drained ($P) and
restarted ($S) as soon as practical.
$HASP094
I/O ERROR ON LlNElna adr,02,OCOO,0001,
{::}
U
Explanation: A 2770, 2780, or 3780 terminal has
disconnected without signing off, and a MULTI-LEAVING
terminal has subsequently connected to the same line and is
attempting to sign on. (The importance level is 7.)
System Action: The previous terminal is signed off, and the
line is disconnected.
Operator Response: The remote terminal operator must redial
and attempt to sign on again.
Section 1: $HASP Messages - JES2
1-9
•
VS2.03.803
$HASP094
I/O ERROR ON LlNElna adr,02,OCOO,OOlD,
{m ..
Explanation: A NAK has been received from the remote
terminal, indicating an error was detected at the terminal. (The
importance level is 7.)
System Action: Normal error recovery procedures are invoked.
Operator Response: None.
$HASP094
I/O ERROR ON LlNElna adr,02,OCOO,0061,
I/O ERROR ON LlNElna adr,cde,sens,ii**,****
~
Explanation: A unit check on the communications adapter has
been detected by JES2~ for more detailed information
concerning the exact nature of the error, IBM 2701 Data
Adapter Unit Component Description (GA22-6864) and/or the
System/360 Component Description - 2703 Transmission
Control (GA27 -2703) should be consulted. (The importance
level is 7.)
System Action: Processing continues.
Operator Response: None.
$HASP094
$HASP094
{::} ee
{::} 70
$HASP094
I/O ERROR ON LlNElna adr,02,OCOO,0070,
{::} 61
Explanation: JES2 has received an incorrect acknowledgment
from a 2770, 2780, or 3780 terminal. This may indicate that
an output device (printer or punch) at the remote terminal has
become not ready. It may also indicate that an output block
has been lost. (The importance level is 7.)
System Action: The last block is retransmitted.
Operator Response: The remote terminal operator should
check (to any extent possible) for missing or duplicate output
and should request a backspace or restart, if the output looks
fluestionable.
$HASP094
I/O ERROR ON LlNElna adr,02,OCOO,OOrr,84 **
Explanation: Invalid data has been received from a 2770,
2780, or 3780. 'rr' indicates the first significant byte received.
(The importance level is 7.)
System Action: Normal error recovery procedures are invoked.
Operator Response: None.
$HASP094
{~~},
{:!}
**
$HASP094
I/O ERROR ON LlNElna adr,02,ODOO,OOl7,84**
Explanation: The card reader on a 2770, 2780, or 3780 has
become not ready. This may be caused by a card feed error or
by the failure of the remote operator to activate the
END-Of-fiLE switch or button. (The importance level is 7.)
System Action: The system waits for the reader to be made
ready and transmission to continue.
Operator Response: The remote terminal operator should
correct the problem and ready the card reader (ensuring that
the END-Of-fiLE switch or button is activated).
I/O ERROR ON LlNElna adr,02,ODOO,OOl7,
{E}··
Explanation: JES2 has received an unexpected EOT. (The
importance level is 7.)
System Action: Normal error recovery procedures are invoked.
Operator Response: None.
1-10
Explanation: A block sequence error has been detected by a
MULTI-LEAVING terminal, indicating that one or more
transmission blocks have been lost. (The importance level is
7.)
"rr" indicates the count that was received at the remote
terminal, and 'ee' indicates the count that was expected.
System Action: Any job printing on the terminal is interrupted,
and any job punching on the terminal is restarted.
Operator Response: This represents a very serious error.
Control records may have been lost, which could cause partial
loss of terminal function. The line should be drained ($P) and
restarted ($S) as soon as practical.
$HASP094
I/O ERROR ON LlNElna adr,cde,sens,ii**, 111***
Explanation: An unusual channel end condition on the
communications adapter has been detected by JES2. for more
detailed information concerning the exact nature of the error,
the appropriate hardware component description manuals
should be consulted. (The importance level is 7.)
System Action: The line is automatically restarted.
Operator Response: None.
I/O ERROR ON LlNElna adr,02,OCOO,ii
Explanation: An invalid termination character was received
from a MULTI-LEAVING terminal. 'ii' indicates the termination
character received. (The importance level is 7.)
System Action: Normal error recovery procedures are invoked.
Operator Response: None.
$HAS~4
I/O ERROR ON LlNElna adr,02,ffff,OOrr,
YS2 System Menage. (YS2.0l.80l)
$HASP094
I/O ERROR ON LlNExxx SNA,qq,rrff,ssss
Explanation: A VTAM RPL request has failed because an I/O
error has occurred on the indicated SNA line. The message
includes:
SNA the type of device
qq the RPL request made (RPLREQ)
rr
the return code (RPLRTNCD)
ff
the feedback field setting (RPLfLDB2)
ssss the SNA sense information (RPLSSNSI)
System Action: Normal recovery procedures are invoked.
Programmer Response: Refer to VTAM Macro Language
Reference, GC27 -6995, for an explanation of the return code,
feedback field setting, and sense information, and correct the
problem.
$HASP095
HASP SYSTEM CATASTROPHIC ERROR.
CODE- cde
Explanation: cde is one of the codes described as follows:
cde
Explanation
A01
JES2 detected more channel end indications for a
device than expected. Only one channel end indication
should be received from lOS for each input! output
operation that JES2 has initiated.
B01
An attempt has been made to return an invalid JES2
buffer to the buffer pool.
B02
The available buffer count for a buffer pool is
non-zero, but no buffer is indicated as available.
E01
The total number of channel end indications from lOS
has exceeded the total number of input! output
operations initiated by JES2. for example, the total
VS2.03.BU3
number of outstanding input/output operations
became negative.
K01
Invalid alteration of checkpoint record contents when
not under control of $QSUSE macro.
K02
Checkpoint records read permanent error.
K03
Two systems using same system identifier, or failure
of shared OASO reserve/release.
K04
Checkpoint records write permanent error.
K05
Checkpoint record has been changed, but not flagged
for checkpoint.
MOl
JES2 has detected more channel end indications for
an RJE line than expected., Only one channel end
indication should be received from lOS for each
input/output operation, initiated by JES2.
M02
An attempt has been made to initiate an input/output
operation on an RJE line before the previous operation
has completed.
M03
An internal logic error has been detected by RTAM
during processing for an SNA remote work station.
R01
RTAM or VTAM has detected a logic error during RPL
processing. If VTAM detected the logic error, message
$HASP094 precedes this message and displays the
related RPL fields.
The purge processor has discovered that some track
VOl
groups to be freed were already free.
Q01
A JES2 processor requested a job queue service
routine function with invalid arguments or failed to
insure that the job queue checkpoint processor was
not active for a $QMOO service function.
Q02
A JES2 processor requested a job queue service and
specified an invalid job queue type.
ABNO The JES2 abnormal exit routine has been entered,
indicating that the JES2 system has been abnormally
terminated.
(The importance level is 7.)
System Action: Message $HASP098 is issued and the system
waits for the operator to respond.
Operator Response: Take a stand-alone dump, and notify the
system programmer.
~
~'
$HASP096
DISASTROUS ERROR - COLD START SYSTEM
ASAP
Explanation: Either a critical I/O error has occurred on the
SYSl.HASPACE data set or an internal logic error has been
detected in JES2. If a corresponding I/O error message
accompanies this message, it will give details of the error.
(The importance level is 7.)
System Action: JES2 continues processing jobs using
unaffected facilities.
Operator Response: If the error appears to be associated with
an I/O error, prevent new jobs from entering the system,
prepare all jobs in the JES2 execution queue for resubmission
(when JES2 is restarted), allow JES2 to complete all current
jobs in execution and all output activity (depleting the output
queues), and stop JES2.
If the message is issued as a result of an internal JES2 logic
error, take a stand-alone dump and notify the system
programmer.
Operator Response: Enter a $S device command when JES2 is
to continue using the device.
$HASP098
ENTER TERMINATION OPTION
Explanation: The JES2 task has recognized a catastrophic
error condition described by message $HASP095. (The
importarice level is 7.)
System Action: The system waits for the operator to reply.
Operator Response: Enter the appropriate response. If you
reply EXIT, JES2 will exit without any attempt to clean up. If
you reply PURG, JES2 will attempt to terminate any attached
tasks, inform tasks waiting on a JES2 function of the failure,
and exit.
If you enter "DUMP text", JES2 will attempt to cause a dump
to the system dump data set of its address space, followed by
the cleanup described for PURG.
Note: The JES2 main task reserve register 13 points to a
16-word register save area. The save area contains the
contents of the registers upon entry to the JES2 error exit
routine. In the case of code ABND, these registers in
accordance with the operating system ESTAE exit routines
interface described in the OS /VS2 Supervisor Services and
Macro Instructions, GC28-0683.
Problem Determination: Table I, items 2, 9, 13, IS, 16, 17,
20, ~1, 22, 27, 29, 33.
'
$HASP099
ALL AVAILABLE FUNCTIONS COMPLETE
Explanation: All JES2 job processors have become dormant,
and no JES2 RJE lines are active. (The importance level is 7.)
System Action: Processing continues and JES2 waits for work.
Operator Response: Enter more jobs into the system or enter a
command that will allow job processing such as:
• $S if a $P has been previously entered and processing is to
be continued.
• $SI if initiators are drained or halted.
• $S devname if devices are drained, halted, or paused.
• $AQ, $AA, or $A j if queues or jobs are held.
• $TI if initiators are not set to select available jobs in the
execution queues.
• $T devname if output devices are not set to select available
output.
• $R ij output is routed to devices that are not currently
operational and should be output to alternate devices.
• $0 if output is held and should be released.
$HASPI00
Jjj ON devname programmer
Explanation: A JOB card has been detected in the input
stream from the indicated device, and the associated job has
been assigned a JES2 job number. The programmer name
displayed is the programmer name from the JOB card. (The
importance level is 5.)
System Action: The previous job in the same input stream (if
any) is queued for execution processing, and input service
processing is initiated for the new job.
Operator Response: None.
$HASPI0l
iii HELD
Explanation: The indicated job has been placed in JES2 HOLD
$HASP097
devname IS DRAINED
Explanation: The operator has entered a $P device command,
~
,
I
directed to the named device, and the device has entered the
DRAINED status. (The importance level is 7.)
System Action: JES2 discontinues use of the deivce until a $S
device command is entered, specifying the device correctly.
JES2 unallocates the deivce, permitting it to be used by other
tasks within the system.
status for one of the following reasons:
• The JOB card specified "TYPRUN - HOLD".
• The JOB card specified "TYPRUN - JCLHOLO".
• The device from which the job was read was set to HOLD
all jobs.
• The class of the job has been set by JES2 initialization
parameters such that all jobs entered in that class will be
held.
Section 1: $HASP Messages - JES2
1-11
VS2.03.803
(The importance level is 3.)
System Action: Processing continues on other jobs.
Operator Response: The reason the job was placed in JES2
HOLD status should be determined, and the job should be
released, when appropriate, for further processing.
$HASPI02
jjj HELD FOR THE FOLLOWING VOLUMES
Explanation: The indicated job has been placed in HOLD status
by the JES2 input service because a /*SETUP control card
was encountered. The text of the control card is displayed with
accompanying $HASPI03 messages. (The importance level is
5.)
System Action: Processing continues, holding the job on the
execution queue,
Operator Response: Ensure that the ,requested volumes are
available to be mounted, and release the job.
$HASPI03
jjj ser, ... ,ser
Explanation: The indicated job has been placed in HOLD status
by the JES2 input service pending availability of the volumes
indicated by ser, ... ,ser. (The importance level is 5.)
System Action: The job is placed in JES2 HOLD status, and
input processing continues.
Operator Response: Ensure that the requested volumes are
available to be mounted and release the job.
$HASPI04 {~~vname}text
JJJ
Explanation: The input service processor has detected a
j*MESSAGE control card in the input stream. (The importance
level is 5.)
System Action: Processing continues.
Operator Response: Observe the message indicated by text
and take any appropriate action.
$HASPllO
jjj -- ILLEGAL JOB CARD
Explanation: The JOB card for the indicated job was found by
the input service processor to be invalid. (The importance level
is 1.)
System Action: Input service processing is terminated for this
job.
Programmer Response: Correct the JOB card, and resubmit
the job. A different value for & RJOBOPT could be specified to
allow the illegal JOB card to be ignored. Illegal and invalid
cards are detailed in the JCL Manual under Coding JES2
Control Statements.
$HASPlll
jjj -- INVALID j*ROUTE CARD
Explanation: The input service processor has encountered an
invalid j*ROUTE control card. (The importance level is 1.)
System Action: Input service processing for the job is
invalid j*OUTPUT control card. (The importance level is 1.)
System Action: Input service processing for the job is
terminated.
Operator Response: Report this message to the system
programmer.
Programmer Response: Refer to the JCL Manual for correct
forms of the j*OUTPUT card, correct and rerun the job.
$HASPI19
jjj DELETED
Explanation: The input service prosessor has deleted the
indicated job. The cause for the deletion may be that the
operator entered a command to cause the deletion, or an error
may have been encountered while inputting the job. When
input errors are encountered, a previously displayed message
details the nature of the error. (The importance level is 1.)
System Action: The job is routed to the print phase for
appropriate action; then, the job is purged.
Operator Response: Report this message to the system
programmer.
Programmer Response: Correct the problem as appropriate
and resubmit the job.
$HASPI20
devname cm
Explanation: The displayed command has been entered from
the d.evice indicated. (The import:ance level is 3.)
System Action: The command is passed to the JES2 command
processor for the further action.
Operator Response: None.
$HASPI25
devname SKIPPING FOR JOB CARD
Explanation: The JES2 input service processor is scanning the
input stream for a JOB card. This message may be
accompanied by diagnostic messages indicating that errors
have been encountered in the reading of jobs. (The importance
level is 3.)
System Action: The input service processor continues to read
the input §tream until a JOB card is encountered or until an
end-of-data condition is recognized.
Operator Response: If you entered a command to delete a job
currently on the device, perform appropriate action consistent
with the reason for deletion. If skipping is caused by the
deletion of a job because of an error encountered, inform the
prcgrammer of the error. Otherwise, check the input stream to
make sure that the cards are in correct order and resubmit the
corrected jobs after canceling any that were incorrectly
entered.
Programmer Response: Correct the JCL in accordance with the
accompanying error messages.
$HASPI50
jjj ON devname
Explanation: The indicated job is now being processed by the
Programmer Response: Refer to the JCL Manual for correct
forms of the j*ROUTE card, correct and rerun the job.
print or punch device. (The importance level is 1.)
System Action: The indicated job is output.
Operator Response: None.
$HASP1l2
$HASPI55
terminated.
II
jjj -- INVALID j*JOBPARM CARD
Explanation: The input service processor has encountered an
invalid j* JOBPARM control card. (The importance level is 1.)
System Action: Input service processing for the job is
terminated.
Programmer Response: Refer to the JCL Manual for correct
forms of the j* JOBPARM card, correct and rerun the job.
$HASP1l3
jjj -- INVALID j*OUTPUT CARD
Explanation: The input service processor has encountered an
1-12
VS2 System Messages (VS2.03.803)
jj devname MAX OF n WCGM'S EXCEEDED
Explanation: For job jjj on the specified 3800 printer, the user
has specified character arrangement tables that fill up more
WCGMs (writable character generation modules) than the
installation has available. An installation can have up to four
WCGMs.
System Action: Processing of the indicated job is halted.
Operator Response: Notify the user of the problem. At the first
opportunity, use the set ($T) command to override the user's
character arrangement table specification. (One way to correct
this error with the $T command is to set all the character
VS2.03.803
arrangement tables to the same value; for example,
Xl = GFlO,X2 == GFlO, and so on.)
$HASP160
devname INACTIVE - CLASS ... class class ... class
Explanation: The indicated device found no work in the
queue(s) specified by class class ... class. (The importance level
is 1.)
System Action: The specified device remains INACTIVE until
work becomes available.
Operator Response: If the device is in operator-controlled
mode, the operator may use the set ($T) command to:
• Alter setup to match work in the listed classes.
• Alter the current class list.
• Switch to automatic mode.
If the device is in automatic mode, the set ($T) command may
be used to alter the class list.
$HASP165 JOB NNNNN jjj
[xxx yyy]
!
ENDED.
ENDED-JCL
ERROR
ENDED-CANCELLED
ENDED-ABENDED
ENDED-cc = dddd
I
Explanation: ENDED-job jjj number nnnnn has terminated.
ENDED-JCL ERROR - job jjj number nnnnn has terminated.
The converter/interpreter or initiator phase of the job
processing could not be completed due to an error in the job
control language.
ENDED-CANCELLED - job jjj number nnnnn was cancelled by
the operator.
ENDED-ABENDED - job jjj number nnnnn has terminated
abnormally.
[xxx yyy] ENDED-cc = dddd - job jjj number nnnnn was
terminated by a condition test specified in the COND
parameter of the job statement being satisfied by the
completion code dddd of the executing step xxx. If stepxxx is a
step of a. cataloged procedure then yyy will be the step that
called step xxx.
System Action: The job enters the output phase and
processing continues. This message is displayed to the TSO
user via a TSO SEND verb if the parap1eter NOTIFY = tsu id, is
detected on the / / JOB card.
Programmer Response: In the case of a ENDED-JCL ERROR
message, check system output for the actual error message.
Correct the indicated error and resubmit. In the case of a
END-ABENDED message, check system output for abend code.
$HASP170
devname
I:~~f£:::l
REPEATED
RESTARTED
SUSPENDED
Explanation: Output processing on the indicated device has
been backspaced, deleted, forward-spaced, repeated,
restarted, or suspended. (The importance level is 3.)
System Action: The system action depends on the specified
function:
• FWD-SPACED - The requested number of pages or cards is
skipped without printing or punching, and processing
continues. If the end of the data set is encountered while
skipping, processing continues with the beginning of the
next data set.
• DELETED - The job being processed on the indicated device
is queued for the next processing phase. Output processing
is terminated.
• BACKSPACED - The requested number of pages or cards is
backspaced, and processing continues. If the beginning of
the data set is encountered while backspacing, processing
continues at the beginning of the data set.
• REPEATED - The job being processed on the indicated
device is requeued. Output processing is continued.
• RESTARTED - The job being processed on the indicated
device is requeued. Output processing for the job is
terminated.
• SUSPENDED - The job being processed on the indicated
device is requeued, so that when it is processed again,
processing will begin one page or card group before the
current point or at the beginning of the data set (whichever
is less). Output processing is terminated.
Operator Response: None.
$HASP175
•
devname PAUSED
Explanation: Output processing on the indicated device is
stopped at an end-of-job boundary. (The importance level is
3.)
System Action: Processing continues and the indicated device
is unavailable.
Operator Response: After removing the processed output, the
operator can cause the device to continue its function by
either depressing first the STOP then the START key on the
device or by typing a $S device command on the system
console. To prevent future device pauses, type in $T
devname,P == NO.
UNKN
CHAR
MODFY
GRAPH
$HASP180 jjj devname FLASH
WCGM
FCB
UCSB
NOT FOUND}
IMAGE xxx I/O ERROR
{
LOAD ERROR
Explanation: The indicated job has requested that image xxx
be loaded into the print device character arrangement table
(CHAR), copy modification module (MODFY), graphic character
modification module (GRAPH), forms overlay frame (FLASH),
writable character generation module (WCGM), FCB, or UCSB.
A search of all images has shown that that specifiedJmage
does not exist in SYSl.IMAGELlB; an I/O error occurred during
an attempt to read from SYSl.IMAGELlB; or a load error
occurred during an attempt to load the image into the printer.
System Action: Processing of the indicated job is halted, and
if the error occurred while processing a forms overlay
(FLASH), the device setup message is issued.
Operator Response: Issue the $DU command to see the
current status. Then use the $T command to correct the
indicated error.
$HASP185
devname TERMINATED
Explanation: Processing of the current data set was abnormally
terminated. (The importance level is 15.)
System Action: Possible causes of this termination are:
1. An I/O error occurred on the SPOOL volume while reading
a control block or a data buffer.
2. While attempting to read the next block of data for this c:iata
set, a block of data not belonging to this job was
encountered.
Note: This message is the expected response when a job
which was in execution during a s,stem failure is printed after
warm start, without being rerun.
Operator Response: Rerun the job.
Section 1: $HASP Messages - JES2
1-13
1
•
VS2.03.803
$HASP190
iii.SETUP - ddd - F - ffff [-C - cccc - T -
ttttJ
Explanation: The indicated job requiris that the setup of the
punch device indicated by ddd be altered to forms - ffff, or
that the printer device indicated by ddd be altered to forms
= ffff, carriage control = cccc, and print train = 'tttt. (The
importance level is 8.)
System Action: Output processing is haltedon the specified
device until an appropriate operator response is received.
Operator Response: Verify that the requested setup has been
completed and enter a start ($5) command for the indicated
device. If you wish to override any or all of the setup
specifications, do so with the set ($T) command followed by a
start ($S) command. Current activity may be suspended by the
restart ($E), interrupt ($1), and cancel ($C) commands. In this
event, all intervening set ($T) commands will be ignored and
the device setup will be that prior to the setup message.
$HASP190 jjj SETUP--PRINTERnn--F
B=
{~}
= fffl--O = name--
Explanation: The indicated job Ojj) requires that the setup of
the 3800 printer device indicated by PRINTERnn be altered to
forms = ffff, forms overlay = name, and burst mode or no
burst mode.
System Action: Output processing is halted on the specified
device until an appropriate operator response is received.
Note: For burst mode, if the burster is not threaded,cthis
message is repeated.
Operator Response: Verity that the requested setup has been
completed and enter a start ($5) command for the indicated
3800 printer device. If you wish to override any or all of the
setup specifications, do so with the set ($T) command
followed by a start ($S) command. Current activity. may be
suspended by the restart ($E), interrupt ($1), and cancel ($C)
commands. In this event, all intervening set commands are
ignored, and the device setup is that prior to the setup
message.
Operator Response: The remote operator should determine the
valid password and correct the sign-on to reflect this
information.
$HASP202
LlNElna - INVALID SIGN ON
Explanation: A remote attempted to sign on the specified line
with an invalid sign-on card. A sign-on card may be invalid if:
1. The remote name is spelled incorrectly.
2. The remote specified has not been generated.
3. The remote specified is attached to another line.
4. The remote name does not begin in column 16.
(The importance level is 3.)
System Action: The attempted sign-on is not allowed, and the
line is left in an INACTIVE status.
Operator Response: The remote operator should verify the
spelling of the remote. If the remote is attached to another
line, steps should be taken to correct this conflict in remote
assignmen·ts'.
$HASP203
RMTxxx DISCONNECTED
Explanation: A remote workstation that was previously signed
on has been signed off. (The importance level is 3.)
System Action: If the line is still active, JES2 prepares for a
new remote workstation to sign on; otherwise, the line will go
into DRAINED status.
Operator Response: None.
$HASP204
RMTxxx--LOGON FAILED--SESSION zzzzzzzz
Explanation: The SNA remote workstation xxx attempted to log
on, but there was no line OCT for the station.
System Action: The attempted logon is not allowed, and the
remote station is not connected.
Operator Response: The network operator should start a
logical line so that the remote operator can log on.
$HASP205
LOGON1--INVALID LOGON--SESSION zzzzzzzz
Explanation: An SNA remote workstation attempted to log on,
$HASP195
PRINTERnn PAPER JAM--APPROX PAGES = xxxx
Explanation: A paper jam has been detected on the specified
3800 printer. xxxx indicates the approximate number of pages
the operator must backspace to recover the print data set.
System Action: Output processing on the specified 3800
printer is halted until an appropriate operator response is
received.
.
Operator Response: Count the number of physical pages in the
paper jam, and then issue the $8 command to backspace the
number of pages specified in the error message (xxxx) plus
the number of physical pages in the paper jam. To ensure
complete recovery of the output, however, you may wish to
increase slightly the number of pages you backspace.
$HASP200
RMTxxx STARTED ON LlNElna [SESSIONzzzzzzzz]
Explanation: A remote workstation has appropriately identified
itself to JES2. (The importance level is 3.) If RMTxxx is an
SNA remote workstation, the message indicates the session
the workstation is on (zzzzzzzz).
System Action: Job processing activity is initiated with the
remote workstation.
Operator Response: None.
$HASP201
LlNElna - INVALID PASSWORD
Explanation: A remote attempted to sign on the specified line
with an invalid password. (The importance level is 3.)
System Action: The attempted sign-on is not allowed, and the
line is left in an INACTIVE status.
1-14
VS2 System Messages (V52.03.803)
but failed for one of the following reasons:
• The remote station was already logged on.
• The logon contained an invalidRMT number.
• The logon contained an invalid remote password.
• The logon contained an invalid line password.
• The syntax of the logon data was invalid.
System Action: The attempted logon is not allowed, and the
remote station is not connected.
Operator Response: If the logon was invalid, correct it and try
to log on again.
$HASP249
devname cm
Explanation: The displayed command has been entered from
the device indicated. (The importance level is 3.)
System Action: The command is passed to the command
processor for further action.
Operator Response: None.
$HASP250
Hi
IS PURGED
Explanation: JE52 has completely finished processing the
designated job, and all JES2 facilities belonging to the job are
made available for reuse. (The importance level is 1.)
System Action: JES2 resources associated with job jjj are
freed.
Operator Response: None.
VS2.03.803
',$HASP260
JES2 CONTROL LOCKOUT - RESET CRASHED
SYSTEM
Operator Response: It may be possible, by specifying SHR and
not using JCL procedures, to correct the problem with the
specified procedure library, without stopping the system .
Explanation: An attempt to read the checkpoint records from
SYSl.HASPCKPT did not complete in the time specified during
JES2 initialization. (The importance level is 7.)
System Action: System continues to wait for read-completion
and starts a new warning interval.
Operator Response: Operator should investigate other systems
sharing the SYSl.HASPCKPT data set for possible system
failure and, if necessary, press SYSTEM RESET. The message
repeats until a failing system is restarted or until a transient
queueing lockout is resolved.
Programmer Response: Review the setting of the & WARNTIM
initialization parameter.
library could not be opened. (The importance level is 15.)
System Action: If the specified procedure library is other than
PROCOO, then an attempt is made to use PROCOO. If PROCOO
cannot be opened, an attempt is made to process the JCL
without using a procedure library.
Operator Response: A DO card for the specified procedure
library may not exist in the procedure used to start the
sub-system.
$HASP301
$HASP308
jjj - DUPLICATE JOBNAME - JOB DELAYED
Explanation: The specified job was delayed for execution,
because a job of the same name was already executing. (The
importance level is 3.)
System Action: The indicated job will be executed when the
job with the same name terminates execution.
Operator Response: None.
$HASP302
abnormally terminated. (The importance level is 15.)
System Action: The job being converted is routed to the print
phase for appropriate action; then the job is purged. The next
job to be converted will cause the sub-task to be re-attached.
Operator Response: Notify the system programmer of this
message.
~
[jji] RE-QUEUED AND HELD
Explanation: The specified job was re-queued for execution
and has been placed in JES2 HOLD status. The job was one
which terminated abnormally and which was re-startable. (The
.
importance level is 7.)
System Action: ProceSSing continues.
Operator Response: The reason the job was placed in JES2
HOLD status should be determined and the job should be
released, when appropriate, for further processing.
$HASP304
STORAGE EXCEEDED OUTPUT MAY BE LOST
Explanation: Sufficient main storage was unavailable to
transfer the information representing a data set to a print or
hold queue. (The importance level is 7.)
System Action: Depending on its prior status, the data set
mayor may not be lost.
Operator Response: A programming error probably exists in
the system which is causing storage to be obtained in
excessive amounts. This condition should be reported to an
IBM programming systems representative.
$HASP305
CONVERSION PROCESSOR AWAITING STORAGE
Explanation: Sufficient common storage was unavailable to
perform JCL conversion. (The importance level is 7.)
System Action: After waiting thirty seconds, the job is
re-submitted for JCL conversion.
Operator Response: If the condition persists, it should be
reported to an IBM programming systems representative.
$HASP306
UNABLE TO OPEN ddn
Explanation: During JCL conversion, the specified procedure
jjj ESTIMATED TIME EXCEEDED [BY mm
MINUTES]
Explanation: The indicated job has execeeded its estimated
real time in the JES2 execution phase by mm minutes. (The
importance level is 5.)
System Action: Processing continues.
Operator Response: Cancel the job if directed to do so by
installation operating procedures.
CONVERSION SUB-TASK ABENDED
Explanation: The JCL conversion sub-task, HOSCNVT, has
Y $HASP303
$HASP307
INVALID LRECL OR BLKSIZE ON ddn
~ Explanation: During JCL conversion, the specified procedure
library was found to have a logical record length other than
80, or a blocksize not an even multiple of 80. (The importance
level is 15.)
System Action: An attempt is made to process the JCL
without using a procedure library.
$HASP309
{
{******** }
c = classes
XB} INIT id INACTIVE.
fifi
monitor name
Explanation: JES2 logical initiator init is idle because the
execution processor discovered that np jobs of the classes
indicated were available in the JES2 job queue. (The
importance level is 5.)
System Action: The execution processor activates the logical
initiator when an appropriate job becomes available.
Operator Response: If the initaitor is not to be used for an
extended period of time, enter a $PI init command for that
initiator. Otherwise, enter a $TI command to allow continuation
of processing, or allow the initiator to remain inactive· as
desired.
$HASP310
jjj TERMINATED AT END OF MEMORY
Explanation: Job jjj terminated as a result of the abnormal
termination of the memory in which it was executing. (The
importance level is 7.)
System Action: Processing continues.
Operator Response: None.
$HASP311
jjj RE-ENQUEUED AT END OF MEMORY
Explanation: Job jjj has been re-enqueued for warm start
processing as a result of the abnormal termination of the
memory in which it was executing. (The importance level is 7.)
System Action: Processing continues.
Operator Response: None.
$HASP312
[subsystem] AWAITING SECONDARY
SUB-SYSTEM WITHDRAWAL
Explanation: The identified primary subsystem is attempting
normal withdrawal as directed by the operator via the $PJES2
command. It is unable to withdraw because other subsystems
are using ~he primary subsystem to run initiators. (The
importance level is 5.)
System Action: JES2 waits for secondary subsystems to
withdraw.
Operator Response: Attempt to clear the primary subsystem by
stopping all secondary initiators and started systems tasks. If
this fails, withdraw the secondary subsystems.
Section 1: $HASP Messages
~
JES2
1-15
•
VS2.03.803
$HASP313
iob Id SPIN/HOLD DATA SET LIMIT EXCEEDED
-OUTPUT LOST
Explanation: The identified job has created more than 255
SYSOUT data sets to be disassociated from normal output. In
the case of SPIN data sets, the JES2 output facilities have
been backed up to the extent the data set could not be
queued for output on the JES2 devices (or external writer).
(The importance level is 3.)
System Action: The system discards the data set.
Operator Response: None
$HASP314
INIT id DRAINED ........ c -= classes
Explanation: The operator has entered a $PI command apd the
initiator identified has subsequently entered the DRAINED
condition. (The importance level is 3.)
System Action: The initiator job associated with the identified
initiator will terminate execution and become eligible for
output.
Operator Response: Enter a $SI command to create a new
initiator to process jobs.
$HASP315
XB }
{. ••••••••
}
INIT Id HALTED
c - classes
{ f) f)
monitor name
Explanation: The operator. has entered a $ZI command and the
identified initiator has subsequently entered the HALTED
condition. (The importance level is 3.)
System Action: The initiator job associated with the identified
initiator remains in an indefinite wait state.
Operator Response: Enter a $SI command to resume
processing jobs with the initiator.
$HASP350
Jjj INIT STOPPED
Explanation: JES2 has caused' an initiator to stop. (The
importance level is 15.)
System Action: The initiator should stop normally. The initiator
is stopped due to an operator request or because the initiator
had been started to run an STC or TSU job and that job had a
JCL error, or because insufficient storage was available.
Operator Response: None.
$HASP352
jjj OPEN FAILED BECAUSE NOT SYSIN, SYSOUT,
NOR PROCESS-SYSOUT
Explanation: An OPEN macro instruction failed for a subsystem
data set because JES2 could not determine the data set's type
from the data set name in the JFCB. (The importance level is
15.)
System Action: Processing continues.
Programmer Response: Resubmit the job.
Problem Determination: Table I, items 1, 3, Sa, 13, 16, 29.
$HASP353
iii
CLOSE FAILED BECAUSE NOT SYSIN, SYSOUT,
NOR PROCESS-SYSOUT
Explanation: A CLOSE macro instruction failed for a subsystem
data set because JES2 could not determine the data set's type
from the data set name in the JFCB. (The importance level is
15.)
System Action: Processing continues.
Programmer Response: Resubmit the job.
System Action: The error is indicated to the user as a
permanent write error.
Operator Response: If the intern~1 reader 10 is STCINRDR,
reissue the START or MOUNT command when there is less
system activity.
Programmer Response: If the internal reader 10 is INTRDR,
rerun the job. If this message occurs frequently, consider
increasing the size of the common storage area.
$HASP355
SPOOL VOLUMES ARE FULL
Explanation: A request to the JES2 direct access space
allocation can not be processed. All available space has been
allocated to JES2 functions. (The importance level is 15.)
System Action: The system suspends JES2 processors and
users of JES2 services that require direct access space, until
an output function completes and the associated direct access
space becomes available.
Operator Response: Determine which jobs are awaltlnl output
($DN command) and then initiate output processi", 'for those
jobs. If. no output is queued, cancel jobs that are awaiting
execution or are in execution.
$HASP356
Jif nnn % SPOOL USAGE
Explanation: In allocating a unit of spool space, JES2 has
found that the total spool space now in use exceeds a
pre-specified warning percentage. (The importance level is
15.)
System Action: Processing continues.
Operator Response: If the percentage in this message· reaches
100 and another unit of spool space is requested, message
$HASP355 will appear. Therefore, do not start any new jobs
for awhile, and attempt to purge any jobs which have
completed execution from the system.
$HASP357
$HASP358
iii Intrdrld - STORAGE NOT AVAILABLE FOR
BUFFERS
Explanation: Either in the common storage area or in the user
memory, storage was not available to buffer data for a JES2
internal reader data set. (The importance level is 15.)
1-16
VS2 System Messages (VS2.03.803)
iii
HIOTSPIN--NO STORAGE AVAILABLE ON SP
231
Explanation: During allocation of a subsystem SPIN or HOLD
data set, JES2 has failed to obtain storage from a common
storage area (CSA).
System Action: The data set is purged and processing
continues.
Programmer Response: Provide more common storage area.
$HASP359
Jif
HCBGM - NO STORAGE AVAILABLE IN SP 230
Explanation: While attempting to start execution of a job, JE52
has failed to obtain storage from the user address space to
hold one of the job's direct access resident control blocks.
(The importance level is 15.)
System Action: Processing continues.
Programmer Response: None.
$HASP361
$HASP354
iii STORAGE UNAVAILABLE FOR SDB
Explanation: JES2 cannot allocate a subsystem data set;
because storage within the user's memory is unavailable for a
subsystem data set block. (The importance level is 15.)
System Action: The subsystem data set is not allocated.
Programmer Response: Reduce the data set requirements of
the job step.
JOB NOT FOUND
Explanation: JES2 was unable to find a job in its job queue
which an initiator requested specifically by job identifier. The
job was created by a START or MOUNT command or by a TSO
LOGON command. (The importance level is 15.)
.
System Action: The requesting initiator is stopped.
VS2.03.803
~ Operator
Response: Reissue the command that created the
'job.
$HASP362
STORAGE UNAVAILABLE FOR SJB
Explanation: JES2 has failed to obtain storage for a subsystem
job block and therefore cannot continue processing for an
initiator. (The importance level is 15.)
System Action: The initiator should stop normally. The initiator
is stopped due to an operator request, or because the initiator
had been started to run an STC or TSU job and that job had a
JeL error, or because insufficient storage was available.
Programmer Response: If this message occurs frequently,
increase the size of the common storage area.
$HASP363
[Jln HCBIO - INVALID TRACK ADDRESS
Explanation: JES2 has attempted to read or write a
disk-resident job control block to an invalid track address.
(The importance level is 15.)
System Action: If the message occurred during job initiation,
the job is terminated. Otherwise, processing continues.
Operator Response: None.
[jjj] HCBIO - INVALID CONTROL BLOCK - xxx
Explanation: JES2 has read a disk-resident job control block
whose identifier, xxx, is unrecognized. (The importance level is
15.)
System Action: The job being initiated is terminated.
Operator Response: None.
$HASP364
$HASP365
jjj DDNAME ddn - DATA SET ACCESSED WHILE
CLOSED
~iExplanation:
A JES2 subsystem data set had been open but is
~now closed and the user program is attempting to gain access
to it. (The importance level is 15.)
System Action: A subsequent attempt to use the data set will
result in a system completion code of OFA.
Programmer Response: Make sure that the data set is open
before attempting to use it.
$HASP366
jjj AWAITING SPOOL SPACE
Explanation: A request for JES2 direct access space allocation
can not be processed. The request is on behalf of a JES2 data
set. This message follows the $HASP3SS message. (The
importance level is 15.)
System Action: The task requesting output to the JES2 data
set is placed in a wait state. When space is freed, JES2
attempts to get direct access space and continue processing
the task.
Operator Response: Attempt to clear the system of jobs by
forcing output of executed jobs or by canceling jobs.
Programmer Response: Provide more space for JES2 data
sets.
$HASP370
[jjj] HCBIO - I/O ERROR
READING}CONTROL BLOCK - xxx
{ WRITING
Explanation: JES2 has encountered a permanent I/O error
while reading or writing a disk-resident job control block
whose identifier is xxx. (The importance level is 15.)
System Action: If the error occurred on a read, the job is
terminated. Otherwise, processing continues.
Operator Response: None.
~$HASP371
jjj HCBFM - FREEMAIN FAILED FOR SP 230
Explanation: ' JES2 failed in attempting to release main storage
for a direct access resident job control block. (The importance
level is 15.)
System Action: Processing continues.
Operator Response: None.
$HASP373
jJJ STARTED
Explanation: The named job is beginning execution. (The
importance level is 15.)
System Action: Processing continues.
Operator Response: None.
$HASP374
jjj - JOB HAS NO JOURNAL
Explanation: The named job was attempting to warm start or
restart. In both cases, a job journal data set is required, but
the job had none. (The importance level is 15.)
System Action: The job is terminated.
Operator Response: None.
$HASP375
Jjj ESTIMATED {LINES } EXCEEDED BY nnn
CARDS
Explanation: Job jjj has exceeded its estimated number of
lines or cards by nnn. (The importance level is 15.)
System Action: The action depends on the installation options.
If abnromal termination results, the system completion code is
722 and a dump mayor may not be taken.
If the' task producing the output is already terminating
(normally or abnormally) JES2 will not attempt abnormal
termination.
Programmer Response: None.
$HASP376
jJj - UNABLE TO PROCESS SUBSYSTEM DATA
SET FOR HOLD
Explanation: JES2 can not obtain sufficient storage in the
common storage area to honor a request to make a held data
set out of a normal SYSOUT data set. (The importance level is
15.)
System Action: The request is ignored and processing
continues.
Programmer Response: If this message occurs frequently,
increase the size of the common storage area. (The
importance level is 15.)
$HASP395
jjj ENDED
Explanation: The named job has completed execution. (The
importance level is 15.)
System Action: Processing continues.
Operator Response: None.
$HASP396
jjj TERMINATED
Explanation: Due to circumstances specified by previous
messages, the named job was unable to start execution. (The
importance level is 15.)
System Action: Processing continues.
Operator Response: None.
$HASP397
jjj RE-ENQUEUED
Explanation: The named job is reenqueued for OS/VS2
warm-start or restart processing. (The importance level is 15.)
System Action: Processing continues.
Operator Response: None.
$HASP398
jjj QUEUED FOR RE-EXECUTION
Explanation: In response to operator command $E jjj or $E j,
or because the initiator has insufficient resources to start the
Section 1: $HASP Messages - JES2
1-17
VS2.03.803
job, the named job is queued for re-execution. (The
importance level is 15.)
System Action: Processing continues.
Operator Response: None.
$HASP400
ENTER REQUESTS
Explanation: JES2is ready for job processing and is waiting
for requests. (The importance level is 15.)
System Action: JES2 will not process jobs until a $S command
is entered.
Operator Response: Perform necessary preparatory functions,
and enter the $S command (if job processing is required) or
$P JES2 if JES2 is to be withdrawn.
$HASP401
EXTENT ERROR ON ser
Explanation: The operator did a JES2 warm start. JES2 has
found that the first extent of data set SYS1.HASPACE on ser is
different than before the warm start, due to: mounting the
wrong volume, starting a different JES2 system, or scratching
and reallocating SYS1.HASPACE. (The importance level is 15.)
System Action: After attempting to verify the remaining
required volumes, JES2 terminates.
Programmer Response: Make sure that all spooling volumes
are correct. If not, mount the correct ones. If correct, perform
a cold start thus destroying any job information contained in
the SYS1.HASPACE data set.
$HASP402
ttt ATTACH ERROR -cde
Explanation: JES2 has attempted to attach a subtask, which is
required for running the system. The module name indicates
the EBCDIC name of the subtask entry ttt, and cde is the OS
completion code returned. If the system is allowed to continue
processing, the results will be unpredictable but will cause
general malfunction as follows:
• HASPIMAG - JES2 FCB and UCS image retrieval facility will
be inactive, output devices requiring images from the
SYSl.IMAGES library will not operate.
• HASPWTO - JES2 WTO interface facility will be inactive,
eventually causing JES2 to become interlocked when it
attempts to use the OS console interface.
• HASPACCT - JES2 SMF interface facility will be inactive,
eventually causing JES2 to become interlocked when it
attempts to write SMF records.
(The importance level is 15.)
System Action: JES2 will attempt to process jobs.
Operator Response: Probable user error. Stop JES2, refer to
the VS2 System Completion Codes manual, and correct the
problem as indicated.
$HASP403
IS SYSTEM XXXX DOWN - - REPLY Y/N
Explanation: The operator has warm-started a single system in
a JES2 shared spool complex. Another system in the complex
is suspected of being down. (The importance level is 15.)
System Action: The warm start does not proceed until the
operator responds to the message.
Operator Response: If the system specified is down, the
operator should reply 'y'. Otherwise the operator should reply
'N'.
$HASP404 {JOB} j - BAD {JCT}- ERRORS MAY OCCUR
STC
lOT
TSU
Explanation: The operator has warm-started JES2. A
direct-access allocation map for the job was discovered to be
in error. (The importance level is 15.)
1-18
VS2 System Messages (VS2.03.803)
System Action: The control block allocation map is altered to
preserve system integrity, and the control block is rewritten.
The job may experience premature end on input data sets
(JCT) or output data sets (lOT).
Operator Response: Consult the installation procedures guide
to determine the advisability of deleting the job, resubmitting
it, or allowing the job to continue.
$HASP40S
{JOB}
STC
TSU
j WAS BEING PURGED
Explanation: JES2 warm-start processing encountered a job
that was being purged when system shutdown. (The
importance level is 15.)
System Action: The identified job is purged.
Operator Response: None.
$HASP406 {JOB} j WAS EXECUTING
STC
TSU
Explanation: The operator has warm-started J£S2. When the
system stopped, the job was in the JES2 execution phase.
(The importance level is 15.)
System Action: JES2 will submit the job to the system for
determination of whether or not the job can be restarted.
When the job is submitted to an initiator, appropriate
messages will be issued allowing the operator to elect restart
options. In the latter case, all of the job's data sets (including
the system message and JES2 job log data sets) may not print
to completion; some may not print at all.
Operator Response: If the normal system action is not desired,
the job should be held or canceled as desired.
$HASP407 {JOB}
STC
TSU
j WAS TERMINATING
Explanation: JES2 warm-start processing encountered a job
that was terminating its execution during system shutdown.
(The importance level is 15.)
System Action: The identified job is· queued for output
processing.
Operator Response: None
$HASP408 {JOB}
STC
TSU
j IS RE-QUEUED AND HELD
Explanation: JES2 warm-start processing encountered a job in
execution during shutdown. The job was journalled or marked
as restartable.
System Action: The identified job is placed back into the
execution queue and held.
Operator Response: None.
$HASP409 {JOB}
STC
TSU
j WAS ON READER
Explanation: The operator has warm-started JES2. When the
system stopped, the job was in the process of reading. (The
importance level is 15.)
System Action: The job is purged.
Operator Response: Resubmit the job.
$HASP410
JOB j WAS PRINTING/PUNCHING
Explanation: The indicated job was printing or punching when
the lastJES2 checkpoint was taken (prior to this warm start).
(The importance level is 15.)
YS2.03.803
~~I
>i
System Action: The job is requeued, and the output function is
continued when print/punch devices are available.
Operator Response: The operator may use the following
console commands:
• $H - hold job - to prevent output from occurring until a $A
(release) command is entered.
• $C - cancel job - to remove the job from the output queue
and pass it to purge.
If neither of these commands is used, the job can be
controlled normally when it is started on a device.
SHASP411
of the checkpoint data set SYS1.HASPCKPT is not sufficient to
hold the job queue checkpoint elements or the track length on
the volume is not at least 6000 bytes long. (The importance
level is 15.)
System Action: JES2 terminates.
Operator Response: Notify the system programmer of this
message.
Programmer Response: Examine the SYSl.HASPCKPT
allocation and the system generation of the device attribute
table for correct track length specifications and correct as
appropriate.
MAXIMUM OF nnn SPOOL VOLUME(S) EXCEEDED
Explanation: More direct-access SPOOL volumes have been
found online than JES2 can handle. (The importance level is
15.)
System Action: JES2 terminates.
Operator REsponse: Probable user error. Check the volume
labels of all direct-access volumes and remove all but nnn
volumes. Restart JES2.
SHASP416
OPERATOR MESSAGE SPACE NOT AVAILABLE
Explanation: JES2 has attempted to reserve tracks from the
are physically online to the CPU than JES2 supports. (The
importance level is 15.)
System Action: The first nnn devices of the specified type will
be used by JES2; additional devices of the specified type will
be ignored.
Programmer Response: Check the OS generation to ensure
that the hardware devices correctly reflect the system
configuration.
primary SPOOL volume for remote operator message queueing
and has found that:
• The first extent of SYS1.HASPACE was not large enough for
the requested number of SPOOL records.
• During JES2 warm start, the SPOOL volume was found
incompatible with the loaded copy of JES2.
(The importance level is 15.)
System Action: JES2 terminates.
Operator Response: During JES2 warm start, match the
primary SPOOL volume with the JES2 loaded module used
during the cold start. During cold start, consult the system
programmer.
Programmer Response: Make sure that the JES2GEN
parameter & SPOLMSG has been correctly applied to the
system, and check the extents of SYSl.HASPACE on the
primary SPOOL volume for requested space.
SHASP413
SHASP417
SHASP412
MAXIMUM OF nnn devtyp EXCEEDED
Explanation: More reader, printer, punch, or RJE line devices
MOUNT ser ON A devtyp
\\
, Explanation: The operator warm-started JES2. Not all SPOOL
" volumes mounted prior to the warm start are now mounted. In
the message, the volume serial number and the device type on
which the volume had been mounted are given. (The
importance level is 15.)
System Action: After attempting to verify the remaining
required SPOOL volumes, the JES2 job terminates.
Operator Response: Probable user error. Mount the required
volume(s) on the required devices, and warm start (or cold
start) JES2.
SHASP414
OBTAIN FAILED FOR dsn ON ser WITH CC cde
Explanation: The operator warm-, cold-, or format-started
JES2. JES2 used the OBTAIN supervisor service to get
information about data set dsn on the volume ser, but OBTAIN
did not work as expected. OBTAIN issued condition code cde
to indicate the problems:
• 04 - The volume was not mounted. This error should not
occur.
• OS - Data set dsn was not allocated on the volume ser.
• 12 - A permanent input/output error was found during
OBTAIN processing.
(The importance level is 15.)
System Action: After attempting to verify the remaining spool
and checkpoint volumes, JES2 terminates.
Programmer Response: Probable user error. If cde is OS,
allocate a data set named dsn on the volume ser and start
JES2 again. If cde is 12, use the IBM utility program IEJDASDR
or IBCDASDI to reinitialize the volume ssss, and then follow
the procedure for cde OS.
SHASP415
JOB QUEUE EXCEEDS CAPACITY OF
CHECKPOINT DATA SET
VOLUME ssss NOT ADDED - COMPLEX NOT
DORMANT
Explanation: The operator has warm-started JES2. JES2 has
found candidate for a spool volume (ssss) that is not recorded
in the checkpoint record as a member of the current pool.
Other system(s) are sharing the checkpoint record; therefore,
the new candidate cannot be added to the pool at this time.
(The importance level is 15.)
System Action: JES2 ignores the presence of this volume.
Operator Response: JES2 does not use the volume, but it
remains allocated.
SHASP41S
PERM I/O ERROR ON ser WHILE FORMATTING
Explanation: JES2 was unable to finish formatting the first
extent of SYSl.HASPACE on the SPOOL volume, because a
hardware error occurred or because the SPOOL volume is not
properly initialized. (The importance level is 15.)
System Action: After attempting to process the remaining
SPOOL volumes, JES2 terminates.
Operator Response: If the error was caused by a hardware
malfunction, have it corrected. If not, the SPOOL volume may
need to be reinitialized. Reinitialize it using IEHDASDR or
IBCDASDI.
SHASP419
REPLY Y OR N TO CONFIRM RESET ON
SYSTEM(S) sid,sid, .•. ,sid.
Explanation: JES2 initialization has determined through
analysis of the checkpoint record that the documented
member(s) of the complex are not currently active. However,
since a system can remain active between a JES2 failure and a
JES2 restart without recording checkpoint records, the above
analysis must be confirmed by the operator. (The importance
level is 15.)
System Action: JES2 waits for the operator to reply.
Explanation: The number of tracks allocated to the first extent
Section 1: SHASP Messages - JES2
1-19
•
VS2.03.803
Operator Response: Determine whether the documented
systems are inactive. Reply 'Y' if all documented systems are
dormant; otherwise reply 'N'.
$HASP420
PERM I/O ERROR .{WRITING} JES2 CKPT
READING
Explanation: JES2 failed to correctly read or format-write the
JES2 checkpoint record because of a hardware malfunction or
the parameters in the device attribute table· do not match the
characteristics of the actual device. (The importance level is
15.)
System Action: JES2 terminates.
Operator Response: If the message was caused by an oversize
checkpoint record, inform the system programmer.
Programmer Response: Check the device attribute table to
insure the values appropriately describe the device.
$HASP421
PREVIOUSLY MOUNTED VOL ser IS
UNFORMATTED
• The previous JES2 did not leave the interface in a
restartable condition.
• An interface user is still actively using the interface.
(The importance level is 15.)
System Action: The JES2 subsystem that is attempting to
restart is terminated.
Operator Response: If there is a JES2 subsystem up and
running, stop that subsystem before attempting to start a new
JES2; otherwise, re-IPL the system.
$HASP426
SPECIFY OPTIONS - SUbsystem identification
Explanation: JES2 has been given control and is requesting
instructions from the operator. (The importance level is 15.)
System Action: JES2 waits for the operator to reply.
Operator Response: Enter the desired options using the OS
reply format. Consult the Operator's Reference for option
selections.
$HASP427
SYNTAX ERROR - RESPECIFY OPTIONS
Explanation: The operator warm-started JES2. The length of
Explanation: JES2 does not recognize one or more of the
the first record of the last track of the first extent on
SYSl.HASPACE is incorrect, due to overwriting, starting a
different JES2system, or mounting the wrong SPOOL volume.
(The importance level is 15.)
System Action: After attempting to verify the remaining
required SPOOL volumes, JES2 terminates.
Operator Response: Probable user error. If the wrong volume
was mounted, mount the correct volume and warm-start JES2.
Otherwise, cold-start JES2; any SPOOL volumes that are not
correctly formatted will automatically be reformatted during a
JES2 cold-start.
initialization options entered by the operator in response to
message $HASP426. (The importance level is 15.)
System Action: JES2 resets to default responses, and waits
for the operator to reply.
Operator Response: Probable user error. Enter the desired
options.
$HASP422
DUPLICATE ser VOLUMES
Explanation: Multiple direct-access volumes have been found
with identical labels. (The importance level is 15.)
System Action: JES2 terminates.
Operator Response: Probable user error. Check the volume
labels of all direct-access volumes on the system and remove
the required volumes. Restart JES2.
$HASP423
ser IS BEING FORMATTED
Explanation: The operator warm, cold, or format-started JES2.
An unformatted SPOOL volume is now being formatted. (The
importance level is 15.)
System Action: JES2 formats unformatted new SPOOL
volumes on a warm start, all unformatted SPOOL volumes on a
cold start, and all SPOOL volumes on a format start.
Operator Response: None.
$HASP424
ser IS NOT MOUNTED
Explanation: The operator warm, cold, or format-started JES2,
and JES2 could not find a direct-access uca with the volume
serial of the primary SPOOL volume. The SPOOL volume must
be mounted and online when JES2 is started. (The importance
level is 15.)
System Action: JES2 terminates.
Operator Response: Probable user error. Make sure the
primary SPOOL volume is mounted, ready, and online. Then
restart JES2.
$HASP42S
SUBSYSTEM INTERFACE NOT DORMANT
Explanation: The operator attempted to start the JES2
subsystem when the interface created by a previous JES2 is
still active. This could be caused by any of the following:
• The previous JES2 is still operating.
1-20
VS2 System Messages (VS2.03.803)
$HASP428
CORRECT THE ABOVE PROBLEMS AND RESTART
JES2
Explanation: This message follows one or more messages
which indicate why JES2 direct-access initialization could .not
complete normally. (The importance level is 15.)
System Action: JES2 terminates.
Operator Response: Correct the above problems and restart
JES2.
$HASP429
SUBSYSTEM NAME NOT DEFINED
Explanation: The operator attempted to start a procedure for
JES2 with a name that was not generated into the operating
system. (The importance level is 15.)
System Action: JES2 terminates.
Operator Response: Notify the system programmer of this
message.
$HASP430
INCOMPATIBLE SUBSYSTEM INTERFACE
Explanation: The operator attempted to start a JES2 system
after a previous JES2 completed its initialization process. The
previous JES2 created an environment that prevents the
current JES2 system from initializing. (The importance level is
15.)
System Action: JES2 terminates.
Operator Response: Re-IPL the operating system or start a
compatible 'JES2.
$HASP431
COLD/FORMAT START DENIED -- COMPLEX
NOT DORMANT
Explanation: Environmenta.1 analysis has determined that at
least one system in the complex is not dormant and therefore
a cold or format start cannot be performed. (The importance
level is 15.)
System Action: JES2 terminates.
Operator Response: Wait for the amount of time specified by
the variable & SYNCTOL, then try again. If the problem
persists, notify the system programmer.
Programmer Response: Each system in the complex uniquely
time-stamps the checkpoint record each time it is written. This
VS2.03.803
requires that all TOO clocks in the complex be synchronized
within the bounds established by the variable & SYNCTOl. If
this constraint is not adhered to (Le. the wrong date is set at
IPL time), cold and format starts are prevented until the
checkpoint· record expires or the checks are bypassed.
$HASP432
REQUESTED JES2 BUFFERS EXCEED AVAILABLE
STORAGE
Explanation: The amount of space required for buffers has
exceeded the available virtual storage.
System Action: JES2 terminates.
Programmer Response: Reduce the number of buffers
specified in the & NUMBUF andlor & NUMTPBF initialization
parameters, or reduce the size of the buffers specified in the
& BUFSIZE andlor & TPBFSIZ initialization parameters.
$HASP433
WARM START DENIED -- SYSTEM NOT
DORMANT
Explanation: Environment analysis has determined that the
checkpoint record for the system being warm-started has not
expired. (The importance level is 15.)
System Action: JES2 terminates.
Operator Response: Wait for the amount of time specified by
the variable & SYNCTOL, then try again. If the problem
persists, notify the system programmer.
Programmer Response: This problem usually results from an
incorrect datel clock setting during a previous IPl.
$HASP434
~ COLD
t
{WARM)
following reasons:
• Permanent I/O error.
• Field named $HASPID did not contain "JES2."
• Operator has replied "N" to message $HASP436.
(The importance level is 15.)
System Action: JES2 terminates.
Operator Response: Notify system programmer.
Programmer Response: Ensure that the system being started is
the same as or is compatible with the last one run. If gross
incompatibilities in HASP parameter values are discovered, the
system must be cold-started.
SYSTEM PARAMETER TABLE ERROR
Explanation: The system parameter table as defined by
parameter cards SI through S7 is invalid for one of the
following reasons:
• The entries in the table are not contiguous.
• The table contains duplicate entries.
• The table does not contain the SMF CPU id for this system.
• An attempt was mac;Je to change the table on a warm start.
• A multiple-system configuration was defined, but the
checkpoint volume or a spool volume was found on a device
whose UCB does not indicate shared capability.
(The importance level is 15.)
System Action: JES2 terminates.
Operator Response: Notify system programmer.
Programmer Response: Analyze parameter cards SI through
S7 and correct the problem. Start JES2 again.
$HASP436
$HASP438
" NUMTGV EXCEEDS TRACKS ON xxxxxx
Explanation: The specified number of track groups in each
volume exceeds the number of tracks in the smallest spool
volume in the system.
System Action: JES2 terminates.
Programmer Response: Increase the size of the spool volume
(that is, select a device that has as many tracks as specified
by & NUMTGV); or decrease the number of track groups per
volume.
$HASP439
CMBS EXHAUSTED--LAST nnn OPERATOR
COMMANDS IGNORED
Explanation: The number of operator commands in the
initialization deck has exceeded the number of buffers
specified on the" NUMCMBS initialization parameter.
System Action: The last nnn commands are ignored, and
processing continues.
Programmer Response: Reduce the number of commands, or
increase the size specified in the & NUMCMBS parameter.
$HASP440
START DENIED --.INVALID
CHECKPOINT RECORD
Explanation: The checkpoint record is invalid for one of the
$HASP435
checkpoint record has been legally requested. The operator is
asked to confirm his intent to change the record. (The
importance level is 15.)
System Action: JES2 waits for the operator to reply.
Operator Response: Reply "Y" if the checkpoint record is to
be changed (this includes the creation of a new checkpoint
data set); otherwise reply "N".
REPLY Y OR N TO CONFIRM CHECKPOINT
RECORD CHANGE
Explanation: Analysis shows that a change to the fundamental
" BUFSIZE TOO SMALL FOR "NUMTGV
AND lOR "NUMDA
Explanation: A track group map fora spool device exceeds
the size specified on the" BUFSIZE initialization parameter.
System Action: JES2 terminates.
Programmer Response: Increase the values specified for
& BUFSIZE, or decrease the value specified for "NUMTGV
andlor & NUMDA. In any case, "BUFSIZE should not be less
than (600 + (& NUMDA( " NUMTGV18»).
$HASP441
REPLY Y OR N TO CONTINUE INITIALIZATION
Explanation: JES2 has found an error during initialization, and
is asking the operator whether or not initialization should
continue.
System Action: If the response is Y, JES2 proceeds, replacing
the flagged parameter value with the last previously specified
legitimate value or with the JES2 default value. If the response
is N, JES2 issues message $HASP428 and then terminates.
Operator Response: Reply Y or N, and notify the system
programmer.
Programmer Response: Correct the indicated error(s).
$HASP442
WARM START DENIED
REQUIRED INITIALIZATION PARAMETERS
FOLLOW
" BUFSIZE " NUMDA " NUMTGV ...
" SPOOL " MAXJOBS " NUMJOES & RECINCR -'
& TCELSIZ " NUMRJE & MINJOES &SPOLMSG-
Explanation: A warm start has failed because of conflicts
between the values of the initialization parameters and the
present configuration. JES2 lists the parameters with the
values that were previously specified for them. The parameters
requiring changes are flagged with an asterisk.
System Action: JES2 terminates.
Section 1: $HASP Messages - JES2
1-21
•
VS2.03.803
Programmer Response: Correct the parameters in conflict, and
restart JES2.
$HASP443
xxxxxx NOT ALLOCATED
Explanation: A spool volume has not been allocated. This
message was preceded by another JES2 message indicating
the problem.
System Action: If the volume is a primary spool volume or a
checkpoint volume, JES2 terminates; otherwise, processing
continues.
Operator Response: Mount the correct volume on the required
device.
$HASP444
System Action: The system scans the remaining parameters,
flags the errors, and issues a message requesting that JES2 be
restarted.
Programmer Response: Correct the line subparameter of the
RMTnnn parameter for this terminal, and restart JES2.
$HASP900
ENTER CARDS, UPDATE, OR END
Explanation: JES2 generation is requesting the JES2
generation parameter and update deck options from the
operator. (The importance level is 15.)
System Action: The system waits for the operator to reply.
Programmer Response: Tell'the operator which response to
enter.
dddddddd PRINT/PUNCH ROUTE CODE INVALID
Explanation: A print/punch route code has been specified that
$HASP901
is greater than the number of available devices; that is, the
number of remote terminals specified in & NUMRJE conflicts
with the route code specified in a READ ERn or Rnnn.RDm
parameter card.
System Action: JES2 terminates.
Programmer Response: Verify the initialization parameters, and
correct the error.
Explanation: The JES2 generation parameter prm is not one of
the defined JES2 generation parameters. (The importance level
is 15.)
System Action: If a batch JES2 generation is not being
performed, the program is not terminated. Control is returned
to the console for operator correction.
Operator Response: Correct the prm parameter.
$HASP448
ILLEGAL BACKSPACE CHARACTER--RESET TO
$HASP902
X'OO'
Explanation: The JES2 generation parameter specification
Explanation: The backspace character conflicts with the
console command character specified in the initialization
parameter & CCOMCHR.
System Action: The system ignores the backspace character
specified, and uses X'OO' instead.
Programmer Response: Select another character for the
& BSPACE initialization parameter.
$HASP449
xxxxxx MUST BE MOUNTED ON SHAREABLE
DEVICE
Explanation: The specified volume has been mounted on a
non-shareable device in a shared spool environment.
volume; otherwise, processing continues.
device.
$HASP450
OPEN FAILED FOR JES2 PARAMETER LIBRARY
Explanation: JES2 issued an OPEN macro instruction for the
parameter library data set and determined that the data set
was not opened. (The importance level is 15.)
System Action: Message & HASP441 follows, requesting
operator action.
Programmer Response: Determine the cause of the error and
correct it.
$HASP451
$HASP903
initialization parameter library. (The importance level is 15.)
System Action: Message & HASP441 follows, requesting
operator action.
Programmer Response: Determine the cause of the error and
correct the parameter errors.
$HASP465 RMTnnn SPECIFIES INVALID LINE VALUE
Explnation: .A BSC remote terminal attempted to specify
ownership of an SNA line; an S~A remote terminal attempted
to specify a BSC line; or a remote terminal (either BSC or
SNA) specified a line number greater than the value specified
for the & NUMLINES parameter.
~-22
VS2 System Messages (YS2.03.803)
JES2 GENERATION UPDATE ERROR -- JES2
GENERATION TERMINATED
Explanation: An error was discovered in the source update
process. This error may result from an error in an update
control card or a sequence error in the update deck. (The
importance level is 15.)
System Action: The last card processed or current card being
processed will be the last card listed on the SYSPRINT data
set.
Operator Response: Inform the system programmer of this
, message.
Programmer Response: Correct the generation card and rerun
the job.
$HASP904
ERROR ON JES2 PARAMETER LIBRARY
Explanation: JES2 encountered an error when reading the
INVALID SYNTAX
violates requirements documented in the SYSGEN manual. (The
importance level is 15.)
System Action: If a batch JES2 generation is not being
performed, the program is not terminated and control is
returned to the console for operator correction.
Operator Response: Inform the system programmer of this
message.
Programmer Response: Correct the parameter from the
console or card reader if non-batch generation is being
performed. Allow the generation to continue.
System Action: JES2 terminates if the volume is a required
Operator Response: Mount the required volume on a shareable
prm - INVALID JES2 GENERATION PARAMETER
INSUFFICIENT DIRECTORY SPACE IN HASPSRC
DATA SET
Explanation: The directory space in the SYS1.HASPSRC data
set is not large enough to contain all the members in the JES2
source date set. (The importance level is 15.)
System- Action: JES2 generation terminates.
Programmer Response: The SYS1.HASPSRC data set should
be scratched and reallocated with a larger directory size. The
JES2 generation should then be repeated.
$HASP905
DIRECTORY I/O ERROR ON HASPSRC DATA SET
Explanation: An I/O error occurred during update of the
directory for the SYS1.HASPSRC data set. (The importance
level is 15.)
System Action: JES2 generation terminates.
I~
VS2.03.803
~Operator Response:
Inform the system programmer of this
'message.
Programmer Response: Scratch and reallocate the
SYS1.HASPSRC data set on another volume and rerun the
JES2 operation.
$HASP906
INVALID SYSIN DATA SET
Explanation: More than the maximum allowable JES2
generation parameters have been read due to a system error
or an invalid input stream. (The importance level is 15.)
System Action: The JES2 generation process is terminated.
Operator Response: Notify the system programmer of this
message.
$HASP950
PLACE RMTGEN OPTIONS IN UNIT ddd AND
REPLY 'GO', OR REPLY 'CANCEL'
Explanation: The JES2 remote generation module EXRMTGEN
has been entered and has determined that the installation has
gel(lerated the JES2 system specifying that remote workstation
programs are to be generated. If the device address displayed
is not a card reader, the JCL is not as anticipated by the
module and the generation of remotes should not be allowed
to continue using this module. (The importance level is 15.)
System Action: JES2 waits for the operator to respond.
Operator Response: If the unit is not a card reader, reply
'CANCEL'. If remote workstations are to be generated at this
time, place workstation descriptions in the card reader (see
System Generation Manual) and reply 'GO'.
$HASP955
INCOMPATIBLE RMTGEN MODULES
Explanation: A module has attempted to read logical records
"~'I: beyond the end-of-file on the CARDIN data set and
/ encountered an end-of-file condition without replacing the
EODAD exit address in the DCB. (The importance level is 15.)
System Action: RMTGEN abnormally terminates with a user
code of 20.
Programmer Response: Restore the JES2 generation modules
using the correct version of the GENRMT module.
$HASP965
"''''''''''INVALID SELECTION CARD"'u",
Explanation: A JES2 remote workstation generation selection
card is invalid for one of the following reasons:
• The program identification card named an unsupported
remote.
• The format of the identification card was incorrect.
• The numeric field was not numeric.
The card in error is displayed preceding the error message,
and the generation of the requested remote is suppressed.
(The importance level is 15.)
System Action: The generation of the remote is suppressed.
Operator Response: Report this message to the system
programmer.
Programmer Response: Correct the selection card and
resubmit the remote generation job. (See the System
Generation Manual section JES2 Workstation Program
Generation.)
$HASP966
uUOPTION SPECifiCATION ERROR""u",
Explanation: A JES2 remote workstation generation option
specification error occurred for one of the following reasons:
• The specified RMTGEN parameter was misspelled.
• The format of the card was incorrect.
• Card sequence numbers were not in ascending order.
• An invalid ./ card was encountered.
• A $. card, other than $.RMTEND, was encountered during
the update process.
• A 1* card was encountered within a remote description
deck.
.
(The importance level is 15.)
System Action: The card in error is displayed preceding the
error message, and the generation of the requested remote is
suppressed.
Operator Response: Report this message to the system
programmer.
Programmer Response: Correct the JES2 remote workstation
generation deck and resubmit the job.
$HASP967
uuJES2 SOURCE LIBRARY ERROR*u*
Explanation: A JES2 source library error occurred during a
JES2 remote workstation program generation for one of the
following reasons:
• An internal control card on the GENPDS data set member
HRTPOPTS was incorrect or missing.
• An overflow of the GENRMT standard options table has
occurred.
(The importance level is 15.)
System Action: The generation of the requested remote is
suppressed.
Programmer Response: Check the spelling on the selection
card and, if spelling is correct, recreate the JES2 generation
modules and source.
$HASP968
*u""UNEXPECTED END Of CARD INPUTu"",,,
Explanation: The last card of the CARDIN data set for a JES2
remote workstation program generation was not $.RMTEND, or
in the case of updating operations .1 ENDUP. (The importance
level is 15.)
System Action: The generation of the requested remote is
suppressed.
Programmer Response: Supply a $.RMTEND card.
$HASP985
*",uREMOTE station EXCEEDS AVAILABLE 1130
STORAGEuU
Explanation: The JES2 remote workstation program that has
just been assembled was found to be too large for the 1130
storage because of remote generation parameter specifications
or modifications. (The importance level is 15.)
System Action: The identified remote workstation generation is
suppressed.
Programmer Response: Alter parameters or modifications so
that less 1130 storage is needed.
$HASP986
",u""REMOTE station DECK INCOMPLETEu,,",,"
Explanation: The END card of the assembler object deck
output for the 1130 workstation program was not encountered
before the end of that data set, thus indicating that the
resultant 1130 deck may be incomplete. (The importance level
is 15.)
System Action: The generation of the remote workstation
program is suppressed.
Programmer Response: Check the remote workstation
generation job JCL, correct and rerun.
$HASP990
S3CNVT - UNEXPECTED OR MISSING
END-Of-DATA
Explanation: During RMTGEN post-assembly processing for a
System/3 workstation, the post-processor has received an
end-of-data before the assembler object deck's END card or
has received no end-of-data on a read immediately after the
END card. In the latter case, the RMTGEN output deck may be
correct. The data definition name is SYSLIN or SYSGO. (The
importance le'(el is 15.)
Section 1: $HASP Messages - JES2
1-23
•
VS2.03.803
System Action: Post-processing completes with return code
12.
Programmer Response: Verify the RMTGEN punched output to
insure it is correct. The last card should contain EOR in
columns 2-4. If necessary, alter the RMTGENprocess by
punching out the assembly object deck and using it as input
(SYSLlN; SYSPUNCH is punched output) to post-processor
program SYS3CNVT.
$HASP991
S3CNVT - UNABLE TO OPEN ONE OR BOTH
DATA SETS
Explanation: During RMTGENpost-assembly processing for a
System/3 workstation, the post-processor was unable to open
the data set for SYSLIN (or SYSGO) and/or the data set for
SYSPUNCH. (The importance level is 15.)
Sys,em Action: Post-processing terminates with return code
16.
Programmer Response: Correct the JCL and resubmit the
RMTGEN job.
1-24
YS2 System Messages (YS2.03.803)
Section 2: Power Warning Feature Support Messages (ICF)
Component Name
ICF
Program Producing Message
Power Warning Feature
Audience and Where Produced
For operator: console.
For Programmer: SYSOUT listing.
Message Format
xx ICFTIMnn Text
xx
Message reply identification (absent, if operator reply not required).
TIMnn
Message serial number.
text
Message text.
Comments
None.
Associated Publications
OS/VS System Programming Library: Supervisor, GC28-0628
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
I
ICFTIMll WARN TIME PARAMETER IS ZERO - REPLY STOP
OR GO
ICFTIM13 LOCATE/OBTAIN FAILED FOR SYS1.WARNx. REPLY STOP OR GO
Explanation: A time parameter of zero indicates that the
Explanation: The dataset (x) is not cataloged.
System Action: Waits for STOP or GO reply.
Operator Response: GO will cause the system to continue with
the Power Warning Feature Support inoperative. STOP will
cause a disabled wait (X'027').
Programmer Response: Catalog the dataset(s).
Power Warning Feature Support is not operative. Two
conditions can cause this,either:
1) The system was generated with a WARN = parameter
greater than zero, but the time parameter in the system
control blocks has subsequently been modified to be zero,
or
2) The system was generated without WARN = parameter
being specified, but the alternate power (AP = yes»
parameter was specified on any IODEVICE macro.
System Action: Waits for operator reply to STOP or GO.
Operator Response: A reply of STOP will cause a disabled wait
(code X'027'). GO will cause the system to continue without
Power Warning Feature Support.
• For condition 1 - - specify a WARN = parameter if Power
Warning Feature Support is desired, and do not
subsequently modify it.
• For condition 2 - - if AP = YES is specified on any
IODEVICE macro during system generation, the WARN
parameter must be also specified. The parameter value
must be one, or greater than one, ·for functional Power
Warning Feature Support.
ICFTIMl2 WARN TIME PARAMETER IS ONE - REPLY STOP OR
GO
Explanation: A time parameter of one indicates that the Power
Warning Feature Support is operative, but when a power
warning is received, action to transfer main storage to a warn
data set will occur immediately.
System Action: Waits for operator reply of STOP or GO.
Operator Response: Reply GO if it is desired to dump
immediately on the first warning Message. ICFfIM51 will be
issued confirming this choice. STOP will cause a disabled wait
(X'027').
Programmer Response: Ordinarily a time parameter should be
specified to minimize system termination due to transient,
nondamaging power fluctuations.
ICFTIMl4 SYSI.WARNx RESIDES ON MORE THAN 1 VOLUME
- REPLY STOP OR GO
Explanation: Dataset has not been allocated contiguous
cylinders.
System Action: Waits for STOP or GO reply.
Operator Response: GO will cause the system to continue with
the Power Warning Feature Support inoperative. STOP will
.
cause a disabled wait (X'027').
Programmer Response Allocate the dataset as a set of
contiguous cylinders.
ICFTIMIS BOTH SYS1.WARN DATASETS ON.SAME VOLUME REPLY STOP OR GO
Explanation: See message.
System Action: Waits for STOP or GO reply.
Operator Response: GO will cause the system to continue with
the Power Warning Feature Support inoperative. STOP will
cause a disabled wait (X'027').
Programmer Response: Properly allocate datasets on separate
volumes.
ICFTIMl6 VOLUME xxxxxx FOR SYS1.WARNx NOT MOUNTED
- REPLY STOP OR GO
Explanation: The volume (x) specified by the catalog to
contain the dataset is not mounted.
System Action: Waits for STOP or GO reply.
Operation Response: GO will cause the system to continue with
the Power Warning Feature Support inoperative. STOP will
cause a disabled wait (X'027').
Section 2: Power Warning Feature Support Messages (lCF)
2·'
Programmer Response: Allocate the datasets on volumes that
will be mounted before IPL.
ICFTIM 17 VOLUME xxxxxx ON UNPOWERED DEVICE - REPLY
STOP OR GO
Explanation: The IODEVICE macro at sysgen did not specify
that the device would be powered by alternate power in the
event of a utility outage.
System Action: Waits for STOP or GO reply.
Operator Response: GO will cause the system to continue with
th~ Power Warning Feature Support inoperative. STOP will
cause a disabled wait (X'027'). Move volume to powered drive
and re-IPL.
Programmer Response: None
ICFTIM18 WARN DATASETS ON DIFFERENT DEVICE TYPES REPLY STOP OR GO
Explanation: See message.
System Action: Waits for STOP or GO reply.
Operator Response: GO will cause the system to continue with
the Power Warning Feature Support inoperative. STOP will
cause a disabl.ed wait (X'027').
Programmer Response: Allocate both dataset(s) on devices of
the same type.
ICFTIM19 COULD NOT OPEN SYSl.WARNx - REPLY STOP OR
GO
Explanation: An indeterminate error has occurred attempting
to access the dataset.
System Action: Waits for STOP or GO reply.
Operator Response: GO will cause the system to continue with
the Power Warning Feature Support inoperative. STOP will
cause a disabled wait (X'027').
Programmer Response: A detailed examination of the
circumstances is necessary.
ICFTIM20 SYSl.WARNx TOO SMALL FOR STORAGE SIZE REPLY STOP OR GO
Explanation: The amount of main storage indicated at Sysgen
or found at IPL exceeds the capacity of the dataset.
System Action: Waits for STOP or GO reply.
Operator Response: GO will cause the system to continue with
the Power Warning Feature Support inoperative. STOP will
cause a disabled wait (X'027').
Programmer Response: Allocate datasets of the appropriate
size.
ICFTIM21
VALID DUMP IN SYSl.WARNx -- REPLY FORM OR
REST
Explanation: The dataset contains a storage dump.
System Action: Waits for reply of FORM or REST.
Operators Response: FORM causes control to be passed to the
user exit, if one has been provided, and causes the data set to
be erased and formatted. REST causes the contents of the
data set to be restored to main storage. If the restore is
successful, the system enters the wait state with a code
(X'026'). If the restore is not successful, the system enters the
wait state with a code of (X'027').
Programmer Response: None in case of wait state X'026'. A
detailed examination of the circumstances is necessary in case
of wait state X'027'.
ICFTIM22 PATH NOT AVAILABLE FOR WARN DATASET -REPLY
STOP OR GO
Explanation: The system has no path to one data set.
2-2
VS2 System Messages (VS2 Release 3.7)
Operator may have varied all paths to the WARN data set
offline.
System Action: Waits for STOP or GO reply ..
Operator Response: GO will cause the system to continue with
the Power Warning Feature Support inoperative. STOP will
cause a disabled wait (X'027'). The operator must make sure
that the WARN datasets are not varied offline.
Programmer Response: None
ICFTIM23 SYSl.WARNx RESIDES ON UNSUPPORTED DEVICE REPLY STOP OR GO
Explanation: The warn data set has been incorrectly assigned
to a device or a volume not supported by the Power Warning
Feature Support. (For example: device assignment of IBM
2305 drum, or a volume assignment on the system residence
volume.
System Action: Waits for STOP or GO reply.
Operator Response: GO will cause the system to continue with
the Power Warning Feature Support inoperative. STOP will
cause a disabled wait (X'027').
Programmer Response: Allocate datasets on the appropriate
devices.
ICFTIM31
I/O ERROR READING SYSl.WARNx -- REPLY STOP
OR GO
Explanation: The status of this dataset cannot be determined
because of error conditions. It may contain a storage dump;
retrieval would require special actions by the user. This
message will always appear the first time after allocation
(unformatted data set).
System Action: Waits for STOP or GO reply.
Operator Response: GO will cause the system to erase and
format the dataset. STOP will cause a disabled wait (X'027').
Note: You should reply GO only if dataset has just been
allocated.
Programmer Response: It may be desirable to copy dataset
despite the error condition, or use other methods to extract
critical information. This dataset should be re-allocated to
avoid future problems.
ICFTIM32 I/O ERROR WRITING SYSl.WARNx -- REPLY STOP
OR GO
Explanation: Dataset cannot be formatted.
System Action: Waits for STOP or GO reply.
Operator Response: GO will cause the system to continue with
the Power Warning function inoperative. STOP will cause a
disabled wait (X'027').
Programmer Response: Re-allocate the dataset.
ICFTIM51 WARN WILL DUMP AT FIRST WARNING
Explanation: No time delay was specified at Sysgen.
System Action: Delay is no greater than that required by
engineering considerations.
Operator Response: None.
Programmer Response: Review appropriateness of a time
delay specification of one.
ICFTIM59 POWER WARNING FEATURE - INITIALIZATION
COMPLETE
Explanation: Power Warning Feature Warning Support has been
initialized.
System Action: Continue normal system activity with the
Power Warning Feature Support operative.
Operator Response: None.
Programmer Response: None.
ICFTIM97 INVALID STORAGE CONFIGURATION FOR RESTORE
Programmer Response:
Explanation: At restore time it is found that the storage
just before this one.
configuration is different than it was when main storage was
transferred to the warn data set.
System Action: Go to a disabled wait state with a code
X'027'.
Operator Response: Reconfigure storage exactly as it was
when main storage was transferred to the warn data set.
Programmer Response: None.
ICFTIM98 CORRECT PROBLEM AND RE-IPL
Explanation: This message is issued if the operator replied
STOP to message 1 through 97.
System Action: Go to a disabled wait state with code X'027'.
Operator Response: Explained in the message that printed just
before this one.
Explained in the message that printed
ICFTIM99 POWER WARNING FEATURE - FUNCTION
INOPERATIVE
Explanation: For reasons described in the preceding messages
to which the operator has replied GO, Power Warning Feature
Support has been deactivated. Receipt of a warning machine
check will not result in main storage being saved.
System Action: Continue normally without the Power Warning •
Feature Support.
Operator Response: None.
Programmer Response: None.
Section 2: Power Warning Feature Support Messages (lCF)
2·3
2-4
VS2 System Messages (VS2 Release 3.7)
Section 3: Virtual Storage Access Method Messages (IDA)
Component Name
IDA
Program Producing Message
VSAM (Virtual Storage Access Method)
Audience and Where' Produced
For programmer: SYSPRINT data set.
,
Message Format
sS,***IDAnnn text
ss
Severity code indicating effect of error one execution of the program being
assembled:
Warning message; successful execution is probable.
4
Error; execution may fail.
8
12 Serious error; successful execution is improbable.
nnn
Message serial number.
text
Message text.
Associated Publications
OS/VS Virtual Storage Access Method (VSAM) Programmer's Guide, GC26-3838
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IDA001
INVALID POSITIONAL PARAMETER, prm - IGNORED
Explanation: A positional parameter whose name is prm was
specified. The specified parameter is not valid.
System Action: The positional parameter is ignored and the
macro instruction is expanded normally. Severity code = 4.
Programmer Response: Probable user error. Correct the invalid
positional parameter and resubmit the job.
Problem Determination: Table I, items 15, 19, 22, 29.
IDA002
keywd KEYWORD REQUIRED - NOT SPECIFIED
Explanation: The required keyword indicated by keywd was
omitted.
System Action: The macro instruction is not expanded.
Severity code = 12.
Programmer Response: Probable user error. Provide the
required keyword and value and resubmit the job.
Problem Determination: Table I, items 15, 19, 22, 29.
IDA003
,INVALID VALUE, val, SPECIFIED FOR keywd
KEYWORD
Explanation: The indicated value specified for the indicated
keyword was invalid.
System Action: The macro instruction is not expanded.
Severity code = 12.
Programmer Response: Probable user error. Correct the invalid
value and resubmit the job.
Problem Determination: Table I, items 15, 19, 22, 29.
IDA004
keywd KEYWORD NOT VALID FOR EXECUTE FORM IGNORED
Explanation: The keyword indicated by keywd is not valid for
the execute form of the macro.
System Action: The keyword is ignored and the macro
instruction is expanded normally. Severity code = 4.
Programmer Response: Probable user error. Remove the
keyword from the execute form of the macro. The keyword
may be specified on the list form, which is referred to by the
execute form.
Problem Determination: Table I, items 15, 19, 22, 29.
IDA005
INVALID OR DUPLICATE SUBLIST ITEM FOR keywd
KEYWORD, xxx
Explanation: The sublist item whose name is xxx was specified,
but it is not valid or is duplicated for the keyword, keywd.
System Action: The macro instruction is not expanded.
Severity code = 8.
Programmer Response: Probable user error. Correct the invalid
or duplicated sublist item and resubmit the job.
Problem Determination: Table I, items 15, 19, 22, 29.
IDA006
keywd VALUE, val, NOT VALID FOR LIST FORM
Explanation: The indicated value specified for the keyword
whose name is keywd is not valid for the list form of the
macro.
System Action: The macro instruction is not expanded.
Severity code = 8.
Programmer Response: None.
Problem Determination: Table I, items 15, 19, 22, 29.
IDA007
LOGIC ERROR IN MACRO mac
Explanation: A logic error has occurred in the macro whose
name is mac.
System Action: The macro in:>truction is not expanded.
Severity code = 12.
Programmer Response: Probable system error. None.
Problem Determination: Table I, items 15, 19, 22, 29.
IDA008
INCOMPATIBLE SUBLIST ITEMS. xxx AND yyy, FOR
keywd KEYWORD
Explanation: The sublist items whose names are indicated by
xxx and yyy, which were specified for the keyword, keywd, are
incompatible.
~I
v'
Section 3: IDA Messages - VSAM
3-1
System Action: The macro instruction is not expanded.
Severity code = 12.
Programmer Response: Probable user error. Remove one of
the incompatible sublist items and resubmit the job.
Problem Determination: Table I, items 15, 19, 22, 29.
IDA009
nnn CONTROL BLOCK KEYWORDS SPECIFIED ONLY ONE ALLOWED
Explanation: On a TESTCB macro instruction, nnn control block
keywords were specified; only one is allowed.
System Action: The macro instruction is not expanded.
Severity code = 12.
Programmer Response: Probable user error. Remove all but
one of the control block keywords and resubmit the job.
Problem Determination: Table I, items 15, 19, 22, 29.
IDA010
EXIT ADDRESS REQUIRED FOR keywd KEYWORD NOT SPECIFIED
Explanation: An exit address required for the keyword, keywd,
was not specified.
System Action: The macro instruction is not expanded.
Severity code = 8.
Programmer Response: Probable user error. Supply the
required exit address and resubmit the job.
Problem Determination: Table I, items 15, 19, 22, 29.
IDA011
keywd IS NOT A VALID xxx KEYWORD - IGNORED
Explanation: The keyword keywd was specified, but it is not a
valid keyword for the xxx control block.
System Action: The invalid keyword is ignored and the macro
instruction is expanded normally. Severity code = 4.
Programmer Response: Probable user error. Remove the
invalid keyword and resubmit the job.
Problem Determination: Table I, items 15, 19, 22, 29.
IDA018
VTAM KEYWORD, keywd,.SPECIFIED WITHOUT
SPECIFYING AM = VTAM
Explanation: The VTAM keyword, keywd, was specified but is
not valid unless AM = VTAM is specified.
System Action: The macro instruction is not expanded.
Severity code = 12.
Programmer Response: Either remove the invalid keyword, or
specify AM = VTAM and resubmit the job.
Problem Determination Table I, items 15, 19, 22, 29.
IDA019
KEYWORDS keywd1 AND keywd2 ARE
INCOMPATIBLE
Explanation: The keywords, keywd 1 and keywd2, cannot be
specified together.
System Action: The macro instruction is not expanded.
Severity code
=
8.
Programmer Response: Correct the indicated error and rerun
the job.
Problem Determination Table I, items 15, 19, 22, 29.
3-2
VS2 System Messages (VS2 Release 3.7)
IDA020
VTAM SUBLIST ITEM, xxx, SPECIFIED FOR keywd
KEYWORD WITHOUT SPECIFYING AM - VTAM
Explanation: The VTAM sublist item xxx was specified for the
keyword, keywd, and is not valid unless AM - VTAM is
specified.
System Action: The macro instruction is not expanded.
Severity code == 12.
Programmer Response: Correct the indicated error and rerun
the job.
Problem Determination: Table I, items 15, 19, 22, 29.
IDA021
keywdl AND keywd2 KEYWORDS MUST BE
SPECIFIED TOGETHER BUT ONE IS MISSING
Explanation: Keywords keywd1 and keywd2 form a pair. One
cannot be specified without the other.
System Action: The macro instruction is not expanded.
Severity code = 8.
Programmer Response: Probable user error. Supply the
missing keyword or remove the one specified, and resubmit
the job.
Problem Determination: Table I, items 15, 19, 22, 29.
IDA022
CONFLICTING SUBLIST ITEMS WERE SPECIFIED FOR
keywd KEYWORD
Explanation: The keyword, keywd, has been specified with
conflicting sublist items.
System Action: The macro instruction is not expanded.
Severity code = 12.
Programmer Response: Correct the sublist item or items that
are in conflict, and resubmit the job.
Problem Determination: Table I, items 15, 19, 22, 29.
IDA024
keywd, A VSAM KEYWORD SPECIFIED FOR A
NON-VSAM CONTROL BLOCK
Explanation: The keyword keywd is a VSAM keyword but is
being specified for a non-VSAM control block.
System Action: The macro instruction is not expanded.
Severity code = 12.
Programmer Response: Probable user error. Correct the
indicated error and resubmit the job.
Problem Determination: Table I, items 2, 15, 19, 22, and 29.
IDA025
www,xxx,yyy CONFLICTING SUBPARAMETERS IN
keywd KEYWORD, www ASSUMED
Explanation: In the keyword keywd the subparameters
www,xxx,and yyy are conflicting. Only one may be specified.
System Action: The macro instruction is expanded using www
as the default. Severity code = 12.
Programmer Response: Probable user error. Specify no more
than one of the conflicting subparameters and resubmit the
job.
Problem Determination: Table I, items 2, 15, 19, 22, and 29.
VS2.03.S0S
Section 4: Access Method Services Messages (InC)
Component Name
IDC
Program Producing Message
Access Method Services
Audience and Where Produced
For programmer: SYSPRINT data set.
Message Format
I DCnnnns ** text
IDCnnnnns ** text
nnnn or nnnnn
Message serial number the first digit of which is a condition code that indicates the severity of the
problem:
Onnn or Onnnn Informational message; no effect on execution.
1nnn or 1nnnn Warning message; no effect on execution.
2nnn or 2nnnn Error; execution may fail.
3nnn or 3nnnn Serious error; successful execution is improbable.
4nnn or 4nnnn Terminal error; successful execution is impossible.
s
Type code:
A
Action; operator must perform a specific action.
D
Decision; operator must choose alternative.
E
Eventual action; operator must perform action when he has time.
I
Informational message.
W Wait; processing stopped until action is determined and performed.
** Indicates a second-level message that further explains a preceding message.
text
Message text.
Associated Publications
OS/VS Virtual Storage Access Method (VSAM) Programmer's Guide, GC26-3838
OS/VS2 Access Method Services, GC26-3841
OS/VS Mass Storage System (MSS) Services for Space Managl;lment, GC35-0012
OS/VS Mass Storage System (MSS) Services for Recovery, GC35-0015
OS/VS2 Catalog Management Logic, SY26-3826
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IDC083E
csn [csn] EJECTED;VOL volser - jjj sss
Explanation: One or both cartridges assigned to the Mass
Storage Volume identified by 'volser' were ejected from the
Mass Storage Facility. The message identifies:
• The cartridge serial numbers of the sequence one and/or
sequence two cartridges ('csn').
• The volume serial number ('volser') of the Mass Storage
Volume.
• The jobname ('jjj') and stepname ('sss') associated with the
eject request.
Operator Response: Remove the ejected cartridge or cartridges
from the cartridge access station of the Mass Storage Facility.
Programmer Response: None.
jjj.sss 3850 DEMOUNT FAILED,VOL = VVvvvv,vua,
RC = X'cde'
Explanation: The system was unable to demount the virtual
volume requested in step sss of job jjj. See message text for
virtual volume serial and virtual (vua) unit address. Refer to
mass storage system (MSS) messages for an explanation of
the reason codes (RC).
System Action: Processing continues.
Operator Action: Fix the problem indicated by the reason code
(RC). Then issue the "UNLOAD" command.
IDC3941
System ACtion: Processing continues.
Operator Response: Remove the scratched cartridge from the
Cartridge Access Station and label it as a scratch cartridge,
IDC79tE
REPLACED CARTRIDGE
EJECTED; jjj sss
csn I UNIDENTIFIED
Explanation: The cartridge serial number (csn) identifies an
ejected cartridge. An old or defective cartridge of a Mass
Storage Volume is ejected from the Mass Storage Facility
(MSF) after being replaced with a different cartridge. The
jobname (jjD and the stepname (sss) identify the job
associated with the ejected cartridge.
If the cartridge was ejected, the replacement failed and the
system failed to read the base volume record. The csn could
not be identified. Messages IDC20S01 and IDC24001 will
following this message indicating that the base volume could
not be read.
System Action: Processing continues.
Operator Response: Remove the cartridge from the Cartridge
Access Station and label it as an old or defective cartridge.
IDCOOOtl
FUNCTION COMPLETED, HIGHEST CONDITION
CODE WAS cde
Explanation: A scratch cartridge was ejected from the Mass
Explanation: This message is issued by any functional
command upon its completion. If some error has occurred, the
condition code is not O. If an error has occurred, it will be
indicated by error messages that precede the comp'3tion
Storage Facility (MSF). The message identifies the cartridge
serial number (csn) of the cartridge ejected plus the jobname
(jjD and the stepname (sss) associated with the ejected
cartridge.
System Action: LASTCC is set to cde, MAXCC is also set if
cde is greater than the current MAXCC value.
Programmer Response: None.
IDC783E
SCRATCH CARTRIDGE csn EJECTED; jjj 555
messa~e.
Section 4: IDC Messages· Access Method Services
4·1
IDC00021
IDCAMS PROCESSING COMPLETE. MAXIMUM
CONDITION CODE WAS cde
Explanation: This message is issued at the completion of the
job step.
System Action: The highest condition code (MAXCC) set
during the step is printed and returned to the caller in register
15.
Programmer Response: None.
IDC00051
NUMBER OF RECORDS PROCESSED WAS nnn
Explanation: This is an informational message indicating the
number of records that were processed in the execution of the
REPRO or PRINT command.
System Action: If input records were selectively processed,
nnn number will include only those actually processed. If the
condition code is 0, then all records were processed. If the
condition code is 4, then some of the records will not have
been processed, 'COUNT' need not be specified for this
situation to occur. For partial data set processing, the user
must be familiar with the contents of the data set to tell why
the condition code of 4 occurred.
Programmer Response: This message might indicate that no
records were processed, which could be an error.
IDC00141
LASTCC = cde
Explanation: This message is issued whenever a non-zero
condition code is returned by any functional command upon its
completion. The error or errors causing the condition code to
be greater than 0 are indicated by error messages that
precede this message. Possible values of the condition code,
cde, and their meanings are:
4 Warning message; successful execution is probable.
8 Serious error, but processing is completed.
12Terminating error; processing of the command is
terminated.
System Action: Processing is completed or terminated
depending on the condition code.
Programmer Response: Correct the cause of the error and
rerun the job.
IDC00601
CARTRIDGE csn EJECTED
Explanation: Either a scratch cartridge or an old or defective
data cartridge was ejected from the Mass Storage Facility.
System Action: The command continues processing.
Programmer Response: None.
IDC00631
CARTRIDGE LABELS AND INVENTORY RECORD
RESTORED
Explanation: The cartridge labels and Inventory data set are
restored to original status because an error was encountered
while relabeling a Mass Storage Volume.
System Action: The command continues processing.
Programmer Response: Take the following action for the
command that failed:
• If a Rename Operation Failed for ADDV
Run ADDV to backout or retry the rename operation if the
volume is inactive. If the volume is active, run MODIFYV or
STOREY to either backout or retry the rename operation.
If the ADDV, MODIFYV, or STOREY commands are run to
recover from a rename failure, a DD statement for the
volume is required and must specify deferred mounting.
The values specified for the VOLUME and NEWSERIAL
parameters depend upon how the volume record is recorded
4-2
VS2 System Messages (VS2.03.S0S)
in the Inventory data set. If the cartridge labels have been
updated, the volume record will be identified by the new
volume serial number. For the VOLUME parameter, specify
the volume serial number as recorded in the cartridge labels
and the volume record. For the NEWSERIAL parameter,
specify the desired volume serial number. Note that the
security check for nonVSAM status and password protected
data sets is bypassed only if the NEWSERIAL parameter
specifies the same volume serial number as recorded in the
Inventory data set for the volume label. This allows the
original volume serial number of a VSAM volume to be
restored if the volume is left partially renamed.
If ADDV, MODIFYV, or STOREY terminates without indicating
the status of the rename operation, LlSTMSVI can be run to
determine whether the volume is flagged for recovery
purposes. If the mismatch flag is set in the volume record,
LlSTMSVI not only lists the standard information for the
volume but also highlights the volume report with a note
that a rename operation failed for the preceding volume and
that serial number 'nnnnnn' is recorded in the volume label
of the volume.
• If a Rename Operation Failed for MODIFYV
To recover from a MODIFYV rename failure 1) run ADDV to
activate the volume if the volume is merely inactive and has
no volume serial mismatch condition, or 2) run ADDV to
both activate the volume and complete the rename
operation if the volume is both inactive and has a volume
serial mismatch condition, or 3) rerun MODIFYV to complete
or retry the rename operation if the volume is active but
has a mismatch condition, or 4) run STOREY to complete or
retry the rename operation if the volume is active and if a
duplicate volume serial number is desired as a result of the
rename.
For the DD statement requirements, the proper VOLUME
and NEWSERIAL parameter values, and use of LlSTMSVI,
refer to the description above for an ADDV rename failure.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, 35a
and 35c.
IDC00641
[SERIAL I OWNER I SERIAL, OWNER] UPDATED IN
CARTRIDGE LABELS AND INVENTORY RECORD
Explanation: Either the volume serial number or owner name
or both was updated in the label of the Data Cartridges
assigned to the Mass Storage Volume and in the volume
record in the Inventory data set. However, the data may not
yet be updated in the software volume label.
System Action: The command continues processing.
Programmer Response: None.
IDC006S1
n BACKUP COPIES EXIST BEYOND MAXIMUM
BACKUP
Explanation: The number indicated by 'n' identifies the number
of backup copies that exceed the backup number specified
through the use of the CREATEV or MODIFYV command.
System Action: The command continues processing.
Programmer Response: The excess backup copies can be
scratched by:
• The next COPYV command executed to create a new
backup copy; the oldest backup copies will be scratched, or
• The SCRATCHY command executed for each backup copy
to be scratched.
IDC00731
VOLUME ATTRIBUTES -CHANGED TO AGREE WITH
GROUP groupname
Explanation: The attributes (bind/nobind, readonly/readwrite,
dasderase/nodasderase, exclusive/shared) of a general-use
volume were changed to match the attributes defined at the
group level for all general-use volumes belonging to the group.
If the user did not explicitly request the attribute change, the
attributes are changed implicitly because:
• The volume is being assigned to a different group
• A volume that does not belong toa group is being assigned
to a group, or
• The group level attributes were changed while a general-use
volume was inactive and is now being activated.
System Action: The command continues processing.
Programmer Response: None.
IDC00851
CARTRIDGES csn [csn] EJECTED
volumes in the inventory data set. A reason code of X'20S' or
X'223' was returned from the Mass Storage Volume Control
functions.
System Action: The command terminates.
Programmer Response: None.
IDCOI041
NO ACTIVE VOLUMES IN THE INVENTORY DATA
SET
Explanation: Either there are no base volume records in the
Inventory data set, or there are no base volume records with
the active flag on in the Inventory data set. A reason code of
X'20S' or X'223' was returned from the Mass Storage Volume
Control functions.
System Action: The comm~nd terminates.
Programmer Response: None.
IDCOI051
NO ACTIVE VOLUMES IN GROUP grpname
Explanation: The cartridge(s) assigned to a Mass Storage
Explanation: Either there are no mass storage volumes in the
Volume were ejected from the Mass Storage Facility. A single
cartridge serial number (csn) identifies the sequence one or
sequence two cartridge successfully ejected. If both cartridges
are in the Mass Storage Facility and are ejected, the cartridge
serial numbers of the sequence one and sequence two
cartridges are listed respectively.
System Action: The command continues processing.
Programmer Response: None.
group grpname, or there are no base volume records with the
active flag on in the group.
System Action: If any groups remain to be processed,
processing continues with the next group. Otherwise, the
command terminates.
Programmer Response: None.
IDC00861
[SERIAL I OWNER
VOLUME LABEL
I
SERIAL, OWNER] UPDATED IN
Explanation: Either the volume serial number or owner name
or both was changed in the volume label as requested.
System Action: The command continues processing.
Programmer Response: None.
IDC00881
CARTRIDGES esn [esn] SCRATCHED FOR COpy
yyddd
Explanation: The cartridges assigned to the copy volume
created on the date indicated by 'yyddd' were successfully
scratched. If only one cartridge was in the MSF, the single
cartridge serial number (csn) identifies the sequence one or
sequence two cartridge that was scratched. If both cartridges
were in the Mass Storage Facility, both cartridges were
scratched and the cartridge serial numbers of the sequence
one and sequence two cartridges are listed respectively.
System Action: The command continues processing.
Programmer Response: None.
IDC00981
**
LOCATION OF VOLUME: location
Explanation: The location information recorded in the Inventory
data set for the cartridges assigned to the Mass Storage
Volume is listed. See the preceding message for the cartridge
serial numbers of these cartridges.
System Action: The command terminates with an error
message unless additional volumes have been specified for
processing.
Programmer Response: Insert the missing cartridges when the
Mass Storage Volume Control portion of the Mass Storage
System Communicator is enabled, and rerun the command. If
the cartridges assigned to the volume are lost, use the
REMOVEVR command to delete the volume record from the
Inventory data set before rerunning the command.
IDCOI021
IDCOI061
NO ACTIVE GENERAL USE VOLUMES IN GROUP
grpname
Explanation: Either there are no mass storage volumes in
group grpname, or there are no base volume records in the
Inventory data set in the group with both the active and
general-use flags on.
System Action: If any groups remain to be processed,
processing continues with the next group. Otherwise, the
command terminates.
Programmer Response: None.
IDCOI071
NO DATA SETS ELIGIBLE FOR SELECTION ON
VOLUME ser
Explanation: No data sets on volume ser met the criteria
specified ,on the command for either listing or scratching.
System Action: If there are more volumes to be processed,
the next volume is processed. Otherwise, the command
terminates.
Programmer Response: None.
IDC01121 dsn SCRATCHED
Explanation: The data set dsn was successfully scratched from
the VTOC.
System Action: If other data sets remain to be scratched,
processing continues with the next data set. Otherwise, the
command terminates.
Programmer Response: None.
IDC02041
PRECEDING COMMAND BYPASSED DUE TO
CONDITION CODES
Explanation: The modal command structure specification
caused the command to be bypassed.
System Action: The command is checked for syntactic errors,
but not executed.
Programmer Response: None.
Problem Determination: Table I, item 4, 29.
NO ACTIVE NON-GROUPED VOLUMES IN THE
INVENTORY DATA SET
Explanation: There are no nongrouped, active mass storage
Section 4: IDC Messages - Access Method Services
4-3
•
•
IDC02061
IMPROPERLY PLACED COMMA HAS BEEN FOUND
AND IGNORED
Explanation: An unneeded comma has been coded; omitted
positional parameters may not be denoted by consecutive
commas.
System Action: The usage .isaccepted and the extraneous
comma is ignored.
Programmer Response: Remove the extra comma.
Problem. Determination: Table I, item 4, 29.
IDC02221
WARNING: COMMAND-END DELIMITER APPEARS
WITHIN APOSTROPHES
A semicolon,
the optional command delimiter, has
been found in an item that is enclosed within apostrophes. A
closing apostrophe may have been omitted.
System Action: The usage is accepted and processing
continues, treating the semicolon as a valid character.
Programmer Response: Insert the missing apostrophe, if one
was omitted, al;ld rerun the job.
Problem Determination: Table I, item 4, 29.
Explanation:
IDC02331
TOO MANY RIGHT PARENTHESES FOUND. EXCESS
IGNORED
Explanation: Too many right parentheses have been found at
the end of a subparameter list or following a first-level
.
parameter.
System Action: The excess parentheses are ignored and
scanning continues.
Programmer Response: Correct the invalid syntax.
Problem Determination: Table I, item 4, 29.
IDC02341 WARNING: TOO FEW RIGHT PARENTHESES FOUND
. AT END OF COMMAND
Explanation: Too few right parentheses have been found at thE
end of the command to properly close off the subparameter
lists.
.
System Action: The usage is accepted and processing
continues.
Programmer Response: Correct the invaUd syntax.
Problem Determination: Table I, item 4, 29.
IDC03611
**
dsn NOT LOCATEP
Explanation: The VSAM or OS locate request for data set dsn
was unsuccessful. A preceding message indicates the reason
for the failure.
System Action: If the SCRDSET command is being run, this
data set is not scratched. If the LlSTDSET command is being
run, this data set is listed unless the UNCATALOGED,
EXPIRATION DATE, EXPIRATION, CREATION DATE, or CREATION
parameter is specified.
Programmer Response: Determine why the data set was not
located, correct the problem if necessary, and rerun the
command.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, and
34.
IDC03621
**
dsn NOT SCRATCHED
Explanation: An error occurred during a VSAM delete request.
The error prevented the data set dsn from being scratched. A
preceding message explains the type of error.
System Action: The command continues to scratch and
uncatalog remaining eligible- data sets.
Programmer Response: Correct the error identified in the
preceding message and do one of the following:
• Rerun the SCRDSET command.
4-4
VS2 System Messages (VS2 Release 3.7)
• Specify DELETE in the DISP parameter on the DD statement
to scratch the data set.
• Run the DELETE command to scratch the data set.
Problem Determination: Table I, items 1, 2, 3, 4, 9, 13, 25a,
29, and 34a.
IDC03631
**
dsn NOT UNCATALOGED .
Explanation: One of the following situations occurred:
• An error occurred during a VSAM del,ete request.
The error prevented data set dsn from being uncataloged.
A preceding message explains the error.
• An error occurred during an OS uncatalog request.
The error prevented data set dsn from being uncataloged.
A preceding message explains the error.
• An error occurred during the scratch of data set dsn.
Because the data set cannot be scratched, no atternpt was
made to uncatalog th~ data set.
'System Action: The command continues to scratch and
uncatalog remai.ning eligible data sets.
Programmer Response: Correct the error identified in the
preceding message. If the data set was already scratched from
the VTOC, do one. of the following:
• Specify UNCATLG in the DISP parameter on the DD
statement to uncatalog the data set.
• Run the DELETE command to uncatalog the data set.
• Run the IEHPROGM utility to uncatalog the data set.
If the data set was not scratched from the VTOC, do one of
the following:
• Rerun the SCRDSET command.
• Specify DELETE in the DISP parameter on the DD statement
to scratch the data set.
• Run the DELETE command to scratch the data set.
• Run the IEHPROGM utility to scratch and uncatalog the data
set.
Problem Determination: Table I, items 1, 2, 3, 4, 9, 13, 25a,
29, an@ 34a.
IDC03961
**
dsn NOT RECATALOGED
Explanation: The data set (dsn) was not recataloged. See
preceding message for the reason.
System Action: The command continues processing.
Programmer Response: Examine the preceding message for
response.
IDC03971
DATA SET CATALOGED IN VSAM CATALOG THAT
DOES NOT OWN VOLUME
Explanation: The data set identified in the subsequent
message was located in a VSAM catalog that does not own the
volume. VSAM catalog management does not support altering
device type and volume serial number in VSAM catalogs other
than the owning catalog.
System Action: The command continues processing.
Programmer Response: Use the Access Method Services
LlSTCAT, DELETE, and DEFINE commands to determine the
fields defined in the entry, delete the entry, and redefine the
entry ,with the new device type.
Problem Determination: Table I, item 1, 2, 3, 4, 13, 14, 25b,
29, and 31.
IDC03981
DATA SET RESIDES ON MORE THAN TWENTY
VOLUMES
Explanation: The data set identified in the subsequent
message resides on more than twenty volumes, and as far as
the program can tell, it has not already been recataloged.
Recataloging is not supported by this program if the data set
resides on more than 20 volumes. If the data set is cataloged
in the VSAM owning catalog, it has already been recataloged.
If the data set is not cataloged at all, this message should be
ignored.
System Action: The command continues processing.
Programmer Response: Use IEHPROGM utility or Access
Method Services DELETE and DEFINE command to recatalog
the data set if it is cataloged and not already recataloged.
Problem Determination: Table I, item 1, 3, 4, 13, 14, 2Sd, 29,
and 31.
IDC05081
DATA ALLOCATION STATUS FOR VOLUME ser IS rc
Explanation: This message indicates the allocation status fr a
volume containing the data component. The code indicating
the status is the VSAM catalog return code; a 0 indicates
success.
System Action: Processing continues.
Programmer Response: See message IDC30091 for a complete
explanation of rc.
IDC05091
INDEX ALLOCATION STATUS FOR VOLUME ser IS rc
Explanation: Tilis message indicates the allocation status for a
volume containing the index component. The code indicating
the status is the VSAM catalog return code; a 0 indicates
success.
System Action: Processing continues.
Programmer Response: See message IDC30091 for a complete
explanation of rc.
IDC05101
'~
I
CATALOG ALLOCATION STATUS FOR VOLUME ser
IS rc
Explanation: This message indicates the allocation status of a
volume containing the VSAM catalog. The code indicating the
status is the VSAM catalog return code; a 0 indicates success.
System Action: Processing continues.
Programmer Response: See message IDC30091 for a complete
explanation of rc.
IDC051l1
SPACE ALLOCATION STATUS FOR VOLUME ser IS rc
Explanation: This message indicates the allocation status for a
volume on which VSAM space is being defined. The code
indicating the status is the VSAM catalog return code; a 0
indicates success.
System Action: Processing continues.
Programmer Response: See message IDC30091 for a complete
explanation of rc.
IDC05121
NAME GENERATED - (x) dsn
Explanation: This is an informational message. Data and index
component names are generated by VSAM catalog
management, when these names have not been specified. The
parenthesized character ('D' or '1') indicates which component
dsn names.
System Action: Processing continues.
Programmer Response: None.
IDC05201
CATALOG RECOVERY VOLUME IS ser
Explanation: This is an informational message indicating the
volume serial number of the volum.e that contains and will
contain all catalog recovery data for the object just defined.
System Action: Processing continues.
Programmer Response: The named volume should be mounted
for any future operation that modifies the catalog entry for the
object just defined.
IDC05261
ALTERED ALLOCATION STATUS FOR VOLUME ser IS
rc
Explanation: This is an informational message indicating the
allocation status of volumes. being added or removed from a
VSAM data set. The code indicating the status is the VSAM
catalog return code (see message IDC30091).
System Action: Processing continues.
Programmer Response: None.
IDC05311
ENTRY xxx ALTERED
Explanation: This message indicates that the specified entry
has been successfully altered.
System Action: Processing continues.
Programmer Response: None.
IDC05321
**
ENTRY xxx NOT ALTERED
Explanation: This message indicates that the entry was not
altered.
System Action: The preceding message in the system output
indicates the reason the entry was not altered. Processing
continues.
Programmer Response: Correct the problem indicated by the
previous message, and reenter the command.
IDC05341
**
MEMBER mem NOT RENAMED
Explanation: This is an informational message indicating the
member name that was not renamed.
System Action: The preceding message in the system output
indicates the reason the member name was not renamed.
Processing continues.
Programmer Response: Correct the problem indicated by the
previous message, and reenter the command.
IDC05351
MEMBER mem RENAMED
Explanation: The indicated member has been successfully
renamed.
.
System Action: Processing continues.
Programmer Response: None.
IDC05481
**
MEMBER mem NOT DELETED
Explanation: This is an informational message only, issued to
inform the operator or programmer the member mem was not
deleted.
System Action: An associated message accompanies this
message indicating why the member was not deleted.
Processing continues.
Programmer Response: None.
IDC05491
MEMBER mem DELETED
Explanation: This is an informational message only, indicating
the member that has been successfully deleted.
System Action: Processing continues.
Programmer Response: None.
IDC05501
ENTRY (x) dsn D"ELETED
Explanation: The specified dsn (data set name) entry was
deleted from the VSAM catalog. x indicates the type of entry:
C--cluster, D--data, G--alternate index, I--index, R--path,
V--volume, U--user catalog; M--master catalog,
A--non-VSAM, B--GDG base, X--alias.
System Action: A volume entry is deleted only when the
volume no longer contains any data spaces. This is an
informational message only. Processing continues.
Programmer Response: None.
Section 4: IDC Messages - Access Method Services
4-5
I
••
**
IDC05511
ENTRY dsn NOT DELETED
Explanation: This message indicates the entry that was not
deleted. An accompanying message will indicate why the entry
was not deleted.
System Action: The named dsn is not deleted.
Programmer Response: Correct the cause of nondeletion.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC05551
DELETION OF SPACE OBJECT DID NOT CAUSE ser
TO BE DELETED
Explanation: When a DELETE command is executed against
volume ser and the FORCE parameter is not specified, all
empty data spaces are deleted; data spaces that still contain
dah set segments are not deleted. Only when all data spaces
on a volume are deleted or when FORCE is specified, is that
volume deleted from its owning catalog.
System Action: The volume is still owned by the catalog in
which it was originally defined.
Programmer Response: None.
IDC06261
IMPORTRA SUCCEEDED FOR data set name
Explanation: The object named as "data set name" has been
successfully imported.
System Action: Normal proceSSing continues.
Programmer Response: None.
IDC06341
NUMBER OF ENTRIES CONVERTED WAS nnn
Explanation: The number of OS catalog entries successfully
converted into entries in the VSAM catalog is indicated.
System Action: Processing continues.
Programmer Response: None.
IDC06351
**
dsn NOT CONVERTED
Explanation: The OS catalog entry specified was not
converted.
System Action: An associated message accompanies this
message containing the information required to correct the
error. Processing continues.
Programmer Response: None.
IDC05711 CATALOG RELOAD HAS BEEN INVOKED
IDC06361
A REPRO command has been executed where the
target data set is a catalog. This message marks the beginning
of processing of a catalog reload operation.
System Action: Processing continues.
Programmer Response: None
Explanation: The number of non-VSAM entries whose volume
Explanation:
IDC05941
PORTABLE DATA SET CREATED SUCCESSFULLY ON
date AT hh:mm:ss
Explanation: At this point, the portable data set contains all
information necessary to re-create the cluster being exported.
System Action: ProceSSing continues.
Programmer Response: None.
IDC06031 CONNECT FOR USER CATALOG dsn SUCCESSFUL
Explanation: This message identifies the name of the catalog
for which CONNECT completed successfully.
System Action: ProceSSing continues.
Programmer Response: None.
IDC06041
DATA SET BEING IMPORTED WAS EXPORTED ON
date AT hh:mm:ss
Explanation: This informational message gives the date and
time that the data set was exported.
System Action: ProceSSing continues.
Programmer Response: None.
IDC0611I DATA SET TO BE IMPORTED ALREADY EXISTS DELETE ATTEMPTED
Explanation: A catalog define was attempted for the data set
to be imported; it failed because an entry with that name
already existed in the catalog. This situation occurs when a
temporarily exported data set is imported back into the catalog
from which it was exported.
System Action: An attempt is made to delete the existing
entry. The message following this message in the listing
indicates whether the delete was successful.
Programmer Response: None.
IDC06221
USERCATALOG catname DISCONNECTED
A user catalog has been disconnected by
IMPORTRA in order to connect a new pointer to the user
catalog.
System Action: ProceSSing continues.
Programmer Response: None.
Explanation:
4-6
VS2 System Messages (VS2 Release 3.7)
NUMBER OF ENTRIES UPDATED WAS nnn
information has been updated is indicated.
Volume information of a non-VSAM entry is updated when the
volume information of a duplicate entry being converted from
the OS source catalog is different from that of the existing
non-VSAM entry.
System Action: Processing continues.
Programmer Response: None.
IDC06371
**
dsn NOT UPDATED
Explanation: This is an informational message only. The OS
catalog entry specified was not converted.
System Action: An accompanying message contains the
information required to correct the error. Processing continues.
Programmer Response: None.
IDC06521
dsn SUCCESSFULLY BUILT
Building of the alternate index identified by dsn
has been successfully completed with no errors encountered.
System Action: Processing continues.
Programmer Response: None.
Explanation:
IDC06651
NUMBER OF ENTRIES THAT MISCOMPARED IN THIS
CRA - nn
Explanation: The COMPARE option was requested and this
informational message indicates the number, nn, of entries
(volume, cluster, alternate index, nonVSAM, and/or user
catalog entries) for which a miscompare between the catalog
recovery area (CRA) and catalog occurred.
System Action: Processing continues.
Programmer Response: Determine whether recovery is
requi~ed. For more information on catalog recovery, see
OS /VS2 Access Method Services.
•
IDC06691
EXPORTING FROM CRA ON VOLUME ser
Explanation: This is an informational message indicating the
current catalog recovery area (CRA) and volume being used to
export the data set(s) named in the following message(s).
System Action: Processing continues.
Programmer Response: None.
IDC06701
DATA SET SUCCESSFULLY EXPORTED
Explanation: The data set named in message IDC06741 was
successfully retrieved and written to the portable data set.
r1
\~
System Action: Processing continues.
Programmer Response: None.
IDC06721
**
LOCKED ON CATALOGcatname
Explanation: This is an informational message providing the
name of the owning catalog whose CRAs will be processed. It
is the name of the catalog owning the first CRA processed.
System Action: Processing continues.
Programmer Response: None.
IDC06741
**
NAME IS dsname
Explanation: This second-level informational message gives
the data set name of the object referred to in the preceding
message(s).
System Action: See the primary message.
Programmer Response: See the primary message.
IDC06761
PORTABLE DATA SET CREATED SUCCESSFULLY ON
date AT time
Explanation: This is an informational message indicating the
portable data set contains the necessary information to
recreate the data set(s) via IMPORTRA.
System Action: Processing continues.
Programmer Response: None.
IDC06801
VOLUME volser CREATED ON CARTRIDGES csnl
csn2
Explanation: A 'new volume was created. The message
identifies the cartridge serial number (csnl and csn2) of the
cartridges used and volume serial (volser) assigned.
System Action: The command continues processing.
Programmer Response: None.
IDC06861
PARTIALLY CREATED VOLUME volser SCRATCHED
Explanation: The partially created volume (volser) was
scratched during back out because an error occurred.
System Action: The command terminates normally.
Programmer Response: Correct the error indicated in a
preceding message and rerun the command.
IDC07031
** VOL volser COPIES TO CART csnl csn2, DATE
yyddd
Explanation: The volume (volser) was copied to the cartridges
(csnl and csn2) on the date indicated by 'yyddd'.
System Action: Processing continues.
Programmer Response: None.
IDC07041
** CARTRIDGES OF OLDEST BACKUP COPY yyddd
SELECTED FOR REUSE
Explanation: The COPYV command selected the cartridges of
the oldest backup copy volume indicated by the date 'yyddd'
for reuse. The preceding message describes the status of the
new copy volume.
System Action: Processing. continues.
Programmer Response: None.
IDC07051
** CARTRIDGES OF AN INCOMPLETE COpy
VOLUME SELECTED FOR REUSE
Explanation: Due to a previous failure by the COPYV
command, the cartridges of an incomplete copy volume were
reused by the command. The preceding message identifies the
status of the new copy volume.
System Action: Continue processing.
Programmer Response: None.
IDC07111
** VOLUME volser RESTORED FROM COPY VOLUME
volser, COPY DATE yyddd
Explanation: The designated volume (volser) was successfully
restored using either the latest backup copy or a user
designated copy 'volser' created on the date indicated by
'yyddd'. However, if the target volume serial number is
different than the copy volume, the target volume serial
number was overwritten during the copy operation and must
be restored. The target volume is currently flagged as an
incomplete copy in the Inventory data set. The command will
restore the volume label and clear the incomplete copy flag
from the Inventory data .set before processing of the command
terminates.
System Action: Processing continues.
Programmer Response: No'ne.
IDC07221
VOLUME volser HAS BEEN ACTIVATED
Explanation: The inactive volume indicated by 'volser' was
made active but either the volume attributes could not be
updated or the volume serial could not be changed.
System Action: Processing continues.
Programmer Response: Run the MODIFYV command to change
the volume attributes or the volume serial number of the
active volume.
IDC07241
** SERIAL NUMBER OF VOLUME volser NOT
CHANGED
Explanation: The volume (volser) has been activated but the
volume serial number could not be changed. See the preceding
message for further explanation of the error.
System Action: Correct the problem as indicated in the
preceding message.
Programmer Response: Run the MODIFYV command to change
the volume serial number of the active volume.
IDC07251
READWRITE ATTRIBUTE SET FOR VOLUME volser
Explanation: The volume (volser) is assigned the readwrite
attribute as requested.
System Action: Processing continues.
Programmer Response: None.
IDC07311
VOLUME volser HAS BEEN MADE INACTIVE
Explanation: The designated volume (volser) was successfully
deactivated and made non mountable.
System Action: Processing continues.
Programmer Response: None.
IDC07331
VOLUME LABEL RESTORED TO ORIGINAL STATUS
Explanation: The volume label is restored to its original status
because the volume cannot be deactivated nor the volume
serial number changed in the cartridge labels. A flag in the
Inventory data set, indicating a mismatch between the volume
label and cartridge labels, will remain set only if the flag was
previously set from an earlier relabel failure by the MODIFYV,
ADDV, or STOREY command.
Sy~tem Action: The command terminates with an error
message.
Programmer Response: Take one of the following actions for
the command that failed:
• If a Rename Operation Failed for ADDV
Run ADDV to backout or retry the rename operation if the
volume is inactive. If the volume is active, run MODIFYV or
STOREY to either backout or retry the rename operation.
If the ADDV, MODIFYV, or STOREY commands are run to
recover from a rename failure, a DO statement for the
volume is required and must specify deferred mounting.
Section 4: IDC Messages - Access Method Services
4-7
The values specified for the VOLUME and NEWSERIAL
parameters depend upon how the volume record is recorded
in the Inventory data set. If the cartridge labels have been
updated, the volume record will be identified by the new
volume serial number. For the VOLUME parameter, specify
the volume serial number as recorded in the cartridge labels
and the volume record. For the NEWSERIAL parameter,
specify the desired volume serial number.. Note that the
security check for nonVSAM status and password protected
data sets. is bypassed only if the NEWSERIAL parameter
speci~ies the same volume serial number as recorded in the
Inventory data set for the volume label. This allows the
original volume serial number of a VSAM volume to be
restored if the volume is left partially renamed.
If ADDV, MODIFYV, or STOREY terminates without indicating
the status of the rename operation, LlSTMSVI can be run to
determine whether the volume is flagged for recovery
purposes. If the mismatch flag is set in the volume record,
LlSTMSVI not only lists the standard information for the
volume but also highlights the volume report with a note
that a rename operation failed for the preceding volume and
that serial number 'nnrinnn' is recorded in the volume label
of the volume.
• If a Rename Operation Faile!:! for MODIFYV
To recover from a MODIFYV rename failure 1) run ADDV to
activate the volume if the volume is merely inactive and has
no volume serial mismatch condition, or 2) run ADDV to
both activate the volume and complete the rename
operation if the volume is both inactive and has a volume
serial mismatch condition, or 3) rerun MODIFYV to complete
or retry the rename operation if the volume is active but
has a mismatch condition, or 4) run STOREY to complete or
retry the rename operation if the volume is active and if a
duplicate volume serial number is desired as a result of the
rename.
For the DO statement requirements, the proper VOLUME
and NEWSERIAL parameter values, and use of LlSTMSVI,
refer to the description above for an ADDV rename failure.
• If a Rename Operation Failed for STOREY
Rerun STOREY or run MODIFYV to either backout or retry
the rename operation.
For the DO statement requirements, the proper VOLUME
and NEWSERIAL parameter values, and use of LlSTMSVI,
refer to the description above for an ADDV rename failure.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, 35a,
and 35c.
IDC07371
FURTHER PROCESSING TERMINATED
Explanation: An error occurred which prevents any further
processing. Preceding messages indicate the extent of the
processing which has been completed. Functions which may
not be completed are:
• Updating the alternate track information in the VTOC of the
TO volume.
• If the volume is VSAM, updating the timestamp in the VTOC
of the TO volume.
• If the FROM and TO volume serial numbers are different,
updating the serial number in the label of the TO volume.
• Updating the owner in the label of the TO volume.
• If a recatalog option was specified or defaulted to,
recataloging the data sets.
• If the scratch option was specified or defaulted to;
scratching the data sets on FROM volume.
Fot conversion from a 3336 Model I Disk Pack to a mass
storage volume, the incomplete copy flag is set in the
Inventory data set for any of the following cases:
4-8
VS2 System Messages (VS2 Release 3.7)
• The FROM and TO volume serial numbers are not the same,
and processing terminated during the copy operation.
• The FROM and TO volume serial numbers are not the same,
and processing terminated before the VTOC and volume
label were updated.
• The TO volume is VSAM· and processing terminated before
the VSAM recataloging was completed.
System Action: The command terminates with an error
message indicating the severity of the problem.
Programmer Response: If the incomplete copy flag is on in the
Inventory data set, rerun the CONVERTV command, recover
from a copy volume using the RECOVERV command, or scratch
the Mass Storage Volume using the SCRATCHY command.
Otherwise, you can decide whether to rerun the CONVERTV
command or to complete the functions not performed by
CONVERTV using other Access Method Services commands or
utility programs. The owner in the volume label can be updated
by the MODIFYV command for Mass Storage Volumes or
IEHDASDR for 3336 Model 1 Disk Packs. Data sets can be
recataloged using Access Method Services DELETE and DEFINE
commands or IEHPROGM utility. Data sets can be scratched
using the Access Method Services DELETE command or
IEHPROGM utility.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, and
35c.
IDC07431
FROM VOLUME COPIED TO THE TO VOLUME
Explanation: The source volume was successfully copied to the
target volume.
System Action: The command continues processing.
Programmer Response: None.
IDC07461
DATA SETS IN VSAM CATALOG SUCCESSFULLY
RECATALOGED
Explanation: Data sets in the VSAM catalog owning the volume
have been successfully recataloged.
System Action: The command continues processing.
Programmer Response: None.
IDC07471
VTOC AND LABEL OF TO VOLUME UPDATED
Explanation: The converted volume now has the appro pi ate
alternate track information and VSAM timestamp in the VTOC,
and owner and volume serial number in the label.
System Action: The command continues processing.
Programmer Response: None.
IDC07481
ELIGIBLE NON-VSAM DATA SETS SUCCESSFULLY
RECATALOGED
Explanation: The data sets not in the VSAM owning catalog
have been recataloged if there were any that needed to be
recataloged.
System Action: The command continues processing.
Programmer Response: None.
IDC07491
VTOC OF FROM VOLUME SCRATCHED
Explanation: The VTOC of the source volume was successfully
scratched.
System Action: The command continues processing.
Programmer Response: None.
IDC07S11
CARTS csnl csn2 SCRATCHED FOR VOLUME volser
Explanation: The requested volume (volser) was scratched.
The message identifies the cartridges scratched (csnl and
csn2).
System Action: The command continues processing.
Programmer Response: None.
IDC07601
RECORD FOR COPY yyddd REMOVED
Explanation: The copy record created on the date indicated by
'yyddd' was removed from the Inventory data set.
System Action: The command continues processing.
Programmer Response: None.
IDC07631
RECORD FOR VOLUME volser REMOVED
Explanation: A base volume record for volume (volser) was
removed from the Inventory data set.
System Action: The command continues processing.
Programmer Response: None.
IDC07801 SCRATCH CARTRIDGE csn EJECTED
Explanation: A scratch cartridge (csn) was ejected from the
Mass Storage Facility (MSF). The message identifies the
cartridge serial number of the cartridge.
System Action: Continue processing.
Programmer Response: None.
IDC07811
NUMBER OF SCRATCH CARTRIDGES EJECTED IS
nnnnnnnnn
Explanation: A number of. scratch cartridges (nnnnnnnnn) were
ejected successfully from the library.
System Action: Continue processing.
Programmer Response: None.
IDC07901
CARTRIDGE csn REPLACED BY CARTRIDGE csn
Explanation: An old or defective cartridge of a Mass
/
Programmer Response: If the data sets must be scratched, use
one of the following methods to scratch them:
• Run the IEHPROGM utility.
• Run the DELETE command.
• Specify DELETE in the DISP parameter on the DO
statement.
Storag~
Volume has been replaced by a scratch cartridge selected by
the user or at random by the Mass Storage Controller (MSC).
The first cartridge serial number (csn) identifies the replaced
cartridge; the second cartridge serial number (csn) identifies
the cartridge used as the replacement. The data on the old or
defective cartridge has been copied to the new cartridge.
System Action: Processing continues.
Programmer Response: None.
IDC08l01 VOLUME ser BEING PROCESSED
IDC08l41
n CATALOGED MULTI-VOLUME DATA SETS WERE
NOT SCRATCHED
Explanation: The number of cataloged multivolume data sets
that were not scratched is n. The SCRDSET command does not
scratch multivolume cataloged data sets.
System Action: Processing continues with the next volume to
be processed.
Programmer Response: If the data sets must be scratched, use
one of the following methods to scratch them:
• Run the IEHPROGM utility.
• Run the DELETE command.
• Specify DELETE in the DISP parame~er of the DO statement.
IDC08l51
VOLUME ser IN GROUP grpname BEING PROCESSED
Explanation: A new volume with the volume serial number ser
in group grpname is being processed. Additional messages
follow to indicate the data sets that have been scratched, if
any.
System Action: The volume is processed.
Programmer Response: None.
IDC08l61 SYSCTLGDATA SET NOT SCRATCHED
Explanation: The PURGE parameter was not specified on a
SCRDSET command and an OS system or CVOL catalog data
set SYSCTLG met the limiting criteria for data set scratching.
Data set SYSCTLG was not scratched.
System Action: Processing continues with the next volume to
be processed.
Programmer Response: If the SYSCTLG data set must be
scratched, use the IEHPROGM utility, or run the SCRDSET
command with the PURGE parameter.
Explanation: A new volume ser is being processed. Messages
IDC08l71
follow to indicate the data sets on the volume that are
scratched.
System Action: -Processing of data sets on the volume begins.
Programmer Response: None.
Explanation: No volumes were processed in group grpname.
ALL ACTIVE VOLUMES IN GROUP grpname WERE
EXCLUDED
removed from the catalog.
Each active volume that normally would have been processed
was excluded with the EXCLUDEVOLUMES parameter.
System Action: If any groups remain to be processed,
processing continues with the next group. If not, the command
terminates.
Programmer Response: None.
System Action: Processing continues.
Programmer Response: None.
IDC08321
IDC08lli
dsn UNCATALOGED
Explanation: The data set entry for dsn was successfully
IDC08l21
n DATA SETS WERE SCRATCHED FROM VOLUME
ser
Explanation: The number of data sets scratched from volume
ser was n.
System Action: Processing continues.
Programmer Response: None.
Explanation: A LlSTMSVI request for all volumes non-grouped
was made. No non-grouped volumes were found in the
inventory data set.
System Action: Processing continues.
Programmer Response: None.
IDC08551
IDC08l31
n CATALOGED GDG TYPE DATA SETS WERE NOT
SCRATCHED
Explanation: The number of cataloged generation data group
(GOG) type data sets that were not scratched is n. The
SCRDSET command does not scratch cataloged data sets with
names that end in 'name.GnnnnVnn'.
System Action: Processing continues with the next volume to
be processed.
NO NON-GROUPED VOLUME RECORDS EXIST IN
THE INVENTORY
CHANGE OF parameter SUCCESSFUL
Explanation: The specified TUNE command parameter
(parameter) was successfully changed.
System Action: The command continues processing.
Programmer Response: None.
Section 4: IDC Messages - Access Method Services
4-9
IDC08611
NO TAPE DATA SETS OPEN FOR THIS CHECKPOINT
not processed.
Programmer Response: None.
list has an invalid type field or the length field is invalid for the
specified type. The condition code remains unchanged.
System Action: The specified dump element is ignored.
Programmer Response: Correct the length and/or type of the
specified dump element.
IDC08621
IDC09231
Explanation: No type 1 DSDRs were found for this checkid.
System Action: Normal processing continues, the checkpoint is
DUPLICATE SELECTED CHECKID
XXXXXXXXXXXXXXXX
Explanation: The same checkid was selected by the user more
than once.
System Action: Normal processing continues, the checkpoint is
not processed.
Programmer Response: Check to see if another checkid was
intended; and then resubmit.
IDC08631
DUPLICATE CHECKPOINT ENTRY
XXXXXXXXXXXXXXXX
Explanation: A duplicate entry was found for a user-selected
checkid already.
System Action: Normal processing continues.
Programmer Response: None.
IDC08641
NO CHECKPOINTS FOUND ON DATA SET
Explanation: No CHR records were found on the checkpoint
data set.
System Action: CHKLlST terminates.
Programmer Response: Verify that the correct checkpoint data
set was used, then resubmit job.
Problem Determination: Table 1, items 1, 2, 4, 26b, and 29.
IDC08741 FOLLOWING NOT ALPHABETIC - INSUFFICIENT
WORK SPACE FOR SORT
Explanation: Insufficient virtual storage is available for sorting
alphabetically the objects to be listed by a LlSTCRA command.
System Action: The sorting is not done and the objects are
listed in the order that they are encountered while reading the
catalog recovery area.
Programmer Response: If a sorted listing is desired, rerun the
job with a larger storage allocation.
IDC08771
NUMBER OF RECORDS THAT MISCOMPARED IN
THIS CRA - nn
Explanation: The COMPARE option was requested and this
message indicates the number (nn) of records for which a
miscompare between the catalog recovery area and catalog
occurred.
System Action: Processing continues.
Programmer Response: Determine whether recovery is
required. For more information on catalog recovery, see
OS /VS2 Access Method Services.
IDC08881
coo ENTRY CONTAINS NO DATA RECORDS
Explanation: There are no data records in the VSAM data set
to be exported. See the primary message for the name of the
data set.
System Action: Processing of catalog information only for this
data set is attempted. See the primary message for processing
result. If processing was successful, then the portable data set
contains the necessary information to redefine the data set via
IMPORTRA.
Programmer Response: None.
IDC09221
'xxx' DUMP ELEMENT INVALID FOR SYMBOLIC
DUMP
Explanation: The specified dump element in a symbolic dump
4-10
VS2 System Messages (VS2 Release 3.7)
'xxx' ARRAY HEADER INVALID FOR SYMBOLIC
DUMP
Explanation: The specified array header in a symbolic dump
list has an invalid extent field (must be greater than 0 and less
than or equal to 99), has an invalid item count field (must be
greater than 0), or is an array header within an existing array
specification (arrays of arrays are not allowed). The condition
code remains unchanged.
System Action: The specified array header is ignored. Dump
elements within the array specification are treated as single
(non-arrayed) items.
Programmer Response: Correct the invalid fields of the
specified array header.
IDC09241 DUMP ROUTINE INVOKED AT 'mac'
Explanation: The Access Method Services dump routine has
been invoked at the specified UDUMP macro (mac), a dump
entry point.
System Action: A dump of the IDCAMS trace tables is
provided, as well as symbolic and/or full region dumps, if
requested by the IDCAMS user.
Programmer Response: None.
IDC09251
DUMP xxx PRODUCED AT DUMP POINT mac
Explanation: A dump was requested and produced at the
specified UDUMP macro (mac). The dump identifier (xxx) is
given.
System Action: Processing continues.
Programmer Response: None.
IDC09701
** NUMBER OF TRACKS = nn; CCHH OF NEXT
TRACK = X' cchh'
.Explanation: The above data could not be restored in the
VTOC.
System Action: The command continues processing.
Programmer Response: If the volume is a virtual volume,
ignore this error since alternate tracks do not apply for virtual
volumes and the problem need not be corrected. If the volume
is a real volume, use the AMASPZAP service aid to place the
information from the subsequent message into the VTOC.
IDCI0691 FUNCTION PERFORMED - ERROR UPDATING
INVENTORY, CODE = X'nnnn'
Explanation: If a Mass Storage Control function was requested,
the function was performed by the Mass Storage Control;
however, an error prevented the Mass Storage Volume Control
Inventory data set from being updated. If only Inventory data
set updating was requested, at least one record was updated
in the Inventory; however, an error prevented the rest of the
records from being updated. nnnn is the reason code returned
from the Mass Storage System Communicator and indicates
the cause of the error. The request has beer1 journalled in the
Mass Storage Volume Control Journal data set.
System Action: The command continues processing. A
subsequent function may fail because of the error in the
Inventory data set.
Programmmer Response: Investigate the reason code returned
from the Mass Storage System Communicator. Contact the
system programmer. The Inventory data set should be restored
VS2.03.807
from the backup copy of the Inventory data set and the
Journal data set.
Problem Determination: Table I, items 1,2,3,4,13,14,29
35a, 35b, and 35c.
IDCI2521 COMMAND ALLOWS NO PARAMETERS PARAMETERS IGNORED
Explanation: This message indicates that for a command
defined to have no parameters, some parameters were coded.
System Action: The parameters are ignored but the command
is processed.
Programmer Response: None.
Problem Determination: Table I, items 13, 20, 29.
IDCI4121 TRACE ALREADY IN REQUESTED STATE
Explanation: The hardware trace is already in the requested
state. The Mass Storage System Communicator reason code is
X'7F'. See the publication "OS/VS Message Library: Mass
Storage System (MSS) Messages", GC38-IOOO for more
information about the reason code.
System Action: The command completes normally.
Programmer Response: None.
IDCI5021 PASSWORD SUPPRESSION IN MODEL OBJECT
Explanation: The password information in the model object
was inaccessible because there was insufficient password
protection authorization or RACF authorization. This is an
informational or warning message that occurs if the password
or RACF authorization provided is not high enough to locate
the passwords themselves; therefore, the passwords were not
used for the object being defined.
System Action: Processing of the command continues. The
passwords are not modeled.
Programmer Response: None, if you did not want to model the
password information. If you did, delete the data set. The,
before redefining, either supply the MASTERPW password of
the model object or have your user profile modified so you
have RAC-alter access to the model object.
Problem Determination: Table I, items 3, 4, 29.
IDCI5431 NEW KEYS AND/OR RECORDSIZE VALUES EQUAL
TO PRIOR DEFAULT VALUES.
Explanation: The ALTER command specified the KEYS or
maximum RECORDSIZE parameter with values equal to the
default values chosen by 1he DEFINE command. The DEFINE
defaults are KEYS (64 0) and RECORDSIZE (4089 4089) for
non-spa;med record data sets or RECORDSIZE (4086 32600)
for spanned record data sets.
System Action: The ALTER command continues processing
with a condition code of 4, altering any parameters other than
KEYS and RECORDSIZE if possible. Invalid key values also
prevent alteration of record size values in the same command
and vice versa.
Programmer Response: None, if the default values are the
correct ones. Otherwise, execute an ALTER command to
correct the values.
Problem Determination: Table I, items I, 2, 3, 4, 29.
IDCI5441 KEYS AND/OR RECORDSIZE VALUES EQUAL TO
PRIOR NON-DEFAULT VALUES
Explanation: The ALTER command specified the KEYS or
maximum RECORDSIZE parameter with values equal to those
already defined.
System Action: The ALTER command continues processing
with a condition code of 4, altering any parameters other than
KEYS and RECORDSIZE if possible . Invalid key values also
prevent alteration of record size values in the same command
and vice versa.
Programmer Response: None, if the specified values are
correct. Otherwise, execute an ALTER command to correct the
values.
Problem Determination: Table I, items I, 2, 3, 4, 29.
IDCI5611 WKSPC LACKING FOR din
Explanation: A larger region size is required for this particular
invocation of Access Method Services and LlSTCAT.
System Action: The LlSTCAT command bypasses the indicated
entry and continues processing with a condition code of 4.
Programmer Response: Rerun the job in a larger region for
those entries that were bypassed.
Problem Determination: Table I, items I, 3, 4, 29.
IDC15621 ler VOLUME SERIAL NUMBER TOO LONG
Explanation: A volume serial number exceeds six characters
for the LlSTCAT SPACE request.
System Action: The LlSTCAT command bypasses the indicated
entry and continues processing with a condition code of 4.
Programmer Response: Rerun the job with the corrected
volume serial numbers.
Problem Determination: Table I, items 3, 4, 29.
•
IDCI5641 chartyp IS AN UNKNOWN TYPE
Explanation: An entry returned from the catalog is a type not
supported by LlSTCAT.
System Action: The LlSTCAT command bypasses the entry
and continues processing with a condition code of 4.
programmer Response: None.
Problem Determination: Table I, items 3, 4, 29.
IDCI5651 xxx NOT A REQUESTED TYPE
Explanation: A desired entry (xxx) was not among the types
requested.
System Action: The LlSTCAT command bypasses the specified
entry and continues processing with a condition code of 4.
Programmer Response: Rerun the job with the correct type or
types specified.
Problem Determination: Table I, items 3, 4, 29.
IDC15661 •• xxx NOT LISTED
Explanation: A specified entry name (xxx) does not exist in the
desired catalog, or may be a volume serial number to be
specified with the type SPACE in a separate LlSTCAT
command request.
System Action: The designated entry is bypassed and
processing continues with a condition code of 4.
Programmer Response: Correct the entry name and rerun the
job to list this particular entry.
Problem Determination: Table I, items I, 3, 4, 29.
IOCI5671 •• INVALID CONTROL INTERVAL NUMBER 'nnn'
Explanation: An entry identified by the control interval number
nnn in the VSAM catalog does not exist.
System Action: The designated entry is bypassed and
processing continues.
Programmer Response: None.
Problem Determination: Table I, items I, 3, 4, 29.
IOCI5691
EXPIRATION PARAMETER DOES NOT APPLY TO
ENTRY TYPE(S)
Explanation: The EXPIRATION option of LlSTCAT was specified
with entry type(s) that contain either no expiration-date field
(for example, UCAT, SPACE) or an expiration-date field that is
never initialized (for example, DATA, INDEX).
Section 4: IDC Messages - Access Method Services
4-11
System Action: LlSTCAT continues normally after the warning
message, processing the specified entry types. (Condition code
of 4.)
4-11.0
VS2 System Messages (VS2.03.807)
I~
Section 4: IDC Messages· Access Method Services
4-11.1
VS2.03.807
Programmer Response: None, but the programmer should be
aware that the listing has not been restricted by the
EXPIRATION option. All specified entry types will be listed.
Programmer Response: The duplicate name must be removed
before the entry can be converted.
Problem Determination: Table I, items 2, 3, 4, 29.
IDCl5741
IDCl6321 CVOL POINTER 'xxx' TO VOLUME 'ser' NOT
CONVERTED
CATALOG ENTRY COMPARISON NO LONGER
FUNCTIONING
Explanation: This message follows the l00th IDC15751
message. Comparison of the backup and target catalog
continues but only volume serial number mismatches are listed.
System Action: Reload processing continues.
Programmer Response: The large number of discrepancies
detected between the target and backup catalogs indicate that
you should use the reloaded catalog with care until the
LlSTCAT output obtained before and after the reload has been
carefully checked.
Problem Determination: Table I, item 34a.
IDCl5751 ONLY
{BACKUP} DEFINES {dsn}
TARGET
ser
Explanation: This message indicates that either the backup or
target catalog does not contain the data set or volume entry.
System Action: Reload processing continues.
Programmer Response: If only the backup defines a data set,
the physical data for the data set probably does not exist on
the volumes indicated. Consequently, the catalog entry should
be deleted. Use the DELETE NOERASE option, since the ERASE
option may affect other users' data.
If only the backup defines a volume, the volume is probably
no longer owned by this catalog. Delete any data sets
indicated as residing on this volume, then delete this volume.
If only the target defines a VSAM data set, access to the
data set has been lost. A backup copy of the data set (output
from EXPORT) sbould be obtained and imported (IMPORT
command).
If only the target defines a non-VSAM data set or an alias
or generation data group, their catalog entries can be
re-established with the DEFINE Command.
If only the target defines a volume, access has been lost to
the volume. If cannot be reused by VSAM until the VSAM
ownership and data space protection attributes have been
removed. (This can be done by executing an off-line
IEHDASDR DASDI, or executing Access Method Services
ALTER REMOVE VOLUME.)
IDCl5951 PASSWORDS SUPPRESSED FOR THE EXPORTED
DATA SET
.
Explanation: The password and other protection information
was inaccessible ~ue to insufficient password or RACF
authorization. (The portable version of the data set has been
created, but without the protection attributes.)
Note: When protection information is exported, it does not
include the RACF profile, the passwords, and other protection
information for the data set. However, the RACF indicator is
exported.
System Action: Processing of the command continues.
Programmer Response: If the protection. attributes are desired,
specify the master level password or have your user profile
modified so it indicates RAC-alter access to the data set.
I
IDCl6311 DUPLICATE ·SYSI.' DATA SET NAME IN VSAM
CAT~OG
Explanation: This is an informational message only. A duplicate
SYSI. data set was found in the VSAM catalog while
attempting to convert an OS catalog entry.
System Action: An accompanying message identifies the entry
not converted. The entry is not converted.
4-12
VS2 System Messages (VS2.03.807)
Explanation: The CVOL name was not converted to an alias
entry in the VSAM master catalog because the CVOLEQUATES
parameter was not specified, or was specified but the CVOL
volume serial number in the CVOL pointer entry was not the
one specified in the parameter.
System Action: The entry is not converted.
Programmer Response: Use the DEFINE ALIAS command to
create an alias entry in the master catalog.
Problem Determination: Table I, items 1, 3,4, 25, 29.
IDCl63al ALIASES OF GENERATION INDEX POINTER ENTRIES
ARE NOT CONVERTED
Explanation: An alias name of an OS catalog generation index
pointer entry (GIPE) was encountered. Because aliases of
VSAM GOG BASE entries are not allowed, the GIPE alias name
is not converted.
System Action: The entry is not converted.
Programmer Response: None.
Problem Determination: Table I, items 1, 3, 4, 25, 29.
IDC16441 ALTERNATE INDEX KEY NOT IN BASE RECORD xxx
Explanation: xxx identifies a base cluster record that is not
long enough to contain the entire alternate key. If the base
cluster is a key-sequenced data set, xxx is the key of the short
base cluster record (up to a maximum of the first ten bytes)
expressed in hexadecimal. If the base cluster is an
entry sequenced data set, xxx is the RBA of the short base
cluster record, given in decimal.
System Action: The base cluster record is bypassed.
Therefore, it will not be reflected in the alternate index being
built (see subsequent message for the name of the alternate
index.)
Programmer Response: After the alternate index is built, the
short record must be deleted and a long enough record
rewritten via a user program with the alternate index as part of
the upgrade set. This will cause the alternate index to be
upgraded to reflect this particular base record.
Problem Determination: Table I, items 2, 3, 4, 29.
IDCl6451 NONUNIQUE AIX KEY keyl
JKEY} IS key2
PRIME
"tRBA
Explanation: The alternate index being built (see subsequent
message for name) was defined with the UNIQUEKEY attribute;
i.e., the alternate key exists on one and only one base cluster
record. However, multiple occurrences of the same alternate
key have been encountered. The message is issued once for
each multiple occurrence. The message gives the alternate key
first (up to a maximum of the first ten bytes) expressed in
hexadecimal. If the base cluster is a key-sequenced data set,
the prime key is given (up to a maximum of the first ten
bytes) expressed in h~xadecimal. If the base cluster is an
entry-sequenced data set, the prime RBA is given in decimal.
System Action: An alternate index record is created containing
the alternate key and only the first prime key or RBA listed. All
subsequent prime .keys/RBAs will not be reflected in the
alternate index record.
Programmer Response: If the UNIQUEKEY attribute was
correctly specified, then the base cluster is in error and must
be corrected via a user program. If the UNIQUEKEY attribute
was incorrectly specified:
• and the alternate index was defined with the REUSE
parameter, change it to NONUNIQUEKEY using the Access
Method Services ALTER command.
I~,
Section 4: IDC Messages· Access Method Services
4-12.1
4-12.2
VS2System Menages (VS2.03.807)
",'.
,J'
• and the alternate index was not defined with the REUSE
attribute, delete the alternate index and redefine it with the
NONUNIQUEKEY attribute.
Then rebuild the alternate index using the BLDINDEX
Command.
Problem Determination: Table I, items 2, 3, 4, 29.
IDCI6461 nnnnn EXCESS PRIME
KEY key
KEY} VALUES FOR AIX
{ RBA
Explanation: key is the key (expressed in hexadecimal, up to a
maximum of the first ten bytes) of an alternate index record
that was too short to contain all the prime key or RBA pointer
values that occurred for that alternate index key. nnnnn gives
the number of pointers that could not fit into the record. The
name of the alternate index being built is given in a
subsequent message.
System Action: The alternate index record is created with only
those pOinters that could fit.,
Programmer Response: Delete the alternate index and redefine
it (using the Access Method Services commands) with a
maximum record size long enough to contain the maximum
number of pointers for anyone alternate key. Then rebuild the
alternate index using the BLDINDEX command.
Problem Determination: Table I, items 2, 3, 4, 29.
IDCI6531
dsn BUILT WITH ERRORS
Building of the alternate index identified by dsn
has been completed but some non-terminating errors were
encountered. Non-terminating errors consist of:
• alternate index key not contained in one or more base
cluster records.
• multiple occurrences of one or more alternate keys for an
alternate index defined with the UNIQUEKEY attribute.
• one or more alternate index records too short to contain all
the prime key or RBA pointers.
All non-terminating errors for this alternate index have been
identified in messages that precede this message.
System Action: The building of the alternate index is compiete.
Programmer Response: Depends on the error encountered.
Refer to the action outlined for the individual errors.
Problem Determination: Table I, items 2, 3, 4, 29, 31.
Explanation:
IDCI66I1 OUT -OF-SYNC DATA SET SUCCESSFULLY
EXPORTED (BY FORCE)
Explanation: The portable data set contains the necessary
information to recreate the data set via IMPORTRA. At the
time of export the data set was out of synchronization, caused
by a mismatch between time stamps or space information. See
the secondary message for the data set name.
System Action: Processing continues.
Programmer Response: None.
IDCI6621
OUT -OF-SYNC DATA SET NOT EXPORTED
Explanation: The VSAM data set named in the message that
follows is out of synchronization and the FORCE parameter was
not specified. The out-of-synchronization is caused by a
mismatch of the space information.
System Action: Processing of the VSAM data set is bypassed.
Programmer Response: If the data set, with its possible
problems, is desired, then the FORCE parameter should be
specified on the EXPORTRA command and the job rerun.
IDCI6631
BYPASSED RELATION dsname
Explanation: An error occurred or a catalog entry could not be
located for a path or an alternate index to a VSAM cluster, an
OS/VS alias for a nonVSAM object, or a nonVSAM object
associated with an OS/VS2 generation data group. Dsname is
the name of the cluster, nonVSAM object, or generation data
group.
System Action: The related object is bypassed and processing
of the named object is continued.
Programmer Response: List the named object after performing
an IMPORTRA operation to determine missing related object(s)
and to redefine the related object(s).
IDCI6641
ASSOCIATION ERROR, dsname
Explanation: The named catalog entry described a generation
data set having no relationship to any OS/VS2 generation data
group, or the entry describes a nonVSAM data set containing
other than an OS/VS alias related to it.
System Action: The association cannot be processed and
processing of the named object is continued.
Programmer Response: List the named object after performing
an IMPORTRA operation to determine missing related object(s)
and to redefine the related object(s).
IDCI6671
VOLUME ser IS OUT-Of-SYNC AND LATER THAN
VOLUME ser
Explanation: The data-set-directory-entry time stamp
mismatches the time stamp for the VSAM data set named in
the following message. The volumes are out of synchronization,
although some of the data sets may still be recoverable.
System Action: The VSAM data set entry and associations are
bypassed.
Programmer Response: Get the two volumes in synchronization
using the IEHDASDR utility program. Then rerun the job.
IDCI6781
**
DATA SET EXPORTED WITH MINOR ERRORS
Explanation: An error occurred while processing an associated
object for an object being exported.
System Action: Processing of the associated object is
bypassed.
Programmer Response: See the preceding message to
determine the type of error and the recovery procedure.
IDCI6791
** OUT -Of-SYNC DATA SET EXPORTED WITH
MINOR ERRORS
Explanation: An error occurred while processing an associated
object for an out-of-synchronization data set. The
out-of-synchronization i~ caused by a mismatch between the
time stamps or space information on the various volumes of a
multi-volume data set.
System Action: Processing of the associated object is
bypassed.
Programmer Response: See the preceding message to
determine the type of error and the recovery procedure.
IDCI7071
**
OWNER ownerid NOT UPDATED IN INVENTORY
FOR NEW COPY yyddd
Explanation: The owner data 'ownerid' in the volume label of
the new copy volume, created on the specified date 'yyddd'
could not be updated in the copy volume record or in the
cartridge labels. This condition occurred because the cartridges
of an existing copy volume were reused. See the preceding
message for further explanation of the problem.
System Action: Processing continues.
Programmer Response: This discrepancy cannot be corrected.
The LlSTMSVI reports will reflect different owners for the
source volume and the designated copy volume, even though
the owner data is correct in the volume labels of both
volumes.
Section 4: IDC Messages - Access Method Services
4 .. 13
41
IDC17421
RECATALOG OPTION INVALID FOR VOLUME
IDC18671 CURRENT VOLUME NOT FOUND xxxxxxx?,
Explanation: The source volume is not owned by a VSAM
Explanation: The volume sequence number exceeded the
catalog. Therefore, the VSAMCATALOG option does not apply.
System Action: No recataloging is performed. The command
continues processing.
Programmer Response: If you want any data sets recataloged,
use the IEHPROGM utility or the Access Method Services
DELETE and DEFINE commands.
Problem Determination: Table I, items 3, 4, 13, 25B, and 29.
number of volumes (JFCBNVOLS) for the indicated ddname.
System Action: Normal processing continues.
Programmer Response: Keep all related data sets and listings
for reference.
Problem Determination: Table 1, items 1, 2, 3, 26b, and 29.
IDC17841 NO SCRATCH CARTRIDGES FOUND IN MSF
Explanation: No scratch cartridges can be ejected from the
Mass Storage Facility (MSF) because there are no scratch
cartridges in the MSF.
Syst.em Action: The command terminates with a message.
Programmer Response: None.
IDC18401 TRACE AREA EMPTY - NO DATA DUMPED
Explanation: An attempt was made to dump trace data but the
trace areas requested were null.
System Action: The command terminates normally.
Programmer Response: Turn the trace on before requesting a
dump.
Problem Determination: Table I, items 2, 3, 4, 13, 29, and 30.
IDC18411 END OF CURRENT DATA COULD NOT BE
DETERMINED - ALL DATA DUMPED
Explanation: An attempt was made to dump only current trace
data, but the end of the current data was not found.
Therefore, all of the trace data was dumped. There may be
data from a previous trace period in the output data set.
System Action: The command dumped all the data in the
requested trace area.
Programmer Response: When you run the trace report
program you can select to process only the data from the
current trace period.
Problem Determination: Table I, items 2, 3, 4, 13, 29, and 30.
IDC18601 SELECTED CHECKID, xxxxxxxxxxxxxxxx NOT FOUND
Explanation: The checkid listed was selected by the user, but
not found in the checkpoint data set.
System Action: Normal processing continues, the CHECKID is
not processed.
Programmer Response: Verify the checkid spelling, and that
the correct checkpoint data set was used.
Problem Determination: Table 1, items 1, 2, 4, and ,29.
IDC186S1
XXXXXXXX ADDITIONAL VOLUME SERIAL NOT FOUND
IN CHKPT DATA SET
Explanation: Probable checkpoint logic error. A type 1 or type
2 DSDR indicated the presence of a type 2 DSDR which did
not exist.
System Action: Incomplete CHKLlST information is listed, and
processing continues with the next checkpoint entry.
Programmer Response: Keep all related data sets and listing
for reference.
Problem Determination: Table 1, items 1, 2, 4, 26b, and 29.
IDC18661 UNEXPECTED EOF ON CHECKPOINT DATA SET
Explanation: End-of-file occured while processing DSDRs.
System Action: CHKLlST utility terminates.
Programmer Response: Keep all related data sets and listings
for reference.
.
Problem Determination: Table 1, items 1, 2, 4, 26b, and 29.
4-14
VS2 System Messages (VS2 Release 3.7)
IDC18701
IlOIlO
IGNORED VSAM ERROR READING CRA - CI 'nn'X
Explanation: A LlSTCRA function encountered an I/O error
reading a catalog recovery area (CRA) record at the specified
control interval. 'nn' is the control interval number in
hexadecimal.
System Action: The record is ignored and processing is
continued as long as no more than 50 errors have been
encountered while processing the LlSTCRA command. When
the number of errors reaches 50, processing is terminated.
Programmer Response: See the preceding message to
determine the cause of the I/O error. Correct the problem if
possible, and resubmit the job.
IDC18711
U IGNORED VSAM ERROR READING CATALOG - CI
'nn'X
Eplanation: A LlSTCRA function encountered an I/O error
reading a catalog record at the specified control interval. 'nn'
is the control interval number in hexadecimal.
System Action: The record is ignored and processing is
continued as long as no more than 50 errors have been
encountered while processing the LlSTCRA command. When
the number of errors reaches 50, processing is terminated.
Programmer Response: See the preceding message to
determine the cause of the 1/0 error. Correct the problem if
possible, and resubmit the job.
IDC18751 ERROR TRANSLATING CRA CI FROM CATALOG CI 'nn'X
Explanation: An error occurred when translating an entry's
catalog control interval number, which points at a related
entry, to a CRA control interval before reading the entry. 'nn'
is the catalog control interval number in hexadecimal. This will
normally result from an incomplete entry definition or an I/O
error identified in a preceding message.
System Action: The error is bypassed and processing is
continued; however, there may be minor errors in the list.
Programmer Response: Restore the volume on which the error
occurred to a previous valid condition. For more information on
catalog recovery, see OS /VS2 Access Method Services.
Problem Determination: Table I, items 2, 3, 4, 29.
IDC18781 IGNORED ERROR FROM IDCRC04, DUMP POINT ID
- xx
Explanation: An error occurred in module IDCRCOll
(EXPORTRA Field Management) when it was called by
LlSTCRA; IDCRC04 was unable to return information about a
field specified by LlSTCRA. This will normally result from an
I/O error identified in a preceding message. The xx is the last
dump point before the error was detected.
System Action: The error is bypassed and processing is
continued; however, there may be minor errors in the list.
Programmer Response: Restore the volume on which the error
occurred to a previous valid condition. For more information on
catalog recovery, see OS/VS2 Access Method Services.
Problem Determination: Table I, items 2, 3, 4, 29.
YS2.03.807
IDC18801 IGNORED I/O ERROR READING VOLUME LABEL
Explanation: A LlSTCRA command encountered an I/O error
reading the format-4 DSCB in the VTOC to obtain the time
stamp information.
System Action: The error is ignored and the time stamps are
not printed.
Programmer Response: List the format-4 DSCB using the
IEHLlST or AMASPZAP utility program or determine the cause
of the I/O error by referring to the reason code in the
preceding error message, correct the problem if possible, and
rerun the job.
Problem Determination: Table I, items 2, 3, 4, 29.
IDC18811 IGNORED OPEN FAILURE FOR ALTERNATE OUTPUT
DATA SET
Explanation: LlSTCRA encountered an error attempting to
open the alternate output data set.
System Action: The error was ignored and the system output
data set used.
Programmer Response: If the output is desired in the alternate
data set, determine the cause of the error, fix it, and rerun the
job.
IDC18871 ERROR REFERENCING CRA ON VOLUME ser REASON CODE cde
Explanation: In opening the catalog recovery area (CRA) there
was a problem indicated by the reason code cde. Possible
reason codes and their meanings are:
Reason
Code Meaning
3 Time stamp for volume was not obtained.
6 I/O error reading the CRA record.
System Action: Processing continues.
Programmer Response: This message requires no action, but
the problem causing it may cause other messages. that you
should act on.
IDC18901 RACF PROFILE COULD NOT BE DELETED ELIGIBLE
NOT
Explanation: As the result of a DELETE or EXPORT command,
a RACF indicated member was successfully deleted. However,
the RACF profile for this data set is not eligible for deletion.
System Action: Processing of the command continues.
Programmer Response: None.
Problem Determination: Table I, items 3, 4, 29.
IDC18911RACF PROFILE COULD NOT BE DELETED FOUND
NOT
Explanation: As the result of a DELETE or EXPORT command,
a RACF indicated member was successfully deleted. However,
the RACF profile for this data set could not be found.
System Action: Processing of the command continues.
Programmer Action: None.
Problem Determination: Table I, items 3, 4, 29.
IDC19271 INVALID 'MARGINS' VALUES SPECIFIED, DEFAULT
MARGINS ASSUMED.
Explanation: The leftmargin value specified in a MARGINS
parameter is not strictly less than the rightmargin value; at
least two' character positions must be provided.
System Action: The default margin values (2,72) are assumed.
The condition code is set to 4.
Programmer Response: Correct the invalid MARGINS
specifications.
Problem Determination: Table I, items I, 3, 4, 29.
IDC19681 VSAM TIME STAMP NOT UPDATED IN VTOC OF
FROM I TO VOLUME volser
Explanation: An error was encountered reading or updating the
VTOC so the VSAM time stamp was not updated for the
volume (volser). "From" or "to" indicates which value
encountered the error for commands that process more than
one value.
System Action: The command terminates normally if no
functions have been performed yet. If some functions have
been performed, the command continues processing.
Programmer Response: Rerun the job if the job was not
completed. If the function completed, use the AMASPZAP
service aid to correct the VSAM time stamp or ignore the
error.
Problem Determination: Table I, items I, 3, 4, 13, 25b, and
29.
IDC19691 ALTERNATE TRACK DATA NOT RESTORED IN VTOC
OF TO VOLUME volser
Explanation: An error was encountered reading or updating the
VTOC so the alternate track information was not restored in
the VTOC of the target volume (volser) after the copy of data.
A previous message explains the error.
System Action: The command continues processing.
Programmer Response: If the volume is a Mass Storage
Volume, ignore this error since alternate tracks do not apply
for Mass Storage Volumes and the problem need not be
corrected. If the volume is a real volume, use the AMASPZAP
service aid to place the information from the subsequent
message into the VTOC.
Problem Determination: Table I, items 1, 3, 4, 13, 14, 25b,
and 29.
IDC20111 FUNCTION CANNOT BE EXECUTED. INSUFFICIENT
MAIN STORAGE
Explanation: An Access Method Services function has been
requested that requires scratching data sets from volumes.
There was not enough virtual storage available to build the
parameter list for the SCRATCH macro. This .message is also
issued if a Mass Storage Control function is required and there
was not sufficient storage to issue the Mass Storage System
Communicator macro.
System Action: The data sets aren't scratched, or the Mass
Storage System Communicator macro is not issued. Other
actions are indicated by following messages;
Programmer Response: Rerun the job in a larger address
space.
Problem Determination: Table I, items I, 3, 29.
IDC20351
INVALID ERROR CONVERSION TABLE
Explanation: An error was detected in the information
transmitted in the Error Conversion Table, when attempting to
convert a numeric error code to a prose message. This should
not occur in a valid program.
System Action: The conversion request is terminated.
Programmer Response: Do the' problem determination action.
Problem Determination: Table I, items 3, 4, 29.
IDC20651
•• UNABLE TO CLEAR SERIAL-MISMATCH FLAG
FROM INVENTORY RECORD
Explanation: A flag indicating a volume serial mismatch exists
between the cartridge labels and the volume label for a Mass
Storage Volume could not be cleared from the Inventory data
set. See the previous message for further explanation of the
problem.
Section 4: IDC Messages· Access Method Services
4-16
I
System Action: The command terminates with an error
message.
Programmer Response: Correct the problem as identified in
the previous message and take the following actions for the
command that failed:
• If a Rename Operation Failed for ADDV
Run ADDV to backout or retry the rename operation if the
volume is .inactive. If the volume is active, run MODIFYV or
STOREV to either backout or retry the rename operation.
4-16.0
VS2 System Messages (VS2.03.807)
If the ADDV, MODIFYV, or STOREV commands are run to
recover from a rename failure, a DO statement for the
volume is required and must specify deferred mounting.
The values specified for the VOLUME and NEWSERIAL
parameters depend upon how the volume record is recorded
in the Inventory data set. If the cartridge labels have been
updated, the volume record will be identified by the new
volume serial number. For the VOLUME parameter, specify
the volume serial number as recorded in the cartridge labels
Section 4: IDC Messages· Access Method Services
4-16.1
and the volume record. For the NEWSERIAL parameter, specify
the desired volume serial number. Note that the security
check for nonVSAM status and password protected data
sets is bypassed only if the' NEWSERIAL parameter specifies
the same volume serial number as recorded in the Inventory
data set for the volume label. This allows the original
volume serial number of a VSAM volume to be restored if
the volume is left partially renamed.
If AOOV, MOOIFYV, or STOREY terminates without indicating
the status of the rename operation, LlSTMSVI can be run to
determine whether the volume is flagged for recovery
purposes. If the mismatch flag is set in the volume record,
LlSTMSVI not only lists the standard' information for the
volume but also highlights the volume report with a note
that a rename operation failed for the the preceding volume
and that serial number "nnnnnn' is recorded in the volume
I.bel of the volume.
• If a Rename Operation Failed for MOOIFYV
To recover from a MOOIFYV rename failure 1) run AOOV to
activate the volume if the volume is merely inactive and has
no volume serial mismatch condition, or 2) run AOOV to
both activate the volume and complete the rename
operation if the volume is both inactive and has a volume
serial mismatch condition, or 3) rerun MOOIFYV to complete
or retry the rename operation if the volume is active but
has a mismatch condition, or 4) run STOREY to complete or
retry the rename operation if the volume is active and if a
duplicate volume serial number is desired as a result of the
rename.
For the DO statement requirements, the proper VOLUME
and NEWSERIAL parameter values, and use of LlSTMSVI,
refer to the description above for an AOOV rename failure.
• If a Rename Operation Failed for STOREY
Rerun STOREY or run MOOIFYV to either backout or retry
the rename operation.
For the DO statement requirements, the proper VOLUME
and NEWSERIAL parameter values, and use of LlSTMSVI,
refer to the description above for an AOOV rename failure.
Problem Determination: Table I, item 1, 2, 3, 4, 13, 29, 35a,
and 35c.
IDC20741 VOLUME ser NOT ACTIVE
Explanation: Volume ser is not active, and is recorded in the
Inventory data set as inactive. The command issuing the
message requires an active volume.
System Action: Processing of the command terminates with a
message indicating the final condition code.
Programmer Response: Run the AOOV command to activate
the volume, and then rerun the command. If the volume is
already active but only the record indicates that the volume is
inactive, contact the space manager. The Inventory data set
may need to be restored from the backup copy and the
Journal data set.
Problem Determination: Table I, items 1, 2, 3, 4, 13, and 29.
IDC20751
lUI
VOLUME volser CANNOT BE ACTIVATED
Explanation: An attempt to make volume (volser) active and
mountable failed. See preceding message for further
explanation of the failure.
System Action: The command terminates with an error
message.
Programmer Response: Rerun the command after:
• Reentering one or both cartridges if the cartridges are
outside the Mass Storage Facility (MSF),
• Correcting the problem as indicated in the preceding
message, or
4·1.6
VS2 System Messages (VS2.03.807)
• Running the EJECTY command to eject the volume and then
reentering the cartridges if the cartridges were originally
entered while the Mass Storage Volume Control (MSVC) was
disabled.'
Problem Determination: Table 1, 2, 3, 4, 13, 29, 35a, and
35c.
IDC20761
•• CART csn [csn] NOT IN MSF FOR COPY yyddd
Explanation: The cartridges assigned to the copy created on
the date indicated by "yyddd" cannot be found in the Mass
Storage Facility (MSF). The cartridge serial numbers (csn
[csn]) identify the sequence one and/or sequence two
cartridge not in the MSF. See preceding message for additional
information.
System Action: The command terminates with a message
unless additional copies are specified for processing.
Programmer Response: Correct the. condition as indicated in
the preceding message. Rerun the command after:
• Reentering the miSSing cartridges,
• Selecting another copy volume,
• If one of the cartridges is lost, running the SCRATCHV
command to make the remaining cartridge assigned to the
volume scratch cartridge and to delete the record from the
Inventory data set, or
• Running the REMOVEYR command to delete the record for
the copy volume if both cartridges are lost.
Problem Determination: Table I, items 2,3,4, 13,29, 35a,
and 35c.
IDC20781
lUI COPY RECORDS FOR VOL volser CANNOT BE
RETRIEVED
Explanation: An attempt to access a record in the Inventory
data set for an existing copy volume failed. The base volume
record indicates additional copy volumes exist; however, the
record for the next copy volume in timestamp sequence cannot
be read. See the preceding message for further explanation of
the failure.
System Action: The command terminates with a message.
Programmer Response: Correct the error as indicated in the
preceding message.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 30,
35a, and 35c.
IDC20791
•• RECORD FOR GROUP groupname CANNOT BE
RETRIEVED FROM INVENTORY
Explanation: An attempt to access the record in the Inventory
data set for group (groupname) failed. See the preceding
message for further explanation of the failure.
System Action: The command terminates with a message
unless additional groups are specified for processing.
Programmer Response: Correct the error as indicated in the
preceding message. Verify that the group name is specified
correctly, then rerun the command.
Problem Determination: Table I, items 2, 3, 4, 13, 29, and
35c.
IDC20801
•• RECORD FOR VOL volser CANNOT BE
RETRIEVED FROM INVENTORY
Explanation: An attempt to access the record in the Inventory
data set for the volume (volser) failed. See the preceding
message for further explanation of the failure.
Programmer Response: Correct the error as indicated in the
preceding message. Before rerunning the command check that
the volume serial number is specified correctly.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 30,
35a, and 35c.
('
I,J
IDC20841
*'CO
CARTRIDGES NOT EJECTED
IDC20951
Explanation: The cartridges assigned to a Mass Storage
Volume could not be ejected from the MSF. If only one
cartridge was in the Mass Storage Facility, an attempt to eject
that one cartridge failed. See the preceding message for
further explanation of the failure.
System Action: The command continues processing.
Programmer Response: Correct the error as identified in the
preceding message and rerun the command.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC20871
** CART csn [csn) NOT SCRATCHED FOR COpy
yyddd
Explanation: The cartridges assigned to the copy volume
created on the date indicated by "yyddd" could not be
scratched. If only one cartridge was in the MSF an attempt
was made to scratch that one cartridge. The cartridge serial
numbers (csn) identify the sequence one and/or sequence two
cartridge not scratched. See the preceding message for further
explanation of the failure.
System Action: The command continues preocessing.
Programmer Response: Correct the problem as indicated in
the preceding message. If the cartridge(s) are out of the Mass
Storage Facility, re-enter the cartridges into the Mass Storage
Facility and rerun the command. If the cartridges are lost, run
the REMOVEVR command to delete the record for the copy
from the Inventory data set and rerun the command if
necessary.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC20911
**
[READONLY I READWRITE) ATTRIBUTE NOT SET
FOR VOLUME volser
Explanation: Volume (volser) could not be assigned the
READONLY or READWRITE attribute. READONLY may be
required because the volume belongs to a group which has the
READONLY attribute specified for all general-use volumes. See
the preceding message for further explanation of the problem.
System Action: The command continues processing.
Programmer Response: Run the MODIFYV command to change
the volume attribute to readonly or readwrite.
Problem Determination: Table I, items 2, 3, 4, 13, and 29.
IDC20931
*'CO VOLUME ATTRIBUTES NOT CHANGED TO AGREE
WITH GROUP groupname
Explanation: An attempt to change the attributes (bind/nobind,
exclusive/ shared, readonly /readwrite, dasderase/ nodasderase)
of a general-use volume failed. The attributes of the volume
do not agree with the attributes specified for all general-use
volumes belonging to the group (groupname). See the
preceding message for additional information on the problem.
System Action: The command continues processing.
Programmer. Response: Run the LlSTMSVI command to list the
information recorded in the Inventory data set about the
group. After determining the volume attributes specified at the
group level, run the MODIFYV command to update the volume
attributes to agree with the group specifications. If there are
many volumes in the group whose attributes do not agree with
the group, you can run the MODIFYG command to request a
change of the group attributes. If you specify the same
attributes on the MODIFYG command as are recorded already
in the group record, MODIFYG will still change the attributes of
all the active general-use volumes for the group.
Problem Determination: Table I, items 2, 3, 4, 13, and 29.
[FROM I TO) VOLUME volser INCOMPLETELY
RENAMED IN A PRIOR OPERATION
Explanation: Volume (volser) cannot be used. A previous
MODIFYV, ADDV, or STOREY command terminated before
completely changing the volume serial number of the volume.
The volume serial number on the cartridge labels' and in the
Inventory record does not agree with the volume serial number
in the volume label. "FROM" and "TO"· designate which
volume is unusable for those commands processing both a
source and target volume having the same volume serial
numbers.
System Action: The command terminates with a message
reflecting the severity of the error.
Programmer Response: Correct the problem as identified in
the preceding message and take the· following actions for the
command that failed:
• If a Rename Operation Failed for ADDV
Run ADDV to backout or retry the remane operaton if the
volume is inactive. If the volume is active, run MODIFYV or
STOREY to either backout or retry the rename operation. If
the ADDV, MODIFYV, or STOREY commands are run to
recover from a rename failure, a DO statement for the
•
volume is required and must specify deferred mounting. The
values specified for the VOLUME and NEWSERIAL
parameters depend upon how the volume record is recorded
in the Inventory data set. If the cartridge labels have been
updated, the volume record will be identified by the new
volume serial number. For the VOLUME parameter, specify
the volume serial number as recorded in the cartridge labels
and the volume record. For the NEWSERIAL parameter,
specify the desired volume serial number. Note that the
security check for nonVSAM status and password protected
data sets is bypassed only if the NEWSERIAL parameter
specifies the same volume serial number as recorded in the
Inventory data set for the volume label. This allows the
original volume serial number of a VSAM volume to be
restored if the volume is left partially renamed.
If ADDV, MODIFY, or STOREY terminates without indicating
the status of the rename operation, LlSTMSVI can be run to
determine whether the volume is flagged for recovery
purposes. If the mismatch flag is set in the volume record,
LlSTMSVI not only lists the standard information for the
volume but also highlights the preceding volume and that
serial number 'nnnnnn' is recorded in the volume label of
the volume.
• If a Rename Operation Failed for MODIFYV
To recover from a MODIFYV rename failure 1) run ADDV to
activate the volume if the volume is merely inactive and has
no volume serial mismatch condition, or 2) run ADDV to
both activate the volume and complete the rename
operation if the volume is both inactive and has a volume
serial mismatch condition, or 3) rerun MODIFYV to complete
or retry the rename operation if the volume is active but
has a mismatch condition, or 4) run STOREY to complete or
retry the rename operation if the volume is active and if a
duplicate volume serial number is desired as a result of the
rename.
For the DO statement requirements, the proper VOLUME
and NEWSERIAL parameter values, and use of LlSTMSVI,
refer to the description above for an ADDV rename failure.
Problem Determination: Table I, items ~, 2, 3, 4, 13, 29, 35a,
or 35c.
IDC20961
[FROM I TO) VOLUME volser INCOMPLETELY COPIED
IN A PRIOR OPERATION
Explanation: Volume (volser) was incompletely copied by the
Section 4: IDC Messages - Access Method Services
4-17
•
COPYV, RECOVERV, or CONVERTV commands and cannot be
used. "FROM" and "TO" designate which volume is unusable
for those commands processing both a source and target
volume having the same volume serial number.
System Action: The command terminates with a message
containing the severity code~
Programmer Response: Correct the problem as indicated in
the preceding message. Take one of the following actions for
the command that failed:
• If a Copy Operati()n Failed in COPYV
Rerun COPYV to complete the copy operation to the
incomplete copy volume (COPYV will reuse the cartridges of
the incomplete copy volume. for the new copy) or run
SCRATCHY to scratch the incomplete copy volume before
rerunning the COPYV command.
IF COPYV terminates without indicating the status of the
copy operation, LlSTMSVI can be run to determine whether
the volume is flagged for recovery purposes. If the
incomplete copy flag is set in the copy volume record,
LlSTMSVI not only lists the standard information for the
volume but also highlights the volume report with a note
that a copy operation failed for the preceding copy volume.
• If a Copy Operation Failed for RECOVERV
Rerun RECOVERV to complete the recover operation to the
target volume that is flagged as an incomplete copy volume.
Otherwise, run SCRATCHY to scratch the target volume. The
incomplete copy volume may even be used as the target
volume in the CONVERTV command. In all cases, the empty
VTOC check or security check for password protected data
sets is bypassed.
If the SCRATCHY command is run, the DO statement is not
required for the volume and if provided, must specify
deferred mounting. If the RECOVERV command is rerun, the
DO statement is not required for the target volume, which is
flagged as an incomplete copy, unless the volume serial
number of the target volume is different from the source
volume. If a DO statement is provided for the target
volume, deferred mounting must be specified. If a VSAM
catalog is on the volume, a .00 statement for the catalog is
not required; if provided, deferred mounting must be
specified.
If RECOVERV terminates without indicating the status. of the
recover operation, LlSTMSVI can be run to determine
whether the volume is flagged for recovery purposes. If the
incomplete copy flag is set in the target volume record,
LlSTMSVI not only lists the standard information for the
volume but also highlights the volume. report with a note
that a copy operation failed for the preceding volume.
• If a Copy Operation Failed for CONVERTV
Rerun CONVERTV to complete the conversion operation to
the target volume that is flagged as an incomple copy
volume. Otherwise, run SCRATCHY to scratch the target
volume. The incomplete copy volume may even by used as
the target volume in the RECOVERV command. In all cases,
the empty VTOC check or the security check for password
protected data sets is bypassed.
If the SCRATCHY command is run, the DO statement is not
required for the incompletely copied volume and if provided,
must specify deferred mounting. If a VSAM catalog is on the
volume and a DO statement for the target v.olume must be
provided and must specify deferred mounting. If a VSAM
catalog is on the volume and a DO statement is provided
for the catalog, the DO statement must also specify
deferred mounting.
If CONVERTV terminates without indicating the status of the
conversion operation, LlSTMSVI can be run to determine
whether the volume is flagged for recovery purposes. If the
incomplete copy flag is set in the target volume record,
4-18
VS2 System Messages (VS2 Release 3.7)
LlSTMSVI not only lists the standard information for the
volume but also highlights the volume report with a note
that a copy operation failed for the preceding volume.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, or
35c.
IDC20971
[FROM I TO) VOLUME volser INCOMPLETELY
CREATED IN A PRIOR OPERATION
Explanation: Volume (volser) was incompletely created by the
CREATEV command and could not be used. "FROM" and "TO"
designate which volume is unusable for those commands
processing both a source and target volume having the same
volume serial number.
System Action: The command terminates with a message
reflecting the severity of the error.
Programmer Response: Before creating the 'volume using the
CREATEV command run the SCRATCHY command to scratch
the partially created volume. In the SCRATCHY run, there must
be no DO statement for the partially created volume; the
empty VTOC check is bypassed.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, 35a,
and 35c.
IDC21001
CATALOG RETURN CODE FOR LOCATE REQUEST
WAS nn
Explanation: The return code from an OS/VS locate request
was nn. See "OS/VS2 System Programming Library: Data
Management", GC26-3830 for a description of the return
codes. The error was detected either in the VSAM or OS
Catalog Management. The subsequent message identifies the
data set not recataloged. During a CONVERTV operation, if the
data set was cataloged in a VSAM user catalog on the
converted volume, the data set may have been recataloged,
and this message can be ignored.
System Action: The command continues processing.
Programmer Response: Correct the error and recatalog the
data set using IEHPROGM utility or the Access Method
Services DELETE and DEFINE commands.
Problem Determination: Table I, item 1, 3, 4, 13, 14, 25d, 29,
and 31.
IDC21011 CATALOG RETURN CODE FOR RECAT REQUEST
WAS nn - REASON CODE nn
Explanation: The return code from an OS/VS recatalog request
was nn. The reason code in register 0 wasnn. See OS/VS
Message Library: Mass Storage System Messages (MSS),
GC38-1000 for a description of the reason codes; and OS/VS
Message Library: VS2 System Codes, GC38-1008 for return
code. A subsequent message identifies the data set not
cataloged.
System Action: The command continues processing.
Programmer Response: Correct the error and recatalog the
data set using the IEHPROGM utility or the Access Method
Services DELETE and DEFINE commands.
Problem Determination: Table I, item 1, 3, 4, 13, 14, 25d, 29,
and 31.
IDC21031 VOLUME IN RECORD CHAIN CANNOT BE
RETRIEVED
Explanation: An Inventory data set error caused a break in the
group or nongrouped volume chain. The next record in the
chain either was not found, or the record indicates that it does
not belong in the chain being processed. A reason code of
X'208' or X'224 was returned from the Mass Storage Volume
Control functions. The error may be caused by another
'~
command updating the Inventory data set while this command
is running.
System Action: Processing continues with the next group, or
processing terminates if the request is for nongrouped
volumes.
Programmer Response: Rerun the command. If there is a
permanent Inventory data set error, contact the system
programmer.
Problem D.etermination: Table I, items 1, 2, 3, 4, 13, 29, and
35c.
name in the catalog, determined that the data set resides on a
device type other than the catalog indicates, or else a
duplicate data set name exists.
System Action: Processing continues with the next data set on
the volume.
Programmer Response: If the device type is incorrect,
uncatalog the data set and then recatalog it with the correct
device type.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, and
34.
IDC21081
IDC23641
00
UNABLE TO PROCESS VOLUME ser
Explanation: Volume ser cannot be processed. A preceding
message indicates the reason why the volume cannot be
processed.
System Action: The command continues with the next volume
to be processed. If there is none, the command terminates.
Programmer Response: Determine from the preceding message
whether a problem exists, and correct it if necessary. Rerun
the command to process the volume.
Problem Determination: Follow the problem determination
actions for the preceding message.
IDC21091
00
REMAINING VOLUMES CANNOT BE PROCESSED
CATALOG ENTRY TYPE FOR DATA SET IS OTHER
THAN NON-VSAM
Explanation: The ULOCATE function, after locating a data set
name in the catalog, determined that the catalog entry type
was not for a VSAM data set, or else a duplicate data set
name exists.
System Action: Processing continues with the next data set on
the volume.
Programmer Response: If the data set entry is cataloged,
rerun the SCRDSET command after restructuring the STEPCAT
concatenation.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, and
34.
Explanation: An error occurred in the Inventory data set that
prevents any more volume records from being read. Remaining
volumes cannot be processed by the command. A preceding
message indicates the type of error encountered with the
Inventory data set.
System Action: The command terminates.
Programmer Response: Contact the system programmer to
correct the problem with the Inventory data set.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, and
35c.
IDC21101
** REMAINING VOLUMES IN GROUP grpname
CANNOT BE PROCESSED
Explanation: An Inventory data set error occurred to prevent
processing down the volume chain for group grpname. The
problem may be temporary, or the Inventory data set may
have permanent errors. A preceding message indicates the
type of error encountered with the Inventory data set.
System Action: Processing continues with the next group to be
processed. If there is none, the command terminates.
Programmer Response: Refer to the preceding message to
determine why processing for this group was terminated.
Contact the system programmer to correct the Inventory data
set if necessary, and rerun the command.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, and
35c.
IDC21111
** REMAINING GROUPS CANNOT BE PROCESSED
Explanation: An error occurred in the InventorY data set that
prevented any more group records from being read. A
preceding message indicates the type of Inventory data set
error.
System Action: The command terminates.
Programmer Response: Refer to the preceding message for
the type of Inventory data set error.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, and
35c.
IDC23601
CATALOG ENTRY FOR DATA SET INDICATES
DIFFERENT DEVICE TYPE
Explanation: The ULOCATE function, after locating a data set
IDC23701
UNABLE TO READ JFCB FOR DO ENTRY ddname
RDJFCB CODE x
Explanation: The system was not able to read the JFCB (job
•
file control block) for the specified DO statement (ddname).
The RDJFCB macro return code was x. This condition generally
occurs when the DO statement was not supplied.
System Action: The command terminates normally.
Programmer Response: Ensure the DO name in the FILE
parameter is correct and there is a corresponding DO card in
the JCL statements.
Problem Determination: Table I, items 1, 2, 3, 4, 13, and 29.
IDC23711
UNABLE TO OBTAIN STORAGE FOR I/O
PROCESSING
Explanation: There was insufficient storage to perform the
necessary I/O processing.
System Action: The command terminates normally.
Programmer Response: Increase the region size for the job
and rerun the command.
Problem Determination: Table I, items 1, 2, 3, 4, 13, and 29.
IDC23721
OPEN ABEND EXIT[dsn
I
VTOC]
Explanation: The OPEN macro encountered an error that
resulted in the OPEN DCB ABEND exit being entered. This
error prevented the opening of the DCB and stopped further
I/O processing. The specified data set (dsn) or the VTOC was
being opened.
System Action: The command terminates normally.
Programmer Response: Examine the write-to-programmer
message issued by the OPEN macro for the specific error
code. Correct the problem and rerun the command.
Problem Determination: . Table I, items 1, 2, 3, 4, 13, and 29.
IDC23731 INVALID PASSWORD dsn
Explanation: One of the following errors occurred:
• The operator did not supply the correct password for the
specified nonVSAM data set (dsn), for the specified VSAM
unique data or index component (dsn), or for a data or
index component within the specified VSAM data space
(dsn).
Section 4: IDC Messages - Access Method Services
4-19
• There is no JOBCAT or STEPCAT DO statement for the
VSAM catalog that owns the volume.
System Action: The command terminates normally. The
requested function cannot be performed.
Programmer Response: If the operator supplied the incorrect
password, do the following:
• Tell the system operator the correct password. The operator
is prompted for the password that corresponds to (1) the
data or index component name or codeword (VSAM data
sets) or (2) the name of the DO statement for the data set
(nonVSAM data sets). Rerun the command.
If there is no JOBCAT or STEPCAT DO statement for the VSAM
catalog, do the following:
• Supply a JOBCAT or STEPCAT DO statement for the catalog
or supply the master password of the VSAM catalog on the
command or via operator prompting. Rerun the command.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 25b, and
29.
IDC23741
CLOSE ABEND EXIT[cIsn
I
VTOC]
Explanation: The CLOSE macro encountered an error that
resulted in the CLOSE DCB ABEND exit being entered. This
error prevented the closing of the DCB and stopped further
I/O processing. The specified data set (dsn) or VTOC was
being closed.
System Action: The command continues processing.
Programmer Response: Examine the write-to-programmer
message issued by the CLOSE macro for the specific error.
Correct the problem and rerun the command if the function
was not performed.
Problem Determination: Table I, items 1, 2, 3, 4, 13, and 29.
IDC23751
** I/O ERROR
VTOC]
[dsn
I
VOLUME LABEL
VOLUME WITH SERIAL volser ALREADY MOUNTED
IN SYSTEM
Explanation: After mounting mass storage volume (volser) the
UCB cannot be posted bec.ause it causes a duplication of
volume label within the system.
System Action: Demounts the mass storage volume. The
command terminates normally.
Programmer Response: Rerun the command after the volume
with the same serial number is demounted.
Problem Determi,nation: Table I, items 1, 2, 3, 4, 13, and 29.
IDC23861
UNIT ASSIGNED TO ddname COULD NOT BE
READING FOR MOUNTING
Explanation: The unit assigned by the DO statement (ddname)
cannot be used to mount needed volumes, because a previous
volume cannot be demounted.
System Action: The command terminates normally.
Programmer Response: Rerun the command. Specify the
correct volume serial on the DO statement. If the same unit is
assigned to the DO statement and the same error occurs,
rerun the command after the operator varies the unusable unit
.
offline.
Problem Determination: Table I, items 1, 2, 3, 4, 13, and 29.
4-20
VS2 System Messages (VS2 Release 3.7)
**
VOLUME volser COULD NOT BE MOUNTED
Explanation: The mount of the specified volume (volser) is
unsuccessful. A preceding message gives the explanation for
this error.
System Action: The command terminates normailly.
Programmer Response: Examine preceding message, correct
the problem, and rerun the command.
Probl.em Determination: Table I, items 1, 2, 3, 4, 13, and 29.
IDC23881
**
VOLUME volser COULD NOT BE DEMOUNTED
Explanation: The demount of the specified volume (volser) is
unsuccessful. A preceding message gives the explanation for
this error.
System Action:
The command terminates normally.
Programmer Response: Examine preceding message, correct
the problem, and rerun the command.
Problem Determination: Table I, items 1, 2, 3, 4, 13, and 29.
IDC23891
~,* DESTAGE OF DATA ON VOLUME volser NOT
SUCCESSFUL
Explanation: The destaging of the specified volume (volser) is
unsuccessful after a successful demount. A preceding message
explains the reason for the error.
System Action: The command cannot perform the next
function because all destaging is not complete.
Programmer Action: Examine preceding message, correct the
problem, and rerun the command. The cartridge of the volume
may need to be replaced via the REPLACEC command.
Problem Determination: Table I, items 1, 2, 3, 4, 13, and 29.
I
Explanation: SYNAD error occured during EXCP I/O processing
for either data set (dsn) the volume label, or the VTOC. Refer
to the preceding message for the cause.
System Action: Processing of the command terminates.
Programmer Response: Refer to the first message, correct any
problems, and rerun the command.
Programmer Determination: Table I, items 1, 2, 3, 4, 13, and
29.
IDC23811
IDC23871
IDC23901
VOLUME volser COULD NOT BE ENQUEUED FOR
EXCLUSIVE USE
Explanation: The enqueue of the specified volume (volser) for
exclusive use cannot be done because the volume serial is
enqueued for shared use.
System Action: The command terminates normally.
Programmer Response: Rerun the command after the volume
is not being used by any other job. Be sure to specify the
volume serial on the DD statement.
Problem Determination: Table I, items 1, 2, 3, 4, 13, and 29.
IDC23911
UNABLE TO ESTABLISH E/STAE ENVIRONMENT RETURN CODE x'nn'
Explanation: The STAE or ESTAE macro returned a non-zero
return code that prevented recovery protection in case of an
abnormal termination of the command. STAE was issued in
VSl; ESTAE in VS2. The primary reason is insufficient storage
to build control blocks.
System Action: Function did not continue.
Programmer Response: Examine the return code, correct the
problem, and rerun the job.
Problem Determination: Table I, items 1, 2, 3, 4, 13, and 29.
IDC23991
CATALOG ENTRY FOR DATA SET INDICATES
DIFFERENT VOLUME
Explanation: The ULOCATE function, after locating the data set
name in the catalog, determined that the data set resides on a
different volume than the catalog indicates, or else a duplicate
data set name exists.
System Action: Processing continues with the next data set on
the volume.
Programmer Response Uncatalog the data set if necessary,
and recatalog it with the correct volume serial number.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, and
34.
IDC24001
MSS REASON CODE IS x' nnnn'
Explanation: The Mass Storage System Communicator reason
code returned as a result of a Mass Storage System
Communicator request. The reason code is "nnnn". See the
publication, "OS/VS Message Library: Mass Storage System
(MSS) Messages", GC3S-1000, for an explanation of the
reason code.
System Action: The function was not performed. The
command terminates normally or attempts to continue.
Programmer Response: See the publication "OS/VS Message
Library: Mass Storage System (MSS) Messages", GC3S-1000,
for the response to the reason code.
IDC24011
MSS POST CODE IS X'nn'
Explanation: The Mass Storage System Communicator
completion code posted in the Event Control Block was "nn".
"nn" = 71 means the request was unsuccessful.
"nn" = 7E means the request was successful, but the staging
pack needs alternate tracks assigned by the utility
programs IEHDASDR or IEHATLAS.
System Action: The function was not performed. The
command terminates normally or attempts to continue.
Programmer Response: Follow the appropriate action which
depends on which POST code is issued.
If the post code was 71, ask the operator if the problem that
occurred while your job was running has been fixed. When it
has, rerun your job.
If the post code was 7E, notify your system programmer that
IEHDASDR should be run the assign alternate tracks to the
staging pack.
Problem Determination: Table I, items 1, 3, 4, 13, 29, and 30.
IDC24021
VOLUME REQUESTED IS NOT AN ACTIVE VOLUME
Explanation: The requested mass storage volume is not in the
Mass Storage Control's Volume Inventory Table. The user is
requesting the wrong volume or the volume is inactive. The
Mass Storage System Communicator reason code is X'OT. See
the publication "OS/VS Message Library: Mass Storage System
(MSS) Messages", GC3S-1000 for more information about the
reason code.
System Action: The command terminates normally.
Programmer Response: Make the mass storage volume
available by either:
• Defining the Mass Storage Volume with the CREATEV
command.
• Activating the Mass Storage Volume with the ADDV
command,
• Inserting and activating the Mass Storage Volume. If the
volume serial number was erroneously specified, change the
serial number. Resubmit the command.
Problem Determination: Table I, items 3, 4, 13, 14, 29, 30,
35a, and 35c.
IDC24031
WORK FILE MUST SPECIFY UNIT IN SDG 0
Explanation: The Mass Storage Volume specified for the work
data set, which is used to copy the Mass Storage Control
tables to, is not mounted Tn a unit in staging drive group O.
The volume must be mounted on the same group as the Mass
Storage Control tables volume. The Mass Storage System
Communicator reason code is X' 1E'. See the publication
"OS/VS Message Library: Mass Storage System (MSS)
Messages", GC3S-1000 for more information about the reason
code.
System Action: The command terminates normally.
Programmer Response: Specify a unit in staging drive group 0
on the DD statement, even though the work data set may be
cataloged. You can use the esoteric name SDGOO created by
the Mass Storage Control Table Create program in the UNIT
parameter of the DD statement, and then rerun the command.
Problem Determination: Table I, items 3, 4, 13, 29, and 30.
IDC24041
VOLUME REQUESTED IS MOUNTED
Explanation: The requested Mass Storage Volume is mounted
and cannot be accessed for the requested function. The
volume may have been mounted on another operating system
when the command was run. The Mass Storage System
Communicator reason code is X'22'. See the publication
"OS/VS Message Library: Mass Storage System (MSS)
Messages", GC3S-1000 for more information about the reason
code.
System Action: The command terminates normally.
Programmer Response: Ensure that you do not have any DD
statements for the volume in the job step if the DD statement
is not required by the command. If you do have a DO
statement for the volume, specify the name of the DO
statement in the FILE parameter of the command so the
command can demount the volume. Be sure to rerun the
command when no other operating system which has shared
access has the volume mounted.
Problem Determination: . Table I, items 3, 4, 13, 30, and 35a.
IDC24051
SPECIFIED CARTRIDGE SERIAL NOT FOUND IN
APPROPRIATE MSC TABLE
Explanation: The cartridge serial number was not found in a
Mass Storage Control table. If the cartridge is supposed to be
a scratch cartridge, the cartridge serial number was not found
in the Mass Storage Control's Scratch Cartridge List for the
Mass Storage Facility specified in the MSF parameter of the
command. If the cartridge was for an inactive volume, the
cartridge serial number was not found in the Mass Storage
Control's Transient Volume Table. The Mass Storage System
Communicator reason code is X'23'. See the publication
"OS/VS Message Library: Mass Storage System (MSS)
Messages", GC3S-1000 for more information about the reason
code.
System Action: The command terminates normally.
Programmer Response: Correct the cartridge serial number
parameter and rerun the command. If running the CREATEV or
COPYV command, make sure the cartridge is a scratch
cartridge in the Mass Storage Facility specfied in the MSF
parameter. You can get a listing of the scratch cartridges
available with the lISTMSF command. If you are running the
EJECTV command, make sure the cartridge serial number
specified is for the volume you want to eject. You can get a
listing of the volume and its cartridge serial numbers using the
lISTMSVI command. If you are ejecting a volume for which
there is no record in the Inventory data set, be sure you have
specified the cartridge serial number of the first cartridge of
the volume. You can get a listing of the cartridge serial
numbers using the lISTMSF command. If you are running the
REPLACEC command, make sure the scratch cartridge
specified in the CARTRIDGE parameter is a scratch cartridge in
the same Mass Storage Facility as the volume.
Problem Determination: Table I, items 3, 4, 13, 29, 30, 35a,
35b, and 35c.
IDC24061
NO SCRATCH CARTRIDGES AVAILABLE IN THE MSF
Explanation: No scratch cartridges remain in the Mass Storage
Facility specified in the MSF parameter. In the case of the
Section 4: IDC'Messages - Access Method Services
4-21
I
• I
REPLACEC command, no scratch cartridges remain in the. Mass
Storage Facility that contains the volume. The Mass Storage
System Communicator reason code is X'24'. See the
publication "OS/VS Message Library: Mass Storage System
(MSS) Messages", GC38-1000 for more information about the
reason code.
. System Action: The command terminates normally.
Programmer Response: Provide more scratch cartridges either
by scratching Mass Storage Volumes, or by entering new
cartridges through the cartridge access station. Ensure that the
correct Mass Storage Facility is specified in the MSF
parameter. Rerun the command.
Problem Determination: Table I, items ~, 4, 13, 14, 29, 30,
3Sa, and 3Sb.
IDC24071
SEQUENCE ONE CARTRIDGE NOT IN MSF
Explanation: The first cartridge of the requested mass storage
volume is not in the Mass Storage Facility. The Mass Storage
System Communicator reason code is X'26'. See the
publication "OS/VS Message Library: Mass Storage System
(MSS) Messages", GC38-1000 for more information about the
reason code.
System Action: The command terminates normally.
Programmer Response: Insert the missing Mass Storage
Volume cartridge and rerun the command.
Problem Determination: Table I, items 3, 4, 13, 14, 29, 30,
3Sa, and 3Sc.
IDC24081
SEQUENCE TWO CARTRIDGE NOT IN MSF
Explanation: The second cartridge of the requested mass
storage volume is not in the Mass Storage Facility. The Mass
Storage System Communicator reason code is X'2A'. See The
publication "OS/VS Message Library: Mass Storage System
(MSS) Messages", GC38-1000 for more information about the
reason code.
System Action: The command terminates normally.
Programmer Response: Insert the missing Mass Storage
Volume cartridge and rerun the command.
Problem Determination: Table I, items 3, 4, 13, 14, 29, 30,
3Sa, and 3Sc.
IDC24091 VOLUME SPECIFIED IS CURRENTLY BEING
DESTAGED
Explanation: Destaging as a result of a demount for the
specified Mass Storage Volume is in progress. This situation
occurs if the volume was mounted by another operating
system at the time the job was run. The Mass Storage System
Cummunicator reason code is X'2B'. See the publication
"OS/VS Message Library: Mass Storage System (MSS)
Messages", GC38-1000 for more information about the reason
code.
System Action: The command terminates normally.
Programmer Response: Rerun the job when the mass storage
volume becomes available.
Problem Determination: Table I, items 3, 4, 13, 29, 30, and
3Sa.
IDC24101
NOT ENOUGH SPACE IN WORK DATA SET TO COPY
TABLES
Explanation: There was insufficient space to perform the copy
of the Mass Storage Control tables. The Mass Storage System
Communicator reason code is X' 49'. See the publication
"OS/VS Message Library: Mass Storage System (MSS)
Messages", GC38-1000 for more information about the reason
code.
System Action: The command terminates normally.
4-22
VS2 System Messages (VS2 Release 3.7)
Programmer Response: If you are running the LlSTMSF
command, ensure that the work data set contains 40
contiguous cylinders in the first extent. If you are running the
TRACE command, ensure that the work data set contains 16
contiguous cylinders in the first extent whether you are
dumping one or both trace areas.
Problem Determination: Table I, items 3, 4, 13, 14, 2Sa, 29,
and 30.
IDC24111
ERROR EJECTING SEQUENCE TWO CARTRIDGE
Explanation: Only the first cartridge of the volume has been
ejected. The second cartridge was not ejected due to an
equipment error. In most cases, sense data for the equipment
error has already been reported in previous sense data. The
Mass Storage System Communicator reason code is X' 4C'. See
the publication "OS/VS Message Library: Mass Storage System
(MSS) Messages", GC38-1000 for more information about the
reason code.
System Action: The job completes normally.
Programmer Response: Rerun the job once because the
problem may be temporary and also to ensure that sense data
is recorded.
Problem Determination: Table I, items 3, 4, 13, 30, and 3Sa.
IDC24141
STAGING DRIVE GROUP SPECIFIED IS INVALID
Explanation: An invalid staging drive group was specified on
the command. The Mass Storage System Communicator reason
code is X'BS'. See the publication "OS/VS Message Library:
Mass Storage System (MSS) Messages", GC38-1000 for more
information about the reason code.
System Action: The command terminates normally.
Programmer Response: Specify a valid staging drive group
number. The staging drive group number must have been
defined by the Mass Storage Control Table Create program.
Rerun the command.
Problem Determination: Table I, items 3, 4, 13, 29, and 30.
IDC241S1 VOLUME REQUESTED IS NOT AN ACTIVE VOLME
Explanation: The requested volume was not found on the Mass
Storage Control's Volume Inventory Table. The incorrect
volume has been specified or the volume is not an active
volume. The Mass Storage System Communicator reason code
is X'C4'. See the publication "OS/VS Message Library: Mass
Storage System (MSS) Messages", GC38-1000 for more
information about the reason code.
System Action: The command terminates normally.
Programmer Response: Make sure the volume serial number is
specified correctly. Activate the volume if it is inactive via the
ADDV command, inserting the cartridges of the volume into
the Mass Storage Facility first if necessary.
Problem Determination: Table I, items 3, 4, 13, 14, 29, 30,
3Sa, and 3Sc.
IDC24161
NEW SERIAL ALREADY ASSIGNED TO ANOTHER
VOLUME
Explanation: The new volume serial specified on the command
already assigned to another volume recorded in the Inventory
data set. The Mass Storage System Communicator reason
code is X'204'. See the publication "OS/VS Message Library:
Mass Storage System (MSS) Messages", GC38-1000 for more
information about the reason code.
System Action: The command terminates normally. If the
volume serial has already been changed in the volume label,
the command attempts to restore the original volume serial.
Programmer Response: If you are executing the STOREY
command, you can use the desired new serial if you specify
the EJECT and NORECORD parameters. Otherwise, you must
select a new volume serial or in some way remove the volume
that currently has that volume serial from the Inventory data
set, either by scratching the volume, by ejecting it and
removing its record, or by renaming it.
Problem Determination: Table I, items 1, 3, 4, 13,29, 35a,
and 35c.
IDC24171
RECORD NOT FOUND IN INVENTORY
Explanation: A required record could not be found in the
Inventory data set. The Mass Storage System Communicator
reason code is X'208'. See the publication "OS/VS Message
Library: Mass Storage System (MSS) Messages", GC38-1000
for more information about the reason code.
System Action: The command either terminates normally or
attempts to continue.
Programmer Response: Ensure that the volume serial number
and the cartridge serial number (if specified) are correct.
Ensure that the group name is correct. Ensure that the copy
date is correct. Rerun the command. If the volume was
entered while the Mass Storage Volume Control portion of the
Mass Storage System Communicator was disabled, there is no
eject for the volume. You must use the EJECTV command to
eject the volume, then reenter the volume while the Mass
Storage Volume Control portion of the Mass Storage System
Communicator is enabled. If everything has been correctly
specified and the volume was not entered while the Mass
Storage Volume Control portion of the Mass Storage System
Communicator was disabled, contact your programming
support group because the Inventory may need to be restored
from the backup copy and the Journal data set.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, 35a,
and 35c.
IDC24181
GROUP NAME OR NEW SERIAL ALREADY EXISTS IN
INVENTORY
Explanation: A new record was requested to be written in the
Inventory dataset; however, a record with that key already
exists. This situ(!tion occurs if the group name or new volume
serial specified on the command already exists in the Inventory
data set. The Mass Storage System Communicator reason
code is X'20A'. See the publication "OS/VS Message Library:
Mass Storage System (MSS) Messages", GC38-1000 for more
information about the reason code.
System Action: The command continues processing.
Programmer Response: Make sure the group name or volume
serial to be assigned is not already recorded in the Inventory.
Specify a unique group name or volume serial and rerun the
command.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, 35a,
and 35c.
IDC24191
RECORD PARAMETER CANNOT BE SPECIFIED FOR
DUPLICATE VOLUME
Explanation: The volume being ejected is a duplicate volume.
Retaining a record for a duplicate volume in the Inventory data
set is not allowed; therefore, the RECORD parameter cannot
be specified. The Mass Storage System Communicator reason
code is X'20E'. See the publication "OS/VS Message Library:
Mass Storage System (MSS) Messages", GC38-1000 for more
information about the reason code.
System Action: The volume is not ejected.
Programmer Response: Do not specify the RECORD parameter.
Rerun the command.
Problem Determination: Table I, items 1, 2, 3, 4,. 13, 29, 35a,
and 35c.
IDC24201
RECORD PARAMETER MUST BE SPECIFIED FOR
BASE VOLUME WITH COPIES
Explanation: The volume being ejected is a base volume which
has copies recorded in the Inventory data set. The base record
must be retained in the Inventory data set if copy records
exist; therefore, the NORECORD parameter is not allowed.
System Action: The volume is not ejected.
Programmer Response: The programmer should do one of the
following:
• Scratch the copies (with the SCRATCHY command).
• Eject the copies and remove their records (with the EJECTV
command).
• Remove the copy records if the copies are ejected already
(with the REMOVEVR command); then rerun the command
to eject the base volume and then its record can be
removed. If you want to retain the copy records, rerun the
command to eject the base volume but do not specify the
NORECORD parameter.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 14, 29,
35a, and 35c.
IDC24211
VOLULE HAS COPIES RECORDED IN INVENTORY
Explanation: The Inventory record for the volume whose
record is to be removed indicates that copy records still exits
for the volume; therefore the volume record cannot be
removed. The Mass Storage System Communicator reason
code is X'218'. See the publication "OS/VS Message Library:
Mass Storage System (MSS) Messages", GC38-1000 for more
information about the reason code.
System Action: The volume record is not removed.
Programmer Response: If the copies are still in the Mass
Storage Facility, scratch them or eject them. Then, rerun the
REMOVEVR command with the ALL parameter to remove the
records for all the copies as well as the record for the base
volume.
Problem Determination: Table I, items 1, 3, 4, 13, 14, 29,
35a, and 35c.
IDC24221
CARTRIDGES STILL IN MSF
Explanation: The record in the Inventory data set for the base
volume or copy being ejected indicates that one or more
cartridges of the volume are still in the Mass Storage Facility;
therefore, the record cannot be removed. The Mass Storage
System Communicator reason code is X'21A'. See the
publication "OS/VS Message Library: Mass Storage System
(MSS) Messages", GC38-1000 for more information about the
reason code.
System Action: The record is not removed from the Inventory;
the command continues processing.
Programmer Response: Run the EJECTV command to eject the
volume specifying the NORECORD parameter.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 14, 29,
35a, and 35c.
IDC24231
GROUP RECORD· NOT FOUND IN INVENTORY
Explanation: The Mass Storage System Communicator reason
code is X'205': See the publication "OS/VS Message Library:
Mass Storage System (MSS) Messages", GC38-1000, for more
information about the reason code. The group specified on the
command does not exist in the Mass Storage Volume Control
Inventory data set.
System Action: The command terminates normally.
Programmer Response: Correct the group name on the
command or use the CREATEG command to create the group.
Rerun the command.
Section 4: IDC Messages - Access Method Services
4-23
•
Problem Determination: Table I, items 1, 3, 4, 13, 29, and
35c.
IDC24281
GROUP LACKS RETPD OR VOLUME IS NOT
GENERAL -TO/FOR INVALID
Explanation: The group record. in the Inventory data set
indicates volumes are still assigned to the group; therefore,
the group cannot be scratched. The Mass Storage System
Communicator reason code is X'21C'. See the publication
"OS/VS Message Library: Mass Storage System (MSS)
Messages", GC38-1000 for more information about the reason
code . .
System Action: The command terminates normally.
Programmer Response: Remove the volumes from the group
and then rerun the command. Either scratch the volumes, eject
them with the NORECORD parameter, remove their records if
they are already ejected, or modify the volumes so they no
longer belong to the group.
Problem Determination: Table I, items 1, 3, 4, 13, 14, 29,
35a, and 35c.
Explanation: The TO or FOR parameter was specified on the
command but the volume was either:
• Not a general-use volume.
• The group the volume is assigned to or is being assigned to
does not have a retention period.
The Mass Storage System Communicator reason code is
X'227'. See the publication "OS/VS Message Library: Mass
Storage System (MSS) Messages", GC38-1000 for more
information about the reason code.
System Action: The command terminates normally. No
modification is performed.
Programmer Response: Make sure you have specified the
correct volume serial number and group name. Do not specify
an expiration data for the volume unless it is ~m active,
general-use volume assigned to a group that has a retention
period.
Problem Determination: Table I, items 1, 3, 4, 13, 29, 35a,
and 35c.
IDC24251
IDC24291
IDC24241
GROUP RECORD NOT SCRATCHED BECAUSE
VOLUMES ASSIGNED TO IT
CARTRIDGE IS ASSIGNED TO A DIFFERENT VOLUME
Explanation: The cartridge serial number specified on the
command was found in the Inventory data set, but the
cartridge serial number is assigned to a volume that has a
different volume serial number than that specified on the
command. The Mass Storage System Communicator reason
code is X'21D'. See the publication "OS/VS Message Library:
Mass Storage System (MSS) Messages", GC38-1000 for more
information about the reason code. '
System Action: The command terminates normally.
Programmer Response: Specify the correct volume serial and
cartridge serial numbers and rerun the command. If the correct
volume and cartridge serial numbers have been specified,
contact the programming support group because the Inventory
data set may need to be restored from a backup copy and the
Journal data set.
Problem Determination: Table I, items 1, 2, 3,4, 13, 29, 35a,
and 35c.
IDC24261
GROUP NAME CONTAINS SPECIAL CHARACTERS
Explanation: The group name specified on command contains
invalid characters; only alphameric and national characters are
allowed in a group name. The Mass Storage System
Communicator reason code is X'225'. See the publication
"OS/VS Message Library: Mass Storage System (MSS)
Messages", GC38-1000 for more information about the reason
code.
System Action: The group is not created.
Programmer Response: Correct the group name and rerun the
command.
Problem Determination: Table I, items 1, 3, 4, 13, 29, and
35c.
IDC24271
SYSGROUP MUST NOT BE SCRATCHED
Explanation: A request was made to scratch SYSGROUP. You
are not allowed to scratch SYSGROUP. The Mass Storage
System Communicator reason code is X'226'. See the
publication 'lOS/VS Message Library: Mass Storage System
(MSS) Messages", GC38-1000 for more information about the
reason code.
System Action: SYSGROUP is not scratched.
Programmer Response: None.
Problem Determination: Table I, items 1, 3, 4, 13, 29, and
35c.
4-24
VS2 System Messages (VS2 Release 3.7)
ATTRIBUTES DO NOT AGREE WITH GROUP
ATTRIBUTES
Explanation: The attributes (bind/nobind, exclusive/shared,
dasderase/nodasderase, readonly/readwrite) specified for the
volume do not agree with those specified in the group record.
Since the volume is a general-use volume in the group or is
being made a general-use volume in the group, the attributes
of the volume must be the same as those for the group. The
Mass Storage System Communicator reason code. is X'228'.
See The publicati<>n "OS/VS Message Library: Mass Storage
System (MSS) Messages", GC38-1000 for more information
about the reason code.
System Action: The command terminates normally.
Programmer Response: Make sure that the attributes you
specify on the command for the volume are the same as the
attributes specified in the group record, or do not specify any
attributes at all on the command and the command will assign
the appropriate attributes. If you have not specified any
conflicting attributes on the command, ensure that. you were
not modifying the group attributes at the same time you were
running the command.
Problem Determination: Table I, items 1, 3, 4, 13, 19, 35a,
and 35c.
IDC24311
RECORD PARAMETER CANNOT BE SPECIFIED - NO
INVENTORY RECORD
Explanation: There is no record in the Inventory data set for
the volume being ejected; therefore the RECORD parameter
cannot be specified. The Mass Storage System Communicator
reason code is X'235'. See the publication "OS/VS Message
library: Mass Storage System (MSS) Messages", GC38-1000
for more information about the reason code.
System Action: The command terminates normally. The
volume was not ejected.
Programmer Response: Make sure that the correct volume
serial and cartridge serial numbers are specified. If the volume
was manually entered in the Mass Storage Facility while the
Mass Storage Volume Control portion of the Mass Storage
System Communicator was disabled, there is no record in the
Inventory data set. Rerun the command and do not specify the
RECORD parameter. If there should be a record in the
Inventory data set, contact the programming support group.
The Inventory may need to be restored from the backup copy
and the Journal data set.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, 35a,
and 35c.
IDC24321
VOLUME ENTERED WHILE MSVC DISABLED RECORD NOT COMPLETE
Explanation: The Inventory record for the volume indicates the
volume was entered into the Mass Storage Facility when the
Mass Storage Volume Control portion of the Mass Storage
System Communicator was disabled. The library identification
fields are still null. The volume cannot be activated because of
the incomplete reco~d. The Mass Storage System
Communicator reason code is X'236'. See the publication
"OS/VS Message Library: Mass Storage System (MSS)
Messages", GC38-1000 for more information about the reason
code.
System Action: The command terminates normally.
Programmer Response: Eject the volume, then reenter it while
the Inventory Control portion of the Mass Storage System
Communicator is enabled. Rerun the command.
Problem Determination: Table I, items 1, 3, 4, 13, 14, 29,
35a, and 35c.
member name in parentheses, which is not an allowable
combination.
System Action: Processing continues.
Programmer Response: Remove the * indicating a generic
entry name or remove the member name to achieve the
desired alteration.
IDC25521
IDC25531
IDC24331
CARTRIDGES NO LONGER ASSIGNED TO SPECIFIED
VOLUME
Explanation: The volume record for the requested volume
indicates the cartridges have been reassigned to a different
volume. This situation occurs when a volume is ejected with
the RECORD parameter, used in a different Mass Storage
System, and then reinstated into the original Mass Storage
System with at least one cartridge serial number that is the
same but with a different volume serial number. The Mass
Storage System Communicator reason code is X'237'. See the
publication "OS/VS Message Library: Mass Storage System
(MSS) Messages", GC38-1000 for more information about the
reason code.
System Action: The command terminates normally.
Programmer Response: Remove any copy volume records for
the requested volume from the Inventory data set by
scratching the copies or by ejecting the copies. Remove the
base volume record and all copy records for the requested
volume. Make sure you have specified the correct volume
serial number and rerun the command.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 14, 29,
35a, and 35c.
IDC24341
COPIES RECORDED IN INVENTORY - NEW SERIAL
NOT ALLOWED
Explanation: The volume being renamed has copies recorded
in the Inventory data set. Because the serial number of a copy
cannot be changed, you are not allowed to change the serial
number of the base volume. The Mass Storage System
Communicator reason code is X'238'. See the publication
"OS/VS Message Library: Mass Storage System (MSS)
Messages", GC38-1000 for more information about the reason
code.
System Action: The command terminates normally. If the
volume serial has already been changed in the volume label,
the command attempts to restore the original volume serial.
Programmer Response: Before renaming the volume, scratch
the existing copies or else eject them with the NORECORD
parameter. However, note that when the copies are reinstated,
they will no longer be considered copies.
Problem Determination: Table I, items 1, 3, 4, 13, 29, 35a,
and 35c.
IDC25331
MEMBER CANNOT BE SPECIFIED WITH A GENERIC
NAME
Explanation: A generic entry name was given followed by a
ENTRY TYPE IS INVALID FOR DELETE
Explanation: The types of entries that can be deleted are
cluster, user catalog, master catalog, non-VSAM, space; alias,
GOG base, path and alternate index.
System Action: The entry is not deleted. The rest of the
entries are deleted if possible.
Programmer Response: If the user thinks the entry is one of
these types, he should list that entry with LIST CAT to check
the type field.
Problem Determination: Table I, items 3, 4, 29.
ERASE OPTION IS INVALID FOR ENTRY TYPE
Explanation: Only VSAM clusters and alternate indexes can be
•
erased.
System Action: The entry is not deleted. The remaining VSAM
entries, if any, are deleted.
Programmer Response: Resubmit the request without the
ERASE parameter.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IDC25541
DYNAMIC ALLOCATION FAILED OR FILE WAS NOT
CODED WITH SCRATCH
Explanation: Dynamic allocation failed. Preceding messages
(lDC39031 and IDC39051) indicate the reason for the failure.
System Action: Processing is terminated for this entry.
Programmer Response: Refer to the dynamic allocation error
messages or supply a FILE parameter.
Problem Determination: Table I, items 1, 3, 4, 5, 29.
IDC25571
SCRATCH NOT AVAILABLE FOR TYPE OF OBJECT
TO BE DELETED
Explanation: The SCRATCH option is invalid for the entry type
being deleted. SCRATCH is invalid for a VSAM master catalog,
user catalog, path, alias, and GOG base.
System Action: Processing for the entry is terminated.
Programmer Response: Ensure that SCRATCH is valid for all
entries specified, or do not use the SCRATCH option.
IDC25591
MEMBER CANNOT BE SPECIFIED WITH A GENERIC
NAME
Explanation: The generic name used is followed by a member
name enclosed in parentheses. This combination is invalid.
System Action: Processing for this entry is terminated.
Programmer Response: Remove the * which indicates a
generic entry name or remove the member name.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC25631
ALLOCATION/VOLUME PARAMETER IS INVALID FOR
ENTRY TYPE(S)
Explanation: A L1STCAT command request for allocation or
volume information conflicts with the desired entries or types
of entries.
System Action: The LlSTCAT command attempts recovery to
list that part of the request that does not conflict.
Programmer Response: Rerun the job with LlSTCAT
parameters that are compatible with the fields specification.
Problem Determination: Table I, items 3, 4, 29.
Section 4: IDC Messages - Access Method Services
4-25
•
IDC26161
PATH dsn WAS NOT SUCCESSFULLY IMPORTED
Explanation: IMPORT was not able to successfully define path
dsn over the object being imported. The most likely cause is a
duplicate object name already in the catalog.
System Action: Processing continues, attempting to define any
remaining paths whose catalog information is stored on the
portable data set.
Programmer Response: Determine if the paths whose defines
failed already exist in the catalog. If so, delete and redefine
them.
Problem Determination: Table I, items 3, 4, 26b, 34a.
IDC26181
INVALID OBJECTS SUBPARAMETER FOR PATH dsn
Explanation: An OBJECTS subparameter other than NEWNAME
or FILE was specified for path object dsn.
System Action: IMPORT processing continues, attempting to
define any remaining paths from the portable data set.
Programmer Response: Probable user error. Correct the
OBJECTS parameter and resubmit the job.
Problem Determination: Table I, items 3, 4, 26b.
IDC26201
OBJECT TYPE NOT SUPPORTED FOR OBJECT dsn
Explanation: The object named was not of a type that could
be defined in the operating system (for example, an OS/VS2
generation data group in an OS/VSl system). In VS2 this
indicates a system error.
System Action: Processing is continued with the next object
on the portable data set.
Programmer Response: Do the problem determination action.
Problem Determination: Table I, items 2, 3, 4, and 29.
IDC26211
IMPORTRA FAILED FOR dsn
Explanation: The object named could not be imported.
System Action: Processing is continued with the next object
on the portable data set.
Programmer Response: Determine the cause of the failure by
examining previous messages on the SYSPRINT output, correct
the problem, and rerun the job.
IDC26301
DUPLICATE DATA SET NAME IN VSAM CATALOG
Explanation: A duplicate data set name was found in the
VSAM catalog while attempting to convert an OS catalog entry.
System Action: An associated message identifies the entry not
converted.
Programmer Response: The duplicate name must be resolved.
Problem Determination: Table I, items I, 3, 4, 29.
IDC26401
dsn NOT AN AIX
Explanation: The data set identified by dsnis not an alternate
index or a path over an alternate index. The data set name
was specified in (1) job control identified via the OUTFILE
dname subparameter or (2) the OUTDATASET dsname
subparameter. The OUTFILE data set must be a defined
alternate index or a path over the alternate index.
System Action: Processing is terminated for this OUTFILE or
OUTDATASET subparameter. However, processing continues
with any other subparameters specified in the OUTFILE or
OUTDATASET parameter.
Programmer Response: The data set name in the job control
identified via the OUTFILE dname subparameter or the data set
name specified in the OUTDATASET subparameter must be
corrected to be that of a defined alternate index or a path
over an alternate index. Then resubmit the job.
Problem Determination: Table I, items 2, 3, 4, 29, 34b.
4-26
VS2 System Messages (VS2 Release 3.7)
IDC26421
dsn NOT RELATED TO BASE
Explanation: The data set identified by dsn is an alternate
index or a path over an alternate index, but the alternate index
is not related to the base cluster. identified via the INFILE or
INDATASET parameter. All alternate indexes identified via the
OUTFILE or OUTDATASET parameter of the BLDINDEX
command must have been defined as being related to the base
cluster identified via the INFILE or INDATASET parameter. This
relationship is established via the RELATE parameter in the
DEFINE ALTERNATEINDEX command.
System Action: Processing is terminated for this alternate
index. However, processing continues for any other alternate
indexes identified via the OUTFILE or OUTDATASET parameter.
Programmer Response: Either the alternate index identified via
the OUTFILE or OUTDATASET parameter or the base cluster
identified via the INFILE or INDATASET parameter must be
corrected so that the proper relationship exists. If the alternate
index was defined improperly, it must be deleted and redefined
with the proper relationship specified in the RELATE
parameter. Then resubmit the job.
Problem Determination: Table I, items 2, 3, 4, 29, 34b.
IDC26471
INSUFFICIENT STORAGE TO OBTAIN BUFFERS AND
WORKAREAS
Explanation: BLDINDEX encountered a failure when attempting
to obtain storage for buffers, workareas and a minimum sort
area. (see OS /VS2 Access Method Services for a discussion of
virtual storage considerations in BLDINDEX.) This is the
amount of storage required to build one alternate index. The
name of the alternate index is given in a subsequent message.
System Action: Processing is terminated for this alternate
index. However, BLDINDEX attempts to process any other
alternate indexes identified via the OUTFILE or OUTDATASET
parameter.
Programmer Response: Increase the virtual storage region size
and resubmit the job.
Problem Determination: Table I, items 2, 3, 4, 29.
IDC26481
JOB CONTROL CARDS FOR EXTERNAL SORT
MISSING ORIN ERROR
Explanation: If this message occurs by itself, the user
specified the EXTERNALSORT parameter, but did not provide
the proper job control for the sort work files. (See OS /VS2
Access Method Services for a discussion of the requirements
for sort work file job controL) If this message is preceded by
IDC26491 or IDC2650l, BLDINDEX was not able to complete an
internal sort and proper job control for the external sort work
files was not supplied. The alternate index being built is named
in a subsequent message.
System Action: Processing is terminated for this alternate
index. However, BLDINDEX attempts to process any other
alternate indexes specified via the OUTFrLE or OUTDAT ASET
parameter.
Programmer Response: Correct the external sort work file job
control and resubmit the job. Alternatively, provide enough
virtual storage so that an internal sort can be performed.
Problem Determination: Table I, items 2, 3, 4, 29.
IDC26491
INSUFFICIENT STORAGE TO PERFORM INTERNAL
SORT
Explanation: Although BLDINDEX was able to obtain a
minimum amount of virtual storage to start the sort, it was less
than the amount calculated to be required for the entire sort
(based on the number of records in the base cluster statistic
stored in the VSAM Catalog entry for the base cluster). Under
these circumstances, BLDINDEX attempts to prepare for an
external sort. This message is issued only when proper job
control for the external sort work files was not supplied.
System Action: Processing is terminated for this alternate
index. However, BLDINDEX attempts to process any other
alternate indexes specified via the OUTFILE or OUTDAT ASET
parameter.
Programmer Response: Correct t~e external sort work file job
control and resubmit the job. Alternatively, provide enough
virtual storage so that an internal sort can be performed.
Problem Determination: Table I, items 2, 3, 4, 29.
IDC26501
INSUFFICIENT STORAGE TO FINISH INTERNAL SORT
Explanation: During initialization, BLDINDEX calculates the
\
amount of storage required for an internal sort. This
calculation is based on the number of records in the base
cluster statistic stored in the VSAM Catalog entry for the base
cluster. In the case of this message, BLDINDEX was able to
obtain enough virtual storage to meet the calculated
requirement. However, the statistic was erroneously low
(probably due to a failure during a close of the base cluster)
and the initial amount of storage obtained was exhausted.
Undex these circumstances, BLDINDEX must perform an
external sort. This message is issued only when proper job
control for the external sort work files was not supplied.
System Action: Processing is terminated for this alternate
index. However, BLDINDEX attempts to process any other
alternate indexes specified via the OUTFILE or OUTDATASET
parameter.
Programmer Response: Correct the sort work file job control.
Alternatively, delete the alternate index, use the EXPORT
command to create a portable copy of the base cluster,
followed by an IMPORT command to rebuild the base cluster.
This action will correct the erroneous statistic. Then redefine
the alternate index. Resubmit the job.
Problem Determination: Table I, items 2, 3, 4, 29.
information regarding the entry identified· by dsn. This indicates
a serious catalog error since the information requested should
be present for all catalog entries, namely: entry type,
associated objects and AMDSB control block (for data
objects).
System Action: If the dsn is the base cluster, BLDINDEX
processing is terminated. If it is an alternate index or a path
over an alternate index, processing is terminated for the
alternate index; however, BLDINDEX attempts to process any
other alternate indexes identified via the OUTFILE or
OUTDATASET parameter.
Programmer Response: Do the problem determination actions.
Problem Determination: Table I, items 2, 3, 4, 29, 34b.
IDC26561
the base cluster or alternate index (identified by dsn) failed.
Message IDC30091 precedes this message and gives the
catalog return code. Refer to that message for an explanation
of the code. The dsname given in this message is that
specified via the INFILEjlNDATASET or OUTFILEjOUTDATASET
parameter. The locate failure may have been against the
•
named object or an object associated with the named object
(for example, the alternate index itself, if the named object is
a path over the alternate index).
System Action: If the failure is associated with the base
cluster, processing is terminated for the entire BLDINDEX
command. If the failure is associated with an alternate index,
processing is terminated for the alternate index; however,
BLDINDEX attempts to process· any other alternate indexes
identified via the OUTFILE or OUTDATASET parameter.
Programmer Response: Correct the error as explained for the
return code and resubmit the job.
Problem Determination: Table I, items 2, 3, 4, 29.
IDC26601
IDC26511
DEFINE OF SORT WORK FILES FAILED
Explanation: In preparing for an external sort BLDINDEX
attempts to dynamically define two sort work files. However,
the define was rejected by VSAM catalog management. This
message is preceded by either message IDC30071 or IDC30091
giving the VSAM catalog return code. Refer to the appropriate
message for an explanation of the code.
System Action: Processing is terminated for this alternate
index. However, BLDINDEX attempts to process any other
alternate indexes specified via the OUTFILE or OUTDATASET
parameter.
Programmer Response: Correct the error as explained for the
return code and resubmit the job.
Problem Determination: Table I, items 2, 3, 4, 29.
IDC26541
dsn WAS NOT BUILT
Explanation: A terminating error was encountered for the
alternate index identified by dsn. The message containing the
terminating error precedes this message.
System Action: Processing is terminated for this alternate
index. However, BLDINDEX attempts to process any other
alternate indexes identified via the OUTFILE or OUTDATASET
parameter.
Programmer Response: Depends on the error encountered.
Refer to the action described for the individual error.
Problem Determination: Table I, items 2, 3, 4, 29, 34b.
IDC26551
UNABLE TO LOCATE ATTRIBUTES OF dsn
LOCATE FAILED FOR dsn
Explanation: The VSAM Catalog locate function issued against
INVALID ENTRY TYPE IN CATALOG, OBJECT
BYPASSED
Explanation: The entry type field indicates the object being
exported is not a VSAM cluster, alternate index, user catalog,
nonVSAM object, or OSjVS2 generation data group.
System Action: Processing for the object is terminated.
Programmer Response: Redefine the object in error. For the
object name, see the following second-level message.
Problem Determination: Table I, items 2, 3, 4, 29.
IDC26661 ENTRY NAME SPECIFIED CANNOT BE FOUND IN
SPECIFIED CRA
Explanation: The data set named in the ENTRIES parameter of
the EXPORTRA command cannot be found in the catalog
recovery area (CRA) specified. See message IDC06741 for the
name of that unlocated data set.
System Action: Processing of this object is terminated and
processing of the next object begins.
Programmer Response: Verify the name and CRA of the data
set to be exported using the LlSTCRA command.
IDC26681 DATA SET NOT EXPORTED, VOLUME ser REQUIRED
BUT NOT SUPPLIED
Explanation: Synchronization 'checking was attempted on a
volume not included in the list of volumes in the CRA keyword.
System Action: The VSAM entry is not processed.
Programmer Response: Add the volume serial number to the
CRA keyword and rerun the job.
Explanation: The VSAM Catalog locate function issued (by
BLDINDEX) has been unable to obtain all the necessary
Section 4: IDC Messages - Access Method Services
4-27
•
IDC26711
WILL NOT PROCESS CRA ON VOLUME ser,
DIFFERENT CATALOG NAME
Explanation: This volume does not belong to the catalog
named in the following message.
System Action: Processing of this volume is discontinued.
Programmer Response: Rerun the job with the correct catalog
name.
IDC26731
CONFLICTING JCL SPECIFICATIONS FOR DNAME
dname
Explanation: Incorrect volume information was specified in the
JCL or EXPORTRA command. Either the CRA dna me is missing
from the job control or. is misspecified in EXPORTRA, or more
than a single volume is specified in the job control for a CRA.
System Action: Processing for this request is terminated.
Programmer Response: Correct the volume information in error
and rerun the job.
IDC26751
DUPLICATE NAME ENCOUNTERED, NAME ON
VOLUME ser BYPASSED
Explanation: Duplicate names were found in the catalog
recovery areas (CRAs) on two different volumes.
System Action: The name specified in the following
second-level message is skipped.
Programmer Response: If the copy of the data set skipped
was on a volume you did not want skipped, rerun the job
specifying only the desired volume and data set.
IDC26771
**
DATA SET NOT EXPORTED
Explanation: An error occurred or a catalog field could not be
located for the object being exported.
System Action: Processing of the EXPORTRA command for the
object is terminated.
Programmer Response: Determine the type of error from the
preceding message, and redefine the object if necessary.
IDC26811
M
VOLUME volser NOT CREATED
Explanation: The volume was not created for the volume serial
number specified by (volser). A preceding message explains
the error.
System Action: The command does not attempt to create any
subsequent volumes and terminates normally.
Programmer Response: Correct the error as indicated in the
preceding message and rerun the command.
IDC26841
**
VOLUME volser NOT INITIALIZED
Explanation: The newly created volume (volser) was not
initialized with a volume label and an empty VTOC. A
preceding message explains the error.
System Action: The command scratches the partially created
volume and then terminates processing normally.
Programmer Response: Correct the error as indicated in the
preceding message and rerun the command requesting
creation of the volumes not created.
IDC26851
M
NO ATTEMPT MADE TO CREATE ADDITIONAL
VOLUMES
Explanation: An error occurred preventing the creation of all
volumes requested. A preceding message explains the error.
System Action: The command terminates normally.
Programmer Response: Correct the error indicated in
preceding message and rerun the command requesting
creation of the volumes not created.
4-28
VS2 System Messages (VS2 Release 3.7)
IDC26871
** PARTIALLY CREATED VOLUME volser NOT
SCRATCHED
Explanation: The partially created volume (volser) was not
scratched during back out because an error occurred. A
preceding message explains the error.
System Action: The command terminates normally. The
volume record in the Inventory data set for the volume
indicates the volume was incompletely created.
Programmer Response: Correct the error indicated in the
preceding message.
Run SCRATCHY to scratch the partially created volume before
rerunning CREATEV to recreate the same volume. A DO
statement is not required even if the partially created volume
is active. If a DO statement is provided, deferred mounting
must be specified. SCRATCHY will bypass the empty VTOC
check of the partially created volume.
If CREATEV terminates without indicating the status of the
volume create operation, LlSTMSVI can be run to determine
whether the volume is flagged for recovery purposes. If the
incomplete create flag is set in the volume record, LlSTMSVI
not only lists the standard information for the volume but also
highlights the volume report with a note that a create
operation failed for the preceding volume.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, 35a,
and 35c.
IDC26881
**
INCOMPLETE VOLUME CREATION FLAG NOT
RESET FOR VOLUME volser
Explanation: The recovery flag for incomplete volume creation
was not turned off in the Inventory record after new volume
creation was completed for volume (volser). A preceding
message explains the error.
System Action: The command scratches the partially created
volume.
Programmer Response: Correct the error indicated in the
preceding message and rerun the command.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, 35a,
and 35c.
IDC26891
INSUFFICIENT NUMBER OF CARTRIDGES SPECIFIED
ON COMMAND
Explanation: The number of cartridges specified in the
CARTRIDGE parameter is insufficient to create the number of
new volumes requested.
System Action: The command creates as many volumes as
possible; then terminates normally.
Programmer Response: Specify sufficient cartridges in the
CARTRIDGE parameter for all volumes to be created or do not
specify any cartridges in the CARTRIDGE parameter and rerun
the command.
IDC27521
**
CARTS csnl cns2 NOT SCRATCHED FOR volser
Explanation: The requested volume (volser) was not scratched
csn 1 and csn2 identify the cartridges not scratched.
System Action: The command terminates normally.
Programmer Response: Correct the error indicated in the
preceding message and rerun the command.
IDC27531
VOLUME volser NOT SCRATCHED, COPIES EXIST
Explanation: The base volume (volser) was not scratched
because copies still exist.
System Action: The command terminated normally.
Programmer Response: Correct the error that prevented the
copies from being scratched and rerun the command
specifying the ALL parameter.
!
i
IDC27611
**
RECORD FOR COPY yyddd NOT REMOVED
Explanation: The volume copy record created on the date
indicated by "yyddd" was not removed from the Inventory
data set. A preceding message explains the reason for the
failure.
System Action: The command continues processing or
terminates depending on the severity of the error encountered.
Programmer Response: Correct the error indicated in the
preceding message and rerun the command to remove records
not removed.
IDC27621
** RECORD FOR VOLUME volser NOT REMOVED
Explanation: The volume record for volume (volser) was not
removed from the Inventory data set. A preceding error
message explains the reason for the failure.
System Action: The command terminates normally.
Programmer Response: Correct the error indicated in the
preceding message and rerun the command to remove the
volume record.
IDC27641
CARTRIDGES STILL IN MASS STORAGE FACILITY
Explanation: A volume record requested to be removed still
has one or both data cartridges belonging to it in the Mass
Storage Facility (MSF).
System Action: The volume or volume copy record is not
removed, the command continues processing.
Programmer Response: Scratch the volume using SCRATCHV
command or eject the volume or copy volume using the
EJECTV command. Then rerun this command.
Problem Determination: Table I, items 2, 3, 4, 13, 14, 29,
35a, and 35c.
IDC27651
RECORD FOR VOLUME volser NOT REMOVED.
RECORD FOR COpy EXISTS
Explanation: A copy volume record still exists. Therefore, the
base volume record for volume (volser) cannot be removed.
See a preceding message for the error that prevented removal
of all copy records.
System Action: The command terminates normally.
Programmer Response: Correct the error indicated in the
preceding message and rerun the REMOVEVR command with
the ALL parameter.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC27821
**
SCRATCH CARTRIDGE csn NOT EJECTED
Explanation: The requested scratch cartridge (csn) could not
be ejected. See the preceding message for further explanation
of the problem.
System Action: Processing continues.
Programmer Response: Correct the problem as identified in
the preceding message and rerun the command to eject the
cartridge.
Problem Determination: Table I, items 2, 3, 4, 13, 29, and
35b.
IDC28001
ATTRIBUTES COULD NOT BE CHANGED FOR
REMAINING VOLUMES IN GROUP
Explanation: Although the group level attributes have been
successfully changed in the group record in the Inventory data
set, the attributes (bind/nobind, readonly/readwrite,
dasderase/nodasderase, exclusive/shared) cannot be changed
for the general-use volumes remaining in the group because
storage for an ECB and message area cannot be obtained or a
base volume record cannot be retrieved from the Inventory
data set.
System Action: The command terminates with a message.
Programmer Response: Correct the problem as identified in a
preceding message. To determine the number of additional
volumes in the group that must be updated, run the L1STMSVI
command. Rerun the command if a large number of volumes
remain to be updated. Otherwise, run the MODIFYV command
to change the volume attributes of each volume if the number
of remaining volumes is small.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC28011
** ATTRIBUTES NOT CHANGED FOR VOLUME volser
Explanation: Although the attributes have been changed in the
group record, the attributes (bind/nobind; readonly/readwrite,
dasderase/nodasderase, exclusive/shared) of volume (volser)
cannot be changed. The volume may be ·currently mounted,
marked in the Inventory data set for recovery purposes, or
unavailable for another reason. See the preceding message for
further explanation of the problem.
System Action: Processing continues.
Programmer Response: Correct the problem as identified in
•
the preceding message. Run the MODIFYV command to change
the volume attributes of each volume that could not be
updated.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, 35a,
and 35c.
IDC28211
~'* SCRATCH CARTRIDGE I MOUNTABLE VOLUME I
NON-MOUNTABLE VOLUME REPORT NOT
PRODUCED
Explanation: The indicated report was not produced due to a
previously identified error.
System Action: The command continues with the next report.
Programmer Response: Check the previous error message for
the cause of the failure. Correct the error and rerun the
command.
Problem Determination: Table I, items 3, 4, 13, and 29.
IDC28231
** [SCRATCH CARTRIDGE I MOUNTABLE VOLUME
I NON-MOUNTABLE VOLUME I EMPTY CELL]
TOTAL COULD NOT BE CALCULATED
Explanation: Because of an error, the summary count
information could not be calculated. A previous message
explains the error.
System Action: The command continues processing, but the
indicated count is not listed.
Programmer Response: Correct the error identified in the
previous message and rerun the command.
Problem Determination: Table I, items 3, 4, 13, 29, and 30.
IDC28311
.~,~
RECORD CHAIN BROKEN, REST OF CHAIN NOT
LISTED
Explanation: The record could not be found for a volume
recorded in the Inventory data set as part of a chain of
nongrouped volumes or a chain of volumes belonging to a
specific group. See the preceding message for further
explanation of the error.
System Action: Processing continues.
Programmer Response: Correct the error as indicated in the
preceding message and rerun the command to list volumes
that could not be listed.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, 35a,
and 35c.
Section 4: IDC Messages - Access Method. Services
4-29
•
IDC28331
** CARTRIDGE RECORD csn NOT FOUND IN
INVENTORY
Explanation: The cartridge record for the cartridge with
cartridge serial number csn cannot be found· in the Inventory
data set.
System Action: Processing continues.
Programmer Response: Correctly specify the cartridge serial
number and rerun the job. If the problem is not the result of a
user error, contact the space manager.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, and
35c.
IDC28731
IDC28761
IDC28341
VOLUME ser NOT IN THE INVENTORY FOR
CARTRIDGE csn .
Explanation: The base, copy, or duplicate record associated
with the mass storage volume ser cannot be found in the
Inventory data set. The cartridge serial number of the cartridge
is csn. The Mass Storage System· Communicator MSSC reason
code that caused the message to be printed is X'23C'.
System Action: Processing continues.
Programmer Response: Contact the space manager.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, and
35c.
FUNCTION SUSPENDED DUE TO I/O ERROR RECORDS DUMPED nnnnnn
Explanation: While dumping trace data records, an I/O error
was encountered and no further processing was possible. The
number of records written to the output file is inserted into the
message. A preceding message explains the I/O error.
System Action: No more data was dumped. The command
terminates normally.
Programmer Response: Rerun the command to get the
remaining trace data. If problem continues, reallocate and
recatalog the data set which is getting I/O errors.
Problem Determination: Table I, items 2, 3, 4, 13, 29, and 30.
IDC28531
**
DISPLAY OF parameter NOT SUCCESSFUL
Explanation: An attempt to retrieve the information for the
indicated tuning parameter (parameter) failed. See preceding
message for an explanation of the error.
System Action: The command terminated normally. No more
parameters displayed.
Programmer Response: Correct the error and rerun the
command.
COMPARE OPTION IGNORED
IGNORED VERIFY FAILURE FOR CRA
Explanation: When a catalog recovery area is opened, a
VERIFY is issued by LlSTCRA to set up the proper end-of-file
condition. The VERIFY was unsuccessful.
System Action: The error is ignored and processing is
continued. An incomplete listing of the contents of the catalog
recovery area may result.
Programmer Response: Restore the volume on which the error
occurred to a previous valid condition. For more information on
catalog recovery, see OS /VS2 Access Method Services.
Problem Determination: Table I, items 2, 3, 4, 29.
IDC28791
IDC28431
**
Explanation: The catalog recovery area on this volume cannot
be opened or belongs to a catalog other than the one for .
which COMPARE was specified. If an error occurred in open, a
preceding message gives the cause.
System Action: The COMPARE option of the LlSTCRA
command is ignored and processing is continued.
Programmer Response: Specify the correct catalog name in
the CATALOG parameter or correct the cause of the Open
error, ahd rerun the job.
CATALOG NOT LOCKED UP FOR THIS EXECUTION
Explanation: LlSTCRA was unable to gain exclusive control of
the catalog. One or more other programs may be updating the
catalog during LlSTCRA execution.
System Action: LlSTCRA processing continues. Some listing
errors or miscompares may result if a catalog or recovery area
entry is updated during LlSTCRA processing.
Programmer Response: If you doubt the accuracy of this CRA
listing, rerun the job when no other programs are accessing
the. catalog.
IDC28821
V5AM ERROR READING CRA CONTROL RECORD
Explanation: A LlSTCRA command encountered an error
reading the control record in the catalog recovery area (CRA)
to determine the size of the table necessary for its processing.
System Action: Processing is terminated for this CRA.
Programmer Response: Restore the volume on which the error
occurred to a previous valid condition. For more information on
catalog recovery, see OS/VS2 Access Method Services.
Programmer Response: Table I, items 2, 3, 4, 29.
IDC28841
IGNORED VERIFY FAILURE FOR CATALOG
Explanation: An attempt to change the specified TUNE
command parameter (parameter) failed. See preceding
message for an explanation of the error.
System Action: The command terminates normally. No more
tuning parameters are changed.
Programmer Response: Correct the error and rerun the
command.
Explanation: When a catalog is opened, a VERIFY is issued by
LlSTCRA to set up the proper end-of-file condition. The
VERIFY was unsuccessful.
System Action: The error is ignored and processing continues.
Erroneous miscompares and/or I/O errors may result.
Programmer Response: Restore the volume on which the error
occurred to a previous valid condition. For more information on
catalog recovery, see OS/VS2 Access Method Services.
Problem Determination: Table I, items 2, 3, 4, 29.
IDC28721
IDC28861
IDC28541
**
CHANGE OF parameter NOT SUCCESSFUL
CRA IS OWNED BY catname
Explanation: The catalog recovery area (CRA) on this volume
belongs to a catalog other than the one for which COMPARE
was specified.
System Action: The COMPARE option is ignored and
processing is continued.
Programmer Response: Specify the correct catalog in the
CATALOG parameter and rerun the job.
4-30
VS2 System Messages (VS2 Release 3.7)
UNABLE TO REFERENCE CRA ON VOLUME ser REASON CODE cde
Explanation: When opening the catalog recovery area (CRA)
there was a problem indicated by the reason code cde.
Possible reason codes and their meanings are:
Reason
Codes Meaning
1 Cannot verify the CRA.
2 Cannot open the CRA.
4 I/O error on control interval No.O
5 I/O error on control interval NO.3
7 Error on number of directories.
8 Error on directory entries.
System Action: The CRA is marked bad and no entries are·
placed on the portable data set.
Programmer Response: If the reason code cde is 1, 2, 4, or 5,
restore the volume on which the error occurred to a previous
valid condition. For more information on catalog recovery, see
as /VS2 Access Method Services.
If the reason code is 7 or 8, provide the FORCE keyword in
the EXPORTRA command to override the synchronization
problem.
IDC29081
ddn NOT FOUND IN SYSTEM
Explanation: An attempt was made to use the volume
identified by ddn. However, a DO statement corresponding to
the ddname could not be found.
System Action: The volume cannot be accessed.
Programmer Response: Correct the erroneous ddname or
provide a DO statement and resubmit the job.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IDC29091
UNABLE TO SCRATCH dsn
Explanation: An error occurred while attempting to scratch
dsn. A subsequent second-level message explains the error.
System Action: The data set is not scratched.
Programmer Response: See the associated message.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IDC29101
**
NO VOLUME MOUNTED
Explanation: None of the volumes specified for the data set is
mounted.
System Action: The data set is not scratched.
Programmer Response: Mount the proper volume(s) and
resubmit the job.
**
IDC29111
DATA SET NOT ON VOLUME ser
Explanation: Volume ser was specified either in the command
or in JCl, but does not contain the data set identified by
preceding message (lDC29091).
System Action: The data set may have been scratched from
other volumes.
Programmer Response: Correct the command or JCL and
resubmit the job.
Problem Determination: Table I, items 1, 2, 3, 4, 25a, 29.
IDC29121
**
PASSWORD VERIFICATION FAILED
Explanation: The data set to be scratched is
password-protected, and the console operator did not supply
the proper password.
System ACtion: The data set is not scratched.
Programmer Response: Resubmit the job, supplying the correct
password when prompted.
Problem Determination: Table I, items 1, 2, 3, 4, 25a, 29.
IDC29131
**
DATA SET HAS NOT EXPIRED ON VOLUME ser
Explanation: The PURGE option was not specified, and the
data set's retention period has not expired.
System Action: The data set is not scratched.
Programmer Response: Resubmit the job; specifying PURGE if
you wish to delete the data set.
Problem Determination: Table I, items 1, 2, 3, 4, 25a, 29.
IDC29141
**
PERMANENT I/O ERROR ON VOLUME ser
Explanation: The VTOC cannot be read because of an I/O
error.
System Action: The data set is not scratched.
Programmer Response: Have the volume restored.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IDC29151
,:::~
UNABLE TO MOUNT VOLUME ser
Explanation: An appropriate unit was not available for
mounting.
System Action: The data set is not scratched.
Programmer Response: Ensure that a unit is available for
mounting.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IDC29161
** DATA SET WAS IN USE
Explanation: The data set to be scratched was in use.
System Action: The data set is not scratched.
Programmer Response: If you wish to delete the data set, you
must ensure that no one else is using the data set when you
rerun the job.
Problem Determination: Table I, items 1, 2, 3, 4, 25a, 25c, 29.
IDC29501
INVALID FORMAT STRUCTURE
Explanation: An element of one of the text format structures is
.
invalid. This message ShOU.ld never appear in a valid program. •
If it does, it is a system error.
• •
System Action: The request to print a line is ignored.
Programmer Response: Do the problem determination action.
Problem Determination: Table I, items 3, 4, 29.
IDC29511
OUTPUT COLUMN SPECIFIED OUT OF RANGE
Explanation: An output column specified is outside the print
line width, for example, not between columns 1 and 121. This
should not occur on a checked-out Access Method Services
command.
System Action: This field imd subsequent fields are ignored.
Programmer Response: Do the problem determination action.
Problem Determination: Table I, items 3, 4, 29.
IDC29521
EXCESSIVE FIELD LENGTH FOR BD OR PU CONV
Explanation: A binary to decimal or packed to unpacked
conversion length was specified as greater than 15 characters.
This should not occur in a valid program.
System Action: The default (15) is used.
Programmer Response: Do the problem determination action.
Problem Determination: Table I, items 3, 4, 29.
IDC29531
A REDO SUB-STRUCTURE IS NESTED
Explanation: A redo structure cannot be defined within the set
of structures to be redone. This should not. occur in a valid
program.
.
System Action: The current redo operation is terminated. All
structures will be treated only once.
Programmer Response: Do the problem determination action.
Problem Determination: Table I, items 3, 4, 29.
IDC29541 STATIC TEXT ENTRY REQUESTED NOT IN MODULE
Explanation: A static text request indicated an entry that was
not in· the module specified. This should not occur in a valid
program.
System Action: The request is not honored.
Programmer Response: Do the problem determination action.
Problem Determination: Table I, items 3, 4, 26c, 29.
IDC29551
INVALID PACKED DECIMAL FIELD
Explanation: A conversion request for packed to unpacked
found· a digit that was not in the range 0 to 9. The input data
may be wrong. This should not occur unless an incorrect field
is being printed.
Section 4: IDC Messages - Access Method Services
4-31
System Action: Conversion stops. Previously converted data
will be printed.
Programmer Response: Check the input data.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC29601 NO PSWDFILE FOR dsn
Explanation: A password protected data set (dsn) was found
on the VTOC but no DO card was found with that data set
name.
System Action: The command terminates normally.
Programmer Response: Provide a DO card with the name of
the data set. Specify the name of the DO card on the
PASSWORDFILE parameter, and rerun the command.
Problem Determination: Table I, items 1, 3, 4, 13, 25b, and
2S.
IDC29611
[FROM I TO VOLUME] volser CONTAINS
NON-VSAM DATA SETS
Explanation: The command requires that no non-VSAM data
sets can reside on the volume (volser). However, a format 1
DSCB was found for a non-VSAM data set. "From" and "to"
indicate which volume contains the data set for those
commands that process more than one command.
System Action: The command terminates normally.
Problem Determination: Table I, items 1, 3, 4, 13, 25b, and
29.
IDC29621
ENTRY NOT FOUND FOR VOLUME volser IN VSAM
CATALOG
Explanation: The volume entry could not be located for the
volume in the VSAM catalog sp,ecified_DY the user on the
command or (if not specified on the command) in the VSAM
catalog in the STEPCAT, JOBCAT, master catalog hierarchy.
The VSAM catalog return code was S..
System Action: The command terminates normally.
IDC29631
FORMAT 4 DSCB NOT FOUND ON VTOC OF
FROM I TO VOLUME
Explanation: the program positioned to the first record in the
VTOC of the volume but it was not a Format 4 DSCB. "FROM"
or "TO" specifies which volume encountered the error for the
commands that process more than one volume.
System Action: The command terminates normally.
Programmer Response: This probably indicates an Access
Method Services error. Possibly the VTOC has been destroyed.
Attempt to list the VTOC using the IEHLlST utility, and
reconstruct the VTOC. Rerun the command.
Problem Determination: Table I, items 1, 3, 4, 13, 25b, and
29.
IDC29641
**
SCRATCH OF DATA SETS NOT PERFORMED
Explanation: An errQr occurred which prevented any data set
from being scratched .. The volume is still marked as VSAM
volume. A preceding message indicates the specific error.
System Action: The command continues processing.
Programmer Response: Run AMASPZAP service aid program to
alter the VTOC if any VSAM data sets are on the volume and
the VSAM data sets have been recataloged. If the volume is
not a VSAM volume, use thelEHPROGM utility's SCRATCH
VTOC statement. '
Problem Determination: Table I, items 1, 3, 4, 13, 14, 25b,
and 29.
IDC29651
ATTEMPT TO SCRATCH DATA SETS TERMINATED
Explanation: An' error' Occurred reading or updating the VTOC
4-32
VS2 System Messages (VS2 Release 3.7)
so that no more data sets could be scratched. The VSAM
ownership flag has been set off in the VTOC ..
System Action: No further attempts to scratch data sets are
made. The command continues processing.
Programmer Response: Run the AMASPZAP service aid,
program to alter the VTOC if the VTOC contains VSAM data
sets and the data sets have beenrecataloged. If the volume is
not a VSAM volume, use the IEHPROGRM utility's SCRATCH
VTOC statement.
Problem Determination: Table I, items 1, 3, 4, 13, 14, 25b,
and 29.
IDC29661
RECATALOGING OF NON-VSAM DATA SETS NOT
PERFORMED
Explanation: An error occurred which prevented any
non-VSAM data sets from being recataloged. A preceding
message will indicate the specific reason for the error.
System Action: The command terminates normally. No further
function is performed.
Programmer Response: Use the IEHPROGM utility or the
Access Method Services DELETE and DEFINE commands to
recatalog the data sets.
Problem Determination: Table I, items 1, 3, 4, 13, and 29.
IDC29671
ATTEMPT TO RECATALOG NON-VSAM DATA SETS
TERMINATED
Explanation: An error occurred after some data sets were
recataloged. A preceding message indicates the specific
reason for the error.
System Action: No further non-VSAM data sets are
recataloged. The command terminates normally. No further
function is performed.
Programmer Response: List the catalog to determine which
data sets were recataloged or, if the LIST parameter was
specified, examine the SYSPRINT listing to see which data sets
were recataloged. Recatalog the data sets not previously
recataloged using the IEHPROGM utility or the Access Method
Services DELETE and DEFINE commands.
Problem Determination: Table I, items 1, 3, 4, 13, and 29.
IDC29711
RESERVE FOR VOLUME volser NOT SUCCESSFUL
Explanation: The reserve with the HAVE option returned an
unsuccessful condition code.
System Action: The command terminates proces,sing.
Programmer Response: Rerun the command.
Problem Determination: Table I, items 1, 3, 4, 13, and 29.
IDC29721
LSPACE ERROR. LSPACE RETURN CODE WAS nn.
Explanation: The LSPACE macro failed to return volume free
space information fora L1STDSET space usage report. The
return code from the LSPACE macro is nn. The following are
possible values for nn:
• 4, indicating an I/O error while reading the DSCBs.
• S,' indicating the last allocation of the volume was made
under DOS.
• 12, indicating the UCB address is invalid, the UCB is not for
a direct-access device, or the UCB-not-ready bit is on,
indicating the device is not ready.
• 16, indicating an invalid message area address or SMF
indicator.
.
System Action: The volume is not processed. If other volumes
were specified, they are processed;
Programmer Response: Determine why the LSPACE macro
failed. Message IDC210S1 follows this messages and identifies
the failing volume.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29.
\~
IDC30031
FUNCTION TERMINATED. CONDITION CODE IS cde.
Explanation: This message is issued when a terminating error
condition has occurred in the execution of a functional
command. Messages printed just before this message in the
program listing indicate the error that occurred.
System Action: Processing continues with the next command,
and LASTCC is set to cde. MAXCC is also set if cde is greater
than the current MAXCC value.
Programmer Response: The appropriate programmer response
is indicated by the preceding messages.
IDC30041
FUNCTION TERMINATED. INSUFFICIENT MAIN
STORAGE:.
Explanation: The region size was not large enough to execute
a functional command.
System Action: Processing continues with the next command.
Programmer Response: Increase the size of the storage
allocated.
Problem Determination: Table I, items 1, 3, 29.
IDC30061
FUNCTION TERMINATED DUE TO BEGINNING
POSITIONING ERROR
Explanation: An error occurred when positioning to a record in
a data set (such as occurs via the FROMKEY facility of the
PRINT command) was attempted. The position indicator may
be beyond the limits of the data set or an I/O error may have
occurred in positioning. An I/O error message may have been
printed.
System Action: The operation is terminated.
Programmer Response: Correct the positioning parameter
value. See the I/O error message description for the I/O error
indicated ahead of this message.
Problem Determination: Table I, items 1, 3, 4, 13, 29.
IDC30071
VSAM CATALOG RETURN-CODE IS rc
Explanation: This condition code was returned as the result of
a catalog error or exceptional condition. This message is used
only when a more specifically worded message does not exist;
in most instances, a subsequent message will indicate the
action taken for the command that encountered the condition.
The return. code, rc, may be either a VSAM return code or a
CVOL processor return code. To determine which, you must
determine whether the entry name specified in the command
was directed to a VSAM catalog or a CVOL catalog. For a
return code to be a CVOL return code, the entry name
specified in the command must be qualified; and the first
qualifier must be identical to an alias entry in the master
catalog. The alias entry must be related to a nonVSAM entry
of the form SYSCTLG.anyname. For example, if A.B.C is the
entry name in the command and A is found to be an alias
relating to SYSCTLG.anyname in the master catalog, then
CVOL processing will take place for the data set A.B.C.
The CVOL processor return codes follow. The VSAM catalog
return codes are listed with message IDC30091, where they
appear together with reason cod~s; for message IOC30071,
ignore these reason codes.
CVOL
Return
Codes Explanation
4 Cannot allocate catlaog, catalog does not exist, or is
not open.
8 The data set does not exist, or a CVOL contains a
CVOL pointer or GOG alias, or the entry name
duplicates an existing name.
20 There is insufficient space in the CVOL data set.
24
LOCATE operation - Permanent I/O error,
unrecoverable error, or nonzero return code from
ESTAE (ESTAE is issued by the CVOL processor).
28 Non-LOCATE operation - Permanent I/O error,
unrecoverable error, or nonzero return code from
ESTAE (ESTAE is issued by the CVOL processor).
48 Function inconsistent with CVOL processor.
See OS /VS2 Using OS Catalog Management with the Master
Catalog: CVOL Processor, GC35-0010, for further information.
System Action: The command is terminated.
Programmer Response: The response depends on the return
code received:
CVOL
Return
•
Codes Response
4 Ensure that the CVOL is mounted; verify the use of the
STEPCAT and JOBCAT JCL or of the ddname DO cards
statement.
8 Check that the entry name is spelled correctly; verify
the use of JOBCAT and STEPCAT catalogs, if employed.
20 See your system programmer for assistance in
reorganizing the CVOL.
•
24 Have the volume restored or try mounting the volume
on a different device.
28 Have the volume restored, or try mounting the volume
on a different device.
48 Verify the use of JOBCAT and STEPCAT catalogs, if
employed, to ensure that the catalog being acted upon
is appropriate to the action you are attemptillg.
Problem Determination: Table I, items 1, 2, 3, 4, 16, 25a, 29,
or 30. (For item 16, the dump identification ZZCA may be used
to obtain a dump just before the CATLG macro is executed.)
IDC30081
FUNCTION IS NOT SUPPORTED IN THIS
ENVIRONMENT
Explanation: A request for prompting or data set name
qualifying has been received while not in a TSO environment.
System Action: The request is terminated.
Programmer Response: None. The message will not result from
a user error.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC30091
VSAM CATALOG RETURN CODE IS rc - REASON
CODE IS IGGOCLaa - crs
Explanation: This return code, rc, and reason code, crs, were
returned by Catalog Management module IGGOCLaa as a result
of a catalog error or exceptional condition.
System Action: Processing associated with the error return
code is terminated.
Programmer Response: See the specific return code and
reason code.
Problem Determination: Table I, items 1, 2, 3, 4, 16, 25a, and
29 or 30. (For item 16, the dump identification ZZCA may be
used to obtain a dump just before the CATLG macro is
executed.)
A complete list of return codes and reason codes follows:
Return Reason
Codes Codes
Description
An error was encountered while performing open/close
4
processing for a' VSAM catalog or a catalog recovery
area. If the catalog is being accessed dynamically due
to a lack of a JOBCAT or STEPCAT DO statement for
the catalog, dynamic allocation may have failed because
the volume is allocated exclusively. The volume may be
allocated exclusively due to one of the following:
specification of deferred mount on a DO statement
•
Section 4: IDC Messages - Access Method Services
4-33
•
•
volume count greater than unit count on a DO
statement
• previous Access Method Services command in the job
step needed to demount the volume and changed the
allocation of the volume to exclusive.
2 Error opening the catalog.
4 Error closing the catalog.
6 A request has referenced a catalog while catalog
management is processing an Access Method Services
DELETE command for the specific catalog.
8 An invalid Access Method Control Block (ACB) was
supplied to catalog management for a catalog to be
used during a catalog request.
10 A specific catalog was not found to be open.
12 Error opening a catalog recovery area.
14 Error closing a catalog recovery area.
16 No master catalog was found on a non-superlocate
request.
18 A catalog recovery area did not exist on a volume, but
was expected.
Programmer Response: For reason codes:
2,4,
12,14 Check for open/close problem determination messages
in the job stream output.
8,16 Contact IBM for programming support.
6,10 Ensure proper usage of JOBCAT or STEPCAT JCL
statements.
18 Determine if the IEHDASDR dump/restore or IBCDASDI
activity has impacted any,VSAM containing volumes and
restore to the proper version. If restore versions are
not available, invoke proper catalog and volume
recovery procedures.
Entry does not exist, if action is one that locates the
8
entry; or entry already exists, if action is one which
adds an entry to a catalog.
2 Catalog cluster record not found.
4 Get for update found a free record instead of correct
record.
6 No record found from record management.
8 A request to place a record by key into a catalog
resulted in a duplicate key error from VSAM.
12 Invalid entry type for Super-Locate on the entry named.
The data set was not found in a catalog.
14 A generation data group entry type for Super-Locate
did not find the specified entry in a catalog.
16 A generation data group entry was found to be deleted
from a catalog.
18 A generation data group type of Super-Locate request
specified an invalid generation number.
20 Volume occurrence entry does not exist in record.
24 Record not found in CRA.
26 Catalog CI number not found in CRA CI translate table.
28 Volume serial number not found in CRA volume time
stamp table.
30 The catalog control record was incorrectly retrieved.
Programmer Response: For reason codes:
2 Call IBM for programming support.
4 Because it is possible during an Access Method
Services DELETE command to leave partial structures in
the catalog if the DELETE does not complete, this error
can occur., Correct the error that caused DELETE to
terminate and rerun the DELETE. If this error is not
related to a DELETE then call IBM for programming
support.
6 Check that the entry name is spelled correctly. In the
instance of an improper DELETE command entry type,
either remove the type specification or correct it. Check
4-34
VS2 System Messages
(VS2 Release 3.7)
8
also that the proper catalog is being searched for the
name you specified.
Check that the entry name is spelled correctly and that
you are using the proper catalog.
12,14,
16,18 Ensure that the proper data set name was specified in
the job contrQI language DO statement.
20 Catalog volume entry record indicates certain VSAM
data sets reference it, but that was not found to be
correct. The catalog should be listed and recovery
procedures may be necessary to synchronize the
catalog to correspond with the proper VSAM data sets.
24 Catalog and a recovery area do not correspond.
Recovery procedures should be used to synchronize the
catalog and the volumes.
26,28 System error while using Access Method Services
EXPORTRA command. Contact IBM for programming
support.
30 This is a system error and indicates a problem with a
VSAM catalog. It may be necessary to rebuild the
catalog, however, it should first be' determined that the
catalog in fact is in error.
20
Insufficient space in VSAM catalog. The catalog is full.
It is impossible to obtain another extent, because there
is no more space on the volume in which the catalog
resides, or the maximum number of extents has been
reached. Reorganization of the data high key range of
the catalog may be required.
24
Permanent read error in VSAM catalog.
Programmer Response: For reason codes:
2,6 If a hardware error is not causing the problem, you
must restore or rebuild the catalog. Messages IEC3311,
IEC3321, and IEC3331 have been printed to aid in
determining where the error occurred.
28
Permanent I/O error in VSAM catalog.
2 I/O error processing the catalog while executing an
Access Method Services command that requires
modifying the catalog.
4 I/O error during catalog OPEN.
8 I/O error processing a catalog recovery area.
Programmer Response: For reason codes:
2,4,8 If a hardware error is not causing the problem, you
must restore or rebuild the catalog. Messages IEC3311,
IEC3321, and IEC3331 have been printed to aid in
determining where the error occurred.
32
Error in VSAM catalog parameter list. Such a condition
indicates an internal error in the Access Method
Services.
2 This is a system error indicating that catalog
management was unable to return the requested data in
the catalog parameter list to extend a data set. The
proper volume occurrence was not found.
4 Invalid catalog parameter list, failed storage validity
check.
6 User provided work area (from catalog parameter list)
outside user region.
8 Error in parameter list - no pointer to work area.
10 Pointer to catalog volume list but no length provided in
work area.
12 Length of volume list but no pointer to volume list
provided in work area.
14 Non-system caller issued update.
Programmer Response: For reason codes:
2,4,
6,8,
10,12 Call IBM for programming support.
VS2.03.807
14
If user programs are interfacing directly with VSAM
catalog management, this is a user error. Otherwise,
contact IBM for programming support.
36
Data set not found.
2 Incorrect record type found in Access Method Services
ALTER command.
4 Data set name not found on the volume table of'
contents.
12 A Super-Locate request to VSAM catalog management
requires dynamic access of a catalog.
Programmer Response: For reason codes:
2 Determine if the correct name was specified in the
command or if the proper fields are requested to be
modified for the entry type.
4 Check that the proper versions of the volume and
catalog are being processed and that the volume is
synchro.nized with the catalog.
12 If this error causes a job to terminate, the user should
ensure that the master catalog references the proper
catalogs and that they are available to the system when
the job stream is executed.
40
Volume list or work area too small. An attempts to
provide VSAM catalog management with sufficient
virtual storage in which to return cataloged information
failed, because the indicated storage requirement
proved to be insufficient.
This condition should not normally occur: it can happen
when two or more tasks are modifying a catalog entry,
causing it to be extended in size, and one task finds
that if was unable to specify sufficient virtual storage
for catalog management's new requirements.
Programmer Response: For reason codes:
o Rerun the job in a larger partition.
44
Callers work area too small.
2 Delete catalog work area too small.
4 Caller work area too small.
6 An Access Method Services DELETE command to delete
an entire generation data group, with the FORCE
parameter, ,encountered a work area too small to
contain names of entries deleted. However, the entire
generation data group was successfully deleted.
Programmer Response: For reason codes:
2,4 Contact IBM for programming support.
6 This is merely a warning condition, no response is
necessary.
Invalid VSAM catalog function.
48
2 Probable system error. The catalog management driver
has been passed a catalog parameter list that is invalid.
6 ALTER of a non-VSAM entry, not allowed for the fields
being modified.
8 ALTER of the catalog name is not allowed.
10 Erase option delete, but file name is for incorrect
catalog.
12 An Access Method Services ALTER command
encountered an inconsistency with the entry type and
the UPGRADE/NOUPGRADE or UPDATE/NOUPDATE
parameters.
14 Data set is update inhibited.
16 Data set is not reusable.
18 It is only valid to change the attributes or ownerid fields
of a generation' data group base entrY by the Access
Method Services ALTER command.
20 Forced delete not allowed on catalog volume.
22 It is not valid to use the NOSCRATCH parameter to
DELETE a data set in a recoverable VSAM catalog.
24 It is invalid to attempt to change the name of a user
catalog or alias entry via the Access Method Services
ALTER Command.
4
26
It is invalid to attempt to change the name of a
nonVSAM entry that is a member of a generation data
group via the Access Method Services ALTER
command.
28 It is invalid to attempt to delete a GOG base entry that
contains nonVSAM entries.
30 It is invalid to delete the master catalog with the FORCE
parameter.
Programmer Response: For reason codes:
2 Call IBM for programming support.
6 'Ensure that the proper entry name was specified on the
Access Method Services ALTER command and that only
fields that exist for a non-VSAM entry are requested to
be changed.
8 Check that you didn't use the catalog name by mistake.
Catalog names can only be changed by doing DELETE
and then re-DEFINE catalog.
10 Do not use a DO name on the catalog parameter in the
Access Method Services DELET~ command if erase
processing is to be performed.
12 Contact IBM for programming support. This is a system
error.
14 Do not open a data set for reset processing that is
inhibited for update processing.
16 Do not open a non-empty data set for reset processing
that is not reusable.
18,24,
26 Do not attempt the invalid ALTER comma~nds. Correct
the commands and re-run the job.
20 The FORCE parameter is not allowed on a DELETE
SPACE command that is issued against a volume
containing a VSAM catalog. Use the DELETE CATALOG
command if that is what is desired. Or, use the ALTER
REMOVEVOLUMES command if the private catalog on
the volume is no longer processable.
22 Do not attempt the invalid DELETE command. Use the
NOSCRATCH parameter to DEL~TE the SPACE if it is
desired to remove the volume from the catalog. Or use
the FORCE parameter on the DELETE USERCATALOG
command if that is desired.
28 Delete the members of the GOG base explicitly.
Alternatively, the GOG base and its members may be
deleted with the use of the FORCE parameter in the
DELETE command.
30 The master catalog cannot be deleted.
52
Permanent I/O error on user volume. An attempt to
modify the VTOC of the volume on which a user
specified data set is being defined of modified failed
because of a read or write error.
x Reason coeds are error codes returned from OS/VS
DADSM.
'
Programmer Response: For reason code:
x If the error is not caused by a hardware error, the
volume must be restored.
56
Security verification failed.
2 All attempts to provide a password via the system
operator were made without success or the user's RACF
authorization W2S inadequate.
4 Non-system caller has specified password level (not
master) in catalog parameter list.
6 No prompt allowed and password not provided on the
Access Method Services command or the user's RACF
authorization was inadequate.
8 User-specified verification routine did not authorize use
of the data set.
10 It is detected that a system with theTime Sharing
Option required a prompt to a terminal, but user
terminal prompts were disallowed by the system
attributes.
Section 4: IDC Messages - Access Method Services
4-35
VS2.03.807
12
A prompt of a user terminal for security data
encountered a system error.
Programmer Response: For reason codes:
2 Message IEC301A has been printed until the number of
ATTEMPTS is exceeded. The operator did not know the
password needed to access this data set. Provide the
operator with the correct password or obtain the
required RACF authorization and rerun the job.
4 Contact IBM for programming support if user written
programs are not calling VSAM catalog management.
6 Either ALTER the passwords to allow operator
prompting or supply the password on the Access
Method Services command or obtain the required RACF
authorization.
8 Evaluate your user-specified verification routine to
determine why register 15 was not zero when control
was given back to the catalog verification routine.
10 Supply the proper password in the command or change
the system to allow terminal prompting.
12 This is a system error. If there are no hardware
problems, contact IBM for programming support.
60
Invalid entry type for requested action.
2 Probable system error. Invalid entry type for extract
operation.
4 Invalid entry type (cluster or nonVSAM).
6 Invalid cluster entry for ALTER of data set attributes.
8 Invalid cluster or index entry for ALTER of buffer size.
10 Invalid entry type (CLUSTER) to ALTER the FREESPACE
or WRITECHECK parameters.
12 Invalid entry type (CLUSTER) to ALTER volumes.
14 Probable system error. An invalid catalog parameter list
was supplied in. an attempt to add a volume.
20 System error. Upgrade set association in base cluster
data record does not point to an upgrade set record.
22 System error. Data association in cluster record does
not point to a data record.
26 ALTER of EXCEPTIONEIT but the entry is not a data or
index component.
28 ALTER of average RECORDSIZE but the entry is not a
data or index component.
30 ALTER of expiration date but the entry is not a cluster,
alternate index, or path.
36 An alias entry may only be DEFINED for nonVSAM or
user catalog entries.
40 System error. Input base record to catalog upgrade
management is not an alternate index, cluster or data
type entry.
42 System error. Input base record to catalog reusable
processing is not a data type entry.
44 An invalid entry type was encountered in a DELETE
operation; other than the expected alias entry.
Programmer Response: For reason codes:
2, 4, 6, 8, 10, 12, 14, 20, 22, 26, 28, 30, 40, 42, ensure
that the name of the entry specified in the command is
correct; ensure that the catalog entry is still valid, by
performing a LlSTCAT run.
If the reason code indicates a system error, list the catalog
using the PRINT command with the DUMP option and call IBM
for programming support; otherwise correct the error and
rerun the job.
36 Do not attempt an invalid DEFINE operation.
44 Ensure that the proper entry name was specified and
that the catalog reflects the expected structure. It may
be necessary to rebuild the catalog.
64
Associated entry does not exist. This condition indicates
that a system error has occurred such that the VSAM
catalog cannot find either a data or an index entry
4-36
VS2 System Messages (VS2.03.807)
which is associated with a cluster or alternate index
entry.
2 Test field name not present in group space header.
4 Associated entry names do not exist.
Programmer Response: For reason codes:
2,4 Call IBM for programming support.
No space available on user volume.
68
2 Cannot extend unique data set, no space on volume.
4 No secondary extent value specified.
6 No space for suballocation.
8 Maximum number of extents on volume reached and no
space on volume.
10 A DADSM error was encountered other than the
following return codes: 4, 8, and 12.
12 More than 16 extents per volume for reusable file.
16 No DA space available for extending a CRA.
Programmer Response: For reason codes:
2,4,
8,16 Scratch unneeded data sets from the volume, or
execute an Access Method Services ALTER command to
add more candidate volumes to the catalog entry for
the data set or add more suballocatable space to the
volume.
6 Either DEFINE more space on the volume, DELETE
usused data sets to make more space or use the
ALTER volume command with the AOOVOLUMES
parameter to the data set to provide space on a new
volume.
10 System error. Contact IBM for programming support.
12 Reload the data set using larger primary allocation.
72
User volume not mounted.
x Reason codes are from VSAM
open/close/end-of-volume, volume mount and verify
routine. See codes associated with message IEC1611
for reason code meaning.
Programmer Response: For reason codes:
x Ensure proper volumes are implicitly or explicitly
allocated via Job Control Language. Also, verify that the
volume and the volume information (timestamps)
contained in the VSAM catalog are at the same level.
76
No unit available for mounting or volume not mounted.
o Access Method Services ALTER name change of a
unigue object but no volumes containing any part of the
data set were mounted.
2 Volume not mounted when expected.
4 Unit not available to mount a volume required for
catalog recovery area (CRA) processing.
6 Catalog Recovery Area (CRA) volume not mounted
during end-of-volume or close request for a VSAM data
set when the catalog update was· required.
8 A" scan of the task I/O table (TIOT) failed to find the
user specified JCL ODname statement.
Programmer Response: For reason codes:
0,2,4,
6,8 Ensure that JCL statements cause the proper volumes
and units to be allocated. Also, that all DOn ames
specified match the Access Method Services dna me
parameter when specified. Also, determine a minimum
unit count and have sufficient units available for the job
execution. Ensure that volumes are allocatable by the
use of dynamic allocation.
80
Invalid related object.
The object specified in the RELATE parameter of a DEFINE
command does not exist, or is improper for the type of object
being defined.
o Related object is reusable.
2 Related object is a relative-record data set.
4 Related object does not exist.
'~
.,\
6
Alternate index or path is not allowed to be built over a
catalog.
Section 4: IDC Messages - Access Method Services
4-36.1
4-36.2
VS2 System Messages (VS2.03.807) ,
VS2.03.807
8
Name of alternate index or path and related object are
identical.
10 No pointer to a related object of an alternate index or
path.
12 Alternate index is not to be built over a base cluster or
related path object is not a cluster or an alternate
index.
Programmer Response: For reason codes:
0,2,4,6,8,10,12 Correct the DEFINE command so that the
entry named in the RELATE parameter is proper for the type
of object being defined.
84
Unexpired purge date.
o An attempt to delete an entry failed because its
expiration date has not been reached, and the DELETE
command did not specify the PURGE option.
Programmer Response: For reason codes:
o Specify the PURGE option, if desired, and rerun the
DELETE command.
88
Error with a catalog recovery area (CRA) define
operation.
6 The total space specified on an Access Method
Services DEFINE RECOVERABLE CATALOG was not able
to contain the size specified for the catalog and the one
cylinder of space required for the catalog recovery area
(CRA).
Programmer Response: For reason code:
6 Allow for a 1 cylinder CRA and the total catalog size in
the total space on the DEFINE RECOVERABLE CATALOG
operation. The VSAM data set or catalog cannot be
extended beyond its current space allocation because it
has already reached the maximum number of extents
permitted within its data spaces, namely 123 for a
VSAM data set that is not a catalog.
92
Maximum number of extents reached.
Programmer Response: For reason code:
o List the catalog, in order to determine space
fragmentation. Delete and redefine data spaces in order
to reduce fragmentation. Use the REPRO command to
reorganize the data set in order to reduce
fragmentation.
An OS/VS DADSM Obtain request failed during a VSAM
94
catalog delete request.
x The reason code is the Obtain return code.
Programmer Response: For reason code:
x Determine the meaning of the obtain return code see
OS/VS2 System Programming Library: Data Management
for these and take the appropriate corrective action
before rerunning the job that encountered the failure.
Error in specifying key length, key position, or record
96
size for an alternate index or spanned cluster.
o Key specified for spanned record exceeds control
interval size.
4 Maximum logical record size for spanned records
exceeds control area size.
6 Alternate index key position plus key length for base
cluster is larger than control interval size minus 10 for
spanned records.
8 Alternate index key position plus key length for base
cluster is larger than record size.
Programmer Response: For reason codes:
0,4,
6,8 Correct the erroneous parameter (KEYS or
RECORDSIZE) and rerun the job.
An unusual condition occurred during ALTER name of a
98
unique or non-VSAM data set.
x The reason code is the same as returned by the OS/VS
DADSM RENAME function in the status byte of the
RENAME volume list.
Programmer Response: For reason code:
x
Determine the meaning of the RENAME return code see
OS/VS2 System Programming Library: Data Management
for these and take the appropriate corrective action
before rerunning the job that encountered the failure.
An OS/VS DADSM SCRATCH request failed during a
VSAM catalog delete request for a unique or non-VSAM
data set.
x The reason code is the OS/VS DADSM SCRATCH
function return code.
Programmer Response: For reason code:
x Determine the meaning of the SCRATCH return code
see OS/VS2 System Programming Library: Data
Management for these and take the appropriate
corrective action before rerunning the job that
encountered the failure.
106 A format-4 DSCB processing error was encountered.
o A read of a format-4 DSCB on a volume returned an
erroneous record.
2 The format-4 DSCB time stamp mismatches the
corresponding catalog time stamp.
Programmer Response: For reason codes:
o Determine if the volume table of contents on the
volume has been destroyed and perform an IEHDASDR
operation to repair the volume. If the volume has to be
restored, the information in the VSAM catalog must be
updated to match the restored version of the volume.
This may require deleting all VSAM data sets and VSAM
space from the catalog and redefining the VSAM space
and importing the data sets.
2 The physical con~ents of the volume implicated disagree
with the information about the volume in the VSAM
catalog that own the volume. This may be due to
IEHDASDR DUMP/RESTORE activity or to Access
Method Services REPRO activity. Determine whether the
volume or the catalog is down-level and restore it to
the proper version of the c ata. This will only be
encountered with recoverable VSAM catalogs.
108 Invalid field name in field parameter list. The field name
does not exist in the VSAM Catalog Management
Dictionary. This is a system error.
Programmer Response: For reason code:
o Call IBM for programming support.
110 Unable to modify or delete RACF profile.
4 The data set to which an ALTER RENAME command is
directed is RACF indicated. However, there is no RACF
profile.
8 An ALTER RENAME command has been issued for a
RACF-protected data set. This failed because as a
result of the new· name, the data set cannot be defined
to the Security Subsystem.
Programmer Response: For reason codes:
4 Make the data set RACF-protected, or remove the
RACF indicator.
8 Use a new name acceptable to the Security Subsystem.
112 Invalid Field Parameter List (FPL).
2 Invalid group code in FPL, combination name in test
FPL, or no test condition specified, or inconsistent
group code.
Programmer Response: For reason code:
2 Probable system error in which case one should contact
IBM for programming support. However, if a user
program is interfacing directly with VSAM catalog
management, the Field Parameter List contains
improper data.
114 A duplicate RACF profile exists.
0,4,8, As a result of an IMPORT, IMPORTRA, or DEFINE
command, VSAM has attempted to establish a RACF
102
Section 4: IDC Messages - A~cess Methocl Services
4-37
VS2.03.807
profile for a cluster/alternate index, data, or index
object (0, 4, and 8 respectively). This failed because a
profile with the same name already exists.
Programmer Response: For reason codes:
0,4,8 Either (1) issue an IMPORT or DEFINE command for the
data set with a different cluster/alternate index, data,
or index name, or (2) have the owner of the profile with
the name you wish to use delete that profile and
associated data, if any.
116 VSAM catalog records are invalid. VSAM catalog
records (with the exception of volume records)
connected with the current operation cannot be
properly interpreted.
4-37.0
VS2 System Messages (VS2.03.807)
2
4
6
8
10
12
14
16
No data returned from EXTRACT for cluster/alternate
index (AIX) processing.
Index entry type not obtained in cluster / AIX processing.
Data entry type not obtained in cluster / AIX processing.
No data returned from EXTRACT for path processing.
Error attempting to obtain AIX data record.
Error attempting to obtain AIX index record.
Error attempting to obtain data record for upgrade
entry.
Error attempting to obtain index record for upgrade
entry.
Section 4: IDC Messages - Access Method Services
4-37.1
VS2.03.807
20 Error attempting to obtain base cluster data record.
22 Error attempting to obtain base cluster index record.
24 Invalid association returned during upgrade retrieval.
Programmer Response: For reason codes:
2,4,6,8,10,12,14,16,20,22,24 The VSAM catalog may need
to be r~stored if the entries in error eannot be deleted by use
of the Access Method Services DELETE command.
118 Data set name ineligible for RACF definition.
0,4,8 As the result of a DEFINE, IMPORT, or IMPORTRA
command, VSAM attempted to define a RACF profile for
a cluster/alternate index, data, or index object (reason
code 0, 4, or 8 respectively). The profile could not be established because this data set cannot be defined to
the Security Subsystem.
Programmer Response: For reason codes:
0,4,8 Examine the requirements for defining a data set in
the Security Subsystem as specified in your installation's
security subsystem documentation. Modify the data set
characteristics (usually, name) accordingly.
Attempt to modify non-existent or system field. This is
120
a system error.
Programmer Response: For reason codes:
o Call IBM for programming support.
124 Invalid control interval number.
2 Invalid RBA return code from VSAM record
management.
4 Define of a VSAM catalog and the VSAM open
encountered an incorrect record.
6 Catalog Control Record (CCR) was retrieved
erroneously.
8 Invalid catalog recovery area (CRA) control interval
number encountered.
Programmer Response: For reason codes:
2,4,
6,8 System error indicating that the VSAM catalog or
catalog recovery area may need to be restored. Use of
the Access Method Services List catalog (LiSTCAT) or
list catalog recovery area (LiSTCRA) may be in error. It
may be necessary to contact IBM for programming
support.
128 User-provided storage is outside user region. Probable
system error.
2 Storage validity check failed on user Field Parameter
List (FPL) or on the user work area referenced from the
Catalog Parameter List (CPL).
6 Catalog Parameter List (CPL) field that references the
work area is zero.
Programmer Response: For reason codes:
2,6 Contact IBM for programming support unless a
user-written program is interfacing directly with VSAM
catalog management.
Invalid pointer value in argument list. Probable system
132
error.
2 No pointer to volume list.
4 No catalog Field Parameter List to access method data
statistics block of data.
6 No catalog Field Vector Table from cluster level.
8 No pointer in catalog Field Parameter List to data set
attributes.
10 No catalog Field Parameter List for volume space
parameters.
12 No pointer to expiration date value.
14 No pointer to creation date in catalog Field Parameter
List.
16 No pointer to device type in catalog Field Parameter
List.
18 No catalog Field Parameter List in catalog Field Vector
Table.
4·38
VS2 System Messages (VS2.03.807)
20
22
24
26
No pointer to the work area.
No pointer to password data of related object.
No pointer to OWNERID in catalog Field Parameter List.
No pointer to cluster space parameter in catalog Field
Parameter List.
28 No pointer to data space parameter in catalog Field
Parameter List.
30 No pointer to index space parameter in catalog Field
Parameter List.
32. No buffer size catalog Field Parameter List in data
catalog Field Vector Table.
34 No buffer size catalog Field Parameter List in cluster
catalog Field Vector Table.
36 No buffer size catalog Field Parameter List in index
catalog Field Vector able.
38 No logical record size catalog Field Parameter List in
cluster or data catalog Field Vector Table.
40 No pointer to file sequence number in volume list
catalog Field Parameter List.
Programmer Response: For reason codes:
2,4,6,8,10,12,14, 16, 18,20,22,24,26,28,30,32,34,36,38,40
Contact IBM for programming support unless a user-witten
program is interfacing directly with VSAM catalog management.
136 Required parameters not supplied. Probable system
error.
2 No length for volume serial list area.
4 Missing dname parameter with define unique data set.
6 Missing cluster entry name.
8 Missing space parameter catalog Field Parameter List in
space catalog Field Vector Table.
10 Missing VOLSER list pointer in space catalog Field
Vector Table.
12 Missing dname pointer in space catalog Field Vector
Table.
16 No space parameter on 'cluster' or 'data' catalog Field
Vector Table.
18 Average logical record size misSing.
20 No key specified.
22 Unigue data set needs DO statement for rename or DO
statement misSing.
.24 No entries in volume list.
26 No entries in device type list.
32 An alias name was not provided on a DEFINE command.
34 Generatiol1 data group limit or attribute data were not
provided on a DEFINE command.
36 No Volume Mount Table (VMT) address supplied in the
Catalog Parameter List (CPL) from VSAM
open/ close/ end-of-volume.
Programmer Response: For reason codes:
2,4,6,8,10,12,16,18,20,24,26,36 Contact IBM for
programming support.
22 Supply a dname job control statement.
32,34 Correct the DEFINE command and re-run the job.
140 Inconsistent or conflicting arguments provided.
2 Index component found for relative record data set or
entry-sequenced data set. This is a system error.
4 Key range is invalid for catalog define or the Key
ranges are not specified in ascending sequence in the
DEFINE of a VSAM Key sequenced data set.
6 Key ranges found on both data and cluster catalog Field
Vector Table. This is a system error.
8 Work area too small. This is a system error.
10 Space parameters found on both cluster and data
catalog Field Vector Table. This is a system error.
12 Buffer size specified more than once. This is a system
error.
14 Average logical record specified on index catalog Field
Vector Table. This is a system error.
16
18
20
Average logical record not valid for catalog DEFINE.
This is a system error.
Average logical record size size specified on cluster and
data catalog Field Vector Table. This is a system error.
The key lengths for data and index are not equal. This
is a system error.
22
24
Inconsistent volume lists with different names in each
list.
Primary allocation for data space less than required for
the catalog.
Section 4: ,IDC· Messages - Access Method Services
4-38.1
4-38.2
VS2 System Messages (VS2.03.807)
26
,....
"
Invalid space request type for catalog DEFINE. This is a
system error.
28 Unequal number of volume serial numbers and file
sequence numbers in list entries.
30 More device type entries exist than volume serial
numbers.
34 Invalid space request type on DEFINE. This is a system
error.
40 Dname not specified for a recoverable catalog.
44 Relative-record data set has a maximum record length
which is not equal to the average record length.
46 EXCEPTION EXIT was specified for a VSAM (not
enhanced VSAM) entry.
48 Access Method Services ALTER of the expiration date
field for a nonVSAM (not enhanced VSAM) catalog
entry.
50 Invalid update extend request.
52 Invalid input to VSAM catalog upgrade management.
54 Index component control interval number not provided
as input for reset of a reusable data set processing in
VSAM Catalog Management.
Programmer Response: For reason codes:
2,6,8,10,12,14,16,18,20,26,34 If the reason code indicates
a system error, co.ntact IBM for programming support.
Otherwise, follow the programmer response indicated by the
reason code.
4 Correct the DEFINE command.
22 Correct the VOLUMES parameter or the dname job
control statement.
24 Increase the space quantity and rerun the job.
28,30,
44 Correct the input and rerun the job.
40 Supply the FILE parameter and rerun the job.
46 ALTER exception exit is not possible for VSAM (not
enhanced VSAM) data sets.
48 Do not attempt to alter non-existent data.
50,52,
54 System error. Contact IBM for programming support.
144 Invalid entry name format or the name has an initial
character as a numeric.
2 Invalid first character (non-alphabetic); Alternate index
or path name is invalid; first character must be
alphabetic.
4 Unique name invalid because it uses Z999999 which is
restricted.
6 Data and index names are not allowed for a catalog.
8 A syntax error was encountered in examining a
generation data group name.
Programmer Response: For reason codes:
2 Correct the entry name.
4 Correct the name to avoid Z999999.
6 Avoid the use of names at the INDEX and DATA level
of DEFINE MASTERCATALOG and DEFINE
USERCATALOG.
8 Correct the name and're-run the job.
148 Volume already owned by another VSAM catalog.
Programmer Response: For reason code:
o Specify a different volume and rerun the command or
use the. Access Method Services ALTER R.EMOVE
VOLUMES command to reset the volume ownership if a
catalog should not own the volume.
152 Cannot delete a non-empty catalog.
Programmer Response: For reason code:
o If it is desired to delete the catalog without deleting all
of its entries, the FORCE parameter can' be specified on
the Access Method Services DELETE CATALOG
command.
Volume does not contain a data space with sufficient
space for another VSAM data set. There is insufficient
space in the data spaces allocated on the volume to
satisfy a request for suballocation.
Programmer Response: For reason code:
o Use the DEFINE command to create more data spaces;
or delete unneeded VSAM data sets; or decrease the
amount of storage required by the object being defined.
160 Deletion of space object did not cause volume to be
deleted. A DELETE command which deletes a space
object will cause all data spaces found on the volume
to be deleted, except for those which still contain data
belonging to non-deleted VSAM data sets. This is
merely an informational message. Note: this error code
is always returned when DELETE space is requested for
a volume. containing a catalog.
Programmer Response: For reason code:
o If it is desired to delete all VSAM space and relinquish
volume ownership without deleting all of the objects,
the FORCE parameter may be Lised. This cannot be
used on a catalog volume. Also, all VSAM objects on
the volu·me must still be explicitly deleted from the
catalog.
164 Insufficient storage available for work area. This
condition arises when there is insufficient virtual storage
available for VSAM catalog management.
2 GETMAIN failure, insufficient virtual storage available.
10 GETMAIN failure, insufficient virtual storage available
for the Catalog Communication Area.
Programmer Response: For reason codes:
2,10 Increase the region size available to the step~
168 Unsupported device type.
2 An Access Method Services DEFINE or IMPORT
command specifies a device type that was not system
generated into the system, or is not acceptable for a
VSAM. catalog or data set.
4 An invalid device name was specified on a define of a
non-VSAM entry.
Programmer Response: For reason codes:
2,4 Specify a device type or· device name that is acceptable
to the system.
172 Duplicate data space name on volume. A DEFINE
command specifies the name of a data set, with the
UNIQUE attribute, but there is already. a data set on the
specified volume with that name; such a data set might
be a non-VSAM data set. This will also occur when a
key-sequenced data set with the UNIQUE attribute
specifies more than one key range on the same volume.
2 Duplicate name on volume during a define of a unique
data set.
4 Duplicate name on volume during an update extend
request in VSAM catalog management.
Programmer Response: For reason codes:
2,4 Select another data set name, scratch the original data
set from the volume or ensure that there are as many
volumes as key ranges for define of ,a unique KSDS.
176 No space in VTOC (volume table of contents) for DSCB
(data set control block). During the definition or
extension of. a data space, an attempt was made to
perform a DADSM allocate or extend function on a
volume in which a new DSCB was to have been written,
but there is no space in the VTOC for an additional
DSCB.
Programmer Response: For reason code:
o Delete any unneeded data sets or data spaces from the
volume, in order to make additional DSCBs available, or
recreate the volume with a larger VTOC.
180 Data space name not found. Probable system error.
156
Section 4: IDC Messages - Access Method Services
4-39
VS2.03.807
Programmer Response: For reason code:
Perform the problem determination action. The catalog
or a volume may have been totally or partially
destroyed.
184 Data set currently open and cannot be deleted or
altered. This condition arises when two different jobs
are referencing the same VSAM data set
simultaneously.
4 The data or index component (or both) is (are) in use
and the data set cannot be deleted.
6 The data component of the page data set is in use or
resides. on the same volume as another data component
of a page data set which is in use. The data set cannot
be deleted or altered.
Programmer Response: For reason code:
4 Rerun the command, and to ensure proper completion,
specify a disposition parameter of OLD, not SHR.
6 Rerun the command ensuring that the page data set is
not active or any other page data set on the same
volume is not active.
188 Catalog unavailable for the remainder of processing
which establishes volumes as candidates for future
extension. This occurs during define of VSAM data sets
only when another error is encountered during
candidate processing. This code appears as a reason
code for the volumes that are not processed due to the
other error code which will appear in the Access
Method Services job stream output.
2 No Request Parameter List was found to be available
for processing of a VSAM catalog request. The request
is ignored until the catalog is available.
Programmer Response: For reason code:
2 If this error causes a job to terminate, contact IBM for
programming support. Otherwise, it is only a means of
communicating a condition within the system that is not
an error.
188 Correct the error associated with the other error code
and rerun the job.
192 Maximum logical record length specified is greater than
32,761 for a non-spanned data set.
Programmer· Response: For reason code:
o Reduce the maximum logical record length or define the.
data set as spanned.
196 Data component control interval size specified is
greater than 32,767.
o Programmer Response: For reason code: Reduce the
control interval size of the data component.
200
Index component control interval size specified is
greater than maximum block size of index device.
Programmer Response: For reason code:
o Reduce the control interval size of the index component
or use a different device with a larger maximum block
size.
204
Key specification extends beyond end of maximum
logical record.
Programmer Response: For reason code:
o Reduce the key length, change the key position, or
increase the logical record length.
208
Buffer space specified is too small. The buffer size
specified during a define action is too small to contain
the minimum number of control intervals for the type of
VSAM data set being defined. An indexed data set
requires enough virtual storage for two data component
control intervals, plus one for an index component
control interval; a non-indexed data set requires two for
the data component.
Programmer Response: . For reason code:
o
1
4-40
VS2 System Messages
(V~2.03.807)
o
Increase the buffer size specified (via the
BUFFERSPACE parameter of the DEFINE command).
212 Control interval size calculation unsolvable. This
condition arises should VSAM Catalog Management be
unable to compute an acceptable control interval size
value. This condition only occurs in the DEFINE and
IMPORT commands.
o Control interval and/or control area calcl.llations are
unsolvable with specified parameters.
4 Specified and default values result in only one control
interval per control area for a key-sequenced data set.
6 Two times the maximum index CONTROUNTERVALSIZE
is greater than the physical block size for nonunique.
8 Two times the maximum index CONTROUNTERVALSIZE
is greater than the physical block size for unique object.
10 Buffer space too small for nonunique object.
Programmer Response: For reason codes:
Refer to OS/VS Virtual Storage Access Method (VSAM)
Programmer's Guide to determine which of the
specifications (buffer size, control interval size, device
type, logical record size, and the UNIQUE attribute) may
have caused the problem.
4 Correct the input and rerun the job.
6,8 Correct the block size or control interval size and rerun
the job.
10 Correct the buffer size and rerun the job.
216 VTOC (volume table of contents) of volume is invalid.
The volume's VTOC is not interpretable.
4 Invalid VTOC deleted during update extend processing
for a VSAM data set.
Programmer Response: For reason code:
4 Have the volume restored in order to correct the VTOC.
220
DOS VTOC cannot be converted to an OS VTOC. During
the initial allocation or extension of a data space on a
DOS formatted volume, an error occurred in DADSM
when it attempted to convert the DOS VTOC to an OS
VTOC.
x The reason code represents the OS/VS DADSM error
return code passed back to the VSAM catalog update
extend function.
Programmer Response: For reason code:
x Restore the volume in order to correct the VTOC.
224 A field in a catalog entry has exceeded the maximum
allowable number of repetitions. This condition arises
should one of the repeating fields within the catalog
entry be requested to be extended, and the extension is
not possible; for example, should more than 255
volume serials be attempted to be placed in the entry,
as might happen when an ALTER command attempts,
through the ADDVOLUMES parameter, to add more
candidate volumes to the entry.
System Action: The additional values are not added to the
entry.
o Maximum number of volume extent (group occurrence)
pOinters have been processed.
2 More than 255 volume extent (group occurrence)
pointers ina record,or more than 125 alternate
indexes in the upgrade set.
Programmer Response: For reason codes:
0,2 Determine why the excessive values are being supplied.
226 Test authorization macro failed.
Programmer Response: . For reason code:
4 Contact IBM for programming support.
228 Time-of-day clock read encountered a hardware error.
Programmer Response: For reason code:
o Contact IBM for system support.
o
230
VSAM catalog retrieve of a control interval failed to get
a low range record from the VSAM catalog. Probable
system error.
Programmer Response: For reason code:
o Contact IBM for programming support.
232
x
An error was encountered while VSAM Catalog
Management was performing SMF (System Management
Facility) processing.
The reason code represents the VSAM catalog
management error code corresponding to the error
encountered while performing SMF processing.
41
Section 4: IDC Message. - Acce•• Method Service.
4-40.1
4-40.2
VS2 System Messages (VS2.03.807)
Programmer Response: For reason coCle:
x Examine the reason code returned and rerun the job
after performing the required corrective measures.
234 End of data encountered while reading the low data key
range of the VSAM catalog. Probable system error.
Programmer Response: For reason code:
o Contact IBM for programming support.
236 Error encountered in space-map. This condition arises
when the catalog's volume entry is invalid.
2 Error while scanning the space-map.
4 Invalid run length code found in the space-map.
Programmer Response: For reason codes:
2,4 The volume entry record needs to be reconstructed. If
that is not possible the catalog needs to be restored.
238 No user catalog entry in the master catalog for Convert
Volume processing.
Programmer Response: For reason code:
o Use the Access Method Services IMPORT CONNECT
command to put an entry for the user catalog into the
master catalog.
240 Required DO statement not supplied.
4 The OS/VS DEVTYPE function failed during DEFINE
processing.
8 Invalid device type encountered during DEFINE
processing.
14 Delete of a unique object but no DO statement
supplied.
16 Delete of a non-VSAM object with the scratch option
but no DO statement supplied.
18 Delete of a VSAM object with the erase option but no
DO statement supplied.
22 No DDname match found in the TIOT.
34 Unable to determine the DO statement name for a
catalog recovery area (CRA).
36 A required DO statement is missing.
Programmer Response: For reason codes:
4,8,14,16,18,22,34,36 Provide the required parameter, or
ensure that the DO statement name is correctly spelled, or
that the DO statement is present for the step. Also, ensure
that the volumes can be allocated by dynamic allocation. If all
of this seems to be proper, contact IBM for programming
support.
242 A physical I/O error occurred trying to erase the data
set being deleted.
x The reason codes are those corresponding to a VSAM
Record Management physical I/O error.
Programmer Response: For reason code:
x Rerun with the NO ERASE option. Data set cannot be
deleted.
244 Erase action failed. This condition arises should VSAM
Catalog Management be unable to open the VSAM data
set being deleted.
System Action: The delete action on that data set is voided.
Programmer Response: For reason codes:
x Determine why the erasure was impossible.
Alternatively, rerun the DELETE command with the
NO ERASE option. Reason codes are returned from
VSAM open.
248 Volume record not found. This condition arises when a
function requires a volume that is not owned by the
VSAM catalog being used.
Programmer Response: For reason code:
o If this occurs during a define action, check whether the
volumes specified in the VOLUMES parameter have
been defined in the catalog in which t~e present
DEFINE command is cataloging a new VSAM object; if
not, execute a define of a space object against the
volumes. Further, the volumes might already be owned
by a catalog other than the one in which the current
object is being defined. In this case, choose other
volumes or cause the volume to be owned by the
current catalog. Similarly, this condition may arise
during an IMPORT or ALTER operation.
250 VSAM Record Management has found a logical error
during erase processing while deleting a VSAM data set.
System Action: The delete action on that data set is ignored,
processing continues.
Programmer Response: For reason codes:
x The data set cannot be erased. Rerun the DELETE
command with the NOERASE option. Reason codes are
from VSAM Record Management logical I/O error.
IDC30101 UNABLE TO OPEN din
Explanation: The dname specified in the command with dsn
indicated either concatenated catalogs or a data set different
from dsn.
System Action: The command terminates with a condi~iori
code of 12.
'
Programmer Response: Ensure that the dname specified in the
command does not identify a DO statement that defines
concatenated catalogs, unless the desired catalog is the first in
the concatenation. Ensure that the command and the JCL
specify the same data set.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IDC30121 ENTRY entryname NOT FOUND
Explanation: The data set name supplied by the user is not in
the specified catalog. See the associated second-level
message for the specific catalog management error code
values. In the TSO environment the second-level message is
not displayed, except by request. To request it, enter a
question mark (?) after the TSO READY message.
System Action: Processing associated with the entry not found
is terminated.
Programmer Response: Check that the entry name is spelled
correctly; verify the use of JOBCAT and STEPCAT catalogs, if
employed.
IDC30131 DUPLICATE DATA SET NAME
Explanation: The data set name supplied by the user is already
in the specified catalog. See the associated second-level
message for the specific catalog management error code
values. In the TSO environment the second-level message is
not displayed, except by request. To request it, enter a
question make (?) after the TSO READY message.
System Action: Processing of the command is terminated.
Programmer Response: Check that the entry name is spelled
correctly; verify the use of the JOBCAT and STEPCAT catalogs,
if employed.
IDC30141 CATALOG ERROR
Explanation: An error occurred during a catalog operation. See
the associated second-level message for the specific catalog
management error code values. In the TSO environment the
second-level message is not 'displayed, except by request. To
request it, enter a question mark (?) after the TSO READY
message.
System Action: Processing associated with the catalog error is
terminated.
Programmer Response: See the programmer response
associated with the second-level message.
IDC30161 CATALOG IS NOT AVAILABLE
Explanation: A required catalog is unavailable to perform the
Section 4: IDC Messages - Access Method Services
4-41
I
VS2.03.807
specified command. See the associated second-level message
for the specific catalog management error code values. In the
TSO environment the second-level message is not displayed,
except by request. To request it, enter a question. mark (?)
after the TSO READY. message.
System Action: The command is terminated.
Programmer Response: Ensure that the catalog specified by
the command exists or determine why it cannot be accessed.
IDC30171 INSUFFICIENT SPACE IN CATALOG
Explanation: The catalog is full. There is no more space on the
volume in which the catalog resides, or the maximum number
of extents has been reached. See the associated second-level
message for the specific catalog management error code
values. In the TSO environment the second-level message is
not displayed, except by request. To request it, enter a
question mark (?) after the TSO READY message.
System Action: The command is terminated.
Programmer Response: Scratch unneeded data sets from the
volume; delete unneeded VSAM data sets. See your system
programmer for assistance in reorganizing the catalog.
IDC30211 USER VOLUME NOT MOUNTED
l.
Explanation: An attempt to update the VTOC on a volume
failed because the volume was not mounted. See the
associated second-level message for the specific catalog
management error code values. In the TSO environment the
second-level message is not displayed, except by request. To
request it, enter a question mark (1) after the TSO READY
message.
System Action: The command is terminated.
Programmer Response: Ensure that the volume is mounted.
IDC3.0221 INVALID RELATED OBJECT
Explanation: The object specified in the RELATE parameter of
a DEFINE command does not exist, or is improper for the type
of object being defined. See the associated second-level
message for the specific catalog management error code
values. In the TSO environment the second-level message is
not displayed, except by request. To request it, enter a
question mark (?) after the TSO READY message.
System Action: The command is terminated.
Programmer Response: Correct the DEFINE command so that
the entry named in the RELATE parameter is correct.
IDC30t81 SECURITY VERIFICATION FAILED
Explanation: The number of attempts (see the ATIEMPTS
parameter of the DEFINE command in OS /VS2 Access Method
Services) was exceeded by the operator, or the user-specified
verification routine (see the AUTHORIZATION parameter of the
DEFINE command) failed to authorize use of the data set or
the user's RACF authorization was inadequate. See the
associated second-level message for the specific catalog
management error code values. In the TSO environment the
second-level message is not displayed, except by request. To
request it, enter a question mark (?) after the TSO READY
message.
System Action: The command is terminated.
Programmer Response: Correct the password specified, obtain
the required RACFauthorization, or determine why the
verification routine did not allow access.
IDC30t91 INVALID ENTRY TYPE FOR REQUESTED ACTIO.N
Explanation: This condition arises if, for example, an attempt
was made to DELETE an index component of a VSAM data set.
See the associated second-level message for the specific
catalog management error code values. In the TSO
environment the second-level message is not displayed, except
by request. To request it, enter a question mark (?) after the
TSO READY message.
System Action: The command is terminated.
Programmer Response: Ensure that the specified action is
allowed for this entry type. The entry type can be validated by
the LlSTCAT command.
IDC30201 INSUFFICIENT SPACE ON USER VOLUME
Explanation: A specified volume cannot accommodate either
the initial allocation of space or a subsequent extension. See
the associated second-level message for the specific catalog
management error code values. In the TSO environment tl:le
second-level message is not displayed, except by request. To
request it, enter a question mark (?) after the TSO READY
message.
System Action: The command is terminated.
Programmer Response: Scratch unneeded data sets from the
volume, or execute an ALTER command to add candidate
volumes for the data set.
IDC30231 UNEXPIRED PURGE DATE
Explanation: An attempt to delete an entry failed because its
expiration date. has not been reached, and the PURGE option
was not specified. See the associated second-level message
for the specific catalog management error code values. In the
TSO environment the second-level message is not desplayed,
except by request. To request it, enter a question mark (?)
after the TSO READY message.
System Action: The command is terminated.
Programmer Response: . Specify the PURGE option, if desired,
and rerun the command.
IDC30241 VOLUME OWNED BY ANOTHER CATALOG
Explanation: Only one catalog may own (that is, allocate space
upon) a given volume. Se the associated second-level
message for the specific catalog management error code
values. In the TSO environment the second-level message is
not displayed, except by request. To request it, enter a
q~estion mark (?) after the TSO READY message.
System Action: The command is terminated.
Programmer Response: Specify an unowned volume and rerun
the command, or use the ALTER REMOVEVOLUMES command
to reset the volume ownership if a catalog does not own the
volume.
IDC30251
INSUFFICIENT SUBALLOCATION DATA SPACE
Explanation: A volume does not contain a data space with
sufficient room for allocation of another VSAM data set. See
the associated second-level message for the specific catalog
management error code values. In the TSO environment the
second-level message is not displayed, except by request. To
request it, enter a question mark (?) after the TSO READY
message.
System Action: The command is terminated.
Programmmer Response: Use the DEFINE command to create
additional data space, delete unneeded VSAM data sets, or
decrease the amount of storage required by the object being
defined.
IDC30261
DUPLICATE DATA SPACE NAME ON VOLUME
Explanation: A DEFINE operation specifies the name of a data
set, with the UNIQUE attribute, but there is already a data set
4·42
VS2 System Messages (VS2.03.807)
'.
on the volume with the same name. This will also occur when
attempting to define a KSDS, with the UNIQUE attribute, which
has more than one key range on the same volume. See the
associated second-level message for the specific catalog
41
Section 4: IDC Messages - Access Method Services
4-42.1
4-42.2
VS2 System Messages (VS2.03.807)
VS2.03.807
management error code values. In the T$O environment the
second-level message is not displayed, except by request. To
request it, enter a question mark (?) after the TSO READY
message.
System Action: The command is terminated.
Programmer Response: Choose another data set name;
scratch the original data set from the volume; or if duplication
is due to key ranges, ensure each UNIQUE keyrange is on a
separate volume.
IDC30271 NO SPAt:E IN VTOC FOR DSCB
Explanation: During the definition or extension of a data
space, an attempt was made to perform a DADSM allocate or
extend function, but there was no space in the VTOC for an
additional DSCb. See the associated second-level message for
the specific catalog management error code values. In the TSO
environment the second-level message is not displayed, except
by request. To request it, enter a question mark (?) after the
TSO READY message.
System Action: The command is terminated.
Programmer Response: Delete any unneeded data sets or data
spaces from the volume to make additional DSCBs available,
or recreate the volume with a larger VTOC.
IDC30281 DATA SET IN USE
Explanation: The data set is currently open and cannot be
deleted. This conition arises when two different jobs are
referencing the same VSAM data set simultaneously. See the
associated second-level essage for the specific catalog
management error code values. In the TSO environment the
second-level message is not displayed, except by request. To
request it, enter a question mark (1) after the TSO READY
message.
System Action: The command is terminated.
Programmer Response: Rerun the command and specify
disposition of OLD, not SHR.
IDC30291
LOGICAL RECORD LENGTH EXCEEDS 32761
Explanation: The maximum logical record length specified is
greater than 32,761 for a non-spanned data set. See the
associated second-level message for the specific catalog
management error code values. In the TSOenvironment the
second-level message is not displayed, except by request. To
request it, enter a question mark (?) after the TSO READY
message.
System Action: The command is terminated.
Programmer Response: Reduce the maximum logical record
length or define the data set as spanned.
IDC30301 CONTROL INTERVAL SIZE TOO LARGE
Explanation: The data component control interval size
specified is greater than 32,767; or the index component
control interval size is greater than the maximum block size of
the index device. See the associated second-level message for
the specific catalog management error code values. In the TSO
environment the second-level message is not displayed, except
by request. To request it, enter a question mark (1) after the
TSO READY message.
System Action: The command is terminated.
Programmer Response: Reduce the control interval size; or
use a different device with a larger blocksize, if the error
occurred due to the index component's device type.
IDC30311 KEY EXTENDS BEYOND MAXIMUM RECORD LENGTH
Explanation: The KEY specification extends beyond the end of
the maximum logical record. See the associated second-level
message for the specific catalog· management error code
values. In the TSO environment the second-level message is
not displayed, except by request. To request it, enter a
question mark (1) after the TSO READY message.
System Action: The command is terminated.
Programmer Response: Reduce the key length, change the key
position, or increase the record length.
IDC30321 BUFFERSPACE TOO SMALL
Explanation: The buffersize specified during a define operation
is too small to contain the mi,nimum number of control
intervals for the VSAM data set being defined. See the
associated second-level message for the specific catalog
management error code values. In the TSO environment the
second-level message is not displayed, except by request. To
request it, enter a question mark (1) after the TSO READY
message.
System Action: The command is terminated.
Programmer Response: Increase the BUFFERSPACE parameter
of the DEFINE command.
IDC30331 VOLUME RECORD NOT FOUND IN CATALOG
Explanation: This condition arises when a function requires a
volume that is not owned by the VSAM catalog being used.
See the associated sec;ond-Ievel message for the specific
catalog management error code values. In the TSO
environment the second-level message is not displayed, except
by request. To request it, enter a question mark (1) after the
TSO READY message.
System Action: The command is terminated.
Programmer Response: Ensure that the volumes specified have
been defined in the catalog against which the request is being
issued.
IDC30341 COMMAND FAILED DURE TO DUPLICATE RACF
PROFILE
Explanation: As the result of an IMPORT, IMPORTRA or a
DEFINE command, VSAM Calalog Management has attempted
to establish a profile. This attempt failed because a profile with
the same name exists.
Note that in addition to this message, an IDC30091 message
with a 114 return code will also be issued.
System Action:: The command is terminated.
Programmer Response: Check the reason code on the
accompanying IDC30091 message. Take the recommended
action for this reason code and rerun the job.
IDC30361 DATASET COULD NOT BE DEFINED TO SECURITY
SUBSYSTEM
Ecplanation: Catalog management attempted to define a RACF
profile for the data set. The security Subsystem rejected the
RACF DEFINE command because the characteristics of the
user and/or the data set makes the data set not eligible for
definition.
System Action: The command is terminated.
Programmer Response: Compare the characteristics of the
data set with the inclusion standards of the Security
Subsystem package as specified in your installation's security
subsystem documentation. Modify the data set characteristics
accordingly and rerun the job.
IDC30621 "'''' CARTRIDGE LABELS AND INVENTORY RECORD
NOT RESTORED
Explanation: An error was encountered while relabeling a mass
storage volume. The attempt to restore the labels of the
cartridges and Inventory data set to their original status failed.
Section 4: IDC Messages - Access Method Services
4-43
•
The volume serial mismatch may exist between the cartridge
labels and volume label for the volume. See the preceding
message for further explanation of the problem.
Programmer Response: Correct the problem as idnetified in
the preceding message and take the following actions for the
command that failed:
• If a Rename Operation Failed for AODV
Run ADDV to backout or retry the rename operation if the
volume is inactive. If the volume is active, run MODIFYV or
STOREY to either backout or retry the rename operation.
If the ADDV, MODIFYV, or STOREV commands are run to
recover from a rename failure, a DO statement for the
volume is required and must specify deferred mounting.
The values specified for the VOLUME and NEWSERIAL
parameters depend upon how the volume record is recorded
443.0
VS2 System Messages (VS2.03.807)
in the Inventory data set. If the cartridge labels have been
updated, the volume record will be identified by the new
volume serial number. For the VOLUME parameter, specify
the volume serial number as recorded in the cartridge labels
and the volume record. For the NEWSERIAL parameter,
specify the desired volume serial number. Note that the
security check for nonVSAM status and password protected
data sets is bypassed only if the NEWSERIAL parameter
specifies the same volume serial number as recorded in the
Inventory data set for the volume label. This allows the
original volume serial number of a VSAM volume to be
restored if the volume is left partially renamed.
I~,
/
Section 4: IDC Messages - Access Method Services
4-43.1
If ADDV, MODIFYV, or STOREY terminates without indicating
the status of the rename operation, LlSTMSVI can be run to
determine whether the volume is flagged for recovery
purposes. If the mismatch flag is set in the volume record,
LlSTMSVI not only lists the standard information for the
volume but also highlights the preceding volume and that
serial number 'nnnnnn' is recorded in the volume label of
the volume.
• If a Rename Operation Failed for MODIFYV
To recover from a MODIFYV rename failure 1) run ADDV to
activate the volume if the volume is merely inactive and has
no volume serial mismatch condition, or 2) run ADDV to
both activate the volume and complete the rename
operation if the volume is both inactive and has a volume
serial mismatch condition, or 3) rerun MODIFYV to complete
or retry the rename operation if the volume is active but
has a mismatch condition, or 4) run STOREY to complete or
retry the rename operation if the volume is active and if a
duplicate volume serial number is desired as a result of the
rename.
For the DO statement requirements, the proper VOLUME
and NEWSERIAL parameter values, and use of LlSTMSVI,
refer to the description above for an ADDV rename failure.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, 34a,
and 34c.
IDC30661
coco UNABLE TO CLEAR INCOMPLETE - COPY FLAG
FROM INVENTORY RECORD
Explanation: The incomplete-copy flag in the Inventory record
for the volume could not be cleared. See the preceding
message for further explanatioFl of the failure.
System Action: The command terminates with an error
message.
Programmer Response: Correct the problem as indicated in
the preceding message. Take one of the following actions for
the command that failed:
• If a Copy Operation Failed in COPYV
Rerun COPYV to complete the copy operation to the
incomplete copy volume (COPYV will reuse the cartridges of
the incomplete copy volume for the new copy) or run
SCRATCHY to scratch the incomplete copy volume before
rerunning the COPYV command.
If COPYV terminates without indicating the status of the
copy operation, LlStMSVI can be run to determine whether
the volume is flagged for recovery purposes. If the
incomplete copy flag is set in the copy volume record,
LlSTMSVI not only lists the standard information for the
volume but also highlights the volume report with a note
that a copy operation failed for the preceding copy volume.
• If a Copy Operation Failed for RECOVERV
Rerun RECOVERV to complete the recover operation to the
target volume that is flagged as an incomplete copy volume.
Otherwise, run SCRATCHY to scratch the target volume. The
incomplete copy volume may even be used as the target
volume in the CONVERTV command. In all cases, the empty
VTOC check or security check for password protected data
sets is bypassed.
If the SCRATCHY command is run, the DO statement is not
required for the volume and if provided, must specify
deferred mounting. If the RECOVERV command is rerun, the
DO statement is not required for the target volume, which is
flagged as an incomplete copy, unless the volume serial
number of the target volume is different from the source
volume. If a DO statement is provided for the target
volume, deferred mounting must be specified. If a VSAM
catalog is on the volume, a DO statement for the catalog is
4·44
VS2 System Messages (VS2.03.807)
not required; if provided, deferred mounting must be
specified.
If RECOVERV terminates without indicating the status of the
recover operation, LlSTMSVI can be run to determine
whether the volume is flagged for recovery purposes. If the
incomplete copy flag is set in the target volume record,
LlSTMSVI not only lists the standard information for the
volume but also highlights the volume report with a note
that a copy operation failed for the preceding volume.
• If a Copy Operation Failed for CONVERTV
Rerun CONVERTV to complete the conversion operation to
the target volume that is flagged as an incomplete copy
volume. Otherwise, run SCRATCHY to scratch the target
volume. The incomplete copy volume may even be used as
the target volume in the RECOVERV command. In all cases,
the empty VTOC check or the security check for password
protected data sets is bypassed.
If the SCRATCHY command is run, the DO statement is not
required for the incompletely copied volume and if provided,
must specify deferred mounting. If a VSAM catalog is on the
volume and a DO statement for the target volume must be
provided and must specify deferrred mounting. If a VSAM
catalog is on the volume and a DO statement is provided
for the catalog, the DO statement must also specify
deferrred mounting.
If CONVERTV terminates without indicating the status of the
conversion operation, LlSTMSVI can be run to determine
whether the volume is flagged for recovery purposes. If the
incomplete copy flag is set in the target volume record,
LlSTMSVI not only lists the standard information for the
volume but also highlights the volume report with a note
that a copy operation failed for the preceding volume.
Problem Determination: Table I, item 2, 3, 4, 13, 29, 35a, and
35c.
IDC30671 FROM I TO
CATALOG
VOLUME yolser OWNED BY A VSAM
Explanation: Volume (volser) is owned by a VSAM catalog and
cannot be used. "From" and "to" designate which volume is
unusable for those commands processing both a source and
target volume having the same volume serial numbers.
System Action: The command terminates with a message.
Programmer Response: Before running the command, either:
• Select a volume not cataloged in a VSAM catalog.
• Use the Access Method Services DELETE command to
delete all VSAM data sets and data spaces on the volume,
provided the volume is active and mountable.
• Do not specify a new serial number through the NEWSERIAL
parameter in the command statement.
Problem Determination: Table I, item 2, 3, 4, 13, 25b, 29, 31,
and 35c.
IDC30701
coco SERIAL I OWNER I SERIAL, OWNER NOT
UPDATED IN VOLUME LABEL [OF TO VOLUME]
Explanation: Either the volume serial number or owner name
or poth was not updated in the volume label as requested. For
those commands processing both a source and target volume
having the same volume serial number, 'of to volume' indicates
which volume could not be updated. A mismatch may exist
between the cartridge labels and the volume label for the mass
storage volume. See the preceding message for further
explanation of the problem.
System Action: The command terminates with a message
reflecting the severity of the error.
Programmer Response: Take one of the following actions for
the command that failed:
• If a Rename Operation Failed for ADDV
Run ADDV to backout or retry the rename operation if the
volume is inactive. If the volume is active, run MODIFYV .or
STOREY to either backout or retry the rename operation.
If the AODV, MODIFYV, or STOREY commands are run to
recover from a rename failure, a DO statement for the
volume is required and must specify deferred mounting.
The values specified for the VOLUME and NEWSERIAL
parameters depend upon how the volume record is recorded
in the Inventory data set. If the volume record is identified
by the new volume serial number because the cartridge
labels have been updated, both the VOLUME and
NEWSERIAL parameters must specify the new volume serial
number. Otherwise, specify the old volume serial number
with the VOLUME parameter and the desired value for the
new volume serial number with the NEWSERIAL parameter.
Note that the security check for nonVSAM status and
password protected data sets is bypassed only if the
NEWSERIAL parameter specifies the same volume serial
number as recorded in the Inventory data set for the
volume label. This allows the original volume serial number
of a VSAM volume to be restored if the volume is left
partially renamed.
If ADDV, MODIFYV, or STOREY terminates without indicating
the status of the rename operation, L1STMSVI can be run to
determine whether the volume is flagged for recovery
purposes. If the mismatch flag is set in the volume record,
L1STMSVI not only lists the standard information for the
volume but also highlights the volume report with a note
that a rename operation failed for the preceding volume and
that serial number 'nnnnnn' is recorded in the volume label
of the volume.
• If a Rename Operation Failed for MODIFYV
To recover from a MOOIFYV rename failure 1) run ADDV to
activate the volume if the volume is merely inactiVe and has
no volume serial mismatch condition, or 2) run ADDV to
both activate the volume and complete the rename
operation if the volume is both inactive and has a volume
serial mismatch condition, or 3) rerun MODIFYV to complete
or retry the rename operation if the volume is active but
has a mismatch condition, or 4) run STOREY to complete or
retry the rename operation if the volume is active and if a
duplicate volume serial number is desired as a result of the
rename.
For the DO statement requirements, the proper VOLUME
and NEWSERIAL parameter values, and use of L1STMSVI,
refer to the description above for an ADDV rename failure.
• If a Rename Operation Failed for STOREY
Rerun STOREY or run MOOIFYV to either backout or retry
the rename operation.
For the DO statement requirements, the proper VOLUME
and NEWSERIAL parameter values, and use of L1STMSVI,
refer to the ,description above for an ADDV rename failure.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC3071I
)
**
COPY NOT COMPLETED
Explanation: The copy operation failed. The target volume is
marked incomplete in the Inventory data set and will be reused
when the command is rerun. See the preceding message for
further explanation of the failure.
System Action: The command terminates with an error
message.
Programmer Response: Correct the error as identified by the
preceding message. To rerun the command, follow the
appropriate recovery actions identified in the recovery section
of the publication, "OS/VS Mass Storage System (MSS)
Services for Space Management", GC35-0012.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 30,
35a, and 35c.
IDC30721 VOLUME ATTRIBUTES DO NOT AGREE WITH GROUP
ATTRIBUTES
Explanation: One or more of the specified volume attributes
(bind/ nobind, readonly / readwrite, dasderase / nodasderase,
exclusive/shared) do not agree with the group level
specifications for all general-use volumes belonging to the
group.
System Action: The command terminates with an error
message.
Programmer Response: Use the L1STMSVI command to list the
group level specifications. Rerun the command with volume
attributes specified that correspond to the group that the
volume is being assigned to.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC30771
**
CART csn [csn] NOT IN MSF FOR VOL volser
Explanation: The cartridges assigned to volume (volser) cannot •
be found in the Mass Storage Facility (MSF). The cartridge
serial numbers (csn [csn]) identify the sequence one and/or
sequence two cartridge not in the MSF. See the preceding
message for additional information.
System Action: The command terminates with a message.
Programmer Response: Correct the problem as indicated in
the preceding message. If the cartridges are outside the MSF,
reenter the cartridges and rerun the command.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC30811
** RECORD NOT RETRIEVED FROM INVENTORY FOR
COPY yyddd, NO. nnn
Explanation: The record cannot be accessed in the Inventory
data set for the. copy created on the date indicated by
"yyddd" and assigned the copy sequenced number (nnn) for
that date. See the preceding message for a further explanation
of the error.
System Action: The command terminates with a message
unless additional copies are to be processed.
Programmer Response: Correct the error as indicated in the
preceding message. Before rerunning the command, ensure
that copy date and sequence number are specified correctly.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 30,
35a, and 35c.
IDC30821
**
COPY NOT PERFORMED
Explanation: The copy operation could not be started to the
target volume. The target volume remains usable since the
original data on the volume has not been destroyed. See the
preceding message for a further explanation of the problem.
System Action: The command terminates with an error
message.
Programmer Response: Correct the error as identified in the
preceding message. To rerun the command, follow the
appropriate recovery actions identified in the recovery section
of the publication "OS/VS Mass Storage System (MSS)
Services for Space Management", GC35-0012.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 30,
35a, and 35c.
IDC30891
A DUPLICATE VOLUME EXISTS WITH SERIAL NO.
volser
Explanation: More than one volume with the volume serial
Section 4: IDC Messages - Access Method Services
4-45
number (volser) is recorded in the Inventory data set.
Duplicate volumes within the same Mass Storage System occur
when:
• The record is deleted from the Inventory data set for an
ejected volume and before the volume is reentered the
serial number has been assigned to another volume.
• The reocrd for an ejected copy volume is deleted from the
Inventory data set and the copy is reentered.
• A volume is entered in the Mass Storage Facility from
another Mass Storage System.
System Action: The command terminates with an error
message.
Prograrrlmer Response: Run the L1STMSVI command to obtain
the sequence one and sequence two cartridge serial numbers
of the correct volume to be processed. Rerun the command
specifying either cartridge serial number with the CARTRIDGE
parameter so that the command can select the correct volume.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC30901
VOLUME volser CANNOT BE RELABELED:
READONLY ATTRIBUTE IS ASSIGNED
Explanation: Volume (volser) has the attribute assigned which
prohibits any changes to be made to the volume.
System -Action: The command terminates with a message
identifying the severity of the error.
Programmer Response: If the volume is recorded as active in
the Inventory data set, use the MODIFYV command to change
the READONLY attribute to READWRITE. If the volume to be
relabeled is inactive, use the ADDV command and specify the
READWRITE parameter.
Problem Determination: Table I, items 2, 3, 4, 13, and 29.
IDC30921
FILE PARAMETER WITH DEFERRED MOUNT
REQUIRED
Explanation: The volume is recorded in the Inventory data set
as incompletely created, incompletely copied, or as having a
volume serial number mismatch. These problems may cause
dynamic allocation of the volume to encounter an error.
Therefore, this command requires a FILE parameter on the
command statement. The FILE parameter must specify the
name of a JCL DO statement which allocates a unit with
deferred mounting to prevent allocation from mounting the
volume.
System Action: The command terminates with a message
identifying the severity of the error.
Programmer Response: Rerun the command with the FILE
parameter specifying the name of a JCL DO statement which
allocates a unit with deferred mounting.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, 35a,
and 35c.
IDC30941
VOLUME volser CANNOT BE RENAMED; COPIES
EXIST
Explanation: The volume serial number cannot be changed on
volume (volser) because there are existing copies of the
volume made via the COPYV command.
System Action: The command terminates with an error
message.
Programmer Response: Run the SCRATCHY command to
scratch all existing copies of the volume and rerun the
command. If the copies must be saved, run the EJECTV
command with the NORECORD option for each copy volume,
or run the REMOVEVR command if the copy is already ejected.
This deletes the copy volume record information recorded in
the Inventory data set and permits the original volume to be
renamed. (However, if an ejected copy volume, not recorded in
4-46
VS2 System Messages
(VS2 Release 3.7)
the Inventory data set, is reentered in the Mass Storage
Facility, the copy will be recorded as a duplicate volume.)
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC30991
LENGTH OF CARTRIDGE SERIAL NUMBER csn
INVALID
Explanation: A cartridge serial number cannot be less than
eleven characters in length. The message identifies the
cartridge serial number (csn) with the invalid length.
System Action: The command terminates with a message
unless additional cartridges have been specified for processing.
Programmer Response: Specify an 11- or 12-character
cartridge serial number and rerun the command. If a cartridge
serial number of 11 characters is specified, the command
extends the cartridge serial number to 12 characters by
inserting a blank character in the fourth position from the left.
If you specify 12 characters, be sure to include the value in
quotes because a blank is required as the fourth character.
Problem Determination: Table I, items 2, 3, 4, 13, and 29.
IDC31I31
INVALID LEVEL PARAMETER
Explanation: There is an asterisk (*) in the last position of the
LEVEL parameter.
System Action: The command terminates.
Programmer Response: Remove the asterisk from the last
position of the LEVEL parameter, and rerun the command.
Problem Determination: Table I, items 1, 2, 3, 4, 13, and 29.
IDC31901
'keywd' PARAMETER INVALID WITH ENTRY TYPE
Explanation: The specified keyword, 'keywd', is improper for
the type of object being altered. This is usually a problem in
distinguishing between cluster and data/index component
attributes.
System Action: The command is terminated.
Programmer Response: Specify the proper data set name and
rerun the command.
Problem Determination: Table I, items 4, 29.
IOC32001 TOO MANY POSITIONAL PARAMETERS AFTER 'prm'
Explanation: A parameter list has too many positional
parameters specified.
System Action: Processing skips to the end of the command;
interpretation of commands resumes with the next command.
Programmer Response: Remove the excess parameters and
rerun the command.
Problem Determination: Table I, items 4, 29.
IDC32011
CONSTANT 'xxx' EXCEEDS LENGTH LIMIT
Explanation: A constant is longer than the maximum allowed
by the parameter definition or by the implementation. An
allowable value must be specified.
System Action: Processing skips to the end of the command;
interpretation resumes with the next command.
Programmer Response: See the definition of the parameter
value in question, specify an allowable value, and rerun the
command.
Problem Determination: Table I, items 4, 29.
IDC32021
ABOVE TEXT BYPASSED UNTIL NEXT COMMAND.
CONDITION CODE IS 12.
Explanation: Following the occurrence of an error in the
current command, the remainder of the command is bypassed.
An error message preceding this message in the program
listing will pinpoint the error.
i~
I,
\~
System Action: No further syntax or semantic checking is
done on the command in question.
Programmer Response: Correct the related error and rerun.
Problem Determination: Table I, items 4, 29.
IDC32031
ITEM 'xxx' DOES NOT ADHERE TO RESTRICTIONS
Explanation: A constant (xxx) does not meet the naming
restrictions on its format. This is usually a problem in
specifying data set names; see OS/VS2 Access Method
Services for data naming conventions.
System Action: Processing skips to the end of the command;
interpretation resumes with the next command.
Programmer Response: Check the data restrictions for the
parameter, correct the item, and rerun the command.
Problem Determination: Table I, items 4, 29.
IDC32051
DELIMITER 'x' IS NOT PROPERLY PRECEDED BY A
CONSTANT OR KEYWORD
Explanation: A delimiter has been specified where a
subparameter list or data should have appeared. The delimiter
is being used improperly. Parentheses are likely to be improper
or a positional parameter may be missing.
System Action: Processing skips to the end of the command;
interpretation resumes with the next command.
Programmer Response: Correct the usage and rerun the
command.
Problem Determination: Table I, items 4, 29.
IDC32071
REMAINDER OF COMMAND INPUT STREAM
IGNORED
Explanation: An error has occurred that prohibits further
scanning of the input stream. There are preceding error
messages to explain the error. The condition code (MAXCC) is
always set to 16 when the remainder of the input stream is
ignored.
System Action: The remainder of the command input stream
has been ignored.
Programmer Response: Correct the related error and rerun the
job.
Problem Determination: Table I, items 4, 29.
IDC32081
LEFT PARENTHESIS MISSING FOLLOWING KEYWORD
'keywd'
Explanation: A keyword is not properly followed by an opening
parenthesis delimiting the subparameter list or constants
associated with the keyword.
System Action: Processing skips to the end of the command;
interpretation resumes with the next command.
Programmer Response: Check the requirements of the
parameter, correct the usage, and rerun the command.
Problem Determination: Table I, items 4, 29.
IDC32091
RIGHT PARENTHESIS MISSING AFTER 'xxx'
Explanation: A right parenthesis is missing which should
delimit the end of one or more constants. Too many items
might be specified.
System Action: Processing skips to the end of the command;
interpretation resumes with the next command.
Programmer Response: Correct the usage and rerun the
command.
Problem Determination: Table I, items 4, 29.
IDC32101
System Action: Processing skips to the end of the command;
interpretation begins with the next command.
Programmer Response: Correct the usage and rerun the
command.
Problem Determination: Table I, items 4, 29.
INVALID PARENTHESES FOR SPECIFYING REPEATED
SUBPARAMETER LIST
Explanation: Parentheses for delimiting repetitions of a
repeated subparameter list are missing or unmatched.
IDC32111
KEYWORD 'keywd' IS IMPROPER
Explanation: A keyword has been found which is not
recognized in its specified usage. It may be misspelled, not
applicable, or specified as a subparameter in the wrong
sub parameter list.
System Action: Processing skips t.o the end of the command;
interpretation begins with the next command.
Programmer Response: Check the usage of the keyword and
check parentheses.
Problem Determination: Table I, items 4, 29.
IDC32121
INVALID LEFT PARENTHESIS AFTER 'prm'
Explanation: A left parenthesis appears to delimit a positional
parameter. However, the positional parameter is not a constant
or list of constants, so no parentheses are allowed.
System Action: Processing skips to the end of the command;
interpretation begins with the next command.
Programmer Response: Correct the usage and rerun.
Problem Determination: Table I, items 4, 29.
IDC32131
KEYWORD 'keywd' APPEARS TOO OFTEN
Explanation: A keyword has been coded more than once in the
same parameter list or subparameter list.
System Action: Processing skips to the end of the command;
interpretation begins with the next command,
Programmer Response: Remove the redundant keyword and
rerun the command.
Problem Determination: Table I, items 4, 29.
IDC32141 HEX OR BINARY CONSTANT SPECIFIED
IMPROPERLY
Explanation: A hexadecimal or binary constant is not of the
form X'···' or B'···'.
System Action: Processing skips to the end of the command;
interpretation begins with the next command.
Programmer Response: Correct the usage and rerun.
Problem Determination: Table I, items 4, 29.
IDC32161 ABOVE TEXT BYPASSED UNTIL NEXT COMMAND
Explanation: Following the occurrence of an error in the
current command, the remainder of the command is bypassed.
An error message preceding this message will pinpoint the
error. The command was being scanned for syntax checking
purposes only when the error was found.
System Action: No further syntax or semantic checking is
done on the command in question. The system condition code
is not affected.
Programmer Response: Correct the related error before
rerunning.
Problem Determination: Table I, items 4, 29.
IDC32171 PASSWORD IMPROPER AFTER 'prm'
Explanation: A password is found following a data item that
does not allow a password.
System Action: Processing skips to the end of the command;
interpretation begins with the next command.
Programmer Response: Remove the improper password and
rerun the command.
Problem Determination: Table I, items 4, 29.
Section 4: IDC Messages· Access Method Services
4-47
I
••
IDC32181 TOO MANY REPEATED SUBPARAMETER LISTS
APPEAR
Explanation: More repeated subparameter lists are coded than
are allowed.
System Action: Processing skips to the end of the command;
interpretation begins with the next command.
Programmer Response: Check the parameter description to
see how many repetitions are allowed. Correct the usage and
rerun.
Problem Determination: Table I, items 4, 29.
IDC32191 VERB NAME 'verb' UNKNOWN
Explanation: The specified verb name is not known to the
system.
System Action: Processing skips to the end of the command;
interpretation begins with the next command.
f>rogrammer Response: Correct the improper verb name and
rerun.
Problem Determination: Table I, items 4, 29.
IDC32201
IMPROPER NUMERIC DIGIT FOUND IN 'prm'
Explanation: An invalid numeric digit has been found. A
decimal number may use only 0-9, a hexadecimal number
specified as X'---' may use only 0-9 and A-F, and a binary
number specified as S'---' may use only digits 0 and 1.
System Action: Processing skips to the end of the command;
interpretation begins with the next command.
Programmer Response: Correct the usage and rerun.
Problem Determination: Table I, items 4, 29.
IDC32211 CONSTANT 'xxx' NOT WITHIN VALUE RANGE
Explanation: A constant is of a value not within the range of
values allowed for this parameter.
System Action: Processing skips to the end of the command;
interpretation begins with the next command.
Programmer Response: Correct the usage and rerun.
Otherwise, take no action.
Problem Determination: Table I, items 4, 29.
IDC32231
TOO MANY CONSTANTS IN LIST BEGINNING AT
'xxx'
Explanation: Too many constants have been coded in a list.
System Action: Processing skips to the end of the command;
interpretation begins with the next command.
Programmer Response: Check the parameter definition to see
how many constants appear in the list. Correct the usage and
rerun.
Problem Determination: Table I, items 4, 29.
System Action: Processing skips to the end of the command;
interpretation begins with the next command.
Programmer Response: Remove one of the parameters and
rerun.
Problem Determination: Table I, items 4, 29.
IDC32401
IDC32411
INVALID 'prm' NAME-xxx
Explanation: A DSNAME or DDNAME does not adhere to
naming restrictions. xxx represents the first sixty-four
characters of the name, if more than sixty-four characters
were entered.
System Action: The user is prompted for a valid name. See
message IDC32491.
Programmer Response: Enter a valid name.
Problem Determination: Table I, items 13, 20, 29.
IDC32421
'prm' VALUE HAS INVALID LENGTH-xxx
Explanation: A constant is either too long or has a null length.
xxx is the first sixty-three characters of the constant, if more
than sixty-three were entered.
System Action: The user is prompted for a valid constant. See
message IDC32491.
Programmer Response: Enter a valid constant.
Problem Determination: Table I, items 13, 20, 29.
IDC32431
'prm' LIST TOO LONG BEGINNING AT xxx
Explanation: A list of nonnumeric constants or subparameter
lists has too many elements. xxx is the first sixty-three
characters, of the constant, if more than sixty-three characters
were entered.
System Action: The user is prompted to indicate whether or
not the excess list elements may be ignored. See message
IDC32501.
Programmer Response: Enter 'OK' to allow the excess
elements to be ignored. Any other response terminates the
command.
Problem Determination: Table I, items 13, 20, 29.
IDC32441
IDC32251
'prm' VALUE OF 'nnn' OUT OF RANGE
Explanation: A number is either larger or smaller than is
allowed for the specified parameter. nnn represents the first
ten digits of the number.
System Action: The user is prompted for a valid number. See
message IDC32491.
Programmer Response: Enter a number within the allowable
value range.
Problem Determination: Table I, items 13, 20, 29.
REQUIRED (SUB)PARAMETER OF 'prm' IS MISSING
'prml' (REPLY'l') AND prm2 (REPLY '2') ARE IN
CONFLICT
Explanation: A parameter required by the command may be
missing, or a parameter that is coded may require the
specified parameter. The missing parameter may be the
keyword parameter indicated or a positional subparameter of
that parameter.
System Action: Processing skips to the end of the command;
interpretation begins with the next command.
Programmer Response: Add the missing parameter and rerun.
Problem Determination: Table I, items 4, 29.
Explanation: Two parameters have been coded that conflict
with each other.
System Action: The user is prompted to indicate which of the
two parameters should be kept. See message IDC32461.
Programmer Response: Enter '1' to keep the first parameter,
or '2' to keep the second parameter.
Problem Determination: Table I, items 13, 20, 29.
IDC32261
Explanation: This message follows message IDC32441 and
allows the operator to specify which parameter to retain.
System Action: The system waits for the user to reply.
Programmer Response: Enter '1' to keep the first parameter
listed in the preceding message or '2' to keep the second
parameter.
INCONSISTENT PARAMETERS INVOLVING 'keywd'
Explanation: The specified keyword indicates a parameter that
may not be coded in conjunction with some other parameter
that is coded.
4-48
VS2 System Messages
(VS2 Release 3.7)
IDC32461
ENTER REPLY NUMBER OF PARAMETER TO BE
RETAINED
f'
~
IDC32471
ENTER SUBFIELD OF KEYWORD 'keywd'
Explanation: A keyword parameter is missing; it is required by
the command or by some other parameter that has been
coded.
System Action: The system waits for the user to reply. Either
a constant or a subparameter set is required.
Programmer Response: Enter the requested subfield data.
Problem Determination: Table I, items 13, 20, 29.
IDC32481
'prm' LIST TOO LONG BEGINNING AT nnn
Explanation: A list of numbers contains too many elements.
nnn is the first ten digits of the number.
System Action: The user is prompted to indicate whether or
not the excess elements can be ignored. See message
IDC32501.
Programmer Response: Reply 'OK' to allow the excess
elements to be ignored. Any other response terminates the
command.
Problem Determination: Table I, items 13, 20, 29.
IDC32491
REENTER
Explanation: This prompting message follows messages that
identify invalid constants; IDC32401, IDC32411, and IDC32421.
System Action: The user is requested to enter a valid
constant.
Programmer Response: Enter a valid constant.
IDC32501
REPLY 'OK' TO IGNORE EXCESS AND CONTINUE
Explanation: This prompting message follows message
IDC32431 or IDC32481 which indicate too many elements have
been coded in a list.
System Action: The user is prompted to indicate whether or
not the excess elements can be ignored.
Programmer Response: If the response is 'OK' or 'OK', 'OK',
'OK' the excess elements are ignored. Any other response
causes command termination.
IDC32511
FOR SUBFIELD REPETITION nnn
Explanation: This message prefaces any other error message
when the parameter involved in the error is within a repeated
subparameter list. It is used to help identify the problem.
System Action: Processing continues.
Programmer Response: Examine the indicated subparameter
list repetition.
IDC32531
MISSING SUBFIELD OF KEYWORD keyword
Explanation: A keyword subparameter is missing, but the
system is not able to prompt the TSO user for it because a
PROFILE NOPROMPT command has been issued.
System Action: The command processing is terminated.
Operator Response: The TSO user should re-enter the
command with the proper keyword.
Problem Determination: Table I, items 13, 20, and 29.
IDC33001
ERROR OPENING
~:~~~
Explanation: An error was detected attempting to open data
set name (text is ddn if the data set name not available). See
associated message for explanation.
System Action: See associated message for explanation.
Programmer Response: Check the associated message.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33011
ERROR CLOSING dsn
Explanation: An error was detected while attempting to close
dsn. See the associated message in the program listing for
explanation.
System Action: See associated message for explanation.
Programmer Response: Check the associated message.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33021 ACTION ERROR ON dsn
Explanation: An error. was detected while attempting to access
dsn. See the associated message in the program listing for
explanation.
System Action: See associated message for explanation.
Programmer Response: Check the associated message.
Problem Determination: Table I, items 1, 3, 4.
IDC33031
**
CANNOT OPEN FOR UPDATE
Explanation: Only VSAM data sets may be opened for update
mode.
System Action: The data set is not opened, and the command
is terminated.
Programmer Response: Change the DO statement to specify a
VSAM data set.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33041
**
JCL STATEMENT MISSING
Explanation: The DO statement named in a FILE, INFILE, or
OUTFILE parameter cannot be found.
System Action: Processing of the command is terminated.
Programmer Response: Check dnames for incorrect spelling or
check for missing DO statements, correct the error, and rerun
the job.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33051
**
CANNOT BE OPENED FOR OUTPUT
Explanation: The processor cannot open this non-VSAM data
set for output. Specifically, ISAM data sets may not be output
data sets.
System Action: Processing of the command is terminated.
Programmer Response: Change the keyword value to specify
either a VSAM or SAM· data set.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33061
**
PS PROCESSING INVALID FOR KEYED DATA SET
Explanation: Physical sequential acce~s is not possible for the
data set. ISAM data sets may not be processed other than
sequentially by key.
System Action: Processing of the command is terminated.
Programmer Response: Change the JCL statement to specify a
VSAM data set, or correct the usage of the data set.
Problem Determination: TaMe I, items 1, 3, 4, 29.
IDC33071
** DATA SET CANNOT BE OPENED FOR KEYED
PROCESSING
Explanation: Only indexed VSAM and ISAM data sets can be
opened for keyed processing.
System Action: Processing of the command is terminated.
Programmer Response: Change the JCL statement to specify a
keyed data set or correct the usage of the data set in the
command and rerun the job.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33081
**
DUPLICATE RECORD xxx
Explanation: The output data set of a REPRO command
already contains a record with the same key or record number.
For an indexed data set, xxx is the first five bytes of the
duplicate key, in hexadecimal format. For a relative record
Section 4: IDC Messages - Access Method Services
4-49
•
data set, xxx is the relative record number (in decimal) of the
duplicate record.
System Action: The record .is not written, and processing
continues.
Programmer Response: None.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33091
**
RECORD xxx NOT WRITTEN. LENGTH INVALID.
Explanation: Record xxx (where xxx is the first five bytes of
the record in hexadecimal format) was not written for one of
the following reasons:
• The record length was greater than LRECL of output data
set (logical processing).
• The record length was less than LRECL of output data set
and output RECFM = FIXED, or output is a relative record
data set.
• The control-interval length to be written did not equal the
control interval size for the output data set.
System Action: Processing continues until four such errors
occur, in which case no more records are written to the data
set.
Programmer Response: Redefine the output data set with the
correct LRECL or control interval size.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33101
** KEY SUPPLIED IS LONGER THAN KEY LENGTH
OF DATA SET
Explanation: The key supplied for positioning was longer than
the key length of the data set. For example, the key specified
by FROM KEY is longer than the key length of the data set.
System Action: Processing of the command is terminated.
Programmer Response: Specify the correct key on the
command and rerun the job.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33111
**
TYPE OF POSITIONING NOT SUPPORTED
Explanation: Positioning is valid only for VSAM and ISAM data
sets.
System Action: Processing of the command is terminated.
Programmer Response: Respecify the JCL statement defining a
VSAM or ISAM data set or remove the positioning parameter
and rerun the job.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33121
**
SYSTEM UNABLE TO ('PEN
Explanation: DCBOFLG was not set aTter an OPEN request.
System Action: The command is terminated.
Programmer Response: See the OS!VS Data Management Macro
Instructions manual. In the description of the OPEN macro
instruction, check for an explanation of failure to set the
DCBOFLG field in a non-VSAM DCB after an OPEN request.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33131
synad message from system
Explanation: An I/O error occurred for a non-VSAM data set.
The SYNA"~F message is written. (See OS/VS Data
Management Services Guide, GC26-3783.)
System Action: The command is terminated.
Programmer Response: Check the explanation in the SYNADAF
message, correct the error, and resubmit the job.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33141
RECORD xxx OUT OF SEQUENCE
Explanation: The key of the record to be written is lower than
the key of the last record written. xxx is the first five bytes in
4- 50
VS2 System Messages
(VS2 Release 3.7)
hexadecimal format of the key of the record that is out of
sequence.
System Action: Rearrange the records to be written so that
they are in ascending key sequence. Resubmit the job.
Programmer Response: The record can be written to the data
set using skip sequential processing. Rerun the job and the
output data set will be opened for skip sequential processing
(because data already exists in the data set) and records that
were out of sequence will be written.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33151
** RECORD SIZE GREATER THAN 32767 NOT
SUPPORTED
Explanation: The system cannot process a nonVSAM data set
with a logical record length greater than 32767.
System Action: Processing of the command is terminated.
Programmer Response: Change the JCL statement to specify a
logical record length (LRECL, for the DCB) not greater than
32767, and rerun the job.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IDC33161
**
DATA SET IS NOT VSAM CATALOG
Explanation: A request is for a VSAM catalog to be opened
and the data set is not a VSAM catalog.
System Action: The command is terminated.
Programmer Response: Correct the catalog keyword to specify
a user catalog and rerun the job.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33171
**
PERMANENT I/O ERROR
Explanation: An I/O error was detected performing an I/O
operation on the data set named in the preceding message.
System Action: Processing of the command is terminated.
Programmer Response: Check the job control statement to be
sure the data set was correctly defined. If it was correctly
defined, a hardware I/O error was encountered and the data
set must be created in a new location.
Problem Determination: Table I, items 1, 2, 3, 4, 29 or 30.
IDC331S1
**
INVALID DATA SET SPECIFICATION
Explanation: A STOW was issued against the data set, but the
specified DCB is not open or is opened incorrectly.
System Action: Processing is terminated.
Programmer Response: Do the problem determination action.
Problem Determination: Table I, items 1, 2, 3, 4, Sa, 16, and
29.
IDC33211
**
OPEN/CLOSE/EOV ABEND EXIT TAKEN
Explanation: The OPEN/CLOSE/EOV SVC routines detected an
error, and an ABEND message has been written to the system
output data set.
System Action: The command is terminated.
Programmer Response: Check the WTP message written by the
OPEN/CLOSE routine, correct the error, and resubmit the job.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC33221
**
DATA SET ORGANIZATION IS NOT VSAM
Explanation: A request for an existing data set indicated the
data set was VSAM. The data set was in fact not VSAM.
System Action: The command is terminated.
Programmer Response: Correct the data set name or type and
rerun the job.
Problem Determination: Table I, items 1, 3, 4, 25a, 29.
VS2.03.808
IDC33251
** INCORRECT BLOCKSIZE SPECIFIED FOR
IMPORTRA
Explanation: The data set cannot be opened due to an
incorrect block size in the INFILE parameter.
System Action: Processing of the IMPORTRA command is
terminated.
Programmer Response: Change the block size in the INFILE
parameter to that used in the EXPORTRA command and rerun
the job.
IDC33261
** REPLACE INVALID FOR OUTPUT THROUGH A
PATH
Explanation: The user has specified the REPLACE parameter in
a REPRO command when the output data set is a path.
REPLACE processing is not allowed for an output path.
System Action: Processing of the command is terminated.
Programmer Response: If the input does not contain any
records duplicating prime keys (and alternate keys of any
upgrade set alternate index having the UNIQUEKEY attribute)
in the output, the user may still execute REPRO by simply
removing the REPLACE parameter.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IDC33271
** DUPLICATE RECORD IN UPGRADE SET - BASE
RECORD xxx
Explanation: During a REPRO operation an attempt has been
made to add a record to the output base cluster. However, a
duplicate record in the upgrade set has been encountered
when upgrading an alternate index with the UNIQUEKEY
attribute over the output data set. If the base cluster is a
key-sequenced data set, xxx is the first five bytes of the prime
key expressed in hexadecimal. If the base cluster is an
entry-sequenced data set, xxx is the first five bytes of the
record expressed in hexadecimal.
System Action: The record is not written into the base cluster.
Processing continues until four action errors occur, at which
point processing terminates.
Programmer Response: If the UNIQUEKEY attribute was
correctly specified, the base cluster record being added is in
error and must be corrected. If the UNIQUEKEY attribute was
incorrectly specified, it may be changed to NONUNIQUEKEY
using the ALTER command. Rerun the job using just those
records that were in error as input.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IDC33301
**
**
mem ALREADY EXISTS
Explanation: A member with the new member name already
exists in the PDS directory.
System Action: The command is terminated.
Programmer Response: Specify a different new name and
rerun the job.
Problem Determination: Table I, items 1, 2, 4, 29.
IDC33321
**
IDC33331
**
CATALOG IS NOT EMPTY
Explanation: The REPRO command to copy a source catalog
into a target catalog failed because the target catalog was not
empty or was empty but had been used (that is, had entries
defined in it, then deleted from it).
System Action: The copy operation isn't carried out, and the
command is terminated.
Programmer Response: Make sure that you have specified the
correct target catalog. If you have, use the L1STCAT command
to determine whether the catalog is empty. If it is empty,
delete it and redefine it. If it is not empty, delete whatever is
defined in it and then delete it and redefine it. Reissue the
REPRO command.
Problem Determination: Table I, items I, 3, 4, 34a.
IDC33341
**
INVALID CI NUMBER
Explanation: The REPRO command to copy a source catalog
into a target catalog failed because there was an invalid
control-interval number in an entry in the source catalog.
System Action: The copy operation isn't carried out, and the
command is terminated.
Programmer Response: Use the L1STCAT command to list all
of the entries in the source catalog. Examine messages from
L1STCAT to determine the entry that contains the invalid
control-interval number. Use the DELETE command to delete
that entry. If the DELETE fails, use the PRINT command to get
a dump-format listing of the source catalog to identify the
catalog record that contains the invalid control-interval number
and to determine what the control-interval number should be.
(For a description of the contents and interrelationship of
catalog records, see OS /VS2 Catalog Management Logic.)
Contact IBM for programming support.
Problem Determination: Table I, items 1, 3, 4, 29, 34a.
IDC33501
SYNAD MESSAGE FROM VSAM
Explanation: An I/O error occurred for a VSAM data set. The
format and explanations of VSAM I/O errors are provided in
OS/VS Virtual Storage Access Method (VSAM) Programmer'~
Guide.
System Action: Processing continues if possible.
Programmer Response: Check the explanation of the error,
correct, and resubmit the job.
Problem Determination: Table I, items 1, 3, 4, 29.
xxx NOT FOUND
Explanation: The entry indicated by xxx does not exist in the
directory.
System Action: The command is terminated.
Programmer Response: Correct the entry name and rerun the
job.
Problem Determination: Table I, items 1, 2, 4, 29.
IDC33311
Problem Determination: Table I, items 1, 3, 4, 29.
INSUFFICIENT MAIN STORAGE
Explanation: There is not sufficient main storage allocated.
System Action: The job is terminated.
Programmer Response: Specify a larger region size and rerun
the job.
IDC33511
**
VSAM {OPEN I CLOSE I I/O} RETURN CODE IS rc
Explanation: An error was encountered during VSAM open,
close, or action request execution, as indicated in the text of
the message. In the message, rc is the error code returned by
VSAM. The VSAM return codes are as follows:
CLOSE Error
Return
Code Meaning
4 The data set indicated by the access-method control
block is already closed.
132 An uncorrectable I/O error occurred while VSAM was
reading the job file control block (JFCB).
136 Not enough virtual storage was available in the
program's address space for a work area for CLOSE.
144 An uncorrectable I/O error occurred while VSAM was
reading or writing a catalog record.
148 An unidentified error occurred while VSAM was
searching the catalog.
184 An uncorrectable I/O error occurred while VSAM was
completing outstanding I/O requests.
Section 4: IDC Messages - Access Method Services
4-51
236
4-51.0
A permanent destaging error occurred in the Mass
Storage System (RELINQUISH). With temporary CLOSE,
VS2 System Messages (VS2.03.S0S)
Section 4: IDC Messages - Access Method Services
4-51.1
a destaging error or a staging error (ACQUIRE) occurred.
OPEN Error
0 When register 15 contains 0, no error. When register 15
contains 8, either (1) VSAM is processing the
access-method control block for some other request, or
(2) DDNAME was not specified in the access-method
control block.
4 The data set indicated by the access-method control
block is already open.
96 Warning message: an unusable data set was opened for
input.
100 Warning message: OPEN encountered an empty
alternate index that is part of an upgrade set.
104 Warning message: the time stamp of the volume on
which a data set is stored doesn't match the system
time stamp in the data set's catalog recold; this
indicates that extent information in the catalog record
may not agree with the extents indicated in the
volume's VTOC.
108 Warning message: the time stamps of a data
component and an index component do not match; this
indicates that either the data or the index has been
updated separately from the other.
116 Warning message: the data set was not properly closed.
Data may be lost if processing continues; the Access
Method Services VERIFY command may be used to
cause the data set to be properly closed. See OS /VS2
Access Method Services, for a description of the VERIFY
command.
128 The DD statement is missing or its ddname does not
match that in the access-method control block.
132 An uncorrectable I/O error occurred while VSAM was
reading the job file control block (JFCB).
136 Not enough virtual-storage space is available in the
program's address space for work areas, control blocks,
or buffers.
144 An uncorrectable I/O error occurrecl---while VSAM was
reading or writing a catalog record.
148 No record for the data set to be opened was found in
the available catalog(s), or an unidentified error
occurred while VSAM was searching the catalog.
152 Security verification failed; the password specified in
the access-method control block for a specified level of
access doesn't match the password in the catalog for
that level of access.
160 The operands specified in the ACB or GENCB macro
are inconsistent with each other or with the information
in the catalog record.
164 An uncorrectable I/O error occurred while VSAM was
/"
reading the volume label.
168 The data set is not available for the type of processing
you specified, or an attempt was made to open a
reusable data set with the reset option while another
user had the data set open.
176 An error occurred while VSAM was attempting to fix a
page of virtual storage in real storage.
180 A VSAM catalog specified in JCL either does not exist
or is not open, and no record for the data set to be
opened was found in any other catalog.
184 An uncorrectable I/O error occurred while VSAM was
completing an I/O request.
188 The data set indicated by the access-method control
block is not of the type that may be specified by an
access-method control block.
192 An unusable data set was opened for output.
196 Access to data was requested via an empty path.
200 Volume is unusable.
4-52
VS2 System Messages (VS2.03.808)
204
The ACB MACRF specification is GSR and caller is not
operating in protect key 7.
208 The ACB MACRF specification is GSR and caller is using
a VS1 system.
212 The ACB MACRF specification is GSR or LSR and the
data set requires create processing.
216 The ACB MACRF specification is GSR or LSR and the
key length of the data set exceeds the maximum key
length specified in BLDVRP.
220 The ACB MACRF specification is GSR or LSR and the
data set's control interval size exceeds the size of the
largest buffer specified in BLDVRP.
224 Improved control interval processing is specified and
the data set requires create mode processing.
232 Reset was specified for a nonreusable data set and the
data set is not empty.
236 Indicates a stage or destage error.
240 Format-4 DSCB and catalog timestamp verification
failed during volume mount processing for output
processing.
244 The volume containing the catalog recovery area was
not mounted and verified for output processing.
physical Error
4 Read error occurred for a data set.
8 Read error occurred for an index set.
12 Read error occurred for a sequence set.
16 Write error occurred for a data set.
20 Write error occurred for an index set.
24 Write error occurred for a sequence set.
Logical Error
4 End of data set encountered (during sequential
retrieval), or the search argument is greater than the
high key of the data set. Either no EODAD routine is
provided, or one is provided and it returned to VSAM
and the processing program issued another GET.
8 You attempted to store a record with a duplicate key,
or there is a duplicate record for an alternate index
with the unique key option.
12 You attempted to store a record out of ascending key
sequence in skip-sequential mode; record had a
duplicate key; for skip-sequential processing, you GET,
PUT, and POINT requests are not referencing records in
ascending sequence; or, for skip-sequential retrieval,
the key requested is lower than the previous key
requested. For shared resources, buffer pool is full.
16 Record not found.
20 Record already held in exclusive control by another
requestor-.
24 Record resides on a volume that can't be mounted.
28 Data set cannot be extended because VSAM can't
allocate additional direct-access storage space. Either
there is not enough space left to make the secondary
allocation request or you attempted to increase the size
of a data set while processing with SHROPT = 4 and
DISP = SHR.
32 An RBA specified that doesn't give the address of any
data record in the data set.
36 Key ranges were specified for the data set when it was
defined, but no range was specified that includes the
record to be inserted.
40 Insufficient virtual storage in the user's address space
to complete the request.
44 Work area not large enough for the data record (GET
with OPTCD = MVE).
64 As many requests are active as the number specified in
the STRNO parameter of the ACB macro; therefore,
another request cannot be activated.
I'"
~j
VS2.03.808
68
72
76
80
84
88
92
96
100
104
108
112
116
132
136
140
144
148
An attempt was made to use a type of processing
(output or control-interval) that was not specified when
the data set was opened.
You made a keyed request for access to an
entry-sequenced data set, or you issued a GETIX or
PUTIX to an entry-sequenced ro relative record data
set.
You issued an addressed or control-interval PUT to add
t6a key-sequenced data set, or you issued a
control-interval PUT to a relative record data set.
You issued an ERASE request for access to an
entry-sequenced data set, or you issued an ERASE
request for access to an entry-sequenced data set via a
path.
OPTCD = LOC specified for a PUT request or in a
request parameter list in a chain of request parameter
lists.
You issued a sequential GET request without having
caused VSAM to be positioned for it, or you changed
from addressed access to keyed access without causing
VSAM to be positioned for keyed-sequential retrieval;
there was no sequential PUT insert for a relative record
data set, or you attempted an illegal switch between
forward and backward processing.
You issued a PUT for update or an ERASE without a
previous GET for update or a PUT IX without a previous
GETIX.
An attempt was made to change a key while. making an
update.
An attempt was made to change the length of a record
while making an addressed update.
The RPL options are either invalid or conflicting in one
of the following ways:
(1 )SKP was specified and wither KEY was not specified
or BWD was specified.
(2)BWD was specified for CNV processing.
(3)FWD and LRD were specified.
(4)Neither ADR, CNV, nor KEY was specified in the
RPL.
(4)Neither ADR, CNV, nor KEY was specified in the
RPL.
(5)WRTBFR, MRKBFR, or SCHBER was issued was
issued, but either TRANSID was greater than 31 or the
shared resource option was not specified.
(6)ICI processing was specified, but a request other
than a GET or a PUT was issued.
RECLEN specified was larger than the maximum
allowed, equal to 0, or smaller than the sum of the
length and the displacement of the key field; RECLEN
was not equal (slot) size specified for a relative record
data set.
KEYLEN specified was too large or equal to O.
During initial data-set loading (that is, when records are
being stored in the data set the first time it's opened),
GET, POINT, ERASE, direct PUT, skip-sequential PUT
with OPTCD = UPD is not allowed. For initial loading of
a relative record data set, the request was other than a
PUT insert.
An attempt was made in locate mode to retrieve a
spanned record.
You attempted an addressed GET of a spanned record
in a key-sequenced data set.
Inconsistent spanned record.
Invalid pointer (no associated base record) in an
alternate index.
The maximum number of pointers in the alternate index
has been exceeded.
152
Not enough buffers are available to process your
request (shared resouces only).
192 Invalid relative record number.
196 You issued an addressed request to a relative record
data set.
200 You attempted addressed or control-interval access
through a path.
204 PUT insert requests are not allowed in backwar mode.
Note: Refer to OSjVS Virtual Storage. Access Method (VSAM)
Programmer's Guide, GC26-3838, for additional information on
the return codes.
System Action: The action depends on the function being
executed. See the message in the program listing following this
message.
Programmer Response: Correct the cause of the error.
Problem Determination: Table I, items I, 3, 4, 29.
IDC33801
FILE ddname MUST SPECIFY A DEMOUNTABLE UNIT
Explanation: The unit for the file defined by the DO statement
with the name ddname was not assigned for exclusive control.
Volumes cannot be mounted or demounted on this unit. Either
the volume allocated by the DO statement was already
mounted when the statement was processed, or the correct
parameters were not specified on the DO statement.
System Action: The job is terminated.
Programmer Response: Rerun the job after demounting the
volume. This causes the device to be asigned for exclusive
control while the job or step is running. See the discussion of
the FILE parameter on the LlSTDSET or SCRDSET command in
OSjVS Mass Storage System (MSS) Services for Space
Management for further details.
Problem Determination: Table I, items 1, 2, 3, 4, 13, and 29.
IDC33831
FILE ddname MUST SPECIFY A VIRTUAL UNIT
Explanation: The DO statement (ddname) specified through the
FILE parameter does not specify a virtual unit but a virtual unit
is required.
System Action: The command terminates normally.
Programmer Response: Correct the UNIT parameter and rerun
the command.
Problem Determination: Table I, items 1, 2, 3, 4, 13, and 29.
IDC33841
FILE ddname SPECIFIED AN INVALID UNIT FOR
FUNCTION REQUESTED
Explanation: The direct access storage unit, specified on the
DO statement (ddname) through the FILE parameter, is not
supported by this function. The unit is not a direct access
device or, if DASD, is not a 3330 or 3330V.
System Action: The command terminates normally.
Programmer Response: Correct the UNIT parameter and rerun
the command.
Problem Determination: Table I, items 1, 2, 3, 4, 13, and 29.
IDC35001
A VALID VSAM DEFINE STRUCTURE WAS NOT
PROVIDED
Explanation: The object parameter list was not specified
properly. The Access Method Services reader jinterpreter
should have detected this error.
System Action: The command is terminated.
Programmer Response: Probable system error. See OSjVS2
Access Method Services for the valid specification.
Problem Determination: Table I, items 3, 4, 29.
IDC35011
MODEL ENTYPE IS NOT CONSISTENT WITH THE
OBJECT BEING DEFINED
Explanation: The object being used to model a VSAM data set
Section 4: IDC Messages - Access Method Services
4-53
or user catalog differs from that being defined.
Problem Determination: Table I, items 3, 4, 29.
System Action: The command is terminated.
Programmer Response: Probable user error. Ensure that the
IDC35141
model object type is identical to that being defined.
Problem Determination: Table I, items 3, 4, 29.
IDC35031
FILE SEQUENCE LIST IS INCONSISTENT WITH
VOLUME LIST
Explanation: The number of elements in the
FILESEQUENCENUMBERS parameter list is not equal to the
volumes in the VOLUMES parameter list.
System Action: The command is terminated.
Programmer Response: Probable user error. Check the
elements in both lists, and make corrections where needed.
Problem Determination: Table I, items 3, 4, 29.
IDC35041
THE RANGE LIST CANNOT BE CONSTRUCTED
In the construction of the RANGELlST, the
allotted area was not sufficient.
System Action: The command is terminated.
Programmer Response: Possible system error. Rerun the job
with the PARM option--PARM TEST (FULL«DEFN.l.l»);
contact your system programmer.
Problem Determination: Table I, items 3, 4, 16, 29.
Explanation:
IDC35051
INCORRECT SPECIFICATION OF SPACE
ALLOCATION
Explanation: The space parameters TRACKS, CYLINDER, or
RECORDS do not appear on the appropriate object parameter
list.
System Action: The command is terminated.
Programmer Response: Probable user error. See the DEFINE
command and space specifications in as /VS2 Access Method
Services.
Problem Determination: Table I, items 3, 4, 29.
IDC35061
A REQUIRED VOLUME LIST HAS BEEN OMITTED
KEYRANGES ARE INVALID
Explanation: The KEYRANGES parameter (DEFINE or IMPORT
command) specified invalid key values for the low or high key
values:
a) The high key value is lower than the low key value in a
low-key high-key pair.
b) Two or more low-key high-key pairs overlap, or are
identical.
System Action: The command is terminated.
Programmer Response: Correct the KEYRANGES specifications.
IDC35151
AVERAGE RECORD SIZE EXCEEDS MAXIMUM
RECORD SIZE
Explanation: The first size value of the RECORDSIZE parameter
is greater than the second.
System Action: Processing for the command is terminated.
Programmer Response: Correct either the average or the
maximum size value.
IDC35161
KEYS PARAMETER REQUIRED FOR KEY SEQUENCED
DATA SET
Explanation: The definition of a KSDS requires the
specification of the key position and length, via the KEYS
parameter.
System Action: Processing for the command is terminated.
Programmer Response: Correct the DEFINE command.
IDC35171
AVG AND MAX RECORDSIZE NOT EQUAL FOR
RELATIVE RECORD DATA SET
Explanation: The RECORDSIZE parameter specified average
and maximum record sizes that were not equal. Relative record
data sets must have fixed-length records.
System Action: The command is terminated.
Programmer Response: Correct either the average or the
maximum size value.
Explanation: The VOLUMES parameter does not appear in the
command when required.
System Action: The command is terminated.
Programmer Response: Probable user error. A volume list
must be available to DATA and INDEX objects (the INDEX
object appears only if the data set is KSDS). The availability
may be through explicit specification of volumes, via
propagation of volumes from the Cluster parameter list or from
the model object.
Problem Determination: Table I, items 3, 4, 29.
IDC35071
THE RECORDSIZE PARAMETER IS REQUIRED BUT
NOT SPECIFIED
IDC351S1
Explanation: The REUSE attribute may not be specified for a
cluster or an alternate index together with the UNIQUE or
KEYRANGES parameter, either explicitly or implicity thru use of
the MODEL parameter.
System Action: The command is terminated.
Programmer Response: Correct the command by deleting
either the REUSE or the UNIQUE and/or KEYRANGES
parameter; then rerun the job.
IDC35191
Explanation: The RECORDSIZE parameter must be specified
when defining VSAM space and the allocation unit is records.
System Action: The command is- terminated.
Programmer Response: Probable user error. Specify
RECORDSIZE and resubmit the job.
Problem Determination: Table I, items 3, 4, 29.
IDC35131
DYNAMIC ALLOCATION FAILED OR FILE NOT
CODED WHEN REQUIRED
Explanation: This message is issued when the Access Method
Services DEFINE command attempts to dynamically allocate a
volume, and the attempt fails. The preceding messages should
indicate why dynamic allocation failed.
System Action: The command is terminated.
Programmer Response: See the explanations for messages
IDC39031 and IDC39051.
4-54
VS2 System Messages (VS2.03.S0S)
REUSE PARAMETER INVALID WITH UNIQUE OR
KEYRANGES
REUSE ATTRIBUTE CONFLICT BETWEEN DATA AND
INDEX
Explanation: The REUSE attribute was not the same for the
data and index objects. Examples:
1. NOREUSE is specified at the cluster level and REUSE is
specified at the data level with nothing specified at index
level resulting in index defaulting to NOREUSE.
2. Modeling at the cluster level and explicitly overriding model
attributes at data or index level but not both.
System Action: The command is terminated.
Programmer Response: Redefine the object ensuring that data
and index REUSE attributes are in harmony.
IDC35211
SPANNED ATTRIBUTE INVALID FOR A RELATIVE
RECORD DATA SET
Explanation: SPANNED and NUMBERED were specified
VS2.03.807
together, either explicitly or through use of the MODEL
parameter. Records of an RRDS may not span control
intervals.
System Action: The command is terminated.
Programmer Response: Correct the SPANNED parameter or
the data set type specification.
IDC35221 SPANNED ATTRIBUTE REQUIRED FOR RECORDSIZE
GREATER THAN 32,761
Explanation: The RECORDSIZE parameter specifies a maximum
size greater than 32,761, but SPANNED is not specified.
System Action: The command is terminated.
Programmer Response: Correct the RECORDSIZE parametet, or
specify the SPANNED parameter.
IDC35231 GENERATION DATA GROUP NAME EXCEEDS 35
CHARACTERS
IDC35301
ENTRY AND NEWNAME PDS NAMES MUST BE THE
SAME
Explanation: An attempt was made to rename PDS member
but the entry name and the new name referenced different
partitioned data set names.
System Action: Processing continues.
Programmer Response: Make sure that the same PDS name is
given in both the entry name and new name parameters.
IDC35361
INVALID USE OF
PARAMETER
* WITH THE NEWNAME
Explanation: If either the ENTRYNAME or NEWNAME
parameter specifies a generic name (*), then both must.
System Action: The command is terminated.
Programmer Response: Ensure that both the ENTRYNAME and
NEWNAME parameters specify a generic name if either do.
Problem Determination: Table I, items 1, 3, 4, 29.
. Explanation: The name specified for a generation data group
cannot exceed 35 characters.
IDC35371
System Action: The command is terminated.
Programmer Response: Shorten the generation data group
Explanation: Either UPGRADE is specified but the object being
name and rerun the job.
IDC35251 INSUFFICIENT SUCURITY AUTHORIZATION TO
ALTER KEYS
Explanation: The level of password supplied was not high
enough or the RACF authorization was insufficient to permit
the ALTER to occur. To modify KEY values, the master
password of the cluster, alternate index, or path is needed or,
alternatively, the catalog master password could be· supplied.
Since both the data and index components will be altered, if
one component is password-protected and the other is not,
the master password of the protected component is sufficient.
System Action: Processing of the command is terminated.
Programmer Response: Supply the proper level password or
have your RACF profile altered to the required level of access.
Rerun the job.
IDC35271
ALTER WAS UNABLE TO LOCATE ATTRIBUTES OF
OBJECT TO BE MODIFIED
Explanation: The entry to be modified could not be found in
the catalog.
System Action: The command is terminated.
Programmer Response: Verify that the catalog entry exists and
the catalog being used is proper.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC35281 THE OBJECT TO BE MODIFIED IS PASSWORD
SUPPRESSED
Explanation: The MASTERPW password of the entry or the
UPDATEPW or higher level catalog password must be supplied
for modifications to be allowed to the entry.
System Action: The command is terminated.
Programmer Response: Verify which password is required and
provide the password.
IDC35291
NAME CREATED FROM GENERIC NEWNAME IS
LONGER THAN 44 CHARACTERS
Explanation: The Access Method Services ALTER command
issues this message when it is asked to rename data sets
using a generic name, and one of the resulting new data set
names is longer than 44 characters.
System Action: The command is terminated.
Programmer Response: Correct the error and rerun the job.
INVALID ALTERNATE INDEX PARAMETERS
SPECIFIED
altered· is not an alternate index, or UNIQUEKEY is specified
but the data object being altered is not the data object of an
alternate index.
System Action: The command is terminated.
Programmer Response: Correctly specify the name of an
alternate index, or the data object name of an alternate index.
Problem Determination: Table I, items 2, 3, 4, 29.
IDC35381
UNIQUEKEY/UPGRADE INVALID FOR NON-EMPTY
ALTERNATE INDEX
Explanation: The UNIQUEKEY or UPGRADE parameter is
specified, but the alternate index is non-empty. These
parameters may only be specified if the alternate index
contains no records.
System Action: The command is terminated.
Programmer Response: If UNIQUEKEY/UPGRADE alternate
index is truly desired, the alternate index must be deleted and
redefined with proper attributes, then rebuilt with BLDINDEX.
Problem Determination: Table I, items 2, 3, 4, 29.
IDC35391
KEYS AND/OR RECORDSIZE PARAMETER SPECIFIED
FOR NON-EMPTY OBJECT
Explanation: The ALTER command specified the KEYS or
RECORDSIZE parameter, but the cluster or alternate index
contains data records.
System Action: The object's catalog entry is not altered.
Programmer Response: If you want to change key position
and/or record size, you must delete, redefine, and reload the
object.
IDC35401
KEYS/RECORDSIZE VALUES CONFLICT WITH
CONTROL INTERVAL SIZE
Explanation: The new key length, key position, or maximum
record size is such· as to require a larger control interval.
System Action: The object's catalog entrY is not altered.
Programmer Response: Delete and redefine the object with the
proper KEYS and RECORDSIZE parameters.
Problem Determination: None.
IDC35411
NEW ALTERNATE INDEX KEY VALUES CONFLICT
WITH BASE CLUSTER· RECORDSIZE
Explanation: The ALTERcommand for an alternate index
specifies a KEYS parameter for a key whose ending position is
outside the base cluster's maximum record size. If the base
Section 4: IDC Messages - Access Method Services
4-55
cluster is spanned, the ending key position must be in the
base cluster's first control interval.
System Action: The object's catalog entry is not altered.
Programmer Response: Correct the ALTER command or
correct the base cluster's maximum record size or control
interval size.
Problem Determination: Table I, items 3, 4, 34b.
IDC35421 AVG AND MAX RECORDSIZE NOT EQUAL FOR
RELATIVE RECORD DATA SET
Explanation: The RECORDSIZE parameter specified average
and maximum record sizes that were not equal. Relative record
data sets must have fixed-length records.
System Action: Processing of the command is terminated.
Programmer Response: Correct either the average or the
maximum size value.
IDC35451 KEYS AND/OR RECORDSIZE VALUES CANNOT BE
ALTERED
Explanation: The ALTER command specified new KEYS or
maximum RECORDSIZE values for an object whose
corresponding values were specified when the object was
defined, or which have been altered to non-default values.
System Action: The object's catalog entry is not altered.
Programmer Response: Delete and correctly redefine the
object.
Problem Determination: Table I, items 3, 4, 34b.
IDC35461
NEW KEY VALUES CONFLICT WITH RECORDSIZE
Explanation: The ALTER command specifies a KEYS parameter
that defines a key whose ending position is outside the
maximum recordsize.
System Action: Processing of the command is terminated.
Programmer Response: Specify key length and position such
that the key is entirely contained in the base cluster record.
Problem Determination: Table I, item 34b.
IDC35471
ENTRY TYPE INVALID WITH KEYS/RECORDSIZE
PARAMETER
Explanation: The entryname specified is not the data
component of a cluster or alternate index, nor is it a cluster or
alternate index, nor is it a path over a cluster or alternate
index.
System Action: The entry's catalog data is not altered.
Processing of the command is terminated.
Programmer Response: Correct the entryname and rerun the
job.
Problem Determination: Table I, items 3, 4, 34b.
IDC35681
IDC35721 TARGET CATALOG IS TOO SMALL TO CONTAIN THE
BACKUP CATALOG
Explanation: The size of the target catalog is inadequate.
System Action: The command is terminated.
Programmmer Response: Determine size of the backup catalog
from LlSTCAT output obtained at the time of the unload.
Redefine the target catalog with adequate space to contain the
low key range of the catalog.
Problem Determination: Table I, items I, 2, 3, 4, 26b, 34a.
IDC35731 NAME , VOLSER , DEVTYP I OF BACKUP AND
TARGET CATALOG DO NOT AGREE
Explanation: The target catalog name, its volume serial
number, and/or the device type do not agree with the backup.
System Action: The command is terminated.
Programmer Response: Check whether you are reloading from
the proper backup into the intended catalog.
Problem Determination: Table I, items 1, 2, 3, 4, 26b, 34a.
IDC35811 REPRO OF CATALOGS CANNOT SPECIFY
DELIMETERS
Explanation: The REPRO command does not process beginning
and ending delimeters when you are copying catalogs.
System Action: The command is terminated.
Programmer Response: Remove the invalid parameters from
the command and rerun job.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC35821 INPUT DATA SET ORGANIZATION INCOMPATIBLE
WITH OUTPUT DATA SET
Explanation: This error condition arises if you try to copy from
a non-relative record data set to a non-empty relative record
output data set that is not specified for reuse.
System Action: The command is terminated.
Programmer Response: Check the status of the input and
output data sets. REPRO is unable to satisfy your request. Set
up data sets correctly and rerun the job.
Problem Determination: Table I, items 2, 3, 4, and 29.
IDC35831 'parameter' INCOMPATIBLE WITH INFILE DATA SET
TYPE
Explanation: The specified parameter is not correctly used with
this type data set. A conflict results between delimiters and
the data set type. An example is specifying the TOKEY
parameter with an relative-record data sets.
System Action: The command is terminated.
Programmer Response: Correct the parameters or data set
specified and rerun.
Problem Determination: Table I, items 2, 3, 4, and 29.
(xxx) INVALID USE OF '"
Explanation: The level name indicated by xxx starts or ends
IDC35841
with an '" which is not allowed.
System Action: The command is terminated.
Programmer Response: Correct the level name and rerun the
job.
Problem Determination: Table I, items 4, 29.
Explanation: A REPRO command specified a VSAM catalog
IDC35701 DELIMITERS MUST NOT BE SPECIFIED WHEN
RELOADING A CATALOG
Explanation: REPRO command delimiters (FROMKEY, TOKEY,
etc.) cannot be specified for reloading a catalog.
System Action: The command is terminated.
Programmer Response: Remove delimiters from the REPRO
command.
Problem Determination: Table 1, items 1, 2, 3, 4, 34b.
4-56
VS2 System Messages (VS2.03.807)
RECOVERABLE CATALOGS CANNOT BE COPIED
copy operation where either the input catalog or the output
catalog or both was defined with the RECOVERABLE attribute.
Neither the source or target catalog can be recoverable in a
catalog copy operation.
System Action: The command is terminated.
Programmer Response: To convert a nonrecoverable catalog
into a recoverable catalog, you must export each VSAM data
set from the nonrecoverable catalog, then import it into the
newly defined recoverable catalog. To convert a recoverable
catalog into a nonrecoverable catalog or to copy a recoverable
catalog into a recoverable catalog, you can either export each
VSAM data set from the source catalog and then import it into
the target catalog or use the EXPORTRA/IMPORTRA
commands to accomplish the same thing on a volume basis.
Problem Determination: Table I, items 2, 3, 4, and 34b.
IDC36071 DELETE UNSUCCESSFUL - NOT A TEMPORARY
DATA SET
IDC35921 THE ENTRYNAME IS NOT CLUSTER OR ALTERNATE
INDEX
Explanation: The object identified by the entry parameter in
the command is not a cluster or alternate index. Only cluster
or alternate index objects can be exported.
System Action: The command is terminated. No export action
takes place.
Programmer Response: If a user catalog is to be disconnected,
DISCONNECT must be specified in the command. Check to be
sure your entry name is really a cluster or alternate index
object name.
Problem Determination: Table I, items 3, 4, 29.
Explanation: The deletion that was to be attempted was not
IDC35931 A REQUIRED CATALOG FIELD WAS NOT LOCATED
Explanation: One of the following required catalog fields could
not be located by catalog management: ENTYPE, ENTNAME, or
NAMEDS.
System Action: The command is terminated. No export action
takes place.
Programmer Response: Something is wrong with the catalog
entry for this cluster. If this happens, consult your system
programmer.
Problem Determination: Table I, items 3, 4, 29.
IDC35961 THE DATA SET SPECIFIED IN THE EXPORT
PARAMETER IS NOT USABLE
II
Explanation: The data set specified in the EXPORT command
has been marked as not usable by a DELETE FORCE operation,
because of space occupancy conflicts.
System Action: Processing of the command is terminated.
Programmer Response: This data set cannot be exported
under current catalog conditions. If you wish to recover the
data, .use the REPRO or EXPORTRA commands.
Problem Determination: Table I, items 1, 2, 3, 4, 34b.
IDC36021 IMPORT OF DATA SET FAILED AFTER DEFINE DELETE ATTEMPTED
Explanation: The cluster or alternate index being imported was
defined successfully, but an error occurred before all the data
was copied into the newly defined cluster or alternate index.
An attempt is being made to delete the cluster. There is a
message preceding this message in the program listing which
will explain why the import failed (invalid DO statement, I/O
error on portability data set, for instance).
System Action: The command is terminated.
Programmer Response: Consult the message preceding this
message in the program listing.
Problem Determination: Table I, items 1, 3, 4, 29.
IDC36061 PORTABILITY DATA SET IN ERROR
Explanation: The data on the portable dataset is not as was
expected; specifically, the record preceding the data records
for the cluster or alternate index is invalid. Probable user
error.
System Action: The command is terminated.
Programmer Response: Ensure that the portable data set to be
processed by IMPORT was created by EXPORT, or that a
portable data set to processed by IMPORTRA was created by
EXPORTRA. If the problem recurs, do the problem
determination action.
Problem Determination: Table I, items 1, 3, 4, 26c, 29.
performed. A duplicate name was found in the catalog, and the
temporary export flag was not on for the duplicate data set or,
in systems with enhanced VSAM, the data set was not empty.
System Action: The command is terminated.
Programmer Response: Change the name, or delete the
duplicate cluster if you mean to replace it.
Problem Determination: Table I, items 3, 4, 29.
IDC36081 CONNECT FOR dsn FAILED
Explanation: This message merely identifies the name of the
user catalog which could not be connected. A message will
follow to explain the catalog return code received when
attempting to connect the user catalog.
System Action: The command is terminated.
Programmer Response: See the message following this
message in the program listing.
Problem Determination: Table I, items 3, 4, 29.
IDC36091 VOLUME SPECIFICATION NEEDED FOR dsn
Explanation: Volume information could not be found on the
portable data set or in the IMPORT command. Probably either
a portable data set from an earlier release is being imported,
or volume information was specified for a path.
System Action: The command is terminated.
Programmer Response: Volumes must be specified in the
IMPORT command for at least one non-path object comprising
the cluster or alternate index.
Problem Determination: Table I, items 3, 4, 29.
IDC36101 SPECIFICATION OF DEVICE TYPES, VOLUMES
REQUIRED FOR CONNECT
Expla~tion:
When connecting a user catalog, the
DEVICETYPES and VOLUMES parameters, as well as the
catalog name, are required.
System Action: The command is terminated.
Programmer Response: Specify device types and volumes in
the command to connect a user catalog.
Problem Determination: Table I, items 3, 4, 29.
IDC36121 DELETE UNSUCCESSFUL - NOT A CLUSTER OR AIX
Explanation: An attempt was made to delete the duplicate
entry because catalog define of the cluster or alternate index
being imported failed due to the existence of a duplicate name
in the catalog. A locate performed on the name revealed that
the entry was not a cluster or alternate index.
System Action: The command is terminated.
Programmer Response: Use the NEWNAME parameter to
change the name of the cluster or alternate index you are
attempting to import. Do a LlSTCAT to see what you really
have; what you are trying to import has a conflicting name in
the catalog.
Problem Determination: Table I, items 3, 4, 29.
IDC36131 ERROR ENCOUNTERED OPENING PORTABILITY
DATA SET
Explanation: The portability data set could not be opened.
System Action: The command is terminated.
Programmer Response:. None. The preceding message in the
listing explains why the entry data set was not opened.
Problem Determination: Table I, items. 1, 3, 4, 26b, 29.
Section 4: IDC Messages - Access Method Services
4-57
•
VS2.03.807
IDC36141
INVALID NAME IN OBJECTS PARAMETER: obj
Explanation: The name specified in the OBJECT parameter in
the IMPORT command does not match any of the object
names for the VSAM data set being imported.
System Action: The command is "terminated.
Programmer Response: Correct the object name.
, Problem Determination: Table I, items 3, 4, 29.
IDC36151 DSNAME ON THE OUTFILE JCL STATEMENT
INCORRECT
Explanation: The cluster or alternate index name of the
imported data set does not match the data set name specified
in the JCL statement identified by the OUTFILE parameter. The
data set name in the JCL statement must be the same as the
object being imported or a path over it.
System Action: Processing for the command is terminated.
Programmer Response: Correct the data set name
specification in the JCL. Note that if the NEWNAME parameter
is specified, the specified data set name must be that name
specified in this parameter.
IDC36171 ATTRIBUTES OF PREDEFINED ENTRY
INCOMPATIBLE WITH THOSE EXPORTED
Explanation: The data, set being imported into is not consistent
with that one which previously exported and new being
imported. One of the following things is wrong:
(a)The relative key positions are not equal.
(b)The data sets are not of the same type (KSDS, RRDS,
ESDS)
(c)The key lengths are not the same.
(d)The maximum record size of the data set being imported
into is less than that of the data set exported.
System Action: IMPORT processing is terminated.
Programmer Response: Delete and redefine the pre-defined
data set with proper attributes. Then rerun the job.
Problem Determination: Table I, items 3, 4, 2Gb, 34b.
IDC36191 ALTER RENAME FOR IMPORTRA FAILED
Explanation: During processing of an IMPORTRA command, an
ALTER operation to rename the object being imported has
failed. If the OUTFILE parameter is specified, the IMPORTRA
command, which alters the name of each VSAM object that it
defines so it may be opened for loading. The name is changed
to that specified on the job control statements and then back
to the original name after loading.
System Action: Processing of the IMPORTRA command is
terminated.
Programmer Response: Determine the reason for the failure of
the ALTER, correct the problem, and rerun the job.
Problem Determination: Table I, items 2, 3, 4, 29.
was not allowed to occur because the user did not specify the
INTOEMPTY keyword. As a security precaution, the system
does not allow imports into an empty data set unless the
INTOEMPTY keyword has been specified.
System Action: The command is terminated.
Programmer Action: If you own an empty data set into which
ypu have planned to import, rerun the job and specify the
INTOEMPTY keyword. If not, determine who owns the existing
empty data set and resolve the conflict in usage of this data
set name to insure proper protection for your data.
Problem Determination: Table I, items 3,4, 29.
IDC36331 SCANNING ERROR ON OS CATALOG WHILE
PROCESSING 'xxx' INDEX
Explanation: An error occurred while scanning the OS catalog.
Processing was at the indicated index.
System Action: Conversion is terminated.
Programmer Response: Verify that the OS catalog being
converted is valid by listing the OS catalog using IEHLlST. If
the catalog appears valid, rerun the job with a PARM
command as follows:
(PARM TEST (FULL«CCVE,1,1), (CCIE,1,1), (CCSE,1,1»»
This will produce a SNAP dump at the error point.
Problem Determination: Table I, items 1, 3, 4, 25, 29.
IDC36411 dsn NOT A BASE CLUSTER
Explanation: The data set identified by dsn is not a base
cluster or a path over a base cluster. The entry name was
specified in job control identified via (1) the INFILE dname
subparameter or (2) the INDATASET dsname subparameter.
The INFILE or INDATASET data set must be a defined,
non-empty base cluster or a path over a base cluster.
System Action: Processing is terminated for the entire
BLDINDEX command.
Programmer Response: The data set name in the job control
identified via the INFILE subparameter or the data set name in
the INDATASET subparameter must be corrected to be that of
a defined, non-empty base cluster or a path over a base
cluster. Then resubmit the job.
Problem Determination: Table I, items 2, 3, 4, 29, 31.
IDC36431
dsn IS EMPTY
Explanation: The base cluster identified by dsn contains no
records. In order to build an alternate index, the base cluster
must contain at least one record.
System Action: BLDINDEX processing is terminated.
Programmer Response: The base cluster must be loaded via a
user program (alternatively, the Access Method Services
REPRO command may be used) with at least one record. Then
resubmit the job.
Problem Determination: Table I, items 2, 3, 4, 29, 34b.
IDC36241 UNABLE TO OBTAIN OUTPUT DATA SET NAME
IDC36821 FINAL CHARACTER(S) IN volser NOT NUMERIC
Explanation: IMPORTRA was unable to obtain the data set
name from the OUTFILE JCL statement. This is probably due to
an error in the JCL statement.
System Action: Processing is terminated.
Programmer Response: Correct the JCL statement. Ensure that
it contains a data set name, volume, unit, DISP = OLD, and the
AMP =- 'AMORG' parameter.
Problem Determination; Table I, items 2, 3,4, 29.
Explanation: A character in the volume serial number (volser)
is not a numeric value and cannot be incremented to created
new volume serial numbers.
System Action: Function terminates normally.
Programmer Response: Specify a beginning volume serial
number with adequate number of numeric ctiaracters and rerun
the command.
IDC36251
IDC36831 volser PLUS COUNT EXCEEDS MAXIMUM VOLUME
SERIAL NUMBER
'INTOEMPTY' KEYWORD NEEDED TO IMPORT INTO
AN EMPTY DATA SET
Explanation: A duplicately named empty data set was
encountered while attempting to perform the import. The
loading of this data set with the data of the portable data set
4-58
VS2 System Messages (VS2.03.807)
Explanation: The number of volumes to be created, added to
the specified volume serial number (volser), exceeds the
maximum value of 999999.
System Action: Command terminates normally.
Programmer Response: Specify a volume serial number with a
lower number or request less volumes to be created and rerun
the command.
IDC37001
•• LATEST COpy RECORD CANNOT BE RETRIEVED
FROM INVEN.TORY
Explanation: An attempt to access the record for the latest
copy recorded in the Inventory data set failed. The command
checks if the latest copy is incomplete due to a previous copy
failure; the cartridges will be 'reused if an incomplete copy
exists. See the preceding message for the error condition.
System Action: The command terminates with an error
message.
Programmer Response: Correct the problem as indicated in
the preceding message and rerun the command.
Section 4: IDC Messages· Access Method Services
4-~.1
4-58.2
VS2 System Messages (VS2.03.807)
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC37011
** OLDEST BACKUP COPY RECORD CANNOT BE
RETRIEVED FROM INVENTORY
Explanation: An attempt to access the record for the oldest
backup copy volume recorded in the Inventory data set failed.
The cartridges of the oldest backup copy are to be either
reused or scratched. See the preceding message for the error
condition.
System Action: This command terminates with an error
message.
Programmer Response: Correct the problem as indicated in
the preceding message and rerun the command.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 30,
35a, and 35c.
IDC37021 TARGET COpy yyddd CANNOT BE USED
Explanation: The command selected the cartridges of an
existing copy volume created on the date indicated by yyddd
for reuse but the cartridges cannot be used. The following
message explains why the designated copy volume cannot be
used.
System Action: The command terminates with an error
message.
Programmer Response: Before rerunning the COPYV command,
either:
• Run the SCRATCHV command to scratch the remaining
cartridge of this unusable copy and delete the record from
the Inventory data set.
• Run the REMOVER command to delete the copy volume
record from the Inventory data set if both cartridges are
lost.
• Reenter the missing cartridges in the Mass Storage Facility
(MSF) while the Mass Storage Volume Control (MSVC) is
enabled.
IDC37061
U
COpy TO CARTRIDGES csn 1 csn2 IS
INCOMPLETE
Explanation: The copy operation to the copy volume failed.
The copy volume is marked incomplete in the Inventory data
set and will be reused by the COPYV command when the
command is run again. The cartridges of the copy volume are
indicated by the cartridge serial numbers (csn1 and csn2) and
were selected either by the user, by the Mass Storage Control
(MSC) at random, or by the command using an existing copy
volume. See the preceding message for further explanation of
the error.
Programmer Response: Before rerunning the COPYV command
correct the problem as indicated in the preceding message.
Rerun COPYV to complete' the copy operation to the
incomplete copy volume (COPYV will reuse the cartridges of
the incomplete copy volume for the new copy) or run
SCRATCHV to scratch the incomplete copy volume before
rerunning the COPYV command.
If COPYV terminates without indicating the status of the copy
operations, LlSTMSVI can be run the determine whether the
volurrie is flagged for recovery purposes. If the incomplete
copy flag is set in the copy volume record, LlSTMSVI not only
lists the standard information for the volume but also
highlights the volume report with a note that a copy operation
failed for the preceding copy volume.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, 30,
35a, and 35c.
IDC37081
U
COPY VOLUME COULD NOT BE CREATED
Explanation: No existing copy volumes were eligible for reuse
for this copy request. An attempt to create a new target
volume from scratch cartridges failed. A new copy volume was
not created. See the precedingJnessage for further explanation
of the problem.
System Action: The command terminates with an error
message.
Programmer Response: Correct the error condition as
indicated in the preceding message and rerun the command.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a and
35c.
IDC37091
** COpy TO CARTRIDGES csn1 csn2 NOT
PERFORMED
Explanation: The Mass Storage Controller (MSC) could not
perform the copy operation to the copy volume. The cartridges
of the copy volume are specified by (csn1 and csn2). The
copy volume remains usable because the original data on the
volume was not destaged. See the preceding message for
further explanation of the error.
System Action: The command terminates with an error
message.
Programmer Response: Correct the error as indicated in the
preceding message and rerun the command.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 30,
35a, and 35c.
IDC37101
U NO BACKUP COPY VOLUMES EXIST FOR
VOLUME volser
Explanation: The designated volume (volser) has no backup
copy. The option to restore from the latest backup cannot be
satisfied. See thepreceding message for further explanation of
the problem.
System Action: The command terminates with an error
message.
Programmer Response: Rerun the command requesting a
specific nonbackup copy volume if any exist.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC37121
U
LATEST BACKUP COpy RECORD CANNOT BE
RETRIEVED FROM INVENTORY
Explanation: The recovery operation requires the latest backup
copy, but the record for that copy volume could not be
retrieved from the Inventory data set. See the preceding
message for further explanation of the error.
System Action: The command terminates with an error
message.
Programmer Response: Before rerunning the command correct
the error as indicated in the preceding message or specify
another copy to be used in the recovery. operation.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC37211 VOLUME volser IS ALREADY ACTIVE
Explanation: The designated volume "volser" is already active.
System Action: The command terminates with a message.
Programmer Response: None.
IDC37291 NEW SERIAL NO. REQUIRED TO ACTIVATE A COpy
.
OR DUPLICATE VOLUME
Explanation: A copy or duplicate volume cannot be activated
unless the volume is relabeled with a unique volume serial
number.
System Action: The command terminates with a message.
Section 4: IDC Messages - Access Method Services
4-59
I
Programmer Response: Rerun the command specifying the
NEWSERIAL parameter and a unique volume serial number that
can be used to relabel the copy or duplicate volume in order
to activate it.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC37301 VOLUME volser CANNOT BE RELABELED; COPIES
EXIST
Explanation: The volume serial number of the volume (volser)
cannot be changed because copies of the volume exist.
System Action: The command terminates with an error
message.
Programmer Response: Rerun the command to store the
volume, but do not request the volume serial number be
changed. If the volume must be renamed, run the SCRATCHY
command to scratch all copies before requesting STOREY to
rename and store the volume.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC37321
**
VOLUME volser COULD NOT BE MADE INACTIVE
Explanation: The status of the volume (volser) could not be
changed from active to inactive. See the preceding message
for further explanation of the error.
System Action: Processing continues.
Programmer Response: Correct the error as identified in the
preceding message.
Rerun STOREY or run MODIFYV to either backout or retry the
rename operation.
If the STOREY or MODIFYV commands are run to recover from
a rename failure, the DO statement for the volume is required
and must specify deferred mounting.
The values specified for the VOLUME and NEWSERIAL
parameters depend upon how the volume record is recorded in
the Inventory data set. If the cartridge labels have been
updated, the volume record .will be identified by the new
volume serial number. For the VOLUME parameter, specify the
volume serial number as recorded in the cartridge labels and
the volume record. For the NEWSERIAL parameter, specify the
desired volume serial number. Note that the security check for
nonVSAM status and password protected data sets is bypassed
only if the NEWSERIAL parameter specifies the same volume
serial number as recorded in the Inventory data set for the
volume label. This allows the original volume serial number of
a VSAM volume to be restored if the volume is left partially
renamed.
If STOREY terminates without' indicating the status of the
rename operation, LlSTMSVI can be run to determine whether
the volume is flagged for recovery purposes. If the mismatch
flag is set in the volume record, LlSTMSVI not only lists the
standard information for the volume but also highlights the
volume report with a note that a rename operation failed for
the preceding volume and that serial number 'nnnnnn' is
recorded in the volume label of the volume.
IDC37341
** VOLUME LABEL COULD NOT BE RESTORED TO
ORIGINAL STATUS
Explanation: Following a failure to deactivate the volume and
change the volume serial number in the cartridge labels, an
attempt to restore the volume label to its original status also
failed. A volume serial-mismatch exists between the volume
label and the cartridge labels of the cartridges assigned to the
Mass Storage Volume. A flag indicating the mismatch is set in
the Inventory data set for the volume. See the preceding
message for further explanation of the problem.
4-60
VS2 System Messages (VS2 Release 3.7)
System Action: The command terminates with an error
message.
Programmer Response: Correct the error as identified in the
preceding message.
• If a Rename Operation Failed for ADDV
Run ADDV to backout or retry the rename operation if the
volume is inactive. If the volume is active, run MODIFYV or
STOREY to either backout or retry the rename operation.
If the ADDV, MODIFYV, or STOREY commands are run to
recover from a rename failure, a DO statement for the
volume is required and must specify deferred mounting.
The values specified for the VOLUME and NEWSERIAL
parameters depend upon how the volume record is recorded
in the Inventory data set. If the cartridge labels have been
updated, the volume record will be identified by the new
volume serial number. For the VOLUME parameter, specify
the volume serial number as recorded in the cartridge labels
and the volume record. For the NEWSERIAL parameter,
specify the desired volume serial number. Note that the
security check for nonVSAM status and password protected
data sets is bypassed only if the NEWSERIAL parameter
specifies the same volume serial number as recorded in the
Inventory data set for the volume label. This allows the
original volume serial number of a VSAM volume to be
restored if the volume is left partially renamed.
If ADDV, MODIFYV, or STOREY terminates without indicating
the status of the rename operation, LlSTMSVI can be run to
determine whether the volume is flagged for recovery
purposes. If the mismatch flag is set in the volume record,
LlSTMSVI not only lists the standard information for the
volume but also highlights the volume report with a note
that a rename operation failed for the preceding volume and
that serial number 'nnnnnn' is recorded in the volume label
of the volume.
• If a Rename Operation Failed for MODIFYV
To recover from a MODIFYV rename failure 1) run ADDV to
activate the volume if the volume is merely inactive and has
no volume serial mismatch condition, or 2) run ADDV to
both activate the volume and complete the rename
operation if the volume is both inactive and has a volume
serial mismatch condition, or 3) rerun MODIFYV to complete
or retry the rename operation if the volume is active but
has a mismatch condition, or 4) run STOREY to complete or
retry the rename operation if the volume is active and if a
duplicate volume serial number is desired as result of the
rename.
For the DO statement requirements, the proper VOLUME
and NEWSERIAL parameter values, and use of LlSTMSVI,
refer to the description above for an ADDV rename failure.
• If a Renam~ Operation Failed for STOREY
Rerun STOREY or run MODIFYV to either backout or retry
the rename operation.
For the DO statement requirements, the proper VOLUME
and NEWSERIAL parameter values, and use of LlSTMSVI,
refer to the description above for an ADDV rename failure.
Problem Determination: Table I, items 1, 2, 3, 4, 13, 29, 35a,
and 35c.
IDC37381
** DATA SETS NOT RECATALOGED IN VSAM
CATALOG
An error occurred which prevented all the data
sets in the VSAM owning catalog from being recataloged. A
preceding message explains the error.
System Action: The command terminates normally. If the
target volume is a 3336 Model 1 Disk Pack, use IEHDASDR to
reformat the volume to meet the empty VTOC requirement of
the CONVERTV command.
Explanation:
Programmer Response: Correct the error and rerun the
command.
Problem Determination: Table I, items 3, 4, .13, 26b, 29, and
31.
IDC37391
FROM AND TO UNITS ARE THE SAME DEVICE TYPE
Explanation: The device type specified in the UNIT parameter
of the FROMFILE DO statement is the same as the device type
specified in the UNIT parameter of the TOFllE DO statement.
System Action: The command terminates normally with an
error message.
Programmer Response: Either correct the UNIT parameter and
rerun the command or if you want to move data between two
volumes of the same type, use the IEHMOVE utility program.
Problem Determination: Table I, items 1, 3, 4, 13, and 29.
IDC37401
MULTIPLE VOLUME SERIAL NUMBERS ASSOCIATED
WITH FILE ddname
Explanation: CONVERTV will only convert a single volume at a
time. The "ddname" has more than one volume associated
with it.
System Action: The command terminates normally.
Programmer Response: Specify only one volume serial on the
DO statement or supply a FROMVOLUME statement for the
volume to be converted. Rerun the command.
Problem Determination: Table I, items 1, 3, 4, 13, and 29.
IDC37411
RECATALOG OPTION INVALID FOR VSAM VOLUME
Explanation: The source volume is owned by a VSAM catalog
and the volume and any VSAM data sets on the volume must
be recataloged. Therefore, NONE is an invalid option.
System Action: The command terminates normally.
Programmer Response: Specify the VSAMCATALOG option on
the RECATALOG parameter or omit the control statement.
Rerun the command.
Problem Determination: Table I, items 3, 4, 13, 25b, and 29.
IDC37441
JOBCAT /STEPCAT MUST NOT BE SPECIFIED FOR
VSAM CATALOG ON VOLUME
Explanation: A JOBCAT or STEPCAT DO statement was used
to allocate the VSAM user catalog on the volume to be
processed. If the VSAM user catalog is on the volume being
processed, the user catalog must not be open as a result of
the use of a JOBCAT or STEPCAT DO statement:
System Action: The command terminates normally.
Programmer Response: Use a standard DO statement ddname
rather than JOBCAT or STEPCAT to allocate the VSAM user
catalog, and supply that ddname in the CATALOG parameter.
Rerun the command. In VS2 you can omit the DO statement
and only specify the name of the catalog on the CATALOG
parameter.
Problem Determination: Table I, items 1, 3, 4, 13, 25b, and
29.
IDC37451
DO NAME MUST BE SPECIFIED FOR VSAM USER
CATALOG ON VOLUME
Explanation: No ddname was specified for the VSAM
CATALOG residing on the volume being processed preventing
the catalog from being opened.
System Action: Command terminates normally.
Programmer Response: Supply a DO statement for the catalog
that owns the volume. The. DO statement name cannot be
JOBCAT or STEPCAT. Specify the name of the DO statement
which allocates the catalog in the CATALOG parameter. Rerun
the command.
Problem Determination: Table I, items 3, 4, 13, 25b, and 29.
IDC3770IVOLUME volser ACTIVE
Explanation: The volume specified by "volser" is active and.
cannot be ejected.
System Action: The command terminates with an error
message.
Programmer Response: Run the STOREY command to both
deactivate and eject the volume.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC38201
** TABLES COULD NOT BE COPIED TO WORK
DATA SET
Explanation: An error code was returned from the request to
copy the MSC tables to the work data set. A preceding
message explains the reason.
System Action: The command preceding terminates normally.
Programmer Response: Check the preceding message. to
determine the exact errror. Correct the error and rerun the
command.
Problem Determination: Table I, items 3, 4, 13, and 29.
IDC38221
MSF NOT AVAILABLE
Explanation: The Mass Storage Facility (MSF) does not have a
staging adaptor assigned to it in the Mass Storage Control
(MSC) tables and cannot be considered to exist for system
use.
System Action: The command terminates normally.
Programmer Response: Specify a valid MSF on the command
and rerun the command.
Problem Determination: Table I, items 3, 4, .13, and 29.
IDC38421
ORDER OF TRACE AREAS COULD NOT BE
DETERMINED - NO DATA DUMPED
Explanation: An attempt was .made to dump both trace areas,
but the first trace area could not be determined. Therefore, no
trace data was dumped. The programmer will have to submit
individual X and/or Y trace dump requests.
System Action: The commandlerminates normally.
Programmer Re~onse: Rerun the TRACE command specifying
either trace area X or trace area Y.
Problem Determination: Table I, items 2, 3,.4, 13, 29, and 30.
IDC38441
BLOCKSIZE OF OUT DATA SET IS NOT A MULTIPLE
OF 264.
Explanation: Because trace records are 264 bytes long, they
must be blocked in multiplies of 264. That is, the blocksize
specified for the Output Data set must be a multiple of 264.
System Action: The Trace Utility is terminated.
Programmer Response: Correct the blocksize specification in
the JCL and rerun the job.
Problem Determination: Table I, items 3, 4, and 29.
IDC38501
THE NUMBER OF SECONDS IN THE LRU CLOCK IS
INVALID
Explanation: The number of seconds in the LRU clock
(LRUCLOCK parameter) is invalid. The only valid numbers are
128,256, 512, 1024, 2048, 4096, 8192, and 16384.
System Action: The command terminates normally. No tuning
parameters have been changed.
Programmer Response: Correct the LRUCLOCK parameter and
rerun the command.
IDC38511
LOWER VALUE MUST BE LESS THAN HIGHER VALUE
FOR ACTIVEPAGES
Explanation: On the ACTIVEPAGES parameter, the lower
Section 4: IDC Messages - Access Method Services
4-61
number of pages is a number greater than or equal to the
higher number of pages. The lower number must be less than
the higher number.
System Action: The command terminates normally. No tuning
parameters have been changed.
Programmer Response: Correct the ACTIVEPAGES parameter
and rerun the command.
IDC38521 TOTAL OF UNITS IN LRUGROUPS MUST BE LESS
THAN OR EQUAL TO 16
Explanation: When the LRU clock units for all groups are
added together they exceed the maximum (16).
System Action: The command terminates normally. No tuning
parameters have been changed.
Programmer Response: Correct the LRUGROUPS parameter
(which specifies the number of LRU clock units) and rerun the
command.
IDC38601
GROUP PARAMETERS CANNOT BE SPECIFIED FOR
NON GROUPED VOLUMES
Explanation: A request to set group level attributes for a
volume that does not belong to a group is invalid.
System Action: The command terminates with an error
message.
Programmer Response: Rerun the command after removing the
conflicting parameters that specify group attributes.
Problem Determination: Table I, items 2, 3, 4, 13, 29, 35a,
and 35c.
IDC38831
** ERROR COUNT EXCEEDED UPPER LIMIT,
FUCNTION TERMINATED
Explanation: A LlSTCRA command encountered more than 50
I/O errors.
System Action: Processing of the LlSTCRA command is
terminated.
Programmer Response: See orevious messages to determine
the cause of the I/O errors. Correct the problem, and rerun
the job.
"
IDC38851 VOLUME ser PERMANENTLY RESIDENT OR
RESERVED
Explanation: Volume ser is marked permanently resident or
reserved in the unit control block (UCB). Therefore, this
volume cannot be demounted. The volume described by the
volume serial (ser) needs to be demounted so that a MSC
fucntion can be performed or to enable the proper volume to
be mounted on the unit.
System Action: Processing of the command is terminated.
Programmer Response: Ensure that the correct volume serial
number was specified on the DD statement for the FILE
parameter. If the correct volume serial was specified, you
cannot run the command w'hile that volume is permanently
resident or reserved.
Problem Determination: Table I, items 1, 2, 3, 4, 13, and 29.
IDC39001
PUTGET ERROR CODE IS re
Explanation: The PUTGET macro instruction failed. The reason
for the error is indicated by rc.
Return
Code Meaning
8
The PUTGET service routine did not complete. An
attention interrupt occurred during the execution of
'PUTGET, and the attention handler turned on the
completion bit in the communications ECB.
12 No prompting was allowed on a PROMPT request. Either
the user at the terminal requested no prompting with
4-62VS2 System Messages
(VS2 Release 3.7)
the PROFILE command, or the current source of input is
an in-storage list.
12 A line could not be obtained after a MODE request. A
chain of second level informational messages exists,
and the current stack element is non-terminal, but the
terminal user did not request PAUSE processing with
the PROFILE command. The messages are therefore not
available to him.
16 The NOWAIT option was specified for TPUT and no line
was put out or received.
20 The NOWAIT option was specified for TGET and no line
was received.
24 Invalid parameters were supplied to the PUTGET service
routirie.
28 A conditional GETMAIN was issued by PUTGET for
output buffers and there was not sufficient space to
satisfy the request.
32 The terminal has been disconnected.
System Action: The command is terminated.
Programmer Response: Correct the error based on the return
code information and rerun the job.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IDC39011
ERROR QUALIFYING dsn
Explanation: The TSO default service routine failed to qualify
the data set indicated.
System Action: The request is terminated.
Programmer Response: An associated message, IDC39021
directs the user in how to correct this error.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IDC39021
** DEFAULT SERVICE ROUTINE ERROR CODE re,
LOCATE ERROR CODE cde
Explanation: This message contains the return code
information required to correct the error indicated in
associated message IDC3901l. The LOCATE error code, cde, is
part of VSAM Catalog Management. Refer to message
IDC30091 for the return codes as well as the possible system
and programmer responses. The possible system and
programmer responses for the default service routine error
conditions along with the return code, rc, are as follows:
Return
Code Explanation
(rc)
4
Return code from PUTLINE or PUTGET was not zero.
Data set name was longer than 44 bytes.
12 An I/O error occurred while searching the catalog, the
catalog data set was not available or the data set name
was not specified correctly.
16 The index structure of the catalog was not consistent
with the data set name. For example, the name
specified was "A.B.C", but there is a data set called
"A.B," so there cannot be one called "A.B.C."
20 The data set name could not be found in the catalog.
24 An attention interruption occurred during processing of
this request.
28 Invalid parameters were specified.
32 It was necessary to prompt the user, but the caller
specified tha~ the user should not be interrupted.
36 Not enough qualifiers were specified for the data set
name. For example, the name specified was "A.B," but
the catalog contains an entry for "A.B.C."
System Action: Processing continues.
Programmer Response: The response depends on the return
codes, rc and cde. Possible responses for return code rc
follow:
8
Return
/
V82.03.807
Code
(rc)
4
8
12
Response
16
Respecify the data set name or rec,atalog the data set.
Respecify the data set name or recatalog the data set.
24 None.
28 Check to be sure the parameter list for IKJEHDEF was
not improperly modified.
32 None.
36 Respecify the data set name.
Problem Determination: Table I, items .1, 2, 3, 4, 29.
20
Make sure the user is still logged on to the system.
Correct the data set name.
Examine the data set name for syntax errors, for
example, embedded punctuation marks. Check the
CVOL index structures to be sure CVOLs are properly
linked. If an I/O error occurred, it may be necessary to
rebuild the catalog.
Section 4: IDC Message.
~
Acce•• Method Service.
4-63
VS2.03.807
4·64
VS2 System Messages (VS2.03.807)
IDC42271
AN 'ELSE' COMMAND APPEARS IMPROPERLY
Explanation: An ELSE modal command appears without a
matching IF-THEN modal command. Modal command
continuation may be incorrect.
System Action: The remainder of the command input stream is
ignored.
Programmer Response: Correct the usage and rerun.
Problem Determination: Table I, items 4, 29.
Section 4: IDC Messages - Access Method Services
4-65
VS2.03.808
IDC42281
24
AN 'END' COMMAND IS INVALID
Explanation: An END modal command occurs without a
matching DO modal command.
System Action: The rerllalnder of the command input stream is
ignored.
Programmer Response: Correct the DO-END usage and rerun.
Problem Determination: Table I, items 4, 29.
IDC42291
'If' COMMAND HAS INVALID RELATIONAL
EXPRESSION
Explanation: An IF modal command has an invalid relational
expression.
System Action: The remainder of the command input stream is
ignored.
Programmer Response: Check the syntax and semantic
requirements of the IF command. Correct the usage and rerun.
Problem Determination: Table I, items 4, 29.
IDC42301
'SET' COMMAND HAS INVALID ASSIGNMENT
EXPRESSION
Explanation: A SET modal command has an invalid assignment
expression.
System Action: The remainder of the command input stream is
ignored.
Programmer Response: Check the syntax and semantic
restrictions on the SET command. Correct the usage and rerun.
Problem Determination: Table I, items 4, 29.
IDC42321
IMPROPER OR MISSING 'THEN' KEYWORD
Explanation: The THEN portion of the IF modal command is
misspelled or missing. Modal command continuation may be
incorrect.
System Action: The remainder of the input stream is ignored.
Programmer Response: Correct the usage and rerun.
Problem Determination: Table I, items 4, 29.
IDC42361
INPUT STREAM END-Of-fiLE fOUND BEfORE
END-Of -COMMAND
Explanation: Command input stream end-of-file has been
found while scanning a command. There may be input records
missing.
System Action: The current command is not processed.
Programmer Response: Add the missing data and rerun.
Problem Determination: Table I, items 4, 29.
IDC42371 TOO MANY LEVELS Of 'If' COMMAND NESTING
Explanation: IF modal commands have been nested to a level
that cannot be handled.
System Action: The remainder of the .command input stream is
ignored.
Programmer Response: Restructure the modal commands to
conform to the restriction of ten levels of nesting.
Problem Determination: Table I, items 4, 29.
IDC49991
UABORT CODE rc
Explanation: This message indicates a termination error, which
caused the processor to abort. The code number (rc) indicates
the nature of the error. Since the error is usually such that no
further processor code may be executed with confidence, this
message appears in the output listing by a
write-to-programmer action.
Return
Code Meaning
20
4-66
Reserved.
VS2 System Messages (VS2.03.808)
I
Text processor's print control table address not set in
GOT.
28 No virtual storage available for one of the following:
• Text processor's translate table.
.Initialization of the I/O adapter.
.Automatic (dynamic) storage of a module.
• Text processor dynamic storage.
See the in-virtual storage trace tables to determine
which is the correct condition.
32 There was a request to access an unopened data set.
36 The processor was unable to open SYSPRINT (or
whichever DO name is employed to denote the
processor's standard listing output data set).
40 Invalid U-macro argument list found.
44 The processor is unable to produce a dump.
52 Reserved.
56 BLDL failed to find a required Access Method Services
module.
Problem Determination: Table I, items 1, 3, 4, 29.
IDCOI0021 RESETCAT CATALOG catname
VOL yolser LEVEL timestamp
Explanation: This message is informational, indicating the
catalog to be reset and the timestamp on the volume.
System Action: Processing continues.
Programmer Response: None.
IDCOIOlll CRA CHOSEN fOR RESET - VOL yolser LEVEL
timestamp
Explanation: This message is informational, indicating the CRA
to be reset and the timestamp on the volume.
System Action: Processing continues.
Programmer Response: None.
IDCOI0371 catname HAS BEEN RESET
Explanation: This message is informational, indicating that
RESETCAT processing has been completed for the indicated
catalog.
System Action: Processing continues.
Programmer Response: None.
IDCOl1201lNCONSISTENT field
Explanation: The fields identified by field do not match in table
entries that are otherwise matching. Two secondary messages
'
identify the specific field or attribute values that are
inconsistent, and the respective tables and table indices in
which the inconsistencies occur. See IBM 3850 Mass Storage
System (MSS) Principles of Operation for locations and
descriptions of the fields in the Mass Storage Control and
Staging Adapter tables. See OS/VS2 Mass Storage System
Communicator (MSSC Logic for locations and descriptions of
fields in the Inventory data set.
-?
System Action: Processing continues.
Programmer Response: Investigate the inconsistency. You can
run the Mass Storage System Access Method Services
DUMPMSS, LlSTMSF, or LlSTMSVI commands to obtain dumps
of the table with the inconsistency. If there is any doubt
whether the inconsistency is temporary or not, rerun the
CHECKMSS command.
Problem Determination: Table I, items 13, 29, and 30.
IDC01l211 DUPLICATE field REfERENCE fOUND
Explanation: More than one table entry references the same
field or attribute (identified by field). All entries should be
unique with respect to that field or attribute. Two secondary
messages identify the specific field or attribute values that are
identical, and the table(s) and table indices in which the
duplicate occurs, See' IBM 3850 Mass Storage System (MSS)
Principles of Operation for locations and descriptions of the
fields in the Mass Storage Control and Staging Adapter tables.
See OS/VS2 Mass Storage System Communicator (MSSC) Logic
for locations and descriptions of fields in the Inventory data
set.
System Action: Processing continues.
Programmer Response! Investigate the duplicate. You can run
the Mass Storage System Access Method Services DUMPMSS,
LlSTMSF, or LlSTMSVI commands to obtain dumps of the table
containing the duplicate information. If there is any doubt
whether the duplicate is temporary or not, rerun the
CHECKMSS command.
Problem Determination: Table I, items 13, 29, and 30.
IDC01l221 SUM = n OF INDIVIDUAL counts FROM table NOT
EQUAL TO TOTAL VALUE
Explanation: The sum n of the individual counts or values
counts obtained from table does not match the field that
should contain the total of the counts or values. A secondary
message identifies the total value, and the table and table
Section 4: IDC Messages - Access Method Services
4-66.1
4-66.2
VS2 System Messages (VS2.03.S0S)
VS2.03.808
indices to locate the entry containing the total. See IBM 3850
Mass Storage System (MSS) Principles of Operation for
locations and descriptions of the fields in the Mass Storage
Control and Staging Adapter tables. See OS /VS2 Mass Storage
System Communicator (MSSC) Logic for locations and
descriptions of fields in the Inventory data set.
System Action: Processing continues.
Programmer Response: Investigate the inconsistency. You can
run the Mass Storage System Access Method Services
DUMPMSS, LlSTMSF, or LlSTMSVI commands to obtain dumps
of the table with the inconsistency. If there is any doubt
whether the inconsistency is temporary or not, rerun the
CHECKMSS command.
Problem Determination: Table I, items 13, 29, and 30
IDC011231
U
VALUE = value table (index)
Explanation: This secondary message identifies the value of
the field or attribute named in a primary message, the table
name table containing the field or attribute, and the table
indices (index) that identify the particular table entry
containing the field or attribute. See IBM 3850 Mass Storage
System (MSS) Principles of Operation for locations and
descriptions of the fields in the Mass Storage Control and
Staging Adapter tables. See OS/VS2 Mass Storage System
Communicator (MSSC) Logic for locations and descriptions of
fields In the Inventory data set.
System Action: Processing continues.
Programmer Response: Follow the Programmer Response for
the primary message.
Problem Determination: Table I, items 13, 29, and 30.
IDC011241 MATCHING field = value NOT FOUND IN table1 TO
MATCH table2 (index)
Explanation: An entry in table2 should have a matching entry
in tablel. No such match was found, or the table2 entry was
invalid. field = value identifies the field or attribute and its
value for which a matching entry was not found or not valid.
The table indices (index) to locate the unmatched tablel entry
are also listed. See IBM 3850 Mass Storage System (MSS)
Principles of Operation for locations and descriptions of the
fields in the Mass Storage Control and Staging Adapter tables.
See OS/VS2 Mass Storage System Communicator (MSSC) Logic
for locations and descriptions of fields in the Inventory data
set.
System Action: Processing continues.
Programmer Response: Investigate the inconsistency. You can
run the Mass Storage System Access Method Services
DUMPMSS, LlSTMSF, or LlSTMSVI commands to obtain dumps
of the tables with the inconsistency. If there is any doubt
whether the inconsistency is temporary or not, rerun the
CHECKMSS command.
Problem Determination: Table I, items 13, 29, and 30.
IDC011461 NO DISCREPANCIES FOUND, REPORT NOT PRINTED
Explanation: No report was printed by the AUDITMSS
command with the CHECK or READLEBEL parameter. No
discrepancies were found.
System Action: The command terminates normally.
Programmer Response: None.
IDC011901 CARTRIDGE csn IS NOW A SCRATCH CARTRIDGE
Explanation: The cartridge with the cartridge serial number csn
is now a scratch cartridge.
System Action: Processing continues.
Programmer Response: None.
IDC110031 CONTROL INTERVAL nnnnnn BYPASSED IN CRA
volser
Explanation: IGNORE was specified and an I/O error was
encountered. The record is ignored. This message is preceded
by IDC33S11 which indicates the nature of the error. nnnnnn is
the control interval number of the record in the catalog.
System Action: Processing continues.
Programmer Response: This may cause errors to be detected
in objects on the volume specified, or objects on the volume
may be totally lost without notification. Perform a LlSTCAT
operation of the catalog to determine which objects still exist
after the reset operation.
Problem Determination: Table I, items 3, 4, 13, 14, 34.
IDCII0151 CONTROL INTERVAL nnnnnn BYPASSED IN
CATALOG
Explanation: IGNORE was specified and an I/O error was
encountered. The record is ignored. Message IDC33511
precedes this message indicating the specific error.
System Action: Processing continues.
Programmer Response: The record noted in the catalog is
inaccessible. If it contained a corresponding reset CRA entry,
the entry will be recovered. If it contained a non-reset CRA
entry, the entry remains inaccessible. A LlSTCAT may reveal
whether the error is of any consequence. nnnnnn is the control
interval number of the record in the catalog.
Problem Determination: Table I, items 3, 4, 13, 14, 34.
IDCI10221 entryname, type
CONTAINS A CONNECTOR TO INVALID RECORD
nnnnnn, type
Explanation: An object contains a dependency on a record
that does not exist. The base record is noted by name and
type. The dependent record which is invalid is noted by its
expected control interval number and record type. The
reference to the invalid record is deleted. See either message
IDC210241, IDC210251 or IDC210261 which follows. The
message will note the other action taken as a result of this
error. nnnnn is the control interval number of the record in the
catalog; type is the entry type of the record.
System Action: Processing continues.
Programmer Response: See the following message (noted in
the explanation) to determine what action was taken.
IDCII0231 entryname, type
ERROR FOR ASSOCIATION [nnnnnn,] type
Explanation: An entry is chained to a record of a type
different than anticipated, or the object noted consists of
incomplete set of records. If the control interval number of the
expected association is not given, then no association for that
object exists in the base record; an association for that type is
required for the entryname noted. Message IDC210261 follows,
noting that the entry has been deleted. nnnnnn is the control
interval number of the record in the catalog; type is the entry
type of the record.
System Action: Processing continues.
Programmer Response: See message IDC210261.
IDCII0291 SPACE MAP FOR VOLUME volser CORRECTED
Explanation: The suballocted VSAM data space has been
corrected to reflect what is on the volume. This correction
occurs if entries are deleted by RESETCAT, or space stated as
suballocated is not suballocated (that is, the space map is
incorrect on entry to RESETCAT).
System Action: Processing continues.
Section 4: IDC Messages - Access Method Services
4-67
VS2.03.808
Programmer Response: This message is given for information
only. It is a correction of some state of error. The error may
be specifically noted in a preceding error message or not at
all. In the latter case, the situation is due to space being
suballocated from available suballocateable space; however, no
entry can be found which claims this space. No corrective
action by the programmer is required.
IDCII0311 UNIQUE DATA SET entryname
HAS FEWER EXTENTS THAN THE DATA SPACE
Explanation: The unique data or index component has less
space described than the data space. No problem exists for
this data set; this message is given to inform you that space
exists which is not in use. If the data set is extended, this
space will be used. No corrective action is taken.
System Action: Processing continues.
Programmer Response: None.
IDCII0331 dsname, volser
NOT DELETED
Explanation: A unique data set, on a volume not being reset,
has no corresponding DATA or INDEX component. The
component was defined on one of the volumes being reset, but
not longer exists on that volume.
System Action: Processing continues.
Programmer Response: If the data set is no longer valid, then
SCRATCH it.
IDCII0361 entryname, type
OUT -OF-SYNC ON volser
Explanation: The data set named may have invalid space
information. The extents occupied by the named data set are
not in conflict with any other VSAM data set or with the
system; however, a self-checking field failed to check. The
data set itself may be all right.
System Action: Processing continues.
Programmer Response: List the data set and ensure that it is
correct and accessible.
IDCII0401 dsname UNKNOWN
Explnation: The VSAM Format 1 OSCB did not have a
corresponding space header in the volume record. Hence, the
catalog does not account for the space allocated to the data
set. The data set noted above was scratched.
System Action: Processing continues.
Programmer Response: If an I/O error occurred when reading
from the CRA for this volume, this condition may arise. It may
also be caused by some previous system error. This message
is given for informational purposes. A later message may
indicate whether objects were marked unusable, perhaps as a
result of this condition. Watch for message IOC210271 or
IOC210301.
IDCll0411 dsname SPACE CORRECTED
Explanation: The extents in the space header for the data
space noted were not identical to the extents in the
corresponding Format 1 OSCB. The extents in the space
header were corrected using the extents in the Format 1 OSCB
and the Format 3 OSCB if one exists.
System Action: Processing continues.
Progrs71mer Response: This may be caused by some previous
system drror. This message is given for information purposes.
A later message may indicate whether objects were marked
unusable, perhaps as a result of this condition if fewer extents
existed in the data set than the data space. Watch for
message IOC210271 or IOC210301.
4-67.0
VS2 System Messages (VS2.03.808)
IDCII0421 dsname SPACE DELETED
Explanation: The space header for the data space referred to
a nonexistent Format 1 OSCB. The space header for the data
space was deleted.
System Action: Processing continues.
Programmer Response: This may be caused by some previous
system error. This message is given for information purposes.
A later message may indicate whether objects were marked
unusable, perhaps as a result of this conditon. Watch for
mesage IOC210371 or IOC210201.
IDCI10431 TIMESTAMP FOR VOLUME RECORD ON VOL volser
WAS CORRECTED
Explanation: The timestamp for the volume record did not
match the timestamp in the VTOC. This may have resulted
from a failure in Catalog Management after updating one and
not the other. The timestamps are synchronized.
System Action: Processing continues.
Programmer Response: None.
IDCII0441 dsname NOT SCRATCHED
Explanation: The attempt to scratch the data set for the
reason stated in preceding message IOCII0401 failed.
System Action: Processing continues.
Programmer Response: See IOCII0401.
IDC210091 entryname, type
DOES NOT EXIST ON VOLUME volser
Explanation: A multivolume data set existed on a volume prior
to reset. The data set is not on the volume and will be marked
unusable.
System Action: Processing continues.
Programmer Response: The data set on valid volumes may be
removed via EXPORT or REPRO prior to deleting the data set.
The data set is unopenable for output.
IDC210201 UNABLE TO ALLOCATE volser
Explanation: An attempt to allocate a volume for RESETCAT
failed. See message IOC39051.
System Action: Processing continues.
Programmer Response: Make the volume indicated available to
RESETCAT via CRAFILES and reissue the command.
IDC210241 entryname, type
CONTAINS AN INVALID ALIAS CHAIN
Explanation: The alias chain for a USERCATALOG or
NONVSAM entry is invalid.
System Action: Processing continues.
Programmer RESPONSE: The alias chain will be corrected. A
LlSTCAT should be run to determine which aliases may be lost.
Problem Determination: Table I, items 3, 4, 13, 14, 34.
IDC210251 entryname, type
HAS AN INVALID GDG DATA SET ASSOCIATION
Explanation: The records associating the GOG data set with
the GOG base are in error. The GOG base has been recovered;
however, the generation data set string associated with this
base has been altered to reflect only those data set
descriptions which can be located.
System Action: Processing continues.
Programmer Response: Perform a LlSTCAT for the GOG base
and determine which entries no longer exist. Though entries do
not exist, RESETCAT has not altered/scratched the data sets.
If the resulting GOG data set string is in error, delete the GOG
and redefine it; then catalog the correct generations by name.
VS2.03.808
IDC210261 entry,type
DELETED
Explanation: A previous message indicates an error which
resulted in this entry being deleted from the catalog.
System Action: Processing continues.
Programmer Response: The entry noted was deleted. Any
space that it occupied has been returned for suballocation if it
was a VSAM object. If the entry is desired, it must be
redefined and loaded. Note that any objects dependent on this
object are also deleted, but no message is given for them. For
instance, if a cluster is deleted, all paths, alternate indexes,
and the upgrade set are also deleted.
IDC210271 (CRA I CATALOG) SPACE ON VOLUME volser NOT
OWNED BY CATALOG
Explanation: The CRA extents. or catalog extents have no
matching extents in any data space.
System Action: Processing continues.
Programmer Response: The resultant catalog is vulnerable
because there are conflicting space ownership requests
between the VTOC and the catalog. After the RESETCAT, use
EXPORT to transfer all data sets on the volume noted and
remove VSAM ownership to the volume. Check the data sets
to ensure that they contain reasonable data. Then add
ownership to the volume, and then use import to reestablish
the data sets.
IDC210301 entryname,type
HAS INVALID SPACE DESCRIPTION FOR volser
/
Explanation: The entry noted claims space on volume. That
space is not allocated to that entry.
System Action: Processing continues.
Programmer Response The data set is marked unusable and
the volume description invalidated. L1STCAT may be run to
determine the invalid extents. Delete the data set. Redefine it
and reload it.
Problem Determination: Table I, items 3, 4, 13, 14, 34.
IDC210321 type DELETED FROM
entryname, type
Explanation: An object of the type specified was defined over
the entry named as entryname. However, the records
describing the object could not be found. Therefore, an object
of the type specified was deleted from the given entryname's
description. No name for the deleted object is given because
the record with its name cannot be found.
System' Action: Processing continues.
Programmer Response: Perform a L1STCAT for the entryname
noted, and try to determine which entity was deleted and
redefine it.
IDC210341 SPACE MAP ERROR FOR volser
Explanation: The space map, which indicates which space is
available for suballocation on a volume, is not the correct
length in the catalog. This may be due to a damaged catalog
or CRA. This situation is not correctable by RESETCAT.
System Action: Processing continues.
Programmer Response: All data sets on the volume noted may
be EXPORTed, the volume and all VSAM space should be
deleted. Redefine the volume in the catalog and IMPORT the
data sets. The error noted may create a conflict in space
allocated between the VSAM catalog and DADSM allocate.
IDC210451 entryname, type
ON cravol RENAMED entryname
bears the same name as some other object in the catalog. One
of the objects was chosen to be' renamed as noted hi the
message.
System Action: Processing continues.
Programmer Response: If the renamed entry was a NONVSAM
entry, the associated Format 1 DSCB has'not been renamed.
The entry may be deleted (NOSCRATCH), the conflict resolved
and the entry redefined.
If a GOG base or GOG set has been renamed, the base and its
associated data sets should be deleted (NOSCRATCH) and
redefined after resolving the conflict.
If a catalog connector was renamed, that catalog may be
EXPORTed (using the DISCONNECT option), the conflict
resolved, and the catalog connector entry IMPORTed.
If an ALIAS was renamed the conflict may be resolved, and
ALTER issued to rename the entry back.
Note that the NONVSAM and GOG data sets will be
inaccessible via this new name, because the Format 1 DSCB
name does not correspond to the catalog name. The catalog
entry is accessible.
IDC210461 entryname, type
ON cravol RENAMED entryname
Explanation: An attempt was made to reset a unique object
into a catalog whcih contains an object of the same name. The
unique object was renamed along with its corresponding
Format 1 DSCB on all volumes.
System Action: Processing continues.
Programmer Response: The object noted is accessible. If
desired, the conflicting named object in the catalog may be
moved or renamed, and this object renamed via ALTER back
to its former name.
IDC210471 entryname,type
ON cravol MAY NOT BE ACCESSED BY NAME
Explanation: An attempt was made to reset a unique object
into a catalog which contained an object of the same name.
RESETCAT attempted to rename the unique object, but failed
either because all volumes were not available (see message
IDC39061) or the RENAME failed.
System Action: Processing continues.
Programmer Response: The object noted may be accessed via
the cluster name, but not the data or index name noted. The
data set may be EXPORTed, and then IMPORTed after
resolving the name conflict in order to gain accessability via
the date or index component name.
IDC211001 UNABLE TO DUMP MSC MAIN STORAGE
Explanation: An error occurred while the Mass Storage Control
main storage was being read. The Mass Storage Control main
storage cannot be dumped. There is a preceding message that
indicates the MSSC reason code associated with the error.
System Action: This dump request is bypassed. Remaining
dump requests are processed.
Programmer Response: Take the action associated with the
MSSC reason code in the preceding message.
Problem Determination: Table I, items 2, 13, and 30.
IDC211011 LOWSECTOR X'II' is GREATER THAN HIGHSECTOR
X'hh'
Explanation: A sector range was specified incorrectly. The low
sector value X'II' was greater than the high sector value X'hh'.
System Action: This dump request is bypassed. Remaining
dump requests are processed.
Explanation: An attempt was made to reset an object which
Section 4: I DC Messages - Access Method Services
4-67.1
Programmer Response: Correct the sector range, specifying a
IDC211041 UNABLE TO DUMP SA X'nnnn' MAIN STORAGE
low sector value that is lower than the high sector value.
Resubmit the command.
Explanation: An error occurred while the main storage of the
IDC211021 UNABLE TO DUMP MSC EXTENDED STORAGE
Explanation: An error occurred while the Mass Storage Control
extended storage was being read. The Mass Storage Control
extended storage cannot be dumped. There is a preceding
message that indicates the MSSC reason code associated with
the error.
System Action: This dump request is bypassed. Remaining
dump requests are processed.
Programmer Response: Take the action associated with the
MSSC reason code in the preceding message.
Problem Determination: Table I, items 2, 13, and 30.
IDC2110311NVALID SSID X'nnnn'
Explanation: The SSID value X'nnnn' was incorrectly specified
for a Staging Adapter. SSIDs for Staging Adapters must be of
the form X'OSxO', where x is in the range 0 through F.
System Action: Requests for this SSID are bypassed.
Remaining dump requests are processed.
Programmer Response: Correct the SSID and rerun the
command.
4·67.2
VS2 System Messages (VS2.03.80S)
Staging Adapter with the SSID of X'nnnn' was being read. The
main storage for that Staging Adapter cannot be dumped.
There is a preceding message that indicates the MSSC reason
code associated with the error.
System Action: This dump request is bypassed. Remaining
dump requests are processed.
Programmer Response: Take the action associated with the
MSSC reason code in the preceding message.
Problem Determination: Table I, items 2, 13, and 30.
IDC211051 UNABLE TO DUMP SA X'nnnn' EXTENDED STORAGE
Explanation: An error occurred while the extended storage of
the Staging Adapter with the SSID of X'nnnn' was being read.
The extended storage for that Staging Adapter cannot be
dumped. There is a preceding message that indicates the
MSSC reason code associated with the error.
System Action: This dump request is bypasssed. Remaining
dump requests are processed.
Programmer Response: Take the action associated with the
MSSC reason code in the preceding message.
Problem Determination: Table I, items 2, 13, and 30.
Section 4: I DC Messages - Access Method Services
4-67.3
VS2.03.808
IDC211061INVALID MSC TABLES RECORD ADDRESS X'cchhrr'
Explanation: A record address for a Mass Storage Control
tables record (cchhrr) was incorrectly specified. Either it is
outside the range of addresses for the Mass Storage Control
tables, or it does not conform to the following rules:
• cc (cylinder) must be in the range X'07' through X'27'.
• hh (head) must be in the range X'OO' through X'12'.
• rr (record) must be in the range X'Ol' through X'20'.
The only exception to the rules is that if cc is X'07', then hh
must be X'Ol'.
System Action: This dump request is bypassed. Remaining
dump requests are processed.
Programmer Response: Correct the address value and rerun
the command.
IDC211071 UNABLE TO COMPLETE MSC TABLES DUMP FROM
RECORD X'cchhrr'
Explanation: An error occurred while the Mass Storage Control
tables record indicated by cchhrr was being read. This record
and the remaining requested records from the Mass Storage
Control tables are not dumped. If cc is X'07', then hh must be
X'Ol'. There is a preceding message that indicates the MSSC
reason code associated with the error.
System Action: This dump request is bypassed. Remaining
dump requests are processed.
Programmer Response: If you have specified X'07' for cc, then
correctly specify hh as X'Ol', and rerun the command.
Otherwise, take the action associated with the MSSC reason
code in the preceding message.
Problem Determination: Table I, items 2, 13, and 30.
IDC211081 MSC TABLES LOWCHR X'cchhrr' IS GREATER THAN
HIGHCHR X'cchhrr'
Explanation: The beginning cchhrr was greater than the ending
cchhrr in a request to dump portions of the Mass Storage
Control tables.
System Action: This dump request is bypassed. Remaining
dump requests are processed.
Programmer Response: Correct the cchhrr values and rerun
the command.
IDC211411 CELL xyz I XRANGE (Iowx highx) IS NOT VALID
FOR MSF n AND NOT PROCESSED
Explanation: Either the CELL xyz or the XRANGE (lowx highx)
indicated is invalid for Mass Storage Facility n. xyz is the
invalid cell location, and (Iowx highx) is the invalid range of X
coordinates. The valid values for coordinates depend upon the
model of Mass Storage Facility:
• For a Model A1/B1, x ranges from 234 through 247, y
ranges from 0 through 27, and z is 0 or 1.
• For a Model A2/B2, x ranges from 206 through 247, y
ranges from 0 through 27, and z is 0 or 1.
• For a Model A3/B3, x ranges from 178 through 247, y
ranges from 0 through 27, and z is 0 or 1.
• For a Model A4/B4, x ranges from 150 through 247, y
ranges from 0 through 27, and z is 0 or 1.
System Action: The indicated CELL or XRANGE value in error
is ignored. Processing continues.
Programmer Response: Correct the value in error and rerun
the command.
Problem Determination: Table I, items 1, 13, and 30.
IDC211441 LOW XRANGE lowx IS GREATER THAN HIGH
XRANGE highx
Explanation: The low value lowx in the XRANGES parameter is
4-68
VS2 System Messages (VS2.03.808)
greater than the high value highx. The values must be in the
range 150 through 247, and the low value must not be greater
than the high value.
System Action: The invalid XRANGE is ignored, and processing
continues.
Programmer Response:: Correctly specify the invalid range
and rerun the command.
Problem Determination: Table I, items 1, 13, and 30.
IDC310001 CATALOG NOT A RECOVERABLE CATALOG
Explanation: The catalog specified for reset is not a
recoverable catalog.
System Action: The RESETCAT command is terminated. No
change has been made to the catalog or a Catalog Recovery
Area (CRA).
Programmer Response: Respecify the catalog to be reset.
IDC310011 SYSTEM MASTER CATALOG SPECIFIED FOR RESET
Explanation: The master catalog was specified for reset. The
master catalog cannot be reset while it is in use as a master
catalog.
System Action: The RESETCAT command is terminated. No
change has been made to the catalog or a Catalog Recovery
Area (CRA).
Programmer Response: Ensure that the catalog to be reset is
not in use as a master catalog before issuing RESETCAT.
IDC310041 DEFINE OF WORKFILE FAILED
Explanatoin: DEFINE failed for the workfile. Message IDC30091
precedes this message identifying the Catalog Management
return code which will indicate the reason for failure.
System Action: The RESETCAT command is terminated. No
change has been made to the catalog or a Catalog Recovery
Area (CRA).
Programmer Response: Take corrective action as noted in the
IDC30091 message.
IDC310051 WORKFILE DEFINED IN THE CATALOG TO BE RESET
Explanation: The workfile was defined in the catalog to be
reset.
System Action: The RESETCAT command is terminated. No
change has been made to be catalog or a Catalog Recovery
Area (CRA).
Programmer Response: Specify a catalog other than the one
being reset via the WORKCAT parameter, or specify another
catalog as the first concatenated entry in the JOBCAT or
STEPCAT statement.
IDC310061 PHYSICAL I/O error - VSAM ACTION CODE rrrr
Explanation: A physical I/O error on the catalog was
encountered while extending the catalog.
System Acton: The RESETCAT command is terminated.
Programmer Response: Correct the physical error and reissue
RESETCAT. The VSAM action code can be found in the OS/VS
Virtual Storage Access Method (VSAM) Programme(s Guide.
The catalog and CRA entries have not been altered and hence
are recoverable in their current state - barring the I/O error.
IDC310071 LOGICAL I/O ERROR - VSAM ACTION CODE rrrr
Explanation: A logical I/O error was encountered while
extending the catalog during RESETCAT. There were not
enough free records in the catalog being reset, consequently
RESETCAT attempted to get more.
System Action: The operation is terminated.
Programmer Response: Correct the logical error. The VSAM
action code can be found in the OS /VS Virtual Storage Access
VS2.03.808
Method (VSAM) Programmer's Guide. If the catalog has
reached 16 extents and cannot be extended further, a larger
catalog may be defined in which to perform the RESETCAT.
The catalog and CRA entries have not been altered.
System Action: The operation is terminated.
Programmer Response: For the catalog being reset, specify
IDC3100S1 ERROR ACCESSING THE CATALOG
IDC3101S1 CRA UNAVAILABLE
Explanation: RESETCAT encountered an error trying to access
Explanation: RESETCAT required a volume that could not be
allocated.
System Action: The operation is terminated.
Programmer Response: A secondary CRA volume was required
during the reset of a catalog and it was not available. If
enough units are not available, specify the volume via a DD
statement and include that DD statement in the CRAFILES
parameter on the command indicating NONE. See message
IDC210201.
the data set specified by the CATALOG parameter. Message
IDC30091 precedes this message identifying the specific error.
System Action: The operation is terminated.
Programmer Response: Correct the error specified in the
IDC30091 message and reissue the command. If the error is
not correctable, a new catalog of the same name may be
defined into which all of the volumes owned by the failing
catalog may be reset using RESETCAT. The entries in the
catalog have not been altered.
IDC310101 CRA DOES NOT BELONG TO CATALOG - VOL volser
Explanation: The CRA was specified for reset, but it belongs to
a catalog other than the catalog to be reset.
System Action: The operation is terminated.
Programmer Response: Respecify the correct volume to be
reset and reissue the command.
IDC310121 MAXIMUM RELATIVE RECORD NUMBER EXCEEDED
IN WORKFILE
Explanation: The workfile relative record number (rrn) limit has
been exceeded. No more records can can be written to the
workfile. The resultant catalog is too large.
System Action: The operation is terminated.
Programmer Response: Respecify subsets of the CRA volumes
specified for reset and issue multiple RESETCAT commands.
The catalog entries have not been altered.
IDC310131 COULD NOT MERGE ONE OR MORE CRAS
Explanation: See preceding message which indicates that:
• Open failed for CRA (lDC33001)
• Close failed for CRA (IDC33011)
• CRA does not belong to catalog to be reset(IDC310101)
System Action: The operation is terminated.
Programmer Response: Correct the error in the referenced
message and reissue the command. The catalog entries have
not been altered.
DISP = (OLD,KEEP) on the DD statement, or get exclusive use.
Reissue the command.
IDC310191 CRA volser SPECIFIED FOR RESET MORE THAN
ONCE
Explanation: The CRAVOLS parameter specified the same
volser more than once, or the CRAFILES parameter specified
the same volser more than once via ddnames.
System Action: The operation is terminated.
Programmer Response: Specify the correct volumes for reset
and reissue the command.
IDC310351 BAD VOLUME RECORDS FOR volser
Explanation: In a CRA, either the volume record for the volser
indicated does not exist or one of its secondary records does
not exist (IECII0221). If IGNORE was specified, the reset will
occur. This may mean that all data sets allocated on this
volume will be marked unusable. If NOIGNORE was specified,
the RESETCAT operation terminates before updating the
catalog or CRA(s).
System Action: The command may terminate (see
Explanation).
Programmer Response: If IGNORE was specified, no error
exists in the catalog; accompanying messages will indicate any
action taken on individual data sets as a result of this. If
NOIGNORE was specified, use EXPORTRA to export all VSAM
data sets on this volume, FORCE DELETE the volume, and use
IMPORTRA to recover all data sets.
IDC310381 COULD NOT UPDATE ONE OR MORE CRAS
Explanation: See preceding mesage which indicates that:
IDC310141 DELETE OF WORKFILE FAILED
Explanation: DELETE failed for the workfile. Message IDC30091
precedes this identifying the specific error.
System Action: The operation is terminated.
Programmer Response: Unless some previous message
indicates a terminating error, the RESETCAT operation has
been completely performed. The workfile may be deleted using
the DELETE command after correcting the error indicated in
mesage IDC30091.
IDC310161 NO CRA SPECIFIED FOR RESET
Explanation: The CRAFILES parameter specified no CRA with
the ALL option; hence, no volume was specified for reset.
System Action~ The operation is terminated.
Programmer Response: Specify the correct volumes for reset
and issue the command.
IDC310171 UNABLE TO GET EXCLUSIVE USE OF THE CATALOG
Explanation: Some other task is open to the catalog requested
to be reset. The RESET operation is unable to reset a catalog
without exclusive use.
• Open failed for CRA (lDC33001)
• Close failed for CRA (lDC3301l)
System Action: The operation is terminated.
Programmer Response: Correct the error in the referenced
message and reissue the command. The catalog entries have
been updated but the CRA entries have not.
IDC311401
** UNABLE TO OBTAIN THE MSF CELL MAPS
MSC CONFIGURATION TABLE
Explanation: Either the Mass Storage Facility Cell Map Table or
the Mass Storage Control Configuration Table could not be
read. Therefore, the status of the Mass Storage Facility cells
could not be obtained, or the availability of the Mass Storage
Facility could not be verified.
System Action: processing of this command terminates.
Programmer Response: Take the corrective action described in
the previous message, and rerun the command.
Problem Determination: Table I, items 1, 13, and 30.
IDC311421 AUDITMSS TERMINATED. NO VALID CELL(S)
XRANGE(S) SPECIFIED
Explanation: The values specified with the CELLS or XRANGES
Section 4: IDC Messages - Access Method Services
4-6S.1
parameters were not valid for the model of Mass Storage
Facility. No AUDITMSS report is produced.
The valid values for coordinates of cells depend upon the
model of Mass Storage Facility:
• For a Model A1/B1, the X coordinate ranges from 234
through 247, the y coordinate ranges from 0 through 27,
and the z coordinate is 0 or 1.
• For a Model A2/B2, the X coordinate ranges from 206
through 247, the y coordinate ranges from 0 through 27,
and the z coordinate is 0 or 1.
• For a Model A3/B3, the X coordinate ranges from 178
through 247, the y coordinate ranges from 0 through 27,
and the z coordinate is 0 or l.
• For a Model A4/B4, the X coordinate ranges from 150
through 247, the y coordinate ranges from 0 through 27,
and the z coordinate is 0 or 1.
System Action: The command terminates.
Programmer Response: Correct the values specified with
CELLS or XRANGES, and rerun the command.
Problem Determination: Table I, items 1, 13, and 30.
4-68.2
VS2 System Messages (VS2.03.808)
IDC311431
** INCOMPLETE CHECK I READ REPORT
PRODUCED, ERROR AT X LOCATION xxx
Explanation: The AUDITMSS command is unable to check the
status of all the requested cells, or to read the labels of all the
requested cartridges. The X coordinate of the cell where the
error occurred is indicated by xxx.
System Action: The command terminates.
Programmer Response: Rerun the command for the values not
processed (all the cells with X coordinate equal to or greater
than xxx), after corrective action was taken as indicated in the
primary message.
Problem Determination: Table I, items 2, 13, and30.
IDC311451
** NO CHECK I READ REPORT PRODUCED, ERROR
AT X LOCATION xxx
Explanation: The AUDITMSS command is unable to check the
status. of any of the requested cells, or to read the labels of
any of the requested cartridges. The X 'coordinate of the cell
where the error occurred is indicated by xxx.
System Action: The command terminates.
Programmer Response: Rerun the command for the values not
processed (all the cells with X coordinate equal to or greater
than xxx), after corrective action was taken as indicated in the
primary message.
Problem Determination: Table I, items 1, 13, and 30.
Programmer Response: Rerun the command after the problem
with the Mass Storage Control has been corrected.
Problem Determination: Table I, items 3, 13, and 30.
IDC311801 PRIMARY TABLES CANNOT BE COPIED TO WORK
DATA SET
IDC311601 TOSTAGINGDRIVE SSID SPECIFIED IS NOT A VALID
MSC TABLES SSID
Explanation: The primary Mass Storage control tables cannot
Explanation: The SSID specified as a target for the table copy
System Action: Processing of this command terminates.
Programmer Response: Ensure that the work data set is
is not an SSID of one of the tables packs. The SSID must be
0,2,4, or 6.
System Action: Processing of this command terminates.
Programmer Response: Correctly specify the SSIO used with
the TOSTAGINGORIVE parameter, and rerun the command.
Problem Determination: Table I, items, 3, 13, and 30.
IDC311701 UNABLE TO DETERMINE PRIMARY MSC TABLES
LOCATION
Explanation: The attempt to read the Mass Storage Control
main storage to determine the primary Mass Storage Control
tables location failed. The information necessary to build the
SSIO for the primary tables is not available.
System Action: Processing of this command terminates.
be copied to the work data set.
allocated properly, and rerun the command.
Problem Determination: Table I, items 3, 13, and 30.
IDC311811 SECONDARY TABLES CANNOT BE COPIED TO
WORK DATA SET
Explanation: The secondary Mass Storage Control tables
cannot be copied to the work data set.
System Action: Processing of this command terminates.
Programmer Response: Ensure that the work data set is
allocated properly, and rerun the command.
Problem Determination: Table I, items 3, 13, and 30.
Section 4: IDC Messages - Access Method Services
•
4-69
4-70
VS2 System Messa,es (VS2 Release 3.7)
Section 5: Supervisor Messages (lEA)
Component Name
lEA
Program Producing Message
ABEND, IEAPRINT program, input/output supervisor, nucleus initialization program (NIP), and supervisor.
Audience and Where Produced
For operator: console.
For programmer: SYSPRINT data set.
Message Format
xx I EAnnns text
xx
Message reply identification (absent, if operator reply not required or if issued by IEAANIP at IPL time).
nnn
Message serial number.
s
Type code:
Action; operator must perform a specific action.
A
E
Eventual action; operator must perform action when he has time.
I
Information; no operator action is required.
W Wait; processing stopped until action is determined and performed.
text
Message text.
Comments
None.
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IEAOOOA
IEAOOOA
IEAOOOI
ddd ,INT REQ,cm,stat,sensbbbbbb"ser ,jjj
ddd,INT REQ,CC = 3/NO PATHS AVAILABLE",jjj
ddd,INT REQ,cm,stat,sensbbbbbb",jjj
Explanation: For the first format of the message, the
input/output supervisor received a 'not oper~tional' indication
on the last available path to a device; for the second format of
the message, the I/O supervisor detected a device that
requires intervention.
In the message text in hexadecimal, the fields are:
ddd
Unit address of the device.
cm
Operation code of the channel command word (CCW) during
whose execution the error occurred. If the channel
command word cannot be found, this field appears as **
stat
Status portion of the channel status word (CSW).
sens
First 2 sense bytes for the error condition.
bbbbbb
Next 3 sense bytes for the error condition. This field
appears only for devices that give more than 2 bytes of
sense information. For the 3340, 24 bytes of sense will be
given.
ser
Serial number of the volume on which intervention is
required. This field appears only for magnetic tapes, direct
access devices or 3540s.
jjj
Job name, in characters, during which intervention is
required. (If the job name cannot be determined, this field
will be left blank.)
Operator Response: For the first format of the message, either
physically turn on a path to the device (for example, a control
unit switch or a channel switch) or VARY a path online that
has been previously varied offline. Then, if necessary, make
the device ready.
For the second format of the message, take an approprrate
action, such as:
• Make the unit ready. If the unit cannot be made ready,
cancel the job.
• Feed more cards to the reader or punch.
• Clear a card jam.
• Empty a stacker.
• Empty the chip box.
• Put paper into the printer or console typewriter.
For the third format of the message, the I/O Supervisor
detected a 3851 device has an intervention required situation,
but the device is capable of handling it. No operator
intervention is required.
Problem Determination: Table I, items 2, 30.
IEAOOOI
ddd,err,cm,stat,sens,
dCbctfd
}
opxxterm
{ binxcylntrck
,[ser],jjj[,hh.mm.ss]
Explanation: An uncorrectable input/ output error was detected
by the I/O supervisor, the basic telecommunication access
method (BTAM), or the telecommunication access method
(TCAM) routine. In systems with the graphics access method
(GAM), unit checks and conditions that require operator
intervention indicate devices that do not exist or that were
included at system generation time but not attached to the
system. Note: For the 2305, 3330 mod 11, 3330, 3340/3344,
3350, and 3851, two lines are required to contain the
message.
Note: Two consecutive commas or a blank. field in the
message text indicates that a field could not be determined or
is contained on the next or previous line of the message.
In the message text, the fields are:
ddd
Unit address of the device or line address of the
telecommunication device, in hexadecimal.
err
Description of the error based on status and sense
information:
BOC - bus out check.
CCC - channel control check.
I EA Messages - Supervisor
5-1
•
VS2.03.801
CDC - channel data check.
CEM - CE message
CHC - chaining check.
CMD - command reject.
CPC - channel program check.
CTRl BlK ERR - the tape ERP is using an input/output
block (lOB) in which the CSW command address is zero
instead of an expected address.
DCC - data converter check (for magnetic tapes only).
DCK - data check.
DSE FAilED - a data security erase failure occurred. An lOB
intercept condition has been detected and the error is
flagged as permanent.
EQC - equipment check.
ERROR ON ERG - a data check occurred during an erase
gap operation. The operation was initiated by the write
recovery procedures. This message is an indication that
some residual data remained on the tape; a later reread
through the erased area may indicate a noise record.
Depending on the length of the noise, a permanent error
(read data check) may occur.
ICC - interface control check.
10E - input/ output error (for errors other than those
described above).
IPl - IPl request (for 370x only).
lOA - lost data (for telecommunications only.)
MAM - missing address marker (for direct access only.)
NIN • not initialized (for 3791 only).
NOISE- ERP - error recovery procedures were in progress
when a short record-data check condition was encountered.
This situation should not occur, and is an indication of
either faulty hardware media, a crimp in the tape, or noise
on the bus line. Repositioning of the tape cannot be
guaranteed under these conditions.
NOISE-USER - a noise record (a record whose length is
less than 12 bytes) was recognized as a cause of a data
check. The noise record is ignored, and no repositioning for
a reread is attempted.
NRF - no record found (for direct access only.)
OVR - overrun (for direct access and magnetic tapes only.)
PRC - channel protection check.
SEN - a unit check occurred during a sense operation.
(When this condition is present, th'e fields cm, stat, sens,
and binxcylntrck do not appear in the message text.)
SKC - seek check (for direct access only.)
SUU - subsystem unit unusable
TOT - time out (for telecommunications only.)
UEX - unit exception.
UNC - unusual command (for 2540 card reader and punch
only).
UNEX INTRPT - (1) The ERP detected an interrupt condition
and only device end is indicated in the CSW status byte.
This will be displayed as a status of x'OOOO' or x'0400'. (2)
The tape drive has gone from 'not ready' to 'ready' status
or has encounterea a 'load check'. This will be displayed as
a status of x'1400'. This is a SECURITY INTERRUPT. A
security interrupt indicates that during the time your drive
was NOT READY, your tape may have been replaced or
moved so that it is mispositioned. If neither of these
situations occurred, the processing may proceed normally.
UNEX lOAD PT - an unexpected load point was
encountered during error recovery for magnetic tape
(probably the result of a recording density incompatibility).
The message may appear twice if the tape is not a standard
label tape.
WRI - write inhibit switch should be checked.
cm
Command code, in hexadecimal, of the channel command
word (CCW) being executed when the error occurred. If the
5-2
VS2 System Messages (VS2.03.801)
channel command word cannot be found, this field appears
as **.
stat
Status portion, in hexadecimal, of the channel status word
(CSW).
sens
The first byte, in hexadecimal, describes a unit check type
error condition (for telecommunication devices). The second
byte, in hexadecimal, contains sense information resulting
from the execution of a diagnostic write/read or read/skip
command (from TCAM) which ended with a unit check
status (2701 data adapter unit). For other devices, these
same two bytes will appear, in hexadecimal, if a unit check
condition is indicated in the stat field. For devices that give
more than two bytes of sense information, this field will also
contain the remaining sense bytes, in hexadecimal. For
devices which give more than 6 sense bytes, this field will
be contained on the second line of the message. For the
3330, 3330 mod 11, 3340/3344, 3350, and 2305, this
field will contain the 8 sense bytes for program errors or 24
sense bytes for equipment and data checks or seek checks
for 3340s.
Note: The message on the system console reflects the
sense-byte information from the last entry for direct access
devices; the sense-byte information located in the
SYSl.lOGREC data refelcts the data from the initial error
condition.
dcbctfd
Record count, in hexadecimal, not including label retords,
This field appears only for magnetic tape and indicates the
count of the record preceding the error record.
opxxterm
TP operation code, in hexadecimal, describing the type of
channel command word (CCW) being executed when the
error occurred. xx is not used, but is followed by the
terminal identification characters, in hexadecimal. It may be
either two bytes or one byte, depending on the terminal
type. If it is one byte, it is left justified. If a dial line is
being used with TCAM, the last four digits of the dial
number are provided.
binxclyntrck
Address, in hexadecimal, of the bin (binx), the cylinder
(cyln), and the track (trck) where the error occurred. When
an error occurs while trying to obtain this data, the last
seek address is substituted, This field appears only for disk
and drum direct access devices. On a data or equipment
check for a 2305, 3330, 3330 mod 11, or 3340/3344, or
3350 this field does not appear. For other errors on these
devices, the field is contained on the· second line.
ser
Serial number of the volume on which the error occurred.
This field appears only for magnietic tapes or direct access
devices.
jjj
Job name.
hh.mm.ss
Time that the message was received in hours, minutes, and
seconds.
Operator Response: Probable hardware error. For magnetic
tape devices, proceed with caution in unconditionally accepting
the results of the operation. Check that tapes being used by
this job have not been replaced or removed. Each message
should be considered as a potential warning of a marginal
condition.
For other than magnetic tape devices, note that some
abnormal error condition occurred. Depending on the severity
of the error (check status and sense information) and
depending on the installation requirements, take the
appropriate action.
Possible values of err and appropriate responses are as
follows:
• CMD REJECT - Correct and retry (for 2305, 3330, 3330
mod 11, 3340/3344, and 3350). If the command is a X'FF',
this is a probable hardware failure. The disengage command
failed and a Customer Engineer's attention is required (for
1419/1275).
• OVR:
BOC - bus out check.
EQC - equipment check.
ICC - interface control check.
These are permanent hardware faults. Customer engineer
action is required.
• DCK - Request an alternate sparing utility program such as
IEHATLAS to perform recovery/replace functions, and to
assign an alternate track spare, if necessary. If the utility
cannot complete, the GET ALT function in the IBCDASDI or
IEHDASDR utility should be invoked. This will assign the
space but will not perform recovery/replace. If no alternate
spares are available, Customer Engineer action is required
(for the 2305, 3330, 3330 mod 11, 3340/3344, and
3350).
• WRI - If the write inhibit switch is set on to inhibit execution
of write commands and the volume should be written on,
set the switch off and rerun the job. If the write inhibit
switch is set on to intentionally inhibit execution of write
commands, follow the procedures established by your
installation (for the 2305, 3330, 3330 mod 11, 3340/3344,
and 3350).
Problem Determination: Table I, items 2, 3~.
IEAOOOI
ddd err"""hh.mm.ss
Explanation: An error was detected by the 3851 Host ERP that
requires a 'CE Message' (CEM) or a 'Subsystem Unit Unusable'
(SUU) Message. Equipment Check (EQ CK) may occur with
CEM and/or SUU. Since the system WTO routine can print only
one message, the ERP will print the CEM and/or SUU message
and the system WTO routine will print the remaining message
with full sense.
ddd - Unit address of the MSC.
err - CEM or SUU.
SUU--Subsystem Unit Unusable. The 3851 subsystem has
marked one of its units unusable due to a error condition.
The SSID of that unit is in sense byte 1 bits 4-7 and sense
byte 2 bits 0-7.
CEM--C E Message. The 3851 Subsystem has detected an
error of importance to the Customer Engineer.
hh.mm.ss - Time the message was received in hours, minutes
and seconds.
System Action: The ERP will continue the recovery action
based on the error condition.
Operator Response: Probable hardware error. Each message
should be considered as a potential warning of a marginal
condition. Depending on the installation requirements, take
appropriate action.
Problem Determination: Table 1, items 2,30.
IEAOOOI
'SYS SWITCH FROM xxx TO
OFFLINE'
III
STARTED, xxx
Explanation: The 3851 Host ERP detected a switchable
permanent I/O error and has started a switch from the Primary
MSC to the Alternate MSC. The MSC that failed is set
OFFLINE. XXX is the address of the MSC that failed, and is
OFFLINE. III is the address of the MSC being switched to and
is the Primary MSC.
System Action: The ERP continues processing the switch to
the Alternate MSC.
Operator Action: Probable Hardware error. Depending on the
installation requirements, take the appropriate action.
Problem Determination: Table 1, items 2,30.
IEAOOOI
'MSC SWITCH FROM xxx TO zzz STARTED, xxx
OFFLINE'
Explanation: The 3851 Host ERP detected that the Primary
MSC has lost the lower interface and has started a switch from
the Primary MSC to the Alternate MSC. The lower interface
was lost due to some other CPU doing a switch for a 'Operator
Vary' or a permanent I/O error 'System switch'. xxx is the
address of the MSC being switched from, and is OFFLINE. zzz
is the address of the MSC being switched to and is the
Primary MSC.
System Action: The ERP continues proceSSing the switch to
the Alternate MSC.
Operator Action: Possible Hardware error. Depending on the
installation requirements, take the appropriate action.
Problem Determination: Table 1, items 2,30.
IEAOOOI
'SYS SWITCH FROM xxx TO zzz ENDED'
Explanation: The System switch function has ended. xxx is the
address of the MSC switched from and is OFFLINE. zzz is the
address of the MSC switched to and is the Primary MSC.
System Action: The ERp·will reissue the failing CCW(s) that
initiated the switch.
Operator Action: None.
IEAOOOI
'MSC SWITCH FROM xxx TO zzz ENDED'
Explanation: The MSC switch function has ended. xxx i~. the
address of the MSC switched from, and is OFFLINE. zzz is the
address of the MSC switched to and is the Primary MSC ..
System Action: The ERP will reissue the failing CCW(s) that
initiated the switch.
IEAOOOI
'SYS SWITCH FROM xxx TO zzz FAILED, zzz
OFFLINE'
Explanation: The MSC being switched to had a permanent I/O
error and is set OFFLINE. There is no usable MSC. xxx is the
address of the failing MSC switched from and is OFFLINE. zzz
is the address of the MSC being switched to. It is OFFLINE and
is the Primary MSC.
System Action: This request and all future I/O requests to this
device will be terminated in error by the MSSC component.
Operator Action: Probable Hardware error. Depending on the
installation requirements, take appropriate action.
Problem Determination: Table 1, items 2,30.
IEAOOOI
'MSC SWITCH FROM xxx TO zzz FAILED, zzz
OFFLINE'
Explanation: The MSC being switched to had a permanent I/O
error and is set OFFLINE. xxx is the address of the MSC
switched from and is OFFLINE. zzz is the address of the MSC
switched to. It is OFFLINE and is the Primary MSC.
System Action: This request and all future I/O requests to this
device will be terminated in error by the MSSC component.
Operator Action: Probable Hardware error. Depending on the
installation requirements, take appropriate action.
Problem Determination: Table 1, items 2,30.
IEAOOOI
'SYS SWITCH FROM xxx TO
ZZZ,
zzz NOT AVAIL'
Explanation: An switchable permanent I/O error was detected
by the ERP but a Alternate MSC does not exist or it i s "
Section 5: lEA Messages.,. Supervisor
5-3
OFFLINE. There is no usable MSC. xxx is the address of the
failing MSC. It is OFFLINE and it is the Primary MSC. zzz is the
address of the Alternate MSC and is OFFLINE. If a Alternate
MSC does not exist, zzz will be ' ALT' .
System Action: This request and all future I/O requests will be
terminated in error by the MSSC component.
Operator Action: Probable Hardware error. Depending on the
installation requirements, take the appropriate action.
Problem Determination: Table 1, items 2,30.
IEAOOOI
'MSC SWITCH FROM xxx TO zzz, zzz NOT AVAIL'
Explanation: The 3851 ERP detected that the Primary MSC
has lost the lower interface and cannot switch to the Alternate
because it is OFFLINE or does not exist. The lower interface
was lost due to some other CPU doing a switch for 'Operator
Vary' or a permanent I/O error 'System Switch'. There is no
usuable MSC. xxx is the address of the MSC switched from. It
is OFFLINE and it is the Primary MSC. zzz is the address of the
MSC'switched to and is OFFLINE. If a Alternate MSC does not
exist, zzz will be ' ALT' .
System Action: This request and all future I/O requests to this
device will be terminated in error by the MSSC component.
Operator Action: Probable Hardware error. Depending on the
installation requirements, take the appropriate action.
Problem Determination: Table 1, items 2,30.
IEAOOll
UNIT ddd, PATH pth INOPERATIVE FOR CPU x
Explanation: One path to a multipath device has become
inoperative. The system continues all operations on a limited
basis, using the remaining paths.
In the message text, the fields are as follows:
ddd
Unit address, in hexadecimal, of the device.
pth
One of the following:
X'80' for primary path CPU 0
X'40' for secondary path CPU 0
X'20' for primary path CPU 1
X'10' for secondary path CPU 1
x
Central processing unit, 0 or 1, for which the path is
inoperative.
System Action: The system will automatically begin reusing the
path when it becomes operational.
Operator Response: Probable hardware error. None.
Problem Determination: Table I, items 2, 30.
IEA0031
I/O MALFUNCTION TO DEVICE ddd. I/O
TERMINATED.
requests to these devices will be terminated in error by the
ERP and returned to the I/O requestor until: 1) the failing CPU
is brought back online, or 2) a path to each device from the
operative CPU is brought online (by VARY PATH or VARY
CHANNEL command).
System Action: This request and all future I/O requests to
these devices are terminated in error by the ERP until paths
on the operative CPU are made available or the failing CPU is
brought back online.
Operator Response: If paths to the listed devices are available
on the operative CPU, they should be varied online. If no such
paths exist the volume should be swapped. Bringing the failing
CPU back online (if this is possible) will also eliminate the
problem.
IEA0051
DEVICE ddd RESERVED ON OFFLINE PATH pth
FROM CPU x.
Explanation: The I/O supervisor found it necessary to reserve
device ddd down a path from CPU x on a path that was
logically offline. This path (pth) is currently the reserved path
for the device. (This message will always be preceded by a
042 wait state, which gives the operator the option to allow
reservation down offline paths or restart the system.)
System Action: Further requests to device ddd will be
terminated in error until path pth from CPU x is varied online
by a VARY PATH and/or VARY CHANNEL command sequence.
Operator Response: Bring path pth from CPU x to device ddd
online by the VARY PATH or VARY CHANNEL command.
IEA0241
ERROR IN GTF. opt TRACE OPTION WAS DISABLED
Explanation: ABDUMP in its formatting of the GTF trace table
found an error record for trace option opt; where opt is EXT,
10, 510, PI, or DSP. This error record was produced when GTF
encountered a program check while attempting to create a
trace record for opt. This message is followed by a
hexadecimal dump of the error record. Refer to messages
AH11181 and AH11201.
Note: If opt is SVC, SV,C tracing will continue.
System Action: The program check for the error record
caused GTF to bypass recording further events for the trace
option opt. However, GTF continued to record all events for
the other trace options requested.
Programmer Response: Probable user error. Ensure that
problem programs are not altering the GTF region.
Problem Determination: Table I, items 1, 2, 16, 29. Ensure
that sufficient storage is available within the GTF region for a
SNAP dump (an additional 4K is needed for ABDUMP /SNAP
execution). Ensure that the GTFSNP catalogued procedure is
used to obtain an ABOUMP /SNAP dump.
Explanation: During a CCH or MIH call to the I/O supervisor
for device ddd, the device failed to terminate ongoing I/O
activity when a halt device-clear I/O sequence was issued. The
device has probably become unusable.
System Action: The most recent I/O request to the device is
terminated in error by the ERP unless DOR is able to
successfully swap the volume.
Operator Response: Vary device ddd offline or swap it to
prevent further requests from encountering the problem.
Problem Determination: Table I, items 2, 18, 24, 30.
found a GTF record with an invalid EIO or FlO field. ABOUMP
prints this message and follows it with a hex.adecimal dump of
the error record.
System Action: Processing continues.
Programmer Response: Probable user error. Ensure that
problem programs are not altering the trace table.
Problem Determination: Table I, items 1, 2, 11, 29.
IEA0041
IEA0301
DEVICES:ddd,ddd,ddd,ddd, ..• ,ddd HAVE BEEN SET
FOR I/O REQUEST TERMINATION.
Explanation: In response to an ACR call to the I/O supervisor,
the listed devices were found to have no paths available from
the operative CPU. The devices have been marked offline for
hierarchy reasons to prevent future allocation. All future I/O
5-4
VS2 System Messages (VS2 Release 3.7)
IEA0251
INVALID GTF RECORD FOLLOWS
Explanation: ABDUMP in its formatting of the GTF trace table
OPEN FAILED FOR DUMP DATA SET FOR
[DUE TO
{~~::} ]
Explanation: An attempt to open a dump data set during
ABEND proceSSing failed. JS signifies a job step task, and ST a
\.1
~\
.}
subtask. If the phrase DUE TO Scde or Ucde appears, the task
was abnormally terminated with a system (S) cde or a user (U)
code of cde.
System Action: The dump is bypassed and abnormal
termination continues.
Programmer Response: If the phase DUE TO cde appears,
respond as indicated for that completion code. If not, make
sure that the dump DO statement is currently specified and
rerun the job.
Problem Determination: Table I, items 1, 15, 29.
IEAIOIA
SPECIFY SYSTEM PARAMETERS FOR RELEASE
xx.yy.zzz
Explanation: This message is issued during system initialization
to allow the operator to change certain system parameters
that were specified during system generation, or later via
IEASYSxx members of SYS1.PARMLIB. In the message text, xx
is the release number, yy is the release level, and zzz is the
system type (PCP, MFT, MVTIMP, VS2).
System Action: The system waits for the operator's response
and changes the system parameters as specified by the
operator.
Operator Response: Reply as specified by the system
programmer. The reply must take one of the forms described
in the System Initialization and Tuning Guide, GC2S-06Sl.
IEAI071
,.I
prm IGNORED
Explanation: A reply to message IEAIOIA names a parameter
prm, that was not selected by the installation for optional
changing when the system is loaded.
System Action: The nucleus initialization program (NIP)
continues processing.
Operator Response: Report this message to the programmer.
Programmer Response: Probable user error. Make sure that
the parameter was not restricted from operator changes in the
IEASYSxx member of SYSl.PARMLIB (OPI - NO option).
Problem Determination: Table I, items 2, 11, 29.
IEAI081
PERMANENT I/O ERROR DURING BLDL
Explanation: The nucleus initialization program (NIP) is unable
to bring the linkage library (SYSl.LlNKLlB) directory into
virtual storage because of an uncorrectable input/output error.
System Action: The nucleus initialization program continues
processing without a resident directory.
Operator Response: Probable hardware error. Report this
message to the programmer.
Problem Determination: If the error recurs, before calling IBM
for hardware support, record the address of the device on
which the input! output error occurred and have it available.
IEA1091
BLDL FAILED FOR FOLLOWING MODULES
mod
mod
Explanation: During nucleus initialization, parts of the resident
directories have not completed. The module names not found
in SYSl.LlNKLlB and therefore not appearing in the resident
directory are printed on the console immediately following this
message.
System Action: The nucleus initialization program (NIP)
continues processing with an incomplete resident directory.
Operator Response:~ Probable user error. Report this message
to the system programmer and save the master console log.
Programmer Response: Probable user error. Ensure that the
modules listed are included in the SYSl.lINKLIB data set.
Problem Determination: Table I, itenls2, 13, 2Sc, 29.
lEA 116A
CONTINUE SYSTEM PARAMETERS
Explanation: During nucleus initialization, the reply to message
IEAIOIA specified CONT as its final entry. The CONT indicated
that the reply was incomplete and that additional parameters
were to be specified.
System Action: The system waits for a reply to message
IEAIOIA.
Operator Response: Continue the reply to message IEAlOlA,
beginning this continuation with REPLY 00.
IEA120A
DEVICE ddd SHARED. REPLY 'CONT' OR 'WAIT'
Explanation: Device ddd is a shared device and is presently
reserved by a central processing unit (CPU) other than the
central processing unit from which an IPL is being performed.
System Action: The system action depends on the operator's
response.
Operator Response: To wait until the device is released by the
central. processing unit that is presently using it, enter REPLY
xx, 'WAIT'. Normal processing will continue after the device is
available.
Otherwise, enter REPLY xx, 'CONTINUE'. This reply will result in
the device being marked unavailable to the central processing
unit from which the IPL is being performed. Processing will
continue. (If this reply is entered, do not execute any job that
might require allocation of device ddd. If such a job is
executed, a mount message will be issued and subsequent
operator action might make the device unavailable to the
central processing unit that originally reserved it.)
Note: If the message appears frequently or if the wait time is
excessive, notify the system programmer at the installation.
lEA 1521
HARDCPY SPECIFICATION INVALID
Explanation: In response to message lEA lOlA or IEA332A, the
operator. specified a device for a hard copy log that was not a
valid console.
System Action: The system issues message IEA332A.
Operator Response: Probable user error. Respond as indicated
for the following IEA332A message.
Problem Determination: Table I, items 11, 29.
IEA1531
HARDCPY CONSOLE UNAVAILABLE
Explanation: In response to message IEAlOlA, HARDCPY
specified a valid console, but the console was unavailable at
IPL time.
Operator Response: Probable user error. Respond as indicated
for the following IEA332A message.
lEA 1541
HARD COpy OF INITIALIZATION MESSAGES
DISCONTINUED
Explanation: The. logging of nucleus initialization program (NIP)
messages must be discontinued because the message buffer is
full. The message or operator reply preceding this message
was the last message recorded.
System Action: System initialization continues.
Operator Response: None.
IEA2081
func FUNCTION INOPERATIVE
Explanation: The nucleus initialization program (NIP) has
detected unrecoverable error conditions during initialization of
function func. As a result, the function has been made
inoperative.
This message is issued in conjunction with a diagnostic
message identifying the specifiC type of error.
System Action: The nucleus initialization program continues
processing.
Operator Response: Report this message to the programmer.
Section 5: lEA Messages - Supervisor
5-5
•
Programmer Response: Probable user error. Respond to the
diagnostic message issued in· conjunction with this message.
IEA2111
OBTAIN FAILED FOR dsn DATA SET
Explanation: The nucleus initialization program (NIP) was
unable to find the data set control block (DSCB) for data set
dsn for one of the following reasons:
• The volume containing the data set was not mounted.
• The data set control block was not in the volume table of
contents (VTOC).
• A permanent input/output error occurred.
System Action: The nucleus initialization program continues
processing.
Operator Response: If the volume that contains the data set is
not mounted, mount it and restart the system. If the volume is
mounted, record the device number and notify the
programmer.
Programmer Response: Probable user error. List the VTOC of
the volume that is supposed to contain the data set. If the
data set is not on the volume, create it and have the system
restarted.
Problem Determination: Table I, items 2, 13, 25b, 29.
The data set may be relocated.
IEA212A
GETMAIN FAILED DURING INITIALIZATION
Explanation: The nucleus initialization program (NIP) issued a
GETMAIN request; however, more storage was requested than
was available.
System Action: The system is placed in a wait state with a
code of X'63'.
Operator Response: Probable user error. Report this message
to the system programmer.
Programmer Response: See the description of wait state code
X'63'.
Problem Determination: Table I, items 11, 29.
IEA3001
mem NOT FOUND IN dsn
Explanation: The nucleus initialization program (NIP) is unable
to find member mem in data set dsn.
System Action: If mem is a NIP module, the system is placed
in a disabled wait state. If not, processing continues.
Operator Response: Probable user error. Report this message
to the system programmer.
Programmer Response: Make sure that mem is included in the
data set.
Problem Determination: Table I, items 2, 11, 29.
5-6
IEA303W
ABEND cde DURING SUPERVISOR INITIALIZATION
Explanation: Abnormal termination (ABEND) was requested by
a system function during nucleus initialization. In the message
text, cde is the system completion code.
System Action: The system is placed in a disabled wait state.
Operator Response: Re-IPL the system and report this
message to the system programmer.
Problem Determination: Table I, item 29.
IEA304W
SYSTEM WAIT STATE - CODE cde
Explanation: The nucleus initialization program (NIP) has
encountered an error which requires that the system
initialization process be discontinued. The reason for
terminating the normal IPL sequence is described by cde,
which is the address portion of the wait state PSW. The first 4
digits of cde are an identifier (if non-zero) which is unique to
the wait state code which is in the last 4 digits of cde.
System Action: The system enters a wait state.
Operator Response: Notify the system programmer of this wait
state code.
IEA305A
INVALID REPLY FORMAT - RESPECIFY
Explanation: During nucleus initialization, the last reply entered
through the console was not in correct format.
System Action: The system ignores the reply just entered and
waits for the reply to be respecified.
Operator Response: Probable user error. Enter the reply
correctly and make sure it is not greater than 80 characters in
length.
I/O ERROR DURING BLDL FOR mem IN dsn
Explanation: An uncorrectable input/output error prevents the
nucleus initialization program (NIP) from reading the directory
entry for member mem from data set dsn into virtual storage.
System Action: If mem is a NIP module, the system is placed
in a disabled wait state. If not, processing continues.
Operator Response: Probable hardware error. Record the
address of the device on which the input! output error
occurred and have it available.
Problem Determination: Table I, items 2, 30.
IEA3011
TOO CLOCK INOPERATIVE
Explanation: NIP found that the time-of-day (TOO) clock is not
working. In an MP environment, this message means that TOO
clocks on all CPUs were found to be inoperative.
System Action: The initialization process continues since the
timer initialization routines, which are invoked during master
scheduler initialization after NIP processing is complete, may
be able to correct the problem. NIP processing may be slightly
degraded if many teleprocessing control units or shared DASD
devices are in the configuration and require initialization.
Programmer Response: If timer initialization cannot correct the
problem during its processing after NIP has completed,
additional messages and information will be provided that may
require hardware support to be provided.
Problem Determination: Table I, item 30.
0, xxx OR yyy
Explanation: During nucleus initialization, direct access devices
xxx and yyy were found to have duplicate volume labels.
System Action: Nucleus initialization is suspended until one of
the identified volumes is demounted.
Operator Response: Demount the volume that is not needed. If
the volume to be demounted is a permanently resident device,
such as a drum, start the system again.
IEA2161
IEA3021
VS2 System Messages (VS2 Release 3.7)
IEA3061
adr, I/O ERROR, cm, stat, sens, ser
Explanation: The nucleus initialization program (NIP) issued an
I/O request to the device at the unit address adr. In the
message text:
• cm is the I/O command which resulted in an unsuccessful
I/O completion.
• stat is the CSW status bytes.
• sens is the first two bytes of sense data.
• ser is the volume serial number of a direct access device
involved.
The I/O request included a command which resulted in an
unsuccessful I/O completion. The CSW status bytes and the
first two bytes of sense data are included as a diagnostic aid
and may be used to determine the cause of the I/O failure.
The sense data appears only for errors involving a unit check
status; the volume serial number appears only for direct
access devices.
System Action: If the I/O request is critical to the system
initialization process, the system will issue message IEA304W
and enter a disabled wait state. Otherwise, processing
continues.
Operator Response: Probable hardware error. Restart the
system. Depending on the severity of the error (check the
status· and sense information) and the installation
requirements, take appropriate action.
Problem Determination: Table I, items 2, 30.
IEA310A
3. If the volume to be mounted is for a required data set and
the volume on device ddd is permanently resident, the
system enters a wait state with a code of X'39'.
Operator Response: In case 1, respond as indicated to
message IEA315A. In case 2, respond as indicated to message
IEA317A; use the cancel option of IEA317A if processing must
continue. In case 3, respond as indicated to wait state code
X'39'.
INVALID REPLY - RESPECIFY
Explanation: During nucleus initialization, the last reply entered
IEA315A
through the console did not contain the information requested
by the system.
System Action: The system ignored the reply just entered and
waits for the reply to be respecified.
Operator Response: Probable user error. Enter the reply again,
correctly.
Explanation: The nucleus initialization program (NIP) requires
IEA3111
UNLABELED DASD ON ddd
Explanation: The direct access device mounted on device ddd
is not formatted correctly.
System Action: The system marks device ddd offline and
issues message IEA3121 to inform the operator that it has
done so.
Operator Response: Probable user error. If this message is
unexpected for the volume on device ddd, report the message
to the system programmer.
Programmer Response: Make sure that the volume mounted
on device ddd has been properly initialized by either the
IBCDASDI program or the IEHDASDR program.
IEA3l21
ddd OFFLINE
Explanation: The nucleus initialization program (NIP) has
placed device ddd offline for the reason indicated in message
IEA31l1.
System Action: The system continues processing without
device ddd.
Operator Response: None.
Programmer Response: Respond as indicated to message
IEA3111.
IEA3l31
DEVICE ddd DISMOUNTED
Explanation: During nucleus initialization, device ddd was
demounted in response to message IEA212A.
System Action: The nucleus initialization program (NIP)
continues processing.
Operator Response: Make sure that device ddd is the device
that you intended to demount. If ddd is not the correct device,
do one of the following:
• Restart the system with the correct device in ready status.
• If the device is not required during system initialization, wait
for system initialization to complete and then enter a VARY
command to establish the desired volume status.
IEA3141
CONFLICTING VOLUME ON ddd
Explanation: The nucleus initialization program (NIP) detected
an invalid speCification while attempting to mount a volume.
ddd identifies the device which contains the correct volume
label but which is an unacceptable unit type.
System Action: One of the following occurs:
1. If the volume on device ddd is not permanently resident,
the system marks ddd not ready and prompts the operator
with message IEA315A to mount the proper volume.
2. If the volume on device ddd is permanently resident but the
volume to be mounted is for an optional data set, the
system prompts the operator with message IEA317A to
respecify.
M ddd,[NL], dsn
that either an unlabeled tape (for the SYS1.DUMP data set) or
the volume containing data set dsn, be mounted on device
ddd.
System Action: The system waits for a volume to be mounted
on device ddd.
Operator Response: Mount either the direct access volume
containing data set dsn or an unlabeled scratch tape, as
directed.
IEA316A
D ddd[.ser]
Explanation: The nucleus initialization program (NIP)
determined that the volume whose serial number is ser was
mounted on device ddd rather than on the device requested. If
ddd is a tape unit, the volume may be mounted on the correct
device, but the volume is. write-protected or contains a
standard IBM tape label.
System Action: The system issues message IEA315A to inform
the operator which volume was expected.
Operator Response: Probable user error. Demount volume ser.
Make sure that the proper volume is mounted on device ddd
and that the volume has been initialized with the proper
volume serial number.
IEA317A
SPECIFY UNIT FOR dsn ON ser [OR CANCEL]
Explanation: The nucleus initialization program (NIP) needs a
data set that does not reside on a previously mounted volume.
This message requests the operator to select a device on
which to mount the volume containing the data set. If the
message text contains 'OR CANCEL', the operator may choose
not to mount the VOlume."
System Action: The system waits for the operator to reply.
Operator Response: Select an available device of the type
required and respond r xx, 'ddd', where ddd is the unit address
of that device. If the option 'OR CANCEL' is included in the
message text, you may respond by signalling EOB; this
indicates that the volume is not available and is not to be used
for this IPl.
IEA3l81
UNIT UNACCEPTABLE
Explanation: The nucleus initialization program (NIP) found
that the unit specified in the reply to message IEA317A was an
unacceptable device type for the data set volume to be
mounted, or contained a volume which could not be
demounted.
System Action: The system rejects the earlier specification
and reissues message IEA317A.
Operator Response: Probable user error. Respond to message
IEA317A with the specification for an alternate unit.
Programmer Response: Make sure that the unit specified is the
proper device type for the volume to be mounted, does not
contain a required system data set, and is, in fact,
demountable.
Section 5: lEA Messages - Supervisor
5-7
41
IEA3191
dsn NOT FOUND ON ser
IEA322A
INVALID prm PARM - RESPECIFY OR CANCEL
Explanation: The nucleus initialization prog,ram (NIP) could not
Explanation: One of the system parameters designated by prm
find data set dsn on the volume which has the volume serial
number ser. The dataset control block is not found in the
volume table of contents (VTOC)..
System Action: If data set dsn is SYSl.LOGREC, SYS1.SVCLlB,
SYS1.PARMLlB, or SYS1.L1NKLlB, the system is placed in a
disabled wait state; otherwise, processing continues.
Operator Response: Probable user error. Report this message
to the system· programmer.
Programmer Response: List the table 9f contents of the
volume that is supposed to contain the data set. If the data
set is not on the. volume, create the data set and have the
system restarted.
Problem Determination: Table I, items 2, 11, 25, 29.
in the message text i.s invalid. For slist of valid system
parameters, refer tothe System Initialization and Tuning GUide,
GC28-0681.
System Action: The system ignores the parameter in error,
and waits for the operator to reply.
Operator Response: Probable user error. Respecify the
parameter correctly (as described in the System Initialization
and Tuning Guide, GC28-068l) or signal EOB to cancel the
use of the parameter for this IPL.
IEA320A
RESPECIFY PARAMETERS OR CANCEL
Explanation: During nucleus initialization, one of the following
contained an invalid parameter:
• The operator's response to message IEAl01A.
• The syste'm parameters defined by an active IEASYSxx list
in SYS1.PARMLIB.
This message may be preceded by an explanatory message.
System Action: The system accepts all parameters specified
before the parameter in error. The system waits for the
operator to enter the respecification or cancellation.
Operator Response: Probable user error. Enter the 'reply again
correctly. Enter a reply specifying only the corrected parameter
and the parameters,that were not accepted (that is, those
parameters following the invalid parameter in the last reply), or
cancel further input by signalling EOB. In this case, the
parameters accepted by the system remain in effect. Any
parameter may be respecified in this response.
Problem Determination: Table I, items 2, 29.
IEA3211
INVALID PARAMETER SYNTAX -prm - text
Explanation: Parameter prm is invalid. The reason for the
invalid specification is described in text:
text
Meaning
INVALID OPI KEYWORD The OPI parameter is· specified
incorrectly in an IEASYSxx member of
SYS1.PARMLIB. OPI must be either
OPI = YES or OPI = NO.
IMPROPER DELIMITER
The parameter prm is followed by an
invalid delimiter. Parameters must be
separated by a comma or a blank.
UNBALANCED PARENS The parameter prm included an
unequal number of right or left
parentheses.
INVALID CONTINUATION The parameter prm included
continuation across more than two
successive lines of text. A parameter
may be continued to only one
additional line of text.
UNDEFINED KEYWORD The parameter prm is invalid for
IEAl01A under OS/VS2.
System Action: The system issues message IEA320A,
IEA332A, or IEA906A and waits for the operator to reply.
Operator Response: Probable user error. Respecify the
parameter correctly or report the problem to the system
programmer.
Programmer Response: Specify the parameter correctly.
Problem Determination: Table I, items 2, 11, 29.
5-8
VS2 System Messages (VS2 Release 3.7)
IEA3231
OPIINVALID IN mem
Explanation: The nucleus initialization program (NIP) found an
invalid OPI parameter in the IEASYSxx member of
SYS1.PARMLIB identified by memo The OPI parameter must be
specified as either OPI = YES or OPI = NO.
System Action: The system terminates the input from member
mem, and issues message IEA3241. It then prompts the
operator for respecification of the SYSP parameter by issuing
message IEA320A.
Operator Response: Probable user error. The SYSP parameter
must be respecified or cancelled. In either case, parameters
interpreted up to the point of the error remain in effect.
Programmer Response: Ensure that the SYSP list of system
parameters is specified correctly.
IEA3241
SYSP INPUT TERMINATED IN mem
Explanation: The input from IEASYSxx member mem has been
terminated because of an error. This message is preceded by
another message explaining the error.
System Action: The system issues message IEA320A which
offers the opportunity to respecify the parameter input which
was truncated in member memo Parameters specified before
the error remain in effect.
Operator Response: Probable user error. Report this message
to the system programmer.
Programmer Response: Correct the conditions reported by the
preceding message.
Problem Determination: Table I, items 2, 11, 29.
IEA3251
IEASYSxx PARAMETER LIST
Explanation: The operator requested a listing of the SYSP list
of parameters when responding to message IEA101A. This
message is the header for the listing of the IEASYSxx member
of SYS1.PARMLIB.
System Action: The system lists the parameters and continues
processing.
Operator Response: None.
IEA3261
LOCATE FAILED FOR dsn
Explanation: The data set dsn could not be found in the
system catalog. Valid values for dsn are SYS1.DUMP,
SYS1.LlNKLlB, SYS1.LPALlB, and SYS1.DSSVM.
System Action: If dsn is SYS1.L1NKLlB, the system enters the
wait state (wait code X'OA'); otherwise, the system provides
additional diagnostic information ;;Ind options by issuing
message IEA3541, IEA35ll, IEA355A, or IEA2081.
Operator Re.sponse:Probable user error. Report this message
to the system programmer along with any associated messages
and wait state codes.
Programmer Response: Use the associated messages to
determine the· action to be taken.
YS2.03.807
IEA3271
LINK LIBRARY DATA SETS NOT FOUND
dsn
dsn
Explanation: The nucleus initialization program (NIP) could not
find or process the link library data sets identified by dsn
because of one of the following:
1. The operator canceled a define-unit request.
2. An I/O error occurred when opening the data set.
3. The system could not find the data set on the volume
indicated by the system catalog.
4. The system could not find a catalog entry for the data set. .
5. More data sets remained to be processed after 15 active
concatenations were created to the LINK library. (15
concatenations is the system limit.)
The first three conditions would have been reported by
previous messages; IEA317A, IEA2111, IEA3191, respectively.
System Action: The system lists th.e data sets that could not
be concatenated to SYS1.LlNKLIB and processing continues.
Operator Response: Report this message to the system
programmer.
Programmer Response: Probable user error. Correct the
condition that caused the error:
1. No action is required.
2. If the error is permanent, attempt to recreate the data set.
3. Make sure that the data set exists on the volume to which
the system catalog points.
4. Catalog the data set.
5. Re-order the data set names so that the 15 data sets that
you want concatenated come first in the list, or put the data
set names in a separate LNKLSTxx list and respond to
message IEAI0IA with the LNK = xx system parameter to
specify the list.
Problem Determination: Table I, items 11, 25c to list
LNKLSTxx members, 29.
IEA3281
LNKLSTxx INPUT TRUNCATED AT dsn
Explanation: The maximum number of data set names that can
be defined in the selected LNKLSTxx members has been
exceeded. The system will' process the first 40 data set names.
In selecting those that may be concatenated to SYS1.LlNKLlB;
the remaining data set names, beginning with dsn, have been
ignored.
System Action: Processing continues.
Operator Response: Report this message to the system
programmer.
Programmer Response: Probable user error. Make sure that
the total number of data set names does not exceed 40 when
defining the possible combinations of LNKLSTxx members that
might be selected during IPL.
Problem Determination: Table I, items 11, 25a to list the
LNKLSTxx members, 29.
IEA330A
CONTINUE prm PARM
Explanation: The operator requested that the parameter
specification be continued. This message permits him to
continue entering information related. to parameter prm.
System Action: The system waits for the operator to reply.
Operator Response: Continue entering parameter prm.
IEA332A
SPECIFY prm [OR CANCEL]
Explanation: The nucleus initialization program (NIP) has
detected the omission of the function defined by parameter
prm in the. system definition. If the function is not optional, the
cancel option is omitted from the message text.
System Action: The system waits for the operator to reply.
Operator Response: Reply in the format specified for message
IEAI0IA as requested by the systems programmer. If CANCEL
is a reply option, you may signal EOB to bypass the
specification of the function prm.
IEA3401
REAL OR VIRTUAL STORAGE NOT AVAILABLE FOR
func
Explanation: The nucleus initialization program (NIP) could not
obtain storage for the function indicated by func· in the
message text.
System Action: If func is not a necessary system function, the
system will continue processing. If, however, func is a
necessary system function, the system enters a disabled wait
state (X'3B').
Functions and system actions are as follows:
func
System Action
PFT
Wait state X'3B'
BLDL/BLDLF Respecification offered by prompt message
MLPA
Message IEA3531 issued - prm INPUT
TERMINATED
FIX
Message IEA3531 issued - prm INPUT
TERMINATED
ASM
Wait state X'3B'
Note: PFT and ASM are not system parameters.
Programmer Response: Probable user error. Make sure that
sufficient storage is available for NIP processing.
Problem Determination: Table I, items 11, 29.
IEA3441
QUICK START FAILED; COLD START INITIATED
Explanation: The CLPA parameter was not specified, and the
paging space did not contain a reusable link pack area. This
could be a normal situation, if this is the first IPL after a new
SYS1.STGINDEX data set and new paging data sets have been
presented to the system. Messages issued previously during
the initialization of the paging space, if any, may give
additional information pertaining to the LPA.
System Action: The system initiates a cold start for the link
pack area.
Operator Response: None.
IEA3501
mem MODULE LIST
Explanation: This is a header message for the library listing
requested by the operator. The modules specified in the
SYSl.PARMLIB member mem are printed following this
message.
System Action: The system prints the list and processing
continues.
Operator Response: None.
IEA3511
dsn REQUIRED FOR mem
Explanation: The nucleus initialization program (NIP) cannot
find the data set dsn. The data set is required for member
mem in the SYS1.PARMLIB.
System Action: Processing continues.
Operator Response: Probable user error. Report the problem
to the system programmer and reply in the format specified
for message lEA 10 1A as requested by the system
programmer, or cancel the job.
Programmer Response: Correct the error.
Problem Determination: Table I, items 2, 25a, 26c for
SYS1.PARMLlB, and 29.
IEA3521
LiSt mem FOR prm INVALID text
Explanation: The SYS1.PARMLIB member mem, which was
defined for parameter prm, is invalid. text identifies the reason
for the invalid specification:
Section 5: 1EA Messages· Supervisor
6-8
VS2.03.807
text
MODNAME mod
Meaning
mod' identifies the name of the invalid
module specified ..
INCO'RRECT LlBNAME The PARMLIB list did not properly
FORMAT
define a module source library.
EXCEED MAX BLDL
The PARMLIB list contained too many
ENTRIEST
module names; BLDL has more than
X'7FFF' names.
INCORRECT VOLID
The PARMLIB list contained volid's that
were specified in the wrong format, or
FIELD
possibly not specified at all.
System Action: The system prompts the operator for
parameter respecification or cancelation.
Operator Response: Probable user error. Respond to the
prompt message and report this message to the system
programmer.
Problem Determination: Table I, items 2, 11, 25c, 29.
IEA3531
prm INPUT TERMINATED AT mod
Explanation: The definition of the parameter prm failed for
lack of storage as indicated by the preceding message. mod
identifies the module which was to be loaded when the error
was detected. If prm is CLPA, an LPA cold start has failed.
System Action: Processing continues. Modules specified before
mod are added to the LPA. If prm is CLPA, the system will be
placed in a X'3A' wait state.
Operator Response: Probable user error. Report this message
to the system programmer.
Programmer Response: Make sure that there is adequate
storage for the prm function bei"g attempted. Respond as
indicated for the wait state code if it occurs.
Problem Determination: Table I, items 2, 11, 29.
IEA3541
CLPA FAILED - text
Explanation: The system link pack area (LPA) could not be
created; text indicates the reason:
text
Meaning
LPALIB UNAVAILABLE The SYSl.LPALIB data set is not
defined in the catalog or the data set
could not be opened. The reason for
the failure is given in the previous
message.
LPALIB EMPTY
The SYSl.LPALIB data set did not
contain any load modules.
STORAGE UNAVAILABLE There is not enough virtual storage to
contain all the modules in
SYSl.LPALIB. The number of modules
in SYS1.LPALIB must be reduced if
cold start is to be successful.
I/O ERROR
An I/O error occurred when the
nucleus initialization program (NIP)
attempted to read a record from the
SYSl.LPALIB directory.
PGOUT ERROR
An error occurred during execution of
the PGOUT macro instruction in an
attempt to page out the LPA area.
PGFIX
An error occurred during the
PGFIX/PGFREE macro instruction in
an attempt to page fix/free the
temporary directory.
NON-EXECUTABLE
Non-executable modules were found
MODS
on SYSl.LPALIB.
System Action: The system follows this message with disabled
wait state code X'3A'. If any modules were successfully loaded
into the LPA, message IEA3531 follows this message.
Operator Response: Probable user error. Report this message
to the system programmer.
Problem Determination: Table I, items 2, 11, 29.
I
&-10
VS2 System Messages (VS2.03.807)
IEA355A RESPECIFY prm OR CANCEL
Explanation: The nucleus initialization program (NIP) has
detected an error in the specification of the prm parameter.
System Action: The system waits for the operator to reply.
Operator Response: Reply in the format specified for message
IEAlOlA, as requested by the system programmer.
Programmer Response: Make sure that the correct format was
given to the operator.
lEA3561
ALIAS allasname OF MODULE mod IGNORED
Explanation: The entry for aliasname in the directory of
SYSl.LPALIB specifies that it is the alias of mod, which is not
in the directory for SYSl.LPALIB.
System Action: This message follows message IEA30l1
(specifying mod). The entry for aliasname will be ignored
during the IPL LPA loading process. The module is not loaded
into the link pack area.
Operator Response: None.
IEA3571
LIST
{IEALODOO}
IEAPAKOO
error-descrlptlon-system-actlon
ERRORS IN
Explanation: One or more errors were detected in proc'essing
the LPA load list (IEALODOO) or the lPA packing list
(IEAPAKOO) during IPL. The error descriptions and their
meanings are:
• DELIMITER FOLLOWING mod INVALID - The left parenthesis
starting a group of module names is missing, or the right
parenthesis following a group of module names is missing,
or a blank is not preceded by a left parenthesis or a
comma. mod is the name of the last valid module found in
the list preceding the error. ·"START is substituted for
modname if no valid names precede the erroneous delimiter
in the list.
• NAME FOLLOWING mod IMPROPER - The name of a
module in the list has more than eight characters. mod is
The name of the last valid module found in the list
,preceding the invalid name. ···START is substituted for
mod name if no valid names precede the erroneous name.
• mod INVALID - The named module is not specified in the
directory of SYSl.LPALlB, is the name of an alias (not a
module), or was specified more than once in the LPA
packing list.
• I/O ERROR FOLLOWING mod - An I/O error occurred while
reading the list. mod is the last valid module name
processed preceding the detection of the I/O error.
• mod NOT FOUND IN LPA - Module mod was specified on
the IEALODOO member, but was not found on the active
LPA queue and had no LPA directory entry. The module is
not loaded.
System Action: The system actions and their meanings are:
• MODULE IGNORED - The specified module name is ignored
and processing of the list continues.
• GROUP TERMINATED - The list is scanned from the point of
th~ error until the next right parenthesis is found,
terminating the group. The modules specified within the
group prior to the error are processed as the sole contents
of the groUJ).-Processing continues at the start of the next
group.
• GROUP IGNORED - The list is scanned from the point of the
error until the next left parenthesis is found, starting the
next valid group. All names. scanned over are ignored.
• LIST TERMINATED - For IEALODOO, the modules specified
within the list prior to the error were 'processed as the sole
content of the list. The system continues processing as if
the end of the list had been reached normally. For
IEAPAKOO, the group being processed is terminated. The
'~
VS2.03.807
modules specified within the group prior to the error are
processed as the sole contents of the group. This is the last
group of modules loaded as a packed unit. The system
continues processing as if the end of the LPA packing list
had' been reached normally.
Operator Response: None.
IEA3581
SYSl.LPALIB MODULE mod NON-EXECUTABLE
Explanation: Module mod on SYS1.LPALIB is marked
non-executable and cannot be loaded into the system link
pack area.
System Action: Processing continues in order to detect any
additional modules which might be non-executable. Message
IEA3541 will follow the last message IEA35SI.
Operator Response: Probable user error. Report this message
to the system programmer.
Programmer Response: Replace the non-executable modules
on SYS1.LPALIB with executable versions.
Problem Determination: Table I, item 2.
IEA3631
mod NOT FOUND IN LPA [;CONSOLE ddd
UNUSABLE]
Explanation: The nucleus initialization program (NIP) could not
find module mod in the link pack area. CONSOLE ddd
UNUSABLE appears when module mod provides functions
needed for console ddd, and, as a result, ddd may not be used
as an active console.
System Action: Except when module mod provides console
functions or when special NIP processing is being performed,
the system indicates which function was made inoperative by
issuing message IEA20SI, and then it continues processing. If
the system cannot continue without module mod, the system
enters the wait state code X'3B'.
Operator Response: Probable user error. Report the problem
to the system programmer.
Programmer Response: Make sure that the missing routine is
included in the LPA. The module must be added to
SYS1.LPALIB if a cold start is used. The module must be
defined in the SYS1.PARMLIB list referenced by the MLPA or
FIX option if. either of these options is used.
Problem Determination: Table I, items 2, 11, 29.
IEA604A
D ddd,ser
Explanation: The operator replaced a required direct access
volume without having received a mount request.
In the message text, 0 indicates that the volume whose serial
number is ser is to be demounted from the device whose unit
address is ddd, in hexadecimal.
Operator Response: Demount the volume. Then respond as
indicated for message IEA605A, which follows this message.
IEA605A
M ddd,ser,,[jjj]
Explanation: M indicates that the volume whose serial number
is ser is to be mounted on the device whose unit address in
hexadecimal is ddd.
Message IEA604A or IEA6061 precedes this message,
indicating the reason for the mount request. In the message
text, jjj is the name of the job in control during which
intervention is required. If the job name cannot be determined,
this field is left blank.
Operator Response: If the volume requested is not available,
cancel the job. Otherwise, mount the indicated volume. (If
message IEA6061 precedes this message, the volume .indicated
in that message must first be demounted from the device.)
IEA6061
ddd,BAD VOLUME LABEL,cm,stat,senbbbbbb"
ser,[JJJ]
Explanation: A permanent input/output error occurred while
trying to read the volume serial number of the indicated
volume.
In the message text, in hexadecimal, the fields are:
ddd
Unit address of the device.
cm
Operation code of the channel command word (CCW) during
whose execl:ltion the error occurred. If the channel
command word cannot be found, this field appears as ••.
stat
Status portion of the channel status word (CSW).
sens
First 2 sense bytes for the error condition.
bbbbbb
Next 3 sense bytes for the error condition. This field
appears only for devices that give more than 2 bytes of
sense information.
ser
Serial number of the volume on which intervention is
required.
jjj
The name of the job in control when intervention is
required. If the jobname cannot be determined, this field is
left blank.
Operator Response: Respond as indicated for message
IEA605A, which follows this message.
IEA7001
cde[ -rc]
jjj } sss ff [dddddddd]
{ aaa
Exp/anati~n: The control program detected an error during the
execution of a GETMAIN or FREEMAIN macro instruction. The
job step was abnormally terminated with a system completion
code of cde. This message provides additional information on
the error.
In the message text, the fields are:
cde
System completion code.
rc
Reason code. Included only when there are multiple reasons
for issuing the message.
jjj
job name
sss
step name
ff
Flag byte. A '00' indicates that the GETMAIN or FREEMAIN
macro instruction was entered via an SVC instruction. An
'SO' indicates that GETMAIN or FREEMAIN was entered via
a branch and that job jjj has been replaced by branch
address aaa.
aaa
Return address of the calling routine from register 14 if the
entry to GETMAIN or FREEMAIN was not via an SVC
instruction.
dddddddd
Variable data in hexadecimal. Data is 1 to 3 complete words
in length.
The length and meaning of the hexadecimal data dddddddd is
dependent on system completion code cde and reason code rc
given in the message text. The meanings of the applicable
reason codes are as follows:
Section 5: I EA Messages· Supervisor
5-11
cde rc Meaning
305 1 Specified virtual storage area was not in named
subpool.
305 2 Specified subpool could not be found.
30A 1 Specified virtual storage area was not in named
subpool.
30A 2 Specified sub pool could not be found.
30A 4 Zero length was not specified for subpool FREEMAIN.
378 1 Specified virtual storage area was not in named
subpool.
5~11.0
VS2 System Messages (VS2.03.807)
378 2 Specified subpool could not be found.
378 4 Zero length was not specified for subpool FREEMAIN.
40A
Subpool FREEMAIN for SQA, CSA, subpools 254 or
255, or invalid subpool; or problem program freeing
subpoolO.
~\
Section 6: IEA Messages· Supervisor
6-11.1
Subpool FREEMAIN for SQA, CSA, subpools 2S4 or
2SS, or invalid subpool, or problem program freeing
subpoolO.
Length and address lists overlap.
S04
Length and address lists overlap.
SOS
604 1 Parameter list for the GETMAIN macro instruction
contained an invalid address, or the address of the
parameter list was invalid.
60S 1 Parameter list for the FREEMAIN macro instruction
contained an invalid address, or the address of the
parameter list is invalid.
804 1 Requested amount of virtual storage was not available.
804 2 A negative length was specified.
80A 1 Requested amount of virtual storage was not available.
878 1 Requested amount of virtual storage was not available.
878 2 A negative length was specified.
90S
Address not multiple of 8.
90A
Address not multiple of 8.
978
Address not multiple of 8.
AOS 1 The area being freed overlaps an area that is already
free.
AOS 2 Part of the area being freed is still fixed in real
storage.
AOA 1 The area being freed overlaps an area that is already
free.
AOA 2 Part of the area being freed is still fixed in real
storage.
A78 1 The area being freed overlaps an area that is already
free.
A78 2 Part of the area being freed is still fixed in real
storage.
B04
Problem program requests subpool 128 to 2SS or
authorized program requests invalid subpool.
B05
Problem program requests subpool 128 to 2SS or
authorized program requests invalid subpool.
BOA
Problem program requests subpool 128 to 2SS or
authorized program requests invalid subpool.
B78
Problem program requests subpool 128 to 2SS or
authorized program requests invalid subpool.
DOS
No AQE when there should be one (LSQA not owned
by requesting task).
DOA
No AQE when there should be one (LSQA not owned
by requesting task).
078
No AQE when there should be one (LSQA not owned
by requesting task).
The meaning of the variable data is:
cde rc word 1 word 2 word 3
30S 1 x2
xS
x6
30S 2 x2
xS
x6
30A 1 x2
xS
x6
30A 2 x2
xS
x6
30A 4 x2
xS
x6
40A
x2
xS
378 1 x2
xS
x6
378 2 x2
xS
x6
378 4 x2
xS
x6
40A
x2
xS
478
x2
xS
504
xl
50S
xl
604 1 xl
60S 1 xl
804 1 x2
x3
804 2 x2
x4
80A 1 x2
x3
878 1 x2
x3
878 2 x2
x4
90S
x2
xS
x6
478
5·12
VS2 System Messages (VS2.03.807)
x2
xS
90A
978
x2
xS
AOS 1 x2
x7
xS
x6
xS
AOS 2 x2
AOA 1 x2
x7
xS
AOA 2 x2
x6
xS
A78 1 x2
x7
xS
A78 1 x2
x6
xS
x2
804
x2
80S
xS
x2
80A
878
x2
DOS
x2
x6
xS
DOA
x2
x6
xS
078
x2
x6
xS
where:
x1- Address of the GETMAIN or FREEMAIN parameter list.
The first word of the parameter list is the address of the
length list specified in the LA operand; the second word
is the address of the address list specified in the A
operand.
x2- The first byte is the number of the subpool for which the
request was made; the last three bytes are the number
of bytes requested.
x3- Number of bytes in the largest available block of virtual
storage in your region.
x4- Full length as specified.
xS- Beginning address of the virtual storage area to be freed.
x6- Address of the task control block (TCB) for the
abnormally terminating task.
x7 - Number of bytes of overlap into free area.
Programmer Response: Refer to the explanation of completion
code cde in the VS2 System Codes publication GC38-1008 for
the complete response to this message.
IEA7031
cde[ -rc] jjj sss MODULE ACCESSED mod
Explanation: During execution of a LINK, LOAD, ATTACH, or
XCTL macro instruction, the control program encountered an
error while loading module mod. The system completion code
is cde. This message provides additional information on the
error.
In the message text, the fields are:
cde
system completion code
rc
reason code. Included only when there are multiple reasons
for issuing the message.
jjj
job name
sss
step name
mod
the name of the module being accessed at the time of the
error.
This message is issued for the following completion codes:
cde rc
Explanation of reason Code
106 B
FETCH's FRR unexpectedly received control
Not enough core for FETCH to do GETMAIN
106 C
106 0
Invalid record type in load module
Invalid address in load module
106 E
106 F
Uncorrectable input/output error
306 4
Program not found in indicated authorized library
306 8
Uncorrectable I/O error
306 C
Authorized user requested a module which could
not be found on an authorized library, but a module
with the same name was found on an unauthorized
library.
406
706
LINK, ATIACH, or XCR TO LOAD ONLY MODULE
Load module marked by linkage editor as 'not
executable'
806 4
Specified entry point not found
806 8
Uncorrectable input/output error
806 C
SVC routine not in LPA
906
Maximum use count exceeded
A06
Serial reusable load module already queued for
prior request
Programmer Response: Refer to the explanation of completion
code cde in the OS/VS Message Library: VS2 System Codes,
GC38-1008 for the complete response to this message.
IEA800A
cde COMMUNICATION TASK ABEND, [NO] DUMP
TAKEN
Explanation: This message informs the system operator that
Commtask has abnormally terminated and a dump was or was
not taken. cde is the ABEND completion code.
System Action: This message is also recorded on the
SYSl.LOGREC data set to aid in problem determination.
Operator Response: None.
UNIDENTIFIED TASK
1EA8011
'Il.,
{
} {JS}
ST FAILED WHILE IN
MUST COMPLETE STATUS
jjj 555
Explanation: Either the job step task (JS) or a subtask (ST)
associated with the job name (jjj) and the step name (sss)
failed while operating in step must complete status. If the job
name or step name is unavailable, UNIDENTIFIED TASK
replaces jjj sss.
System Action: Exclusive systems enqueued resources follow
this message. The 'must complete' status is reset.
Operator Response: Notify the system programmer that a
'must complete' task has failed.
Problem Determination: Table I, items 2, Sa, 15, 16, 29.
j
IEA8031
{~~} FAILED WHILE IN 'STEP MUST COMPLETE'
The job step was abnormally terminated with a system
completion code of 206. This message provides additional
information on the error.
In the message text, the fields are:
rc
reason code
jjj
job name
sss
step name
ff
always 0
dddddddd
address of LINK or XCTL parameter list in hexadecimal.
Always 0 for LOAD or DELETE macro instructions.
[dddddddd]
variable data in hexadecimal. Data is 1 to 2 complete words
in length.
The meaning of hexadecimal data [dddddddd] is dependent on
the reason code rc given in the message. The meanings of the
applicable reason codes are:
rc Meaning
1 LINK or XCTL parameter list address invalid.
2 LINK, LOAD, XCTL, or DELETE address of EP/DE invalid.
3 LINK, LOAD, XCTL - DE supplied in parameter list too small
to describe the requested module, or DE supplied in
parameter list contained an invalid c-byte (user data field
length.)
•
The meanings of the variable length data are:
r Word 1 Word 2
1
2 Xl
3 Xl
X2
where:
Xl is the address of EP/DE
X2 is the expected length of DE or the invalid length (because
of Invalid c-byte)
Programmer Response: See the programmer response for
system completion code 206.
STATUS DUE TO
{Ucde}
Scde
Explanation: Either the job step task (JS) or a subtask (ST)
failed while operating in 'step must complete' status. The error
that caused the failure is represented by the system (Scde) or
the user (Ucde) completion code.
System Action: The operator is notified of this, along with
exclusive systems resources held. The 'must complete' status
is reset.
Programmer Response: Locate the task that failed while
operating in 'step must complete' status to determine the
cause of the failure. Correct the error and run the job again.
Problem Determination: Table I, items Sa, 15, 16, 29.
immediate termination while the system dump routine
(ABDUMP) was formatting the trace buffers in the GTF region.
System Action: Trace formatting is terminated and ABDUMP
continues its dump processing. The formatted trace output is
incomplete as it does not include the most current trace
entries.
Operator Response: Notify the system programmer and
proceed according to the response documented for the error
message or termination code that occurred upon termination
of GTF.
IEA8061
IEA8091
jjj.sss HAS BEEN TERMINATED DUE TO AN
UNCORRECTABLE I/O ERROR ON THE PAGE DATA
SET
Explanation: A task has been terminated due to an I/O error
(system completion code X'28'). In the message text, jjj
indicates the job name, and sss, the step name.
Operator Response: None. Repeated occurrences of this
message indicate that the page data set should be reallocated
and formatted at the next IPL.
Problem Determination: Table I, items 1, 2, Sa, 13, 16, 29.
IEA8071
206-rc jjj
555
ff dddddddd [dddddddd]
Explanation: The control program detected an error during the
execution of a LINK, LOAD, DELETE or XCTL macro instruction.
IEA8081
GTF TERMINATED DURING TRACE FORMATTING
Explanation: GTF encountered a severe error which caused
ERROR IN BUFFER REMAINDER OF BUFFER
IGNORED
Explanation: An invalid length field in the GTF trace buffers
was discovered.
System Action: Remainder of buffer is not formatted.
Programmer Response: None.
Problem Determination: Table I, items 4, 7a, 13, 29.
IEA810E
UNCORRECTABLE I/O ERROR ON LPA PAGE;
CREATE LPA ON NEXT IPL
Explanation: An uncorrectable I/O error occurred while
attempting to page in a warm start copy of a LPA page. Since
the external storage for this LPA page cannot be read, the
problem will recur on the next IPL unless a new LPA is
Section 5: lEA Messages - Supervisor
5-13
I
created.
System Action: The task for which paging of the LPA page
was being done will be abnormally terminated.
Operator Response: On the next IPL, create a new LPA via the
CLPA parameter when specification of system parameters is
requested.
IEA8501
FOLLOWING WILL BE PROCESSED
ser ON devtyp ccc-ccc
Explanation: This message lists all volume attribute list entries
that were encountered before the I/O error referred to in
message IEA949A.
ser ON devtyp ccc-ccc is written for each volume. ser is the
serial number of the volume, devtyp is the device type, and
ccc-ccc specifies the characteristics requested for the volume:
P/R-PUB Permanently resident, public
P/R .. PRV Permanently resident, private
P/R-STR Permanently resident, storage
RSV-PUB Reserved, public
RSV-PRV Reserved, private
RSV-STR Reserved, storage
System Action: Processing continues. Attributes will be set as
indicated unless overridden by subsequent entries.
Operator Response: None.
IEA85U---FOLLOWING MAY BE MOUNTED
ser ON devtyp
IEA851A REPLY DEVICE ADDRESSES OR U
Explanation: All volumes described in VATLSTxx, permanently
resident and reserved volume attribute list in SYSl.PARMLlB,
were not mounted at system start.
ser ON devtyp is written once for each unmounted volume. ser
is the serial number of a volume to be mounted and devtyp is
the type of device, such as 2314 or 3330, that the volume is
to be mounted on. devtyp does not specify any special
features, such as track overflow, that may be required; it is
the user's responsibility to select the device that has any
required special features.
System Action: The system waits for the operator to reply.
Operator Response: If any of the listed volumes are to be
mounted, enter REPLY xx, 'ddd,ddd,ddd, .. .' where each ddd is a
device address. Any valid direct access devices can be used,
including those that already have volumes mounted on them.
Mount the required volumes on the devices replied, after
message IEA860A appears.
If no volumes are to be mounted, enter REPLY xx, 'U'.
IEA8521
ddd ADDRESS INVALID - n
IEA852A REPEAT REPLY.
Explanation: The reply to message IEA851A is invalid.
Message IEA8521 is issued for each invalid device in the reply
and it is followed by message IEA852A. ddd identifies the
device in error and n identifies the cause of the error as
follows:
n Meaning
1 Duplicate device address.
2 Device address is unkhown to the system.
3 Device contains a permanently resident or reserved volume.
4 D~:vice is not direct access.
5 Device type is not needed to satisfy mount of the requested
volumes.
6 Program to check for data path to the offline device was
not in the system.
7 No data path available to the device.
8' No operational data path· to the device.
9 Device is for an exposure within a multiple exposure device,
but is not the base exposure.
10Device address for a non-demountable device that was
online at IPL.
11 Device address is for a 3850 Mass Storage System (MSS)
device.
System Action: The system waits for the operator to reply.
5-14
VS2 System Messages (VS2 Release 3.7)
Operator Response: Probable user error. Enter the reply again
correctly or enter REPLY xx, 'u' .
Problem Determination: Table I, items 2, 7a, 29. Make sure
that the device is defined to the system correctly.
IEA853A REPLY CONT, END OR RESPECIFY.
Explanation: While reading VATLSTxx, referred to in message
IEA949A, the system detected an uncorrectable input/output
error.
System Action: The system waits for the operator to reply.
Operator Response: If the system can continue without
VATLSTxx, enter REPLY xX,'CONT' or REPLY xx,'END' or REPLY
xx,'nn', where nn is a new VATLST number. If the reply is
CONT, the system will try to continue processing other
specified VATLST members. If the reply is END, no more
VATLST processing will be done. If the reply is nn, VATLSTnn
will be processed before processing the remaining VATLST
members.
Problem Determination: Table I, items 2, 7a, 11, 29.
ERROR READING VOLUME LABEL.
IEA8541
Explanation: The system cannot read the volume label on the
device whose address is specified in subsequent message
(either IEA9851 or IEA9481). If message IEA3061 precedes this
message, an input/ output error occurred when reading the
label. Otherwise the volume does not contain a standard label
or, in the case of Mass Storage System (MSS) volume, the
volume serial number on the label does not match the volume
serial number requested from the 3850 MSS. The later case
can occur when an MSS volume label has been clipped to a
different serial number.
System Action: On an MSS volume, the VATLSTxx entry is
ignored; processing continues with the remaining VATLSTxx
entries. For non-MSS volumes the system waits for the correct
volume to be physically mounted, as long as all device
addresses specified in reply to IEA851A have not yet had
volumes mounted on them. If they have, the system does not
wait; a mount request for the desired volume must be issued
later.
Operator Response: For MSS volumes, no response is
necessary. For non-MSS volumes, if the wrong volume is
mounted, remove it and mount the correct volume. If no
volume can be mounted (for example, there is an error on that
device), and the device is listed in IEA860A, reply 'NO' to
message IEA893A when all other required devices have been
mounted (that is, when the required devices are not listed on
IEA893A).
Problem Determination: Table I, items 2, 7a, 11, 29.
IEA8551
INVALID VATLSTxx ENTRY
Explanation: There is an invalid entry in VATLSTxx
(permanently resident and reserved volume attribute list).
System Action: Processing continues with the remaining
VATLSTxx entries.
Programmer Response: Using IEBPTPCH, print the VATLSTxx
member from SYSl.PARMLIB. Correct the invalid entry by use
of the IEBUPDTE utility.
IEA856W
ACR RECURSIVELY INVOKED BY CPU x
Explanation: An attempt was made to invoke ACR while
another ACR process was still active in the system. In the
message text x is the CPU address.
System Action: An attempt is made to record the LOGREC
buffer on SYSl.LOGREC for the indicated CPU, and all CPUs
are placed in a wait state.
Operator Response:· A probable hardware error exists on more
than one CPU. Take a stand alone dump, then the system
should be restarted and IFCEREPO should be scheduled for
execution.
Problem Determination: Table I, items 11, 18, 30.
\~
IEA857W
UNREC
ACR ERR-x-R
= nn
D = dd
Explanation: An unrecoverable error was encountered during
ACR processing. ACR has attempted recovery and was
unsuccessful. Recovery was being attempted by R for D. In the
message text, the fields are as follows:
x - CPU address.
ERR S - software error encountered
H - hardware error encountered
R - recovery CPU
D - dead CPU
x - code as follows:
1 - The failure occurred prior to entering post processing.
2 - The failure occurred during ACR post processing.
System Action: An attempt is made to record the LOGREC
buffer for the dead CPU in SYSl.LOGREC. All CPUs are placed
in a wait state.
Operator Response: If H is indicated, a probable hardware
error exists. If S is indicated, a probable software error exists.
Take a stand-alone dump, then restart the system and
schedule IFCEREPO for execution.
Problem Determination: If H is indicated, see Table I, items 11,
18, 30. If S is indicated, see Table I, items 11, 18, 29 or 30.
IEA8581
ACR COMPLETE, CPU x NOW OFFLINE
Explanation: ACR was invoked and has successfully placed a
failing CPU logically offline. In the message text x is the CPU
address.
System Action: Processing continues. This message is written
as a system action message to keep the message text from
rolling off a graphic console screen. This message must be
manually deleted by the operator using control (K) command.
Operator Response: Delete the message from console and
schedule the IFCEREPO program for execution.
Problem Determination: Table I, items 18, 30.
IEA8591
UNREQUESTED VOLUME. UNIT ddd NOW
UNLOADED.
Explanation: A volume was mounted on a unit specified by the
operator in response to message IEA851A for which no entry
exists in VATLSTxx.
System Action: The volume is unloaded.
Operator Response: Mount a volume requested in message
IEA851A on this unit. Reply 'u' to message IEA893A when the
device is ready. If no volume can be mounted on this unit,
reply 'NO' to message IEA893A when all other required
devices have been mounted, that is, when the required devices
are not listed in message IEA893A.
Problem Determination: Table I, items 2, 7a, 11, 29. Display
the label on the volume.
IEA860A
ddd,ddd, ...
REPLY U WHEN ALL DEVICES ARE READY.
Explanation: Volume attribute processing is waiting for the
volumes to be mounted on these devices.
System Action: The system waits for the operator to reply.
Operator Response: Mount volumes, as listed in message
IEA8511, on these devices. When the devices are raady, reply
'u' to this message.
IEA861A
VAL = nn NOT FOUND. REPLY U OR CORRECT
VALUE
Explanation: No volume attribute list (VATLST) with the suffix
nn exists in SYSl.PARMLIB.
System Action: The system waits for the operator to reply.
Operator Response: If an error was made in the reply to
message IEA101A, enter REPLY xx, 'nn' where nn is a correct
value. Enter REPLY xx, 'u' to ignore this volume attribute list
and continue processing any other specified lists.
Problem Determination: Table I, items 2, 7a, 11, 29. Use
IEBPTPCH to list the members of SYSl.PARMLIB.
IEA8621
RCT INITIALIZATION FAILED
Explanation: Th~ region control task was unable to initialize an
address space for a START, MOUNT, or LOGON request.
System Action: This address space is terminated due to an
error during initialization of the address space by the region
control task.
Programmer Response: None.
Problem Determination: Table I, items 7, 16, 18, 27, 29.
IEA8631
j TOO ~ SPECIFICATION IN COMMNDxx
ICOM~
Explanation: A TOD or COM parameter in the identified
SYSl.PARMLIB member was syntactically incorrect.
System Action: The parameter is ignored. Processing of the
COMMNDxx member continues.
Operator Response: Probable user error. Take appropriate
action as specified by the installation operating procedure and
report this message to the system programmer.
Programmer Response: List, check, and correct the syntax of
the parameters in the specified COMMNDxx member. Make
sure that the installation operating procedure tells the operator
what to do if invalid parameters are found in any COMMNDxx
members.
Problem Determination: Table I, items 2, 26c,29.
IEA8641
GETMAIN FAILED FOR COMMNDxx - (cm)
Explanation: A conditional GETMAIN for SQA core for the
specified command (cm) failed due to insufficient SQA space.
This command was one of the 'canned' commands
implemented by the system programmer.
System Action: Processing of the COMMNDxx members is
discontinued. No 'canned' commands will be issued. Message
IEA2081 func FUNCTION INOPERATIVE will follow this message.
Operator Response: Take the appropriate action as specified
by the installation operating procedure.
Programmer Response: Make sure that sufficient storage is
available for NIP processing. List the COMMNDxx members
being used for the current IPL.
Problem Determination: Table I, items 11, 26, 29.
IEA8651
SYSTEM ERROR DURING NIP PROCESSING OF prm
PA~AMETER - IPL TERMINATED
Explanation: A system error was detected while processing the
parameter indicated by prm in the message text. The error was
detected while attempting to prompt for the parameter
specified in the message and could mean that processing
modules have been overlaid or some necessary data
destroyed.
System Action: The system will enter a disabled wait state
with a wait state code of 03D displayed in the wait state PSW.
Operator Response: Dump real storage and notify the system
programmer of this message. Then re-IPL the system.
Problem Determination: Table I, items 2, 11, 16, 29.
IEA8661
VOLUME ser ON [V]xxx REQUIRED ON A
~devtYPt
iVyyy ~
Explanation: Volume ser is mounted on unit xxx, but the
VATLST entry for this volume specified device type 'devtyp' or
Section 5: lEA Messages - Supervisor
5-15
I
3850 Mass Storage System (MSS) unit 'yyy'. If V is specified,
unit· xxx is a MSS unit.
System Action: If ser is not a premounted, P/R volume, it will
be unloaded. ·If volume ser is a premounted, P/R volume,
message IEA947A will be issued.
Operator Response: If the volume is unloaded, the correct
volume may be mounted on the device type specified in the
message.
IEA8671
DUPLICATE VOLUME ser. UNIT ddd NOW
UNLOADED.
Explanation: Volume serial number ser duplicates the serial
number of a volume already mounted.
System Action: The volume on device ddd has been unloaded.
Operator Response: Mount a different volume on the unit if
ddd is listed in message IEA860A, or if all units listed in
message IEA860A have not come ready. If the unit was replied
in response to message IEA851A, the volume must have a
serial number listed in message IEA851A.
IEA8681
PARMTZ MEMBER IN PARMLIB INVALID. SYSGEN
VALUE BEING USED
Explanation: The time zone value specified in the PARTMZ
PARMLIB member is unacceptable for one of the following
reasons:
• The value is not between 00.00.00 and 12.00.00.
• The value is not in the proper syntax format. That format is:
~E t,hh[.mm[.ss]]
where E and W indicate whether the time
lw~
zone is East or West of the GMT zone.
System Action: The time zone constant specified in the
PARMTZ PARMLIB member is not used. The system will use
the time zone value specified at system generation time.
Operator Response: Probable user error. Take the appropriate
action as specified by the installation operating procedure and
report this message to the system programmer.
Programmer Response: Make sure that the time zone value
specified in the PARMTZ PARMLIB member is between
00.00.00 and 12.00.00 and it is in the proper syntax.
DSS INOPERATIVE,
~LOCATE~
FAILED FOR SYS1.DSSVM
lOPEN ~
Explanation: An attempt was made to 1) locate the
SYS1.DSSVM data set in the system catalog, or 2) open the
SYSl.DSSVM dataset. When the attempt failed, DSS was made
inoperative and control returned to NIP.
System Action: Processing continues ..
Programmer Response: Make sure that the data set has been
allocated and cataloged properly.
Problem Determination: Table I, items 2, 17b, 25a, 29.
IEA8691
IEA8701
DSS INOPERATIVE, ALIAS IQAINIOO NOT FOUND IN
LPA
Explanation: The DSS RIM (IEAVNPB6) was unable to find a
CDE or LPDE in the link pack area (LPA) for the entry point
IQAINIOO (in load module IQAENVOO). DSS was made
inoperative and control returned to NIP.
System Action: Processing continues.
Programmer Response: Make sure that module IQAENVOO with
alias IQAINIOO is link-edited correctly into SYS1.LPALIB.
Problem Determination: Table I, items 2, 17b, 25c, 27, 29.
~SYS1.NUCLEUSll/O ERROR DURING DSS RIM
lSYS1.DSSVM 5 PROCESSING
Explanation: lOS was unable to read from or write to the
indicated data set because of an I/O error.
System Action: Processing continues.
Operator Response: Record the device address on which the
error occurred.
IEA8711
lEA8721
INVALID IPS IN IEAIPSxx
Explanation: The system resources manager initialization
5-16
VS2 System Messages (VS2 Release 3.7)
program has found invalid IPS data in the IEAIPSxx list.
System Action: All IPS data in this list is ignored. The operator
will be prompted to respecify the IPS system parameter.
Operator Response: Probable user error. Take the appropriate
action as specified by the installation operating procedure.
IPL/NIP can continue if the operator specified another valid
IEAIPSxx list or enters EOB in response to the prompting
message following this message. Report this message to the
system programmer.
Programmer Response: Probable user error. List, check and
correct the syntax of the IPS parameters in the specified list.
The SET command may be issued to obtain more error
information about the IPS. Ensure that the installation
operating procedure tells the operator what to do if the
specified list is rejected during IPL/NIP.
Problem Determination: Table I, items 2, 26c, 29.
IEA8731
SKELETON IPS IN CONTROL - ALL USERS AT SAME
LEVEL
Explanation: This message indicates that the skeleton IPS has
been used by the system.
System Action: The system continues processing with a
skeleton IPS. The valid performance group numbers are 1 and
2. There will be no distinction in the performance given to
users among various performance groups.
Operator Response: The operator may subsequently use the
SET command to specify a valid IPS to supersede the skeleton
IPS. Report this message to the system programmer.
Programmer Response: Ensure that the installation operating
procedure tells the operator what to do if the skeleton IPS has
been used. Create a valid IEAIPSxx member using a utility
program such as the IEBUPDTE program.
Problem Determination: Table I, items 2, 29.
IEA8741
INVALID prm SPECIFICATION IN IEAOPTxx
Explanation: The system resources manager initialization
program has found an invalid specification of a prm parameter
in thelEAOPTxx member of SYSl.PARMLlB. prm is the
keyword identification for a category of system resources
manager tuning parameters.
System Action: All the parameters for the prm category of the
IEAOPTxx list will b~ ignored. System resources manager
initialization will supply default values for these parameters and
will continue processing.
Operator Response: Probable user error. Take the appropriate
action as specified by the installation operating procedure. Let
the system continue with the default tuning parameters or
re-IPL the system with a valid IEAOPTxx list. Report this
message to the system programmer.
Programmer Response:. Probable user error. List, check and
correct the syntax of the parameters in the specified IEAOPTxx
list. Ensure that the installation operating procedure tells the
operator what to do if invalid parameters are found in the
IEAOPTxx list during IPL/NIP.
Problem Determination: Table I, items 2, 26c, 29.
IEA8751
SYS1.DUMPxx FULL
Explanation: The first record in the SYS1.DUMP data set,
SYSl.DUMPxx, is not an end-of-data record. The data set may
contain an SVC Dump.
System Action: The data set is unavailable for use by SVC
Dump.
Operator Response: None. This message is generated as part
of the response for a LIST request on the DUMP option in the
reply to message IEA101A.
IEA8761
SYS1.DUMPxx EMPTY
Explanation: The first record in the SYS1.DUMP DASD data
set, SYS1.DUMPxx, is an end-of-data record.
~"
System Action: The data set is available for use by SVC
Dump.
Operator Response: None. This message is generated as part
of the response for a LIST request on the DUMP option in the
rep~y to message IEAI0IA.
IEA877A
SPECIFY FULL DASD SYS1.DUMP DATASETS TO BE
EMPTIED,
TAPE UNITS TO BE USED AS SYS1.DUMP
DATA SETS OR 'GO'
Explanation: The operator has specified a LIST request on the
DUMP option in the reply to message IEA101A. This message
is issued after the operator has been informed of the status
(empty or full) of each DASD SYSl.DUMP data set.
System Action: The system waits for the operator to reply.
Operator Response: Reply with the last two digits of the names
of those full DASD SYSl.DUMP data sets which are to be
reused (data that exists in the data set is lost) and/or tape
units to be used as SYSl.DUMP data sets, or 'GO'. If DASD
data set names and/or tape units are given in the reply, they
will be made available to SVC Dump. If the operator replies
with 'GO', the current status of the SYSl.DUMP data sets will
remain unchanged.
Examples of operator replies are as follows:
• R xx, 'DA = (yy{ ,yy, ..... })'
Note: yy is the last two digits of the name SYSl.DUMPxx
that have been indicated by message IEA8761. To empty
more than one DASD SYSl.DUMP data set, specify the last
two digits of each SYSl.DUMPxx data set name, separated
by commas.
• R xx, '(TA,ddd,ddd)'
Note: ddd and ddd are tape device addresses to be used by
SVC Dump. The devices specified cannot be devices that
have already been made available to SVC Dump.
• R xx, 'DA = (yy),(TA,ddd)'
• R xx,'GO'
IEA8801
Explanation: This message indicates that the DASD data set is
unusable by SVC Dump:
• The data set is on an unsupported device.
• An uncorrectable. error has occurred.
System Action: The data set will not be made available for
SVC Dump. Processing continues.
Operator Response: None.
IEA88l1
TOO MANY SYS1.DUMP DATASETS
Explanation: More than 10 data sets have been specified for
SYSl.DUMP data sets.
System Action: The first 10 data sets encountered will be
used as SYSl.DUMP data sets. The others will be ignored.
Operator Response: None.
IEA882A
REPLY FOR LIST REQUEST OF DUMP OPTION
INVALID - RESPECIFY
Explanation: An invalid reply was generated to message
IEA877A:
• A full DASD SYSl.DUMP data set was incorrectly specified.
• A tape unit to be added to the SYSl.DUMP data sets was
incorrectly specified.
System Action: The system waits for the operator to reply.
Operator Response: Probable user error. Respecify the reply to
message IEA877 A.
IEA8831
~DULE
IEAVTSDR NOT FOUND
Explanation: T~SVC Dump resource manager, IEAVTSDR,
could not be found in the link pack area (LPA).
System Action: Processing continues.
Operator Response: Notify the system programmer of this
message.
IEA8841
IEA8781
SYS1.DUMPxx UNACCEPTABLE FOR A SYS1.DUMP
DATASET
NO DASD SYSl.DUMP DATASETS AVAILABLE
PARAMETERS INVALID FOR SYS1.PARMLIB MEMBER
mem
Explanation: The operator requested the DASD function of the
Explanation: When mem is IEAABDOOor IEADMPOO, the
DUMP option in the reply to message IEAI0IA, but there are
no DASD SYSl.DUMP data sets available.
System Action: There are no DASD SYSl.DUMP data sets
available for use by SVC Dump.
Operator Response: None.
installation default options for SYSABEND or SYSUDUMP
dumps, respectively, are invalid.
System Action: If this message is followed by message
IEA88SI, there are valid and invalid parameters in memo The'
valid options will be used for memo Otherwise, all options were
invalid and no default dump options will be recognized.
Operator Response: Report this message to the system
programmer or installation manager. The message indicates
that the member mern should be corrected in SYSl.PARMLlB.
IEA879A
DEVICE AT ddd UNACCEPTABLE FOR A SYS1.DUMP
DATA SET - RESPECIFY
For the DUMP option of the reply to message
IEAI0IA, or in response to message IEA877A, or a previous
issuance of this message, the operator specified (TA,ddd)
where ddd is an unacceptable unit address for a SYSl.DUMP
tape data set:
• The unit control block (UCB) for ddd cannot be found.
• Device ddd is not a 2400 series tape device.
• Device ddd is not available, not operational, or nonexistent.
• An uncorrectable error has occurred.
• The device specified in response to a previous issuance. of
this message has been previously specified, and is not the
device that originally encountered the error.
• If ddd is blank, a syntax error occurred in a previous
response to this message.
System Action: The system waits for the operator to reply.
Operator Response: Probable user error. Verify that the device
is operational and is specified correctly. Then enter (TA,ddd)
again. If the second attempt also fails, specify another tape
device or press EOB to skip, and notify the system
programmer.
Explanation:
IEA88S1
VALID OPTIONS FOR SYS1.PARMLIB MEMBER mem
SDATA = op,op, .•. ,op
PDATA = op,op, ... ,op
Explanation: Valid and invalid dump options were defined in
SYSl.PARMLlB for member memo The SDATA and/or PDATA
options listed will be used as installation defaults.
System Action: Valid dump options will be recognized.
Operator Response: Report this message to the system
programmer or installation manager.
IEA886A
TODCLOCK(S) MUST BE SET
Explanation: No time-of-day clock is in the set state.
System Action: The system waits for the operator to reply.
Operator Response: Enter REPLY xx, 'prm' where prm may be
as follows:
DATE = yy.ddd[,CLOCK = hh.mm.ss][,GMT][,IPS = nn]
yy - is the year 00-99.
Section 5: lEA Messages - Supervisor
5-17
•
ddd- is the day 001-366.
hh - is the hour 00-23.
mm -is the minute 00-59 ..
ss - is the second 00-59.
nn - is a 2-character value which when appended to IEAIPS
specifies a member name.
The bracketed parameters are optional. If GMT is specified,
the entered DATE and CLOCK values are understood to be
Greenwich Mean values. If GMT is omitted, they are
understood to be local values, and will be converted by the
system to a GMT value with which to set the clocks.
IEA887A
IEA887A
CPU xx LOCAL DATE == yy.ddd,CLOCK == hh.mm.ss
TOD CLOCK(S) MUST BE SET WITH GMT, OR
SELECT ADDRESS
Explanation: There are at least 2 set time-of-day clocks in the
system which are not in synchronism.
The local date and clock values for each set clock are
displayed. In the message text, yy specifies the year (00-99),
ddd specifies the day (001-366), hh specifies the hour
(00-23), mm specifies the minute (00-59), ss specifies the
second (00-59), and xx specifies the CPU address (00-15).
System Action: The system waits for the operator to reply.
Operator Response: Reply as in message IEA886A, or enter
REPLY xx,'ADDR == xx" where xx is the address of the CPU
whose CLOCK and DATE values are displayed in the message.
The IPS parameter is also acceptablE! in the latter reply.
The latter response causes all time-of-day clocks in the
system to be synchronized to the value in the clock of the
selected CPU.
IEA888A
IEA888A
GMT DATE == yy.ddd,CLOCK == hh.mm.ss
LOCAL DATE == yy.ddd,CLOCK == hh.mm.ss REPLY U,
OR GMT/LOCAL TIME
Explanation: Either there is only one time-of-day 'clock in the
system and it is set, or all set clocks are in synchronism.
The local and Greenwich Mean date and clock values are
displayed for the operator's verification. In the message text,
yy specifies the year (00-99), ddd specifies the day
(001-366), hh specifies the hour (00-23), mm specifies the
minute (00-59), and ss specifies the second (00-59).
System Action: The system waits for the operator to reply.
Operator Response: If the values displayed are acceptable,
enter REPLY xx,'U'. If you wish to change any of the values,
specify CLOCK == hh.mm.ss and/or DATE == yy.ddd. GMT must
be entered to change a Gre.enwich Mean value, and must not
be entered to change a local value. The IPS parameter may
also be entered by itself, or in conjunction with the CLOCK,
DATE, .and. GMT parameters.
If the reply is anything except 'U', this message is repeated
with the changed values displayed.
IEA889A
DEPRESS TOD CLOCK SECURITY SWITCH
Explanation: The operator has accepted the values displayed
in message IEA888A. The· system is ready to synchronize the
time-of-day clocks in the configuration and requires that the
security switch be pressed in order to do so.
System Action: The system waits until the operator
acknowledges receipt of the message. When acknowledgement
is received, the system determines if the swtich has been
pressed. If it has not been pressed within 30 seconds, or if the
operator has pressed the switch but releases it before the
synchronizing procedure can complete, the message is
reissued.
Operator Response: Reply using only the reply id to
acknowledge your receipt of the message. (No reply text is
5-18
VS2 System Messages (VS2 Release 3.7)
required.) Then, press the security switch and hold it down for
5 to 10 seconds.
IEA8901
cm FAILED - MEMORY COULD NOT BE CREATED
Explanation:, An address space could not be created for the
command. Address space create or address space initialization
failed while trying to complete initialization for the address
space.
Note: Failure may be due to system overload or lack of
paging space.
System Action: The partially created address space is cleaned
up and the command is aborted.
Programmer Response: If message was issued when trying to
start an initiator, ASM. may have run out of paging space. It
may be necessary to re-IPL and specify larger or additional
paging data sets. If these are not readily available, it may be
possible to re-IPL with existing page data sets after modifying
ASM paging constant ILRSLOTC as described under wait code
03C.
Operator Response: Enter the command again. Inform the
system programmer that this message has been issued if the
message is issued again.
IEA8911
NO MAXUSER VALUE SPECIFIED, DEFAULT VALUE
OF 256 USED
Explanation: The NO MAXUSER value was specified; default
value is being used.
System Action: Processing continues.
Operator Response: None.
IEA8921
MAXUSER VALUE OF vailS TOO LARGE FOR
AVAILABLE SQA
Explanation: SQA core could not be obtained to build the
ASVT for the MAXUSER value specified. Either the MAXUSER
value is too large, or SQA is insufficient.
System Action: Processing continues.
Operator Response: If the MAXUSER is too large, respecify a
smaller value. Otherwise, examine the use of SQA and re-IPL
the system. If the problem persists, contact the system
programmer.
Problem Determination: Table I, items 2, 29.
IEA893A
ddd,ddd, ...
NOT READY. REPLY U WHEN DEVICES ARE READY,
OR NO IF NOT MOUNTING.
Explanation: Volume atteibute processor is waiting for the
volumes to be mounted on these devices.
System Action: The system waits for the operator to respond.
Operator Response: When all of the volumes in message
IEA851A that you require have been readied on the devices
listed in message IEA860A, reply 'U'. If any devices have not
been readied, message IEA893A will be reissued, listing those
devices. Respond as above if there are more volumes to be
mounted. If no more volumes are to be mounted on the
devices listed, reply 'NO'.
IEA8941
REQUESTED VOLUME ON REQUESTED UNIT. ddd
NOW UNLOADED.
Explanation: A volume requested in VATLSTxx was mounted on
a device address that was not in the reply to message
IEA851A.
System Action: The volume is unloaded.
Operator Response: Mount the volume on a requested unit if
the attributes are to be processed.
IEA895A FORMAT ERROR. REPEAT REPLY.
Explanation: An error exists in the reply to message IEA851A.
System Action: The reply is ignored and the system waits for
the operator to enter another reply.
Operator Response: Enter the reply again correctly, or reply
'U'.
IEA8961
RECORDING FUNCTION NO LONGER ACTIVE
Explanation: Due to errors considered unrecoverable, the
recording function has been turned off. No further writing to
SYS1.LOGREC or the operator via this function will occur.
System Action: All further requests for recording are rejected.
Requestors are given a return code indicating that the facility
is no longer active.
Operator Response: If recording is deemed critical, the system
must be re-IPLed.
Problem Determination: Table I, items 2, 16, 29.
IEA8971
RTM BLDCPOOL FAILED
Explanation: RecoveryItermination management initialization
has failed to acquire a pool of quickcells via the BLDCPOOL
service that is necessary to the functions operation.
System Action: Initialization is terminated. The system is
placed in a disabled wait state with a wait state code of X'45'
displayed in the wait state PSW.
Operator Response: Report this message to the system
programmer.
Problem Determination: Table I, items 11, 29.
IEA8981
!
CPU x HAS PERMANENTLY DAMAGED
TOD CLOCK
. CLOCK COMPARATOR
CPU TIMER
I
IEA903A
DEPRESS TOD CLOCK SECURITY SWITCH WHEN
ENTERED TIME OCCURS
Explanation: The operator has responded to message
IEA888A, IEA886A, or IEA887A in such a manner that a
time-of-day clock requires setting.
System Action: The system waits until the operator
acknowledges receipt of the message. When acknowledgement
is received, the system attempts, for a I-minute interval, to
set a time-of-day clock. If the operator has not pressed the
switch during that interval, the original message that the
operator responded to will be re-issued.
Operator Response: Reply 'u' to acknowledge your receipt of
the message. (No reply text is .required.) Then press the
security switch at the exact instant of the time you entered in
response to message IEA888A, IEA886A, or IEA887A.
IEA9041
VALUE FOR WTOBFRS MUST BE BETWEEN 20 AND
9999
Explanation: The parameter for WTOBFRS must be a decimal
value between 20 and 9999. The value specified contained a
nonnumeric character or was not in the acceptable range.
System Action: Message IEA906A is issued.
Operator Response: Respond to message IEA906A with REPLY
xx, 'WTOBFRS - nnn' where nnn is a decimal value between 20
and 9999.
IEA9051
VALUE FOR WTORPLY MUST BE BETWEEN 5 AND
100
Explanation: The parameter for WTORPLY must be a decimal
value between 5 and 100. The value specified contained a
nonnumeric character or was not within the acceptable range.
System Action: Message IEA906A is issued.
Operator Response: Respond to message IEA906A with REPLY
xx, 'WTORPLY - nnn' where nnn is a decimal value between 5
and 100.
Explanation: A sufficient number of machine checks have
occurred on the specified timing component on CPU x since
the last local midnight or IPL to cause the system to mark it
as unusable.
System Action: The system will not attempt to use the
specified component on CPU x until a re-IPL occurs. Note: If
the time-of-day clock is specified, the CPU's clock comparator
is also considered to be unusable.
If the damaged component is a time-of-day clock or clock
comparator, job step timing will become inacurate as far as
the affected CPU is concerned. Additionally, tasks with
outstanding real or wait type intervals, and those requesting
new intervals, will be abnormally terminated.
If the damaged component is a CPU timer, task type intervals
will not be timed for tasks executing on CPU x. If all CPU
timers available to a task are permanently damaged, tasks with
outstanding task type intervals, and those requesting new
intervals, will be abnormally terminated.
Operator Response: If the system action is unacceptable, enter
a VARY CPU x, OFFLINE command.
Problem Determination: Table I, items 18, 30.
Explanation: The system cannot initialize SQA or CSA
successfully.
System Action: Severe error. The system is placed in a 030
wait state following this message.
Operator Response: Take a dump of the system and notify the
system programmer of this message.
Problem Determination: Table I, items 2, 16,.29.
IEA8991
IEA9081
LOCAL TIME CHANGE REJECTED--NO GOOD TOD
CLOCKS
Explanation: The operator requested that the local time be
changed, or reset to its IPL-time value. A good time-of-day
clock is required for this operation, but none exists. Message
IEA8981 should have appeared previously, once for each
time-of-day clock in the system.
System Action: Processing continues without a change to the
local time.
Operator Response: None.
IEA906A
RESPECIFY prm PARM OR ENTER EOB
Explanation: Incorrect information has been entered for
parameter prm. Previous messages may diagnose the specific
error in the parameter specification.
System Action: The system waits for the operator to reply.
Operator Response: Reenter the prm parameter with a
corrected value, or respond with EOB to cause the system
defaults for the parameter to be used.
IEA9071
UNABLE TO INITIALIZE PAGE AND lOR SEGMENT
TABLE FOR SQA OR CSA
QUICKSTART REQUIRES PREVIOUS IPL SQA
SIZE-PREVIOUS SIZE USED
Explanation: The current requested SQA size is not the same
as the reclaimed size; both must be the same.
System Action: The system will default to the reclaimed SQA
size and continue processing.
Operator Response: Do not specify SQA size on a quick start.
Section 5: lEA Messages -Supervisor
5-19
•
VS2.03.807
IEA909A
ONLY nnnK OF
REAL
} STORAGE AVAILABLE FOR
{SQA}
{ VIRTUAL .
CSA
RESPECIFY OR ENTER EOB FOR DEFAULT REAL
Explanation: The requested area was too large.
System Action: The system waits for the corrected smaller
value to be entered.
Operator Response: Reenter the parameter with a smaller
value.
Operator Response: Respond to the prompt message with
appropriate text and report this message to the system
programmer.
Programmer Response: To avoid this message in subsequent
IPLs, correct the contents of IEASYSNN according to the
syntax for specifying paging space data set names.
Problem Determination: Table I, items 2, 25c (IEASYSNN of
SYS1.PARMLlB), 29.
IEA916E
IEA9101
CCH OPERATION IMPAIRED
Explanation: The nucleus initialization program (NIP) has been
unable to locate the module-dependent CCH modules which
are necessary to give CCH full recovery capability. As a result,
the CCH ,unction is running impaired.
.
System Action: The nucleus initialization program continues
processing.
Operator Response: Probable user error. Report this message
to the system programmer.
Programmer Response: Place the missing modules identified
by message IEAl061 in SYSl.LlNKLlB, and re-IPL the system
to establish full error recovery capability to the CCH function.
IEA9111
COMPLETE/PARTIAL DUMP ON
SYSl.DUMPxx/UNIT -= ddd
Explanation: A partial or complete SVC Dump was generated
to the DASD data set SYSl.DUMPxx or to the tape volume on
the device with the unit address ddd. If a partial dump was
generated, an I/O error may have occurred while writing to the
dump data set or the dump data set may have been filled
before all the requested~ data was dumped.
System Action: Processing continues.
Operator Response: To maintain the availability of SYSl.DUMP
data sets, the following should be done: if the dump is on a
tape (UNIT == ddd), rewind and unload the tape and mount
another unlabeled scratch tape. If· the dump is on a DASD
(SYS1.DUMPxx), the dump should be copied to another
installation data set by the use of the AMDPRDMP service aid
for further processing.
IEA9121
RECOVERY/TERMINATION DUMP FAILED [DUE TO
cde]
Explanation: SNAP was called by the ABDUMP phase of
recovery /termination. SNAP failed for one of the following
reasons:
• DCB not open or invalid page referenced during validity
checking.
• TCB address invalid or invalid page referenced during
validity checking; or insufficient storage available.
• DCB type not correct.
If the phrase 'DUE TO cde' appears, abnormal termination
with a system completion code of cde has occurred.
System Action: No dump is taken.
Programmer Response: Correct the original failure (cde) if
specified.
IEA915E
SYNTAX ERROR IN IEASYSNN CONTENTS, PROMPT
FOLLOWS
Explanation: Paging data set names· specified in the IEASYSNN
PARMLIB .member do not conform to the syntax rules defined.
The paging initialization routine will subsequently request the
operator to respecify this information.
System Action: Paging initialization invokes the prompt
routine, which will request a new set of text for the PAGE ==
parameter. Paging initialization continues after receipt of the
new text.
5-20
VS2 System Messages (VS2.03.807)
!
SYNTAX ERROR IN {PAGE SWAPDUPLEXPAGNUMSYSTEM PARAMETER, PROMPT FOLLOWS
Explanation: Information specified. in the indicated system
parameter does not conform to the syntax defined for it. The
operator will subsequently be requested to respecify that
parameter.
System Action: Paging initialization invokes the prompt
routine, which will request a new set of text for the indicated
parameter. Paging initialization continues after receipt of the
new text.
Operator Response: Respond to the prompt l1)essage with
syntactically correct parameter text and notify the system
programmer that this problem exists.
Programmer Response: Make sure that documentation for
specification of the system parameter conforms to the syntax
defined for the parameter.
Problem Determination: Table I, items 2, 29.
!
IEA9181
lPAGE
DATA SET dsn NOT ACCEPTED
SWAP
DUPLEX
Explanation: Either data set dsn is already being used by
paging initialization or addition of this name to the list of
paging or swapping data sets would exceed the limit. A limited
number of paging or swapping data sets may be known to the
paging or swapping routines at one time.
If message IEA922D follows this message, a limit has not been
reached, but the data set is already in use. Message IEA922D
will offer the operator a chance to respecify a data set name.
System Action: Initialization continues.
Operator Response: If a paging or swapping data set limit has
been reached, notify the system programmer.
Programmer Response: If for any reason this data set must be
used and some others previously known to paging routines
should be omitted, respecify the paging data sets when
restarting the system with the CLPA or CVIO option.
Problem Determination: Table I, item 29.
IEA9201
1
PAGE
SWAP
DUPLEX
!
DATA SET dsn NOT LOCATED
Explanation: A request to locate data set dsn resulted in an
error. Either the data set cannot be located in the catalog or
catalog information does not agree with expected and
necessary attributes of a page or swap data set.
System Action: If DUPLEX is specified in the message text and
the DUPLEX page data set is known from a previous IPL and
should be used under current IPL options, message IEA9421
will follow, and paging initialization continues. If the data set
was newly specified during this IPL, message IEA9222D will
follow this informational message, offering the operator a
chance to respecify the data set name before paging
initialization continues.
VS2.03.807
"
If PAGE is specified in the message text and the page data set
is known to paging initialization routines from a pervious IPL as
containing VIO pages which should be used under current IPL
options, message IEA9301 will follow, and paging initialization
will continue.
In all other cases, message IEA922D will follow this message.
Operator Response: Report this message to the system
programmer.
Programmer Response: If the data set should be used in
subsequent systems, prepare it according to instructions
before the next IPL.
I
I
Section 5: lEA .Messases. ~ Supervisor
5-20.1
5-20.2
VS2 System Messages (VS2.03.807)
VS2.03.807
IEA9211
PAGE DATA SET dsn INVALID
IEA924D
Explanation: The cataloged information about this page data
set indicates some discrepancy with the requirements of a
page data set. It may not be a device supported for paging or
the data set is not defined as previously known to paging
initialization.
System Action: If the. page data set was to contain PLPA
pages, message IEA935W will follow, and IPL will terminate.
If the data set specified is the DUPLEX page data set and if it
is known from a previous IPL and should be used under
current IPL options, message IEA942 I will follow, and paging
initialization continues.
If the data set specified is a page data set known to paging
initialization as containing VIO pages which should be used
under current IPL options, message IEA9301 will follow, and
paging initialization continues.
In all other cases, message IEA922D will follow, offering the
operator a chance to respecify the data set name before
continuing.
Operator Response: Report this message to the system
programmer.
Programmer Response: Check catalog information about this
data set. If necessary, redefine before the next IPL.
Problem Determination: Table I, item 29.
IEA922D
REPLY 'DSN
= dsn' OR 'IGNORE'
Explanation: This message provides the system operator with
~\
,J
,/
the opportunity to respecify a· paging space data set name, for
a reason documented by a preceding message on the console
sheet.
System Action: The system waits for the operator to reply. If a
new data set name is provided, that data set is processed as a
paging space. If 'IGNORE' is specified, paging initialization
continues with the existing list of paging spaces.
Operator Response: To add a data set to the collection of
paging spaces, enter REPLY xx, 'DSN = dsn' where dsn is the
data set name for the new paging space. To continue without
additional paging data sets, enter REPLY xx, 'IGNORE'. Notify
the system programmer of this message.
Programmer Response: Appropriate action is described with
the documentation of the message which preceded this
message on the console sheet.
IEA923D VOLUME ser NEEDED FOR {PAGE}
SWAP
DATA SET WAS NOT MOUNTED;
REPLY 'GO' OR 'IGNORE'
Explanation: An open of a data set on this volume was
attempted, and paging initialization was informed that the
volume was· not mounted. The data set does not contain any
pages of PLPA or VIO· that would be missed with the IPL
options in effect.
System Action: The system waits for the operator to reply. If
the volume is to be provided, paging initialization continues, a
mount message is issued, and the data set is used. If the
volume is not provided, paging initialization continues without
the data set.
.
Operator Response: Either enter REPLY xx,'GO' and prepare to
mount the requested volume, or enter REPLY xx, 'IGNORE'.
Notify the system programmer of this message if the volume is
not made available.
Programmer Response: Review space now being used for
paging or swapping, depending upon which type was ignored.
The PAGEADD command may be needed to help system
performance if insufficient space has resulted.
Problem Determination: Table I, item 29.
VOLUME ser NEEDED FOR PAGE DATA SET WAS
NOT MOUNTED;;
CLPA MAY BE FORCED
}
{ NEW PLPA DATA SET MAY BE REQUESTED
REPLY "GO' OR 'IGNORE'
Explanation: An open for a required page data set on this
volume was attempted, and paging initialization was informed
that the volume was not mounted. If CLPA MAY BE FORCED is
specified in the message text, then the COMMON page data
set is on this volume. If NEW PLPA DATA SET MAY BE
REQUESTED is specified, then the PLPA page data set is on
this volume.
System Action: The system waits for the operator to reply. If
the volume is to be provided ('GO'), paging initialization
continues, a mount message is issued, and the data set is
used. In most cases, if the volume is not to be provided
('IGNORE'), a new data set name will. be requested by
message IEA922D. However, if a quick or warm start is in
progress, the PLPA page data set overflowed to the COMMON
page d.,ta set, and the unmounted volume contains this
COMMON page data set, paging initialization will force a cold
start (CLPA) and issue message IEA9291.
Operator Response: Either enter REPLY xx, 'GO' and prepare to
mount the requested volume, or, enter REPLY xx, 'IGNORE' and
notify the system programmer.
Programmer Response: If a permanent change is desired,
•
update SYS1.PARMLIB to reflect the new PLPA or COMMON
page data set name. Otherwise, complete the IPL, correct the
problem, and re-IPL with the original data sets.
Problem Determination: Table I, item 29.
IEA925D
VOLUME ser NEEDED FOR PAGE DATA SET WAS
NOT MOUNTED; CVIO MAY BE FORCED; REPLY "GO'
OR 'IGNORE'
Explanation: An open of a page data set on this volume was
attempted, and paging initialization was informed that the
volume was not mounted. The volume contains pages of VIO
data sets which may be required for recovery of one or more
VIO data sets. Replying IGNORE will force the CVIO option.
System Action: The system waits for the operator to reply. If
the volume is to be provided, paging initialization continues, a
mount message is issued, and page data sets on that volume
are used. If the volume is not provided, paging initialization
continues without page data sets on that volume. In addition,
the CVIO option will be in effect, causing all VIO data sets
from previous IPLs to be unrecoverable.
Operator Response: Either enter REPLY xx, 'GO' and prepare to
mount the requested volume, or enter REPLY xx, 'IGNORE'.
Notify the system programmer of this message if the volume is
not made available.
Programmer Response: Review paging space since CVIO
option is in effect unexpectedly. Only data sets specified on
this IPL will be attempted for use. The PAGEADD command
may be needed.
Problem Determination: Table I, item 29.
IEA9271
PLPA AND COMMON PAGE DATA SETS FULL FROM
PREVIOUS IPL
Explanation: On a previous IPL, the PLPA and COMMON page
data sets were filled up during the write of the pageable LPA.
The CSA and the rest of the pageable LPA have no primary
slots.
System Action: Paging initialization continues with the DUPLEX
page data set. If there is no DUPLEX page data set, message
IEA935W is issued.
Operator Response: Report this message to the system
programmer.
Section 5: lEA Messages - Supervisor
5-21
I
VS2.03.807
Programmer Response: If a warm start is· necessary to clean
up work in the system, make sure that the previous DUPLEX
page data set is usable, and re-IPL. Otherwise, redefine the
I
5·21.0
VS2 System Messages (VS2.03.807)
I
PLPA and COMMON page data sets, and· re-IPL with the CLPA
option.
Section 5: lEA Messages· Supervisor
5-21.1
VS2.03.807
IEA9291
CLPA FORCED
Explanation: This message provides further information about
the nature of the IPL as it changes. The paging initialization
routines are unable to fulfill the ... CLPA (not CLPA) IPL option,
for the reason documented in the preceding message.
System Action: Paging initialization continues as if CLPA had
been specified.
Operator Response: Report this message to the system
programmer.
Programmer Response: See the documentation for the
messages that preceded this message on the console sheet.
IEA9301
CVIO FORCED
Explanation: This message provides further information about
the nature of this IPL as it changes. The paging initialization
routines are unable to fulfill the ... CVIO (not CVIO) IPL option,
for the reason documented in the preceding message.
System Action: Paging initialization continues as if CVIO had
been specified.
Operator Response: Report this message to the system
programmer.
Programmer Response: See the documentation for the
messages that preceded this message on the console sheet.
IEA9311
ESTAE REQUEST FOR GTF TRACE FORMATTING
FUNCTION UNSUCCESSFUL
Explanation: GTF formatting module, IGCOF05A, was unable to
establish ESTAE environment.
System Action:· No GTF buffers are formatted.
Programmer Response: None.
Problem Determination: Table I, items 4, 7a, 13, 29.
certain minimum number of paging data sets with a minimum
number of system-page-sized slots in a certain distribution
available to paging initialization. The paging resource
initialization manager has determined that this is not available.
System Action: System initialization ceases. The system enters
a wait state.
Operator Response: Report this message to the system
programmer.
Programmer Response: Either 1) redefine spaces to conform
with the description provided in paging planning specifications
and re-IPL with the CLPA option, or 2) provide additional
paging spaces and make them available to paging initialization
via either the PAGE = parameter or PARMLIB during re-IPL.
Problem Determination: Table I, item 29.
IEA9361
FUTURE QUICK OR WARM STARTS OF THIS IPL
WILL FAIL
Explanation: On a CLPA IPL, paging initialization needed to
write quick/warm start data to the first records of the PLPA
page data set. Howver, the write failed, and none of the
information will be accessible to a future IPL.
System Action: Paging initialization continues.
Operator Response: Report this message to the system
programmer.
Programmer Response: When using this PLPA page data set
again, perform a CLPA IPL.
Problem Deterinination: Table I, item 29.
IEA9371
COMMON PAGE DATA SET TIMESTAMP FAILURE
Explanation: When this message is followed by message
Explanation: GTF formatting module was unable to load format
appendage xxx.
System Action: Formatting of the GTF buffers will continue,
dumping in hexadecimal any record that requires format
appendage xxx for editing.
Programmer Response: None.
Problem Determination: Table I, items 7a, 9a, 13, 29.
IEA935W, paging initialization was unable to read or write the
timestamp record in the COMMON page data set. The
timestamp is written on CLPA IPLs; it is read on ... CLPA (not
CLPA) IPLs if part of the PLPA was written to the COMMON
page data set.
When this message is followed by message IEA9291, paging
initialization read the timestamp in the COMMON page data
set, but the timestamp failed to match the timestamp of the
PLPA slot information.
System Action: If unable to access the COMMON page data
set, the system enters a wait state. If the wrong level of the
COMMON page data set is accessed, system operation
continues with the CLPA IPL forced.
Operator Response: Report this message to the system
programmer.
Programmer Response: If a wait state occurred, correct or
replace the COMMON page data set, and re-IPL with the CLPA
option.
If a wait state did not occur, and a warm start is necessary,
stop the IPL, make the correct level COMMON page data set
available, and re-IPL.
IEA9341
IEA938W
IEA9321
INSUFFICIENT STORAGE FOR GTF BUFFER
FORMATTING
Explanation: There is insufficient SQA for GTF buffer
formatting.
System Action: No GTF buffers are formatted.
Programmer Response: None.
Problem Determination: Table I, items 4, 7a, 13, 29.
IEA9331
UNABLE TO LOAD FORMAT APPENDAGE xxx.
FURTHER RCDS
REQUIRING THIS MOD WILL BE DUMPED IN HEX
INVALID RETURN CODE RECEIVED FROM mod.
FURTHER RCDS
REQUIRING THIS MOD WILL BE DUMPED IN HEX
Explanation: On return from module mod an invalid return
code was recognized.
System Action: FQrmatting of the GTF buffers will continue,
dumping in hexadecimal any record that requires this module
for editing.
Programmer Response: None.
Problem Determination: Table I, items 7a, 9a, 13, 29.
IEA935W
INSUFFICIENT PAGING RESOURCES, IPL
TERMINATED
Explanation: To support minimal paging there must be a
5·22
VS2 System Messages (VS2.03.807)
NO STORAGE AVAILABLE, PAGING INITIALIZATION
TERMINATED
Explanation: A request for additional storage failed during
paging initialization. The resource initialization managers are
unable to continue. A probable reason is that ·the system
queue area i(SQA) maximum amount specified has been
exceeded.
System Action: System initialization ceases. The system enters
a wait state.
Operator Response: Report this message to the system
programmer.
Programmer Response: Make sure that SQA assignment. is as
recommended. If not, increase SQA maximum size to that
recommended in generating a new system. Otherwise, the
VS2.03.807
system configuration may be too small, or there may be a
problem with at least one resource initialization manager.
Problem Determination: Table I, items 2, 11, 17, 29.
IEA939D
QUICK AND WARM START DATA IS INVALID,
RE-IPL OR REPLY 'GO' FOR COLD START
Explanation: A .. CLPA (not CLPA) IPL was attempted, and
informaticm on the PLPA paging data set was inaccessible:
• The PLPA paging data set specified on this IPL must be the
same as that used on the previous successful CLPA IPL.
• If the same data set was being used, then the needed
information is not able to be read.
System Action: The system waits for the operator to reply.
Operator Response: Either enter REPLY xx, 'GO' if a cold start
(CLPA) is desired, or re-IPL with a different data set specified
for PLPA paging. Report this message to the system
programmer.
Programmer Response: Verify that the correct SYS1.PARMLIB
is being used. Also, verify the previous use of the PLPA paging
data set.
Problem Determination: Table I, item 29.
IEA9401
THE FOLLOWING PAGE DATA SETS ARE IN USE
PLPA ..• dsn
COMMON. dsn
[DUPLEX • dsn]
LOCAL •• dsn
Explanation:: This message is issued if L is specified on the
PAGE == system parameter, or if paging initialization has been
forced to change the list of page data sets originally specified.
The list of data sets should help the operator verify which
paging volumes are in use, especially after a warm start where
data sets used on the previous IPL were not specified on this
IPL.
System.Action: Initialization continues.
Operator Response: None.
IEA941D
VOLUME ser NEEDED FOR DUPLEX DATA SET NOT
MOUNTED;
DUPLEXING MAY BE STOPPED, REPLY 'GO' OR
'IGNORE'
Explanation: An open on volume ser was attempted, but
paging initialization was informed that the volume was not
mounted. If duplexing is desired for this IPL, the volume must
be mounted.
System Action: The system waits for the operator to reply. If
the volume is to be provided, paging initialization continues, a
mount message is issued, and the data set is used. If the
volume is not provided, paging initialization continues without
duplexing.
Operator Response: Either enter REPLY xx, 'GO' and prepare to
mount the requested volume, or enter REPLY xx, 'IGNORE'.
IEA9421
\
DUPLEXING INACTIVE,
NO DATA SET }
{ BAD TIMESTAMP
Explanation: A DUPLEX page data set and the CLPA option
were specified either on the current IPL or on the CLPA IPL for
which the current IPL is based. While attempting to use the
DUPLEX page data set, a problem was detected:
• If NO DATA SET is specified in the message text, the
reason for the problem is documented in the preceding
message.
• If BAD TIMESTAMP is specified in· the message text, and if
the CLPA option was specified or forced, the attempt to
write a timestamp to the first record of the data set failed.
If the CLPA option was not used, the attempt to read the
timestamp failed or the timestamp no longer matched that
of the PLPA slot information.
System Action: Paging initialization continues without
duplexing.
Operator Response: To restore duplexing, perform a CLPA IPL
with the DUPLEX page data set specified. If necessary, replace
or correct the DUPLEX page data set.
IEA943W
FAILURE DURING REBUILD OF PLPA
Explanation: For a .. CLPA (not CLPA) IPL, paging initialization
attempted to restore paging information for the PLPA data set
into the page tables representing the PLPA. However, the page
table could not be found or PLPA slot information was invalid.
For a CLPA IPL, paging initialization attempted to save paging
information found in page tables representing the PLPA.
However, a page table could not be found.
System Action: Paging initialization terminates with a wait
state code of X'060'.
Operator Response: Report this message to the system
programmer. Re-IPL with the CLPA option specified.
Problem Determination: Table I, item 29.
IEA9441
QUICK OR WARM STARTS FROM THIS IPL WILL
HAVE RANDOM RESULTS
Explanation: On a quick or warm start, an attempt to write
page data set information to the PLPA page data set has
failed. The failure may have destroyed previous information or
may have just left the information down level. Further use of
the information would therefore cause unpredictable results.
System Action: The present IPL continues processing.
Operator Response: Report this message to the system
programmer. If the present IPL status is either specified or
forced CVIO, and it is desired to do -CVIO (warm start) on the
next IPL, then stop the current IPL. If the present IPL status is
..CVIO (warm start), continue with the current IPL only to clear
up previous VIO-related jobs. Re-IPL according to the system
programmer's instructions.
Programmer Response: Evaluate the PLPA page data set, and
replace or redefine, as necessary. Then, re-IPL with this PLPA
page data set and the CLPA option specified.
Problem Determination: Table I, item 29.
IEA945W
UNABLE TO USE CLOCK FOR TIMESTAMP
Explanation: On an IPL in which CLPA or CVIO was specified
or forced, paging initialization needs a unique number
(timestamp) to mark corresponding information and data sets.
An attempt to use the STCK instruction to obtain this number
failed with a condition code of 2 or 3.
System Action: IPL is terminated with a wait state code of
X'060'.
Operator Response: Repeat the IPL. If the problem persists,
the clOCk is not even able to be set.
Problem Determination: Table I, item 30.
IEA946W
NO{VIRTUAL} STORAGE AVAILABLE FOR SQA
REAL
Explanation: During a GETMAIN or a FREEMAIN it was
necessary to obtain storage in the system queue area (SQA)
for an internal control block. No virtual or real space was
available.
System Action: The system was placed in a wait state with a
wait state code of 101 (virtual) or 102 (real).
Section 5: lEA Messages - Supervisor
5-23
•
Operator Response: Restart the system. If the message occurs
frequently with the VIRTUAL option. installation action is
needed to increase the space allowed for· the system queue
area; more space should be specified at system generation
time or in response to message IEA101A during system IPL. If
the message occurs frequently with the REAL option.
installation action is required to decrease the fixed real
storage requirements of the system.
Probl,m Determination: Table I. items 2. 11. 29.
IEA947A
REPLY U TO CONTINUE. OR RE IPL.
Explanation: A system volume. specified in message IEA8661.
is not mounted on the device type specified in the VATLST
entry.
System Action: The system waits for the operator to reply.
Operator Response: If the wrong volume was mounted at IPL.
mount the correct volume. If the correct volume is mounted.
reply ·u· to continue. and notify the system programmer of the
VATLST entry error. If you reply ·U·. the system will ignore the
attributes of the volume and they will remain P/R .. Public.
IEA9481
[V]xxx NOW UNLOADED.
Explanation: The system has unloaded the volume on device
xxx. If V is present in the message. the volume is a Mass
Storage System (MSS) volume.
System Action: The volume is unloaded.
Operator Response: Respond as indicated by the operator
response for preceding message (either message IEA8541 or
IEA8661).
IEA9491
IEA949A
I/O ERROR READING VATLSTxx.
REPLY YES FOR LIST OF ENTRIES THAT WILL BE
PROCESSED. OR U FOR NO LIST.
Explanation: The system detected an uncorrectable
input! output error while reading VATLSTxx. a member of
SYS1.PARMLIB containing a volume attribute list. If message
IEA949A does not appear. then no VATLST entries had been
encountered before the error occurred.
System Action: The system waits for the operator to reply.
Operator Response: If message IEA959A appears. then reply
'YES' for a list of entries (encountered before the error
occurred) that will be processed. If no listing is desired. reply
·U·.
IEA9501
MODULE mod NOT FOUND; MC ROUTING INACTIVE
Explanation: Module mod was not found in LPA. This module
5-23.0
VS2 System Messages (VS2.03.807)
is required for use with the MONITOR CALL routine facility;
any of the following users of this facility will be unable to
initialize:
GTF
System Action: Processing continues.
Programmer Response: If any of the above functions are
desired. the following modules must be present in LPA:
AHLSETEV
AHLSETD
AHLMCER
After updating the necessary libraries with these modules.
re-IPL the system to initialize the desired function.
Problem Determination: Table I. items 2. 13. 7c. 29.
IEA9511
IPC FAILURE ON CPU x.
IEA9521
IPC FAILURE ON CPU(S) aa.bb ••••• pp
STATUS - stat}
{ CODE- rc
Explanation: During execution of the nucleus initialization
program for a multiprocessor configuration. a SIGP instruction
for either initial program reset (IPR) or restart was executed
by the interprocessor communications (IPC) function to CPU x.
STATUS - stat
The SIGP instruction resulted in condition code· 1 (SIGP
function unsuccessful) and status information stat being stored.
The IPC function returned a code of 8 to its caller.
, Code - rc
The IPC function returned the undefined return code rc to its
caller. The status of the SIGP function is unknown.
System Action: The signaled CPU is treated as offline; no
initialization is performed for it. Processing continues for the
other CPUs in the configuration.
Operator Response: Probable hardware error. If the subject
CPU is required to be online. analyze the status information
and adjust the switches on the CPU and either restart the
system or execute a VARY CPU ONLINE to that CPU.
Problem Determination: Table I. items 2. 29. or 30. Also have
the recorded switch settings on the subject CPU avaUable.
Explanation: During execution of the nucleus initialization
,program (NIP) for a multiprocessor configuration. a SIGP
instruction for either initial program reset (IPR) or restart was
executed by the interprocessor communication (IPC) function
to CPU(s) aa.bb •...• pp. The SIGP instruction resulted in '
condition code 2 (SIGP function not completed because the
access path to the addressed CPU was busy or the addressed
Section 5: IEA Messages· Supervisor
5-23.1
CPU could not accept or respond to the function code.) The
IPC function returned a code of 4 to its caller.
System Action: The signaled CPUs are treated as offline and
no initialization is performed for them. Processing continues
for the other CPUs in the configuration.
Operator Response: Probable hardware error. If the subject
CPUs are required to be online, make sure that no other CPU
is signaling them and that. the SIGP instruction is installed on
them and either re-IPL the system or execute a VARY CPU
ONLINE to them.
Problem Determination: Table I, items 2, 30.
IEA9531
UNABLE TO INITIALIZE CPU(S) aa,bb, •.• ,pp
Explanation: During execution. of the nucleus initialization
program (NIP) for a multiproeessing configuration, CPUs
aa,bb, ... ,pp did not successfully complete their initialization.
System Action: Any storage areas allocated to the CPUs are
freed and the CPUs are treated as offline.
Operator Response: Probable hardware error. If the subject
CPUs are required to be online, either restart the system or
execute a VARY CPU ONLINE to them.
Problem Determination: Table I, items 2, 30.
IEA9541
MALFUNCTION ALERT GENERATED BY CPU(S)
aa,bb, .•. ,pp
Explanation: During execution of the nucleus initialization
program (NIP) for a multiprocessor configuration, CPUs
aa,bb, ... ,pp generated malfunction alerts. Malfunction alerts are
generated by a CPU when a machine check condition arises
but machine checks are disabled in the CPU's PSW and the
'hard stop' bit is on in the CPU's machine control register 14.
System Action: If the malfunction alert occurred before the
CPU was initialized, no attempt is made to initialize it. If the
malfunction alert occurred during or after the initialization of
the CPUs, any storage areas allocated to the CPUs are freed
and the CPUs are marked offline.
Operator Response: Probable hardware error. If the subject
CPUs are required to be online, either restart the system or
execute a VARY CPU ONLINE to them ..
Problem Determination: Table I, items 2, 30.
IEA9551
nnnK OF ONLINE REAL STORAGE, MAY BE
INSUFFICIENT
Explanation: During execution of the nucleus initialization
program (NIP), nnnK (K = 1024) of real storage was found
online. This is less than the minimum of 768K required to
execute OS/VS2 release 2.
System Action: System initialization attempts to continue. NIP
reduces the sizes of certain permanent system cell pools to
their minimum to use as little real storage as possible.
Operator Response: None.
If LOW appears in the message text, the value specified will
not allow sufficient real storage for the minimum. V - R region
for NIP.
System Action: The installation-specified value is ignored and
the default maximum of 2 megabytes (2,097,152 bytes) is
used in determining the top of NIP's V - R region.
IEA9571
program (NIP) for a multiprocessor configuration, the restart
resource word 'CVTRSTWD' contained wd when the IEAVNIPO
CSECT of NIP required the restart resource. At the time
IEAVNIPO executes, the word should contain zeros.
System Action: IEAVNIPO treats the situation as an error and
appropriates the restart resource by putting NIP's 10 in the
word and using the resource.
Pr9grammer Response: Probable user error. Make sure that no
superzaps have been applied to the field 'CVTRSTWD' in
the nucleus. If they have, resuperzap the field to zero.
Problem Determination: Table I, items 2, 29.
IEA9581
TOP OF NIP V - R REGION IS TOO
~HIGHl
lLOwf
Explanation: The installation-specified value for the top of the
nucleus initialization program's (NIP) V = R region is not
acceptable. The installation specifies this value by running a
superzap against field 'NVTNVRSZ' in the IEAVNIPO CSECT of
the nucleus. If HIGH appears in the message text, the value
specified will not allow:
• The V - R region to fit below the low end of the master
scheduler's LSQA.
• The V - R region to fit below the low unavailable address.
• Sufficient real storage for the minimum number of reserved
frames.
5-24
VS2 System Messages (VS2.03.807)
EXCP APPENDAGE NAME TABLE NOT BUILT
Explanation: During nucleus initialization, the IEAAPPOO
member of SYS1.PARMLIB was accessed to build a table of
valid module ids which may be loaded as EXCP appendages.
Due to an I/O error or to a syntax error in IEAAPPOO the
constructing of this table was not completed.
System Action: No user-supplied appendages will be loaded
for a DCB where MACRF - (E) unless the user is operating in
system key 0-7 or authorized under APF. If an OPEN is
attempted against a DCB with appendage IDS to be loaded
and either of these conditions is met, a 913 ABEND with a
return code 20 will result.
Operator Response: Report this message to the system
programmer. IEAAPPOO must be rebuilt prior to the next IPL
for jobs which require unauthorized EXCP appendage routines.
IEA9591
ERROR CAUSED ACTIVE LPA TO BE TRUNCATED,
MODULE CONTROL MAY BE LOST.
Explanation: Recovery from a system error required the active
link pack area to be truncated. This means that modules in the
LPA may no longer be invokable and attempts to use them
may cause abnormal termination or unpredictable results.
System Action: The system continues processing; a record
indicating the error is written to SYS1.LOGREC.
Operator Response: Report this message to the system
programmer. If frequent abnormal terminations occur, re-IPL
may be necessary.
Problem Determination: Table I, items 2, 29. Dump the
SYS1.LOGREC data set and save the output.
IEA9601
IEA9561
RESTART RESOURCE WORD CONTAINED wd
Explanation: During execution of the nucleus initialization
ENQ/DEQ CONTROL QUEUES WERE DAMAGED.
RESTORATION ATTEMPTED.
Explanation: The ENQ/DEQ controJ blocks contained invalid
data which caused the current ENQ or DEQ request to function
incorrectly.
System Action: If the error was considered correctable, the
correction was made. The task from which the error was
detected was terminated.
If the error was considered uncorrectable, the control queues
were corrected, only to allow dequeues relating to the
damaged area. All enqueues relating to the damaged area will
be terminated with a 838 ABEND completion code. The task
from which the error was detected is terminated.
Operator Response: Notify the system programmer.
Note: Related information can be found in SYSl.LOGREC.
Problem Determination: Table I, items 2, 3, 4, 13, 16, 18, 29.
IEA9611
RESOURCE NAMED xxx, yyy MAY BE DAMAGED
Explanation: This message follows message IEABOll. It
indicates a task or an address space that abnormally
terminated while in 'step must complete' status, while holding
the resource named xxx (ENQ q-name), yyy (ENQ r-name).
System Action: The indicated resource was dequeued and the
'must complete' status reset. Processing continues.
Operator Response: Notify the system programmer.
Problem Determination: Table I, items 2, Sa, 15, 16, 29.
IEA962A
MESSAGE FOR INACTIVE CONSOLE nn. REPLY
SSEND,
OR OK.
1DELETE, 5
t
Explanation: A message has been enqueued to the inactive
console whose console id is nn.
System Action: The message remains enqueued to the inactive
.console until a reply is given.
If the console has been activated before the reply is issued,
the reply is ignored. If the message issuer terminated or has
issued a DOM for the message, the reply is ignored and the
message is deleted.
Operator Response: Enter one of the following replies:
• REPLY xx,'SEND'; the message will be rerouted to the
master console and deleted from ·the inactive console's
queue. This reply is not valid for multiple-line messages.
• REPLY xx, 'DELETE'; the message will be deleted from the
inactive console's queue.
., REPLY xx,'OK'; the message will remain enqueued to the
inactive console.
IEA963A
I
INVALID REPLY TO MESSAGE IEA962A. REPLY
SSEND,
OR OK.
1DELETE,5
t
Explanation: The reply given to message IEA962A was invalid.
System Action: The message remains enqueued to the inactive
console until a correct reply is given.
Operator Response: Enter. one of the following replies:
• REPLY xx, 'SEND'; the message will be rerouted to the
master console and deleted from the inactive console's
queue. This reply is not valid for multiple-line messages.
• REPLY xx,'DELETE'; the message will be deleted from the
inactive console's queue.
• REPLY xx, 'OK'; the message will remain enqueued to the
inactive console.
IEA9641
HARDCOPY SUSPENDED, NO HARDCOPY DEVICE
AVAILABLE
Explanation: The device which had been receiving hardcopy or
which was scheduled to receive hardcopy has become
unusable. Hardcopy is required either because of the console
configuration or because the HARDCPY parameter was
specified at IPL time. Neither an appropriate console nor the
SYSLOG data set is available to switch the hardcopy output to.
System Action: Processing continues. Messages processed
during the suspended period will not be saved for hardcopy
later.
Operator Response: Hardcopy may be restarted by varying a
hardcopy console online (that is, a console with paper output),
or by starting the system log and varying hardcopy to SYSLOG.
IEA967A
UNSUCCESSFUL RECOVERY ATTEMPT BY
SUPERVISOR CONTROL
Explanation: . Supervisor control has suffered a double
recursive ABEND in supervisor control buffer FRR.
System Action: The system enters a disabled wait state.
Operator Response: Re-IPL.
Problem Determination: Table I, items 2, 13, 29.
IEA969A
- WARNING - SIGP IPR FAILED DURING ALTERNATE
CPU RECOVERY PROCESSING
Explanation: An attempt by module IECVRSTI to reset the
dead CPU and its I/O devices by means of a SIGP instruction
has failed.
System Action: Processing continues; however, since the I/O
devices on the dead CPU have not been reset, any device
which had an I/O operation outstanding for the dead'CPU
might be inaccessible to the live CPU.
Operator Response: Probable hardware error.
Caution: Since the dead CPU has not been reset; START,
RESTART, or RESET should not be attempted on the dead CPU
until the dead CPU has been reconfigured to unit processor
mode. After the dead CPU has been reconfigured, and only
after this has been done, the dead CPU should be RESET to
free the I/O devices.
This is a hardware malfunction which might cause gradual loss
of I/O function to the system.
Problem Determination: Table I, item 30.
IEA9701
CHANNEL RECONFIGURATION HARDWARE
ACTIVATED
Explanation: The Channel Reconfiguration .Hardware (CRH) is a •
hardware feature on the System/370 168MP which, under
system control, enables the operative CPU to access the
channels on the inoperative or offline CPU. The Channel
Reconfiguration Hardware is now being used because one of
the following has occurred.
.
• A hardware failure on one CPU caused the Alternate CPU
Recovery (ACR) function to take the failing CPU offline and
activate CRH.
• The operator has issued a Vary Channel command that
made a channel online; this particular channel is the first
channel varied online that is attached to an inoperative or
offline CPU.
System Action: System processing continues.
Operator Response: Notify system programmer.
CAUTION: CRH is .intended. only for temporary use to service
the I/O devices on the offline CPU until all critical jobs can
complete processing. The operator should then vary all
channels on the inoperative CPU offline as soon as possible.
When all channels on the inoperative CPU are offline, CRH is
automatically deactivated.
Since CRH relies in part on the hardware contained in the
failing or offline CPU, certain portions of that CPU cannot be
powered off while CRH is active. The inoperative or offline
CPU must be in stopped state to prevent selection of any
channels being accessed by CRH. the System Mode switch for
configuring to a uniprocessor or multiprocessor must be left in
MP mode.
IEA971 I
UNABLE TO ACTIVATE CHANNEL
RECONFIGURATION HARDWARE
Explanation: An error occurred while activating the Channel
Reconfiguration Hardware (CRH); see message IEA9701.
System Action: If CRH was invoked by Alternate CPU
Recovery (ACR), ACR processing continues as if CRH were not
available.
If CRH was invoked due to a Vary Channel command, the
channel is not brought online.
Operator Response: Notify your IBM representative.
Problem Determination:· Print SYSl.LOGREC.
Section 5: lEA Messages - Supervisor
5-25
4
IEA9721
CHANNEL RECONFIGURATIONHARDWARE
DEACTIVATED
Explanation: The Channel Reconfiguration Hardware (CRH) is
no longer being used (see message IEA9701) because of one
of the following actions:
• The operator issued a Vary CPU command that brought the
offline GrU back online.
• The operator issued a Vary CPU command that brought the
offline the last channel attached to the offline CPU.
System Action: System processing continues.
Operator Response: None, since the operator has caused the
system action.
IEA9731
MSC AT dd DOES NOT INITIALIZE, RC == xxx
Explanation: During system initialization, the alternate MSC at
the unit address shown is online. But it does not respond
properly to an initialize order. It returned the reason code
shown.
System Action: System initialization continues, as does MSSC
Initialization. MSC backup is not available.
Operator Response: Probable 3850 hardware error. The 3850
can be used without backup if this is acceptable.
Problem Determination: Table I, Item 2
IEA9741
NO 3850. MODULE xxxxxxxx NOT FOUND
Explanation: During system initailization, the search for the
module name shown was unsuccessful.
System Action: The 3850 is not available. The message
IEA9811 follows.
Operator Response: Inform the system programmer.
Programmer Response: Ensure that all MSSC modules have
been included in the appropiate libraries.
Problem Determination: Table I, items 2, 17a and 17b.
IEA9751
NO 3850. NO MSC ONLINE
Explanation: During system initialization an MSC is not online;
therefore the 3850 cannot be used.
System Action: The 3850 is not available. The message
IEA9811 follows.
Operator Response: To use the 3850, make sure that at least
one MSC is online before reinitializing the systems.
Problem Determination: Table I, item 2.
IEA9761
MSC AT ddd NOT ONLINE
Explanation: The alternate MSC, for the 3850 at unit address
ddd, is not online.
System Action: The 3850 initialization and other system
initialization continues without the backup capability of the
alternate MSC.
Operator Response: If the alternate MSC is desired vary it
online.
Problem Determination: None
IEA9771
NO 3850. NO MSC INITIALIZED. [MSC ddd REAS
CODE == xxx]
Explanation: During system initialization, no MSC returned a
satisfactory response for attempts to initialize this host CPU's
interface to the MSC. Return codes from the MSC [or MSCs]
are shown in the message with the corresponding unit address.
System Action: The 3850 is not available. Message IEA9811
follows.
Operator Response: Probable 3850 hardware error. Do not
initiate jobs that require the 3850.
IEA9781
PURGE 3850 AT SYSTEM INITIALIZATION TIME
FAILED, RC == xxx
Explanation: The MSC returned the 3850 code, shown upon
the request for purge (from system parameters), during system
initialization.
System Action: System initialization continues, as does the
3850 initialization.
Operator Response: Inform the system programmer, who will
investigate the meaning of the return code.
Problem Determination: Table I, item 2.
IEA9791
NO 3850. ASSOCIATE FAILED, RC == xx
Explanation: During system initialization for a tightly-coupled
MP host pair, attempts to inform the MSC of the association
failed. RC == xxx incicates the reason for the failure.
System Action: The 3850 is not available. Message IEA9811
follows.
Operator Response: Inform the system programmer that a
probable configuration error has occurred.
Programmer Response: Check the Table Create utility
specifications. This CPU may not be defined as a candidate for
a tightly-coupled multiprocessing pair member. See OS/VS
Message Library: Mass Storage System (MSS), GC38-1000 for
explanation of reason codes.
Problem Determination: Table I, item 2.
IEA9801
NO 3850. DISASSOCIATE FAILED, RC == xxx
Explanation: During system initialization, the DISASSOCIATE
CPU command to the 3850 failed. xxx specifies the reason for
failure.
System Action: The 3850 is not available. The message
IEA9811 follows.
Operator Response: Do not initiate jobs that require the 3850.
Inform the system programmer. See OS/VS Message Library:
Mass Storage System (MSS), GC38-1000, for explanation of
reason code.
Problem Determination: Table I, item 2.
IEA9811
NO 3850. REPLY U TO CONTINUE WITHOUT 3850
OR REIPL
Explanation: For the reason described in the preceding
message (either IEA9741, IEA9751, IEA9771, IEA9791, or
IEA9801), the 3850 cannot be used during this IPL.
System Action: The system waits for the operator's response.
Operator Response: If the IPL cannot continue without the
3850, correct the condition specified in the preceding message
and relPL. If the IPL can continue without the 3850, reply ·U·.
The IPL will continue with any system resources obtained for
the 3850 programming support freed.
Problem Determination: Refer to the problem determination of
the preceding message on the operator console.
IEA9821
INVALID REPLY TO IEA9811. REPLY U OR REIPL
Explanation: The reply to IEA981 is invalid. The system
expects a •U·.
System Action: The system waits for the operator's response.
Operator Response:. To continue this IPL without the 3850,
reply ·U·. Otherwise, make the 3850 available and re-IPL.
Problem Determination: None.
IEA9831
NO 3850. IEAVNPC2 LOAD FAILED, ABEND
CODE == XXX
Explanation: During system initialization, the module IEAVNP02
could not be loaded by the alternate entry point IEAVNPC2.
System Action: The 3850 is not available. System initialization
continues.
5-26
VS2 System Messages (VS2 Release 3.7)
VS2.03.810
Operator Response: Inform system programmer.
Programmer Response: Investigate the load failure according
to the abend code from load shown in this message.
Problem Determination: Table I, items 2, 17a and 17b.
disconnected and, if so, disconnect DSS. Then issue a Vary
Channel command to bring the desired channels online to the
offline· CPU.
IEA9851
IEA9901
UNABLE TO UNLOAD MSS VOLUME ser FROM Vxxx
- RC == ret.
Explanation: Due to a ptevious error (see messages IEA8661,
IEA8541, and IEA9861), the system "ttempted to unload MSS
volume ser from device xxx. The unload failed; ret represents
the failure reason code. See OS/VS Message Library: Mass
Storage System (MSS) Messages, GC38-1000 for an
explanation of the reason code.
System Action: The VATLSTxx entry specifying that particular
volume is ignored. Processing continues with the remaining
VATLSTxx entries.
Operator Response: None.
Programmer Response: Use the return code to determine the
problem with 3850 Mass Storage System (MSS).
IEA9861
MSS VOLUME ser REQUIRED ON Vxxx.
Explanation: A VATLSTxx entry specified that an MSS volume
ser was to be mounted on device xxx. A volume with a
different volume serial number was found on xxx.
System Action: The system unloads the volume presently on
xxx and mounts ser on xxx.
Operator Response: None
IEA9871
UNABLE TO MOUNT MSS VOLUME ser ON Vxxx RC == ret.
Explanation: An attempt to mount an MSS volume ser on
device xxx failed, with the return code ret from 3850 Mass
Storage System (MSS).
System Action: The VATLSTxx entry specifying that particular
volume is ignored. Processing continues with the remaining
VATLSTxx entries.
Operator Action: None
Programmer Action: Determine the cause of the problem by
using OS/VS Message Library: Mass Storage System (MSS)
reason Messages, GC38-1000 to obtain an explanation of
codes.
IEA9881
PREFERRED AREA HAS EXPANDED.
RECONFIGURABILITY MAY BE IMPAIRED.
Explanation: Real Storage Management assigned a page of
SQA, nonswappable LSQA, or a nonswappable long-term fixed
page to a real frame in the nonpreferred area. A storage unit
encompassing all or part of the non-preferred area may not
reconfigure successfully. The Display Matrix command can be
used to determine the remaining non-preferred area.
System Action: The storage unit is designated as preferred
storage, and thus eligible for additional long-term resident
pages.
IEA9891
;/
Operator Response: Determine whether DSS can be
DSS ACTIVE - CANNOT ACTIVATE CHANNEL
RECONFIGURATION HARDWARE
Explanation: In OS/VS2 Release 2, the Dynamic Support
System (DSS) and Channel Reconfiguration Hardware (CRH)
(see message IEA9701) are mutually exclusive. The CRH
init,alization procedure has determined that DSS is active and
therefore cannot allow CRH to be activated.
System Action: If CRH was invoked by Alternate CPU
Recovery (ACR), ACR processing continues as if CRH were not
available.
If CRH was invoked dure to a Vary Channel command, the
channel is not brought online.
NUCMAP NOT COMPLETED I xxx---xxx
l)xxx---xxx == MAX SIZE EXCEEDED - NUCMAP
size exceeded allocated space on SYSl.bSSVM. Only the first
and last five pages are written and available 2)xxx---xxx ==
SPACE NOT AVAILABLE -Unable to obtain enough storage to
build NUCMAP. NUCMAP empty except for a dummy entry.
System Action: Normal processing continues.
Programmer Response: l)Make sure the number of ESD
entries in nucleus are correct. 2)Make sure that unneeded
storage space during NIP is freed.
Problem Determination: Table 1, item 2, 17b, 27, and 29.
Explanation:
IEA9911
DSS INOPERATIVE, NO NUCMAP AVAILABLE
Explanation: There is not enough storage available to build
NUCMAP and the NUCMAP dummy entry. (DSS must have a
NUCMAP dummy entry.)
System Action: Normal processing continues.
Programmer Response: Make sure that all unneeded storage
space during NIP is freed.
Problem Determination: Table 1, items 2, .17b, and 29.
IEA9961
READ FOR JFCB/JFCBE FAILED. STANDARD
DUMP FORMAT ASSUMED.
Explanation: During ABEND processing, modules IEAVTABD
and IEAVAD01 issued the QMNGRIO macro instruction to
determine the requested format of the dump. However, a
failure was encountered while attempting to read the JFCB or
JFCBE.
System Action: Module IEAVTABD will initialize the dump DCB
to dump in the standard format of 120 characters per line, and
module IEAVAD01 will use the DCB set up by IEAVTABD for
the dump. Processing continues.
Programmer Response: None.
Problem Determination: Table I, items 1, 13, 15.
I.EA9971
READ FOR JFCB/ JFCBE FAILED, DUMP CANCELLED.
Explanation: Module IEAVADOl issued the QMNGRIO macro
instruction to determine the requested format of the SNAP or
ABEND dump. However, the routine called by IEAVAD01 failed
while attempting to read the JFCB or JFCBE.
System Action: The dump is canceled, and a return code of
X'08' is returned to the caller.
Programmer Response: Rerun the job.
Problem Determination: Table I, items 1, 13, 15.
IEA999W
ADDRESS TRANSLATION ERROR IN MASTER
MEMORY
Explanation: The program check first level interrupt handler
has encountered recursive addressing translation exceptions.
There is a possibility that the segment table or common page
tables for the master scheduler's address space have been
initialized incorrectly, or have been overlaid.
System Action: All CPUs are placed in a wait state.
Operator Response: Probable software error. Take a
stand-alone dump. Restart the system and execute IFCEREPO
to obtain a listing of LOGREC.
Problem Determination: Table I, items 11, 18, 29.
Section 5: I EA Messages - Supervisor
5-27
5-28
VS2 System Messages (VS2.03.810)
Section 6: Data .Management Messages (lEe)
Component Name
IEC
Program Producing Message
Data management.
Audience and Where Produced
For operator: console.
Message Format
xx IECnnns text
xx
Message reply identification (absent, if operator reply not required).
nnn
Message serial number, which is coded to indicate the data management function:
Onn End of volume
lnn Open
2nn Close
3nn Catalog management
4nn Checkpoint/ restart
5nn Open/Close/EOV /DADSM common messages
6nn Direct access device space management (DADSM)
7nn Tape label creation
8nn BTAM
9nn Problem Determination and 3505/3525
s
Type code:
A
Action; operator must perform a specific action.
D
Decision; operator must choose an alternative.
E
Eventual action; operator must perform action when he has time.
I
Information; no operator action is required.
text
Message text.
Comments
dsn
ser
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IECOOIA
Data set name will not appear in the message text if the JSCB is not available.
Volume serial number will not appear in the message text for unit record equipment.
M ddd,ser[,jjj,sss] [,dsn]
Explanation: M indicates that a stack of documents, identified
by ser, is to be readied on 1419/1275 unit ddd.
jjj indicates the job requesting the volume and sss indicates
the job step requesting the volume. if these fields appear in the
message text.
If a MONITOR DSNAME command is active, dsn indicates the
data set requesting the volume.
System Action: The job step waits for the operator to ready
the documents or until the task reaches TIMEOUT.
Operator Response: Ready the indicated documents on the
device.
Problem Determination: Table I, items 1, 2, 3, 4, Sa, 13, 15,
16, 29. Table II, Format 3.
IEC003E
R ddd,ser,jjj,sss [,SPACE = prm][,dsn]
Explanation: R indicates that the volume on device ddd is to
be demounted and retained near the computer for use in the
near future:
• If ser is a 6-digit number, it is the serial number of the
volume, which contains labels.
• If ser begins with a slash or L, the volume to be demounted
is unlabeled; the number after the slash or L is an internal
serial number assigned by the system to an unlabeled
volume. If ser begins with L, the number after the L is of
the form xxxyy, where xxx is the data set number and yy is
the volume sequence number of the data set.
In the message text, labtyp and den appear only for tape
volumes. The volume has the type of label specified by labtyp:
SL for standard label, AL for ANSI label, NSL for nonstandard
label, or NL for no label; the density is as specified by den.
The volume is being used by step sss of job iii.
For direct access volumes, if a MONITOR SPACE command
is active, the field
SPACE = cccc,tttt,aaaa/yyyy,zzzz is specified:
cccc
Total number of free cylinders on the volume.
tttt
Total number of tracks in addition to the free cylinders.
aaaa
Areas or extents dividing the cylinders and tracks.
yyyy
Maximum number of contiguous free cylinders of the largest
extent within the total remaining space.
zzzz
Number of tracks in addition to the free cylinders of the
largest extent within the total remaining space.
If an error occurred during the listing of the parameters in
the SPACE field, one of the following messages is specified:
• LSPACE-PERMANENT I/O ERROR
• LSPACE-NON-STANDARD OS VOLUME
• LSPACE-NOT A DIRECT ACCESS VOL
• LSPACE-INVALlD PARAMETER
If a MONITOR DSNAME command is active, data set dsn
contained on the volume is also specified in the message text.
System Action: For tape, the system rewinds and unloads the
tape volume.
Operator Response: Demount the volume. Mark the serial
number, label type; and density on the volume, if they are not
so marked. (The internally assigned number should appear
externally on the volume in case a subsequent step needs the
volume; for the subsequent mounting, the system will specify
the volume by the internally assigned number.) Then retain the
volume near the computer. If LSPACE-PERMANENT I/O
Section 6: IEC Messages - Data Management
6-1
41
ERROR was in the message, a permanent I/O error was
encountered while trying to read the VTOC. Execute the
IEHLlST utility program to list the VTOC of this volume. If
errors occur, take appropriate action as indicated in the
message. If LSPACE-NOT A DIRECT ACCESS VOL or
LSPACE-INVALID PARAMETER was in the message, perform
the problem determination action.
Problem Determination: Table I, items 2, 29.
IEC0061
UNABLE TO ACTIVATE A VIO DATASET DURING
RESTART PROCESSING
Explanation: The Auxiliary Storage Manager (ASM) was unable
to reset its control blocks for a VIO data set to its status at
the time it was journaled. This message should be followed by
message IEF086!.
System Action: Restart processing is terminated.
Programmer Response: See message IEF0861 and rerun the
job.
Problem Determination: Table I, items 1, 3, 4, 29.
IEC0111
031-rc,jjj,sss,ddn[ -#],ddd,ser,dsn
Explanation: An input/output error occurred during the
execution of a QISAM CLOSE macro instruction issued by task
termination (the problem program returned control to the
supervisor without issuing a CLOSE macro instruction). In the
message text, 031-rc associates this message with system
completion code 031 and with return code rc. Other fields in
the message text are:
jii
job name
sss
step name
ddn[ -#J
DOna me (followed by a concatenation number if it is part of
a concatenation and not the first DO statement in the
concatenation).
ddd
device address
ser
volume serial number
dsn
data set name
The values of rc and their meanings are ~l follows:
Return
Code
Meaning
08
An input/output error occurred during execution of a
CLOSE macro instruction for an ISAM data set opened
for QISAM mode while task termination was in
progress.
System Action: The task is terminated and no SYNAD exit is
taken because the user program did not execute a CLOSE
macro instruction for the ISAM data set opened for QISAM
processing prior to returning control to the supervisor.
Programmer Response: If the task was in the process of
loading the ISAM data set, the data set must be reloaded. If
the task was updating records (QISAM scan mode), any
records waiting to be rewritten when the error occurred will
not be rewritten. To ensure that the SYNAD routine gets
control, issue a CLOSE macro instruction for the ISAM data set
prior to returning control to the supervisor.
Problem Determination: Table I, items 1, 3, Sa, 15, 29.
IECOl4E
0 ddd
Explanation: 0 indicates that the volume on device ddd is to
be demounted. The control program has determined that this
volume, mounted in response to an earlier mount message,
either:
6-2
VS2 System Messages (VS2 Release 3.7)
• Contains labels that cannot be read due to a permanent
input/output error.
• Contains no label or nonstandard labels when standard
labels were specified.
• Contains standard labels when no labels or nonstandard
labels were specified.
• Contains labels that .are written in a density other than the
density specified.
System Action: The system rewinds and unloads the tape
volume.
Operator Response: Demount the volume. The system will then
request that a new volume be mounted. Mount a volume with
the correct density and label type.
Problem Determination: Table I, items 1, 2, 3, 4, Sa, 16, 28,
29. Table II, Format 3.
IECOISI
A37 -rc,mod,jjj,sss,ddn[ -#],ddd,ser
Explanation: The error occurred during end-of-volume
processing. In the message text, A37 -rc associates this
message with system completion code A37 and with return
code rc. Other fields in the message text are:
jjj
job name
sss
step name
ddn[ -#J
DDname (followed by a concatenation number if it is part of
a concatenation and not the first DO statement in the
concatenation).
ddd
device address
ser
volume serial number
mod
The name of the module in which the error occurred.
The values of rc and their meanings are as follows:
Return
Meaning
Code
An SVC 55 (EOV) was issued, usually by a CHECK,
04
GET, or PUT routine, against a DCB which was not
open.
08
DEB does not point to DCB.
System Action: The task is terminated unless the error is to
be ignored as specified in the DCB ABEND exit routine.
Programmer Response: Probable user error. An open DCB may
have been partially overlaid, closed by the user in a SYNAD
routine, or automatically closed by a previous end-of-volume
error where ignore was specified in the DCB ABEND exit
routine. Correct the errors causing abnormal termination as
indicated by the return code in the message text. Rerun the
job.
Problem Determination: Table I, items 1, 4, Sa, 15, 16 29.
Table II, Format 3.
IEC0201
.
OOI-rc,mod,jjj,sss,ddn,[ -#][ddd,ser,dsn]
\NO ERROR HANDLING, (SYNAD), EXIT SPECifiED!
ERROR OCCURRED WHILE CLOSING DATA SET
NON-ACCEPTABLE ERROR
DCB EROPT = ABE OR AN INVALID CODE,
AND lOR NO SYNAD EXIT SPECifiED
GET ISSUED AfTER END-Of-fiLE
Explanation: A 001 system completion code was issued for
step sss of job jii for one of the following reasons:
• If rc is 1,- an I/O error occurred during BDAM CREATE,
BSAM, BISAM, QSAM, or BDAM and no SYNAD exit was
specified by the user.
• If rc is 2, an error was encountered while attempting to
close the data set.
• If rc is 3, for QSAM, an error was encountered that could
not be accepted.
• If rc is 4, for QSAM, ABE or an invalid value for EROPT
parameter in the DCB and/or no error handling (SYNAD)
exit was specified.
• If rc is 5, for QSAM, a GET was issued after end-of-file.
In the message text, ddn is the data definition name of the DD
statement describing the data set, ddd is the unit name, ser is
the serial number of the volume, and dsn is the data set name.
mod is the name of the module in which the error occurred.
Note: The unit address (ddd), volume serial number (ser), and
data set name (dsn) fields do not appear in the message text
when it applies to a SYSIN/SYSOUT data set.
Note: System completion code 001 is also issued when the
logical record length and block specified in the data control
block or DD statement differ from the logical record length and
blocksize that occur in the data set.
System Action: A WTP message is issued to give the ABEND
and return codes, pertinent control blocks are recorded on the
GTF data set, and the job abnormally terminates.
Programmer Response: None.
Problem Determination: Table I, items 1, 3, 25a, 29.
IEC0211
NO SPACE IN PASSWORD DATA SET
Explanation: I The password data set on the system residence
device is full. No additional entries may be added until entries
are deleted or a new password data set is created.
System Action: The job step is terminated.
Operator Response: Inform the programmer responsible for the
installation that you have received this message.
Programmer Response: Delete outdated entries in the present
password data set or create a new password data set.
Problem Determination: Table I, items 2, 25a, 29.
IEC0221
137 -rc,mod,jjj,sss,ddn[ -#],ddd,ser ,dsn
Explanation: The error occurred during end-of-volume on a
magnetic tape. In the message text, 137-rc associates this
message with system completion code 137 and return code rc.
Other fields in the message text are:
jjj
job name
sss
step name
ddn[ -#1
DDname (followed by a concatentation number if it is part
of a concatenation and not the first DD statement in the
concatenation).
ddd
device address
ser
volume serial number
mod
The name of the module in which the error occurred.
dsn
data set name
The values of rc and their meanings are as follows:
Return
Code
Meaning
An I/O error occurred while writing an end-of-volume
04
label or a tape mark.
An I/O error occurred while positioning the tape in
08
preparation for label processing.
An I/O error occurred reading a trailer label for a data
OC
set opened with the option INPUT or INOUT. If the
data set was opened with the option RDBACK, the I/O
error occurred reading the header label.
10
An I/O error occurred while positioning a magnetic
tape at the end of the data set.
14
An I/O error occurred reading header labels for a data
set opened for INPUT or INOUT. If the data set was
opened for RDBACK, the error occurred while reading
the trailer label.
18
An I/O error occurred while positioning a magnetic
tape data set at the first data record.
lC
An invalid trailer label was read during end-of-volume
proceSSing. Execute the IEBPTPCH utility program to
determine the contents of the volume. Take any
corrective· action necessary to recreate the volume so
that the information may be accessed.
20
An invalid header label was read during
end-of-volume processing. Execute the IEBPTPCH
utility program to determine the contents of the
volume. Take any corrective action necessary to
recreate the volume so that the information may be
accessed.
24
A specific volume serial number was specified for the
second or subsequent volume of an output data set on
magnetic tape. During EOV processing, it was
discovered that the expiration date (from the HDRI
label of the first data set currently on the specified
volume) had not passed. When requested to specify
whether the volume could be used in spite of the
expiration date, the operator did not reply 'U'. Ask the
operator to reply 'U' or specify another volume serial
number.
System Action: The task is terminated unless the error is to
be ignored as specified in the DCB ABEND exit routine. If the
error is to be ignored, the system will attempt to close the
DCB before returning to the user.
Programmer Response: Probable user error unless an I/O
error has occurred. Correct the errors that caused the
abnormal termination as indicated by the return code in the
message text. Then resubmit the job.
If I/O error has occurred, a defective volume or device may be
the cause. Rerun the job, specifying a differentvolume or
device. If a scratch volume was being used when the I/O error
occurred, request a different volume. If that does not solve the
problem, request a different device in the UNIT parameter of
the DD statement. If a specific volume is needed, try
requesting a different device in the UNIT parameter of the DD
statement. Rerun the job.
Problem Determination: Table I, items 1, 4, Sa, 16, 29. Table
II, Format 3.
IEC0231
237-rc,mod,jjj,sss,ddn[ -#],ddd,ser,dsn
Explanation: The error occurred during end-of-volume. In the
message text, 237-rc associates this message with system
completion code 237 and with return code rc. Other fields in
the message text are:
Hi
job name
sss
step name
ddn[ -#J
DDname (followed by a concatenation number if it is part of
a concatenation and not the first DD statement in the
concatenation).
ddd
device address
ser
volume serial number
I
!
Section 6: IEC Messages - Data Management
6-3
mod
The name of the module in which the error occurred.
dsn
data set name
The values of rc and their meanings are as follows:
Return
Meaning
Code
The block count in the DCB does not match that in
04
the trailer label. A block of data has been missed or
skipped (probably due to a hardware error).
The DSNAME in a header label does not match that i'n
08
the JFCB on the second or subsequent volume of a
magnetic tape data set. Verify that the correct volume
and DSNAME were specified.
System Action: The task is terminated unless the error is to
be ignored as specified in the DCB ABEND exit routine. If the
error is to be ignored, the system will attempt to close the
DCB before returning to the user.
Programmer Response: Probable user error unless hardware
error has occurred. Correct the errors causing the abnormal
termination as indicated by the return code in the message
text. Then rerun the job.
Problem Determination: Table I, items 1, 4, Sa, 16, 29. Table
II, Format 3.
IEC0241
337-rc,mod,jjj,sss,ddn[ -#],ddd,ser,dsn
Explanation: The error occurred when the end of a data set
was reached. In the message text, 337 -rc associates this
message with system completion code 337 and with return
code rc. Other fields in the message text are:
iii
job name
sss
step name
ddn[ -#J
DOna me (followed by a concatenation number if it is part of
a concatenated data set and not the first DO statement in
the concatenation).
ddd
device address
ser
volume serial number
mod
The name of the module in which the error occurred.
dsn
data set name
The values of rc and their meanings are as follows:
Return
Meaning
Code
The end of a data set was reached, but no
04
end-of-data-set routine (EODAD) was specified in the
DCB.
No EODAD specified in the DCB for DO DUMMY data
08
set.
System Action: The task is terminated.
Programmer Response: Probable user error. Correct the errors
causing the abnormal termination as indicated by the return
code in the message text. Then rerun the job.
Problem Determination: Table I, items 1, 4, Sa, 16, 29. Table
II, Format 3.
IEC0251
437-rc,mod,jjj,sss,ddn[ -#],ddd,ser,dsn
Explanation: The error occurred at an end-of-volume. In the
message text, 437 -rc associates this message with system
completion code 437 and with return code rc. Other fields in
the message text are:
iii
job name
6-4
VS2 System Messages (VS2 Release 3.7)
sss
step name
ddn[ -#J
DDname (followed by a concatenation number if it is part of
a concatenation and not the first DO· statement in the
concatenation).
ddd
device address
ser
volume serial number
mod
The name of the module in which the error occurred.
dsn
data set name
The values of rc and their meanings are as follows:
Return
Code
Meaning
When FEOV was issued, it was found that the DCB
08
pointer was invalid. Correct any errors that may have
caused the DCB to be invalid.
OC
DEB not in DEB table.
System Action: The task is terminated unless the error is to
be ignored as specified in the DCB ABEND exit routine. If the
error is to be ignored, the system will attempt to close the
DCB before returning to the user.
Programmer Response: Probable user error. Correct the errors
causing the abnormal termination as indicated by the return
code in the message text. Then rerun the job.
Problem Determination: Table I, items 1, 4, Sa, 16, 29. Table
II, Format 3.
IEC0261
637 -rc,mod,jjj,sss,ddn[ -#],ddd,ser,dsn
Explanation: The error occurred during end-of-volume for a
data set on magnetic tape or an end-of-volume during
concatenation. In the message text, 637 -rc associates this
message with system completion code 637 and with return
code rc. Other fields in the message text are:
jjj
job name
sss
step name
ddn[-#J
DDname (followed by a concatenation number if it is part of
a concatenation and not the first DO statement in the
concatenation).
ddd
device address
ser
volume serial number
mod
The name of the module in which the error occurred.
dsn
data set name
The values of rc and their meanings are as follows:
Return
Meaning
Code
04
An I/O error occurred while reading a tape label,
writing a tape mark, or positioning a magnetic tape
volume.
08
Following user trailer label processing, an I/O error
occurred positioning a magnetic tape.
Concatenation of data sets with unlike attributes was
OC
detected, but not specified in the DCB (i.e.,
DCBOFLGS bit 4 is 0).
10
An I/O error occurred while positioning a magnetic
tape data set that was opened with the option INPUT
"',
or INOUT to be read backward. If it is a tape with
standard labels, the error occurred positioning at the
labels. If it is a tape with no labels, the error occurred
positioning at the data.
An I/O error in tape positioning occurred for a data
14
set with the LEAVE option specified in the OPEN
macro instruction or with the LEAVE option specified
in the FEOV macro instruction.
An I/O error in tape positioning occurred for a data
18
set opened with the REREAD option.
An I/O error occurred in tape positioning when FEOV
lC
is issued for a data set with DISP = PASS and no
OPEN option 2 specified.
An I/O error occurred rewinding a scratch magnetic
24
tape volume. Either FEOV with a REWIND option was
issued, or no OPEN option 2 was specified when the
DISP was not PASS.
2C
An I/O error occurred while rewinding a magnetic tape
volume prior to verifying the volume label.
34
An I/O error occurred during end-of-volume
processing while reading the volume label of a
magnetic tape volume.
38
An I/O error occurred while positioning a tape without
a label or with nonstandard labels.
3C
An I/O error occurred while positioning a
concatenated magnetic tape data set. If it has
standard labels, the error occurred positioning at the
labels. If it has no labels, the error occurred
positioning at the data.
40
An I/O error occurred while positioning a magnetic
tape data set that was opened with the option INPUT
or INOUT to be read forward. If it is a tape with
standard labels, the error occurred positioning at the
labels. If it is a tape with no labels, the error occurred
positioning at the data.
44
An I/O error occurred while checking sense bytes to
determine if a file protect ring is on a magnetic tape
containing a data set opened for INOUT.
An I/O error occurred in tape positioning following
4C
user header label processing.
System Action: The task is terminated unless the error is to
be ignored as specified in the DCB ABEND exit routine. If the
error is to be ignored, the system will attempt to close the
DCB before returning to the user.
Programmer Response: Probable user error unless an I/O
error has occurred. Correct the errors causing abnormal
termination as indicated by the return code in the message
text. Then rerun the job.
If an I/O error has occurred, a defective volume or device may
be the cause. Save the output from the failing job to aid in the
analysis of the problem.
Rerun the job specifying a different volume or device. If a
scratch volume was being used when the I/O error occurred,
request a different volume. If that does not solve the problem,
request a different device in the UNIT parameter of the DO
statement. If a specific volume is needed, try requesting a
different device in the UNIT parameter of the DO statement.
Rerun the job.
Problem Determination: Table I, items 1, 4, Sa, 16, 29. Table
II, Format 3.
IEC0271
737 -rc,mod,jjj,sss,ddn[ -#],ddd,ser,dsn
Explanation: The error occurred during end-of-volume or
during allocation of a secondary quantity of direct access
storage as requested in the SPACE parameter of the DO
statement for the data set. In the message text, 737 -rc
associates this message with system completion code 737 and
with return code rc. ther fields in the message text are:
jjj
job name
sss
step name
ddn[ -#J
DOna me (followed by a concatenation number if it is part of
a concatenation and not the first DO statement in the
concatenation).
ddd
device address
ser
volume serial number
mod
The name of the module in which the error occurred.
dsn
data set name
The values of rc and their meanings are as follows:
Return
Meaning
Code
04
An I/O error occurred reading or writing a DSCB
during end-of-volume processing.
08
An I/O error occurred reading a direct access volume
label during end-of-volume processing.
OC
An I/O error occurred reading the DSCB for a
concatenated partitioned data set.
10
An I/O error occurred writing a file mark for a data
set on a direct access device.
14
An I/O error occurred while reading a DSCB preparing
for user trailer label processing.
lC
An I/O error occurred while reading a format-3 DSCB.
24
A missing member name was detected by BLDL while
searching for the TTR of a concatenated member.
2C
The error occurred when a FEOV macro instruction
was issued while attempting to write a file mark at the
end of the data. The DCBFDAD field in the DCB
indicated an extent number in the DEB greater than
the number of extents in the data set. Consequently, it
could not be determined where the file mark should
have been written.
34
An error occurred during a MOUNT, DEMOUNT,
ACQUIRE or RELINQUISH operation on a Mass Storage
System· (MSS) virtual volume. See message IEC0661.
38
The MSS hardware mounted a virtual volume other
than the one requested.
System Action: The task terminates unless the error can be
ignored as specified in the DCB ABEND exit routine. If the
error can be ignored, the system attempts to close the DCB
before returning to the user.
Programmer Response: If an I/O error has occurred, a
defective volume or device may be the cause. Save the output
from the failing job to aid in the analysis of the problem.
Rerun the job specifying a different volume or device. If a
scratch volume was being used when the I/O error occurred,
request a different volume. If that does not solve the problem,
request a different device in the UNIT parameter of the DO
statement. If a specific volume is needed, try requesting a
different device in the UNIT parameter of the DO statement.
Rerun the job.
If return code is 2C, probable user error. Make sure that the
DCBFDAD field is not being invalidated before the FEOV macro
instruction is issued.
Problem Determination: Table I, items 1, 4, Sa, 16, 29. Table
II, Format 3.
Section 6: lEe Messages - Data Management
6-5
VS2.03.80S
IEC0281
837-rc,mod,jjj,sss,ddn[ -#],ddd,ser,dsn
Explanation: The error occurred during end-of-volume for a
sequential data set. In the message text, 837 -rc ass.ociates
this message with system completion code 837 and with return
code rc. Other fields in the message text are:
iii
job name
sss
step name
ddn[ -#J
DDname (followed by a concatenation number if it is part of
a concatenation and not the first DO statement in the
concatenation).
ddd
device address
ser
volume serial number
mod
The name of the module in which the error occurred.
dsn
data set name
The values of rc and their meanings are as follows:
Return
Meaning
No address was found for the JFCB extension in the
SWA. Specify more volume serial numbers for a larger
volume count in the VOL parameter of the DO
statement.
OC
The indicated tape volume whose serial number is ser
was requested and mounted on unit ddd but another
data set was processing the volume.
System Action: The task is terminated unless the error is to
be ignored as specified in the DCB ABEND exit routine. If the
error is to be ignored, the system will attempt to close the
DCB before returning to the user.
Programmer Response: Execute job step again.
Problem Determination: Table I, items 1, 4, 5a, 16, 29. Table
II, Format 3.
Code
08
IEC0291
937 -rc,mod,jjj,sss,ddn[ -#],ddd,ser,dsn
Explanation: The error occurred at an end-of-volume. This
abnormal termination condition results from an unsatisfactory
response by the operator to message IEC254D, IEC255D, or
IEC256A. These messages are issued when a checkpoint data
set is created, modified, or deleted in installations that wish to
ensure the security of their checkpoint data sets. External
labeling and suggested installation procedures are discussed in
OS/VS Checkpoint/Restart, GC26-3784. In the message text,
937-rc associates this message with system completion code
937 and with return code rc. Other fields in the message text
are as follows:
iii
job name
sss
step name
ddn[ -#J
DDname (followed by a concatenation number if it is part of
a concatenation and not the first DO statement in the
concatenation).
ddd
device address
ser
volume serial number
mod
The name of the module in which the error occurred.
dsn
data set name
6-6
VS2 System Messages (VS2.03.S0S)
The values of rc and their meanings ate as follows:
Return
Meaning
1) If the data set is opened for input, the second or
succeeding volume of a secure· checkpoint data set
has been found to be insecure.
2) If the data set is opened for output, the second or
succeeding volume of a secure checkpoint data set
could not be made secure.
14
During EOV processing, the second or subsequent
volume of a noncheckpoint data set was found to be a
secure checkpoint data set.
An unauthorized user has issued a FEOV or an EOV
18
SVC against a checkpoint data set open with a
security interface.
1C
An error was detected after mounting a new volume
for a data set that spans volumes. The extents listed
in the data extent block (DEB) and in the data set
control block (DSCB) do not match.
The indicated tape volume whose serial number is ser
20
contained ASCII labels. The volume accessibility byte
(offset X'OA' in the volume label) is not blank. This
indicates that the label was not created on an IBM
system or that it was created by the user. If the
volume accessibility is not blank, the tape cannot be
used on an IBM system.
A specific volume serial number was specified for the
24
second or SUbsequent volume of an output data set on
magnetic tape. During EOV processing for this volume,
it was determined that the first data set currently on
the specified volume was password protected, and the
protection mode indicator in the HDR1 label did not
match that in the JFCB. Supply the password to the
operator or select another volume.
At end of volume, the caller is not authorized to use
28
the data set on the new volume.
RACF definitions are inconsistent. A previously
2C
allocated multi-volume direct access data set is being
processed for output. The first volume was
RACF-defined, but the current volume is not
RACF - indicated.
An end of volume occurred and the data set on the
30
new volume is RACF-indicated in the Format-1 DSCB;
however, the data set on the new volume is not
RACF-defined.
34
A VSAM data space requested at end of volume is
RACF-defined.
38
RACF failed to add a volume to an existing
RACF-defined, direct access data set while the data
set was being extended to a new volume.
3C
RACF definitions are inconsistent. A previously
allocated multi-volume direct access data set is being
processed for output. The first volume was not
RACF-defined, but the current volume is
RACF - indicated.
System Action: The task is terminated unless the error is to
be ignored as specified in the DCB ABEND exit routine. If the
error is to be ignored, the system will attempt to close the
DCB before returning to the user.
Programmer Response: If the return code is 10 and the data
set is open for input, one of the checkpoint data set volumes
has lost its secure status. Contact the installation personnel to
verify the secure status of the checkpoint volumes. If all
volumes are found to be secure, rerun the job and make sure
the operator responds correctly when the system requests the
status of each volume. Otherwise, rerun the job which creates
the checkpoint data set.
Code
10
VS2.03.808
If the return code is 10 and the data set is open for output,
one of the volumes specified on the checkpoint data set DD
statement could not be made secure. Contact the installation
personnel and verify the eligibility of all volumes, then rerun
the job.
If the return code is 14, probable user error. Contact the
installation personnel to ensure that the status of each data
set volume is as expected.
If the return code is 18, probable user error. Only
APF-authorized programs can access a secure checkpoint data
set. Remove the referenced FEOV SVC call, recompile the
program, and rerun the job.
If the return code is 1C, probable user error. Check to see if
the program incorrectly modifies the job file control block
(JFCB) of the subject data set after OPEN and before CLOSE.
Of particular interest are the JFCB data set name field and
volume serial number field.
If the return code is 20, make sure that the correct volume
was mounted. If the correct volume was mounted, the tape
volume must be recreated for use on an IBM system.
If the return code is 28, the owner of the data set must
update the RACF data set profile to permit access.
If the return code is 2C or 3C, make RACF definitions
consistent among all volumes of a multi-volume data set.
If the return code is 30, define the data set to RACF without
setting the RACF-indicated bit in the Format-1 DSCB.
If the return code is 34, delete the RACF-definition of the
VSAM data space.
If the return code is 38, the data set may have been
previously defined to RACF on the new volume. Check with the
data set owner, or inspect the data set RACF profile.
Problem Determination: Table I, items 1, 3, 4, Sa, 29, 36.
Section 6: IEC Messages - Data Management
6-6.1
6-6.2
VS2 System Messages (VS2.03.808)
IEC0301
I"
837 -rc,mod,jjj,sss,ddn[ -#],ddd,ser ,dsn
Explanation: The error occurred during end-of-volume. In the
message text, B37-rc associates this message with system
completion code B37 and with return code rc. Other fields in
the message text are:
jjj
job name
sss
step name
ddn-#
DOna me (followed by a concatenation number if it is part of
a concatenation and not the first DD statement in the
concatenation).
ddd
device address
ser
volume serial number
mod
The name of the module in which the error occurred.
dsn
data set name
The values of rc and their meanings are as follows:
Return
Code
Meaning
04
During end-of-volume processing the system had to
demount a volume in order to mount the next volume
of the data set. It was unable to demount the volume
for one of the following reasons:
• The volume was permanently resident.
• The volume was reserved.
• Another job had data sets allocated on the volume.
• There were OPEN data sets on the volume for the
failing task.
For an output data set on a direct access device, the
system might have needed to demount the volume for
one of the following reasons:
• No more space was available on the volume.
• The data set already had 16 extents, but required
more space.
• More space was required, but the volume table of
contents (VTOC) was full. If additional space were
allocated, another data set control block (DSCB)
might have been needed, but could not have been
written.
For an output data set on magnetic tape, a volume
needed to be demounted because the reflective spot
was encountered and more records were to. be written.
For an input data set on more than one volume, one
of the volumes needed to be demounted so that the
next one could be mounted, but the system was
unable to demount the volume.
08
During end-of-volume processing, the system
attempted to extend data set dsn to a volume on
which the DOS bit or the DIRF bit (bits 0 and 5
respectively in the DS4VTOCI byte of. the format-4
DSCB) was set. The VTOC for the volume could not be
converted to standard format for one of the following
reasons:
• Two data sets were allocated to the same space on
the volume.
• A split cylinder data set was located on cylinder
zero, the same cylinder as the VTOC, or the same
cylinder as a non-split cylinder data set.
• The DADSM VTOC conversion routine had been
modified (by altering CSECT IGG0325Z, as specified
in OS/VS2 DADSM Logic) to reject any sp~ce
allocation requests on a volume on which the DIRF
bit is set to one.
• Under DOS,. the alternate tracks were assigned to
cylinder zero.
OC
The indicated direct access volume ser on unit ddd
was requested to continue processing the data set,
but the. unit already contained 127 users, the
maximum number.
System Action: The task is terminated unless the error is to
be ignored as specified in the DCB ABEND exit routine .. If the.
error is to be ignored, the system will attempt to close the
DCB before returning to the user.
Programmer Response: Probable user error. For all cases,
allocate as many units as volumes required.
For the first two cases, if the volume to be demounted is
permanently resident or reserved, set up the JCL to allocate
devices that are removable.
For the third case, change the JCL to request deferred
mounting, or specify more volumes than units to prevent
sharing of required units.
For the fourth case, rewrite the program or change the JCL
insuring that there are no open data sets on volumes that
must be demounted.
For the next case (first of 08 return code), scratch one of the
data sets that has the overlapping extent.
For the next case (second of 08 return code), either scratch or
move the split cylinder data set that is causing the error.
For the next case (third of 08 return code), the VTOC can be
converted by either removing the modification to IGG0325Z or
by resetting the DIRF bit to zero and setting the DOS bit to
one and allocating a non-ISAM data set to the volume.
For the next case (last of 08 return code), the volume can
only be used under the Disk Operating System (DOS).
In all cases, correct the errors and execute the job step again.
Problem Determination: Table I, items 1, 4, 5a, 16, 2~. Table
II, Format 3.
IEC0311
037 -rc,mod,jjj,sss,ddn[ -#],ddd,ser,dsn
Explanation: The error occurred when an output operation to a
direct access device was requested. In the message text,
D37 -rc associates this message with system· completion code
D37 and with return code rc. Other fields in the message text
are:
jjj
job name
sss
step name
ddn[ -#]
DDname (followed by a concatenation number if it is part of
a concatenation and not the first DO statement in the
concatenation).
ddd
device address
ser
volume serial number
mod
The name of the module in which the error occurred.
dsn
data set name
The values of rc and their meanings are as follows:
Return
Code
Meaning
04
A data set opened for output used all the primary
space, and no secondary space was requested.
Change the JCL specifying a larger primary quantity or
add a secondary quantity to the space parameter on
the DD statement.
Section 6: IEC Messages - Data Management
6-7
System Action: The task is terminated unless the error is to
be ignored· as specified in the DCB ABEND exit routine. If the
error is to be ignored, the system will attempt to close the
DCB before returning to the user.
Programmer Response: Probable user error. Correct the errors
that caused the abnormal termination as indicated by the
return code in the message text. Rerun the job.
Problem Determination: Table I, items 1, 4, 5a, 16, 29. Table
II, Format 3.
IEC0321
E37 -rc,mod,jjj,sss,ddn[ -#],ddd,ser,dsn
Explanation: The error occurred when an output operation was
requested. The data set was on a direct access or magnetic
tape device. In the message text, E37 -rc associates this
message with system completion code E37 and with the return
code rc. Other fields in the message text are:
jjj
job name
sss
step name
ddn[ -#J
DDname number if it is part of a concatenation and not the
first DO statement in the concatenation).
ddd
device address
ser
volume serial number
mod
The name of the module in which the error occurred.
dsn
data set name
The values of rc and their meanings are as follows:
Return
Code
Meaning
A data set opened for output used all space available
04
to or on the current volume, and no more volumes
were available. Change the JCL specifying more
volumes.
• Not enough volumes were specified for the data
set, through the SER, volume count, or REF
subparameter of the VOLUME parameter of the DO
statement. When all the volumes were filled, the
program attempted to write another record.
• For a partitioned data set on direct access volume,
all space was filled when the program attempted to
write another record. (A partitioned data set can
reside on only one volume.)
• For a partitioned data set on a direct access
volume, 16 extents had been used when the
program attempted to write another record;
however, no volume was available for demounting.
On a data set opened for output, end-of-volume had
08
found a DSCB with a duplicate data set name on the
next volume, with a volume sequence number less
than that in the DEB.
• A multi-volume physical sequential data set was
being wirtten on a direct access device. All space
was filled on a volume, and an attempt was made
to obtain space on the next specified volume. Either
the space was not available on that volume or the
data set already existed on that volume.
System Action: The task is terminated unless the error is to
be ignored as specified in the DCB ABEND exit routine. If the
error is to be ignored, the system will attempt to close the
DCB before returning to the user.
6-8
VS2 System Messages (VS2 Release 3.7)
Programmer Response: Probable user error. Correct the errors
causing the abnormal termination as indicated by the return
code in the message text as follows:
For Return code 04, case 1, specify at least one more volume
than the number of volumes previously used for the data set.
For case 2, specify a different volume for the data set. For
case 3, either specify a volume for the data set, use a utility
program to reorganize the volume so that data sets will not be
fragmented (that is, no more than 16 extents used for this
data set), or change the program so that a device will be free
when a volume must be mounted.
For return code 08, either specify a new volume to continue
the data set or make sure that enough space is available on
both the current volumes and insure that the data set does not
already exist on volumes to be used containing the data set.
In all cases, rerun the job.
Problem Determination: Table I, items I, 4, 5a, 16, 29. Table
II, Format 3.
IEC0331
C37-rc,mod,jjj,sss,ddn[ -#],ser,dsn
Explanation: The error occurred when an input operation was
requested. The data set was on a direct access device. In the
message text, C37 -rc associates this message with system
completion code C37 and with return code rc. Other fields in
the message text are:
jjj
job name
sss
step name
ddn[ -#J
DDname (followed by a concatenation number if it is part of
the concatenation and not the first DO statement in the
concatenation).
ddd
device address
ser
volume serial number
mod
The name of the module in which the error occurred.
dsn
data set name
The values of rc and their meanings are as follows:
Return
Code
04
Meaning
An end~of-volume condition occurred on a data set
opened for input, but the next volume of the data set
contained more than 16 extents.
An end-of-volume condition occurred on a data set
08
opened for input, but the next volume of the data set
contained a type of split cylinder allocation that
cannot be processed under OSjVS.
System Action: The task is terminated unless the error is to
be ignored as specified in the DCB ABEND exit routine. If the
error is to be ignored, the system will attempt to close the
DCB before returning to the user.
Programmer Response: Probable user error. The volume was
created on DOS and is not compatible with OSjVS. Either
recreate the data· set under OSjVS or correct the problem by
creating it under DOS so it is compatible.
Problem Determination: Table I, items 1, 5a, 13, 25a, 29.
Table II, Format 3.
IEC0361
002-rc,mod,jjj,sss,ddn[-#][,ddd,ser,dsn]
Explanation: The error occurred while the control program was
processing a sequential data set with BSAM or QSAM, or
creating a direct data set. In the message text, 002-rc
associates this message with system completion code 002 and
with return code rc. Other fields in the message text are:
jjj
job name
sss
step name
ddn[-#l
DDname (followed by a concatenation number if it is part of
a concatenation and not the first DO statement in the
concatenation).
ddd
device address
ser
volume serial number
mod
The name of the module in which the error occurred.
dsn
data set name
Note: The unit address (ddd), volume serial number (ser), and
data set name (dsn) do not appear in the message text when
it applies to a SYSIN/SYSOUT data set.
The values of rc and their meanings are as follows:
Return
Meaning
Code
The data set was being processed using QSAM. An
04
invalid record was encountered on GET operation.
The length field of the record descriptor word (ROW)
for a variable length record specifies a value less than
4. This code also occurs if segments of variable
spanned records were not in proper sequence when
reading with QSAM.
An invalid record was encountered on a QSAM or
08
BSAM PUT or WRITE operation. The record or block
length plus the key length and required overhead add
up to more than 32,767 bytes.
An invalid record was encountered on a QSAM or
OC
BSAM PUT or WRITE operation. The record or block
length plus the key length and required overhead is
greater than the DSAD track capacity.
An invalid record was encountered on a QSAM PUT
10
operation; the data set uses the track overflow
feature. The ROW for a variable length record
specifies a length greater than 32,752.
An invalid record was encountered on a QSAM PUT or
14
WRITE operation. The record length is greater than the
blocksize specified in the DCB.
An invalid record was encountered on a QSAM PUT
18
operation; the data set uses the variable record
format. The value in the length of the ROW is invalid
for one of the following reasons:
• It is greater than 32,767, or greater than the
blocksize specified in the DCB.
• It is less than 4, or less than 5 if ASA control
characters are used.
The error occurred during the creation of a direct data
IC
set. A WRITE macro instruction was issued for a
record larger than the track capacity, and the record
format does not use the track overflow feature.
The error occurred during the creation of a direct data
20
set. A WRITE macro instruction was issued causing a
secondary extent to be obtained. The block will not fit
oli the amount of space allocated for the secondary
extent.
The error occurred during the creation of a direct data
24
set. A WRITE macro instruction was issued to write out
a block larger than the primary extent on the
preallocated data set. This could also occur if
a
'",
allocation of the primary extent was split and any of
the secondary extents were smaller than the block.
28
The error occurred during the creation of a direct data
set. During the execution of OPEN it was detected that
the blocksize was larger than the primary extent.
2C
The error occurred while opening an ISAM data set for
QISAM load mode. Too many tracks were specified for
cylinder overflow, or DCB BlKSIZl;: is not a multiple of
DCB lRECl.
System Action: For all return codes except 2C, pertinent
control blocks are written to the GTF trace data set as follows:
Code
Trace Data
04
DCB, lOB, or ICB seek field, current logical record
(maximum, 88 bytes).
08,10, DCB, DECB (if BSAM), current block (maximum, 88
14
bytes).
OC,lC DCB, DECB (if BSAM), current block (maximum, 88
bytes), track capacity.
18
DCB and the current logical record (maximum, 88
bytes).
20,24 DCB, DECB, current block (maximum, 88 bytes), track
capacity, current DEB extent.
2C
No trace data.
For all return codes except 2C, the user's DCB ABEND exit
routine is taken if one is provided.
Programmer Response: Probable user error. If rc is 04, 08,
10, or 14, verify that the record size passed to the access
method is correct. If rc is 14, if necessary, increase the
blocksize to accomodate the largest logical record.
If rc is OC or 1C, use a smaller blocksize, or a device with a
greater track capacity, or specify track overflow.
If rc is 20, 24, or 28, allocate a larger primary or secondary
extent, specify a smaller blocksize, or use a device with
greater track capacity. If the error occurred because the
primary allocation was fragmented into a number of extents,
specify the CONTIG subparameter on the SPACE parameter.
If rc is 2C, change the CYLOFl operand of the DCB macro
instruction to reflect the correct number of tracks, or correct
DCB BlKSIZE.
Correct the error and rerun the job step.
Problem Determination: Table I, items 1, 3, Sa, 15, 29.
IEC0371
008-rc,mod,jjj,ddn,ddd,ser,dsn
Explanation: The error occurred following execution of a
CHECK macro instruction during the processing of the creation
of a direct data set. In the message text, 008-rc associates
this message with system completion code 008 and with return
code rc. Other fields in the message text are:
jjj
job name
sss
step name
ddn
DOna me
ddd
device address
ser
volume serial number
mod
The name of the module in which the error occurred.
dsn
data set name
The values of rc and their meanings are as follows:
Return
Code
Meaning
04
During the creation of a direct data set, EOV was
unable to allocate more space because the current
Section 6: IEC Messages - Data Management
6-9
volume was taken. The user returned to the CHECK
module from his SYNADroutine.
08
During the creation of a direct data set, an I/O error
occurred and the SYNAD exit was taken. The user
returned from his SYNAD routine to the check module.
System Action: The user's DCB ABEND exit routine will
receive control if one was specified. On return, the following
control blocks are traced to a GTF data set for return code 04:
1) all DEB extents and 2) the first 88 bytes (or less if
blocksize is less) of the user's output record. No control
blocks are traced for return code 08. In both cases, the task is
terminated.
Programmer Response: For return code 04, allocate more
space or more volumes. For return code 08, check the lOB in
error. If the 10BCSW field does not indicate a user error,
(user's data area less than blocksize or not in user key, which
could result in a channel program check), rerun the job.
Problem Determination: For return code 04, see Table I, items
3, 4, 5b, 16, 25a, 29. For return code 08, see Table I, items
3, 4, Sa, 13, 16, 29, or 30, (if not user error).
IEC0401
ddn
= rc
UNABLE TO LOAD
3890 CONTROL UNIT.}
{ FORMAT RECORD xxx .
Explanation: If 3890 CONTROL UNIT appears in the message
text, the 3890 document processor support was unable to load
the 3890 control unit for the data set ddn for reason rc. If
FORMAT RECORD xxx appears in the message text, the 3886
optical reader support was unable to load a format record
whose identifier is xxx for data set ddn for reason rc.
The values of rc and their meanings are as follows:
Return
Meaning
Code
For the 3890, the SCI program or subroutine was not
04
added to SYSl.IMAGELlB.
For the 3886, the format record specified for the data
set was not added to SYSl.IMAGELIB.
08
For the 3890, unable to load an SCI program or
subroutine from SYSl.IMAGELlB; make sure
SYSl.IMAGELIB was mounted.
For the 3886, unable to load a format record from
SYSl.IMAGELlB; make sure SYSl.IMAGELIB was
mounted.
OC
A hardware error occurred.
10
For the 3890, one of the following occurred:
• DCB address operand in the SETDEV macro
instruction was missing.
• IREC operand in the SETDEV macro instruction was
missing.
• Sum of the lengths for the fields (bytes) specified
in the IREC macro instruction does not equal
LRECL-12. (LRECL is specified in the DCB macro
instruction.)
• I/O error posted in the data control block.
• The data control block specified in the SETDEV
macro instruction was not opened.
For the 3886, the format record identifier was miSSing
from the SETDEV parameter list when the execute
form of the macro was issued.
14
For the 3890, the error can be found by investigating
the. sense bytes and header record.
18
For the 3890, the SCI program does not begin with
the ENTR· stacker control instruction.
System Action: The error occurred during a SETDEV operation
where the 3890 control unit or format record was to be
dynamically loaded. The write-to-programmer message is
6-10
VS2 System Messages (VS2 Release 3.7)
printed and control is returned to the user with a return code
in register 15.
Programmer Response: For the 3890, return codes 04, 08, 10,
and 18 are probable user errors. Correct the error and
resubmit the job. Return code OC is a probable hardware error
and return code 14 is an exceptional condition that should be
handled according to condition.
For the 3886, return code 04 and 10 are probable user errors.
Make sure that the SETDEV parameter list has a format record
identifier when the execute form of the macro is issued (return
code X'10'). If the return code is X'04', make sure that the
format record specified for the data set has been added to
SYSl.IMAGELIB. If the return code is X'08', make sure the
volume containing SYSl.IMAGELIB is mounted. If the return
code is X'OC', it is a probable hardware error.
Problem Determination: Table I, items 2, 29 or 30.
IEC0411
005-rc,mod,JJJ,sss,ddn[ -#],ddd
Explanation: The DECB specified is invalid. In the message
text, 005-rc associates this message with system completion
code 005 and with return code rc. Other fields in the message
text are:
jjj
job name
sss
step name
ddn[ -#J
DDname (followed by a concatenation number if it is part of
a concatenation and not the first DO statement in the
concatenation).
ddd
device address
mod
The name of the module in which the error occurred.
The values of rc and their meanings are as follows:
Return
Code
Meaning
04
A required address was not specified. This can be
either 'the header address and/or the area address.
08
The RBL type of read was not used for the 3886.
System Action: The task is terminated with a 005-rc system
completion code.
Programmer Response: Make sure the RBL type of read is
. used and the area address and header address parameters are
specified so that the DECB is valid.
Problem Determination: Table I, items 1, Sa, 15, 16, 29.
IEC0421
INVALID DATA - prm SPECIFIED FOR opr
Explanation: The parameter prm passed to the data
management routine for 3886 support was invalid. The
operation, opr, can be one of the following:
RD L1NENO An attempt to read backwards was made
(for example, a line number less than the
last line read was specified) or the support
detected two EOP conditions on successive
reads with no eject between them.
L1NEFMAT The line format number specified was
greater than 63.
NUM TIME MKS - The number of timing marks specified on
an eject was greater than 33.
NO LINE FMAT No line format number specified for read.
LINE MK CODE - The code specified for a line mark was
greater than 15.
LINE NK NO The line number to be marked was greater
than 33.
DOC CODE The code specified for a document mark
was greater than 15.
System Action: Processing continues. An I/O error will be
caused by the invalid data passed to the device.
Programmer Response: Correct the invalid data specification
and rerun the job.
Problem Determination: Table I, items 1, Sa, 15, 16, 29.
IEC0661
jjj,ser[,ddd] MSS FAILURE IN func. CODE = hhh.
Explanation: An error occurred while the MSS (Mass Storage
System) communications routine (SVC 126) was processing a
request from End-of-Volume. The fields of the message text
are:
jjj
job name
ser
volume serial number
ddd
device address
func
MOUNT, DEMOUNT, ACQUIRE, or RELINQUISH
hhh
return code from SVC 126. See OS/VS Message Library: VS2
System Codes, GC3S-100S, for the values of hhh and their
meanings.
System Action: A 737-34 abend is requested.
Programmer Response: See OS/VS Message Library: VS2 System
Codes, GC3S-100S, for the programmer responses to each
return code.
Problem Determination: See OS/VS Message Library: VS2 System
Codes, GC3S-100S.
IEC0671
CHKPT = EOV FACILITY EXECUTED
UNSUCCESSFULLY
Explanation: The checkpoint at EOV facility, moduel IFG055SX
received a return code, other than 0 or 4, which indicates an
unsuccessful or unusual execution of the CHKPT macro. A
preceding OS/VS Checkpoint/Restart message (prefixed IHJ)
should identify more exactly the nature of the problem.
Checkpoint/Restart, if required would probably not be possible
using the Checkpoint at EOV checkpoint data set (SYSCKEOV)
entry which just failed.
System Action: Processing continues. Checkpoint at EOV will
be attempted again at the next end-of-volume occurrence.
Operator Response: Refer to associated IHJ message for
recommended action and notify programmer of error situation.
IEC0701
rc[ (sfi)] -ccc,jjj,sss,ddn,ddd,ser ,xxx,dsn,cat
Explanation: An error occurred during end-of-volume (EOV)
processing for a VSAM data set. In the message text, rc
indicates the specific error that occurred. Other fields in the
message text are:
(sfi)
subfunction information (error information returned by
another component invoked by EOV). This field appears only
for certain error codes, and its format is shown with those
codes to which it applies.
ccc
function code:
Operation being
performed when
error was
Function
detected
Code
Read JFCB.
200
201
Initialize for VSAM end-of-volume processing.
Locate and mount volume.
202
Allocate space.
203
204
Switch volumes.
205
Build control blocks.
206
207
20S
209
Update SMF record.
Preformat extent.
Record management, catalog update.
Reset control blocks.
jjj
jobname
sss
stepname
ddn
DOna me
ddd
device address, if the error is related to a specific device
ser
volume serial number, if the error is related to a specific
volume
xxx
name of cluster that contains the data set being processed
when the error was detected; or when not available, the
DSNAME specified on the DO statement specified by the
ACB.
dsn
name of the data set being processed when the error was
detected
cat
catalog name
Note: Any missing field is indicated by a comma.
The values of rc and their meanings are as follows:
Return
Code
Meaning
04
An internal error was detected while the VSAM catalog
ACB processor was in control.
20
Not enough virtual storage was available for work
areas, buffers, or control blocks.
22
An I/O error occurred while I/O requests were being
completed.
2S
The requested system or user catalog does not exist
or is not open.
The (sfi) field in the message is of the form (rc,crs,cmi) where:
rc catalog return code
crscatalog reason code
cmicatalog module name that detected the error.
See message IDC30091 for a listing of these catalog return
codes and reason codes.
32
The catalog record for the data set being processed
was not found.
The (sfi) field in the message is of the form (rc,crs,cmi) where:
rc catalog return code
crscatalog reason code
cmicatalog module name that detected the error.
See message IDC30091 for a listing of these catalog return
codes and reason codes.
33
Cannot extend the VSAM catalog. The VSAM catalog
has reached the maximum number of extents. Either
additional space is unavailable or a system error
occurred.
The (sfi) field in the message is of the form (rc,crs,cmi) where:
rc catalog return code
crscatalog reason code
cmicatalog module name that detected the error.
See message IDC30091 for a listing of these catalog return
codes and reason codes.
34
The data set has reached the maximum number of
extents.
The (sfi) field in the message is of the form (re,crs,cmi)
where:
rc catalog return code
crscatalog reason code
cmicatalog module name that detected the error.
Section 6: IEC Messages - Data Management
6-11
•
See message IDC30091 for a listing of these catalog return
codes and reason codes.
35
The catalog record for the data set has reached the
maximum number of sets of fields allowed. The
number of key ranges and volume entries have
reached the maximum allowed.
The (sfi) field in the message is of the form (rc,crs,cmi) where:
rc catalog return code
crscatalog reason code
cmicatalog module name that detected the error.
See message IDC30091 for a listing of these catalog return
codes and reason codes.
36
An I/O error was detected while the system was
reading or writing a catalog record.
The (sfi) field in the message is of the form (rc,crs,cmi) where:
rc catalog return code
crscatalog reason code
cmicatalog module name that detected the error.
See message IDC30091 for a listing of these catalog return
codes and reason codes.
37
An unexpected return code was returned by the
catalog routines.
The (sfi) field in the message is of the form (rc,crs,cmi) where:
rc catalog return code
crscatalog reason code
cmicatalog module name that detected the error.
See message IDC30091 for a listing of these catalog return
codes and reason· codes.
50
End-of-volume was unable to fix the access method
control blocks for the dataset being processed in
storage.
90
MSS MOUNT error. The (sfi) field contains the return
code from MSS; for these codes, see OS!VS Message
20
Specify a larger region and rerun the job. For
information on possible region size limitation, see the
section, "Limiting User Region Size IEALlMIT" in
22
Rerun the job specifying a different device for the
volume. ,
Make sure the correct catalog is open by specifying it
in the JOeCAT or STEPCAT DO statement and rerun
the job.
Make sure the data set entry is contained in the
master catalog or a user catalog specified in a
JOeCAT or STEPCAT DO statement. Use the Access
Method Services L1STCAT command to list the data
set entries in a specific catalog.
The Access Method Services DELETE command can be
used to delete entries from the catalog. If no entries
can be deleted the Access Method Services EXPORT
command can be used to move some of the data sets
defined in the full catalog to a portable volume. The
IMPORT command can be used to define the exported
data sets in a user catalog that has space available.
Use the Access Method Services REPRO command to
make a backup copy of the cluster that contains the
data set. Delete the cluster from the catalog with the
DELETE command. Use the DEFINE command to
redefine the cluster in the catalog with increa.sed
space allocation. Reload the backup of the cluster with
the REPRO command.
Use Access Method Services to: 1) copy the cluster
that contains the data set to another volume, 2)
delete the cluster, 3) redefine the cluster and either
reduce the number of key ranges and volumes or
increase the space allocation for each key range to
reduce the number of overflow volumes, and 4) reload
the copy of the cluster.
Specify a different device for the catalog that caused
the problem, and rerun the job.
Rerun the job. If the error persists, restore the catalog
and all volumes controlled by the catalog from
synchronized restore tapes.
Rerun the job.
This is a hardware error. Proceed as directed under
the MSS return code with this value.
This is a hardware error. Proceed as directed under
the MSS return code with this value.
This is a hardware error. Proceed as directed under
the MSS return code with this value.
This is a hardware error. Proceed as directed under
the MSS return code with this value.
You may ignore the warning. However, increased
system running time is likely to result. To remedy this,
proceed as directed under the MSS return code with
this value.
Delete unneeded data sets from the volumes you
specified or use the Access Method Services ALTER
command to provide a different list of volumes for
space allocation.
Use the Access Method Services ALTER command to
provide additional volumes for the data set.
Make sure at least one of the units allocated for your
program is flagged as nonsharabl.e so the volume can
be demounted. You can do this by specifying DEFER
or more volume serial numbers than units on the DO
statement.
Make sure at least one
),
DEVCHAR The device characteristics
specified for stations in this line
group are not consistent with the
devices specified on the DD
statement.
LCBCORE There is not enough main storage
to build a line control block (LCB)
for a line group.
SCBCORE There is not enough main storage
to build a station control block
(SCB) for a switched line.
BSCINER The binary synchronous interface
specified in the data control block
does not agree with that specified
in a unit control block (UCB) for a
line in this line group.
NVALU.CB No valid unit control block (UCB)
addresses were found for this line
group; all UCB addresses checked
were zero.
HPSZLRG The sum of the header prefix size
plus the number of bytes reserved
in the first buffer of each message
by the RESERVE = operand of the
line group DCB macro is equal to,
or greater than, the size of the
buffers assigned to the lines in the
group for input; thus, there is no
room in the buffers for data.
NODATST There is no data set for the type
of queuing specified by the
terminal table entry for a line or
line group.
NOLINES The QUEUES = operand of a
TERMINAL macro specified an
unopened data set because each
terminal entry for each line in .this
line group specified an unopened
data set. The data set for this line
group cannot be opened.
RELINEO A queue control block (QCB) was
found that specified a relative line
number of zero.
CHARERR The optional features specified in
the unit control block (UCB) do
not agree with those reflected in
the device characteristics entry for
this line.
DSPAREA There was not enough main
storage to satisfy a GETMAIN
request to build a TCAM control
area in the subpool.
An invitiation list is not specified
INVLlST
for each line in the line group.
OS MCP The Message Control Program was
not assembled with VS/TCAM
macros.
PLCBCOR No storage available for PLCBs.
NOTKEY6 The TCAM Message Control
Program does not reside on the
installation-defined authorized
library or the MCP is not in the
program properties table.
OA
041-1
DISKAVT
An incorrect length is specified for
the address vector table (AVT) in
order to support switched message
queuing. Disk queuing is specified
in a DCB macro defining a
message queues data set, but the
INTRO macro that generates the
AVT specifies DISK = NO.
OB 041-2 KEYLNGR The key length specified by the
KEYLEN = operand of the INTRO
macro does not agree with the key
length specified in the IEDQDATA
DD statement of the IEDQXA utility
used to format the message
queues data set.
OC 041-3 DEVUCBS Dissimilar disk types are defined
for message queuing.
OD 041-4 QUEUING The OPTCT = operand for this
DCB specifies something other
than reusable or nonreusable
queuing.
OE 041-5 MDEBCOR A GETMAIN macro was issued by
TCAM to obtain main storage to
build a data extent block (DEB) for
a message queues data set, but
there was not enough main
storage to satisfy the request.
OF
041-6 MIOBCOR A GETMAIN macro was issu~d by
TCAM to obtain main storage to
build input/output blocks (lOBs)
for a message queues data set,
but there was not enough main
storage to satisfy the request.
10 041-7 NOFORMT The message queues data set was
allocated but not formatted
correctly; the last record number
written on a track is zero.
11 041-8 UNAUTH The invoking task is not an
authorized program.
17 041-G DSPAREA There -was not enough main
storage to satisfy a GETMAIN
request to build a TCAM control
area in the subpool.
20 041-P NOTKEY6 The TCAM Message Control
Program does not reside on the
installation-defined authorized
library or the MCP is not in the
program properties table.
System Action: The action taken depends upon the return code
provided by the user's asynchronous error routine. If no error
routine is provitled, TCAM will terminate with the system
completion code indicated in the message text by cde. If the
message code is 040-1 or 041-8 no exit to the user's
asynchronous error routine is made and the task is terminated
with a system completion code of cde.
Programmer Response: Probable user error. No action is
required if the programmer has provided a user ABEND entry
in the problem-program exit list named by the EXLST =
operand of the DCB macro instruction whose DD statement is
named ddn. The routine specified by the entry is given control
from the TCAM Open Error Handler routine. If no user routine
is provided, TCAM issues an ABEND macro instruction for the
MCP causing it to terminate abnormally with the system
completion code indicated in the message text by cde.
Programmer responses for probable values for yare:
W
Section 7: lED Messages - Telecommunications Access Method
7-3
•
Code in Console
y
Programmer Response
Reg. 0 Code
040-1 DEBCORE Specify a larger region size on the
01
JOB statement for the MCP.
040-2 OEVLlNE Specify similar stations in the line
02
group; reassemble and rerun the
MCP.
03
040-3 NOTPDEV Check the addresses specified in
the line group DO statements to
be sure that the line addresses are
valid.
04 040-4 CTLUNIT Check the addresses specified in
the line group DO statements to
be sure that the line addresses are
valid.
05
040-5 BRIXUCB Check the addresses specified in
the line group DO statements to
be sure that the line addresses are
valid.
040-6 DEVCHAR Check the addresses specified in
06
the line group DO statements to
be sure that the line addresses are
valid.
07
040-7 LCBCORE Specify a larger region size on the
JOB statement for the MCP.
08
040-8 SCBCORE Specify a larger region size on the
JOB statement for the MCP.
040-9 BSCINER Check the type of interface
09
specified in the INVLlST =
operand of the DCB macro against
the bit settings specified in the
UCBs for each line in this line
group.
040-A NVALUCB Specify DO statements with valid
11
UNIT = operands.
12 040-B HPSZLRG Specify a larger buffer size for the
input on the BUFSIZE = and
BUFIN = operands of the line
group DCB macro, reassemble,
and rerun the job. (If a DO
statement is used instead of
specifying the RESERVE =
operand, a reassembly is not
required.)
13 040-C NODATST If main storage queuing is being
used, verify that data sets were
provided at INTRO execution time;
if disk queuing is being used,
ensure that the disk message
queues data sets are opened
before opening any line groups.
14 040-0 NOLINES If main storage queuing is being
used, verify that data sets were
provided at INTRO execution time.
If disk queuing is being used,
ensure that the disk message
queues data sets are opened
before opening any line groups.
15 040-E RELINEO Each TERMINAL macro must
specify an unframed decimal
integer between 1 and 255,
inclusive (zero is invalid).
16 040-F CHARERR Verify that all DO statements
specify the correct type of UCB for
the lines being opened.
17 040-G DSPAREA Specify a larger region on the JOB
statement for the MCP.
7-4
VS2 System Messages (VS2 Release 3.7)
IED0091
040-H
INVLlST
Either remove excessive DO cards
or reassemble the MCP with an
invitation list included for each line
in the line group.
19 040-1 OS MCP
Reassemble MCP with VSjTCAM
macros.
1E 040-N PLCBCOR Increase region size of JOB card,
or decrease the number of PLCBs
when specifying TCAM parameters.
20
040-P NOTKEY6 The TCAM MCP must be link
edited to the installation-defined
authorized library or the TCAM
MCP must be renamed with one of
the names in the program
properties table.
OA 041-1 DISKAVT Specify DISK = YES in the INTRO
macro, reassemble, and execute
again.
OB 041-2 KEYLNGR Reassemble the job with the
proper length specified in the
KEYLEN = operand of the INTRO
macro and rerun the MCP, or
restart the TCAM job and override
the KEYLEN = value by entering
REPLY xX,'K = nn, U' to message
IED004A, or reformat the disk to
the proper key length using the
IBDQXA utility and rerun the MCP.
OC 041-3 DEVUCBS Ensure that the disk types
specified for message queuing are
similar.
00 041-4 QUEUING Check and correct the contents of
the DCB field.
OE
041-5 MDEBCOR Specify a larger region size on the
JOB statement for the MCP.
OF
041-6 MIOBCOR Specify a larger region size on the
JOB statement for the MCP.
10 041-7 NOFORMT Reformat the data set using the
IEDQXA utility and rerun the MCP
job.
11 041-8 UNAUTH Contact your system programmer.
Program must be authorized.
17 041-G DSPAREA Specify a larger region size on the
JOB statement for the MCP.
20 041-P NOTKEY6 The TCAM MCP must be link
edited to the installation-defined
authorized library or the TCAM
MCP must be renamed with one of
the names in the program
properties table.
If the problem recurs, do the following before calling IBM for
programming support:
• Make sure that a SYSABEND DO statement was included for
the failing job step.
• Have a listing of associated Message Control Program
available.
Problem Determination: Table I, items 1, 2, Sa, 10, 13, 29.
18
ddn-CHECKPOINT DISK ALLOCATION ERROR DATA SET NOT OPENED
Explanation: The amount of disk space specified on the DO
statement for the checkpoint data set, or the region size, is
insufficient for minimum checkpoint requirements. The
checkpoint data set is not opened.
System Action: The checkpoint facility is not available to the
Message Control Program (MCP) since MCP terminates
abnormally with system completion code 045-9.
)(
I
\~
\
Programmer Response: Probable user error. If the checkpoint
facility is required, reallocate the checkpoint data set giving it
more space, and run the MCP job again with DISP = NEW
coded in the DO statement for the checkpoint data set.
Problem Determination: Table I, items Sa, 10, 29.
IED0101
CHECKPOINT -INSUFFICIENT CORE
ddn NOT OPENED xxx
ENVIRON xxx
INCIDENT xxx
CKREQ name xxx
INCIDENT RECORD IGNORED
l
1
Explanation: A GETMAIN macro instruction issued by a
checkpoint routine cannot be satisfied because insufficient
main storage is available. The xxx qualifier is the number of
bytes of storage requested. For a checkpoint request record,
the name qualifier is the name of the process entry in the
terminal table for which a checkpoint request record would
have been taken had sufficient main storage been available.
ddn identifies the checkpoint data set.
System Action: If the data set was not opened, processing will,
continue without the checkpoint facility. If the data set has
been opened successfully, either (1) the checkpoint record
indicated in the message was not taken, but the checkpoint
facility is still active and will continue processing, or (2) the
incident record was not used by TCAM in reconstructing the
environment during restart.
Programmer Response: Probable user error. Specify a larger
region and do a TCAM warm restart. A warm restart uses the
checkpoint facility to recreate the environment prior to a
normal closedown. The warm restart is specified as the
STARTUP = W operand of the INTRO macro instruction or as a
REPLY xx, 'S = W,U' response to message IED002A.
Problem Determination: Obtain an ABEND dump of the Message
Control Program taken immediately after the error message
was issued.
IEDOlll
SYSTEM INTERVAL CANNOT BE ALTERED
Explanation: A system interval of zero or no system interval at
all was specified in the INTVAL = operand of the INTRO
macro instruction or in the operator's response to a message
issued at execution time, or the Time-Sharing Option (TSO) is
active and an operator command was entered to modify the
value of the interval. The interval, a time during which polling
and addressing are suspended on multipoint lines to polled
stations, cannot be altered.
System Action: The requested action is not taken. Normal
processing continues.
Operator Response: If the interval feature is required, close
down the system. Either reassemble with a positive value
specified in the INTVAL = operand of the INTRO macro
instruction and restart, or restart the job with a non-zero value
provided in the REPLY xx, 'I = nn,U' response to message
IED002A. If the interval feature is not required, refrain from
entering the MODIFY id, INTERVAL = SYSTEM[,nn] operator
commands.
Probelm Determination: If a non-zero system interval is
specified and this response is received, see Table I, items 2,
29.
Have a listing of the Message Control Program available.
Have the console listing or the terminal listing for the device
which entered the command available.
IED0121
TSO SESSION ON LINE Ina COMMAND REJECTED
Explanation: An operator command to stop the line Ina has
been entered, but a TSO session is currently in progress on
the line; or an operator command to close down TCAM has
been entered, but TSO is currently active.
System Action: The command is rejected. Normal processing
continues.
Operator Response: None. Information only. If the line must still
be stopped, wait until the TSO session has been completed
and reenter the command. If TCAM must be closed down, stop
TSO and then re-enter the command.
Problem Determination: Table I, items 2, 10, 29. If TSO is not
currently active, or if Ina in the response does not agree with
the value specified in the command, instruct the terminal user
to retain the terminal listing or record what is currently
displayed on the graphics device.
IED0131
STOP REQUEST FOR SELF - VARY COMMAND
REJECTED
Explanation: An operator command to stop a line was entered,
but the line specified is associated with the station that
entered the command.
System Action: The line is not stopped, Normal processing
continues.
Operator Response: None.
IED0141
TCAM ALREADY IN SYSTEM
Explanation: The TCAM initialization routine has detected the
presence of another Message Control Program (MCP) in this
system.
System Action: Initialization of the second MCP is terminated.
A return code of X'04' is returned to the user immediately
following the INTRO macro instruction in the MCP. If the MCP
is not halted, results are unpredictable, and may cause the
previous MCP to also become unpredictable.
Programmer Response: Close down the MCP currently in the
system before attempting to restart the MCP for which this
message is issued. An invalid procedure in closing down the
•
previous MCP may leave a non-zero value in CVT +X'FO'. When
TCAM starts, the word must be zero to avoid this error
condition. ~ake sure there is no other TCAM MCP operating
before attempting to set this word to zero.
Problem Determination: Table I, items 2,29.
IED0151
TCAM AP OPEN ERROR 043-rc ddn ~jj
Explanation: In attempting to open the application program
data set represented by the DO statement named ddn in the
job named jjj, TCAM's Open Executors encountered an error.
In the message text, rc is a one-byte reason code naming the
specific error that was encountered. Possible values for rc and
their meanings are:
01
An application program OPEN has been issued but there
is no Message Control Program (MCP) active in the
system.
02 The QNAME = parameter of a DO statement for an
application program is not the name of a process entry
in the terminal table,- or the process entry named is
inconsistent with the DCB macro instruction format.
03
Insufficient virtual storage was available in the MCP to
build internal control blocks, or PGFIX macro failed for
the process entry workarea.
04
A process entry named on a DO statement associated
with an application program is currently being used by
another data control block.
05
Insufficient virtual storage was available in the application
program area to build internal control blocks.
Section 7: lED Messages - Telecommunications Access Method
7-5
•
The application program attempted to open a secured
queue. The system operator rejected the request.
07 The application program is not authorized but user has
coded either AUTH = yes (default) or TCAM INTRO
macro.
System 'Action: TCAM will terminate the application program
with a system completion code of 043.
Operator Response: Report this message to the system
programmer.
Programmer Response: The possible values of rc and their
appropriate responses are:
01
Verify that an MCP is active before attempting to start
an application program.
02,04 Recode the QNAME = parameter specifying the name
of a valid process entry.
03
Specify a larger region size in the JOB statement for
the MCP or restart the system, specifying a larger
system queue space.
05
Specify a larger region size in the JOB statement for
the application program or restart the system,
specifying a larger system queue space.
07
Link edit application program as authorized into an
authorized library, or specify AUTH = NO on the
INTRO macro instruction.
Problem Determination: Table I, items 2, 10, 29.
Operator Response: Check the required format of the operator
command and correct the operand in error. Respecify the
command.
Problem Determination: Table I, items 2, 10, 29. Instruct the
terminal user to retain the terminal listing or record what is
currently displayed on the graphics device.
IED0161
Explanation: The operator entered a command to start
autopolling on the line. This response confirms that the action
was taken.
System Action: Autopolling begins for th,e line. Normal
processing continues.
Operator Response: None.
06
STATION station NOT FOUND
Explanation: An operator command referring to a station
named station was entered, but station is not an entry in the
TCAM terminal table.
System Action: The action requested by the command is not
taken. Normal processing continues.
Operator Response: Verify the spelling of the station name.
Remember that lower-case characters entered from a station
other than the system console are not generally equivalent to
upper case characters. Respecify the command.
Problem Determination: If the station name is correct, and the
response is still received, see Table I, items 2, 10, 29. Instruct
the terminal user to retain the terminal listing or record what is
currently displayed on the graphics device.
IED0191
IED0201
IED0211
IED0181
cm COMMAND INVALID
Explanation: An operator command was entered, and a field in
the operand list is incorrectly formatted, or required operands
are missing, or operands are in the incorrect order. In the
message text, cm is the verb of the command in error.
System Action: The requested action is not taken. Normal
processing continues.
7 -6
VS2 System Messages (VS2 Release 3.7)
~ grpname,
AUTO POLL STARTED FOR
1address
IED0221
rln
t
5
AUTO POLL ALREADY STARTED FORsgrpname, rlnt
1address
\
Explanation: The operator entered request to start autopolling
on a line. The line is already being autopolled.
System Action: Normal processing continues.
Operator Response: None.
TRACE STARTED FOR
S grpname, rln
1address
LINE Ina NOT OPEN
Explanation: An operator command was entered that referred
to line Ina, but the command was not honored for one of the
following reasons:
1. The line was not open.
2. The OPEN macro for the line specified IDLE.
3. The groupname specified had no matching DO statement.
4. The relative line number specified was either zero or was
higher than any relative line number in the gr9uP.
System Action: The requested action is not taken. Normal
processing continues.
Operator Response: Verify that the line referred to is open and
active. Reenter' the command. If the line is open but inactive, it
may be activated with a VARY (lna),ONTP operator command
before reentering the command which provided this response.
Problem Determination: Table I, items 2, 10, 29. Instruct the
terminal user to retain the. terminal listing or record what is
currently displayed on the graphics device.
xxx STARTED
Explanation: An operator command to start the line or station
named xxx was entered. The line or station is started, and the
message is a confirmation of the action taken.
System Action: The line or station is started. Normal
processing continues.
Operator Response: None.
IED0231
IEDO 171
xxx ALREAOY STARTED
Explanation: An operator command to start the line or station
named by xxx was entered. The line or station is already
active.
System Action: The command is ignored and normal processing
continues.
Operator Response: None.
t
5
Explanation: An operator command to start TCAM's line I/O
interrupt trace was entered for the line. This message· confirms
that the action has been taken. The line I/O interrupt trace is
a sequential recording in virtual storage of I/O interrupts on a
line.
System Action: I/O trace is started on the line. Normal
processing continues.
Operator Response:· None.
IED0241
TRACE ALREADY STARTED FOR
Sgrpname, rln
1address
t
5
Explanation: The operator entered a command to start TCAM's
line I/O interrupt trace for the line, but I/O trace was already
active for this line.
System Action: Normal processing continues.
Operator Response: None.
IED0251 {statname
} ALREADY STOPPED
grpname, rln
address
Explanation: The operator entered a command to stop a line or
station. This line or station is not currently active.
System Action: Normal processing continues.
Operator Response: None.
IED0261
{statname
} STOPPED
grpname, rln
address
Explanation: The operator entered a command to stop a line or
station. The line or station is stopped. This message confirms
the action taken. Processing continues.
System Action: The line or station stops. Processing continues.
Operator Response: None.
IED0271
~grpname,
AUTO POLL STOPPED FOR
1address
rln t
~
Explanation: The operator entered request to stop autopolling
on a line. This message confirms that autopolling has been
stopped.
System Action: Autopolling stops on the line. Processing
continues.
Operator Response: None.
IED0281
AUTO POLL ALREADY STOPPED FOR{grpname, rln}
address
The second format of the message is issued if the command
was directed to a 3705 line: the line is identified by
grpname,rln; stat represents the status of the line as follows:
AC Line is active
AP Activate line is in progress
BS esc line
DH Deactivate line halt is in progress
DL Switched line
DO Deactivate line orderly is in progress
EP
Line is in EP mode
LI
Line is free
MP Multipoint line
MT Multipoint tributary
PS
Point-to-point Secondary
SN Session is currently active on the line
SS
Service seeking is in progress
TC A test command has been received for a device on
the line
System Action: Processing continues.
Operator Response: None.
IED0331
Explanation: The operator entered a command to stop
autopolling on a line. Autopolling on the line is not in progress
at this time.
System Action: Processing continues.
Operator Response: None.
IE00291
TRACE STOPPED FOR
~ grpname,
1address
rln t
~
Explanation: The operator entered a command to stop line I/O
~,
,)
i
interrupt trace for the specified line. This response confirms
that tracing is stopped.
System Action: Line I/O trace is stopped for the line.
Processing continues.
Operator Response: None.
IED0301
~
TRACE ALREADY STOPPED FOR
grpname, rln t
,
1address
Explanation: The operator entered a"command to stop line I/O
interrupt trace on the specified line. Line I/O trace is not
currently active on this line.
System Action: Processing continues.
Operator Response: None.
IED0311
station QUEUE SIZE
STATUS = stat
= nnn
QUEETYP
= bb
Explanation: An operator command to display the queue for the
station named station is entered. This message displays the
fields of the queue. In the message text, nnn is the number of
messages currently on the queue; stat is the equivalent of the
status bits currently on; and bb is the queuing type for this
queue.
System Action: Processing continues.
Operatc!! Response: None.
t
j Ina LNSTAT = stat, ... ERR = xxx, ...
1grpname,rln LNSTAT = stat
~
Explanation: The operator entered a command to display the
status of a line. The first format of the message is issued if
the command was directed to a 2701/02/03 line. The line is
identified by Ina; stat is the equivalent of the status bits
currently on in the line control block, and xxx represents the
equivalent of the bits currently on in the message error record
for the line.
IE00321
station STATUS = stat, .. .INTENSE = zz IN-SEQ = aaa
OUT -SEQ = bbb
Explanation: An operator command to display the fields of the
entry for the station named station was entered. In the
message text, stat represents the eqiJivalents of the status
bytes of the entry, zz is the setting of the error recording field,
and aaa and bbb are the input and output sequence numbers,
respectively.
System Action: Processing continues.
Operator Response: None.
IED0341
station HAS NO opt OPTION
Explanation: An operator command to display or modify the
contents of the option field named opt for the station named
station was entered. No option field named opt exists for this
station.
System Action: The requested action is not taken. Processing
continues.
Programmer Response: Verify that the option named opt is
spelled correctly and is defined for the station named station.
Reenter the command.
Problem Determination: If the option field named by opt exists
for the station named station, and the message recurs see
Table I, items 2, 10, 29. Instruct the terminal user to retain
the terminal listing or record what is currently displayed on the
graphics device.
IED0351
station OPTION· opt = zzz
Explanation: An operator command to display the contents of
the option field named opt for the station station is entered. In
the message text zzz represents the requested contents.
System Action: Processing continues.
Operator Response: None.
IED0361
jgrpname, rlntACTIVE = yyy, ..•
1address
~
Explanation: The operator entered a command to display the
list of active stations associated with a line. In the message
text, yyy represents the entries that meet this requirement.
System Action: Processing continues.
Operator Response: None.
Section 7: lED Messages - Telecommunications Access Method
7-7
•
IE00371
~grpname,
rlnllNACTIVE
1address
= yyy, •..
~
Explanation: The operator entered a command to display the
list of inactive stations associated with a line. In the message
text, yyy represents the names of the entries which meet this
requirement.
System Action: Processing continues.
Operator Response: None.
IE00381
station IS ON LINE ddn rln Ina
Explanation: An operator command to display the. line
information associated with the station named station was
entered. In the message text, ddn is the DOna me of the line
on which the station is an entry, rln is the relative line number
and Ina is the unit control block identification (the hardware
address) of the line associated with the station.
System Action: Processing continues.
Operator Response: None.
IE00391
NO STATIONS INTERCEPTED
Explanation: An operator command requesting the display of
the list of all currently intercepted (held) stations in the system
is entered. No stations are currently being held.
System Action: Processing continues.
Operator Response: None.
IE00401
INTERCEPTED STATIONS = station, ...
Explanation: An operator command requesting display of the
list of all stations which are currently intercepted (held) was
entered. In the message text, station represents the names of
the stations which meet this requirement.
System Action: Processing continues.
Operator Repsponse: None.
IE00411
PRIMARY = station
Explanation: An operator command requesting display of the
name of the current primary operator control station was
entered. In the message text, station is the name of the
current primary control station.
An operator command requesting that the station named
station be made the primary operator control station was
entered. This response confirms that the action was taken.
System Action: Processing continues. If the command entered
was MODIFY id,PRIMARY = station, the named station is made
the primary operator control station.
Operator Response: Retry the command.
IE00421
station ALREADY· PRIMARY
Explanation: An operator command requesting that the station
named station be made the primary.operator control station
was entered, but station is already the primary operator
control station.
System Action: Processing continues.
Operator Response: None.
IED0431
SECONDARY
= xxx, •..
Explanation: An operator command requesting display of the
list of all secondary operator control stations was entered. In
the message text, xxx represents the names of all entries
which meet this requirement. The system console (SYSCON)
will not be listed as a secondary operator control station
unless there are no other secondary stations. If the primary
operator control station is not the system console, it will be
listed as a secondary station.
System Action: Processing continues.
Operator Response: None.
7-8
VS2 System Messages (VS2 Release 3.7)
IED0441
station NOT ELIGIBLE FOR PRIMARY
Explanation: An operator command requesting that the station
named station be made the primary operator control station
was entered, but station is not eligible to be made the primary
(Le., it is not defined as a secondary operator control station).
System Action: The primary operator control station remains
unchanged. Processing continues.
Operator Response: Retry the command.
Problem Determination: If the station is a valid secondary
operator control station, see Table I, items 2, 10, 29. Save the
terminal listing for the device which entered the command or
record what· is currently displayed on the graphic device.
IED0451
SYSTEM INTERVAL ALREADY ACTIVE
Explanation: An operator command to activate the system
interval was entered, but a previous request has already been
honored.
System Actiqn: ProceSSing continues. The system interval is
being activated already.
Operator Response: None.
IE00461
LINE FOR station IS OUTPUT ONLY STATION
Explanation: An operator command to start or stop a terminal
for entering messages is received, but the line has no
capability to enter messages. In the message text, station is
the name of the station to be started or stopped.
System Action: The requested action is not taken. Processing
continues.
Operator Response: Retry the command.
Problem Determination: If the station named station in the
response is not an output only station or is not identical to the
name specified in the command, see Table I, items 2, 29.
Instruct the terminal user to retain the terminal listing or
record what is currently displayed on the graphics device.
IED0471
SYSTEM INTERVAL IS
~ ~~TIVE~
Explanation: If the message text includes val, an operator
request to change the system interval has been entered and
the response (this message) confirms that the requested
action has been taken. If the message text contains ACTIVE,
an operator request to start or stop a line group has been
entered but the system interval is active, the message
indicates that the request is rejected.
System Action: The value of the system interval has been
changed to val, or the command has been rejected.
Operator Response: None.
IED0481
POLLING DELAY FOR station IS val
Explanation: An operator command to change the polling
interval for the line on which the station named station is a
member to a new value of val is entered. This message
verifies that the requested action is taken.
System Action: The polling delay for the line group on which
the named station· is a member is changed to val. Processing
continues.
Operator Response: None.
IED0491
OLT CONTROLS RESOURCE
grpname,rln}
address
{ station
COMMAND REJECTED
Explanation: A command that would modify the status of the
resource was entered, but the resource is currently controlled
by the on-line test (OlT) feature. The resource may be a line
(grpname,rln), a subchannel address (address), or a station
(station).
System Action: The requested function is not performed.
Processing continues.
Operator Response: Wait until OLT has released the resource
before attempting to modify the resource status.
Problem Determination: If the resource named in the message
is not identical to that specified in the command, or if online
test is not active in the system, see Table I, items 2, 10, 29.
Save the terminal listing for the device which entered the
command or record what is currently displayed on the graphic
device.
IED0501
station OPTION opt MODIFIED
Explanation: An operator command to modify the contents of
the option field named opt associated with the station named
station was entered. This message confirms that the requested
action was taken.
System Action: The option field is modified as requested.
Processing continues.
IED0511
Problem Determination: If a non-zero value is specified for
trace and the message recurs, see Table I, items 2, 10, 29.
Instruct the terminal user to retain the terminal listing or
record what is currently displayed on the graphics device.
IED0561
station SET FOR HOLD, SEQ-OUT = nnn
Explanation: An operator command to intercept (hold) the
station named station was entered. This message confirms that
the action is taken. In the message text, nnn is the output
sequence number associated with the station at the time the
station is intercepted.
System Action: The named station is intercepted. Processing
continues.
Operator Response: None.
IED0571
station ALREADY SET FOR HOLD
Explanation: An operator command to hold the station named
station was entered, but the station is already intercepted.
System Action: The requested action is not taken. Processing
continues.
Operator Response: Retry the command.
IED0531
station ALREADY RELEASED
Explanation: An operator command to release the station
named station was entered. The station is already released.
System Action: The requested action is not taken. Processing
continues.
Operator Response: None.
IED0541
station RELEASED, SEQ-OUT = nnn
Explanation: An operator command to release the station
named station was entered. This message confirms that the
station is released. In the message test, nnn is the sequence
number for output currently associated with the station.
System Action: The station named station is released.
Processing continues.
Operator Response: None.
IED0551
I/O TRACE CANNOT BE ALTERED
Explanation: An operator command to start or stop the TCAM
line I/O interrupt trace facility was entered, but there is no
trace table available into which entries can be made.
System Action: The requested action is not taken. Processing
continues.
Operator Response:' If the trace feature is required, close down
the system and restart; when message IED002A is issued,
enter REPLY xx, 'T = nn,U,' where nn is a non-zero value.
Otherwise, refrain from attempting to start or stop the trace
facility.
Ina NOT CAPABLE OF AUTO POLL
Explanation: An operator command to start or stop autopolling
on the line named Ina is entered, but the line is not ,capable of
being autopolled (per its unit control block).
System Action: The requested action is not taken. Processing
continues.
Operator Response: None.
IED0581
IED0521
station OPTION opt DATA FORMAT INVALID
Explanation: An operator command to modify the contents of
the option field named opt associated with the station named
station was entered, but the data format specified in the
command differs from the definition of the option field format.
System Action: The option field is not modified. Processing
continues.
Operator Response: Verify that the type specified in defining
the option matches that specified in the command. Respecify
the command.
Problem Determination: If the types are identical and the
problem recurs, or if the station named station or the option
named opt in the response do not agree with the
corresponding values in the command, see Table I, items 2,
10, 29. Instruct the terminal user to retain the terminal listing
or record what is currently displayed on the graphics device.
1grpname,
rlnlsENSE COUNT = sens SETTING = zz
address
statname
Explanation: The operator entered a command to modify the
setting of the sense information for a station or line. sens is
the requested sense count and zz is the requested sense type.
This message confirms that the requested action is taken.
System Action: Sense information is modified for the station or •
line named. Processing continues.
Operator Response: None.
Problem Determination: If the line or station named xxx, the
sense count, or the setting in the response do not agree with
the corresponding values in the command, see Table I, items
2, 8, 10, 29. Instruct the terminal user to retain the terminal
listing or record what is currently displayed on the graphics
device.
IED0591
jgrpname, rlntLlST STATUS
1address
5
= stat, ...
Explanation: The operator entered a command to display the
status of the invitation list for a line. In the message text, stat
represents the equivalent of the status information bits.
System Action: Processing continues.
Operator Response: None.
IED0601
station CANNOT BE HELD
Explanation: An operator command to hold the station named
station was entered, but the station is not capable of being
held (for instance, it is on a line which is not open or has been
opened idle, or no HOLD macro has been coded in the
Message Control Program, it is defined with main storage only
queues.)
System Action: The requested action is not taken. Processing
continues.
Operator Response: None.
Section 7: lED Messages - Telecommunications Access Method
7-9
IED0611
POLLING DELAY FOR station CANNOT BE ALTERED
0020
Explanation: An operator command to modify the polling
interval for the line associated with the station named station
is entered, but the line is a switched (dial) line.
System Action: The requested action is not taken. Processing
continues.
Operator Response: None.
IED0621
station OPTION opt CANNOT ACCEPT SPECIFIED
DATA
Explanation: An operator command to modify the contents of
the option field named opt associated with the station named
station was entered, but the data to replace the current setting
of the option field is greater in length than the field.
System Action: The requested action is not taken. Processing
continues.
Operator Response: Verify that the data length defining the
option is not less than that specified in the command. Reenter
the corrected command.
Problem Determination: If the replacement data will fit in the
option field and the problem recurs, or if the station named
station or the option named opt in the response do not agree
with the corresponding values in the command, see Table I,
items 2, 29. Instruct the terminal user to retain the terminal
listing or record what is currently displayed on the graphics
device.
IED0631
CLOSEDOWN IN PROGRESS - COMMAND REJECTED
Explanation: System closedown is in progress. All further
operator commands will be rejected.
System Action: The requested action is not taken. System
closedown continues.
Operator Response: Refrain from entering TCAM operator
commands.
IED0641
LINE Ina CONTROL UNIT NOT OPERATIONAL
Explanation: The Transmission Control Unit (TCU) to which the
specified line is connected is not operational. The line is not
immediately available for message transmission.
System Action: Processing continues, but stations on the line
named by Ina cannot be used for message transmission.
Operator Response: The TCAM job that is being started may be
canceled and restarted after the control unit is made
operational, or· after the TCU is made operational this line may
be activated by entering VARY (line),ONTP. If the control unit
is online and the problem recurs, see Table I, item 30.
0024
0028
6.
System Action: Initialization of the MCP is terminated. The
error code is returned to the user in register 15 by the INTRO
macro instruction. If the MCP is not halted when INTRO's
return code is non-zero, results are unpredictable.
Programmer Response: If rc is 0008 or 0012, either increase
the region size, or specify smaller optional features. If rc is
0004, close down the MCP currently in the system before
attempting to restart the MCP for which this message is
issued. If rc is 0016 or 0020, verify that the terminal table
entries are correct in the assembly, close down the MCP
currently in the system, and reassemble and restart the job
with the corrected entries. If rc is 028, either the TCAM MCP
does not reside on the installation - defined authorized library.
The MCP is not in the program properties table, or data sets
specified on the JOBUB or STEPUB DO statement are not
authorized.
Operator Response: Contact the system programmer.
Problem Determination: Table I, items Sa, 10, 29.
IED0671
INITIALIZATION ERROR rc
Explanation: The non-resident initialization routines have
returned a decimal return code, represented in the message
text by rc, to the'INTRO macro instruction. This code is passed
on to the user's next instruction by the INTRO macro
instruction. The values of rc and their meanings are:
0004
The Message Control Program (MCP) initialization
routine has detected the presence of another MCP in
this system.
0008
Sufficient virtual storage was not available to satisfy a
GETMAIN request in one of the non-resident
initialization routines.
0012
Sufficient virtual storage was not available to satisfy a
GETMAIN request in one of the non-resident
initialization routines.
0016
A terminal definition error. The module has found one
or more incorrectly specified TERMINAL macro
instructions, while sorting the terminal name table.
7-10
VS2 System Messages (VS2 Release 3.7)
TCAM INITIALIZATION BEGUN
Explanation: The parameters on the IEDQDATA DO statement
have been examined and found satisfactory. Formatting of the
message queues data set by the IEDQXA utility has begun.
System Action: Processing continues.
Programmer Response: None. Information only.
Operator Response: None. Information only.
IED0681
IED0651
One of the following errors has occurred in defining
the primary operator control terminal:
a) The terminal defined as the primary operator
terminal could not be found in the terminal name
table.
b) The primary operator control terminal did not have
send and receive capabilities.
c) The primary operator control terminal was not
defined as being a possible secondary operator
control terminal.
An error occurred while sorting the device 10 table for
a concentrator terminal. One of the following errors
occurred:
a) The terminal-name table offset in the device 10
table was not found in the offset table.
b) The device-dependent fields of the terminal entry,
pointed to by the device 10 entry did not indicate a
concentrator or attached terminal.
The MCP is not executing in authorized protection key
UNABLE TO OPEN IEDQDATA
Explanation: An attempt has been made to format a message
queues data set on disk by the IEDQXA utility program, but the
IEOQDATA DO statement for this utility is missing. This
message may be due to a possible error while attempting to
read the JFCB for the IEOQDATA DO statement.
System Action: The IEOQXA utility abnormally terminates with
an error code of 20 in register 15.
Programmer Response: Probable user error. Supply the missing
DO statement and resubmit the initialization job. Have a listing
of the utility JCL available before calling IBM for programming
support.
.
Operator Response: Contact the system programmer.
IED0691
INVALID KEYLEN FOR IEDQDATA
Explanation: Either the DCB = operand of the IEDQDATA DO
statement for the IEOQXA formatting utility program has been
omitted, or DCB = KEYLEN = integer has been coded on this
DO statement and the integer is less than 31.
System Action: The IEDQXA utility abnormally terminates with a
return code of 8 in register 15.
Programmer Response: Probable user error. Supply a correct
IEDQDATA DO statement and resubmit the initialization job. If
the problem recurs, have a listing of the utility JCL available
before calling IBM for programming support.
Operator Response: Contact the system programmer.
IED0701
IEDQDATA DOES NOT SPECIFY CONTIG SPACE IN
CYLINDERS
Explanation: The SPACE = keyword on the IEDQDATA DO
statement for the IEDQXA disk-initialization utility has specified
CYL but not CONTIG, or CONTIG but not CYL, or neither. The
following is an example of a properly coded SPACE =
parameter:
/ /IEDQDATA DO (other operands),SPACE =
(CYL,(2,2)"CONTIG)
System Action: The IEDQXA utility abnormally terminates with a
return code of 16.
Programmer Response: Probable user error. Correct the
SPACE = parameter on the IEDQDATA DO statement and
resubmit the initialization job. If the problem recurs, have a
listing of the utility JCL available before calling IBM for
programming support.
Operator Response: Contact the system programmer.
IED071 I
UNEQUAL PRIMARY AND SECONDARY EXTENTS ON
IEDQDATA
Explanation: The SPACE = keyword on the IEDQDATA DO
statement for the IEDQXA disk-initialization utility does not
specify a number of cylinders for secondary allocation equal to
the number of cylinders specified for primary allocation; TCAM
requires that the primary and secondary allocation be equal.
This message also occurs if not enough space was available
for contiguous secondary allocation.
System Action: The IEDQXA utility abnormally terminates with a
return code of 16 in register 15.
Programmer Response: Probable user error. Respecify the
SPACE = parameter of the IEDQDATA DO statement so that
the primary and secondary allocation are equal, and resubmit
the initialization job. Have a listing of the utility JCL available
before calling IBM for programming support.
Operator Response: Contact the system programmer.
IED0721
I/O ERROR ON IEDQDATA
Explanation: An I/O error from which recovery cannot be made
has occurred during an attempt to format a message queues
data set by means of the IEDQXA utility.
System Action: Initialization is terminated with a return code of
12 in register 15. The data set is not completely formatted.
Programmer Response: Use the IEHPROGM system utility to
scratch the data set, and resubmit the initialization job. If
possible, try to avoid the allocation of the same area, as it
probably contains a bad track .
.operator Response: Start TCAM only if it does not require the
message queue data set defined by the IEQDATA DO
statement in the message text. Otherwise, contact the system
programmer. If the problem recurs, use the IBCDASDI
independent utility to assign alternates for defective tracks on
the volume being used.
IED0741
TCAM INITIALIZATION COMPLETE
Explanation: A message queues data set on disk has been
completely formatted by the IEDQXA utility program, and is
ready for use by a TCAM Message Control Program.
System Action: Normal end of job.
Operator Response: None. Information only.
IED0751
END OF EXTENT. RECORD COUNT IS nnn, TIME IS
xxx SEC
Explanation: One extent (volume) of a message queues data
set residing on disk has been formatted by the IEDQXA utility
program. The record count, indicated by nnn, is the cumulative
total. That is, nnn is the total number of records formatted
thus far in the entire data set, and not just in this one extent.
nnn = cumUlative record count
xxx = cumulative elapsed time
System Action: Processing continues ..
Operator Response: None. Information only.
IED0761
TCAM NON-REUSABLE DISK THRESHOLD
CLOSEDOWN
Explanation: The message queues data set located on
nonreusable disk has received enough messages so that the
percentage of the data set area on disk specified by the
THRESH = operand of the DCB macro instruction for the data
set has been exceeded.
System Action: The system begins a flush closedown of the
TCAM MCP. A flush closedown sends all queued messages to
their destinations before closing.
Operator Response: Contact the system programmer.
Programmer Response: Reformat the non-reusable disk
message queue data set with the IEDQXA utility, and start the
job with S = C coded for the INTRO macro instruction. If this
message is followed by a system completion code 045 with a
user code of 001, the THRESH = value specified was too high,
and register 6 points to a CPB.
Problem Determination: If the value in CPB+X'2D' (3 bytes in
length) greatly exceeds the total number of records formatted
in the non-reusable disk data set, check Table I, items Sa, 10,
29.
IED0771
station OPTION opt DATA CHARACTER INVALID
Explalllation: An operator command to modify the contents of
the option field named opt associated with the station named
station is entered, but the contents of the modification data do
not agree with the framing characters surrounding the data.
System Action: The requested action is not taken. Processing
continues.
Operator Response: Verify that the data 'specified within the
framing characters is invalid for the framing characters used.
Reenter the correct command.
Problem Determination: If the data is valid and the problem
recurs, or if the station named station or the option named opt
in the response do not agree with the corresponding values in
the command, check Table I, items 2, 10, 29. Instruct the
terminal user to retain the terminal listing or record what is
currently displayed on the graphics device.
IED0781
DLQ TERM ERROR
= operand of the
INTRO macro cannot be a dead-letter queue either because it
is a TSO station or because it is undefined.
System Action: The termname table offset of the station
defined as the dead-letter queue is not stored in the address
vector table (AVT) and processing continues.
Programmer Response: Probable user error. If no action is
taken, the dead letter queue is not defined for the MCP. If a
dead-letter queue is desired do the following:
• Terminate the job.
• Specify a valid station for the DLQ = operand of the INTRO
macro by either 1) recoding the INTRO macro and
Explanation: The station named in the DLQ
Section 7: lED Messages - Telecommunications Access Method
7-11
I
I
reassembling, or 2) by entering REPLY xx,'Q = name,U' to
message IED002A at execution time.
• Resubmit the job.
Problem Determination: Table I, items 5a, 10, 29.
IED0791
ENDING STATUS NOT RECEIVED FROM LINE Ina LINE UNAVAILABLE
Explanation: The Transmission Control Unit to which this line is
connected is not operational. An interrupt indicating successful
completion of the initial channel program has not occurred for
this line, and the line is not available for sending or receiving.
System Action: The error message is written to the console
and the next line in the line group is checked to see if the
initial channel program has completed. If it has not, the error
message is written again.
Operator Response: None. The line is not usable. If the problem
recurs call IBM for hardware support.
Problem Determination: Table I, items 2, 30.
IED0801
START OF TCAM SYSTEM DELAY
Explanation: Someone has entered MODIFY id,INTERVAL =
SYSTEM which activated the system interval.
System Action: Polling and addressing on multipoint lines are
suspended for the duration of the interval currently defined for
the system. Switched (dial) lines are not affected. If there are
no dial lines in the system, this message will be'followed by
what seems to be a system WAIT state. At the end of the
interval, operations will automatically resume.
Operator Response: None. At the end of the system interval,
normal operations will resume. Changing the length of the
delay interval with an operator command will not affect this
delay, only subsequent ones. TCAM may be stopped or
cancelled during a system delay.
IED0811
END OF TCAM SYSTEM DELAY
Explanation: The system interval has expired.
System Action: The Message Control Program is resuming
normal operations.
Operator Response: None. Information only.
IED0821
ddn CHECKPOINT DISK ERROR -- DATA SET NOT
OPENED
Explanation: Either the control record for the checkpoint data
set could not be read during a restart, or none of the
environment records could be read during a restart. As a
result, the checkpoint data set is not open. The ddname of the
data set is ddn.
System Action: The checkpoint data set is not opened, the
environment is not reconstructed, and the checkpoint facility is
not available to the Message Control Program. The MCP
terminates abnormally with system completion code 045-9.
Note: This message will also result if you created a data set
with one level of TCAM and tried to warm start with another
level of TCAM.
Programmer Response: The IBCDASDI utility program should be
used following closedown to clean up the disk on which the
data set is located, if the checkpOint facility is desired.
Problem Determination: Table I, items 29 or 30.
IED0831
CHECKPOINT DISK ERROR -- RECOVERY FROM
PREVIOUS RECORD
Explanation: TCAM's checkpoint routine could not read the
environment record that was to be used to reconstruct the
environment. If possible, the next-most-recent environment is
used to reconstruct.
7 - 12
VS2 System Messages (VS2 Release 3.7)
System Action: The next-most-recent environment record is
used to reconstruct the TCAM environment.
Programmer Response: Information. The environment is not as
well reconstructed when older records are used. If the problem
recurs frequently, the IBCDASDI utility program should be used
to clean up the disk on which the data set is located. In this
case, a cold restart only can be performed.
Problem Determination: Table I, item 30.
IED0841
CHECKPOINT DISK ERROR - - RECOVERED
Explanation: An error occurred while TCAM was writing an
environment, checkpoint request or incident record into the
checkpoint data set, but space for another such record was
available in the data set.
System Action: Since space was available, TCAM wrote the
record into the available space and processing continues. No
data was lost.
Programmer Response: Information. If this message recurs
often, IBCDASDI utility program should be used following
closed own, to clean up the disk. The restart following disk
cleanup must be a cold restart.
Problem Determination: Table I, item 30.
IED0851
t
CHECKPOINT DISK ERROR - - j CKREQ
RECORD IGNORED
INCIDENT ~
t
Explanation: The specified record (checkpoint request or
incident) could not be read at restart time, and was therefore
not used by TCAM in reconstructing the environment.
System Action: The system environment is reconstructed, but
the specified record is not included. Processing continues.
Programmer Response: Information. The reconstructed
environment is not as up-to-date as it would be otherwise. If
this message recurs frequently, the IBCDASDI utility program
may be used following closed own to clean up the disk on
which the checkpoint data set is located. The restart following
disk cleanup must be a cold restart.
Problem Determination: Table I, item 30.
IED0861
CHECKPOINT DISK ERROR --
~ ENVIRONMENT
tCKREQ,name
t
~
Explanation: Due to a faulty disk, no environment or checkpoint
request record area is available to hold the latest such record
taken.
System Action: The data in the record is lost. Processing
continues.
Programmer Response: If a complete checkpoint facility is
desired, close down the Message Control Program, use the
IBCDASDI utility program to clean up the disk, and do a cold
restart. A cold restart is the same as the original start-up.
Problem Determination: Table I, item 30.
IED0871
CHECKPOINT DISK ERROR -- CONTROL RECORD ddn
Explanation: Due to an I/O error on disk, the control record
does not reflect the latest environment checkpoint taken. As a
result, this environment checkpoint record will not be used for
restart. The ddname of the data set is indicated by ddn.
System Action: Processing continues.
Programmer Response: Information. The environment
reconstructed after restart becomes increasingly less accurate
as older records are used. The IBCDASDI utility program may
be used to clean up the disk after closedown of the Message
Control Program. If it is, only a cold restart (identical to the
original start-up) can be performed. If the problem recurs, call
IBM for hardware support.
Problem Determination: Table I, item 30.
IE00881
station ON DIAL LINE - CANNOT BE VARIED
System Action: The command is rejected. Normal processing
continues.
Operator Response: Close down the TCAM MCP and rerun;
when message IED002A is issued, enter REPLY xx,'O = nn,U',
where nnis a non-zero value.
Problem Determination: Table I, items 10, 29.
Explanation: An operator command to start or stop the station
named station for entering data is entered, but the station is
on a switched (dial) line.
System Action: The requested action is not taken. If a VARY
station, ONTP,b is entered, the station will be released if it is
held. If as VARY station, OFFTP,b is entered, the station will
be held if it is eligible. Processing continues.
Operator Response: None.
IE00901
IE00961
station IS NOT SINGLE ENTRY
Explanation: The indicated subtask of TCAM has abnormally
terminated, and the related functions will no longer be
performed.
System Action: Limited processing continues.
Programmer Response: Determine the reason for the abnormal
termination, correct and rerun. Close down the TCAM job and
rerun.
Problem Determination: Table I, items Sa, 10, 29.
Explanation: An operator command requesting display or
modification of station information for the station named
station is entered, but station is not a single station entry.
System Action: Processing continues.
Operator Response: None.
IE00911
LINE FOR station NOT OPEN
Explanation: An operator command requesting display or
modification of status for the station named station is entered,
but the line for the station is not open or has been opened
idle.
System Action: Processing continues.
Operator Response: Ensure that the correct station name is
specified and that the line is open and active; then retry the
command.
IE00921
TCAM IS CLOSED DOWN
Explanation: A TCAM closedown has been completed and
control has returned to the code which follows the READY
macro instruction coded in the Message Control Program.
System Action: Normal end of job.
Programmer Response: None.
Operator Response: None.
IE00981
binary synchronous line named Ina be started was entered, but
the specifications for the dual communication interface
contained in the UCB do not agree with the specifications
contained in the DCB.
System Action: The command is rejected. Processing
continues.
Operator Response: None.
SET SYSTEM INTERVAL COMMAND ACCEPTED
Explanation: The operator entered a command requesting
activation of the system interval, which suspends polling and
addressing on multipoint lines to polled stations. This message
confirms that the command has been accepted.
System Action: A system interval is activated. Processing
continues.
Operator Response: None.
IED0941
IED0971
BISYNC ERROR - LINE Ina CANNOT BE STARTED
Explanation: An operator command requesting that the 2701
IE00931
CHECKPOINT
.\ NO LONGER ACTIVE
OPERATOR CONTROL
COMWRITE
TOTE
CORE REQUESTED FOR ON-LINE TEST NOT
AVAILABLE
Explanation: The amount of virtual storage requested by the
OLTEST = operand of the INTRO macro instruction is not
available. However, the minimum amount of virtual storage
required to run one on-line test is available.
System Action: Only one on-line test may be run at a time.
Limited processing continues.
Programmer Response: Probable user error. If more than one
on-line test is to be run simultaneously, close down the
Message Control Program (MCP) and rerun with a larger
region specified.
Problem Determination: Table I, items 10, 29.
DCB NOT CLOSED FOR MESSAGE PROCESSING
PROGRAM - jjj
Explanation: A TCAM closedown has started, but a TCAM DCB
in an application program is still open. jjj specifies the job
name of the mother task.
System Action: The closedown will not complete until the
closed own is performed for the DCBs.
Operator Response: No action required if the DCB is closed by
the application program EODAD exit routine and closed own
proceeds normally. (STOP = and EODAD = operands must be •
properly specified on the application program input DCB.)
Otherwise, cancel the job named jjj arid inform the application
programmer that his job was canceled so closedown of the
Message Control Program could proceed.
IED0991
ROUTINE LOADED
Explanation: The routine that was called by the command
MODIFY id,DEBUG = L,yyy is loaded and initialfzed.
System Action: Normal processing continues.
Operator Response: None. Information only.
IED1001
ROUTINE DEACTIVATED
Explanation: The routine designated in the command MODIFY
id,DEBUG
= D,yyy
is deactivated and deleted.
System Action: Normal processing continues.
Operator Response: None. Information only.
IED1011
RESTART IN PROGRESS
Explanation: The requested operation cannot be processed
because TCAM is being restarted.
System Action: The command is ignored. Normal processing
continues.
IED0951
MODIFY OLT REJECTED - OLT NOT ACTIVE
Explanation: The request for an on-line test (OLT) is rejected
because the subtask that handles the requests has either
terminated or was never activated (because OLTEST == 0
(0= 0) was specified in the INTRO· macro).
Operator Response: Reenter the command after the restart is
completed. If the problem recurs, obtain a SYSABEND dump of
the region in which the Message Control Program resides.
Problem Determination: Table I, item 29.
Section 7: lED Messages - Telecommunications Access Method
7-13
I
IED1021
INVALID OPERAND
Explanation: The format of the command MODIFY
id,DEBUG == subparameter, routine is incorrect.
System Action: The command is ignored. Normal processing
continues.
Operator Response: Probable error caused by improper
command specification. Check for errors in one or more of the
following operands:
• A subparameter other than L or 0 is specified.
• An invalid routine name is specified. Valid names are
IEDQFElO, IEDQFE20, IEDQFE30, and IEDQFE40. Reenter
the command with the correct format.
Problem Determination: Table I, items 2, 29.
Programmer Response: Probable user error. Instruct the
operator to enter REPLY xx, 'G = YES' as a response to
message IED002A to insure proper initialization of the
debugging aids. Make sure that a DO card is present
specifying the COMWRITE data set, either on magnetic tape or
disk.
Operator Response: Notify the system programmer.
Problem Determination: Table I, items 2, 11, 29. Have available
the output of AMDSADMP, formatted by AMDPRDMP showing
the nucleus and the TCAM region.
IEDI091
ROUTINE NOT DELETED
Explanation: A request has been made to deactivate a routine,
Explanation An operator command requesting activation of a
debugging routine is entered, but the routine is already active.
System Action: The command is ignored. Normal processing
continues.
Operator Response: None.
Problem Determination: Table I, items 2, 11, 29. Have available
the AMDSADMP output, formatted using AMDPRDMP showing
the nucleus and the TCAM REGION.
and the SVC 9 (DELETE) function failed.
System Action: The routine is not deleted. Normal processing
continues.
Programmer Response: This message is a result of a failure of
the DELETE function of the OS/VS supervisor. The requested
module to be deleted could not be found by OS/VS; however,
it was found by the TCAM operator control facility.
Problem Determination: Table I, items 2, 11, 29. Have available
the AMDSADMP output, formatted by AMDPRDMP showing the
nucleus and TCAM region.
IED1041
IED1121
IED1031
ROUTINE ALREADY ACTIVE
ROUTINE NOT ACTIVE
TCAM REQUESTED COMWRITE CLOSEDOWN
Explanation: A request has been made to deactivate a
Explanation: TCAM is closing down and is closing the FE
debugging routine that is not active.
System Action: The command is ignored. Normal processing
continues.
Operator Response: None.
Problem Determination: Table I, items 2, 11, 29. Have the
operator control console listing available. Have available the
AMDSADMP output, formatted using AMDPRDMP and showing
the nucleus and the TCAM region.
Common Write (COMWRITE) subtask.
System Action: Normal end of job follows.
Operator Response: None. Information only.
IED1051
RETURN CODE == rc
Explanation: A user-written routine has passed a return code to
a debugging routine of the operator control facility.
System Action: Normal processing continues.
Programmer Response: The indicated return code probably
denotes an exceptional condition in the user routine.
Determine the problem from the return code given and correct
the problem.
IED1061
IED1131
I/O ERROR Ina,statsens,recordtype,COMWRITE
CLOSING
Explanation: A permanent I/O error has been detected on the
indicated device. In the message text, Ina, is the hardware line
address, statsens is the CSW status byte and sense byte, and
recordtype is the type of record (BUFF, 10TR, or STCB) being
written when the I/O error occurs.
System Action: The FE Common Write (COMWRITE) task
terminates abnormally with a system completion code of 044.
Operator Response: Probable hardware error. Check recording
medium (tape or disk) for damage. If COMWRITE is required,
TCAM must be stopped and restarted specifying another
device for COMWRITE.
Problem Determination: Table I, items 18, 30.
MULTIPLE REQUEST
Explanation: The routine requested is already active in the
IED1141
cde ABEND COMWRITE CLOSING
Explanation: The FE Common Write (COMWRITE) task has
system.
System Action: The request is ignored. Normal processing
continues.
Programmer Response: The requested routine was probably not
loaded via a program other than by the MODIFY id,
DEBUG == x,yyy operator command. Determine how the module
was loaded previously and correct.
Problem Determination: Table I, items 2, 11, 29. Have available
the AMDSADMP output, formatted using AMDPRDMP and
showing the nucleus and the TCAM region.
Operator Response: Notify the system programmer.
abnormally ended with the system completion code indicated
by cde.
System Action: The COMWRITE task is terminated with the
indicated code.
Programmer Response: A system completion code of 044 is
normally caused by invalid or missing JCL. Examine the job
control statements, and ensure that a COMWRITE DO card
exists and is valid. Rerun the job.
Operator Response: Contact the system programmer.
Problem Determination: Table I, items Sa, 29.
IED1071
IED1151
COMWRITE NOT· ACTIVE
Explanation: A request has been made to activate a debugging
routine which requires that the FE Common Write task
(COMWRITE) be active. COMWRITE is not active because
COMWRTE == YES was not specified on the INTRO macro
instruction.
System Action: The request is ignored. Normal processing
continues.
7 -14
VS2 System Messages (VS2 Release 3.7)
userid DATA AREA EXCEEDS CORE
Explanation: This message is caused by an invalid parameter
list being passed to the FE Common Write (COMWRITE) task.
Sntem Action: The request is ignored. Normal processing
continues.
Operator Response: Contact system programmer.
Programmer Response: Probable user error. Examine the user
routine using 'userid' and correct any errors.
Problem Determination: Table I, items 2, 11, 29. Have the
COMWRITE output data set. Have available the AMDSADMP
output, formatted by AMDPRDMP, showing the nucleus and the
TCAM region.
IEOl161
userid PARMLIST NOT ON FULLWORD BOUNDARY
Explanation: This message is caused by an invalid parameter
list being passed to the FE Common Write (COMWRITE) task.
System Action: The request is ignored. Normal processing
continues.
Operator Response: Contact the system programmer.
Programmer Response: Probable user error. Examine the user
routine using 'userid' and correct any errors.
Problem Determination: Table I, items 2, 11, 29. Have the
COMWRITE output data set. Have available the AMDSADMP
output formatted by AMDPRDMP, showing the nucleus and the
TCAM region.
IE01171
userid BLKSIZE EXCEEDS DEVICE SPECS
Explanation: A parameter list passed to the FE common write
(COMWRITE) task describes a block of data whose length
exceeds the maximum that the device containing the
COMWRITE data set can handle.
System Action: The request is ignored. Normal processing
continues.
Operator Response: Contact system programmer.
Programmer Response: Probable user error. Examine the user
routine using 'userid' and correct any error.
Problem Determination: Table I, items 2, 11, 29. Have the
COMWRITE output data set. Have available the AMDSADMP
output, formatted by AMDPRDMP, showing the nucleus and the
TCAM region.
IE01181
PERMANENT I/O ERROR ON TRACE UNIT
Explanation: While reading the SYSUTI data set, a permanent
I/O error has been encountered.
System Action: Processing terminates.
Operator Response: Check the recording medium (tape or disk)
of the. trace data set for damage. If the medium is tape, clean
the device.
Problem Determination: Table I, items 18, 30.
IE01191
UNABLE TO OPEN ddn
Explanation: The system was unable to open the data set
named ddn.
System Action: Processing terminates.
Operator Response: Probable user error. Check and correct the
job control language for the indicated data set and rerun the
job. This message is normally caused by the lack of a DO
statement or by the ddname being misspelled.
Problem Determination: Table I, items 1, 2, 29.
IE01201
REQUESTED TIME NOT FOUND
Explanation: The time specified in the BLOCK == parameter of
the EXEC statement for the COMEDIT printing utility was not
IED1221
INVALID MESSAGE CHAIN
Explanation: The chaining sequence of the message queues
data set has been invalidated.
System Action: Processing terminates.
Programmer Response: None.
Problem Determination: Before calling IBM for programming
support make sure that a listing of the message queues data
set is available.
IE01231
INVALID PARAMETERS
Explanation: While scanning the EXEC statement parameters for
the IEDQXB or IEDQXC printing utilities, an error has been
detected.
System Action: If the IEDQXB utility is being used, the error is
noted on the SYSPRINT data set. For either utility, processing
terminates.
Programmer Response: Probable user error. Check and
correctly specify the parameters on the EXEC statement. For
the proper specification of parameters, refer to the OS/VS
TCAM Programmer's Guide GC30-2041).
Problem Determination: Table I, items 1, 2, 29.
IED1241
QUEUE HAS BEEN WRAPPED
Explanation: While running the IEDQXC printing utility,. the
message queues data set has run out of space and started to
overlay the beginning of the data set (wrap-around).
System Action: Since the message queues data set can no
longer be formatted reliably, the IEDQXC printing utility is
terminated.
Programmer Response: In order to obtain the printed output
from the message queues, process it via a system utility. To
avoid the wrap-around in the future, format a larger message
queues data set with the IEDQXA utility.
Problem Determination: Before calling IBM for programming
support, make sure that a listing of the message queues data
set is available.
IED1251
BLOCK == PARM REQUIRES TAPE INPUT
Explanation: The BLOCK == keyword parameter was specified in
the EXEC statement for the COMEDIT formatting utility, but the
SYSUTI DO card specified a direct access device.
System Action: The trace data set is formatted with the
BLOCK == parameter ignored. Normal processing continues.
Programmer Response: None.
Problem Determination: Table I, items 1, 5a, 29. Instruct the
operator to cancel the job, requesting a dump and save the
output.
IED1211
found on the tape dataset described by the SYSUTI DO
statement. Two conditions may cause the error:
• There were no subtask control blocks (STCBs) or buffers on
the trace data set.
• The time specified is later than the latest time recorded in
the trace data set.
System Action: Processing terminates. No printout is provided.
Programmer Response: Probable user error. Ensure that STCBs
are being traced and the BLOCK == parameter is correctly
specified. The time stamp fields in the various trace records
on tape are chronologically earlier than the BLOCK ==
parameter.
Problem Determination: Table I, items 1, 2, 29. Have a listing
of the COMWRITE data set available.
xxx BYTES NEEDED
Explanation: The operator entered MODIFY id,DEBUG == x,yyy,
but insufficient storage exists for loading the requested
debugging aid.
System Action: The requested debugging aid is not loaded.
Normal processing continues.
Programmer Response: Specify a larger region size for the
TCAM Message Control Program (MCP).
Operator Response: Specify a larger region size for the TCAM
MCP, if possible. Otherwise, contaCt the system programmer~
Problem Determination: Table I, items Z, 10, 11, 29. Have
available the AMDSADMP output formatted by AMDPRDMP
showing the nucelus and TCAM region.
Section 7: lED Messages - Telecommunications Access Method
7-15
41
IED1271
OlT REQUEST REJECTED, CONTROL TERMINAL
UNIDENTIFIED
Explanation: This message is issued when the symbolic name of
the control terminal specified in the Test Request Message
(TRM) is not contained in the TCAM terminal table, or an
invalid control terminal field is found in the TRM (for example,
no slash foliowing the prefix).
System Action: The TRM is canceled. Processing continues.
Operator Response: Reenter the TRM and specify a valid
control terminal. If there is a valid translate table for the TRM,
no more than eight characters between the prefix and the first
slash, and the control terminal. is identical to the name of an
entry in the TCAM terminal table, obtain and have available
the following before calling IBM for programming support:
• A listing of the TCAM Message Control Program.
• The TRM that was canceled.
• The control terminal printout.
IED1281
ALTERNATE PRINTER REQUESTED BY OlT ALREADY
IN USE
Explanation: This message is issued when the alternate printer
requested in the option field of a Test Request Message (TRM)
has already been assigned as a test device to another On-line .
Test (OlT). The TRM is canceled and must be reentered to
initiate an OlT.
System Action: The TRM is canceled. Normal processing
continues.
Operator Response: Reenter the TRM and specify an alternate
printer not in use.
Problem Determination: If this problem recurs and the alternate
printer is not in use, obtain and have available the following
before calling IBM for programming support:
• A listing of the TCAM Message Control Program.
• The TRM that was canceled.
• The control terminal printout.
IED1301
OlT REQUEST REJECTED, CONTROL TERMINAL NOT
OPEN
Explanation: This message is issued when TOTE determines
that the specified control terminal is not on an opened line.
The problem could be that the required DO card is missing
from the TCAM JCL. The Test Request Message (TRM) is
canc~ed.
.
System Action: The TRM is rejected and normal processing
continues.
Operator Response: Check JCl for a DO card for the control
terminal. Restart the Message Control Program with a valid DO
card for this terminal. Reenter the TRM.
Problem Determination: If the problem recurs, obtain and have
available the following before calling IBM:
• The TRM.
• The control terminal printout.
IED1331
C. T. REQUESTED BY OlT ASSIGNED TO ANOTHER
OlT
Explanation: This message is issued when the control terminal
(CT) device requested in the Test Request Message (TRM) has
already been assigned as a test device to another On-line Test
(OlT). The TRM is canceled and must be reentered to initiate
an on-line test.
System Action: The TRM is canceled. Normal processing
continues.
Operator Response: Reenter the TRM and specify a control
terminal not in use.
Problem Determination: If this problem recurs and the control
terminal is not in use, have the following available before
calling IBM for programming support:
• A listing of the TCAM Message Control Program.
• The TRM that was canceled.
• The control terminal printout.
IE01381
ERROR SORTING DEVICE 10 TABLE, xxx
Explanation: An error occurred while sorting the device 10
table. xxx identifies the terminal name being processed when
the error occurred.
System Action: A return code of X'18' is passed to the
initialization routine (lEOQOA) in register 15. IEOQOA issues
error message IE00651, suspends calling other INTRO,
nonresident, initialization routines, and returns to INTRO, which
passes control to the next instruction.
Problem Determination: Execute the AMASPZAP service aid
program to obtain a dump of module IEDQOA at the point the
error message was issued. Table I, items 3, 10, 16, 29.
IE01391
PRINTING STOPPED
Explanation: A maximum of 5 IE01401 'TCAM DISK ERROR. ..'
messages have been printed; message IE01391 indicates that
there are more to be printed.
System Action: Printing of further messages has been
suppressed.
Operator Response: None.
IED1401
TCAM DISK ERROR
cde,bbbbbbbb,cccccccccccccccc,dd,eeffff~f
Explanation: An error occurred while reading from, or writing
to, disk:
cde Contents of IOBECBCC (completion code).
b-b Hexadecimal equivalent of IOBFlAGl-2 and IOBSENSO-l.
c-c Hexadecimal equivalent of 8-byte IOBCSW (first byte if
IOBFlAG3).
d-d Character UCB id.
e-e Either RO (Read) or WR (Write).
f-f
Hexadecimal equivalent of 3-byte CPOADOR (disk record
number).
See OSjVS2 TCAM logic, SY30-2040, for further explanation
of these fields.
System Action: Processing continues.
Operator Response: None.
IED1431
station GENERAL POll STARTED
Explanation: An operator command was entered to activate
the general poll invitation characters associated with the
station named station.
System Action: The general poll invitation characters were
activated and all specific poll characters on the control unit
were deactivated.
Operator Response: None.
IED1441
station GENERAL POLL STOPPED
Explanation: An operator command was entered to deactivate
the general poll invitation characters associated with the
station named station.
System Action: The general poll invitation characters were
deactivated and all specific poll characters on the control unit
were activated.
Operator Response: None.
IED1451
station GENERAL POLL ALREADY STARTED
Explanation:. An operator command was entered to activate
the general poll invitation characters associated with the
7-16
VS2 System Messages (VS2 Release 3.7)
station named station.
System Action: The command was ignored because the
general poll invitation characters were active already;
processing continues.
Operator Response: None.
System Action: Processing continues.
Operator Response: Reply D to dump the entire message data
set, or C to cancel the dump. Notify system programmer of
action taken.
IED1511
IED1461
station GENERAL POLL ALREADY STOPPED
Explanation: An operator command was entered to deactivate
the general poll invitation characters associated with the
station named station.
System Action: The command was ignored because the
general poll invitation characters were inactive already;
processing continues.
Operator Response: None.
IED1471
station COMMAND INVALID FOR GENERAL POLL
Explanation: An operator command was entered to hold
(suspend transmission) or release (release intercepted station)
the general poll station named station.
System Action: The command was ignored because it is not a
valid command for general poll stations; processing continues.
Operator Response: None.
IED148D
IS C.U. FOR DEVICE ddd CONNECTED ONLY TO
THIS SYSTEM?
Explanation: The configuration data indicates this control unit
(C.U.) is either switchable or shared between two central
processing units. This message is trying to determine if the
control unit is connected to this system exclusively. If
switched, it must be switched to the central processor. If
shared, the sharing processor must not use the test device
during the on-line test (OLT).
System Action: Processing continues.
Operator Response: Reply YES if the C.U. is, or can be,
connected to this system and the device is not being used by
another control unit processor; if neither condition is met,
reply NO.
IED1491
TOTE BUSY
Explanation: All storage available to the telecommunications
on-line test executive (TOTE) for running on-line tests is
currently in use. The Test Request Message (TRM) that was
entered cannot be processed and is rejected. This message is
issued to the terminal entering the TRM except when the
requesting terminal is:
1. A concentrator or a terminal attached to a concentrator, or
2. A 3270 terminal when general poll is active.
3. A terminal in TSO session.
When either of these exceptions occurs, the message is issued
to the system console.
System Action: The TRM is rejected and processing continues.
Operator Response: Either wait until a later time and try to
enter the TRM again, or at the next TCAM startup increase the
size of the OLTEST parameter (0 = n) to increase the amount
of storage reserved for TOTE.
Problem Determination: Table I, items 1, 10, 11, 29.
IED150D
TCAM REUSABLE Q WRAPPED - REPLY 'D' TO
DUMP ENTIRE MSG DATA SET OR 'C' TO CANCEL
Explanation: This message is not supplied at the time the
reusable queue wraps. Rather, it is supplied when the IEDQXC
utility is used to format and print data from a reusable DASD
message queues data set that wrapped previously. Individual
queues cannot be dumped since the first record number of an
individual queue cannot be determined. The entire message
data set must be dumped.
cuu tttt yy ERS z
cuu xx tttt THRESHLD
cuu xx tttt yy eeee zzzz yy eeee zzzz yy
eeee zzzz yy eeee zzzz
cuu ww tttt eeeeeee zzzz eeeeeee zzzz
eeeeeee zzzz eeeeeee zzzz
Explanation: This message provides the results of a scan of
the error file of an IBM 2715 Transmission Control Unit. The
scan occurs when the error threshold for one of the area
stations connected to the 2715 is exceeded (threshold value is
eight) or when manually requested at the 2715 or at the 2740
terminal attached to the 2715. TCAM prints the message on
the master console, the teleprocessing console, or the system
maintenance console, depending on the routing code specified
at the 2715. In all four formats of the message text, cuu is the
address in EBCDIC of the communications line (channel and
unit), xx is the address in hexadecimal of the area station for
which the error scan is reported, tttt is the time (0001-2400)
when the error occurred, and ww is the address in hexadecimal
of a particular adapter within the 2715. Fields appearing
uniquely within a message format are described below.
The first format of the message is issued when five or more of
the eight errors involved a particular one of the devices
attached to the area station. In the message text, yy is the
address in hexadecimal of the device for which the errors
occurred, and z is the number of errors (from decimal 5 to 8)
that occurred for the device.
The second format of the message indicates that the threshold
value of eight has been reached for the area station whose
address is xx, but that no one device attached to the station
accounted for as many as five of the errors.
The third format of the message is issued twice whenever an
error scan for a particular area station is manually requested
at the 2715 or at the 2740 terminal attached to the 2715. The
address of device yy for which the error data eeee was
recorded at time zzzz is given four times in each message; the
two messages together thus provide information about the
eight most recent error occurrences for area station xx.
The fourth format of the message is issued twice whenever an
error scan for a particular 2715 adapter is manually requested
at the 2715, the 2740 terminal attached to the 2715, or the
central system console. The error data eeeeeee for adapter
ww recorded at time zzzz is given four times in each message;
the two messages together thus provide information about the
eight most recent error occurrences for adapter ww.
System Action: Processing continues.
Operator Response: None.
IED1521
ddn-CHECKPOINT BLKSIZE TOO SMALL - nnn WAS
USED
Explanation: A checkpoint data set block size less than 300
bytes was specified for environment checkpoint records for a
checkpoint data set TCAM used the default value of 300 for
TCAM checkpoint data set.
System Action: Processing continues.
Programmer Response: Change the value of the BLKSIZE =
operand of the checkpoint PCB macro instruction. Specify a
value between 300 and 3520 inclusive, for TCAM.
Section 7: lED Messages - Telecommunications Access Method
7 -17
a
IEDl531
ddn-CHECKPOINT BLKSIZE TOO BIG - nnn WAS
USED
Explanation: A block size greater than 3520 bytes was
specified for environment checkpoint records for a checkpoint
data set; TCAM assigned a value of 3520.
System Action: Processing continues.
Programmer Response: Change the value of the BLKSIZE =
operand of the checkpoint DCB macro instruction. Specify a
value between 300 and 3520, inclusive, for TCAM checkpoint.
IEDl541
TOTE CANNOT RETURN DEVICE ddd TO ORIGINAL
STATUS
IED1591
REUS
1
~1~:;SI
hh.mm.ss
FULL
ENDS
Explanation: This message informs the operator when TeAM
reusability starts and completes compressing of the TCAM
reusable disk message queues.
• STARTS - Reusability has started compressing.
• QUITS - Reusability has completed compressing.
• FULL - TCAM temporarily will stop receiving messages after
the current message is processed.
• ENDS - TeAM resumes receiving messages.
System Action: Processing continues.
Operator Response: None.
Explanation: The telecommunications on-line test executive
(TOTE) remembers the status of a device (terminal or line)
from the point that testing of that .device began. When TOTE
completed testing device ddd, it could not return that device
to its original status. This message is normal for a control
terminal, alternate printer, or test device that is a dial station,
or a station using storage-only queuing, because the VARY
command to activate station to receive and transmit causes a
bad return code.
System Action: Processing continues.
Operator Response: Determine the status of device ddd
through operator control facilities. Since the device does not
have the same status as it had at the beginning of the test,
use TCAM operator control to return it to the desired status.
Problem Determination: Table I, items 1, 4, 10, 13, 29.
queue that was coded as secure.
System Action: The TeAM application program executor is
waiting for a reply from the system operator indicating whether
to open the queue or to abend the application program: error
code 043-6. Message IED0151 is issued if the program is
terminated.
Operator Response: Reply Y to open the queue and continue
processing; reply N to prevent opening the queue and abend
the application program.
IEDl551
IED1731
TCAM START REJECTED - TCAM MCP IS
UNAUTHORIZED.
IED169D
QNAME qname SECURE, CAN jjj OPEN, REPLY Y OR
N
Explanation: An application program is attempting to open a
ddd IS NOT A VTAM CONTROL UNIT OR RESOURCE
Explanation: A VTAM operator command was issued to a unit
other than a 3705 control unit or resource.
System Action: Command is rejected. Processing continues.
Operator Response: Ensure that the control unit or resource
associated with the command is valid in a VTAM environment.
Explanation: The TCAM message control program that was
started does 1) not reside on the installation-defined
authorized library or 2) the mime of the MCP message control
program is not in the Program Properties Table.
System Action: TCAM is terminated.
Operator Response: Notify the system programmer of this
message.
Programmer Response: 1) the TCAM MCP must be link edited
to the installation-defined authorized library, or 2) the TCAM
MCP must be renamed with one of the names in the Program
Properties Table.
Explanation: The action requested by a MODIFY command has
been completed for station identified by station.
System Action: Processing continues.
Operator Response: None.
IEDl561
IED20l1
station ON CONCENTRATOR - CANNOT BE VARIED
Explanation: A VARY command was received for starting or
stopping the station named station from accepting or entering,
but the station is attached to a concentrator.
System Action: The requested action is not taken. Processing
continues.
Operator Response: None.
IEDl571
TCAM SYSTEM DELAY ACTIVE - HALT COMMAND
REJECTED
Explanation: A TCAM HALT command for system closedown
was issued during a TCAM system delay.
System Action: The requested action is not taken. Processing
continues.
Operator Response: Reissue the TCAM HALT command after
the system delay expires.
IEDl581
DIAL Ina,nnn.. (up to 20 digits) .. nnn
Explanation: This message signals the operator that a
transmission is pending on line Ina.
System Action: Processing continues.
Operator Response: Dial the number indicated by nnn to
enable transmission.
7-18
VS2 System Messales (VS2 Release 3.7)
IED1931
BLOCK HANDLER SET ASSOCIATION MODIFIED FOR
station
cm COMMAND INVALID FOR VTAM
Explanation: An operator command that is invalid for a 3705
was issued specifying a 3705 address or ddname. cm is the
first ten bytes of the error command.
System Action: Command rejected. Processing continues.
Operator Response: None.
IED2111
ON-LINE TESTING ACTIVE
Explanation: This message indicates to the control terminal
that a test request message has been received. Initial setup
for handling the TRM has started.
System Action: Processing continues.
Operator Response: None.
IED2121
CLASS NOT TP, OR SUPPORTED GRAPHIC - ABORT
Explanation: The specified test device is not a teleprocessing
device or a TCAM-supported graphic device. The test is
rejected for that device.
System Action: The test request message is canceled.
Operator Response: Reenter TRM for valid graphic or TP
device.
Problem Determination: Table I, items 1, 4, 10, 11, 29.
IED213D
CAN ON-liNE TEST USE PROTECTED DEVICE ddd
IED2191
Explanation: The configuration data set for the control terminal
or the alternate printer indicates that the terminal is a
protected device. Authorization for use of the terminal must be
obtained from the system operator before test can be done.
System Action: Processing continues. TOTE waits for the
operator to respond.
Operator Response: Reply YES if device can be used by TOTE;
or, reply NO to cancel the test request message.
Note: Proper reply format described in IED3351 explanation.
IED2141
OlT SUB MODULE mod NOT FOUND IN LIBRARY
Explanation: An on-line test (OlT) requested TOTE to load
module mod. The module was not found in any of the libraries
specified by TCAM JCL.
System Action: Processing continues.
Operator Response: Put module mod in the appropriate library
and reenter the test request message.
IED2151
OlT REQUEST REJECTED, UNABLE TO AllOCATE
RESOURCES CT / AP
Explanation: This message is issued for one of the following
reasons:
• There are not enough dummy terminal entries specified for
TOTE on the n ABLE macro.
• The queue control block (QCB) for the terminal is marked
as being in the delay queue.
• The terminal is a concentrator. A concentrator cannot be
specified as a control terminal (CT) or as an alternate
printer (AP).
• For a terminal attached to a concentrator, the symbolic
name of the concentrator could not be found in the
Terminal Name table.
System Action: The test request message is canceled.
Processing continues.
Programmer Response: Do one of the following:
1. Increase the OLTERM = operand of the
ABLE macro in
the MCP to allocate enough dummy terminal entries.
2. If the queue control block for the terminal indicates that the
terminal is in the delay queue, reenter the test request
message specifying a different terminal as either the control
terminal or the alternate printer.
3. Verify that the terminal is not a concentrator. If it is one,
reenter the test request message specifying a different
terminal or the alternate printer.
4. If the symbolic name of the concentrator is not in the
Terminal Name table, reassemble the MCP and include the
name.
n
IED2161
TRM CANCELED - TOTE CANNOT USE TSO DEVICE
ON-LINE TESTING ENDED
Explanation: The on-line test function has been completed.
System Action: Normal processing continues.
Operator Response: None.
IED2201
ERROR - MORE THAN 10 TEST DEVICES ENTERED
Explanation: This message is issued when more than 10 test
devices are specified in a TRM. Ten is the maximum number of
devices that may be entered in the test device field.
System Action: The operator is prompted for the remainder of
the Test Request Message (TRM) beginning with the test
device field.
Operator Response: Wait to be prompted for the remainder of
the TRM.
IED2211
TRM CANCEllED - STOP FAilED FOR DEVICE ddd
Explanation: TOTE issued an operator control command to
stop the named device and a bad return code was received. If
the device is a:
1. Terminal - V ddd,OFFTP,B has failed.
2. Subchannel address - V ddd,OFFTP,C for a 2701/02/03
has failed.
The on-line test is terminated because TOTE cannot have
exclusive use of the named resource.
System Action: The test request message (TRM) is canceled.
Normal processing continues.
Operator Response: None.
Problem Determination: Table I, items 1, 4, 10, 29.
IED2231
ON-LINE TESTING CANCELED
Explanation: The On-line Test has been canceled for one of
the following reasons:
• Alternate printer not open.
• Resource in unshared state.
• I/O error in loading configuration data.
• No configuration data.
• Control unit not connected to proper CPU.
• No line available for switched terminal test.
• Start/stop line failed.
• Test device does not belong to TCAM.
• A cancel request TRM.
• TCAM clo~edown.
• Configuration data sets cannot be opened.
• DIAGMSG open failed.
• Device protected.
System Action: The test reqeust message is terminated.
Processing continues.
Operator Response: None.
Problem Determination: Table I, items 1, 4, 10, 29.
I
Explanation: This message occurs for any of the following
IED224D
conditions:
• A remote terminal is specified either as control terminal or
as alternate printer in a TSO-only environment.
• A remote terminal is specified either as control terminal or
as alternate printer in a mixed environment when the
terminal is still logged on to TSO.
• A remote terminal is specified as a test device in either a
TSO-only or a mixed environment when the terminal is still
logged on to TSO.
System Action: The test request message is canceled.
Processing continues.
Operator Response: Perform the terminal LOGOFF procedure.
For a TSO-only environment, specify the system console
(SYSCON) as control terminal, and either SYSCON or SYSOUT
as alternate printer.
Explanation: This message is issued when exclusive use of
subchannel addresses ddd, ... ,ddd is needed for testing; ddd
are physical addresses of the 2701, 2702, 2703, 3270, or
7770 being tested.
System Action: Processing continues. TOTE enters a wait state
for three minutes. If a reply is not received within three
minutes, the on-line test is canceled.
Operator Response: Reply r xx, 'YES' if all activity on the
indicated subchannel addresses can be suspended for the
duration of the test; otherwise, reply r xx, 'NO'.
CAN OlT HAVE EXCLUSIVE USE OF CONTROL
UNIT(S) ON ADDRESS(ES) ddd, (up to 10
addresses), ddd
Section 7: lED Messages - Telecommunications Access Method
7-19
IED2251
INVALID TEST DEVICE ENTRY - TEST LINE NOT
OPENED
Explanation: The entry in the Test Device field is on a line that
has not been opened. Lines used in a test must be opened by
the Message Control Program.
System Action: The test request message is canceled.
Processing continues.
Operator Response: Correct the run to ensure the MCP opens
the line the test device is on and reenter the test request
message.
Problem Determination: Table I, items 1, 4, 10, 29.
IED2261
TRM REJECTED - TCU NOT CONNECTED TO
PROPER CPU
Explanation: The Transmission Control Unit (2701/02/03) is
either switchable between two CPUs or shared; the operator
could neither connect the TCU to the proper CPU (if
switchable) lior guarantee exclusive use of the TCU (if shared).
System Action: The test request message is canceled.
Processing continues.
Operator Response: Rerun the test request message when the
TCU is available. '
IED2271
CHAN ADDR(S) SPECIFIED IN TRM ARE MIXED
2701,2,3 WITH 3705
Explanation: A Test Request Message (TRM) was entered that
specified both 3705 and 2701, 02, or 03 in the test device
field. Because of test differences for 3705s and for
2701/02/03s, the mix is invalid for transmission control unit
testing.
System Action: The test request message is canceled.
Processing continues.
Operator Response: None.
IED2281
TRM REJECTED - I/O ERROR LOADING
CONFIGURATION DATA
Explanation: Permanent input! output error found during
directory search.
System Action: The test request message (TRM) is canceled.
Processing continues.
_Operator Response: Use the configuration facility to
reconfigure the device in question.
Problem Determination: Table I, items 1, 4, 10, 26c, 29.
IED2291
TRM REJECTED - NO CONFIGURATION DATA
Explanation: No configuration data was found for the test
device.
System Action: The test request message (TRM) is canceled.
Processing continues.
Operator Response: Configure test device and reenter TRM.
Problem Determination: Table I, items 1, 4, 26a, 29.
IED2311
Explanation: The resource (for example line, terminal, display)
requested as a test device in this test request message (TRM)
is being used by a TRM currently being processed.
System Action: TRM is canceled. Processing continues.
Operator Response: Rerun TRM when resource becomes
available.
Problem Determination: Table I, items 1, 4, 10, 11, 29.
IED2321
TRM REJECTED - CONFIGURATION DATA SET
CANNOT ~E OPENED
Explanation: One or both of the configuration data sets
required by TOTE could not be opened.
Sample JCL:
DO DSN = SYS1.0LT2L1B,DISP = OLD
/ /OLTLIB
//
VOL = SER = xxxxxx,UNIT = 23xx
/ /CDSLIB DO DSN = SYS1.CDSLlB,DISP = OLD
//
VOL = SER = xxxxxx,UNIT = 23xx
System Action: The test request message (TRM) is canceled.
Processing continues.
Operator Response: Correct the JCL describing SYS1.0LT2L1B
and/or SYS1.CDSLlB; reenter the test request message.
Problem Determination: Table I, items 1, 4, 10, 25a, 29.
7-20
VS2 System Messages (VS2 Release 3.7)
INVALID ALTERNATE PRINTER ENTRY
Explanation: An invalid name has been entered in the option
field for the alternate printer.
System Action: The operator is prompted to reenter the
alternate printer location.
Operator Response: Reenter the alternate printer name
specifying a valid TCAM terminal name.
Problem Determination: Table I, items 1, 3, 4, 10, 13, 29.
IE0233D
INVALID EP LEVEL - ENTER 0, 1, 2" OR 3
Explanation: During a prompt request, an invalid error print
(EP) level was entered. Valid levels are 0, 1, 2, and 3.
System Action: Processing continues.
Operator Response: Enter desired level of error print. Valid
levels are 0, 1, 2, and 3.
Note: Proper reply format described in IED3351 explanation.
Problem Determination: Table I, items 1, 4, 11, 29.
IE02340
ENTER DIFFERENT TERMINAL, SYSOUT, SYSCON OR
NAP
Explanation: The alternate printer entered in the option field of
the TRM is in use as a test device by another OLT. This is a
request to the operator to enter the option again.
System Action: Processing continues.
Operator Response: Specify a terminal not in use by another
OLT request, or specify the system console or system output
device, as the alternate printer. The alternate printer option
can be canceled by entering NAP.
Note: Proper reply format described in IED3351 explanation.
IE02360
DIAGMSG OPEN FAILED
Explanation: A test request message specifying the option
APSYSOUT has been entered to cause the output to go to the
alternate printer (AP) SYSOUT. However the OPEN for the
SYSOUT device (DDNAME = DIAGMSG) failed.
System Action: The test request message is canceled and
processing continues.
Operator Response: Correct the run so the OPEN for DIAGMSG
will not fail and reenter the test request message.
Problem Determination: Table I, items 1, 4, 10, 11, 29.
IED2371
IED2301
REENTER TRM LATER - RESOURCE IN
UNSHAREABLE STATE
OPERATOR WILL ONLY ALLOW CONCURRENT
MODE - TRM REJECTED
Explanation: For a line test or when non-concurrent mode
(NCM) is specified in an option field of a test request message
(TRM), the operator will only allow concurrent mode (CM)
operation.
System Action: The test request message is rejected and
processing continues.
Operator Response: None.
IE02381
DO CARD MISSING FOR LINE ENTRY IN TEST
DEVICE FIELD
Operator Response: Enter C to cancel TRM; R to restart
prompting or GO to use truncated TRM.
Explanation: The DO card for the line entry being tested was
Note: Proper reply format is described in the explanation of
omitted from the TCAM JCL.
System Action: The operator at the control terminal is
prompted for the remainder of the test request message
beginning with the Test Device field.
Operator Response: Read the TCAM JCL in again and include
DO cards for all line entries to be included in the Test Device
field.
Problem Determination: Table I, items 1, 3, 4, 13, 29.
message IED3351.
IE02391
Problem Determination: Table I, items 1, 4, 10, 13, 29.
IE02451
the test request message.
System Action: Processing continues.
Operator Response: None. TOTE will ask if you wish to
continue prompting.
Problem Determination: Table I, items 1, 4, 10, 13, 29.
xxxxxxxx - ROUTINE BYPASSED - CONTROL AND
TEST TERMINALS ON SAME LINE
Explanation: The operator has entered a test request message
with the control and test terminal on the same line. The
current routine of test section xxxxxxxx does not allow the two
terminals to be on the same line. The routine is bypassed.
System Action: - Processing continues.
Operator Response: To ensure that all routines will be run,
specify the system console or a terminal on a different line
than the test terminal as the control terminal.
IE02461
TERMINAL xxxxxxxx CANNOT BE SWITCHED TO
PRIMARY
BACKUP
of the test request message.
System Action: Processing continues.
Operator Response: None. TOTE will ask if you wish to
continue prompting.
Problem Determination: Table I, items 1, 4, 10, 13, 29.
IE02471
Explanation: A Test Request Message (TRM) requesting that
IE02471
terminal xxxxxxxx be tested in either backup or primary mode
was entered. The teleprocessing on-line test executive (TOTE)
could not perform the switch.
System Action: The TRM is canceled and processing
continues.
Operator Response: If the TRM request was for a test in
backup mode, make sure the terminal is switchable. Correct
the TRM and reenter.
IE02411
IE02410
IE02471
IE02470
ENTER ALTERNATE PRINTER LOCATION. VALID
ENTRIES ARE
SYSOUT - SYSCON - SYMBOLIC TERMINAL NAME
Explanation: For a prompt request these are valid alternate
printer entries: SYSOUT, SYSCON or a symbolic name of the
terminal.
System Action: Processing continues.
Operator Response: Enter the name of the device you wish to
be used as the alternate printer.
Problem- Determination: Table I, items 1, 4, 10, 13, 29.
IE02420
DO YOU WANT TO CONTINUE PROMPTING? YES OR
NO
Explanation: During a prompt operation an invalid reply was
detected. The operator has the choice of continuing or
terminating the prompt run.
System Action: Processing continues.
Operator Response: Reply NO to cancel the test request
message. Reply YES to initiate a repeat of the message which
was responded to incorrectly.
Note: Proper reply format is described in the explanation of
message IED3351.
IE02431
IE02431
IE02430
TRM BUFFER TOO SMALL· FOR LAST ENTRY
MAKE ENTRY FROM APPROPRIATE PARENTHESES
YOU CAN REENTER(R), CANCEL(C) OR USE TRM AS
IS (GO)
Explanation: .During a prompting operation the buffer was
found to be too small for the test request message (TRM).
System Action: Processing continues.
OPTION ENTRY INVALID
Explanation: An invalid option was entered in the option field
IE02471
IE02401
ERROR IN TEST LOOP OR ERROR LOOP NUMBER
Explanation: An invalid test or error loop count was entered in
VALID OPTIONS ARE
TLNNNN,NTL,ELNNNN,NEL,CP,NCP,
NMI,MI,NP,TPP,TAP,NBK,BK
CM, NCM, NEP, AP, NAP, TR, EXT = datal - NNNN
IS A 4-01GIT DECIMAL NUMBER
EPN-WHERE N IS LEVEL OF PRINTED OUTPUT
WANTED
DEFAULT OPTIONS ARE CP, NTL, NEL, CM, NAP,
NMI, EP, TPP AND BK
ENTER ONE OPTION OR NONE
Explanation: The operator is asked to enter one of the
available options or NONE (default options are underlined):
Option
Explanation
Testing Loop
TLn
Repeats specified test n
times, where n is a
decimal number between
1 and 9999. If n is
omitted, a default of 500
is assigned. It is
recommended that a
value always be assigned
to n when the TLn option
is selected.
No Testing Loop
NTL
Do not repeat test.
ELn
Error Loop
Loops n times on the set
of instructions detecting
the first error, where n is
a decimal number
between 1 and 9999. If
n is omitted, a default
value will be assigned by
the on-line test. It is
recommended that a
value always be aSSigned
to n when the ELn option
is selected.
No Error Loop
NEL
Do not loop on an error.
Control Print
CP
Prints control messages,
such as section start and
termination messages.
NCP
No Control Print
Do not print control
messages.
APterm
Alternate Printer
Sends error printouts to
the station, whose
symbolic name is term,
Section 7: lED Messages - Telecommunications Access Method
7-21
•
instead of the station
from which the test is
controlled.SYSCON or
SYSOUT are also valid
names for the alternate
printer.
No Alternate Printer
Send error printout to
control terminal.
Concurrent Mode
TOTE will allow
automatic subchannel
address sharing.
NCM
Non-Concurrent Mode TOTE will not allow
automatic subchannel
address sharing.
Error Print
Specifies level of error
EPn
print, where n is an
integer between 0 and 3.
Level 0 specifies the
minimum error print,
whereas level 3 specifies
the maximum error print.
If n is omitted, a default
value of 3 will be
assigned by TOTE.
Do not provide error
No Error Print
NEP
print.
NP
Do not print control
No Print
messages or error prints.
MI
Manual Intervention
Routines that require
manual intervention will
be executed. This option
is normally selected
when terminal tests are
run.
Routines that require
No Manual
manual intervention will
Intervention
not be exeucted.
TR
Traces macro calls made
Trace
by the on-line test.
Does not trace macro
No Trace
calls made by the
on-line test.
After line connection is
No Break
NBK
originally established, do
NOT break and
reestablish the
connection for each I/O
operation. Reestablish
the connection only if
broken by TOTE for user
communication
(2701/2/3 only).
Non-Concurrent Mode
(NCM) is set when this
option is specified.
Break and reestablish
Break
line connection for each
I/O call by the on-line
test (2701/2/3 only).
Allows data to be
EXT - datal External Data
entered into the on-line
text (must be last option
entered if used). The
slash delimits the test
data and the test
request message option
field.
System Action: Processing continues.
7-22
VS2 System Messages (VS2 Release 3.7)
Operator Response: Enter NONE to terminate prompting for
the option field. Enter any option listed under valid test
request message options that were specified in the
explanation.
Note: Proper reply format is described in the explanation of
message IED3351.
IED2481
INVALID ENTRY FOR ADDITIONAL TESTS - VALID
ENTRIES ARE A-Ill.
Explanation: An invalid test entry was entered.
System Action: Processing continues.
Operator Response: None.
Problem Determination: Table I, items 1, 4, 10, 11, 29.
IED2491
INVALID ROUTINE ENTRY
Explanation: An invalid routine number was entered in test
field.
System Action: Processing continues.
Operator Response: None.
Problem Determination: Table I, items 1, 4, 10, 11, 29.
IED2501
INVALID TEST NAME
Explanation: An invalid test name was entered in the test field.
System Action: Processing continues.
Operator Response: None.
Problem Determination: Table I, items 1, 4, 10, 11, 29.
IED251D
ENTER ALPHA CHARACTERS SEPARATED BY
COMMAS FOR OTHER SELECTIONS
Explanation: This message asks the operator to enter
additional test suffixes separated by commas.
System Action: Processing continues.
Operator Response: Enter the suffixes or other tests that are
to be run on the test device.
Note: Proper reply format is described in the explanation of
message IED3351.
IED252D
DO YOU WANT OTHER TEST SECTIONS RUN ON
THIS DEVICE? ANSWER YES OR NO
Explanation: The operator is asked if other sections are to be
run on test device.
System Action: Processing continues.
Operator Response: Enter YES if other test sections are to be
run. Enter NO if no other sections are to be run.
Note: Proper reply format is described in the explanation of
message IED3351.
IED253D
ENTER ROUTINE NUMBER(S) - EXAMPLE 1, 4-6, 9
Explanation: The operator is asked to enter routine numbers
to be run in the test section.
System Action: Processing continues.
Operator Response: Enter the routine numbers that are to be
run. Note that routine selection can be made when only one
test section is specified.
Note: Proper reply format is described in the explanation of
message IED3351.
IED254D
DO YOU WANT TO SELECT ROUTINES IN THIS
TEST? ANSWER YES OR NO
Explanation: The operator is asked if a routine is desired.
System Action: Processing continues.
Operator Response: If YES is entered, the operator will be
prompted for the routine numbers to be run. Routine selection
is not requested if NO is entered.
/1
'~
Proper reply format is described in the explanation of
message IED3351.
Note:
IED255D
Note: Proper reply format is described in the explanation of
message IED3351.
Problem Determination: Table I, items 1, 4, 10, 11, 29.
ENTER TEST TO BE RUN - FORMAT
NNNNB/ANNNNB -EXAMPLE 2700A/T2700A
IED264D
Explanation: The operator is asked to enter the 10 .of the test
section to be run.
Explanation: This message is issued to determine if there are
any more test device entries to be built in the test request
message.
System Action: Processing continues.
Operator Response: Enter YES if more test devices are to be
entered. Enter NO to terminate prompting for test devices.
Note: Proper reply format is described in the explanation of
message IED3351.
System Action: Processing continues.
Operator Response: Enter the name of the test to be run (use
either the NNNNB or the ANNNNB (format). If 'T' is the prefix
character for the test, the prefix may be omitted.
Note: Proper reply format is described in the explanation of
message IED3351.
IED256D
DO YOU WANT TO BE PROMPTED? ANSWER YES
OR NO
IED265D
Explanation: The operator is asked whether or not he wishes
to be prompted for the test request message.
System Action: Processing continues.
Operator Response: If YES is entered, the operator is
prompted for the test request message. If NO is entered,
prompting is terminated and the test request is canceled.
Note: Proper reply format is described in the explanation of
message IED3351.
IED2591
ENTER SYMBOLIC NAME OF TERMINAL OR CUU OF
TCU TO BE TESTED
Explanation: This message asks the operator to enter the test
device 10. Valid entries are line addresses (CUU) and symbolic
terminal names.
System Action: Processing continues.
Operator Response: Enter the line address (CUU) or the
symbolic name of terminal on which the test is to be run.
Note: Proper reply format is described in the explanation of
message IED3351.
INVALID RESPONSE
Explanation: An invalid response has been entered in response
to a prompter or configurator question.
System Action: Processing continues.
Operator Response: None.
Problem Determination: Table I, items 1, 4, 10, 11, 29.
IED2601
ARE THERE ANY MORE TEST DEVICES? ANSWER
YES OR NO
IED2661
CONTROL TERMINAL}
ALTERNATE PRINTER
{ TEST DEVICE
IS ATTACHED TO
3704/3705
NCP -- INVALID
Explanation: A TRM (Test Request Message), entered to
TCAM/TOTE, requested that a device attached to an IBM
3704,3705 NCP be assigned as the control terminal, alternate
printer, or test device. For TCAM level 8 TOTE, only terminals
attached to IBM 2701/02/03 control units are eligible.
System Action: The TRM is rejected. If this device was
selected during a prompting run, TOTE asks you to select
another device type. Normal processing continues.
Operator Response: To use and/or test devices attached to an
IBM 3704/3705 NCP, use VTAM/TOLTEP.
TEST DEVICE ALLOCATED TO VTAM -- INVALID
TOTE DEVICE
Explanation: A TRM (Test Request Message), entered to
TCAM/TOTE, requested a test on a local 3704, 3705, or
3270. The requested device is attached through VTAM and
cannot be tested by TCAM/TOTE.
System Action: The TRM is rejected. If this device was
selected during a prompting run, TOTE asks you to select
another device type. Normal processing continues.
Operator Response: Test this device using VTAM/TOLTEP.
IED2671
ERROR IN OPTION FIELD
Explanation: An invalid option is specified in the test request
IED2611
message.
INVALID TEST DEVICE ENTRY
System Action: Processing continues.
Operator Response: None. The user will be asked if he desires
Explanation: An invalid test device has been entered. Valid
test devices are line addresses (CUU)and symbolic names of
terminals.
System Action: Processing continues.
Operator Response: None.
Problem Determination: Table I, items 1, 4 10, 11, 29.
IED2621
to be prompted.
Problem Determination: Table items 1, 4, 10, 11, 29.
IED2681
ALREADY HAVE 10 TEST DEVICES - TEST DEVICE
PROMPTING FINISHED
Explanation: The maximum number of test devices that can be
specified in a test request message has been reached.
Prompting for more test devices is terminated.
System Action: Processing continues.
Operator Response: None.
IED263D
INVALID RESPONSE, PLEASE ENTER YES OR NO
Explanation: An invalid response was entered. The operator is
asked to reenter response.
System Action: Processing continues.
Operator Response: Enter YES or NO depending upon the
question that was previously asked.
ERROR IN TEST FIELD
Explanation: An invalid test section has been specified in the
test request message.
System Action: Processing continues.
Operator Response: None. The user will be asked if he desires
to be prompted.
Problem Determination: Table I, items 1, 4, 10, 11, 29.
IED2691
ERROR IN TEST DEVICE FIELD
Explanation: An invalid test device has been detected.
System Action: Processing continues.
Operator Response: None. The user will be asked if he desires
to be prompted.
Problem Determination: Table I, items 1, 4, 10, 11, 29.
Section 7: lED Messages - Telecommunications Access Method
7·23
•
IED2701
TRM PROMPTER RUNNING
Explanation: This message is issued to notify the operator that
the test reqeust message (TRM) will be prompted for.
System Action: Processing continues.
Operator Response: None.
IED2711
PROMPTING NOT ALLOWED ON 1060, REENTER
TRM
Explanation: A prompting request with a 1060 device as
control terminal has been specified. Prompting is not allowed
on a 1060 terminal.
System Action: Processing continues.
Operator Response: None.
Problem Determination: Table I, items 1, 3, 4, 10, 11, 29.
Operator Response: None.
Problem Determination: Table I, items 1, 3, 4, 10, 11, 29.
IED2781
TRM CANCELLED - - TEST DEVICE IS BEING
GENERAL POLLED
Explanation: One of the test devices named in the TRM is
being general polled.
System Action: The TRM is cancelled. Normal processing
continues.
Operator Response: Stop general poll on the devices to be
tested using operator control commands and re-enter the
TRM.
IED279D
ENTER NEXT MESSAGE SEGMENT
Explanation: The control terminal is a numeric-only device.
IED2721
TRM REJECTED - TEST IN BACK-UP MODE NOT
YET SUPPORTED
Explanation: A test request message (TRM) was entered that
specified the option test alternate path (TAP). The
teleprocessing on-line test executive (TOTE) does not
presently support this function.
System Action: The TRM is rejected. Processing continues.
Operator Response: Reenter the TRM and specify or default to
the test primary path (TPP) option.
The control terminal is prompted for building the next portion
of the test request message.
System Action: Processing continues.
Operator Response: Respond with 99999, 10, and the next
character of the test request message.
Note: See example in the OS/VS 'TCAM User's Guide',
GC30-2045.
IED2801
CONFIGURATOR STARTED
Explanation: This message is issued when a configuration
IED2731
ERROR - MORE THAN 256 TEST DEVICES ENTERED
Explanation: This message is issued when more than 256 test
devices are specified in a test request message (TRM) that
requests deallocation of TCAM devices. The maximum number
of devices that can be deallocated is 256.
System Action: The TRM is rejected. Processing continues.
Operator Response: Reenter the TRM and specify 256 or less
test devices.
IED2741
ERROR - TEST DEVICE NOT ALLOCATED TO TCAM
request message (CRM) is recognized and the
TOTE/Configurator is activated.
System ACtion: Processing continues.
Operator Response: None.
IED2811
CONFIGURATOR COMPLETED
Explanation: This message is issued when a configuration run
is either completed or terminated.
System Action: Processing continues.
Operator Response: None.
Explanation: This message is issued when a test device entry
. for a device not currently allocated to TCAM is detected in a
deallocation test request message (TRM).
System Action: The TRM is rejected. Processing continues.
Operator Response: Reenter the TRM and specify in the Test
Device Field only devices which are currently allocated to
TCAM.
IED275D
REPLY 'TOTE' TO RETURN TO TCAM SUBCHANNELS
nnn ...
Explanation: This message is issued:
a. After a deallocation test request message has been
processed; the telecommunications on-line test executive
(TOTE) has taken the devices indicated by nnn away from
TCAM (nnn represents the Test Device Field entered in the
deallocation TRM).
b. A response other than TOTE was entered in response to
this message.
c. The UCB resources which TOTE is attempting to return to
TCAM are still allocated to another job.
System Action: Processing continues.
Operator Response: When ready to return the devices to TCAM
reply TOTE.
IED2771
1060 CANNOT BE CONTROL TERMINAL FOR
PROMPT OR CON FIG
Explanation: The operator entered a req~est specifying a 1060
terminal as control terminal for a prompting or configuration
run. A 1060 terminal cannot be the control terminal for either.
System Action: Processing continues.
7-24
VS2 System Messages (VS2 Release 3.7)
IED282D
ENTER FUNCTION: ADD, CHANGE, DELETE, EXHIBIT,
OR NONE
Explanation: This message is issued to determine the type of
configuration run desired.
System Action: Processing continues.
Operator Response: To add a new configuration data set entry,
reply ADD or A; to replace an existing CDS entry, reply
CHANGE or C; to delete an existing CDS entry, reply DELETE
or 0; to exhibit an existing entry, reply EXHIBIT or E; to
eliminate processing, reply NONE or N.
Note: Proper reply format is described in the explanation of
message IED3351.
IED283D
ENTER A LINE ADDR. OR A SYMBOLIC TERMINAL
NAME
Explanation: This message is issued to determine if the
configuration is for a local device or a remote device.
System Action: Processing continues.
Operator Response: For local devices enter a 3-digit line
address, such as 01C. The first digit must always be numeric;
otherwise, it will be treated as a symbolic name. For remote
devices enter the symbolic name used by TCAM to identify the
device, such as NYC.
Note: Proper reply format is described in the explanation of
message IED3351.
IED2841
OLT ABEND cdexxx
Explanation: An on-line test (OLT) has abnormally terminaled
with a system completion ABEND code of cde and a user
\
}I
ABEND code of xxx. The test is canceled and all associated
cleanup is performed.
System Action: The on-line test is canceled. Processing
continues.
Operator Response: For a response of cdeOOO, refer to the
corresponding system completion code to determine the nature
of the failure. For a response of OOOxxx, notify your IBM CE of
the user ABEND code.
Problem Determination: Table I, items 1, 3, 4, 5a, 10, 13, 16,
29.
IED286D
ENTER TYPE OF TERMINAL
IED2961
IED296D
Explanation: This message is issued to determine the type of
terminal to be configured.
System Action: Processing continues.
Operator Response: Enter the type of terminal, such as 1050,
2740,2741.
Note: Proper reply format is described in the explanation of
message IED3351. Refer to message IED2911 and IED2921 for
supported devices.
IED287D
configuration run for a non-telecommunications device is
requested, or if a delete run is requested for a configuration
data set entry with device protection. The device class field in
the unit control block must be either X'10' or X'40' for·the
configuration data set entry to be modified or deleted. If the
device protection bit is on, the configuration data set can be
changed or deleted only from ~he system console.
System ACtion: Processing continues.
Operator Response: None.
Problem Determination: Table I, items 1, 3, 4, 10, 11, 13, 26c,
29.
LINE NOT OPENED
ENTER LINE ADDRESS (FORMAT CUU)
Explanation: The message is issued when the remote device
being configured is on a line that has not been opened by
TCAM.
System ACtion: Processing continues.
Operator RESPONSE: Enter a 3-digit line address; such as
01C. The first digit must always be numeric.
Note: Proper reply format is described in the explanation of
message IED3351.
ENTER ADAPTER LINE CODE: (EBCDIC,
TRANSCODE, ASCII)
Explanation: EBCDIC, TRANSCODE, and ASCII are the valid
adapter line codes for the device being configured. This
message is issued when the device being configured is not
open.
System Action: Processing continues.
Operator Response: Reply either EBCDIC, TRANSCODE, or
ASCII depending on the line adapter code for the device being
configured.
Note: Proper reply format is described in the explanation of
message IED3351.
IED2971
TEST DEVICE DOES NOT BELONG TO TCAM
Explanation: All test devices must be defined and opened in
the MCP.
System Action: The test request message is canceled.
Processing continues.
Operator Response: Specify a valid test device.
Problem Determination: 1, 3, 4, 10, 29.
IED298D
ARE THERE OTHER ENTRIES TO ADD? (YES OR NO)
Explanation: This message provides a complete list of
start/stop terminals supported by the TCAM/TOTE
Configurator.
System Action: Processing continues.
Operator Response: None.
Explanation: This message is issued to determine if there are
other device configurations to be added to the configuration
data set.
System Action: Processing continues. The configurator waits
for the operator to respond.
Operator Response: Reply YES if there are other additions;
otherwise, reply NO.
Note: Proper reply format is described in the explanation of
message IED3351.
IED2921
IED299D
IED2911
,v'
START STOP TERMINALS SUPPORTED: 1030, 1050,
1060, 2260, 2265, 2740, 2741, 2769
BI-SYNC TERMINALS SUPPORTED: 2770, 2780,
1130,2020,3270,3670, S360
Explanation: This is a complete list of Bi-sync terminals
supported by TCAM/TOTE Configurator.
System Action: Processing continues.
Operator RESPONSE: None.
IED2931
OLD ENTRY DELETED FROM CDS
Explanation: A CDS entry has been deleted from the CDS data
set. For CHANGE configuration runs, the old entry is not
deleted until the new entry has been successfully added.
System Action: Processing contiunues.
Operator Response: None.
IED2941
NEW ENTRY ADDED TO CDS
Explanation: The new or changed CDS (configuration data set)
entry has been successfully added to the CDS.
System ACtion: Processing continues.
Operator Response: None.
IED2951
MODIFICATION/DELETION NOT PERMITTED FOR
THIS DEVICE
ARE THERE OTHER ENTRIES TO CHANGE? (YES OR
NO)
Explanation: This message is issued to determine if there are
other device configurations to be changed in.the configuration
data set.
System Action: Processing continues. The configurator waits
for the operator to respond.
Operator Response: Reply YES if there are other changes;
otherwise, reply NO.
Note: Proper reply format is described in the explanation of
message IED3351.
IED300D
ARE THERE OTHER ENTRIES TO DELETE? (YES OR
NO)
Explanation: This message is to determine if there are other
configuration data set entries to be deleted.
System Action: Processing continues. The configurator waits
for the operator to respond.
Operator Response: Reply YES if there are other entries to be
deleted; otherwise, reply NO.
Note: Proper reply format is described in the explanation of
message IED3351.
Explanation: This message is issued when a change or delete
Section 7: lED Messages - Telecommunications Access Method, 7-25
•
•
IE03010
ARE THERE OTHER ENTRIES TO EXHIBIT? (YES OR
NO)
Explanation: This message is issued to determine if there are
other device configurations to be exhibited.
System Action: Processing continues. The configurator waits
for the operator to respond.
Operator Response: Reply YES if there are other entries to be
exhibited; otherwise, reply NO.
Note: Proper reply format is described in the explanation of
message IED3351.
allowed since a concentrator cannot be a test device. Only
terminals attached to the concentrator can be configured and
tested.
System Action: Processirig continues.
Operator Response: Enter the symbolic name of a terminal
attached to a concentrator rather than the symbolic name of
the concentrator.
IE03101
NAME NOT FOUND IN TCAM TERMINAL TABLE
Explanation: This message is issued when the symbolic name
Explanation: This message number precedes every line of a
graphic, terminal, or TCU configuration data exhibit when
running the EXHIBIT function of the TOTE configurator. The bit
settings and field descriptions are described in Configuration
Data Set Guide, 099-CDSG.
System Action: Processing continues.
Operator Response: None.
for the remote device being configured is not defined in TCAM
or the remote device is attached through VTAM.
System Action: Processing continues.
Operator Response: Before a remote device can be configured,
it must be defined in TCAM. For VT AM terminals, use TOlTED
to configure the remote device. Contact the system
programmer for the correct or new symbolic name and enter
th.e name.
Problem Determination: Table I, items 1, 4, 10, 29.
IE03030
IE03111
IE03021
(configuration data exhibited)
DO YOU WISH TO CONTINUE? (YES OR NO)
Explanation: This message is issued after some error
messages to determine whether to continue the configuration
run.
System Action: Processing continues.
Operator Response: Reply YES to continue with the
configuration run; otherwise, reply NO.
Note: Proper reply format is described in the explanation of
message IED3351.
IE03041
INVALID TEST DEVICE - TOTE DOES NOT SUPPORT
THE lOCAL 3270
Explanation: A test request message (TRM) has been entered
specifying a 3270 local attached to TCAM as the test device.
A 3270 local can only be tested by OlTEP since the test
requires separate channel end/device end handling.
System Action: The TRM is canceled. Processing continues.
Operator Response: To test a local 3270 attached to TCAM,
use the deallocation TRM explained in the OS/VS TCAM User's
Guide - GC30-2045.
IE03061
UNCORRECTABlE INPUT/OUTPUT ERROR
Explanation: This message is issued when the SYNAD exit
(error analysis routine) associated with the data control block
for the local or remote configuration data set is entered
because an uncorrectable input or output error is detected
after execution of a READ or WRITE macro instruction.
System Action: The configurator is terminated. Processing
continues.
Operator Response: None.
Problem Determination: Table I, items, 1, 3, 4, 13, 29.
IE03071
UNABLE TO OPEN CDS DATA SET
Explanation: The ,open for the local configuration data set
OlTLiB or the remote configuration data set (CDSLlB) was
unsuccessful.
System Action: Processing continues.
Operator Response: Verify that the JCL for the job includes a
DO card for both CDSLIB and OlTLIB.
Problem Determination: Table I, items 1, 3, 4, 29.
IE03081
CONCENTRATOR CANNOT BE CONFIGURED
Explanation: A configuration request was entered for a
symbolic name of a concentrator. A configuration is not
7-26
VS2 System Messages (VS2 Release 3.7)
CDS DATA SET IN UNSHAREABlE STATE REENTER TRM lATER
Explanation: A configuration run consists of manipulating
members of a partitioned data set (either CDSLIB or OlTLlB).
In order to ensure the integrity of these data sets, exclusive
use of them is required during a configuration run. Therefore,
the test request message (TRM) is rejected if a TRM is
entered while a configuration run is in process or a
configuration request (CRM) is entered during execution of an
on-line test .
. System Action: Processing continues.
Operator Response: Wait until the current configuration run or
on-line test has completed and reenter the TRM or CRM.
IE03121
PERMANENT I/O ERROR - CDS ENTRY MAY HAVE
BEEN DELETED
Explanation: A STOW macro instruction was issued to delete
the named device and a non-zero return code was returned.
The named device may not have been deleted due to an I/O
error.
System Action: Processing continues.
Operator Response: Verify that the named device has been
deleted by trying to run an EXHIBIT function. If the device is
still in the data set, the configuration data set (CDS) will be
exhibited. Run the delete operation again.
Problem Determination: Table I, items 1, 3, 4, 13, 29.
IE03131
UNCORRECTABlE ERROR ATTEMPTING TO ADD
NEW ENTRY
Explanation: A return code of X'10' was returned from the
STOW macro indicating that a permanent input or output error
was detected when attempting to update the directory.
System Action: The new entry was not added to the data set.
Processing continues.
Operator Response: Enter the ADD function again. If the 'error
persists, scratch and reallocate the data set.
Problem Determination: Table I, items 1, 3, 4, 13, 29.
IE03141
OUT OF SPACE TO ADD NEW ENTRY
Explanation: A return code of X'OC' was returned from the
STOW macro indicating that there is no space left in the
directory of either the local or remote configuration data set.
The entry could not be added.
System Action: Processing continues.
Operator Response: Increase directory block allocation for the
data set.
Problem Determination: Table I, items 1, 3, 4, 13, 25a, 29.
IED3151
ENTRY TO DELETE NOT FOUND
graphic device as indicated by the class byte of the
configuration data set. Only devices of class type 10, 40, 42
and 44 can be displayed.
System Action: Processing continues.
Operator Response: Specify a device that is a terminal, a line,
or a graphic device.
Problem Determination: Table I, items 1, 3, 4, 13, 26c, 29.
\
Explanation: The device named to be deleted or changed was
not found in the directory of the remote or local configuration
data set.
System Action: Processing continues.
Operator Response: None.
Problem Determination: Table I, items 1, 3, 4, 13, 26a, 29.
IED3161
IED3241
IS THE DEVICE TO BE CONFIGURED A 37041 REPLY
YES OR NO
Explanation: A control unit address (CUU) was entered for a
configuration run. It cannot be determined from the unit
control block (UCB) whether the device is a 3704 or a 3705.
System Action: Processing continues. TOTE waits for the
operator to reply.
Operator Response: Reply 'YES' if the device to be configured
is a 3704. Reply 'NO' if the device to be configured is a 3705.
See the explanation of message IED3351 for the proper reply.
ALREADY CONFIGURED: REQUEST CHANGE
FUNCTION TO MODIFY
'
Explanation: The device for which the ADD configuration
request was entered is already configured.
System Action: Processing continues.
Operator Response: The existing device configuration should
be exhibited. If not correct, it can be changed by entering a
CHANGE configuration request.
Problem Determination: Table I, items, 1, 4, 10, 13, 26a, 29.
IED3251
NO UNIT CON FIG MODULE FOR THIS DEVICE
Explanation: A BLDL macro was issued for the unit
System Action: Processing continues.
Operator Response: Determine the correct line address for the
configurator requested, and the module named was not found
in OLTUB.
System Action: Processing continues.
Operator Response: Obtain a partitioned data set (PDS) list of
OLTLIB and call your local program support representative.
Problem Determination: Table I, items 1, 3, 4, 13, 26a, 29.
device and perform the configuration run again.
Problem Determination: Table I, items 1, 3, 4, 10, 11, 13, 29.
IED3261
IED3191
INVALID LINE ADDRESS
Explanation: The line address entered does not exist in the
unit control block (UCB).
IED3201
Explanation: The BLDL macro return code indicates an I/O
error occurred in searching the directory for a unit
configurator.
System Action: Processing continues.
Operator Response: Reenter the ADD request.
INVALID TERMINAL TYPE
Explanation: A configuration run has been requested for an
unsupported terminal type.
System Action: Processing continues.
Operator Response: Refer to message IED2911 for valid
start/stop terminal types and message IED2921 for valid
Bi-sync terminal types.
Problem Determination: Table I, items 1, 3, 4, 13, 29.
IED3211
IED3271
UNSUPPORTED DEVICE TYPE
DEVICE NOT CONFIGURED
Explanation: This message is issued when a bad return code is
returned by the BLDL macro. The device named was not found
in either OLTUB (local configuration data set) or CDSLIB
(remote configuration data set).
System Action: Processing continues.
Operator Response: Verify that the device named is a valid
CUU for the system or a valid symbolic terminal name in the
TCAM term name table. If the name is valid, the device has
not been configured. Run the ADD function for the device.
Problem Determination: Table I, items 1, 3, 4, 13, 26a, 29.
IED3231
EXHIBIT OF THIS DEVICE CONFIGURATION NOT
PERMITTED
Explanation: The device named is not a terminal, line, or
UNABLE TO LOAD UNIT CON FIG MODULE
Explanation: The configurator ADD schedule cannot load the
Explanation: This message is issued when the configuration
request is for a device not defined in the unit control block as
communications (X'40') or graphics (X'10').
System Action: Processing continues.
Operator Response: Only telecommunications devices can be
configured by TOTE; that is, the device must be defined in the
unit control block as communications (X'40') or graphics
(X'lO').
Problem Determination: Table I, items 1, 3, 4, 10, 11, 29.
IED3221
I/O ERROR: UNABLE TO CONFIGURE THIS DEVICE
TYPE
unit configurator module because of a lack of main storage
assigned to TOTE.
System Action: Processing continues.
Operator Response: None.
Problem Determination: Table I, items 1, 4, 10, 13, 26a, 29.
IED328D
CAN PROTECTED DEVICE ddd BE TESTED
Explanation: Device ddd has been defined to TOTE as a
'protected' device and needs the system operator's approval
to be tested.
System Action: Processing continues according to the
operator's response. If the response is Reply xx, 'YES' the test
is continued. If the' response is Reply xx,'NO' the test request
message is canceled.
Operator Response: A response of Reply xx, 'YES' will allow the
on-line test to test device ddd. A response of Reply xx,'NO'
will cancel the test request message.
Note: Proper reply format is described in the explanation of
message IED3351.
IED3291
SYSTEM OPERATOR WILL NOT ALLOW TEST ON
PROTECTED DEVICE ddd
Explanation: The system operator replied 'NO' to message
IED328D.
System ACtion: The test request message is canceled.
Processing continues.
Operator Response: None.
Problem Determination: Table I, items 1, 4, 10, 13, 29.
Section 7: lED Messages - Telecommunications Access Method
7-27
•
IED3301
OLT MODULE mod CANNOT BE LOADED
Explanation: The OlT (on-line test) specified by mod is not in
the OlT library. The specified OlT section is not executed.
System Action: Processing continues.
Operator Response: Check that the specific OlT name is valid
and rerun OlT.
Problem Determination: Table I, items 1, 4, 13, 26a, 29.
IED3311
..
have a test request key or on-line test key to facilitate
entering the required header.
The above replies assume that the following message was
printed at the start of the test:
IED3351
*** CONTROL TERMINAL ID IS 04 ***
System Action: Processing continues.
Operator Response: None .
NOT ENOUGH COR!' FOR SECTION xxxxxxxx
Explanation: The on-line test specified by xxxxxxxx is too large
to run in the main storage assigned to TOTE. The test
specified is not executed.
System Action: Processing continues.
Operator Response: At INTRO execution, specify a larger value
for OlTEST = operand.
Problem Determination: Table I, items 1, 4, 13, 26c, 29.
IED3361
IED3321
IED3371
xxxxxxxx NOT OPENED
MACRO FUNCTION NOT SUPPORTED
Explanation: A macro function specified in a request to TOTE
is not supported.
System Action: Processing continues.
Operator Response: Cancel the test request message. The
results of the on-line test being run may be inaccurate.
Problem Determination: Table I, items 1, 4, 10, 13, 29.
MACRO LEVEL NOT SUPPORTED
Explanation: • The test device is a terminal. The line has not
Explanation: A macro has been issued by an on-line test. The
been opened by TCAM.
System Action: The test request message is canceled.
Processing continues.
Operator Response: Verify that a DO card is included for the
line that the test terminal is on.
Problem Determination: Table I, items 1, 4, 10, 11, 29.
macro is not supported by TOTE.
System Action: Processing continues.
Operator Response: Cancel the test request message. The
results of the on-line test being run may be inaccurate. Verify
that correct level of on-line tests is being run.
Problem Determination: Table I, items 1, 4, 10, 13, 29.
IED3331
IED3421
S xxxxy UNIT ddd
Explanation: Section y of test xxxx for unit ddd has started.
This is the SECTION START message requested by the control
print option in the test request message.
System Action: Processing continues.
Operator Response: None.
IED3341
S*T xxxxy UNIT dddt
UNIT ddd ~
IT xxxxy
Explanation: Section y of test xxxx for unit ddd has
terminated. This is the SECTION TERMINATE message. The
first form of the message indicates that errors were detected.
The second form indicates that no errors were detected.
System Action: Processing continues.
Operator Response: None.
IED3351
*1l11li xxxxxx CONTROL TERMINAL ID IS nn *1l11li
OPEN FOR TEST DEVICE(S) FAILED - TRM
REJECTED
Explanation: Possibly a DO card is missing for the test or wrap
device.
System Response: The test request message (TRM) is
rejected. Processing continues.
Operator Response: Add a DO card to the TCAM JCl and
reenter the test request message.
Problem Determination: Table I, items 1, 4, 13, 29.
IED3431
ALTERNATE PRINTER LINE NOT OPENED
Explanation: The line on which the alternate printer is located
has not been opened by the TCAM message control program.
System Action: The alternate printer site will be prompted for.
Operator Resporrse: Reenter a valid opened terminal for the
alternate printer.
Problem Determination: Table I, items 1, 3, 4, 10, 13, 29.
Explanation: This message notifies the control terminal of the
internal identification digits (nn) assigned to this on-line test.
The identifying number must be included in every reply to
TOTE from a remote device. It must not be included in replies
entered from the system console. xxxxxx is the address of the
on-line control TEST block.
Example:
If the message IE02551 ENTER TEST TO BE RUN - FORMAT
NNNNB/ ANNNNB EXAMPLE 2700A/T2700A appears, then the
proper response would be one of the following depending on
the type of the control terminal.
Response
Terminal Type
9999904T2700A
Start stop or local 22xx
device
S
O%/04T2700A
H
r xx,
I
T2700A I
Binary Synchronous or
local 32xx device
System console
Note: SOH is the start-of-header control character. For
bi-sync terminals, consult the related hardware manual for the
correct method of entering the reply. Many bi-sync devices
7-28
VS2 System Messages (VS2 Release 3.7)
IED3441
(printout of test request message)
Explanation: The complete test request message is printed
either after prompting is completed or after a numeric test
request message has been entered.
System Response: Processing continues.
Operator Response: None.
IED3451
TRM REJECTED - OLT CAN NOT USE PROTECTED
DEVICE term
Explanation: The system operator has rejected a request by
TOTE to use the terminal term as a control terminal or an
alternate printer. The configuration data set for the terminal
indicates that the terminal is a protected device.
System Action: The test request message (TRM) is canceled.
Processing continues.
Operator Response: To run the TRM, enter as the control
terminal or alternate printer (whichever applies) a terminal that
is not device-protected. If the rejected terminal is still desired
as the control terminal or alternate printer, reply positively to
the authorization request message IE02131.
Problem Determination: Table I, items 1, 3, 4, 10, 13, 29.
IED3461
xxxxxxxx - MI ROUTINE BYPASSED - MI NOT
SPECIFIED
System Action: Processing continues.
Operator Action: None.
Explanation: In the test xxxxxxxx specified in the test request
message, the operator did not specify the MI option. Only
routines that require no manual intervention are run.
System Action: Processing continues.
Operator Response: To ensure that all MI routines are
executed, include the MI option in the OPTION field of the test
request message.
Problem Determination: Table I, items 1, 3, 4, 10, 13, 29.
IED3831
ddd SWITCHED TO
command to switch VTAM devices for a VTAM terminal named
ddd. It indicates that the command was successful.
System Action: Processing continues.
Operator Response: None.
t
IED3851
grpname,rln ALREADY IN REQUESTED MODEM
SPEED
INACTIVE open lines command; it indicates that all open TCAM
lines are active.
System Action: Processing continues.
Operator Response: None.
5BACKUP STATE
1PRIMARY~
Explanation: This message is issued in response to an
operator command to switch network backup for a VTAM
terminal named ddd. The resource was already in the
requested state.
System Action: The command is rejected. Processing
continues.
Operator Response: None.
INACTIVE open lines command; it indicates that no TCAM lines
are open.
System Action: Processing continues.
Operator Response: None
IED3911
attached to the concentrator identified by station-c, as
indicated in an operator command.
System Action: The command is rejected. Processing
continues.
Operator Response: Verify that the terminal identified by
station is a terminal attached to the concentrator identified by
station-c and reenter· the command.
Problem Determination: Table I, items 2, 10, 29.
operator control command to change the modem speed. The
requested speed was already in effect.
System Action: Processing continues.
Operator Response: None.
grpname,rln CANNOT CHANGE SPEED
Explanation: This message is issued in response to an
operator control command to change the modem speed for the
line identified by grpname,rln. The modem does not have the
speed select feature.
System Action: Processing continues.
Operator Response: None.
SPEED CHANGE COMPLETED FOR grpname,rln
Explanation: This message is issued in response to an
operator control command to change the modem speed. The
command was executed successfully and the line is now
operating at the requested speed.
System Action: Processing continues.
Operator Response: None.
IED3881
IED3881
station IS NOT A TERMINAL ATTACHED TO
CONCENTRATOR station-c
Explanation: The terminal identified by station is not a terminal
Explanation: This message is issued in response to an
IED3871
station IS NOT A CONCENTRATOR OR AN
ATTACHED TERMINAL
Explanation: The station identified by station is not defined as
a concentrator or a terminal attached to a concentrator.
System Action: The command is rejected. Processing
continues.
Operator Response: Verify that the station identified by station
is a concentrator or an attached terminal and reenter the
command.
Problem Determination: Table I, items 2, 10, 29.
IED3921
IED3861
NO LINES OPEN
Explanation: This message is issued in response to a display
Explanation: This message is issued in response to the modify
ddd ALREADY IN
NO LINES INACTIVE
Explanation: This message is issued in response to a display
IED3901
5BACKUP l
~PRIMARY5
IED3841
IED3891
INACTIVE - ddn,rln,lna
INACTIVE - grpname,rln,linename
Explanation: This message is issued in response to the display
INACTIVE open lines command; all inactive open TCAM lines
are listed. ddn is the name from a DO card representing a line
group attached to a 2701/2702/2703. grpname is the name
of a GROUP macro representing a line group attached to a
VTAM. rln is the relative line number of the line within the
group. Ina is the hardware address of the line. linename is the
name of a TERMINAL macro representing a line within the
group. Up to seven rln-Ina or rln-linename combinations may
be listed in the message.
IED3931
station 1 AND station2 UNLIKE DEVICES, COMMAND
REJECTED
Explanation: The stations identified by station 1 and station2
were found to be incompatible for one of the following
reasons:
• DVCID - NONE was coded on one or both TERMINAL
entries.
• The device characteristics of the two devices were not
identical.
• The device IDs of the two stations were not the same
length.
System Action: The command is rejected. Processing
continues.
Operator Response: Verify that the stations identified by
station1 and station2 have the same device characteristics, the
DCVID - NONE was not coded on the TERMINAL entry, and
that the device IDs are of equal length. Then reenter the
command.
Problem Determination: Table I, items 2, 10, 29.
IED3941
DEVICE ID SWAP FOR station1 AND statlon2
COMPLETE
Explanation: The device IDs of the station~ identified by
station 1 and station2 have been swapped.
System Action: Processing continues.
Operator Response: None.
Section 7: lED Messages - Telecommunications Access Method
7-29
•
IED4001
ddd IS A VTAM RESOURCE - VT AM NOT ACTIVE
Explanation: This message is issued in response to an
operator command requesting. that some function be
performed on a VTAM resource. The VTAM/TCAM LINK is
inactive.
System Action: Processing continues.
Operator Response: None.
IED4221
ddd SWITCHED TO BACKUP ON LINE
jgrpname,rln
1UNKNOWN,OOO ~
t
Explanation: This message is issued in response to an
operator command to switch a terminal attached to a VT AM to
a backup path. ddd is the terminal's station name. The backup
line that the terminal was switched to is identified by
grpname,rln. UNKNOWN,OOO indicates that the resource 10 of
the .Iine chosen by the network control program was not
returned to the host. The switch was successful. The backup
line cannot be stopped while being used as a backup path.
System Action: Processing continues.
Operator Response: None.
IED426D
SPECIFY TCAM RECORDS TO BE DUMPED, ALL, OR
END
Explanation: This message is issued in response to a request
to dump a series of TCAM message queue records.
System Action: The dump routine waits for the operator to
specify the range of records to be dumped.
Operator Response: Enter the record numbers of the first and
last message queue records to be dumped (numbers should be
provided by system programmer) or, if desired records have
been dumped, enter END.
IED4271
TCAM RECORDS DUMPED
Explanation: The requested TCAM message queue records
have been dumped.
System Action: Processing continues.
Operator Response: None.
IED4341
TERM = term LINE
DIGITS = nnn
= Ina
ddd ACTIVE - SWDEVICE COMMAND REJECTED
Explanation: An operator command to switch the device
identified by ddd to backup was entered, but the device had
not been previously stopped.
System Action: The command is rejected. Processing
continues.
Operator Response: Vary the station OFFTP,B and then reenter
the original command. After switching to backup has
completed, vary the station ONTP,B.
IED4431
grpname,rln IS NOT A VTAM LINE
Explanation: This message is a response to an operator
command that requested modification of line information for
the line specified by grpname,rln. grpname,rln is not a VTAM
line entry.
System Action: The command is rejected. Processing
continues.
Operator Response: Retry the command using he correct
grpname,rln for the VTAM line.
IED4451
LINE grpname,rln ALREADY AT STATION LIMIT
Explanation: This message is issued in response to an
operator control command that requested switching a station
to the backup line identified by grpname,rln. The backup line
already has its maximum number of stations (3) attached.
System Action: The command is rejected. Processing
continues on the primary line. •
Operator Response: Request another backup line, switch one
of the attached stations to its primary line, or allow the 3705
to select a backup line.
LINE grpname,rln UNAVAILABLE FOR BACKUP
Explanation: This message is issued in response to an
REQUIRES A MANUAL DIAL
SESSION STARTED FOR TERM
DIALED
IED4421
IED4481
Explanation: This message is issued when a manual dial
operation is required to initiate a terminal session over
LINE = Ina. The line is currently operating in manual dial mode.
The manual dial connection must be established and the
session started before a CHANGE MODE operator command
can be issued for the line.
System Action: Processing continues; however, a manual dial
operation must be performed to start a session with
TERM = term.
Operator Response: Use the specified digits to dial the
terminal.
IED4351
System Action: The command is rejected. Processing
continues.
Operator Response: After the switch command being executed
has completed, reenter the rejected command.
= term,
MANUALLY
Explanation: This message is issued after a terminal session
has been initiated across a dial line in manual mode.
System Action: Processing continues.
Operator Response: None.
operator control command that requested switching of a
station to its backup line. The line identified by grpname,rln is
not available for backup.
System Action: The command is rejected. Processing
continues on the primary line.
Operator Response: If the specified line is active and other
lines are available, request an alternate backup line or allow
the 3705 to select a backup line. Otherwise, use a VARY
command to activate the line and then reenter the original
command.
IED4511
STOP COMMAND INVALID FOR TCAM - USE Z TP
Explanation: Response to an attempt to halt TCAM by using a
STOP operator control command. The STOP command is
invalid for TCAM.
System Action: The requested action is not taken. Processing
continues.
Operator Response: Use a TCAM HALT command (Z TP).
IED4601
TCAM ERROR - {OPEN ACB} UNSUCCESSFUL - rc
SETLOGON
IED4361
SWDEVICE IN PROCESS - COMMAND REJECTED
Explanation: This message is a response to an operator
command to switch a device to backup. A previous switch
command was still in process and the second command could
not be executed.
7-30
VS2 System Messages (VS2 Release 3.7)
Explanation: While attempting to open the. ACB
(access-method control block) used to identify TeAM to
VTAM, TCAM detected a nonzero return code from VTAM.An
unsuccessful open or an unsuccessful set logon has occurred.
rc is a 2-byte VTAM return code.
System Action: Normal processing continues.
Programmer Response: Consult the OPEN macro return codes
found in the VTAM Macro Language Reference, or consult
return codes for SETLOGON failure in the VTAM Macro
Language Reference prior to taking any action.
System Action: Normal processing continues.
Programmer Response: Consult the CLOSE macro return codes
found in the VTAM Macro Language Reference prior to taking
any action.
IED4611
IED4651
TCAM/VTAM LINK ACTIVATED
TCAM/VTAM LINK ALREADY ACTIVATED
Explanation: The TCAM/VTAM LINK has been successfully
Explanation: An operator control command to activate the
activated through operator control.
System Action: None.
Operator Response: None.
TCAM/VTAM LINK was entered. The TCAM/VTAM LINK is
already active~'
System Action: Normal processing continues.
Operator Response: Resubmit job when LINK is available.
IED4621
VTAM IS NOT IN THE SYSTEM
Explanation: VT AM was not specified as a feature on the
IED4661
INTRO macro coded in the MCP.
System Action: None.
Programmer Response: Add VTAM to the options coded on the
INTRO macro if you desire VTAM.
Explanation: An operator control command to deactivate the
IED4631
TCAM/VTAM LINK was entered. The TCAM/VTAM LINK is
already inactive.
System Action: Normal processing continues.
Operator Response: None.
TCAM/VTAM LINK DEACTIVATED
Explanation: The TCAM/VT AM LINK has been successfully
deactivated using operator control.
System Action: None.
Operator Response: None.
IED4641
TCAM/VTAM LINK ALREADY DEACTIVATED
TCAM/VTAM INTERFACE NOT DEACTIVATED - rc
Explanation: The TCAM/VTAM interface has not been
deactivated. The CLOSE ACB issued by an operator control
module has failed to complete for the reason identified by the
return code value (rc is a 2-byte VTAM return code).
IED5011
TCAM INITIALIZATION ERROR 045-8
Explanation: The MCP could not be executed because either
the INTRO failed or no DCBs were opened.
System Action: Processing terminates with ABEND 045.
Programmer Response: For INTRO failure, refer to message
IED0651. For no DCB opened, insure that the job control
language contains a DD card for each DCB to be opened.
•
Section 7: lED Messages - Telecommunications Access Method
7-31
7-32
VS2 System Messages (VS2 Release 3.7)
Section 8: Master Scheduler Messages (lEE)
Component Name
lEE
Program Producing Message
Master Scheduler.
Audience and Where Produced
For operator: console.
Message Format
xx IEEnnns text
xx
Message reply identification (absent, if operator reply not required).
nnn
Message serial number.
s
"
I~,
/
Type code:
Action; operator must perform a specific action.
A
D
Decision; operator must choose an alternative.
E
Eventual action; operator must perform action when he has time.
I
Information; no operator action is required.
W Wait; processing stopped until action is determined and performed.
text
Message text.
Comments
None.
Associated Publications
Operator's Library: OS/VS2 Reference (JES21. GC38-0210
Operator's Library: OS/VS2 Display Consoles, GC38-0260
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IEE0191
em QUOTE(S) MISSING.
Explanation: In the cm command, one or more apostrophes
that should appear are missing.
System Action: The system did not execute the command.
Operator Response: Probable user error. Enter the command
again, making sure that the required apostrophes are used.
Problem Determination: Table I, items 2, 7ab, 29.
IEE0231
em CLASSNAME ERROR.
Explanation: In the cm command, the class specified was not a
valid job class or system output class.
System Action: The system did not execute the command.
Operator Response: Probable user error. Enter the command
again, making sure that the class name is correct.
Problem Determination: Table I, items 2, 7ab, 29.
IEE0251
UNIT ddd HAS NO
LOGICAL }PATHS
{ PHYSICAL
Explanation: A VARY command was entered for a device
having no available path.
System Action: The command is not executed.
Operator Response: If NO LOGICAL PATH appears in the
message text, enter a VARY PATH, VARY CHANNEL, or VARY
CPU (whatever was not issued previously) command to make a
path available. If NO PHYSICAL PATH appears, there is a
probable hardware error.
Problem Determination: Table I, items 2, 11, 29.
IEE0261
cm NOT SUPPORTED.
Explanation: If the command indicated by cm in the message
text is LOG or WRITELOG, the system log is not active for one
of these reasons:
• The WRITELOG CLOSE command had been issued.
• The system log task terminated abnormally.
• If cm is DDR SYSRS, dynamic device reconfiguration (or the
SYSRES option of dynamic device recongifuration) is not
supported by OS/VS2. The system cannot complete the
SWAP request entered by the operator.
This message is also issued if a DISPLAY NET, VARY NET, or
HALT NET command is issued.
System Action: The system did not execute the command.
Operator Response: Probable user error. If cm is LOG or
WRITELOG, and if the system log is supposed to be kept,
report the message to the system programmer at the
installation.
Problem Determination: Table I, items 2, 7ab, 17ab, 29. If the
function denoted by the command is supported, and any
necessary data sets are cataloged and mounted, and you must
have the function before proceeding, check Table I, items 11,
29.
IEE0321
WRITELOG COMMAND PENDING. CLASSNAME
class.
=
Explanation: A WRITELOG command was entered to write the
currently recording system log data set on the system output
writer of class class. However, execution of a previously
entered WRITELOG command is still pending.
System Action: The second WRITELOG command is ignored.
Operator Response: If execution of the second WRITELOG
command is required, reissue the WRITELOG command.
~,.
Section 8: lEE Messages - Master Scheduler
8-1
•
IEE0331
HALT OR WRITELOG CLOSE COMMAND HAS BEEN
ISSUED
Explanation: A HALT or WRITELOG CLOSE command was
entered to close the data set currently recording. However, the
execution of a previously entered HALT or WRITELOG CLOSE
command has not completed.
System Action: The second HALT or WRITELOG CLOSE
command is ignored. After execution of the first command has
completed, the log is no longer supported.
Operator Response: None.
IEE0371
LOG NOT ACTIVE
Explanation: The SYSTEM LOG function is not active for
current processing because of one of the following:
• Log initialization failed. This message is preceded by
IEE5331.
• Log ABEND recursion in more than one log data set. This
message preceded by message IEE7691.
• The system log function is terminating as the result of a
WRITELOG CLOSE or HALT command. This message is
preceded by message IEE0431.
System Action: The SYSTEM LOG is not supported for current
processing. Any WTL issued subsequently will be converted to
WTOs and issued to the master console under message
number IEE1471.
Operator Response: In the first case, an attempt is made to
initialize the log from the console via a WRITELOG START
command. If the same message sequence reappears and the
system log is critical to the system, the system must be
reinitialized.
In case two, no response is required. Notify the system
programmer of this message.
In case three, reinitialize the system log via a WRITELOG
START command if the system log function is desired.
IEE0411
THE SYSTEM LOG IS NOW ACTIVE
Explanation: A SYSTEM LOG data set has now been opened
and is ready to receive WTL macro and LOG command
messages.
System Action: Processing continues.
Operator Response: None,.
IEE0431
A SYSTEM LOG DATA SET HAS BEEN QUEUED TO
SYSOUT CLASS class
Explanation: The system log data set was closed and queued
to SYSOUT class class (where class is a valid output class)
because of one of the following reasons:
• The data set is full. The maximum number of system log
records, as specified in the limit parameter, has been
reached, and an internal WRITELOG command was issued to
close the current log data set.
• A WRITELOG command was issued.
• A WRITELOG CLOSE or HALT command was issued while
the log data set was open, followed by message IEE0371.
System Action: For data set full, and for a WRITELOG
command, the currently recording data set is closed, and a
new data set is obtained. A WRITELOG CLOSE or HALT
command will result in the currently recording log data set
being closed and the system log will become inactive.
Operator Response: If it is required to print the system log
data set at this time, start a writer to the class defined by this
message or change the class currently being processed by an
active writer.
8-2
VS2 System Messages (VS2 Release 3.7)
IEE050A
SMF OPTION CANCELED - REPLY U TO CONTINUE
OR RE-IPL
Explanation: During execution of the System Management
Facilities function, the task abnormally terminated.
System Action: No jobs in the system will terminate until the
reply U is given. All data currently residing in the" System
Management Facilities buffers will be preserved. It is necessary
to restart the system in order to reinstate the System
Management Facilities function.
Operator Response: If the system should proceed without
recording System Management Facilities records, enter REPLY
xx, ·U'. If the System Management Facilities function must be
active, restart the system and inform the programmer
responsible for the system.
Problem Determination: If the indicated function is required
before proceeding, see Table I, items 2, 7ab, 11, 29.
IEE0701
hh.mm.ss CPU/CHANNEL STATUS lid]
01 0123456789ABCDEF
yy xxxxxxxxxxxxxxx
CPUzz SERIAL aaaaaabbbb
Explanation: In response to the Display Configuration Matrix
command, this message indicates the status of all central
processing units and all channels in the OS/VS2 system:
• rid] a three-digit decimal CONTROL message identification
number. It is used in conjunction with the CONTROL
C,D command for canceling status displays being
written on typewriter or printer consoles, or being
displayed in-line (not in display area) on a display
(CRT) console. This identification number does not
appear when the display is presented in a display area
on a display console.
• Each y indicates the status of central processing units 0 and
1:
II<
offline
o CPU 0 online.
1
CPU 1 online.
Not in system.
• Each x indicates the status of a channel:
offline on all central processing units.
o online on central processing unit 1 only.
S
online on all central processing units.
not in the system.
One line conaining the CPUid, serial number, and
model number for each online CPU will be written.
zzz CPUid
aaaaa
CPU serial number
bbbb
CPU model number
System Action: Processing continues.
Operator Response: None.
IEE0711
~
hh.mm.ss DEVICE STATUS lid]
0123456789ABCDEF
xxxxxxxxxxxxxxxx
Explanation: In response to a Display Configuration Matrix
command, this message indicates the status of all devices in
the OS/VS2 system.
In the message text, the first and second lines appear once.
The third line appears for each unique channel/control unit
address in the system. In the third line, the first two digits (cc)
are read in conjunction with the hexadecimal digits in the
second line (0123456789ABCDEF) to form unique unit
addresses. Example: Device ccO, device cc1, ... , device ccF.
• rid] a three-digit decimal CONTROL message identification
number. It is used in cori"jlJnction with the CONTROL
C,D command for canceling status displays being written on
typewriter or printer consoles, or being displayed
in-line (not in display area) on a display (CRT)
console. This identification number does not appear
when the display is presented in a display area on a
display console.
• Each cc indicates a unique channel/control unit address in
the system.
• Each x indicates the status of the device represented by
reading the first two digits of the third line and the
hexadecimal digits in the second line:
• A letter 'V' after one or more of the X's above means that
this device is a virtual 3330-type device which is part of a
3850 Mass Storage System (MSS).
*
offline to all central processing units.
o online to central processing unit 0 only.
1
online to central processing unit 1 only.
S
online to all central processing units.
not in the system.
A letter 'V' after one or more of the X's above means
that this device is a virtual 3330-type device which is
part of a 3850 Mass Storage System (MSS).
System Action: Processing continues.
Operator Response: None.
IEE0731
cm IMPROPER CHANNEL NUMBER SPECIFICATION
Explanation: In the cm command, a channel number was
specified for a channel that was not in the system at system
generation.
Operator Response: Probable user error. Enter the command
again correctly, specifying a channel that is in the system.
Problem Determination: Table I, items 11, 29.
IEE0781
cmd 3851 TYPE COMMAND INVALID
Explanation: An MSS command (VARY or HALT command with
S parameter, Assign Primary Host, or PURGE) was issued and
either:
• MSS was not included during system generation
• A previous HALT command with S parameter was successful
• MSS initialization failed and the SSC message module is not
available to the host system. cmd represents the command
verb in error.
System Action: The command is rejected.
Operator Response: Do not issue the MSS commands unless
MSS has been initialized during system generation, or after
HALT command with S parameter has been issued. Inform the
system programmer.
Programmer Response: Correct the initialization problem that
caused the SSC message module to become nondispatchable.
Problem Determination: Issue the DUMP command, and reply
with r id,sdata,stor = (OOOOOO,FFFFFF). Table 1, items 2 and
16.
IEE0841
cm '\..3851 PARAMETER MISSING
{ cuuf
Explanation: Invalid specification in either:
• The VARY command (when cuu is part of the message, the
cuu represents a DSM)
• The HALT command, where cm represents the command
verb in error
For the VARY command, the cuu represents a Data Staging
Manager (DSM) of the 3850 Mass Storage System (MSS).
Including MSC in a VARY command is only valid when the S
parameter is also included. The operator issued the VARY
command and either failed to use the S parameter, or
erroneously specified a cuu that identified an MSC specified an
incorrect cuu (which identified a DSM.)
For the HALT command, one of the MSS parameters
(DINIT/SNAP /LONG) was specified but the operator did not
include the S parameter.
System Action: If cuu appears in the message text, the VARY
command is rejected for the cuu specified in the message, and
processed for the other cuu(s) that may have been specified.
If cm appears in the message text, the HALT command is
rejected.
Operator Response: Respecify the VARY command to include
the S parameter (v cuu,online/offline,s) where cuu is the unit
address of an MSC, or issue the VARY command as v
cuu,online/offline where cuu -is not the unit address of an
'Msc.
Respecify the HALT command with the S parameter, (HALT
S,DINIT/SNAP /LONG)?
Programmer Response: None
Problem Determination: Issue the DUMP command, and reply
with r id,sdata,stor = (OOOOOO,FFFFFF). Table I, items 2 and
16.
IEE094D
SPECIFY OPERAND(S) FOR DUMP COMMAND
Explanation: A dump command has been issued from the
operator's console. This message allows the operator to
specify the storage locations to be dumped.
System Action: Dump command processing waits pending the
operator's reply.
Operator Response: Determine which address space to dump
and what storage areas and/or storage ranges. Then enter the
reply.
ASID = nnn
Specifies the address space to be dumped. nnn is the
decimal representation of an address space identification
number. The address space so identified will be dumped
according to the options of the SDATA and STOR
parameters.
JOBNAME= jjj
jjj is a jobname or userid. The address space so identified
will be dumped according to the options of the SDATA and
STOR parameters.
TSONAME=jjj
iii is a userid. The address space identified will be dumped
according to the option of the SDATA and STOR
parameters.
U
Causes the SDATA default options to be taken for the
Master Memory. Any other data in the command is ignored.
SDATA = (opt..opt)
(PSA, NUC,SQA,LSQA, RGN, TRT,CSA,SWA,LPA)
The underlined options are default options and will be used
if SDATA is specified without any options.
STOR = (x,y[,x,y])
Where x represents starting addresses in decimal or
hexadecimal, and y represents ending addresses in decimal
or hexadecimal format of the storage locations to be
dumped. The decimal addresses must represent a multiple
of 1024 (IK).
Examples:
R xX,ASID = 44,SDATA = (PSA,NUC,TRT),
STOR = (008800,00FFOO)
R xX,JOBNAME =:= USERJOB,SDATA,STOR = (00456K,00490K)
R xX,STOR = (000000,00FFFF,01000K,02000K)
Note: SDATA may also be specified with STOR.
Section 8: lEE Messages - Master Scheduler
8-3
•
VS2.03.804
VS2.03.813
IEE1021
hh:mm.ss yy.ddd
ACTIVITY
[id]
xxxxx JOBS
{
xxxxx INITIATORS
Hi sss PPP
V == R
stradrK - endadrK
iii sss PPP
V == V
[S]
xxxxx TIME SHARING USERS
xxxxx ACTIVE
xxxxx MAX VTAM TSO USERS
userid[S] userid[S] userid[S] ...
DISPLAY TRUNCATED - INSUFFICIENT STORAGE
Explanation: In response to a DISPLAY or TRACK command
with A,L1ST as its operand, this message identifies the number,
names, and userids of active tasks.
The header line appears in response to all DISPLAY or TRACK
commands. The subsequent lines appear dependent upon the
operands of the DISPLAY or TRACK command:
JOBS or J
xxxxx JOBS xxxxx INITIATORS
with ,LIST
jjj sss (etc.)
L
(per active job, MOUNT, or TASK)
TS
- xxxxx TIME SHARING USERS
xxxxx ACTIVE xxxxx MAX VT AM TSO USERS
with ,LIST
userid, use rid. "
L
(list of all active TSO users - 6 per line)
A
- all information for JOBS and TS
with ,LIST - The above, plus all ,LIST
L
information for JOBS and TS
DISPLAY TRUNCATED - INSUFFICIENT STORAGE will appear
when a GETMAIN failure occurs with that position of the
message for which storage could be obtained.
In the message text, the fields are:
hh.mm.ss
Hour (hh) minute (mm) second(ss). This will be 00.00.00 if
the TOO clock is not working when the information is
gathered for the display.
yy.ddd
The last two digits of the year (yy), and the day of the year
(ddd). If the date could not be provided when the
information for the display was gathered, yy.ddd will appear
as 00.000.
[id]
A three-digit decimal identification number. It is used in
conjunction with the CONTROL C,D command for canceling
status displays being written on typewriter or printer
consoles or being displayed in-line (not in display area) on
a display (CRT) console. This identification number does not
appear when the display is presented in a display area on a
display console. (id appears only for DISPLAY, not TRACK.)
xxxxx
Number of active tasks (0 through 99999). If LIST is not
specified, this is only information displayed.
jjj
This field is one of the following:
• The jobname of a job attached by an initiator.
• The procedure name of a task created via the START
command or the MOUNT command.
• STARTING if initaition of a started job or system task is
incomplete.
sss
This field is one of the following:
• The stepname for a job attached by an initiator
• The identifier of a task created via the START command.
• The stepname for a step that called a cataloged
procedure.
• The stepname within a cataloged procedure called by a
step.
• STARTING if initiation of a started job or system task is
incomplete.
ppp
This field is one of the following:
8-4
VS2 System Messages (VS2.03.813)
• The stepname within a cataloged procedure that was
called by the step specified in field sss.
• Blank if there is no cataloged procedure.
stradrk - endadrk
Starting and ending addresses, in decimal, of the V == R
region occupied by the task. These fields appear as 5-digit
decimal multiples of 1024 followed by the letter K, (for
example, 00040K). If the job is not specified for a V == R
region, the starting and ending addresses will not appear.
userid
Userid of each time-sharing user, or STARTING, if logon
p~ocessing for the user is not complete.
System Action: Processing continues.
Operator Response: If DISPLAY TRUNCATED appears on a
display requesting the LIST option, refrain from using LIST until
system activity diminishes.
The fields jjj and sss are, respectively, the procname and 10
required by the STOP and MODIFY commands.
IEE1101
hh.mm.ss
PENDING REQUEST[S] [id]
SUMMARY: [n REPLY ID[S]] [n READY UNIT[S]]
[n INTERVENTION[S] REQUIRED]
[xx yy zz ... ]
&::::]
[READY UNIT[S]:
ddd [ddd ddd ... ]]
[INTERVENTION[S] REQUIRED: ddd [ddd ddd ... ]]
Explanation: This message is issued in response to a DISPLAY
R[, LIST] command if there is any operator action required. In
the message text the fields are:
hh.mm.ss
Hour (hh) minute (mm) second (ss). This will be 00.00.00 if
the TOO clock is not working when the information is
gathered for the display.
id
A three-digit decimal identification number. It is used in
conjunction with the CONTROL C,D command for canceling
status displays being written on typewriter or printer
consoles or being displayed in-line (not in display area) on
a display (CRT) console. This identification number does not
appear when the display is presented in a display area on a
display console.
n
A one- to four-digit decimal number representing the
number of reply ids, ready units, or interventions required
that is to be displayed in the message text.
xxyyzz ...
The two-digit REPLY IDS outstanding if only the R operand
is specified.
xx text
yy text
zz text
The REPLY IDS and corresponding text. Up to 64 characters
of each text will be displayed. The remaining text, if any,
will be truncated after the last blank preceding the 66th
position. The text will appear for each outstanding WTOR
only if the ,LIST or ,L operand is specified.
ddd
The address of each unit for which MOUNT request was
issued, and not yet performed (with READY UNITS:). The
address of each unit having an intervention required
condition pending (with INTERVENTION REQUIRED:).
Note: The second line (SUMMARY line) of the mes"age
indicates the types of requests which are outstanding.
Operator Response: For each xx, yy, or zz listed, find the last
message on the console printout with that identifier and reply
as indicated by the message.
For each ddd listed, find the last MOUNT message on the
console printout for .that device and mount the indicated
volume, or find the last intervention-required message on the
console printout and mount a volume on the indicated unit.
•
Section 8: lEE Messages - Master Scheduler
8-4.1
8-4.2
VS2 System Messages (VS2.03.813)
Note: A MOUNT message may not yet have been issued for
device ddd. If this is the case, no action should be taken until
the MOUNT message has been issued.
IEE1111
NO OUTSTANDING REQUESTS
Explanation: In response to a DISPLAY command with R in its
operand, this message indicates that there are no messages
awaiting replies and there are no unfulfilled mount requests.
System Action: Processing continues.
Operator Response: None.
IEE1351
either reserved or permanently resident.
System Action: The system did not execute the command.
Operator Response: Probable user error. Change the MOUNT
command to specify a different device, or enter an UNLOAD
command and wait for the device that was specified to be
released.
Problem Determination: Table I, items 2, 4, 7ab, 29.
IEE1361
IEE1221
START COMMAND JCL ERROR
Explanation: Either a START command was specified
incorrectly, or the cataloged procedure invoked by the
command contains incorrect job control statements.
System Action: The system did not execute the command.
Operator Response: Probable user error. Look in the SYSOUT
data set for messages associated with. this command; these
messages will describe any errors found in the reader or writer
procedure or in the overriding job control statements
generated from the START command. After making
corrections, enter the command again.
Problem Determination: Table I, items 2, 4, 7ab, 26d, 29.
IEE1241
MOUNT COMMAND JCL
ER~
IEE1301
TIMEOUT - TERMINAL RESET
Explanation: The 2740 console, upon which this message
appears, timed out because the operator did not terminate his
input message with EOB (end-of-block) within 28 seconds of
requesting entry to the console or entering the last character
of data.
System Action: The system reset the terminal to 'stand by'
state and ignored the operator's incomplete input message.
Operator Response: Reenter the input message and terminate
with EOB.
IEE1321
START COMMAND DEV ALLOC ERR
Explanation: During processing of a START command, an error
was detected during allocation of the device specified in the
command.
.
System Action: The system did not execute the command.
Operator Response: Probable user error. Make corrections
indicated by other messages on the console or in the SYSOUT
data set. Then enter the command again.
Problem Determination: Table I, items 2, 4, 7ab, 26d, 29.
IEE1341
MOUNT COMMAND DEV ALLOC ERR
Explanation: During processing of a MOUNT command, an
error was detected during allocation of the device specified in
the command.
System Action: The system did not execute the command.
Operator Response: Probable user error. Make corrections
indicated by other messages on the console or in the SYSOUT
data set. Then enter the command again.
Problem Determination: Table I, items 2, 4, 7ab, 26d, 29.
TIME - hh.mm.ss DATE - yy.ddd
Explanation: In response to a DISPLAY T command, this
message indicates the time of day and the date.
In the message text, hh specifies the hour (00-23), mm
specifies the minute (00-59), ss specifies the second (00-59),
yy specifies the year, and ddd specifies the day (001-366).
Operator Response: None.
IEE1381
cm ALREADY IN SYSTEM
Explanation: Command cm was issued. However, the command
is currently being processed in the system.
System Action: The system did not execute the command.
Operator Response: None.
IEE141A
Explanation: The procedure invoked by a MOUNT command
contains invalid job control statements.
System Action: The system did not execute the command.
Operator Response: Probable user error. Look in the SYSOUT
data set for messages beginning with IEF and" associated with
this command; these messages will describe any errors found
in the procedure. If possible, correct the job control
statements· in the procedure; otherwise, report this message to
the programmer responsible for the system at the installation.
Problem Determination: Table I, items 2, 4, 7ab, 26d, 29.
ERR - REQUESTED DEVICE RESERVED
Explanation: A MOUNT command specified a device that is
MASTER AND ALL ALTERNATES UNAVAILABLE ISSUE VARY MSTCONS
Explanation: An attempt to switch from a master console to an
alternate console has failed because no alternate consoles are
active. The attempt to switch consoles was either initiated
automatically by the device support processor because of an
uncorrectable input/output error, or by the operator pressing
the external interrupt key.
System Action: The system continues processing.
Operator Response: Any operator receiving this message can
enter a VARY MSTCONS command declaring his console or
another active secondary console as the master console. The
VARY MSTCONS command will be accepted from the first
console to issue the command. The console identified as the
master console in the command will assume the functions of
the master console ~nd will receive message IEE1431. (Since
the system continues to queue messages to the master
console while it is waiting for the VARY MSTCONS command
•
to be entered, the command should be entered as soon as
possible.)
If the console switch was caused by the pressing of the
interrupt key, no additional response is required.
Problem Determination: If the console switch occurred as 8
result of an uncorrectable input/output error, see Table I,
items 2,30.
IEE1421
ddd NOW RECEIVING HARDCOPY
Explanation: The hard copy log function has been assumed by
console ddd for one of the following reasons:
• The system log data sets are unavailable.
• The system was erroneously asked to switch the hardcopy
log to a graphic console, during a console switch.
System Action: The hard copy log is switched to console ddd.
Operator Response: If ddd is an acceptable hard copy log, no
response is necessary. Otherwise, a VARY HARDCPY command
must be issued from the master console to switch the log to
an acceptable console.
Section 8: lEE Messages - Master Scheduler
8-5
VS2.03.807
(
IEE1431
IEE1431
OLD - console NEW - console VALDCMD - auth
ROUTCDE - routed T - a H - b
Explanation: This message provides a display of the console's
attributes after a console switch has occurred. The switch
occurred for one of the following reasons:
• The system detected an uncorrectable input/output error on
a console.
• A VARY MSTCONS command was entered.
• The INTERRUPT key was pressed on the operator's control
panel.
In the message text. the fields are:
console
ddd
Device address of the console.
ddd.ddd
Device addresses of the composite console.
auth
SYS
Commands authorized for console are CANCEL. HALT.,
HOLD. MODE. MODIFY. RELEASE. RESET. SET. SETDMN.
START. STOP. CHNGDUMP. TRACE and WRITELOG.
10
Commands authorized for console are MOUNT. UNLOAD.
VARY for devices and SWAP.
CONS
Command authorized for console is VARY and the routing
location operand (L - ).
INFO'
Commands authorized for console are DISPLAY.
CONTROL, MSGRT. STOPMN. MONITOR. LOG. REPLY.
TRACK. STOPTR and SEND.
ALL
Commands authorized for console are all the commands
listed above under SYS. 10. CONS. and INFO.
NONE
No ~mmand authority. which occurs with an output only
device.
routcd
x.x....
The routing codes assigned to the console or hard copy
device; if a composite console. the routing codes
aSSigned to the output device.
ALL
All of the routing codes.
NONE
None of the routing codes.
a
M
Master console.
S
Secondary console.
b
Y
Yes; hard copy log.
N'
No; not a hard copy log.
System Action: The system continues processing.
Operator Response: If the console switch was caused by a
VARY MSTCONS command or by the pressing of the
INTERRUPT key. no response is required.
Note: The failing console is left online. and unallocated.
Problem Determination: If the console switch occurred as a
result of an uncorrectable input/output error. see Table I,
items 2. 30. '
IEE1471
text
Explanation: This message contains the text portion of any
8-6
VS2 System Messages (VS2.03.807)
LOG command or WTL macro Jtxecutions issued while the
system log is not supported. If the log is not active. a WTL
macro instruction is converted to a WTO and assigned this
message 10.
System ActiOn: The system sends each incoming log record as
the text of this message.
Operator Response: If the log is not being supported. report
the message to the system programmer at the installation.
IEE1501
CHANGE OPTIONS IF DESIRED
Explanation: The operator at a CRT console issued a
reference-type CONTROL command. requesting a display of
some current CONTROL or MSGRT conditions. The display, in
CONTROL or MSGRT command format. appears in the entry
area where the operator may choose to change it.
System Action: Processing continues.
Operator Response: If no changes are desired. perform the
CANCEL action. If desired. change the command and ENTER it.
The new values become effective immediately.
IEE1511
DELETE REQUEST
INCONSISTENT-
NO DELETABLE MESSAGES
INVALID RANGE
SEG-O
INVALID OPERAND
NO DISPLAY ON SCREEN
NO DISPLAY IN AREA
USE STOPTR 10 DELETE
I
I
Explanation: The operator entered a request to delete
messages from a dip lay console screen, and one of the
following error conditions occurred:
NO DELETABLE MESSAGE
CONTROL E,F CONTROL E,SEG or CONTROL E,nn C,MJ was
issued, but there were no messages that could be erased by
this request.
INVALID RANGE
CONTROL E,nn C,nnJ was issued. but one or more of the
message numbers specified was not displayed in the visible
message area.
CONTROL E,nn C,nnJ was issued. but the specifi~d message
numbers were invalid.
CONTROL E,nn C,nnJ was issued, but the specified message
numbers included blank lines.
SEG - 0
CONTROL E,SEG was issued, but SEG was specified with a
value of zero.
INVALID OPERAND
CONTROL EX - comma does not follow E.
NO DISPLAY ON SCREEN
CONTROL E,N was issued. but the message line numbers
were already removed.
CONTROL E,D,L - cc was issued, but no status display is on
the screen specified by cc.
NO DISPLAY IN AREA
CONTROL E,D,L - eea was issued, but no status display is in
the area specified by cca.
USE STOPTR TO DELETE
CONTROL E,DC,L -eeaJ was issued to erase a TRACK
dynamic display. The STOPTR command must be used to
tell the system the dynamic display is no longer required.
This results in an automatic erase of the display currently
on the screen.
System Action: The command is not executed.
Operator Response: Correct the command and reissue it.
o C.K may be entered to obtain a display which explains the
CONTROL command. ,
\'
"
IEE1521
"'ENTER'" "'CANCEL'" *0 C,K*
Explanation: This message appears upon initialization only if
the console device is a 2250 or 3277 Display Unit. It permits
the operator to use the light pen (if the device has this
feature) for ENTER and CANCEL actions, and to request a
display of the CONTROL command. The message ap.pears
whenever the instruction line is not required for another
message. (Positioning the light pen on ENTER has the same
effect as pressing the alternate coding (ALTN CODING) and
numeric 5 (END) keys. Positioning the light pen on CANCEL
has the same effect as pressing the alternate coding (ALTN
CODING) and numeric 0 (CANCEL) keys. Positioning the light
pen on 0 C,K has the same effect as typing 0 C,K in the entry
area and performing an ENTER action; this action will cause a
display of the CONTROL command with a brief explanation of
all its operands.
System Action: Processing continues.
Operator Response: If the display unit has a light pen and you
want to, you may position the light pen on 0 C,K for an
explanation of the CONTROL command (displayed in the status
display area.) If an ENTER or CANCEL action is disired,
position the light pen on the word that represents the desired
action.
IEE153E
ERROR - ENTRY GREATER THAN 126 CHARACTERS
Explanation: The 127th position in the entry area contains a
character other than a blank (or EOM symbol on the 2260.)
The cursor appears under the 127th character to aid the
operator in correcting the command.
System Action: U.ntil the 127th position contains a blank (or
EOM symbol), the system ignores all commands.
Operator Response: Correct the command that appears in the
entry area and make sure that a blank is typed in the 127th
position. Then perform an ENTER action.
If it is desired to clear the entry area before making the
correction, perform the CANCEL action. Then enter the
command correctly and perform an ENTER action.
IEE1541
ILLEGAL CURSOR OPERATION - CURSOR
REPOSITIONED
Explanation: The operator performed an ENTER action while
the cursor was positioned in an invalid area. The following are
valid areas:
• Any pOSition on a no-action message line.
• The asterisk on an action message line.
• ENTER, CANCEL, or 0 C,K in the instruction line.
• Any position in the entry area.
• Any of the detectable options in the control line of a status
display.
If the cursor is positioned at any other place, it is an error.
System Action: The cursor is repositioned to the left of the
entry area.
Operator Response: Position the cursor properly to perform
the desired operation.
IEE1561
cm INVALID OPERAND - op
Explanation: In the CONTROL command, one of these error
conditions occurred:
• The specification (S) operand was invalid.
• The first character after CONTROL (or K) was not E, S, 0,
T, C, N, A, or V.
• The operand following CONTROL 0 (of K D) was not N;
N,HOLD; F; H; or U; PFK.
• RNUM or RTME specified a value of zero.
• The K N,PFK command contains an error. The type of error
is indicated by the location of the cursor:
a. If the cursor is positioned under the first letter of a
keyword (CMD, KEY, PFK, or CON), that keyword or its
trailing equal sign is incorrect.
b. If the cursor points to the number of the key being
defined, that key is either not a numeric character, not a
key that was defined during system generation, or is a
key being defined as a list of keys that is already
contained within another list of keys.
c. If the cursor points to a key number after the KEY =
parameter, that key is either not a numeric character, the
number of the key that is being defined, a key which has
been defined as a list of keys, or a key that was not
defined during system generation.
d. If the cursor points to some other location, a syntax
error exists at the position indicated by the cursor.
• The multi-line WTO 10 specified on the K C,D,ID command
is invalid or is directed to the wrong console.
• The operands on the K V command are invalid.
In the message text, op represents the first six characters of
the invalid operand.
System Action: The command was not executed.
Operator Response: If the command is K or MR, correct the
command by positioning the cursor under the characters to be
changed and typing the correct information. Then perform the
ENTER action.
If desired, the command may be canceled.
IEE157E
DELETION REQUESTED
Explanation: The operator issued a deletion request in
conversational mode. The deletion request appears in
command form in the entry area, and the messages selected
for deletion are indicated by vertical lines displayed in position
3 of the message line.
System Action: No messages are deleted until the operator
has responded to this message.
Operator Response: Respond in one of the following ways:
• To remove the indicated messages, perform an ENTER
action, or position the light pen on the same message.
• To change the deletion request, position the cursor under
the proper characters and type the desired information.
(Also, the light pen may be positioned on message line.)
Then perform an ENTER action. AJI messages that are to be
deleted will be marked with vertical lines. Verify that the
messages so marked are correct and perform an ENTER
action.
• To retain the messages, perform a CANCEL action. This
restores the screen, blanks the entry area, and repositions
the cursor at the left side of the entry area.
IEE1581
K
REQUEST
INCONSISTENT -{ STATUS ALREADY EXISTS}
NO DISPLAY ON SCREEN
NO DISPLAY IN AREA
LAST FRAME DISPLAYED
FRAME NOT COMPLETE
DISPLAY IS NOT DYNAMIC
NO TRACK ACTIVE
Explanation: One of the following error conditions occurred
when the CONTROL (K) command was issued:
STATUS ALREADY EXISTS
A CONTROL option was requested which is already in
effect. For example K S,DEL = R is entered when the
console is in roll mode.
NO DISPLAY ON SCREEN
A CONTROL option for a display, such as framing or
erasing, was requested and there is no display on the
screen.
Section 8: lEE Messages - Master Scheduler
8-7
•
NO DISPLAY IN AREA
A CONTROL option, such as framing or erasing, was
requested for a display in a particular area and there is no
display in that area.
LAST FRAME DISPLAYED
K D,F or K D,F,L = cca was issued but the last frame of the
display is already on the screen.
FRAME NOT COMPLETE
A framing request K D,F was issued, but the frame of the
display currently on the screen is not complete yet. The
request must be reissued when the current frame is
complete.
DISPLAY IS NOT DYNAMIC
'Hold' K D,H or 'update' K D,U of a display was requested,
but the display is not dynamic (TRACK). These options
apply only to a dynamic display, which is initiated by use of
the TRACK command.
NO TRACK ACTIVE
A K, T,REF or K,T,UTME = nnn command was issued for a
console not receiving output from the TRACK command.
System Action: The command is not executed.
Operator Response: In the' first case, change the command and
reenter, or CANCEL the command since the condition already
exists.
In the second case, change the command to specify the
correct console 10, with L = cc, and reenter or CANCEL the
command since the conditions required by the command do
not exist.
In the third case, change the command to specify the correct
area and reenter, or CANCEL the command.
In the fourth case, CANCEL the command since no more
frames can be displayed.
In the fifth case, enter the request again after the entire frame
has been displayed.
In the sixth case, change the command to specify the correct
display with L = cca and reenter, or CANCEL the command.
In the seventh case, issue a TRACK command for the console,
if desired.
IEE159E
MESSAGE WAITING
Explanation: All message lines are filled, but another message
is waiting to be displayed. This message appears if automatic
message deletion was not in effect (DEL = N) or if automatic
message deletion was in effect (DEL = Y) but no messages in
the message area contained vertical lines in position 3.
This message also appears if the screen is full of intervention
required (INT REQ) messages, or WTORs.
System Action: No new messages are displayed until some
messages are deleted either by the operator, by a system
task, or by a problem program. (Messages are deleted by a
problem program or system task only if automatic message
deletion is in effect.)
Operator Response: Delete the messages by using either the
CONTROL command, the light pen, or the cursor. (In
conversational mode, it will be necessary to perform an ENTER
action a second time without making any changes to signal
verification of the deletion request.) If enough messages are
removed so that all waiting messages are displayed, this
message is removed.
If the screen is full of intervention required (lNT REQ)
messages, perform the actions where possible; then, if
automatic message deletion is not in effect, delete those
messages from the screen.
If the screen is full of WTORs, start replying to them; then,
delete those messages from the screen.
8-8
VS2 System Messages (VS2 Release 3.7)
IEE1601
UNVIEWABLE MESSAGE
Explanation: A status display is temporarily replacing one or
more messages.
System Action: If a system task or a problem program has
issued a DOM macro instruction, and if DEL = Y is in effect,
automatic message deletion occurs. Otherwise, the system
continues queueing the new messages until the operator either
removes the status display or removes some messages above
the status display. (Message IEE159E replaces this message if
there are more messages waiting than are currently being
displaced by the status display.)
Operator Response: Respond in one of the following ways:
• Enter a CONTROL E,D command or position the light pen on
*E* in the title line to remove the display, thereby freeing
the bottom portion of the message area for displaying
messages.
• Request message deletion by using the cursor or light pen
or by entering a CONTROL command, thereby removing one
or more messages above the display so that more
messages can be displayed.
IEE1611
WARNING - CON
= N,OEL = Y
Explanation: One of the following occurred:
• Automatic message deletion was in effect (DEL = Y) when
the operator entered a CONTROL S,CON = N command,
requesting non-conversational mode.
• Conversational mode was not in effect (CON = N) when the
operator entered a CONTROL S,DEL = Y command,
requesting automatic message deletion.
• The operator entered a CONTROL S,CON = N,DEL = Y
command, requesting non-conversational mode and
automatic message deletion.
This message is a warning in response to an erase (E) request.
System Action: ProceSSing continues. Some Messages other
than the requested messages may be lost.
Operator Response: If automatic message deletion is in effect,
it is strongly recommended that conversational mode be used
so that messages can be verified before they are deleted. If
conversational mode is not desired, d~lete the messages
manually before the message area is "filled.
IEE1621
hh.mm.ss K COMMANO [id]
Explanation: This is the control line of the Status Display
initiated by the DISPLAY C,K command:
[id]
Is a three-digit decimal identification number. It is used in
conjunction with the CONTROL C,D command for canceling
status displays being written on typewriter or printer
consoles or being displayed in-line (not in a display area)
on a display (CRT) console. This identification number does
not appear when the display is presented in a display area
on a display console.
Operator Response: None.
IEE1631
MOOE= {:O}
Explanation: The operator entered a CONTROL S,DEL = R or
CONTROL S,DEL = RD command, as indicated in the message
text, requesting that roll mode be in effect.
System Action: When the message area is filled, the number
of messages specified by the RNUM parameter (of the
CONTROL command) is removed at the interval specified by
the RTME parameter (of the CONTROL command) or as long
as there are messages waiting to be displayed.
Operator Response: None.
IEE1641
ILLEGAL LIGHT PEN - CURSOR DETECT
Explanation: An error occurred because the light pen or the
cursor was not positioned in a valid location. The only' valid
locations for positioning the light pen or the cursor are:
• In any position on a non-action message line.
• On the asterisk on an action message line.
• On a detectable CONTROL command option (such as *F or
*E) in the control line of a status display.
• On *ENTER*, *CANCEL*, or *0 C,K* in the instruction line.
System Action: The system does not act upon the invalid
request; the'screen remains the Same.
Operator Response: Position the light pen or cursor properly to
perform the desired operation.
IEE167E
OUTPUT IN HOLD MODE
Explanation: No new messages can be written on the screen
until the operator takes some action, such as confirming a
command or canceling a request. This message appears only
on 2260 console devices.
System Action: The display console is in HOLD mode. No
more messages will be displayed until the operator has
responded to this message.
Operator Response: Enter data or perform a CANCEL action by
repositioning the cursor next to the START MI symbol and
pressing the ENTER key.
IEE170E
IEE170E
RETRYABLE ERROR. RECENT ACTION MAY NEED TO
BE REPEATED.
PRESS THE CANCEL KEY TO RESTORE THE
SCREEN.
Explanation: A hardware error occurred that was not caused
I~
V
by operator action. If the same error occurs again, the device
is considered unusable and the error is logged. In addition,
multiple console support will transfer the routing codes and the
command input capability of this console to an active alternate
console, and will issue message IEE1431. (Anything in the entry
area at the time of the error will be lost.)
System Action: If the operator does not perform a CANCEL
action, the system automatically rewrites the screen after
approximately 30 seconds have elapsed (this results in the
same effect as a CANCEl action). If the operator requests that
the consoles be switched, the system writes all succeeding
messages on the new console device.
Operator Response: Probable hardware error. To continue,
perform a CANCEL action. The messages are rewritten on the
screen. However, any status displays are lost. The request
must be reentered.
Note: The 2260 display console does not have a CANCEL key;
the system will automatically restore the screen in about 30
seconds.
Problem Determination: Table I, items 2, 30.
IEEI71E
IEEI71E
CONDITIONAL ERROR. RECENT ACTION MAY NEED
TO BE REPEATED.
PRESS CANCEL TO CONTINUE, OR SWITCH
CONSOLES.
Explanation: A hardware error has occurred. However, the
device may still be usable.
System Action: If the operator does not perform a CANCEL
action, the system automatically rewrites the screen after
approximately 30 seconds have elapsed (this results in the
same effect as a CANCEL action). If the operator requests that
the consoles be switched, the system writes all succeeding
messages on the new console device.
Operator Response: Probable hardware error. If the device is
still usable, perform a CANCEL action to continue operating.
However, keyboard, cursor,' or light pen actions may need to
be repeated.
Note: The 2260 display console does not have a CANCEL key;
the system will automatically restore the screen in about 30
seconds.
If it is desired not to continue, use the multiple console
support option to remove this device as a console.
Problem Determination: Table I, items 2, 30.
IEE1921
INVALID PROCEDURE PARM FIELD FORMAT
Explanation: The writer procedure invoked by a START XWTR
command contains an EXEC statement with an invalid PARM
parameter.
System Action: The system did not execute the command.
Operator Response: Report this message to the system
programmer at the installation.
IEE2501
hh.mm.ss CONSOLE DISPLAY [Id]
AUTH 10 AREA ROUTCD
CONSOLE/ALT COND
Console/alt
H
authl nn z,a.-a 2 routed
SYSLOG
H
routed
M [, T]
auth2 nn z,a. -a2 routcd
console / alt
[,J]
A [,P][,T]
[,J]
N [,P][,T]
S [,P)[,T]
[,J]
Explanation: In response to a DISPLAY CONSOLES command,
this message provides a display of the system console
configuration. The first format of .the message always appears;
the second or third format appears if a hard copy device is
available; the last format appears for each console specified at
system generation.
In the message text, the fields are:
rid]
A three-digit decimal identification number. It is used in
conjunction with the CONTROL C,D command for canceling
status displays being written on typewriter or printer
consoles or being displayed in-line (not in a display area)
on a display (CRT) consoles. This identification number
does not appear when the display is presented in a display
area on a display console.
CONSOLE
console
ddd
Device address of the primary console, which is
either an output device or an input! output device.
ddd,ddd
Device addresses of the composite primary console.
Note: JES specifies dummy uca address for dummy
subsystem console.
ddd/JES MCS console in use by subsystem
JES/JES subsystem only console
SYSlOG
The SYSLOG is the hard copy device.
AlT
alt
ddd
Device address of the alternate console.
ddd,ddd
Device ad~resses of the composite alternate
console.
COND
H
Hardcopy device.
Section 8: lEE Meua.es - Master Scheduler
8-9
•
YS2.03.807
The routing codes assigned to the console or hard
copy device; if a composite console, the routing
codes assigned to the output device.
M
Master console.
A
.Active console.
N
Inactive console.
A,P
In the process of becoming an active console.
N,P
In the process of becoming a non-active console.
After M, A, N, or A,P, or N,P:
,T
Requesting timestamps and jobnames before all
messages.
,J
Requesting only jobnames before all messages.
S
Subsystem console
AUTH
authl
CMOS
Operator and system commands and responses are
to be written on the hard copy log.
STCMDS
Operator and system commands and status displays
are to be written on the hard copy log.
INCMDS
Operator and system commands and in-line
responses are to b~ written on the hardcopy log.
NOCMDS
~.-\
Operator and system 'commands and responses are
not to be written on the hard copy log.
auth2
SYS
Commands authorized for console are CANCEL,
HALT, HOLD, MODE, MODIFY, RELEASE, RESET,
SET, SETDMN, START, STOP, SWITCH,
CHNGDUMP, TRACE and WRITELOG.
10
Co'mmands authorized for console are MOUNT,
SWAP, UNLOAD, and VARY for devices.
CONS
Command authorized for console is VARY for
consoles, and the routing location operand (L - ).
INFO
Comrt:lands authorized for console are DISPLAY,
LOG, CONTROL, MONITOR, MSGRT, STOPMN,
REPLY, SEND, TRACK, and STOPTR.
ALL
Commands authorized for console are all the
commands listed above under SYS, 10, CONS, and
INFO.
NONE
No command authority, which occurs with an
_output only_device.
10 nn
The system identification number for this console.
AREA
z, a 1 - a2 ~he range of area designators defined for this
console, where z is the id of the. message area, a1 is the
bottom area and a2 is the top area. The presence of some
or all of these deSignators is dependent upon the area
definitions currently in effect at this console.
ROUTCD
routcd
8·10
VS2 System Messages (VS2.03.807)
ALL
All of the routing codes.
NONE
None of the routing codes.
Operator Response: None.
Note: In a system which has no CRT consoles sysgened, the
AREA column will not be displayed.
IEE2981
cm INVALID CHARACTER
Explanation: In the cm command, an invalid character (not
enclosed in apostrophes) was found in the operation, operand,
or comment field.
System Action: The command was not executed.
Operator Response: Probable user error. Enter the command
again, correctly. (If the command was originally entered
through the input stream, the command may be reissued
through the console in response to this message.)
Problem Determination: Table I, items 2, 7b, 29. If unable to
continue system operation see Table I, item 11.
IEE2991
{SYSLOG} REQ'D FOR HARDCOPY
ddd
Explanation: The operator entered the VARY HARDCPY,OFF
command without first reassigning the hardcopy function to
either the system log, a stand-alone console, or an operator's
console. If more than one console is active, or if a single
graphics console is active, the hardcopy function is required.
System Action: The command is not executed.
Operator Response: Enter the VARY HARDCPY command
specifying a new hardcopy device, or the system log. Then
reenter the previous command.
IEE3001
ddd/aaa INVALID ALTCON
Explanation: In a VARY ddd,CONSOLE command, parameter
ALTCON specified an invalid alternate console aaa:
• ddd and aaa are the same device.
• ddd has input/output capabilities and aaa has only output
capabilities.
System Action: In the first case, the command is not
processed for device ddd. In the second case, if device ddd
was previously a console, the previous alternate console is
maintained; otherwise, device ddd is made a console, and the
alternate console specified at system generation is maintained.
Operator Response: In the first case, choose another alternate
console and reenter the command. In the second case, choose
an alternate console with input/output capabilities and reenter
the command.
iii CANCEL COMMAND ACCEPTED
Explanation: Job jjj was canceled in response to a CANCEL
command, or by the system. If the job was canceled by the
systeri'l, messages will follow explaining the reason for the
cancelation.
System Action: All references to the job are deleted from the
system.
Operator Response: None.
IEE3011
IEE3021
{PATH(ddd,X)}
ddd
ONLINE [NOT VERIFIED]
Explanation: One of the following occurred:
• In response to a VARY device online command, 1he system
has placed device ddd online.
r~
• In response to a VARY PATH online command, the path to
device ddd has been placed online.
• For active TP devices, validity check of physical path to the
device is bypassed. The path is marked online.
System Action: Processing continues. The new path is now
available for system use.
Operator Response: None.
IEE3031 {PATH(ddd,X)}
ddd
OFFLINE
Explanation: One of the following occurred:
• In response to a VARY device offline command, the system
has placed device ddd offline.
• In response to a VARY PATH offline command, the path to
device ddd has been placed offline.
System Action: Processing continues.
Operator Response: None.
IEE3041
jjj JOB RESET
Explanation: In response to a RESET command, the system
has changed the performance group of the job named jjj.
System Action: Processing continues.
Operator Response: None.
IEE3051 {cm
} COMMAND INVALID
(blanks)
MODE
Explanation: The cm command is invalid for one of the
following reasons:
• The command is misspelled or punctuated incorrectly.
• A command valid only at Initial Program Load (IPL) was
used after IPL.
• A command was issued without a prerequisite command.
• A TRACK command was issued to a non-CRT device.
• Incorrect operand - as in HOLD or RELEASE commands
without TP operand.
If blanks appear, the operand of the central command was too
long, or a framing quote was not found within 62 bytes.
MODE indicates that ECC was requested in record mode while
HIR was in quiet mode.
System Action: The system did not execute the command.
Operator Response: Probable user error. If blanks or cm
appear, enter the command again correctly. For MODE, if
desired, enter the command to place HIR into record mode
before resubmitting the command to place ECC into record
mode.
Problem Determination: Table I, items 2, 29.
IEE3061
cm INVALID NUMERICS
Explanation: In the cm command, a parameter value that is
supposed to be numeric either contains one or more
characters that are not numbers or has too large a value.
Example: RESET JOBX,PERFORM = 2X where the performance
group must be a number between 0 and 255.
System Action: The system did not execute the command.
Operator Response: Probable user error. Enter the command
again correctly.
Problem Determination: Table I, items 2, 29.
IEE3071
cm DELIMITER· ERROR
Explanation: In the cm command, either the punctuation for a
parameter is incorrect, or the operand field is not followed by
a blank.
Example: V (132,133,ONLINE - where the device list must
have a closing parenthesis.
System Action: The system did not execute the command.
Operator Response: Probable user error. Enter the command
again correctly.
Problem Determination: Table I, items 2, 29
IEE3081
cm TERM LENGTH ERROR
Explanation: In the cm command, a parameter is too long or
short. Either the parameter is not spelled correctly or a comma
is not in the correct location.
If this is a VARY Range specification, you can not mix single
units with ranges of units.
Example: C ABCDEFGHI - where a job name cannot exceed 8
characters.
System Action: The system did not execute the command.
Operator Response: Probable user error. Enter the command
again correctly.
Problem Determination: Table I, items 2, 29.
IEE3091
cm UNIDENTIFIABLE KEYWORD
Explanation: In the cm command, a keyword is misspelled.
System Action: The system did not execute the command.
Operator Response: Probable user error. Enter the command
again correctly.
Problem Determination: Table I, items 2, 29.
IEE3101
cm KEYWORD MISSING
Explanation: In the cm command, a required keyword
parameter is missing.
System Action: The system did not execute the command.
Operator Response: Probable user error. Enter the command
again correctly.
Problem Determination: Table I, items 2,. 7ab, 29.
IEE3111
cm PARAMETER MISSING
Explanation: In the cm command, a required parameter is
missing.
System Action: The system did not execute the command.
Operator Response: Probable user error. Enter the command
again correctly.
Problem Determination: Table I, items 2, 29.
IEE3121
em PARAMETERS CONFLICT
Explanation: In the command indicated by cm in the message
text, a keyword parameter either appears more than once or
conflicts with another parameter.
If cm is a VARY command, it indicates that the CONSOLE
keyword cannot be specified on a Vary Range command or on
a VARY command with an MSS parameter.
System Action: The system did not execute the cm command.
Operator Response: Probable user error. Enter the correct
command again.
Problem Determination: Table I, items 2, 29.
IEE3131 {CN(XX)
}
devname
UNIT REF INVALID
HARDCOPY
Explanation: In a command, the unit name indicated by
devname or the console 10 indicated by CN(xx) is invalid or
indicates a device type that cannot be used for the purpose
intended by the command. If a Vary Hardcopy Off command is
entered and there is no currently-recording hardcopy log,
HARDCOPY will replace devname in the message text. In the
case of an invalid composite specification, both the I-unit and
the O-unit device addresses will appear. If only one unit of a
composite specification is specified, this message will appear
with the unit even though it is a valid part of a composite
specification. The entire specification must be used.
If 'V CN(xx),AUTH =: value' was issued (where xx is the console
10) and the consode 10 is invalid or the issuer is not
authorized, the authority value for the specified console is not
changed.
If the unit is offline when an UNLOAD command is issued, then
the UNLOAD command will not be processed.
Example: UNLOAD 130 - where 130 is offline; will yield
IEE3131 130 UNIT REF INVALID
Section 8: lEE Messages - Master Scheduler
8-11
•
If a Vary Range command (e.g. vary xxx-yYY,offline) is entered
and each of the specified units is individually invalid, xxx-yyy
replaces devname in the message.
If a VARY CONSOLE command was issued on device xxx, and
the said device is not active and not ready, this message will
be issued to show the status.
System Action: The system did not execute the command.
Operator Response: Probable user error. Enter the command
again, correcting the unit name.
Problem Determination: Table I, items 2, 7ab, 29.
IEE3141
cm UNIT NOT AVAILABLE
Explanation: In the cm command, one or more units specified
are unavailable; that is, they are already in use. If an UNLOAD
command was entered, cm specifies the unit name.
System Action: The system did not execute the command.
Operator Response: Probable user error. Enter the command
again correctly.
Problem Determination: Table I, items 2, 7b, 29.
IEE3151
em UNIT NOT SUPPORTED
Explanation: In the cm command, one or more units specified
are invalid; that is, they cannot be used for the purpose
intended by the command.
System Action: The system did not execute the command.
Operator Response: Probable user error Enter the command
again correctly.
Problem Determination: Table I, items 2, 7ab, 29.
IEE3241
userid NOT LOGGED ON
Explanation: The operator has entered CANCEL U = userid, but
the specified user, userid, is currently not running in the
system.
System Action: The command was not executed.
Operator Response: None.
IEE3281
cm COMMAND ABORTED
Explanation: Due to an insufficient amount of storage, the
system was unable to schedule a command for execution. This
message is also issued if an· attempt is made to obtain more
address spaces than the system limit, or for VARY device
online, if the device would hot accept on I/O command. This
last case would result if another CPU has reserved the device
and then does not release it, or if there is a hardware error.
System Action: The command is not executed.
Operator Response: Reenter the command at a later time.
ddd IN USE BY A SYSTEM COMPONENT
Explanation: The user issued a V ddd,ONLINE command or, a
V ddd,CONSOLE command. The specified device is presently in
use by a system component and cannot be made available to
VS until completion of the system component.
System Action: The system does not process the request.
Operator Response: Reissue the command when the system
component has completed.
IEE3291
IEE3341
HALT EOD SUCCESSFUL
Explanation: In response to a HALT EOD command, the system
has stored internal input! output device error counts in the
SYS1.LOGREC data set.
Operator Response: The power can be turned off.
IEE3351
Explanation:
VOL PARAMETER MISSING
In a MOUNT command, the VOL parameter is
missing.
System Action: The system did not execute the command.
Operator Response: Probable user error. Enter the command
again correctly.
Problem Determination: Table I, items 2, 7ab, 29.
8-12
VS2 System Messages (VS2 Release 3.7)
IEE3381
ddd INACTIVE AS HARDCPY
Explanation: In response to a VARY HARDCPY,OFF command,
the hard copy capabilities have been varied out of device ddd.
System Action: Since hardcopy is not required, the command
has been accepted by the system.
Operator Response: None.
IEE3391
ddd CHANGING STATUS
Explanation: A VARY command was issued for device ddd.
However, the device is currently in the process of changing
status. In the case of an invalid composite· specification, both
the I-unit and the O-unit device addresses will appear.
System Action: The system did not execute the command.
Operator Response: Use the DISPLAY CONSOLES command to
determine the status of the device. After the device has
completed its status change, reenter the command.
IEE3411 {~~t} NOT ACTIVE
JJJ
Explanation: A command was received which applies to the
task named ttt; however, no task with this name is currently
active. The message will also appear if JOBX was running but
was defined in the Program Properties Tables as being
non-cancelable.
If TRACE STATUS was issued, and ttt is TRACE, the system
tracing is not active.
Example: CANCEL JOBX is issued with no JOBX running.
If a DISPLAY T command is issued and the clock was
inoperative, ttt will be CLOCK.
System Action: The command was not executed.
Operator Response: Verify that the task has been started by
issuing a DISPLAY A, LIST command or make sure that the task
name was specified correctly in the command.
If ttt is CLOCK, reissue the D T command if desired. The same
results could occur.
If ttt is TRACE, no response is needed.
Problem Determination: Table I, items 2, 7ab, 29. If unable to
continue system operation, see Table I, item 11. For CLOCK,
add item 7d.
Note: After a swap from a started reader or writer, all console
communication must be with the old device address until the
reader or writer in the swap is closed. Then the new device
address can be used.
IEE3421
cm REJECTED - TASK BUSY.
Explanation: The command named cm was received; however,
either the command applies to a task that has not finished
processing a previous command or the command was entered
for a job or task that is in a 'must complete' mode.
Example: With JOBX running, STOP X was issued. If MODIFY
X, parameters is issued, message IEE3421 will be issued.
System Action: The command was not executed.
Operator Response: Reenter the command after the previous
commands have completed execution.
IEE3451
cm AUTHORITY INVALID
Explanation: Command cm was entered from a console without
the proper command authority.
Example: K V was issued against the Master Console. MSGRT
with L = cca was issued from a console without routing
authority. The L = cca operand was attached to a command
issued from a console without routing authority.
System Action: The system did not execute the command.
However, if a VARY command was entered, the command will
not be processed only for the device specified in the message
text.
Operator Response: Probable user error. Reenter the command
from a console with the proper command authority.
Problem Determination: Table I, items 2, 7ab, 17ab, 29. Issue
a 'DISPLAY CONSOLES' command.
If unable to continue system operation, see Table I, item 11.
YS2.03.807
IEE3491
{ IEE3491
{
HARDCOPY CONSOLE}
CONSOLES
CONSOLE/ALT COND AUTH
console/alt
H
authl
SYSLOG
}
console / alt
J
SET. SETDMN, START, STOP, SWITCH,
CHNGDUMP, TRACE and WRITELOG.
10 AREA
nn z,a l -a2
ROUTCD
routcd
routcd
1M
auth2
A[,P]
N[,P]
N[,T]
Explanation: In response to a VARY command, this message
provides a display of the console configuration. In response to
a VARY HARDCPY command, the first format of the titie line
and the data line appears with the label line. In response to a
VARY CONSOLE command, the second format of the data line
appears with the title and label lines.
In the message text, the fields are:
CONSOLE
console
ddd
Device address of the primary console~ which is
either an output device or an input; output device.
ddd,ddd
Device addresses of the composite primary console.
SYSLOG
The SYSLOG is the hardcopy device.
ALT
alt
ddd
Device address of the alternate console.
ddd,ddd
Device addresses of the composite alternate
console.
COND
10
Commands authorized for the console are MOUNT.
UNLOAD. SWAP, and VARY for devices.
CONS
Command authorized for the console is VARY. for
consoles, plus use of the routing location operand.
INFO
Commands authorized for console are DISPLAY.
LOG, and CONTROL. MONITOR, MSGRT, STOPMN.
REPLY. SEND. TRACK. and STOPTR.
ALL
Commands authorized for console are all the
commands listed above under SYS, 10. CONS. and
INFO.
NONE
No command authority. which occurs with an
'output only' device.
10 nn
The system identification number for this console.
AREA
z, al - a2 the range of area designators defined for this
console. where z is the id of the message area. al is the
bottom area and a2 is the top area. The presence of some
or all of these designators is dependent on the area
definitions currently in effect at this console.
ROUTCD
routcd
x.x•...
The routing codes assigned to the console or
hardcopy device; if a composite console. the
routing codes assigned to the output device.
ALL
H
Hardcopy device.
M
Master console,
A
Active console.
A,P
In the process of becoming an active console.
N
Non-active console.
N,P
In the process of becoming a non-active console.
N.T
Cannot be made a console until the Online Test
Executive Program (OLTEP) completes its online test
program.
AUTH
authl
CMOS
Operator and system commands and all responses
are to be written on the hardcopy log.
STCMDS
Operator and system commands and status displays
are to be written on the hardcopy log.
INCMDS
Operator and system commands and inline
responses are to be ~ritten ori the hardcopy log.
NOCMDS
Operator and system commands and responses are
not to be written on the hardcopy· log.
auth2
·SYS
Commands authorized for the console are CANCEL.
HALT. HOLD. MODE. MODIFY. RELEASE. RESET.
All of the routing codes.
NONE
None of the routing codes.
Operator Response: None.
Note: If the console specified is not a CRT console. the AREA
column will not be displayed.
IEE3511
SMF SYS I.MAN RECORDING NOT BEING USED
Explanation: During SMF initialization. one of the following
•
occurred:
• Space was not allocated for the SYS1.MAN data set or
SYSl.MAN data set could not be opened.
• MAN = NONE was specified. indicating that no data records
were to be written in the SMF data set.
System Action: In the first case. message IEE3581. or IEE3631
precedes this message. indicating the cause of the error. In
both cases. processing continues. but no records are written in
the SYSl.MAN data set.
Operator Response: In the first case. inform the system
programmer to properly define the SMF parmlib member as
indicated in the response to the preceding message. In the
second case no response is required.
IEE352A
SMF MEMBER SMFPRMxx MISSING - REPLY WITH
SMF VALUES OR RE-IPL
Explanation: During SMF initialization. the specified SMF
parmlib member was not found in the SYS1.PARMLIB data set.
System Action: SMF initialization will not continue until the
operator has responded to this message.
Operator Response: Probable user error. Enter REPLY
xx. 'keywd = val. keywd = val'. listing all the required SMF
parameters as defined by the programmer responsible for the
system at your installation. Inform the programmer responsible
Section 8: lEE Messages - Master Scheduler
8-13
for the system to define the SMF member In the
SYSl.PARMLIB data set, thereby eliminating the need to
redefine the SMF parameters from the keyboard at every IPL.
Problem Determination: Table I, items 2, 7ab, 29. Execute the
IEHLlST utility program to list members of SYSl.PARMLIB and
save the output.
IEE353A
I/O ERROR ON SMFPRMxx READ - REPLY WITH
SMF VALUES OR RE-IPL
Explanation: During SMF initialization, an uncorrectable
input!output error occurred while reading or searching for the
SMFPRMxx member in the SYSl.PARMLIB data set.
System Action: SMF initialization will not continue until the
operator has responded to this message.
Operator Response: Restart the system. If the error persists,
enter REPLY xx, 'keywd - val,keywd - val', listing all the
required SMF parameters as defined by the system
programmer at your installation. Inform the system
programmer to redefine the SMF parmlib member.
'Problem Determination: Table I, items 2,7ab, 29.
IEE3541
SMF PARAMETERS
Explanation: This message is issued if OPI - YES was specified
in theSMF parmlib member. All the parameters of the SMF
parmlib member are listed, one parameter to a line, following
this message; each parameter is listed in the format
'keywd - val'.
System Action: Message IEE357A is issued, permitting
changes to be made.
Operator Response: None.
IEE3551
SMF PARAMETER ERRORS
IEE3551 {keYWd UNRECOGNIZABLE KEYWORD/FORMAT}
keywd - val INVALID VALUE SPECIFIED
keywd - KEYWORD NOT SPECIFIED
Explanation: During SMF initialization, a parameter was
specified incorrectly either in the SMF parmlib member or in a
reply from the. console. The specific error is listed in the
second line of the message:
keywd UNRECOGNIZABLE KEYWORD/FORMAT
An unrecognizable keyword was detected; keywd specifies
up to 25 characters of the keyword in error.
keywd - val INVALID VALUE SPECIFIED
The keyword specified is valid, but the value specified is
invalid.
keywd - KEYWORD NOT SPECIFIED
The keyword specified is required, but was not found in the
SMF parmlib member.
System Action: Message IEE356A follows, permitting changes
to be made.
Operator Response: None.
IEE356A
REPLY WITH SMF VALUES
Explanation: This message follows message IEE3551, and
permits corrections to be made to the parameters in error.
System Action: SMF initialization will not continue until the
operator has responded to this message.
Operator Response: Enter REPLY
xx,'keywd - val,keywd - val...', correcting the parameters in
error indicated in message IEE3551. Inform the system
programmer to correct the errors in the specification of the
SMF parmlib member.
Problem Determination: Table I, items 2, 7ab, 29. Execute the
IEBPTPCH utility program to list the SMF parmlib member from
SYSl.PARMLlB, and save the output.
8-14
VS2 System Messages (VS2.03.807)
IEE357A
REPLY WITH SMF VALUES OR U.
Explanation: This message follows message IEE3541, and
permits changes to be made to the parameters listed.
System Action: SMF initialization will not continue until the
operator has responded to this message.
Operator Response: If any parameters are to be changed,
enter REPLY xx,'keywd - val,keywd - val ... ', specifying the
changes desired. If parameters are not to be changed, enter
REPLY xx, 'U'.
IEE3581
SMF SYSl.MAN {~} NOT FOUND ON ser
Explanation: The SYS1.MAN data set, as indicated In the
message text, was specified for the device whose volume
serial number is ser. However, no space was allocated for the
data set on that device.
System Action: System operation continues, but no records
are written in the SYS1.MAN data set.
Operator Response: Probable user error. Inform the
programmer responsible for the system either to allocate
space for the data set on the indicated device or to properly
redefine the data set.
Problem Determination: Execute the IEHLlST utility for the
volume and save the output. Table I, items 2, 7ab, 29.
IEE3591
INCOMPATIBLE SMF VALUES FOR OPT AND DSV.
OPT - 2 SUBSTITUTED.
Explanation: The value OPT - 1 is not compatible with the
value DSV - 2 or DSV - 3 for the recording of STEP and/or
VOLUME information for SMF. The value OPT - 2 is required to
create preliminary records needed for the above SMF
information.
System Action: The value OPT - 2 is substituted. Processing
continues and SMF information is recorded.
Programmer Response: Probable user error. If STEP and/or
VOLUME information is not desired, reinitialize the system and
specify SMF parameter value DSV - 0 or DSV - 1.
Problem Determination: List the specified SMF SYSl.PARMLIB
member to verify the parameter defaults specified. The user
may change these defaults in SYS1.PARMLlB, or override them
through the console at system initialization, to conform to his
current SMF requirements.
IEE3601
SMF NOW RECORDING ON SYSl.MAN{X} ON ser
TIME - hh.mm.ss
Y
Explanation: Records are being written in the SYS1.MAN data
set, as indicated in the message text, on the device whose
volume serial number is ser. The message also indicates the
time of day, where hh specifies the hour (00-23), mm
specifies the minute (00-59), and ss specifies the second
(00-59).
System Action: The SMF records are initially placed in a
buffer; when the buffer is full, the data in the buffer is written
in the indicated data set. If the system fails before the buffer
is full, the records are lost.
Operator Response: None.
IEE3611
SMF DATA LOST -- SYSl.MANX/Y NOT AVAILABLE
TIME - hh.mm.ss
Explanation: The SYS1.MANX and SYS1.MANY data sets are
both full. Therefore, no more records can be written. The
message also indicates the time of day, where hh specifies the
hour (00-23), mm specifies the minute (00-59), and 55
specifies the second (00-59).
System Action: System operation continues, but no records
are written in the SYS1.MAN data sets. Until a data set
becomes available, a record is kept of the number of records
lost and of the starting and ending times of the period during
which no records were written. When a data set becomes
available, an SMF data lost record (type 7) is written.
Operator Response: Initiate execution of the IFASMFDP
program. If a dump program is currently executing, ensure that
it completes as soon as possible.
IEE362A
SMF ENTER DUMP FOR SYS 1.MAN {~} ON ser
Explanation: The SYS1.MAN data set, as indicated in the
message text, is full or end-of-day was specified. The data set
is on the device whose volume serial number is ser.
System Action: The system waits for the operator to enter a
DUMP command for the SYS1.MAN data set.
Operator Response: Initiate execution of the IFASMFDP
program for the indicated data set.
IEE3631
SMF
ser NOT DIRECT ACCESS
Explanation: The SYS1.MAN data set cannot be used because
a device other than direct access was specified for the
SYS1.MAN data set. In the message text, ser is the volume
serial number of the volume.
System Action: Processing continues, but no records are
written in the SYS1.MAN data set.
Operator Response: Probable user error. Inform the
programmer responsible for the system to properly define the
device or to make the specified device available.
Problem Determination: Table I, items 2, 7ab, 29.
IEE3641
SMF I/O ERROR ON ser
Explanation: A permanent input/output error has occurred
while writing in the SYS1.MAN data set. ser is the the volume
serial number of the device on which the data set resides.
System Action: If an alternate data set is available, records
will be written on that data set.
Operator Response: Inform the system programmer to define c
different SMF SYS1.MAN data set.
Problem Determination: Table I, items 2, 7ab, 29.
IEE3651
SMF
SYSl.{MAN{~}
}
NOT OPENED
PARMLIB
Explanation: The SYS1.MAN data set or the SYS1.PARMLIB
data set could not be opened. The indicated data set has not
been allocated or mounted properly.
System Action: Processing continues but no records are
written to the SYS1.MAN data set or in the case of
SYS1.PARMlIB, message IEE356A will be issued, permitting
SMF parameters to be entered.
Operator Response: Probable user error. Inform the system
programmer to allocate the indicated data set.
Problem Determination: Table I, items 2, 7ab, 29.
IEE3761
VARY REJECTED, PATH(ddd,x) LAST PATH TO
DEVICE
Explanation: A VARY PATH command requested that the last
path to device ddd, on CPU x, be varied offline. A VARY PATH
with UNCOND command requested that the last path to an
allocated device ddd be varied offline.
System Action: The command is not executed. The system
continues operation.
Operator Response: Probable user error. If ddd does not
indicate the desired path, enter the command again correctly.
The last path to an allocated device cannot be varied offline.
Problem Determination: Table I, items 11, 29.
IEE3781 VARY REJECTED, PATH(ddd,x) DOES NOT EXIST
Explanation: A VARY PATH command requested that a
non-existant path to device ddd on CPU x be varied online or
offline.
System Action: The command is not executed; processing
continues.
Operator Response: Probable user error. If ddd does not
indicate the desired path, enter the command again correctly.
Problem Determination: If ddd does indicate the desired path,
or if the problem recurs, see Table I, items 11, 29.
IEE3791
VARY REJECTED, PATH(ddd,x) RESERVED
Explanation: A VARY PATH command requested that the path
to shared direct access storage device ddd, CPU x, be varied
offline. However, the path is temporarily reserved and cannot
be varied.
System Action: The command is not executed; processing
continues.
Operator Response: Probable user error. If desired, enter the
VARY PATH command again after the shared device has been
released.
Problem Determination: Table I, items 11, 29.
IEE3801
ddd DEVICE TYPE INVALID
Explanation: A SWAP command was entered; however, device
ddd is not supported by dynamic device reconfiguration.
System Action: The command is not executed; processing
continues.
Operator Response: Probable user. error. If a swap is still
desired, reenter the command using a supported device. DDR
supports the following devices:
Tape:
2401, 2415, 2420, 3410, 3411, 3420 (All models)
Disc:
2314, 2319, 3330, 3330 mod 11, 3340/3344,3350
Unit Record:
1403, 1443, 2501, 2520, 2540, 3211, 3505, 3525
Problem Determination: Table I, items 11, 29.
IEE3811
ddd DEVICE UNALLOCATED
Explanation: A SWAP command was entered for device ddd.
However, the device has not been allocated to a job.
Therefore, a swap cannot be performed.
System Action: The command is not executed. The system
continues operation.
Operator Response: Probable user error. If movement of the
volume on device ddd is not desired, none.
If movement of the volume on device ddd is desired, issue a
VARY DEVICE offline command for the device and move the
volume. If the VARY DEVICE command is not executed
successfully, then the device has since been allocated and the
SWAP command can be reentered.
Problem Determination: Table I, items 11, 29.
IEE3821
{!~}
CURRENTLY ACTIVE
Explanation: A command was entered; however, a request is
outstanding.
If TRACE status was issued, and ttt is TRACE, the system
tracing is active.
System Action: The command is not executed.
Operator RespC'!1se: Wait for the outstanding request to
complete. Then, if desired, reenter the command.
Note: Canceling the affected job will purge the outstanding
request.
Problem Determination: Table I, items 11, 29.
Section 8: lEE Messages - Master Scheduler
8-15
•
IEE4001
THESE MESSAGES CANCELLED- XX,XX,XX
Explanation: The operator need not respond to the messages
whose reply identifiers are given by xx. The messages have
been canceled and the requirement for a reply no longer
exists. The messages were canceled because the issuing task
terminated or specifically requested that the message be
canceled.
System Action: The system continues processing. The reply
identifiers may be used to identify some future message.
Operator Response: None.
IEE4501
requested attributes. This message appears as the last line of
the display.
System Action: The command was executed.
Operator Response: None.
IEE4531
UNIT STATUS, INVALID OPERAND. RE-ENTER
Explanation: In the DISPLAY U command, invalid parameters
were specified.
System Action: No display was created.
Operator Response: Enter the command correctly, specifying
valid parameters.
hh.mm.ss UNIT STATUS rid]
UNIT STATUS, DEVICE DOES NOT EXIST
Explanation: In response to a DISPLAY U command, this
IEE4541
message provides a display of the requested information. The
message may appear in either of two formats:
• If OFFLINE is not specified in the DISPLAY U command, the
following headings will appear on the second line of this
message -- UNIT, TYPE (for TP devices, only control unit
will be shown), STATUS, VOLSER, and VOLSTATE. If two or
more units are being described, the headings will appear
twice on the second line. The third line and each
succeeding line, will contain information as described by the
headings.
The following alphabetic characters may appear in the
STATUS field with these meanings:
o - online
S - SYSRES
C - console
A - allocated
BSY - busy
MTP - mount pending
NRD - not ready
R - reserved, shared DASD
• If OFFLINE is specified in the DISPLAY U command, the
following headings appear on the second line -- UNIT and
TYPE. Up to seven units may be described on the third line
and each succeeding line of the display.
rid]
A three-digit decimal identification number. It is used in
conjunction with the CONTROL C,D command for
canceling status displays being written on typewriter or
printer consoles or being displayed in-line (not in a
display area) on a display (CRT) console. This
identification number does not appear when the display
is presented in a display area on a display console.
Note: A MOUNT pending deSignation for a given device
(shown as 'mtp' in the message text) does not indicate that a
volume should be mounted on the device in the following
cases:
• No MOUNT message has yet been issued for the device (in
this case the device will also be designated allocated shown as 'A' in the message text.)
• One or more MOUNT messages were issued for the device
but the job(s) for which the messages were issued has been
canceled.
In the first case no action is necessary because a MOUNT
message mayor may not be issued. In the second case no
action is necessary, but issuing an UNLOAD command to the
device will clear the mount-pending condition.
System Action: Processing continues.
Operator Response: None.
Explanation: In the DISPLAY U command, the Single device
IEE4521
UNIT STATUS NUMBER OF UNITS REQUESTED
EXCEEDS NUMBER AVAILABLE
Explanation: In the DISPLAY U command, the number of
devices specified for which information was to be supplied
exceeded the number of devices in the system with the
8-16
VS2 System Messages (VS2 Release 3.7)
specified did not correspond to any device in the system.
System Action: No display was created.
Operator Response: Enter the command correctly, specifying a
valid device description.
IEE4551
UNIT STATUS, NO DEVICES WITH REQUESTED
ATTRIBUTES
In the DISPLAY U command, attributes were
specified that did not correspond to any devices in the system.
System Action: No display was created.
Operator Response: Enter the command correctly, specifying
valid device descriptions.
Explanation:
IEE479W
MASTER SCHEDULER~[ABEND Cde,]}
REIPL
[FAILED,]
.
[DUMPED,]
Explanation: The master scheduler failed. If ABEND appears in
the message text, cde is the system completion code. If
FAILED appears, the task failed during initialization. The
optional field DUMPED indicates that a complete dump has
been taken to the SYS1.DUMP data set. If DUMPED is omitted,
there is no usable dump.
System Action: The system enters a permanent wait state.
Operator Response: Restart the system.
Programmer Response: If cde appears in the message text,
take the action indicated for that system completion code.
Problem Determination: Table I, items 2 and 29. Print the
SYS1.DUMP data set if DUMPED appeared in the message.
Otherwise, take a stand-alone dump.
IEE4801
iii [COMMAND]
TERMINATED
lABEND cde,
I
[DUMPED,]
FAILED,
iii terminated where iii may be
one of the following:
• The name of the abnormally terminating task.
• The abnormally terminating command, in which case
COMMAND appears in the message text.
• SVC 34, in which case the command scheduler abnormally
terminated. The "ABEND cde" is always issued with SVC
Explanation: The named task,
34.
If ABEND cde appears in the message text, cde is the system
completion code. If FAILED appears, the task failed during
initialization. The optional field DUMPED indicates that a
complete dump has been taken to the SYS1.DUMP data set. If
DUMPED is omitted, there is no usable dump.
System Action: The task is terminated immediately. A record
describing the error is written to' the SYS1.LOGREC data set
and. a dump is attempted.
Programmer Response: .If ABEND cde appears in the message
text, take the action indicated for that system completion
code.
~,
'[
",/
Problem Determination: Table I, items 2, 7d, 16, 29.
IEE506E
IEE4811
Explanation: The master scheduler failed. The cde in the
message text is the system completion code. The optional field
DUMPED indicates that a complete dump has been taken to
the SYSl.DUMP data set. If DUMPED is omitted, there is no
usable dump.
System Action: The task will automatically restart.
Operator Response: None.
Programmer Response: Take the action indicated for the
system completion code.
Problem Determination: Table I, items 2 and 29. Print the
SYSl.DUMP data set if DUMPED appeared in the message.
Otherwise, take a stand-alone dump.
Explanation: During either a Vary CPU or a Vary Channel
command, an attempt was made to reset or restart the
requested CPU using the signal processor instruction. The
subject CPU failed to respond to the request.
System Action: The system continues processing.
Operator Response: Probable user error. Check to see if power
is up on the central processing unit to be varied online, and
check the configuration panel to ensure that the switches are
set correctly. Also, ensure that the correct micro program has
been loaded, i.e., that a diagnostic is not currently active. To
enable channel reconfiguration hardware to operate, the CPU
to which the requested channel is attached must be powered
up, and the configuration control panel must be set to MP
mode.
IEE482E
IEE5101
MASTER SCHEDULER ABEND
cde[DUMPED,]RESTARTING
MASTER SCHEDULER RESTART FAILED,ABEND
RECURSION,REIPL
Explanation: An attempt to restart the master scheduler failed.
This message will always be preceded by this message,
IEE4811.
System Action: The system will continue to process without
the master scheduler.
Operator Response: After current system processing has
stopped, restart the system to restart the master scheduler.
Programmer Response: Respond as indicated to message
IEE481I.
IEE500E
VARY REJECTED, CHANNEL(x,y) NOT OPERATIONAL
Explanation: A test of channel x of central processing unit y
indicated that the channel was not operational.
System Action: The VARY channel online command is not
executed.
Operator Response: Probable user error. Set the channel on
and reenter the VARY command.
IEE5021
CH(x,y) OFFLINE
Explanation: In response to a VARY channel offline command,
channel x of central processing unit y has been marked offline
in the channel table or was already offline.
System Action: Processing continues.
Operator Response: None.
IEE5041
CPU(x) ONLINE
Explanation: In response to a Vary CPU Online command,
central processing unit (CPU) x has been placed online. All
attached channels that are operational are marked online as
well as all operational paths utilizing the new CPU.
System Action: The system continues processing.
Operator Response: None.
IEE5051
STORAGE LOCATIONS
;;;;~WK
1
t
TO
1;::::ZK l
OFFLINE.
uuM
~
vvM
~
Explanation: In response to a VARY storage offline command,
the storage from wwwwwK to xxxxxK has been placed offline.
yyyyyy and zzzzzz are the addresses in hexadecimal. uuM and
vvM are the addresses in decimal megabytes.
System Action: Processing continues.
Operator Response: None.
IEE5121
ddd BUSY
Explanation: A Vary CPU or Channel Offline command has
detected that the I/O activity has not completed on device
ddd.
System Action: The Vary CPU or Vary Channel Offline
processor waits for three minutes maximum for all associated
I/O to complete. This message is issued after 15 seconds if all
associated I/O has not completed, to notify the operator of
busy devices. If the three-minute waiting time expires and all
associated I/O is not complete, message IEE717D is issued.
Operator Response: None.
CH(x,y) ONLINE
Explanation: In response to a VARY channel online command,
channel x of central processing unit y has been placed online
or was already online.
System Action: Processing continues.
Operator Response: None.
IEE5031
VARY CPU REJECTED, CPU DID NOT RESPOND TO
RESET/RESTART
CPU(x) OFFLINE
Explanation: In response to a Vary CPU Offline command,
central processing unit x has been placed offline.
System Action: Processing continues.
Operator Response: None.
IEE5131
COMMAND PROCESSING LIMITED
Explanation: The Command Scheduling Control Block (CSCB)
chain was invalid and was truncated at the last valid block.
This message will always be preceded by the message IEE4811
or message IEE4801.
System Action: The system will continue processing but the
capability to MODIFY, STOP, CANCEL and DISPLAY certain
tasks may be lost and attempts to use them may result in
error messages.
Operator Response: None.
Programmer Response: Respond as indicated to message
IEE4811 or IEE4801.
IEE515E
VARY STOR FAILED, STORAGE PHYSICALLY
REMOVED FROM SYSTEM
Explanation: A VARY STOR command failed because some of
the storage units have been dialed out of the system and
cannot be addressed.
System Action: The command is aborted in the process of
validating storage. The requested storage is placed offline or,
in the case of VARY STOR ONLINE, remains offline. The offline
storage below the unconfigured storage has been cleared and
validated.
Operator Response: Probable user error. If a VARY ONLINE
command was entered, dial the storage range back into the
system and reenter the VARY command. Otherwise, no
response is necessary.
Section -8: lEE Messages - Master Scheduler
8-17
•
IEE5171
VARY STOR REJECTED, INVALID ADDRESS
Explanation: In a VARY STOR command, one of the following
errors was made:
• One or more storage addresses had a syntax error.
• The address range was above the highest range selected at
IPL time.
• The address range was specified in the wrong order.
System Action: The command is rejected; processing
continues.
Operator Response: Probable user error. Enter the command
again correctly.
IEE519E
VARY STOR REJECTED, (startaddr,endaddr) CAUSES
INVALID OVERLAP
Explanation: In a VARY STOR command, the storage
addresses in the text cause an invalid overlap of a previous
offline request which has not yet completed. Possible causes
for invalid overlap are:
• The addresses of a VARY STOR ONLINE command do not
exactly match the addre~ses of a previous offline request
which has yet to complete.
• A VARY STOR OFFLINE command has the same addresses
as a previous offline request which has yet to complete. The
duplicate request is rejected.
System Action: The status of the storage specified remains
unchanged; processing continues.
Operator Response: Probable user error. If the intention is to
cancel the previous VARY OFFLINE command, reenter the
VARY ONLINE command specifying the same addresses as in
the VARY OFFLINE command. Otherwise, wait until the VARY
OFFLINE command completes and reenter the VARY ONLINE
command.
System Action: The command is not executed. The system
continues processing.
Operator Response: Probable user error. Do not enter a VARY
command that eliminates access to the system console or the
hardcopy device if an alternate does not exist. If possible, vary
a device online as a console, with system console authority, on
the other CPU. This allows the object CPU to be varied offline
without loss of the master console.
IEE5281
Explanation: The storage address range specified in a VARY
storage offline command overlaps the permanently resident
storage. This storage includes the nucleus code and its buffers.
System Action: The command is rejected; processing
continues.
Operator Response: Probable user error. Enter the command
again correclty.
IEE5311
class class has failed. Class class is a valid output class.
Because un allocation failure may occur before or after the
system log data set has been queued to an output class, the
status of the data set is unknown.
System Action: Processing continues.
Operator Response: None.
IEE5201
IEE5231
INVALID COMMAND IN ONE CPU SYSTEM
LOG DATA SET UNALLOCATION FAILED TENTATIVE DATA LOSS - CLASS = class
Explanation: An attempt to unallocate a log data set for output
IEE5321
VARY STORAGE OFFLINE CANCELLED DUE TO
SUBSEQUENT ONLINE
Explanation: A VARY STOR offline command has previously
been issued, but had not completed. In response to a VARY
online command for the same block of storage, the VARY
offline command was canceled.
System Action: The VARY STOR offline processing is
terminated and the VARY STOR online processing will attempt
to bring the requested storage online.
Operator Response: None.
VARY STOR REJECTED, REQUEST OVERLAPS
PERMANENTLY RESIDENT STORAGE.
SYSTEM LOG DEFINED AS HARDCOPY - WRITELOG
CLOSE COMMAND REJECTED
Explanation: A WRITELOG CLOSE command was rejected
because the system log is defined as the hardcopy device, and
there are no other hardcopy devices online.
System Action: Processing continues with the current log
active.
Operator Response: In order to close the system log, a
hardcopy device must be varied online, and the WRITELOG
CLOSE command must be reissued.
IEE5331
SYSTEM LOG INITIALIZATION HAS FAILED
Explanation: The command cannot be executed in a
Explanation: Initialization of a system log failed at IPL or via a
partitioned system. The message is also issued if an attempt is
made to remove the only processing unit in multisystem mode.
System Action: The command is not executed; processing
continues.
Operator Response: Probable user error. Enter only commands
valid for systems with one central processing unit.
Problem Determination: Table I, items 2, 11, 29.
WRITELOG START command.
This message will be followed by message IEE0371.
System Action: The system log function is not active.
Operator Response: Respond as indicated by message IEE0371.
IEE5241
Explanation: As a result of an internal or external WRITELOG
command, an alternate LOG data set was scheduled for
allocation or open processing. A failure occurred during the
processing of this data set.
System Action: The system log continues recording WTLs on
the current data set.
Operator Response: If it is not critical that the current log data
set be written out, no response is necessary. If it is critical
that the current log data set be written out, reissue the
WRITELOG command. If this message reappears, issue a
WRITELOG CLOSE command for log termination; after message
IEE0371 appears, issue a WRITELOG START command to
reinitialize the log function.
STORAGE LOCATIONS
;y~;;WK\
TO
l=~Kt
ONLINE.
vvM
~
1uuM
Explanation: In response to a VARY storage online command,
storage from wwwwwK to xxxxxK has been placed online..
yyyyyy and zzzzzz are the addresses in hexadecimal. uuM and
vvM are the addresses in decimal megabytes.
System Action: Processing continues.
Operator Response: None.
IEE527E
VARY COMMAND REJECTED, WOULD REMOVE
ACCESS TO CONSOLE/HARDCOPY
Explanation: To avoid lising access to the system console to
the system console or to hardcopy device, the system ignored
a Vary CPU Offline or Vary Channel Offline command.
8-18
VS2 System Messages (VS2 Release 3.7)
IEE5341
LOG DATA SET SWITCH FAILED - CURRENT LOG
DATA SET RECORDING
IEE5351
em INVALID PARAMETER
Explanation: A parameter on the em command is invalid. If em
is TRACE, an operand other than ON, OFF, STATUS, or NUll
was found.
System Action: The system does not execute the cm
command.
Operator Response: Reenter the cm command correctly.
IEE5361
IPS VALUE val NOW IN EFFECT
Explanation: The IPS (Installation Performance Specifications)
contained in member IEAIPSxx are now governing the system;
xx is the value of the IPS parameter specified on the SET
command.
System Action: The system continues processing under the
new IPS.
Operator Response: None.
IEE5371
IPS IN IEAIPSxx INVALID
Explanation: The SET IPS processor found invalid parameter
specifications in the member IEAIPSxx of SYSl.PARMLlB; the
suffix xx is the value specified in the IPS parameter of the SET
command.
System Action: Processing continues with the existing IPS. IPS
parameter error messages IRA3001 and IRA3011 will be written
to the system log data set.
Operator Response: Report this message to the system
programmer.
Programmer Response: Probable user error. list, check, and
correct the syntax of the IPS parameters in the specified list.
Obtain error information off the system log data set to help
diagnose the error. Ensure that the installation operating
procedure tells the operator what to do if the specified list is
rejected during SET.
Problem Determination: Table I, items 2, 26c, 29.
Operator Response: Probable user error. Make sure that
PARMLIB is mounted. If it is, then there is a probable
hardware failure on initial read.
Problem Determination: Table I, items 2, 30.
IEE541E
VARY COMMAND REJECTED, WOULD REMOVE LAST
PATH TO DEVICE ddd
Explanation: If UNCOND was not specified, any element of the
last path to any online device cannot be varied offline. If
UNCOND was specified, the path represented the last path to
an allocated device. The path cannot be varied until the device
becomes unallocated or another path is made available.
Note: A VARY command that removes the last path to an
allocated device will always be rejected.
System Action: The command is not executed; processing
continues.
Operator Response: If the specified device is unallocated,
specify the UNCOND operand on the command. If UNCOND
was specified, the device is allocated and the CPU specified
represents the last path to the device.
IEE6001
REPLY TO xx IS; text
Explanation: This message notifies all console operators that
received a message request with identification xx that a reply
has been accepted to the message. The first 43 characters of
the accepted reply appear as 'text'. The text mayor may not
be enclosed in quotes depending on whether or not the reply
was enclosed in quotes. The message text will be replaced
with the word SUPPRESSED if the ROUTCDE of the WTOR was
9 (security).
System Action: The system continues processing.
Operator Re~ponse: None.
IEE6991
REPLY xx IGNORED; NON-DECIMAL 10
Explanation: A REPLY xx command was entered specifying a
IEE5381
IEAIPSxx MEMBER NOT FOUND IN SYS1.PARMLIB
Explanation: The SET IPS processor cannot retrieve the IPS in
IEAIPSxx due to the member not found condition; xx is the
number specified in the IPS parameter of the SET command.
System Action: Processing continues with the existing IPS.
Operator Response: Probable user error. Report this message
to the system programmer. Verify that the xx specified on the
command is valid. If desired, reissue the SET command
specifying a different IEAIPSxx member name via the IPS
parameter.
Programmer Response: Ensure that the installation operating
procedures tell the operator whichlEAIPSxx members may be
used.
Problem Determination: Table I, items 2, 25c, 29.
IEE5391
I/O ERROR DURING PROCESSING OF MEMBER
IEAIPSxx OF SYSl.PARMLIB
Explanation: The SET IPS processor cannot retrieve the IPS in
IEAIPSxx member due to a permanent I/O error; xx is the
number specified in the IPS parameter of the SET command.
System Action: Processing continues with the existing IPS.
Operator Response: Probable hardware error. If desired,
re-issue the SET command, specifying a different IEAIPSxx
member name via the IPS parameter.
Problem Determination: Table I, items 2, 30.
non-decimal id. The reply id must be entered as decimal digits
with or without a leading zero in ids 01 through 09.
System Action: The REPLY xx command is ignored. The
system continues processing.
Operator Response: Probable user error. Enter the REPLY
command again correctly.
Problem Determination: Table I, items 2, 29.
IEE7001
Explanation: A REPLY xx command was entered and the reply
text was too long for the user's buffer.
System Action: The REPLY xx command is ignored. The
system continues processing.
Operator Response: Probable user error. Enter the REPLY
command again correctly.
Problem Determination: Table I, items 2, 29.
IEE7011
OPEN FAILED - SYS1.PARMLIB DURING
PROCESSING OF MEMBER IEAIPSxx.
Explanation: The SET IPS Processor could not open PARMLIB
when trying to process member IEAIPSxx.
System Action: Processing continues with the existing IPS.
REPLY xx IGNORED; NO REPLIES OUTSTANDING
Explanation: REPLY xx was entered when a reply was not
being requested.
System Action: The unexpected REPLY xx was ignored. The
system continues processing.
.
Operator Response: None.
IEE7021
IEE5401
REPLY xx IGNORED; REPLY TOO LONG FOR
REQUESTOR
REPLY xx IGNORED; IMPROPER USE OF DELIMITERS
Explanation: REPLY xx was invalid for one of:the following
reasons:
• A closing apostrophe did not follow the text when the text
was preceded by an apostrophe.
Section 8: lEE Messages - Master Scheduler
8-19
I
• An invalid character (a character other than a comma,
space, or EOB) followed the id.
System Action: Thl REPLY xx was ignored. The system
continues processing.
Operator Response: Probable user error. Enter the REPLY
command again correctly.
Problem Determination: Table I, items 2, 29.
IEE7031
REPLY xx NOT REQUESTED FROM THIS CONSOLE
Explanation: A REPLY xx command was entered by a
secondary console in response to a message that the console
did not receive.
System Action: The REPLY xx command is ignored. The
system continues processing.
Operator Response: Probable user error. Enter the command
again from the master console or from a console that received
the message.
Problem Determination: Table I, items 2, 29.
IEE7041
REPLY xx NOT OUTSTANDING
Explanation: A REPLY xx command was entered; however,
there is no outstanding reply request with the identification xx.
Either the message request has already been answered or the
message reply identification xx is incorrect.
System Action: The REPLY xx command is ignored. The
system continues processing.
Operator Response: Probable user error. If the reply
identification was incorrect, enter the command again
correctly.
Problem Determination: Table I, items 2, 29.
IEE7061
~SWITCHt
1HALT
NOT SUCCESSFUL
5
Explanation: One of the following occurred:
• The SWITCH SMF command was entered in a system not
supporting SMF.
• The SWITCH SMF or the HALT EOD command was entered
while the SMF recording data sets were being switched or
while there was no SMF data set available.
System Action: The command was not executed.
Operator Response: Reenter the command as soon as the data
set switch has completed.
Problem Determination: Table I, items 2, 7ab, 29.
IEE7071
em yyy NOT EXECUTED
Explanation: The command indicated by cm in the message
text could not be performed by the system for one of the
following reasons:
• The subsystem resources are in use.
• The subsystem buffers are filled.
In the message text, yyyis the parameter field. (cm+yyy will
not exceed 8 characters.)
System Action: The system did not execute the command
(cm).
Operator Response: Enter the command (cm) again when the
previously entered subsystem commands have completed
execution.
Problem Determination: Table I, items 2, 29.
IEE7081
keywd KEYWORD, VALUE INVALID
Explanation: The value of keyword keywd was unacceptable to
the system. Example: The performance group number specified
on the PERFORM keyword is not defined to the system
resource manager.
System Action: No change is made in the performance group
for the job specified on the command.
8-20
VS2 System Messages (VS2 Release 3.7)
Operator Response: Probable user error. Reenter the
command, specifying a performance group number that is
defined.
Problem Determination: Table I, items 2, 29. List the IPS
member of SYS1.PARMLIB under which the system is running.
IEE7091
HARDCOPY REQUIRED - NO HARDCOPY DEVICE
AVAILABLE
Explanation: This message warns that the system is in
'hardcopy is mandatory' mode and that there is no SYSLOG or
paper device to make into hardcopy; however, the operator
has added a new console to the system configuration.
System Action: Processing continues.
Operator Response: Do one of the following:
• Make sure that the system log is available, then issue a
VARY SYSLOG,HARDCPY command to function as the
hardcopy device.
• Enter a VARY CONSOLE command to bring an input! output
or output only paper (non-graphics) console online as the
active console. This device will automatically be assigned
the hardcopy function.
Note: There is no need to use the VARY HARDCPY
command unless you want to change the hardcopy authority
and rout codes.
IEE7101
~ddd
t
NOW RECEIVING HARDCOPY
1SYSLOG5
Explanation: The system does not have an active hardcopy
device, however, the addition of a console to the system
console configuration makes hardcopy mandatory. Either ddd
or SYSLOG has been forced by the system to act as the
hardcopy device.
System Action: Processing continues.
Operator Response: If device ddd is not desired as the current
hardcopy log do one of the following:
• Make sure that the system log is available, then issue a
VARY SYSLOG,HARDCPY command to switch the hardcopy
function to SYSLOG.
• Enter a VARY CONSOLE command to bring an input! output
or output only paper (non-graphics) console online as the
active console. Then enter a VARY HARDCPY command to
assign this console the hardcopy status.
• If hardcopy is not desired, make sure that there is only one
paper console and no graphics consoles functioning on the
system and then enter a VARY HARDCPY,OFF command to
terminate the hardcopy function.
IEE7111
SYSTEM UNABLE TO DUMP
Explanation: SVC Dump could not complete the dump to the
SYS1.DUMP data set. The system was unable to dump or a
partial dump was taken. SVC Dump may have been processing
another dump at the time the command was issued.
System Action: Processing continues.
Operator Response: Enter the dump command again.
IEE7121
em PROCESSING COMPLETE
Explanation: System processing for the cm command has
completed successfully. If cm is CHNGDUMP, one of the
following has been accomplished:
• The dump defaults for SYSABEND or SYSUDUMP DD's
specified in SYSl.PARMLIB were temporarily overridden by
the CHNGDUMP command; or, the dump options specified
when a system task issues the SDUMP macro are
temporarily overridden by the CHNGDUMP command.
• The overrides specified by a previous issuance of the
CHNGDUMP command have been eliminated.
")
If cm is TRACE, and the command issued was TRACE ON, the
Master Scheduler will retain system tracing after job entry
subsystem initialization. If the command was TRACE OFF, the
Master Scheduler will terminate system tracing after subsystem
initialization. In either case, no system ~ction is taken if the
command is issued after subsystem initialization.
System Action: The system has executed the command.
Operator Response: None.
Problem Determination: Table I, items 2, 29.
IEE7131
cm COMMAND PROCESSOR FAILED [-ISSUE K
E,D,L = cca TO DELETE]
Explanation: While processing a cm command an
unrecoverable internal error occurred.
System Action: The command processor terminates. The
system attempts to record the error status in SYSl.LOGREC
and to dump a copy of the main work area to SYSl.OUMPnn;
processing continues.
Operator Response: Retry the command. If the command
continues. to fail, seek system programming support. If cm is
TRACK, issue K E,O,L = cca (where cc identifies the command
on which TRACK was processing and a is the area owned by
TRACK) to erase the display, if desired.
Problem Determination: Print the SYSl.0UMP data set to
obtain a copy of the program workarea. Table I, items 2, 18,
29.
IEE7141
PATH(ddd,x) NOT OPERATIONAL
Explanation: A VARY PATH command requested that path ddd
on CPU x be placed online. The path has been found to be not
operational. The path is not brought online.
System Action: Processing continues; the requested path is
not brought online.
Operator Response: Insure that the requested path is
operational, that power is up on the device and that all
switches are enabled; then retry command.
Problem Determination: Table I, items 11, 24, 29, or 30.
IEE7151
cm COMMAND REJECTED, INVALID SYNTAX
Explanation: In a cm command, the operand field had a syntax
error. Either there was an illegal or missing delimiter, or a
keyword was misspelled.
System Action: The command is rejected; processing
continues.
Operator Response: Probable user error. Reenter the command
correctly.
IEE7181
IEE718D
System Action: The VARY CPU command processor waits for
the operator to reply. Processing continues while the command
processor waits for the reply.
Operator Response: If the CPU must be taken offline
immediately, reply 'YES'. This will prevent any new jobs from
being scheduled with affinity to the object CPU. Then either
wait for the already scheduled jobs to complete or cancel
them. In either case, after the jobs have completed, the VARY
CPU,OFFLINE command can be issued again to take the CPU
offline.
Note: If, after replying 'YES', you decide that you no longer
wish to remove the CPU from the system, enter a VARY
CPU,ONLINE command to make the object CPU available for
job scheduling.
If the CPU does not need to be removed from the system
after receiving messages IEE7181 and IEE7180, reply 'NO' to
message IEE7180. This will cause the VARY CPU,OFFLINE
command to be terminated. The object CPU will remain
available for job scheduling.
IEE7191
ddd BUSY, REPLY EXTEND OR CANCEL
Explanation: Vary CPU or Vary Channel command processor
waited three minutes for all associated I/O to complete on
specified channel(s). The I/O activity has not completed.
System Action: Command processor waits for a reply from the
operator. Meanwhile the system continues processing.
Operator Response: Respond with one of the following:
• EXTEND - The command processor waits another
three-minute interval for I/O to complete. If the I/O is not
complete at the end of the time period, the command
processor reissues this message.
• CANCEL - The system cancels this VARY command,
restores itself to the status at the time the command
processor was invoked and continues processing.
VARY COMMAND REJECTED, OUTSTANDING
RESERVE TO DEVICE ddd
Explanation: A VARY CPU or CHANNEL OFFLINE command has
been rejected because the CPU or channel represents the path
on which there is currently an outstanding reserve to a shared
direct access device. If the CPU or channel was removed, a
release would never be issued.
System Action: The VARY OFFLINE command is not executed.
Processing continues.
Operator Response: Retry the VARY OFFLINE command.
IEE7201
NO PFK ALLOCATION
Explanation: The operator has entered the CONTROL
command with either the N,PFK; O,PFK; or E,PFK operand
when PFK support has not been included in the system.
System Action: The command is not exeucted.
Operator Response: Check with the system analyst or the
system programmer to make sure that PFK support has been
included in the system during system generation.
Problem Determination: Execute the AMASPZAP service aid
program to dump load module IEEPFKEY from SYSl.OCMLlB
and save the output. Table I, item 29.
IEE7211
IEE717D
nnn JOBS SCHEDULED WITH AFFINITY TO CPU x
SHOULD CPU BE UNAVAILABLE FOR JOB
SCHEDULING? REPLY YES OR NO.
PFK nnn NOT SUPPORTED
Explanation: The operator pressed PFK nnn (or selected
displayed number nnn from the PFK display line with the light
pen) for which support had not been requested at system
generation.
System Action: Processing continues.
Operator Response: Retry the operation. Check the PFK
specification for correctness. If the problem recurs, do the
following before calling for IBM support:
• Issue 0 PFK command from the console.
• Have the hardcopy printout available.
IEE7221
PFK nnn NOT DEFINED
Explanation: This message indicates that the operator has
pressed PFK key nnn or positioned the light pen over PFK key
number nnn, and either of the following conditions occurred:
• The selected key has no commands defined for it.
• A zero length command is contained within the key
definition.
System Action: Processing continues.
Section 8: lEE Messages - Master Scheduler
8-21
•
Operator Response: Use the DISPLAY PFK command to
IEE751E
request a display of the commands associated with the PFK
keys. If the selected key is undefined, select another key or
use the CONTROL N,PFK command to define commands for
the key. If the selected key is defined, check the command
syntax. A semi-colon incorrectly located immediately behind
the first quote or immediately in front of the last quote, or two
semi-colons together within the command, can cause a zero
length indication.
Problem Determination: Table I, items 2, 29.
Explanation: A system error was encountered during quiesce.
System Action: The command is not executed. Processing
IEE7231
PFKIN PROCESS. LAST INTERRUPT IGNORED
SYSTEM ERROR ENCOUNTERED DURING QUIESCE
continues.
Operator Response: Reissue the command.
Problem Determination: Format the SYS1.DUMPnn data set to
obtain a copy of the main workarea. Table I, items 2, 18, 29,
IEE7521
QUIESCE WAS SUCCESSFUL
Explanation: QUIESCE executed successfully.
System Action: Processing continues.
Operator Response: None.
Explanation: The operator pressed a nonconversational PFK
(or selected a nonconversational PFK number with the light
pen) and then pressed a second PFK (or selected a second
PFK number) before processing of the first request was
complete.
System Action: The system does not recognize the second
request. This message is displayed in the instruction line until
processing of the first request is complete; then it is removed.
Operator Response: Wait until the message is removed from
the instruction line, then reenter the second request.
Problem Determination: Table I, items 2, 29.
IEE7241
hh.mm.ss PFK DEFINITIONS [Id]
KEY# CONY DEFINITIONS
nnn stat xxx
Explanation: This message is displayed on a CRT console in
response to a DISPLAY PFK command~ It provides' a display of
the operator commands associated with each PFK key.
In the label line KEY # refers to the number of the PFK key (or
displayed PFK key number), CON refers to conversational
mode, and DEFINITION refers to the current definition of the
key.
In the message text the fields are:
hh.mm.ss
The time of day, where hh specifies the hour (00-24), mm
specifies the minute (00-59), and ss specifies the second
(00-59).
rid]
A three-digit decimal identification number. It is used in
conjunction with the CONTROL C,D command for canceling
status displays being written on typewriter or printer
consoles or being displayed in-line on a display (CRT)
console.
nnn
The number of the key whose definition is displayed on this
line.
stat
The status of the conversational mode: YES, if
conversational mode is in effect; NO, if conversational mode
is not in effect; and blank, if the key is not defined.
xxx
The current definition for the key. This field can contain up
to 108 characters or 52 key numbers separated by
commas; this field will be continued on a second line, if
necessary. If the key is not defined, this field contains NOT
DEFINED.
Operator Response: None.
IEE7341
ddd NOW UNLOADED
IEE7531
QUIESCE UNSUCCESSFUL (rc)
Explanation: A QUIESCE command was entered, but an
abnormal condition has occurred. In the message text, rc is
the reason code.
The values of rc and their meanings are' as follows:
rc
Meaning
04
The stop and restart subroutine, IEESTPRS, was
unable to stop the system because one of the CPU's
was disabled for machine check interrupts at each of
two separate status inspections.
'
08
Subroutine IEESTPRS was unable to stop the system
because one of the online CPU's was in a check stop
state when the subroutine issued a SIGP SENSE
instruction to it.
An error return code was received from the
12
interprocessor services routine (IPC) when subroutine
IEESTPRS requested a direct signal to another CPU.
16
An unexpected event in the stop and restart
subroutine, IEESTPRS, resulted in that subroutine's
fuctional recovery routine gaining control.
20
The interrupt handler subroutine for the stop and
restart subroutine, IEESTPRS, encountered an
unexpected return code when it issued SIGP restart to
a CPU.
System Action: The system action depends on the value of rc:
04
The command is not executed. Processing continues,
and any CPU's that have been stopped are restarted.
08
The system restarts CPU's that were placed in the
manual state prior to the time an online CPU was
found in the check stop state. The command is not
executed and processing continues.
12
The system restarts CPU's placed in the manual state
prior to the time an error return code was received
from the IPC routine.
'
16
All online CPU's are started or restarted, so that the
system is restored as near as possible to it's state
prior to the attempted quiesce.
20
The system continues processing with the loss of the
CPU that failed on SIGP restart.
Operator Response: The proper response depends on the value
of rc indicated in the message text:
04
Reissue the command.
08
Reissue the command.
Reissue the command.
12
Reissue the command.
16
20
Reissue the command. Do not press the RESTART key
on the failing CPU as the results are unpredictable.
Problem Determination: Table I, items 2, 29.
Explanation: In response to an UNLOAD command, the system
has unloaded a volume from device ddd,
System Action: Processing continues.
Operator Response: None.
Problem Determination: Table I, items 2, 7a, 29.
8-22
VS2 System Messages (VS2 Release 3.7)
NOT ALL DEVICES BROUGHT ONLINE WITH
CPU/CHANNEL
Explanation: In response to a VARY CPU or CHANNEL
IEE7541
command, the CPU or channel was brought online. However,
not all the devices attached to that CPU or channel were
brought online automatically.
System Action: The system continues processing normally. The
object CPU or channel is online; however, not a" attached
devices were brought online.
Operator Response: Insure that power is up on a" required
devices and that the meter switches are enabled. Devices
which are sysgened by non-existant may cause this message
during the first VARY after IPL.
IEE7551
VARY COMMAND SMF RECORD ERROR
Explanation: During processing of a VARY CPU, VARY
CHANNEL or VARY PATH command, an error was encountered
in writing SMF records recording the CPU, channels and
devices brought online or taken offline. This is an informational
message informing the operator that the SMF data for his
installation is in error for this reconfiguration.
System Action: The reconfiguration requested is performed;
processing continues.
Operator Response: If required, inform appropriate personnel
of the time and place the error occurred in SMF data.
IEE7561
VARY COMMAND CANCELED BY OPERATOR
Explanation: During a VARY CPU or VARY CHANNEL OFFLINE
command, I/O was not able to be quiesced on devices
attached to that CPU or channel, or jobs were found with
affinity to the subject CPU and the operator requested to
cancel the command.
System Action: The VARY command is not executed.
Processing continues in the state previous to the issuance of
the command.
Operator Response: None.
IEE7571
VARY CPU REJECTED, CLOCKS CANNOT BE
SYNCHRONIZED.
Explanation: In response to a VARY CPU ONLINE command,
an attempt was made to bring the object CPU into the system.
However, a synchronization check on the object CPU's clocks
revealed that they could not be synchronized with the good
CPU.
System Action: The VARY command is rejected. No
reconfiguration is performed. The system continues processing
normally in the state previous to the issuance of the command.
Operator Response: Retry the VARY command. If the problem
persists, notify the system programmer.
IEE7581
VARY CPU REJECTED, MACHINE CHECK ON
TARGET CPU.
Explanation: While attempting to bring a CPU into the
configuration in response to a VARY CPU, ONLINE command, a
machine check occurred on the object CPU.
System Action: The VARY CPU command is rejected. No
reconfiguration is performed. The system continues processing
normally in the state previous to be issuance of the command.
Operator Response: Retry the VARY command.
Problem Determination: Table I, item 29.
IEE7591
VARY CPU REJECTED, WOULD RESULT IN A NO
CLOCK CONDITION.
Explanation: In response to a VARY CPU,OFFLINE command,
an attempt was made to take the object CPU offline. However
it was determined that the only good clocks for the installation
were the clocks on the object CPU. Therefore, the CPU was
not taken offline.
System Action: The VARY CPU command is not executed. No
reconfiguration takes place. The system continues processing
normally in the state previous to issuance of the command.
Operator Response: Retry the operation.
IEE760E
cm COMMAND REJECTED, STORAGE NOT
AVAILABLE
Explanation: In a cm command, no storage was available for
an internal work area.
System Action: The command processing is terminated and a"
resources are freed; processing continues.
Operator Response: Try the command again when more
storage is available.
IEE7611
CPU x OFFLINE WITH UNKNOWN STATUS
Explanation: The object CPU in a VARY CPU,OFFLINE
command has gone offline. However, the exact status of the
offline CPU cannot be determined. This could have been
caused by a machine check on the object CPU after it has
been marked offline. The situation is not critical.
System Action: Processing continues.
Operator Response: None.
IEE7621
VARY COMMAND TERMINATED DUE TO SYSTEM
RECOVERY
Explanation: During a VARY CPU or CHANNEL command, a
failure occurred which resulted in a processor being removed
from the sys~em. The VARY command was not permitted.
System Action: The system is automatically reconfigured due
to ACR. Processing continues.
Operator Response: Determine the status of the system and if
the VARY function is still required, reenter the VARY command.
IEE7631
VARY CHANNEL COMMAND REJECTED, CPU
OFFLINE
Explanation: In response to a VARY CHANNEL command, it
was determined that the CPU specified was offline, and one of
the following conditions applies:
• Not a model 168 MP system.
• System not sysgened for CRH support.
System Action: The command was not executed. Processing
continues.
Operator Response: The CPU to which the channel is attached
must be online before a VARY CHANNEL command can be
performed unless CRH hardware and software ·support is
provided.
IEE7641
VARY STORAGE OFFLINE WAITING TO COMPLETE.
Explanation: In response to a VARY STOR OFFLINE command,
all the requested storage could not be placed offline
immediately.
System Action: The system has made this storage unavailable
for allocation and will wait for storage to be released so it may
mark it offline. Processing continues.
Operator Response: If the VARY STaR OFFLINE request has
not completed in a few minutes than display the status of
storage by entering a D M = STaR command. The offline
request may be canceled at any time by entering a VARY
STOR ONLINE command with the same address range as
specified on the offline request.
IEE765D
ENTER OPTION FOR VARY ONLINE. SELECT 0,1, OR
2.
Explanation: In response to a VARY STaR ONLINE command,
the entire range of storage cannot be brought online because
of one or more storage errors. The page frames with errors
Section 8: lEE Messages - Master Scheduler
8-23
•
are reported in the preceding messages, IGF9711 and IEE7661.
System Action: The command processor waits for the operator
to reply.
Operator Response: Select one of the following:
o Bring online the good storage and the storage which is
scheduled to go offline due to a previous storage error.
Currently failing storage is left offline.
1 Bring online only the good storage. Storage scheduled to go
offline due to a previous error and currently failing storage
are left offline.
2 Cancel online request. Do not bring any storage online.
IEE7661
BAD STORAGE AT
VALIDATED.
{XXXXXK}
yyyyyy
CAN NOT BE
Explanation: The 4K page frame at xxxxxK is scheduled to go
offline due to a previous storage error and cannot be validated
until the page frame is released and placed offline. yyyyyy is
the address in hexadecimal.
System Action: The command processor continues processing.
Operator Response: Respond to message IEE765D to inform
the command processor if online processing should continue.
The page will be brought online without validating if the reply
to message IEE765D is O.
IEE7671
hh.mm.ss
STORAGE SIZE lid]
HIGH REAL STORAGE ADDRESS IS xxxxxK
Explanation: In response to a 0 M command requesting the
high address, this message indicates the highest possible real
address for the system. In the message text, the decimal K
address xxxxxK indicates either the highest real address or the
highest potential address specified at system generation time,
whichever is larger. The lid] is the CONTROL message
identifier and appears only if first message of 0 M text.
System Action: Processing continues.
Operator Response: None.
IEE7681
hh.mm.ss OFFLINE STORAGE BLOCKS lid]
c xxxxxK - yyyyyK
NO STORAGE OFFLINE
NO RECONFIGURABLE STORAGE UNITS DEFINED
Explanation: In response to a DISPLAY M comm"nd requesting
storage status, the blocks of real storage offline or pending to
go offline are displayed. Reconfigurable storage units (RSU)
are also displayed. An RSU is a storage box (either online or
offline) that contains no long-term fixed pages and can thus
be reconfigured with the Vary Storage command. In the
message text the first line appears once and the second line
appears for each block of storage that is offline or pending to
go offline. If no storage is offline, just the first and third
messages are printed. If there are no RSUs the fourth line is
also printed.
c
status of storage block
Offline.
p
Pending to go offline.
R
Reconfigurable storage range:
xxxxxK Starting address in real storage of the storage
block.
yyyyyK Ending address in real storage of the storage block.
[id]
CONTROL message identifier. Appears only in first
line of message text.
System Action: Processing continues.
Operator Response: None.
o
IEE7691
SYSTEM ERROR IN SYSTEM LOG
Explanation: This message is issued under one of the following
conditions:
8-24
VS2 System Messages (VS2 Release 3.7)
• A recursive ABEND has occurred in the log task.
• An ABEND occurred during processing of the log STAE
routine.
System Action: The log is set inactive and clean-up of the log
task is performed. The log function is placed in a wait state.
Operator Response: If the log is required for this IPL, attempt
to reactivate it by issuing the WRITELOG START command. If
this message recurs, notify the system programmer.
Problem Determination: Table I, items 2, and 29.
IEE770W
ATTEMPTED EXECUTION OF DELETED MP MODULE
Explanation: This message is associated with system wait state
code 01A. An attempt was made to execute multiprocessing
modules not included in the nucleus when the system was
generated. The multiprocessing modules were not included as
a result of specifying the parameter ACRCODE = NO on the
CTRLPROG system generation macro. The error condition
causing this wait state (only for a system generated with a
subset of multiprocessing code deleted) is that a system error
caused an incorrect attempt to execute the deleted modules.
System Action: The system enters a disabled wait state.
Operator Response: Probable system error. Notify the system
programmer of this message and wait state code.
Problem Determination: Table I, items 11, 29.
IEE7711
VARY CPU REJECTED, WOULD REMOVE LAST CPU
Explanation: This message is issued if an attempt is made to
remove the only remaining central processing unit in an MP
system.
System Action: The command is not executed; processing
continues.
Operator Response: A CPU may have been marked unavailable
for job scheduling by replying 'YES' to message IEE718D
during a VARY CPU offline command. If it is desired to restore
the CPU tei available state, issue a VARY CPU online
command.
IEE7721
CPU (x) UNAVAILABLE FOR AFFINITY SCHEDULING
Explanation: While attempting to vary a CPU offline, programs
were found with affinity to the subject CPU. The operator has
requested that the CPU be marked available for starting any
new steps with affinity to the subject CPU.
System Action: Any programs currently running with affinity to
the subject CPU will complete. Any jobs not requiring affinity
to the subject CPU will be processed normally; however, any
job, with the first job step requesting affinity to the subject
CPU, will not be initiated until the subject CPU is marked
available again. Any job with other than the first job step
requesting affinity to the subject CPU will be failed.
Operator Response: The CPU may be varied offline by
reissuing the VARY CPU offline command. The CPU may be
made available for affinity scheduling by issuing a VARY CPU
online command.
IEE7731
VARY TERMINATED, CHANNEL RECONFIGURATION
HARDWARE NOT ACTIVATED
Explanation: In response to a Vary channel online command
fo, a channel attached to an offline CPU, an unsucessful
attempt was made to activate the channel reconfiguration
hardware of the Model 168 MP system.
System Action: The system continues processing. The
requested function was not performed.
Operator Response: Retry the operation. Of still unable to
activate the channel reconfiguration hardware, notify the IBM
program support representative. The problem is probably a
programe error, and not a hardware error.
(1I,,~
IEE7741
3851 NOT CONFIGURED FOR MP OPERATION
RC = XXX
Explanation: In response to a Vary CPU Online command or a
Vary Channel Online command for a channel attached to an
offline Model 168, MSS was informed that the new processor
will be operating in MP mode. The command was rejected by
MSS. RC = XXX is the return code issued by MSS to the
request.
System Action: The CPU or channel is brought online and
normal processing continues. If an attempt is made to access
a volume within MSS via a path from the new'- CPU or channel,
the request is rejected by the MSS.
Operator Response: Probable user error. MSS must have all
possible configurations defined during the table create
definition. Notify your system programmer.
IEE7751
STORAGE UNAVAILABLE FOR SYSTEM LOG
BUFFER-LOG CLOSE IN PROCESS
Explanation: A request for main storage in CSA via a
BLDCPOOL macro instruction was rejected. A possible cause
may be a program in a WTL macro loop.
System Action: The system log is closed to allow log buffers
to be freed. System processing continues. This message will be
followed by message IEE0431 and IEE0371.
Operator Response: Notify the system programmer. If the
system log was the hardcopy device, hardcopy will now be
directed to the master console (if a paper console). This
output may be stopped by entering a VARY hardcopy OFF
command. If message· IEE1471 appears repeatedly with the
same text, this would indicate a WTL loop problem. If a
problem program is issuing the WTL, cancel the job.
After message IEE0371 is issued, the system log may be made
active via a WRITELOG START command and hardcopy may be
assigned to it via a VARY command.
Problem Determination: Table I, items 2, 3, 4, 11, 13, 16, 29.
IEE7771
cm
INVALID FROM SUBSYSTEM CONSOLE
Explanation: The cm command was issued from a subsystem
console but the issuing sub-system console cannot support
this command.
System Action: The system did not execute the command.
Operator Response: Probable user error. If the function
performed by cm command is desired, issue the equivalent
subsystem command or issue cm command from a system
console.
Problem Determination: See Table 1, items 2, 29.
IEE7791
VARY xxx-yyy RANGE INVALID
Explanation: The system detected an error in a VARY
command that specified a range of unit addresses (xxx-yyy);
the address yyy is lower than the address specified by xxx.
Example:
V 250-235,ONLINE
System Action: The system did not execute the command.
Operator Response: Probable user error. Reenter the Vary
Range command with yyy address higher than or equal to xxx
address.
Problem Determination: Table 1, items 2, 29.
IEE7801
PATH (DD,X) INCOMPLETE
Explanation: A Vary Path command requested that path DOD
on CPU X be placed online. The path was marked online;
however another element of the path is currently offline (i.e.
channel).
System Action: The system continues operation. The path was
marked online, but will not be used until the channel is brought
online.
Operator Response: Use the Display Matrix command to
determine which element of the path to the requested device
is offline. Vary commands may then be issued for these
elements.
IEE7811
PAGEADD COMMAND - UNABLE TO PROCESS DUE
TO ERROR AT IPL
Explanation: During IPL, lists of active page and swap data
sets were unable to be built, and message ILR0041 or ILR0211
was issued as a result of the problem. Without the lists, the
"PAGEADD command is unable to determine if the data set
names in the command stream are unique.
System Action: The PAGEADD command is failed, and will
continue to fail when issued during the current IPL.
Operator Response: Do not issue the PAGEADD command
during this IPL.
IEE7821
PAGEADD COMMAND dsn {PAGE}
DATA SET
SWAP
ALREADY IN USE BY SYSTEM
'
NOT CATALOGED
INSUFFICIENT STORAGE TO PROCESS THIS DATA
SET
VOLUME NOT MOUNTED - DATA SET WILL NOT BE
{
PROCESSED
.
HAS AN INVALID DEVICE TYPE
ALREADY IN USE BY SYSTEM
Explanation: The PAGEADD command requested that data set
dsn be added to the system page/swap data sets. However,
data set dsn is already being used as a page/swap data set.
System Action: The PAGEADD command continues processing.
Operator Response: If the data set name was entered
incorrectly, reissue the command specifying the correct data
set name.
NOT CATALOGED
Explanation: The PAGEADD command was unable to add data
set dsn to the system because data set dsn was not cataloged.
System Action: The, PAGEADD command continues processing.
Operator Response: To add data set dsn as a page/swap data
set, run the AMS define utility to create a page/swap space.
Then, reissue the command.
INSUFFICIENT STORAGE TO PROCESS THIS DATA SET
Explanation: While attempting to add page/swap data set dsn,
the PAGEADD command was unable to obtain enough SQA to
build the control blocks needed for the data set.
System Action: The PAGEADD command continues processing.
Operator Respones: Reissue the PAGEADD command. If the
problem persists, increase the size of the SQA at the next IPL.
VOLUME NOT MOUNTED - DATA SET WILL NOT BE
PROCESSED
Explanation: The PAGEADD command was unable to open the
page/swap data set dsn because the volume containing the
data set was not mounted.
System Action: The PAGEADD commmand continues
processing.
Operator Response: Mount the requested volume, and reissue
the command.
HAS AN INVALID DEVICE TYPE
Explanation: During PAGEADD processing, it was determined
that data set dsn resides on a volume of a device type which
is not supported for page/swap data sets.
System Action: The PAGEADD command continues processing.
Section 8: lEE Messages - Master Scheduler
8-25
•
VS2.03.807
Operator Response: Inform the system programmer that a
problem occurred in the ASM control blocks or code.
Programmer Response: This situation should not occur. If it
does occur, it is indicative of a problem in the ASM control
blocks or code. Verify that module ILRPGEXP and the VSAM
catalog entries for the page and swap data sets have not been
altered erroneously.
Problem Determination: Table I, items 2, 8.
IEE7831
PAGEADD COMMAND dsn {PAGE}
DATA SET
SWAP
NOW AVAILABLE FOR SYSTEM USE
Explanation: The PAGEADD command processing for the
page/swap data set dsn is complete.
System Action: The PAGEADD command continues processing.
Operator Response: None.
IEE7841
PAGEADD COMMAND dsn {PAGE}
DATA SET
SWAP
LENGTH OF DATA SET NAME GREATER THAN 44
OR NULL
Explanation: In the PAGEADD command, the length of the
• If the error was during READ or GETMAIN, it may be
possible to reenter the command with no errors.
• If the error was during WRITE, the quick/warm start data is
probably unusable. If a quick/warm start is to be attempted
in spite of a WRITE error, do not attempt to use the
PAGEADD command again for a page data set, since no
further attempts to update the quick/warm start data will be
made by PAGEADD.
System Action: The PAGEADD command will continue or fail
after a response to message IEE787 A, which follows this
message.
Operator Response: Respond to message IEE787 A, which
follows this message:
• To keep quick/warm start capability:
- For READ and GETMAIN, enter REPLY xx, 'END' ,and
enter the command again. If the command still fails, do
not enter REPLY xx, 'U'.
- For WRITE, enter REPLY xx, 'END', and do not enter the
PAGEADD command again.
• To continue PAGEADD processing:
- Enter REPLY xx, 'U'. This reply will destroy all quick/warm
start capability.
IEE787A
PAGEADD COMMAND - REPLY U OR END
Explanation: This message is issued following message
page/swap data set name dsn is zero or greater than 44
characters.
System Action: The PAGEADD command continues processing.
Operator Response: Probable _user error. Reissue the
PAGEADD command, specifying the correct data set name.
Multiple names should be separated by single commas.
IEE7861.
System Action: The PAGEADD continues after REPLY xx, 'U',
and fails after REPLY xx, 'END'.
Operator Response: Enter REPLY xx, 'U' to continue, or REPLY
xx, 'END' to fail the PAGEADD command.
IEE7851
IEE788A
PAGEADD COMMAND MAXIMUM NUMBER OF
PAGE}
{ SWAP
DATA SETS
FOR THIS IPL IN USE
REMAINDER OF COMMAND WILL NOT BE
PROCESSED
Explanation: 4n the PAGEADD command, the maximum number
of page/swap data sets that can be added during one IPL
have been added. The number is determined by the PAGNUM
system parameter which was specified at IPL.
If this message occurred for page data sets, it may still be
possible to add swap data sets. If this message occurred for
swap data sets, it may still be possible to add page data sets.
System Action: The PAGEADD command is terminated.
Operator Response: If more page/swap space is needed, it
may be acquired at the next IPL by either of the following:
• Specify more page/swap data sets on the PAGE and SWAP
system parameters.
• Increase the number of page/swap data sets which may be
added to the system on the PAGNUM system parameter.
IEE7861
PAGEADD COMMAND READ
} ERROR FOR QUICK/WARM START DATA
WRITE
{ GETMAIN
CONTINUE PAGEADD OR KEEP QUICK/WARM
START CAPABILITY FOR NEXT IPL
Explanation: The PAGEADD command encountered an error
while attempting to read, write, or obtain storage for
quick/warm start data (ILRTPARB). ILRTPARB contains
information about in-use page data sets, and must be updated
when adding a page data set if the next IPL is to be a quick or
warm start. The status of the quick/warm start data is
unknown at this time, but it may still be possible to
quick/warm start.
8-25.0
VS2 System Messages (VS2.03.813)
PAGEADD COMMAND - INVALID REPLY - REPLY U
OR END
Explanation: The reply entered in response to message
IEE787 A was invalid. The only acceptable replies are U and
END.
System Action: The PAGEADD continues after REPLY xx, 'U',
and fails after REPLY xx, 'END'.
Operator Response: Enter REPLY xx, 'U' to continue, or REPLY
xx, 'END' to fail the PAGEADD command.
IEE7891
PAGEADD COMMAND
READ} ERROR FOR QUICK/WARM START DATA
{ WRITE
QUICK/WARM STARTS FROM THIS IPL WILL HAVE
UNPREDICTABLE RESULTS
Explanation: Abnormal termination occurred while ILRPREAD
was accessing page data set information (lLRTPARB) needed
for a quick/warm start. (ILRTPARB resides in the PLPA page
data set.) The status of ILRTPARB is unknown.
• For READ: If the error occurred while reading ILRTPARB,
the error may have been temporary. It may still be possible
to quick/warm start, and the PAGEADD command may be
reentered without further destroying quick/warm start
capability.
• For WRITE: If the error occurred while writing ILRTPARB,
the status of the data set is unknown. It may still be
possible to quick/warm start. However, further use of the
PAGEADD command for page data sets will definitiely
destroy quick/warm start capability.
System Action: The PAGEADD command is failed.
Programmer Response: Determine the cause of the abnormal
condition, whether the PAGEADD command should be allowed
this IPL, and whether a quick or warm start should be
attempted next IPL.
Operator Response: Report this message to the system
programmer before issuing any more PAGEADD commands.
VS2.03.813
IEE7961
DOMAIN DISPLAY
DMNNO MIN MAX WT MPLT CMPL RUA INCU
GOOU OUTU
dmnno min max wt mplt cmpl rua incu goou outu
Explanation: In response toa DISPLAY DMN command, this
message provides a display of the domain descriptor table.
The first and second lines of the message always appear; the
third line appears for each domain.
In the message text, the fields are:
DMNNO
A decimal number identifying the domain from which this
line of data is taken.
MIN
The minimum multiprogramming level of this domain.
MAX
The maximum multiprogramming level of this domain.
WT
The weighting factor used in defining the relative
importance of this domain when SRM assigns new
multiprogramming levels to domains.
MPLT
The current multiprogramming level target.
CMPL
The current multiprogramming level.
RUA
The average number of ready users.
INCU
The current number of swappable in-storage users.
GOOU
The average number of users going out.
OUTU
The current number of users on the out-of-storage queue.
Operator Response: None.
I);
)
\
IEE7971
DMN nnn NOT DEFINED IN DOMAIN TABLE
Explanation: Domain nnn that was requested does not have an
entry in the domain descriptor table under which the system is
currently running.
System Action: The command that requested the domain is
not executed.
Operator Response: Reenter the command, specifying a valid
domain.
IEE7981
MIN VALUE EXCEEDS MAX VALUE IN DOMAIN
TABLE
Explanation: While attempting to use the SETDMN command to
change the minimum or maximum multiprogramming level
value for a domain, the mimimum value was set greater than
the maximum value.
System Action: The command is not executed. The domain
table remains unchanged.
Operator Response: Reenter the command, specifying a
correct minimum or maximum value.
IEE824A
cde COMMUNICATION TASK ABEND, xxx DUMP
TAKEN
Explanation: The communications task abnormally terminated
and is attempting a STAR retry. All I/O processing for operator
consoles has been halted and only the master console is
active. The fields in the message text are:
• cde - the ABEND completion code.
• xxx - NO if no dump was taken; blank if a successful dump
was taken.
'
System Action: All pending messages and outstanding WTORs
are discarded. Users of communication task functions (WTO,
WTOR, DOM) can expect unpredictable results. All user tasks
and TSO tasks in real storage are abnormally terminated if
they have unanswered WTORs. A dump is attempted using the
SVC Dump facility.
Operator Response: If the message indicates that a successful
dump was taken, use the AMDPRDMP program to print it. A
re-IPL of the system may be necessary. If you choose not to
re-IPL, use the VARY command to reactivate other consoles.
Problem Determination: Table I, items 2, 16, 29.
IEE8241
TASKNAME ttt FAILED, TERMINATED [,DUMPED]
STARTED TASK
Explanation: An ABEND, program check, depression of the
RESTART key, or machine check took place with STARTED
TASK (taskname ttt, if available) in control. If DUMPED
appears in the message text, a dump was taken to
SYS1.DUMP.
System Action: The STARTED TASK is terminated immediately.
A record describing the error is written to SYS1.LOGREC and a
dump is attempted to SYS1.DUMP.
Operator Response: Reissue the START or MOUNT command,
if one was attempted and failed.
Programmer Response: Reissue the LOGON command, if a
LOGON was attempted and failed.
Problem Determination: Table I, items 1, 2, 3, 7a, 16, 28, 29.
IEE9081
cm CMD LENGTH EXCEEDS MAX
Explanation: In the cm command, the length of the operand
field exceeds the maximum number of characters.
System Action: The system did not execute the command.
Operand Response: Probable user error. Enter the command
again with a shorter operand field.
Problem Determination: Have available the master console
sheet or the listing from a. terminal in operator mode.
IEE9201
NO TR UPDATE AT hh.mm.ss yy.ddd
Explanation: A time interval has elapsed at hh.mm.ss signaling
that an updated display be created on behalf of the TRACK
command. However, I/O has not been completed for the
previous TRACK display.
In the message text, hh.mm.ss indicates the time (in hours,
minutes, and seconds) and yy.ddd indicates the date (in the
last two digits of the year and the day of the year). If the date
could not be provided when the information for the display was
gathered, yy.ddd will appear as 00.000.
System Action: No updated display will be created. A new
time interval will be established and another attempt will be
made to create an active display when the new interval
expires.
Operator Response: None. However, if this condition occurs
frequently, the time interval should be increased by entering K
T,UTME = nn.
Section 8: lEE Messages - Master Scheduler
8-25.1
•
IEE9211
em op REJECTED
IEE9241
l
DISPLAY ALREADY EXISTSl
DISPLAY' AREA BUSY
NO TRACK TO STOP
NEEDS DISPLAY AREA '
DEVICE NOT SUPPORTED
Explanation: A TRACK, STOPTR, or K V command was entered
and Qne of the following error conditions occurred:
• DiSPLAY ALREAD.Y EXISTS - A TRACK command requested
a dynamically updated status display at a console already
displ~ying a dynamic display. A TRACK command requesting
the same options as being display is issued to a TRACK
display in Hold Mode in an attempt to get it updated. Only
one TRACK display can appear on a console.
• DISPLAY AREA BUSY - A DISPLAY or TRACK command was
issued specifying an area (L - cca) in which a display
already existed ..
• NO TRACK TO STOP - A STOPTR command was entered 1)
with an area specified that did not contain a TRACK display,
or 2) to a, console which did not contain a TRACK display.
• NEEDS DISPLAY AREA - 1) A TRACK command was issued
to a console without any areas. defined. 2) A DISPLAY
command was issued to a console in STATUS DISPLAY
mode without any areas defined.' 3) A TRACK command was
issued 'with L - z (in-line operand).
• DEVICE NOT SUPPORTED • A K V,USE - MS was entered in a system which has no
paper consoles online.
• A K V command was entered against a 2250.
INVALID AREA DEFINITION
SCREEN SIZE EXCEEDED
}
DISP,LAY IN OR ABOVE AREA
{
AREA TOO SMALL
Explanation: The operator entered a CONTROL A,II (or K A,II)
command to define or redefine the screen areas or a K
A,NONE command in which one of these errors was detected:
SCREEN SIZE EXCEEDED
The sum of the lengths of the areas defined exceeded the
size of the message area on the console for which the
definition was requested.
DISPLAY IN OR ABOVE AREA
Redefinition was requested wbich affects an area with a
display in or above it. Any area definition requested while a
display is on the screen may differ from the previous
definition only in regard to display areas above the area in
use. The operator attempted to clear the screen of all area
definitions via K A,NONE and one of the areas contained a
display.
AREA TOO SMALL
An attempt was made to define a display area of less than
four lines.
System Action: The command is not executed.
Operator Response: Correct the command and reissue it if
desired. If the problem recurs, have the hardcopy log available
before calling IBM for support. For K A,NONE error, erase the
displays, then reissue the command.
IEE9251
Operator Response:
• OISPLAY ALREADY EXISTS - ,If the TRACK display is in
HOLD mode as a result of a K D,H command, a K D,U
command will result in the TR display being reactivated.
While in Hold Mode, a TRACK command can be issued to
change the display options thC!t will appear after a K D,U is
issued to reactivate the display.
• NO TRACK TO STOP - If a TRACK display is active, supply
the L - cca operand on the PT command and reissue.
• NEEDS DISPLAY AREA - For the TRACK or DISPLAY
command, first issue the K A,II,II command to define areas.
For the DISPLAY command, the above or K V the console to
message stream.
• DISPLAY AREA BUSY - Reenter the command specifying
another area.
• DEVICE NOT SUPPORTED • Vary a paper console online, repeat the K V,USE = MS
command.
• The K V command is not valid for the Master Console or
a 2250.
Problem Determination: Table I, items 2, 29.
IEE9221
K T,UTME - nnn,L - cc
Explanation: This message is issued in response to a K T,REF
or K T command issued on a non-CRT console. The value
specified by nnn is the number of seconds in the time interval
(30 - 999) for updating of dynamic display on console cc. It
represents the CONTROL (K) command that set the time
interval.
cc is the identifier of the console specified in the K T,REF
command issued at the console receiving this message.
System Action: Processing continues.
Operator Response: Change the time interval, if desired.
8.26
VS2 System Messages (VS2.03.813)
K OPERAND op
FOR CRT ONLY
}
{ FOR NON CRT ONLY
Explanation: K, TRACK, or STOPTR command operand op
applies only to CRT consoles. If entered from a non-CRT, it
must be routed to a CRT console. A MSGRT K was issued
from a CRT device.
System Action: The command is not executed.
Operator Response: Correct the command and reissue it if
desired, D C,K may be entered for an explanation of the
CONTROL command. The TRACK and STOPTR commands are
valid only to CRT devices. The only way to direct a K
command from one CRT device to another is to use the
L - cca operand on the K command.
Problem Determination: Table I, items 2, 29.
IEE9261
L - cca OPERAND INVALID
cca NOT AN AREA
}
cc NOT A CONSOLE
cc FULL CAPABILITY
ON THIS COMMAND
cc OUTPUT ONLY
DYNAMIC DISPLAY AREA
cc SUBSYSTEM CONSOLE
Explanation: One of the following error conditions occurred as
a result of the location operand, L - cca (cca in the message
text is replaced with the invalid operands).
• cca NOT AN AREA - The area specified by the L - cca
operand 1) was invalid, 2) does not exist, 3) was other than
'Z' for a non-CRT console, or 4) was 'Z' for a status display
console.
• cc NOT A CONSOLE - The console ID specified by the
L - cca operand is not an existing or active console.
• cc FULL CAPABILITY - The console ID specified is not the
requestor's own console, a message stream (MS) console,
or status display (SO) console. No routine is allowed to a
full capacity (FC) console.
;I
• ON THIS COMMAND - The L = operand was specified on
one of the following commands:
KS
KD
K E,N
K D,N
K E
K D,N,HOLD
K D,PFK
K E,SEG
K E,PFK
K N,PFK
• cc OUTPUT ONLY - 1) An attempt was made to make a
console full capability via the K V,USE = FC command. The
console was an output only device. 2) An attempt was made
to define areas via K A,II command on a console which is in
message stream mode.
• DYNAMIC DISPLAY AREA - The area specified by the
L = cca operand contains a dynamic display.
• cc SUBSYSTEM CONSOLE - An attempt was made to route
to a console under the control of the job entry subsystem.
System Action: The command is not executed.
Operator Response:
• cca NOT AN AREA - Change the area specification and
reenter the command. If the problem recurs, a console
switch may have taken place. If one has, reenter the
command specifying the valid area for the alternate
console.
• cc NOT A CONSOLE - Change the console id specification
and reenter the command. If the problem recurs, a console
switch may have taken place. If one has, reenter the
command specifying the alternate console's id.
• cc FULL CAPABILITY - Specify your own console or a
message stream or status display console and reenter the
command.
• DYNAMIC DISPLAY AREA - Specify another area and
reenter the command.
• ON THIS COMMAND - Reenter the command without the
L = cca command.
• cc OUTPUT ONLY - 1) Unless the system is re-sysgened,
this device will not be able to serve as a Full capability
console, 2) The console may be altered to status display
mode via the K V, USE = SD and the K A,II command can be
reentered.
• cc SUBSYSTEM CONSOLE - Change the console ID
specified and re-enter the command.
Problem Determination: Table I, items 2, 29.
IEE9271
CONTROL REQUEST AMBIGUOUS
SPECIFY DISPLAY ID}
{ SPECIFY L OPERAND
Explanation: The Control (K) command cannot be executed
without further information:
• SPECIFY DISPLAY ID - A CONTROL C,D (or K C,D)
command was entered without the id operand. To cancel a
display (K C,D, id), the id of the display to be terminated
must always be specified. It is found at the extreme
righthand side of the control line of the display. (For use on
paper consoles only.)
• SPECIFY L OPERAND - A CONTROL command for an
out-of-line display, such as a frame or erase command, was
issued without the' routing location parameter (L = cca), and
more than one display exists on the screen. The area id of
the display area tQ_be controlled must be specified by using
the L operand.
System Action: The command is not executed.
Operator Response: Reissue the command specifying the
missing operand.
Problem Determination: Table I, items 2, 11, 29.
IEE9281
DISPLAY AREA 10'5 FOR CONSOLE cc ARE id, id, .••
Explanation: This message is issued in response to 1) the
operator defining areas for console cc via K A,II,II, 2) the
operator issuing K A, NONE to delete the screen areas on
console cc, 3) the operator issuing K A or K A,REF to discover
the areas presently defined to console cc, along with message
IEE9291. The display area identifiers are listed in the order in
which the areas were defined,· from the bottom of the screen
to the top.
System Action: Processing continues.
Operator Response: The operator' may route displays to the
areas defined by using the display area id, or for K A, NONE
redefine some areas.
IEE9291
K A,
NONE,L = ee
}
{ length, ... ,L = cc
Explanation: This message is issued, on non-CRT consoles
only, in response to the operator issuing a K A,REF command
for console cc. It represents the CONTROL (K) command
which defined the display areas for the console whose address
is specified by cc.
System Action: Processing continues.
Operator Response: Change the display area definition via K
A,II,II ... command, if desired.
IEE9301
MR [[(0 = [(]display op[,display op)] ... ,
L
=l~.e 1
cea
ee*
)][,(TR = A,L =
l~c ~)]['(K'L =t~C J)]l
eea
ce*
eea
ce*
Explanation: This message is issued, on non-CRT consoles
only, in response to the operator issuing a MR REF command.lt
represents the MSGRT (MR) command which specified the
routing defaults currently in effect. If NONE appears, no
routing defaults have been established. If no area id (a) was
specified, an asterisk is displayed in the output.
System Action: Processing continues.
Operator Response: If desired, change the routing defaults with
the MR command.
IEE9311
cm op INSUFFICIENT STORAGE FOR COMMAND
Explanation: While attempting to fulfill the request specified by
the cm, op command, a GETMAIN was issued requesting
storage to build a control block and/or work area. The
requested storage was not available. This condition may occur
during definition of display areas or when routing to a console
other than the requesting console.
System Action: The command cm op was not executed.
Operator Response: Reenter the command at a later time.
Problem Determination: Table I, items 2, 29.
IEE9321
nnn
Explanation: A multiple line WTO macro instruction was issued
with descriptor code 9· and no control line text was supplied.
The number, nnn is used with the CONTROL (K) command to
cancel the display.
System Action: SVC 35 has supplied this message as a control
line. The number, nnn, is the display identification number.
Operator Response: None.
Section 8: lEE Messages - Master Scheduler
8-27
•
IEE9331
DCMLIB OPEN FAILED
Explanation: When attempting to open the display control
module library (SYS1.DCMLlB) in secondary storage, the
system was either unable to locate the library, unable to open
the library, or the volume containing the library was off-line
during IPL.
System Action: The PFK command entry facility will be
inoperative because the system was unable to read the
command definitions into virtual storage.
Operator Response: All commands that are normally entered
by means of the PFK or the light pen must be entered from
the typewriter keyboard. Report the problem to the
programmer responsible for the system.
IEE9341
PFK UPDATE FAILED
Explanation: An I/O error occurred: (1) when the system
8-28
VS2 System Messages (VS2 Release 3.7)
attempted to read the permanent PFK definition from
secondary storage during IPL, or (2) when the system
attempted to write a new PFK definition in secondary storage
after the operator issued a CONTROL N,PFK command.
System Action: If an error occurs on a read during IPL,the
permanent PFK definitions will be unavailable for the system
operation following the current IPL. If an error occurs for a
PFK update, the permanent copies of the PFK definitions will
not be altered, and the PFK updates will not carry over to
subsequent IPLs.
Operator Response: If an error occurs on a read during IPL,
the operator will have to define each PFK key for the current
IPL. If an error occurs during a PFK update, the new definition
will be effective only for the current IPL. Report this problem
to the programmer responsible for the system.
Section 9: Job Scheduler Messages (IEF)
Component Name
IEF
Program Producing Message
Job scheduler.
Audience and Where Produced
For programmer: listing of job control statements in SYSOUT data set.
For operator: console.
Message Format
IEFnnnl text
(in SYSPRINT)
xx IEFnnns text
(on console)
nnn
Message serial number.
text
Message text.
xx
Message reply identification (absent, if operator reply not required).
s
Type code:
Action; operator must perform a specific action.
A
Decision; operator must choose an alternative.
D
E
Eventual action; operator must perform action when he has time.
I
Information; no operator action is required.
W Wait; processing stopped until action is determined and performed.
Comments
None.
Associated Publications
OS/VS2 JCL, GC28-0692
Operator's Library: OS/VS2 Reference (JES2), GC38-0210
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IEFOSSI
REGION UNAVAILABLE, ERROR CODE = cde
Explanation: It is not possible to obtain a region for the job
step. The error code cde explains why the region could not be
obtained:
OS
A V = V region was requested and a region size was
specified which was larger than the private area, or a
V = R region was requested and a region size greater
than the V = R area was specified. (In case no region
size was specified, it is possible for the V = R default
to be greater than the size of the V = R area.)
16
A V = R region was requested, but either long-fixed or
damaged pages in the V = R area made it impossible
to obtain the requested region, or a V = R region was
requested and there was not enough SQA available for
the system to complete the processing of the request.
20
Either a V = V or V = R region was requested.
Fragmentation by LSQA, SWA, or subpools 229 or 230
has made it impossible to obtain the requested region
(because no contiguous block storage exists which
could satisfy the request.)
24
A request for a V = R region could not be satisfied
because the installation GETPART exit routine rejected
the request.
System Action: The step is terminated with a system
completion code of S22.
Programmer Response: Resubmit the job. If cde is OS, it may.
be necessary to either decrease the size requested for the
region or to submit the job to be run on a system with a larger
amount of V = R storage available or a larger private area.
If cde is 20, and if a V = V region with a size approximately
equal to the private area was requested, it will be necessary to
decrease the region size. See the system programmer for help
in determining your region requirements.
If cde is 24, resubmit the job, requesting a region whose size
is not greater than the limit set by the installation GETPART
exit routine.
Problem Determination: Table I, items 1, 2, 3, 7a, 29.
IEFOS61
ERROR IN SWA RECOVERY - RESTART CANCELLED
Explanation: During restart for the job, an error was
encountered while merging control blocks from the job journal
with those already in the Scheduler Work Area. A control block
requiring updating was not found.
System Action: The error prevents successful completion of
restart processing; the job is canceled.
Programmer Response: Resubmit the job as deferred step or
checkpoint/ restart.
Problem Determination: Table I, items 1, 3, 4, 29.
IEFOS71
ERROR ON JOB JOURNAL - RESTART CANCELLED
Explanation: • During restart for the job, an error was
encountered in accessing the job journal. The error occurred
during GET.
System Action: The error prevents successful completion of
restart processing; the job is canceled.
Programmer Response: Resubmit the job as a deferred step or
checkpoint/restart:
Problem Determination: Table I, items 1, 3, 4, 29.
Section 9: IEF Messages - Job Scheduler
9-1
•
IEF0891
ERROR ON WRITE TO JOB JOURNAL - JOB NOT
ELIGIBLE FOR RESTART
Explanation: An error was encountered while attempting to
write to the job journal.
System Action: Processing of the job continues until
completion. However, no more journalling will be done for this
job.
Programmer Response: Ignore the message if the job is
completed successfully. If the job fails, refer to message
IEF168lfor more information and the action to be taken.
IEF090E
PROTECT KEY UNAVAILABLE. jjj PLACED ON HOLD
Q
Explanation: Job iii requested ADDRSPC = REAL for at least
one step; all protection keys, 9 through 15, were currently
assigned to other jobs that require unique protection keys.
(The jobs that require unique protection keys are those that
specify ADDRSPC = REAL for one or more steps.)
System Action: The job is placed on the HOLD queue.
Operator Response: Either release the job from the HOLD
queue at a time when a protection key is available or cancel
the job. Enter a DISPLAY A command to determine if there are
fewer than 7 jobs reserving a protection key. If there are fewer
than 7 jobs, consult Problem Determination below.
Problem Determination: Table I, items 2, 7c, and 29.
jjj-LOGGED ON [-TIME = hh.mm.ss]
Explanation: In response to a MONITOR command with
JOBNAMES or SESS in its operand, this message indicates that
a user has logged on to the system under time sharing and his
session name is Hi.
If T is also specified in the operand of the command, then the
time of day appears, where hh specifies the hour (00-23), mm
specifies the minute (00-59), and ss specifies the second
(00-59).
System Action: Session iii is entering allocation.
Operator Response: No response required. However', if the
user should not be logged on at this time, issue CANCEL
U = iii command and the session will be terminated.
IEF1261
iii-LOGGED OFF [-TIME
= hh.mm.ss]
Explanation: In response to a MONITOR command with
JOBNAMES or SESS in its. operand, this message indicates that
the session iii has terminated (been logged off of the system).
This message is not issued if session jjj has terminated
abnormally.
If T is also specified in the operand of the command, then the
time of day appears, where hh specifies the hour (00-23), mm
specifies the minute (00-59), and sss specifies the second
(00-59).
System Action: Session jjj has completed termination.
Operator Response: None.
PROTECT KEY UNAVAILABLE. START ppp REJECTED
IEF0911
Explanation: The program indicated in procedure ppp is a
program that requires a unique protection key; all the
protection keys, 9 through 15, were currently assigned to
other jobs. (The jobs that require unique protection keys are
those that specify ADDRSPC = REAL for one or more steps.)
System Action: The task is not started.
Operator Response: If the task is required, reenter the START
command at a time when a protection key is available. Enter a
DISPLAY A command to determine if there are fewer than 7
jobs reserving a protection key. If there are fewer than 7 jobs,
consult Problem Determination below.
Problem Determination: Table I, items 2, 7c, and 29.
IEF0921
jjj sss ppp WAITING FOR xxxK REAL STORAGE
Explanation: During initiation of procedure step ppp of step
sss of job iii, the requested V = R region of size xxxK could
not be immediately obtained.
System Action: The initiator waits until the request can be
satisfied.
Operator Response: No action is required, however, you may
do one of the following:
• Enter a CANCEL command for other jobs which are running
in V = R storage, in an effort to free V = R storage.
• Enter a CANCEL command for job jjj to terminate
processing for that job.
Report this message to the system programmer.
Problem Determination: Table I, items 1, 2, 3, 7a, 29.
IEF0991
JOB
iii WAITING FOR DATA SETS
iii requires data sets that are not available.
Explanation: Job
These data sets are named in message IEF8631. When the data
sets become available, the system will reserve them for the
job and· processing will continue.
System Action: Processing of the job is suspended until the
data sets become available.
Operator Response: None required. However, if you want to
terminate processing of the job, a CANCEL command may be
issued.
9-2
IEF1251
VS2 System Messages (VS2 Release 3.7)
IEF1271
iii sss [ppp] ddn[ +xxx] - NO SPACE PARAMETER
OR ZERO SPACE REQUEST AT ABSTR ZERO
Explanation: No SPACE parameter appears in a DO statement
(ddn) defining a new direct access volume, or an absolute
track request was made for no space (zero space) beginning
at absolute track zero.
In the message text, +xxx refers to the relative position of a
concatenated DO in relation to the first DO in the
concatenated group ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. If the data set is
not new, correct the DISP parameter by specifying OLD, SHR,
or MOD. If the data set is new, make sure that a SPACE
parameter appears. Then rerun the job.
Problem Determination: Table I, items 1, 2, 4, 7c, 25a, 29.
IEF1281
iii sss [ppp] ddn[ + xxx] - INVALID REQUEST FOR
ISAM INDEX
Explanation: The control program is unable to allocate space
for the index of a new indexed sequential data set for one of
the following reaso'ns:
• An embedded index was requested for the index or overflow
area by a DO statement specifying the index quantity
subparameter in its SPACE request.
• An embedded index was requested for multivolume prime
area. The request was made by a DO statement specifying
an index quantity in the SPACE parameter,
DSNAME = name(PRIME), and a device number greater than
1 in the UNIT parameter.
In the message text, +xxx refers to the relative position of a
concatenated ISAM DO statement in relation to the first DO for
the ISAM data set ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Correct the faulty
DO statement, and rerun the job. In the first case, delete the
index quantity subparameter. In the second case, delete the
index quantity subparameter or change the device number
subparameter to 1.
Problem Determination: Table I, items 2, 7c, 29.
"
I
,J'
IEFI291 jjj sss [ppp] ddn[ + xxx] - MULTIVOLUME INDEX NOT
ALLOWED
Explanation: The control program is unable to allocate a
multivolume index for a new indexed sequential data set. A
device number greater than 1 cannot be specified in the UNIT
parameter of a DD statement specifying
DSNAME = name(lNDEX).
In the messate text, +xxx refers to the relative position of a
concatenated ISAM DD statement in relation to the first DD for
the ISAM data set ddn.
System Action: The job is terminated.
Programmer Response: Delete the device number
subparameter, or reduce it to 1. Then rerun the job.
Problem Determination: Table I, items 2, 7c, 29.
IEF1301
jjj sss [ppp] ddn[ +xxx] - DSNAME ELEMENT
WRONG - MUST BE INDEX, OVFLOW, OR PRIME
Explanation: In one of the DD statements defining an indexed
sequential data set, the element part of the DSNAME
parameter is other than PRIME, INDEX, or OVFLOW.
In the message text, +xxx refers to the relative position of a
concatenated ISAM DD statement in relation to the first DD for
the ISAM data set ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Correct the
element subparameter. List the volume table of contents
(VTOC) of each volume that will contain the data set using the
USTCAT command. If the name of this data set appears in any
VTOC, remove it using the DEFINE and DELETE commands.
Then rerun the job.
Problem Determination: Table I, items 1, 2, 3, 7c, 14, 29.
IEF1311
jjj sss [ppp] ddn[ +x?,x] - MULTIVOLUME OVFLOW
REQUEST NOT ALLOWED
Explanation: A DD statement is requesting a multivolume
overflow area for a new indexed sequential data set by
specifying a device number greater than 1 in the UNIT
parameter and DSNAME = name (OVFLOW). This is not
allowed.
In the message text, +xxx refers to the relative position of a
concatenated ISAM DD statement in relation to the first DD for
the ISAM data set ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Change the device
number subparameter to 1. List the volume table of contents
(VTOC) of each volume that will contain the data set using the
LlSTCAT command. If the name of the data set appears in any
VTOC, remove it using the DEFINE and DELETE commands.
Rerun the job.
Problem Determination: Table I, items 1, 2, 4, 7c, 29.
IEF1321
jjj sss [ppp] ddn[ +xxx] - SPACE PARAMETER
WRONG - CYL AND ABSTR CONFLICT
Explanation: The SPACE parameter in one of the DD
statements defining an indexed sequential data set is incorrect.
One of the. DD statements defining this data set specified
ABSTR and specified CYL. Space for one area of an indexed
sequential data set cannot be allocated using the CYL
subparameter while the space for another area is allocated
using the ABSTR subparameter.
In the message text, +xxx refers to the relative position of a
concatenated ISAM DD statement in relation to the first DD for
the ISAM data set ddn.
System Action: The job is termin~ted.
Programmer Response: Probable 'user error. Correct the
SPACE parameter. List the volume table of contents (VTOC) of
each volume that will contain the data set using the LlSTCAT
command. If the name of this data set appears in any VTOC,
remove it using the DEFINE and DELETE commands. Then
rerun the job.
Problem Determination: Table I, items 2, 7c, 14, 29.
IEFI331
jjj sss [ppp] ddn[ +xxx] - SPACE PARAMETER
WRONG - CYL AND CONTIG CONFLICT
Explanation: The SPACE parameter in one of the DD
statements defining an indexed sequential data set is incorrect.
The CONTIG subparameter appears for a CYL request in one
of the DD statements, while not in another. Space for one area
of an indexed sequential data set cannot be allocated
contiguously if space for another area is not.
In the message text, +xxx refers to the relative position of a
concatenated ISAM DD statement in relation to the first DD for
the ISAM data set ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Correct the
SPACE parameter. List the volume table of contents (VTOC) of
each volume that will contain the data set using the LlSTCAT
command. If the data set name appears in any VTOC, remove
it using the DEFINE and DELETE commands. Rerun the job.
Problem Determination: Table I, items 2, 7c, 14, 29.
IEF1341
jjj sss [ppp] ddn[ +xxx] - SUBPARAMETER WRONG
IN SPACE PARAMETER - MUST BE CYL OR ABSTR
Explanation: The SPACE parameter in a DD statement defining
a new indexed sequential data set is incorrect. A subparameter
other than CYL or ABSTR is present in the statement.
In the message text, +xxx refers to the relative position of a
concatenated ISAM DD statement in relation to the first DD for
the ISAM data set ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Correct the invalid
subparameter. List the volume table of contents (VTOC) of
each volume that will contain the data set using the LlSTCAT
command. If the name of the data set appears in any VTOC,
remove it bsing the DEFINE and DELETE commands. Then
rerun the job.
Problem Determination: Table I, items 2, 7c, 14, 29.
IEF13S1
jjj sss [ppp] ddn[ +xxx] - PRIMARY SPACE REQUEST
MAY NOT BE ZERO
Explanation: In a DD statement defining an indexed sequential
data set, the primary space subparameter is zero. This is not a
valid space request.
In the message text, +xxx refers to the relative position of a
concatenated ISAM DD statement in relation to the first DD for
the ISAM data set ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Change the
primary space request to a non-zero positive value, and rerun
the job.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF1361
jjj sss [ppp] ddn[ +xxx] - DUPLICATION IN
ALLOCATION - INDEX AREA REQUESTED TWICE
Explanation: Two DD statements defining the same indexed
sequential data set are requesting space for the index area.
Following the allocation of an index area requested by a DD
statement containing DSNAME = name(INDEX), either a DD
statement containing DSNAME = name(PRIME) requested an
embedded index through an index quantity in its SPACE
parameter, or another DD statement was found specifying
DSNAME = name(lNDEX).
Section 9: IEF Messages - Job Scheduler
9-3
•
In the message text, +xxx reters to the relative position of a
concatenated ISAM DD statement in relation to the first DD for
the ISAM data set ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Either eliminate
the DD statement that specifies DSNAME = name(lNDEX) or
eliminate the index quantity subparameter in the DO statement
specifying DSNAME = name(PRIME). List the volume table of
contents (VTOC) of each volume that will contain the data set
using the L1STCAT command. If the name of the data set
appears in any VTOC, remove it using the DEFINE and DELETE
commands. Rerun the job.
Problem Determination: Table I, items 2, 7c, 14, 29.
iii
IEF1401
sss [ppp] ddn[ +xxx] - DIRECTORY SPACE
REQUEST LARGER THAN AMOUNT AVAILABLE ON
THIS VOLUME
Explanation: The directory for a new partitioned data set was
not allocated because the space requested for the directory by
the SPACE parameter of the associated DD statement
exceeded the space available on the specified volume.
In the message text, +xxx refers to the relative position of a
concatenated DD in relation to the first DO in the
concatenated group ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Reduce the
directory quantity subparameter or request a different volume.
Then rerun the job.
Problem Determination: Table I, items 1, 2, 4, 7c, 2Sa, 29.
iii
IEF1411
sss [ppp] ddn[ +xxx] - INDEX REQUEST MUST
PRECEDE PRIME FOR ISAM DATA SET
Explanation: In the DD statement defining an indexed
sequential data set, a statement containing
DSNAME = name(PRIME) was found to precede a statement
containing DSNAME = name(lNDEX).
In the message text, +xxx refers to the relative position of a
concatenated ISAM DD statement in relation to the first DD for
the ISAM data set ddn.
System Action: The job is terminated.
Programmer Response: Reorder the DD statements for the
data set, making sure that INDEX is placed before PRIME. List
the volume table of contents (VTOC) of each volume that will
contain the data set using the L1STCAT command. If the name
of the data set appears in any VTOC, remove it using the
DEFINE and DELETE commands. Then rerun the job.
Problem Determination: Table I, items 1, 4, 7c, 14, 29.
IEF1421
iii
sss [ppp] STEP WAS EXECUTED - COND CODE
cde
Explanation: Step sss of job iii, or cataloged procedure step
ppp, was executed, and the condition code for the step is cde.
Note: This condition code originates from the contents of
general purpose register 15 at the end of the step. If the last
task of the step did not set a completion code in register 15,
the cde field of the message is meaningless.
System Action: The system will continue to process further
steps of the associated job if so allowed by the COND =
parameter of subsequent EXEC statements.
Programmer Response: None.
IEF1431
iii sss [ppp] ddn[ +xxx] - LAST CONCATENATED DO
CARD UNNECESSARY OR INVALID FOR THIS DATA
SET
Explanation: In processing the DO statement defining an
indexed sequential data set, it was found that at least four
9-4
concatenated DO statements were present for the data set.
The DO card(s) after the third card are unnecessary.
In the message text, +xxx refers to the relative position of a
concatenated ISAM DO statement in relation to the first DO for
the ISAM data set ddn.
System Action: The job is terminated, and the extra DO
statements are not processed. If any non-ISAM in the
concatenation were allocated, they are deleted.
Programmer Response: Remove the extra DD statements. List
the volume table of contents (VTOC) of each volume that will
contain the da'ta set using the L1STCAT command. If the name
of the data set appears in any VTOC, remove it using the
DEFINE and DELETE commands. Then rerun the job.
Problem Determination: Table I, items 1, 4, 7c, 14, 29.
VS2 System Messages (VS2 Release 3.7)
IEF14S1
iii
sss [ppp] ddn[ +xxx] - SPACE REQUEST MUST
BE ABSTR FOR DOS VOLUME
Explanation: In DD statement ddn defining an indexed
sequential data set with multivolume prime area, the space for
one of the prime volumes (except the first one) was requested
on a volume where the DOS bit (bit 0 of the DS4VTOCI field)
is set in the format 4 DSCB; however, the SPACE parameter
for the DD statements that define the data set specified CYL.
In the message text, +xxx refers to the relative position of a
concatenated DO in relation to the first DD in the
concatenated group ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Request space by
coding ABSTR for the SPACE parameter or request a different
volume. Execute the L1STCAT command to list the volume
table of contents (VTOC) of each volume that will contain the
data set. If the name of the data set appears in any VTOC,
remove it using the DEFINE and DELETE commands. Then run
the job again.
Problem Determination: Table I, items 1, 3, 7c, 2Sa, 29.
IEF16SI
cm
Explanation: Command cm was entered through the input
stream.
System Action: If the operator is requested to authorize
execution of commands entered through the input stream,
message IEF166D follows to permit the operator to respond.
Operator Response: Respond to message IEF166D, if issued.
IEF166D
REPLY YIN TO EXECUTE/SUPPRESS COMMAND cm
Explanation: This message permits the operator to authorize
execution of the command displayed in message IEF16SI,
which precedes this message.
Operator Response: If the command displayed in preceding
message IEF16S1 is to be executed, enter REPLY xx, 'Y'.
If the command displayed in preceding message IEF16SI is not
to be executed, enter REPLY xx, 'N'.
IEF1671
NO JOB JOURNAL OPTION SPECIFIED - REST ART
CANCELLED
Explanation: The job was abnormally terminated and was
eligible for automatic restart but, as the NO-JOB Journal had
been specified for this job, automatic restart was not possible.
System Action: The job is terminated.
Programmer Response: Resubmit the job for deferred restart,
if desired. If automatic restart support is desired for future
submissions of this job, request that the installation run the
job with the job journal option.
Problem Determination: Table I, items 1, 29.
IEFI681
ERROR ON JOB JOURNAL - RESTART FOR JOB
CANCELLED
Explanation: The job has abnormally terminated and was
eligible for automatic restart, but as there was an error on the
job journal, automatic restart was canceled.
System Action: The job is terminated.
Programmer Response: Resubmit the job for deferred restart,
if desired.
Problem Determination: Table I, items 1, 29.
IEFI691
RESTART CANCELLED FOR JOB jjj
Explanation: During an automatic restart of job jjj, one of the
following occurred:
• While merging control blocks from the job journal with those
already in the Scheduler Work Area, a control block
requiring updating was not found.
• In accessing the job journal, an error occurred during GET.
System Action: The error prevents successful completion of
restart processing; job jjj is canceled.
Operator Response: None.
Problem Determination: Table I, items 1, 3, 4, 29.
IEFI701
n
No RPL pointer existed therefore cannot access ACB.
Enqueue to serialize execution of PUT failed.
PUT to system message data set failed.
Unpredictable ABEND.
jjj
y'
.I
Jobname.
System Action: Processing continues .
Operator Response: None.
IEFI72E
jjj. HELD, CPU (x) OFFLINE
Explanation: The first step of job jjj requires hardware features
present only on CPU x, and CPU x is offline.
System Action: Job jjj is placed in a HOLD state.
Operator Response: Issue a VARY ONLINE command for CPU x
before releasing job jjj from the HOLD state to be run.
Problem Determination: Table I, items I, 2, 3, 7a, 29.
IEFI731
IEFI751
jjj FAILED, CPU (x) OFFLINE
Explanation: One of the following occurred:
• Job jjj was initiated as a result of a START command and
requires hardware features present only on CPU x, and CPU
x is offline.
• A step other than the first step of job jjj requires hardware
features present only on CPU x, and CPU x is offline.
System Action: The job is terminated.
Operator Response: If the message is written as a result of a
START command, reissue the START command when the
required CPU is online .. If the message occurs frequently, notify
the system programmer.
Programmer Response: Resubmit the job, informing the
operator to have the appropriate CPU online.
Problem Determination: Table I, items I, 2, 3, 7a, 29.
IEFI761
WT1R
SYSTEM ERROR BEFORE JOB INITIATION
Explanation: While this job was being processed an ABEND,
program check, depression of the RESTART key, or a machine
check took place before the job was initiated.
~~:s~~TI!NG FOR WORK,
FORMS =
WRITER =
DEST=
JOBID =
Explanation: The External Writer is waiting for work. The
optional parameters indicate which selection criterion the
External Writer is using to wait for work.
System Action: The External Writer is in a wait state until
either a MODIFY or STOP command is received or until work is
received from JES2 that satisfies the named selection criterion.
Operator Response: Verify that the selection criterion is valid,
(the FORMS required is a valid form number, the DEST
specified is still valid, or the WRITER name is valid). If
WRITER = STDWTR was specified to the named External Writer
in a MODIFY command, a WRITER = blank will appear in the
message, indicating that a named writer is selecting data sets
that have no writer name on their SYSOUT DD card.
IEFlt71
WTR ddd INVALID MODIFY KEYWORD
Explanation: The named External Writer received an invalid
keyword in the last MODIFY command.
System Action: The External Writer does no more work until
another valid MODIFY command is receivQd. The External
Writer is waiting for either a STOP or MODIFY command.
Operator Response: Enter a new valid MODIFY command or
stop the writer.
IEFI781
WTR ddd MODIFY PARAMETER INVALID.
Explanation: The named External Writer received an invalid
MODIFY parameter.
System Action: The External Writer does no more work until
another valid MODIFY command is received;
Operator Response: Enter a new valid MODIFY command or
stop the writer.
Programmer Response: Check to see if the FORMS parameter
was greater than 4 characters, or the WRITER or JOBID
parameter was greater than 8 characters in length. Also verify
that the MODIFY parameters contained valid characters.
IEF1791
IEF1741
AMP KEYWORD xxxxxxxx DUPLICATE OR
CONFLICTING PARM STEP NOT EXECUTED
Explanation: A duplicate or conflicing AMP keyword has been
discovered by the AMP interpreter.
System Action: The job is termi~ated.
Programmer Response: Probable user error. Delete the
duplicate keyword, or correct the conflicting keyword or
keywords. Then rerun the job.
n jjj (53 bytes of message passed to WTP)
Explanation: Write-to-programmer was unable to complete
processing. The n value indicates the reason for the failure.
This message will be built and issued to hardcopy. In the
message text, the fields are as follows:
I
2
3
4
System Action: A return code indicating a system error is sent
to the job entry subsystem. The job entry subsystem will
decide what to do with the job, (probably terminate it). A
record describing the error is written to SYS1.l0GREC. A
dump is taken to the SYSI.DUMP data set on a program check
or depression of the RESTART key.
Operator Response: None.
Programmer Response: Resubmit the job if it is terminated.
Problem Determination: Table I, items 1, 2, 3, 7a, 16, 28, 29.
WTR ddd INVALID
JOBID
{ DEST
j
}
xxxxxx
Explanation: The named External Writer attempted to request
a data set from JES2 with either a JOBID or DEST selection
criteria and the JOBID or DEST was invalid to JES2.
Section 9: IEF Messages - Job Scheduler
9-5
•
System Action: The External Writer does no more work until
another valid MODIFY command is received.
Operator Response: Enter a new valid MODIFY command or
stop the writer.
iii
sss [ppp] - INSUFFICIENT REAL OR VIRTUAL
STORAGE FOR ALLOCATION
IEF1801
Explanation: Allocation was unable to obtain sufficient main or
virtual storage for processing.
System Response: The job is terminated.
Programmer Response: Resubmit the job.
Problem Determination: Table I, items 1, 3, 4, 7c, 29.
REGION UNAVAILABLE FOR RESTART, ERROR
CODE = cde
IEF1861
Explanation: It is not possible to obtain a region for a
checkpoint restart. The error code cde explains why the region
could not be obtained:
08
The region parameter was increased so that the region
could not be allocated or the configuration of the
system changed so that the region could not be
obtained:
• For ADDRSPC = REAL, the size of the REAL area
was decreased.
• For ADDRSPC = VIRT, the size of the private area
decreased because the size of the nucleus
increased or the size of the SQA or the IPA
increased.
16
If a REAL region was requested, either long-fixed or
damaged pages in the REAL area made it impossible
to obtain the required region.
20
Either a virtual or real region was requested.
Fragmentation by lSQA, SWA, or subpools 229 or 230
has made it impossible to obtain the requested region
(because no contiguous block of storage exists which
could satisfy the request.)
24
A request for a V = R region could not be satisfied
because the installation GETPART exit routine rejected
the request.
System Action: The step is terminated with a system
completion code of 822.
Programmer Response: Resubmit the job. If cde is 08, ensure
that the configuration of the system on which the restart is to
be done makes it possible to obtain the region owned when
the checkpoint was taken, or if the requested region size was
greater than the size of the region owned when the checkpoint
was taken, decrease the region size.
If cde is 20, and if an ADDRSPC = VIRT region with a size
approximately equal to the private area was requested, it will
be necessary to decrease the region size. See the system
programmer for help in determining your region requirements.
If cde is 24, resubmit the job, requesting a region whose size
is not greater than the limit set by the installation GETPART
exit routine.
Problem Determination: Table I, items 1, 2, 3, 7a, 29.
IEF1871
iii
FAILED - SYSTEM ERROR IN INITIATOR
Explanation: While job
iii was being processed, an ABEND,
program check, depression of the RESTART key, or machine
check occurred with the initaitor in control.
System Action: One of the following actions occurs depending
upon the status of the job at the time of the error:
• The job is terminated immediately.
• The step is terminated with a 922 system completion code.
In either case, a record describing the error is written to
SYS1.l0GREC, unless the ABEND was an OPEN failure. A
dump is taken to SYS1.DUMP when applicable.
9-6
VS2 System Messages (VS2 Release 3.7)
Programmer Response: Resubmit the job.
Problem Determination: Table I, items 1, 2, 3, 7a, 16, 28, 29.
IEF1881
PROBLEM PROGRAM ATTRIBUTES ASSIGNED
Explanation: The name of the program to be executed is a
name which is deSignated to receive one or more. special
properties. However, the job has not satisfied all the
requirements to obtain the properties.
System Action: The special properties whose requirements
were not met were not assigned. Instead of these special
properties, problem program attributes were assigned.
Operator Response: If no special properties are required,· no
action is necessary. If special properties are required and a
JOBUB or STEPlIB is being used, make sure that the program
library is authorized, or notify the system programmer.
Programmer Response: Make sure that the special attributes
'started only' or 'I-step only' are either satisfied or are not
required for the assignment of the required special properties.
Problem Determination: Table I, items 1, 2, 3, 7a, 29.
IEF1921
iii
555 ppp ddn[ +xxx] - NO ELIGIBLE DEVICE TYPE
CONTAINS ENOUGH UNITS TO SATISFY REQUEST
Explanation: There are not enough available devices of the
type specified in the UNIT parameter of DO statement ddn to
satisfy the request. If an esoteric unit name such as SYSDA is
specified, no single device type· within the esoteric has enough
available devices.
Note: A device is not considered eligible to a
telcommunications request if it is an active console, is
allocated, or is in use by a system function such as OlTEP,
DSS, or a system utility.
In the message text, +xxx refers to the relative position of a
concatenated DO in relation- to the first DO in the
concatenated group (ddn).
System Action: The job is terminated.
Programmer Response: Probable user error. Make sure that
the deivce type specified in the UNIT parameter can supply
the number of devices needed. If necessary, change the UNIT
parameter.
Problem Determination: Table I, items 1, 3, 4, 7c, 29.
IEF1931
iii
sss [ppp] ddn[ +xxx] - SPACE NOT OBTAINED
BECAUSE OF PERMANENT I/O ERROR
Explanation: An uncorrectable inputjoutput error occurred
when an attempt was made to obtain space on the direct
access device required by ddn.
In the message text, +xxx refers to the relative pOSition of a
concatenated DO in relation to the first DO in the
concatenated group (ddn).
System Action: The job is terminated.
Programmer Response: Rerun the job.
Problem Determination: Table I, items 1, 2, 3, 4, 7c, 29.
IEF1941
jjj sss [ppp] ddn[ +xxx] - VOLUME SEQUENCE
NUMBER EXCEEDS NUMBER OF VOLUME SERIALS
Explanation: The volume sequence count specified in DO
statement ddn is greater than the number of volume serial
numbers specified. One of the following has occurred:
• ddn has specified volume serial numbers in the VOL
parameter. The sequence count exceeds the number of
volume serials specified.
• ddn refers back to or is receiving a passed data set from
another DO which specifies a number of volume serials that
is less than the sequence count in ddn.
• ddn refers to a cataloged data set. The number of volume
serials for that data set is less than the volume sequence
count.
In the message text, +xxx refers to the relative position of a
concatenated DO in relation to the first DO in the
concatenated group (ddn).
System Action: The job is terminated.
Programmer Response: Probable user error. Check to make
sure that the volume sequence count is equal to or less than
the number of volume serials specified.
Problem Determination: Table I, items 1, 3, 4, 7c, 29.
IEFl9SI
jjj sss [ppp] ddn[ +xxx] - MAXIMUM NUMBER OF
DEVICES FOR DO EXCEEDED
Explanation: The number of units requested by DO statement
ddn was insufficient to permit mounting of all required
volumes. When the scheduler attempted to increase the unit
count so that a volume could be mounted, the maximum of 59
units per DO statement was exceeded.
In the message text, +xxx refers to the relative position of a
concatenated DO in relation to the first DO in the
concatenated group (ddn).
System Action: The job is terminated.
Programmer Response: Probable user error: If possible,
change the program so that fewer voluems need to be
mounted at the same time.
Problem Determination: Table I, items 1, 3, 4, 7c, 29.
IEFl961
text
Explanation: The text portion of this message has been
generated during the process of starting the Master Scheduler
and/or a job entry subsystem and is the actual JCl and
messages that would be generated for the start process. It is
put out based on the MSGlEVEl specification in the JCl.
System Action: The text has been written to hardcopy to make
it available for future reference. The message id that could
follow message IEFl961 should be consulted for a further
explanation of why the specific message was issued.
Programmer Response: look up the separate message if
available.
Problem Determination: Table I, items 2, 29.
IEFI971
SYSTEM ERROR DURING {AllOCATION
}
UNAlLOCATION
Explanation: Allocation or unallocation error routines have
been entered following a system failure that took place while
this job was in allocation or unallocation. The system failure
was one of the following:
• depression of the RESTART key
• machine check
• ABEND
• program check
System Action: If an ABEND occurred or a program check or
depression of the RESTART key occurred, a dump is taken to
the SYSLDUMP data set and a record describing the error is
written to the SYSl.lOGREC data set.
Programmer Response: Resubmit the job.
Problem Determination: Table I, items 1, 2, 3, 7a, 16, 28, 29.
IEF2011
jjj 555 [ppp] - JOB TERMINATED BECAUSE OF
CONDITION CODES
Explanation: Step sss of job jjj, or cataloged procedure step
ppp, terminated either normally or abnormally by issuing a
RETURN or ABEND macro instruction that specified a
completion code. This completion code satisfied a condition
test specified by a code and operator subparameter in the
COND parameter of the JOB statement.
Note: This message does not appear if the condition code
from the last step of the job satisfied a condition test.
System Action: The job was terminated, so the remaining
steps in the job were not executed.
Programmer Response: If termination was intentional, no
action is needed.
If termination was not intentional, do the followi~g:
• Correct the error that caused the completion code to be
issued by the problem program.
• Change the conditon test specified in the COND parameter
of the JOB statement, if the problem program contained no
errors.
• Submit for execution the remainder of the job, including the
problem program if.it contained an error.
Problem Determination: Table I, items 1, 2, 4, 7c, 29.
IEF2021
STEP - 'sss,' WAS NOT RUN BECAUSE OF cde
Explanation: If cde is CONDITION CODES, a problem program
terminated by issuing a RETURN macro instruction that
specified a completion code. This completion code satisfied a
condition test (specified by a code, operator, and job step
name subparameter) in the COND parameter of an EXEC
statement.
If cde is COND = ONLY, the COND parameter of an EXEC
statement specified ONLY, but no previous job steps had
abnormally terminated.
In the message text, sss is the job step name of the EXEC
statement containing the COND parameter.
System Action: The job step specified by the succeeding EXEC
statement was not executed. The remainder of the job was or
was not executed, depending on the condition tests specified
in the EXEC statement for each step.
Programmer Response: If termination was intentional, no
action is needed.
If termination was not intentional, do the following:
• Correct the error that caused the completion code to be
issued by the problem program.
• Change the condition test specified in the COND parameter
of the succeeding EXEC statement, if the problem program
contained no errors. Then execute the problem program, if
it contained an error, and the job step that was not
executed.
Problem Determination: Table I, items 1, 2, 4, 7c, 29.
IEF2091
VIRTUAL STORAGE UNAVAILABLE FOR jjj.sss.ppp
Explanation: During execution of a checkpoint restart for
procedure step ppp of step sss of job jjj, all or part of the
virtual storage for the restart job was not available for one of
the following reasons:
• A deferred restart was being performed but the virtual
storage area requested was larger than the area used
originally. Since the original area was adjacent to the link
pack area, the virtual storage area could not be increased.
• A deferred restart was being attempted on a different
system, or the same system, with different IPl parameters
such that the system queue area occupied part or all of the
required region area.
• A deferred restart was being performed, but after IPl the
link pack area had expanded into the required virtual
storage area.
System Action: Restart for job jjj is terminated.
Operator Response: Restart the system and run the job again.
During system initialization, specify the same options as those
used when the checkpoint was taken. If such a rerun fails or is
Section 9: IEF Messages - Job Scheduler
9-7
•
not feasible, report this message and circumstances to the
system programmer.
Programmer Response: Probable user error. Request the use
of a system known to be adequate for restart.
Problem Determination: Table I, items 1, 2, 7a, 29.
IEF2101
iii sss [ppp] ddn[ +xxx]- UNIT FIELD SPECIFIES
INCORRECT DEVICE NAME
Explanation: In a DO statement, the "unit name subparameter
in the UNIT parameter was invalid:
• The unit was not defined when the system was generated.
• If a cataloged data set was being referenced, the unit field
in the catalog entry is incorrect.
• No UNIT parameter was supplied for a non-cataloged,
non-passed data set.
In the message text, ddn is the data definition name in the
name field of the DO statement.
System Action: The job was terminated.
Programmer Response: Probable user error. Correct the unit
name subparameter, and submit the job again.
Problem Determination: Table I, items 1, 2, 4, 7c, 29.
IEF2111
jjj sss [ppp] ddn[ +xxx] - DATA SET RESERVATION
UNSUCCESSFUL
Explanation: During allocation processing, data set reservation
for a data set name was unsuccessful. The data set name type
was a non-VIO, temporary, direct access data set name
specified by user or one of the following situations occurred.
These situations involve an attempt at data set reservation for
a cataloged data set which, when located in a catalog, was
found to have a name different from that specified by the
user:
• REAL name of a data set for which the user specified an
alias.
• Catalog-generated name for a relative GOG specified by the
user.
• Each catalog-generated name for a GOG when user
requests all levels of the GOG.
System Action: The job was terminated.
Programmer Response: Probable conflict in use (share vs.
exclusive) of data set. Resubmit the job for processing.
Problem Determination: Table I, items 1, 2, 3, 4, 7c, 25d, 29.
IEF2121
jjj sss [ppp] ddn[ +xxx] - DATA SET NOT FOUND
Explanation: In processing a DO statement, the job scheduler
found one of the following:
• The data set name in the DSNAME parameter did not
contain all the levels of qualification, making it impossible to
locate the cataloged data set.
,
• The DCB parameter or the REF subparameter of the
VOLUME parameter contained invalid information.
• The data set was not cataloged or passed.
• A level of index was either missing or incorrect in a
gene~ation data group.
• In a step, an attempt was made to receive a passed data
set. However, a data set with the same name was
previously received in this step.
• A data. set catalogued in a user catalog was requested and
there was no JOBCAT or STEPCAT DO in the JCL.
In the message text, ddn is the data definition name in the
name field of the DO statement.
System Action: The job was terminated.
Programmer Response: Probable user error. If the data set
name was specified incorrectly, correct it. If the DCB or
VOLUME parameters were incorrect, correct them. If the data
set was not cataloged, either catalog it or, on the DO
statement, specify the volume serial number of the volume on
which the data set resides. But, if the DO statement was
correct, recatalog the data set.
Problem Determination: Table I, items 1, 2, 4, 7c, 25d, 29.
9-8
VS2 System Messages (VS2 Release 3.7)
IEF2131
jjj sss [ppp] ddn[ + xxx] - UNDETERMINED ERROR
PROCESSING CATALOGED DATA SET
Explanation: During allocation processing, an undetermined
error was received from catalog management while attempting
to retrieve volume and unit information for the data set name
specified on DO statement ddn.
System Action: The job was terminated.
Operator Response: Probable system error. Report this
message to the system programmer.
Problem Determination: Table I, items 1, 2, 3, 4, 7c, 25d, 29.
IEF2171
jjj sss [ppp] ddn[ + xxx] - VOLUME CONTAINING
PATTERN DSCB NOT MOUNTED
Explanation: In a DO statement, the data set name in the DCB
parameter specified a data set on a volume that was not
mounted when the job was to be executed.
In the message text, ddn is the data definition name in the
name field of the DO statement.
System Action: The job was terminated.
Programmer Response: Probable user error. Resubmit the job,
"'aking sure that the volume containing the data set is
mounted before the job step is to be executed.
Problem Determination: Table I, items 1, 4, 7c, 25b, 29.
IEF2181
iii
sss [ppp] ddn[ + xxx] - PATTERN DSCB RECORD
NOT FOUND IN VTOC
Explanation: In a DO statement, the data set name in the DCB
parameter specified a data set that did not exist in the
volumes specified or a model DSCB did not exist on the
catalog volume for a GOG request.
In the message text, ddn is the data definition name in the
name field of the DO statement.
System Action: The job was terminated.
Programmer Response: Probable user error. Check the volume
table of contents (VTOC) for the data set control block (DSCB)
specified in the DCB parameter on the volume pointed to by
the catalog. If the request is for a generation data group
member, check the catalog volume VTOC for a DSCB for the
GOG group. Correct the error and rerun the job.
Problem Determination: Table I, items 1, 4, 7c, 25b, 29.
IEF2191
iji sss [ppp] ddn[ +xxx] - GOG GROUP NAME
EXCEEDS 35 CHARACTERS
Explanation: In DO statement ddn, the data set name in the
DSNAME parameter was a generation data group (GOG) name
longer than the maximum length of 35 characters. The extra
length made it impossible to obtain the data set name's final
qualifications from the catalog.
in the message text, +xxx refers to the relative position of a
concatenated DO to the first DO for the concatenated group.
System Action: The job was terminated.
Programmer Response: Probable user error. Change the
generation data group name so that it does not exceed 35
characters, and rerun the job.
Problem Determination: Table I, items 1, 4, 7c, 25b, 29.
jjj sss [ppp] - PGM = *.00 - REFERENCED STEP
WAS NOT EXECUTED - OR DATA SET TYPE INVALID
Explanation: In an EXEC statement, the name of the program
to be executed was specified by a reference to the data
definition name of a DO statement in a previous step of the
job. One of the following occurred:
• The previous step, which contained the DO statement, was
not executed because a condition test specified in the
COND parameter of the step's EXEC statement was satisfied.
• The data set was not direct access or virtual access, or it
was a subsystem data set (SYSIN, SYSOUT, etc.).
System Action: The job is terminated.
Programmer Response: Probable user error. In the EXEC
statement that refers to the DO statement in the previous
step, include the condition tests specified in the previous
IEF2211
step's EXEC statement or make sure that the data set is direct
access or virtual access and not a subsystem data set. Then
rerun the job.
Problem Determination: Table I, items 1, 3, 4, 7c, 29.
IEF225D
SHOULD jjj.sss.ppp [checkid] RESTART
Explanation: Automatic restart was requested by procedure
step ppp of step sss of job iii and one of the following
occurred:
• The step was abnormally terminated with a completion code
that makes the step eligible to be restarted.
• The system failed.
If the checkpoint identification, checkid, is omitted in the
message text, step restart was requested; if the checkpoint
identification is present, checkpoint restart was requested.
Operator Response: If the checkpoint identification is the same
as in a previous request for a restart by the same job, and if
the job was previously terminated with the same completion
code, it may be desirable to prevent another restart at the
same checkpoint. Enter one of the following replies:
• REPLY xx, 'YES' if automatic restart is to be authorized.
• REPLY xx, 'NO' if automatic restart is to be denied, thus
causing the system to dispose of data sets as if restart had
not been requested.
• REPLY xx,'HOLD' if the job· is to be held until the operator
issues a RELEASE command, at which time automatic
restart will be performed. (If it is desired to terminate the
job, the CANCEL command should not be issued until after
the RELEASE command has been issued.)
IEF2291
~)
y
LRECL EXCEEDS 32K
Explanation: The variable record extension (VRE) input or
output logical record length exceeds 32,760 bytes. The output
data set records were defined as variable spanned with
machine code control characters, but the input records did not
contain machine code control characters.
System Action: The External Writer closes its SYSOUT data set
and ceases processing.
Programmer Response: If it is necessary to process records
with a length greater than 32K bytes, do not request control
characters for the External Writer's output data set unless
control characters have been included in the input records.
Problem Determination: Table I, items 1, 2, 3, 13, 15, 29.
IEF233A
M ddd,ser,[labtyp],
~
jjj,sss
jjj
{ !!!,sss,dsn
JlJ"dsn
Explanation: M indicates that a volume is to be mounted on
device ddd. The volume is required by job iii or, if applicable,
step sss of job jjj. (If this message is issued for a system task,
sss will appear as a system task identifier.)
If a MONITOR DSNAME command is active, the name, dsn, of
a nontemporary data set requiring the volumes is also
specified in the message text. The data set name will not be
specified for data sets being deleted. If the data set name
causes the message to exceed 70 characters, the data set
name will appear on the second line of the message text.
• If ser is a 6-digit serial number, the volume with that serial
number is to be mounted on device ddd.
• If ser is SCRTCH, a scratch volume is to be mounted. The
scratch tape volume must have the type of label specified
by labtyp: SL for standard label or standard user label, NSL
for non-standard label, or NL for no label or by-pass label.
• If ser is PRIVAT, a scratch volume is to be mounted. It will
be marked PRIVATE and demounted at the end of job iii.
• If ser begins with L, the volume to be mounted is unlabeled·
the number after the L is an internal serial number assigned
by the system to an unlabeled volume and is of the form
xxxyy, where xxx is the data set number and yy is the
volume sequence number for the data set.
System Action: The task waits fot the volume to be mounted
if the device is direct access. If a scratch volume is to be
mounted, all other jobs requiring the same device group will
not be allocated until the operator responds to this message.
Operator Response: For tape, if ser is SCRTCH, make sure that
the file protect ring has been inserted in the volume.
Mount volume ser on the device; then ready device ddd. If a
mount is requested for a device with non-removable volumes,
ready the device in order to indicate that the volume is
mounted. If the volume cannot be mounted, enter a CANCEL
command to terminate job iii. Separate commands are
necessary to cancel all jobs requiring volume ser.
IEF233D
M ddd,ser,[labtyp],
jjj,sss
m
jjj,sss,dsn
{ jjj"dsn
1
OR RESPOND TO IEF455D MESSAGE
Explanation: M indicates that a volume is to be mounted on
device ddd. The mount is required for a dynamic allocation for
step sss of job iii.
If a MONITOR command is active, the name, dsn, of a
nontemporary data set requiring the volume is also specified in
the message text. The data set name will not be specified for
data sets being deleted. If the data set name causes the
message to exceed 70 characters, the data set name will
appear on the second line of the message text:
• If ser is a 6-digit serial number, the volume with that serial
number is to be mounted on the device.
• If ser is SCRTCH, a scratch volume is to be mounted. A
scratch tape volume must have the label type specified by
labtyp: SL for standard label or standard user label, NL for
no label or bypass label, or AL for ANSI label.
• If ser is PRIVAT, a private volume is to be mounted.
• If ser begins with an L, the volume to be mounted is
unlabeled. The number after the L is an internal serial
number assigned by the system in the form of xxxyy, where
xxx is the data set number and yy is the volume sequence
number for the data set.
System Action: The task waits for the volume to be mounted
or for the operator to reply NO to message IEF455D. The job
will not proceed until the operator responds to this message.
Operator Response: If the required volume is available, mount
it and ready device ddd. If a mount is requested for a device
with a non-removable volume, ready device ddd .
For tape, if ser is SCRTCH or PRIVAT, make sure the file
protect ring has been inserted in the volume.
If for any reason the volume cannot be mounted, reply NO. A
reply of NO to this message also serves as a reply of NO to
any other mount message for step sss of job iii.
IEF234E
{~} ddd
[,er
{
PVT}, { !!!
}] [,SPACE
PUB
JJJ,sss
STR
= prm]
Explanation: K indicates that the volume is to be demounted
and returned to the library. R indicates that the volume on
device ddd is to be demounted and retained near the
computer for use in the near future; o indicates that the
volume is to be demounted and used subsequently as a
scratch volume:
• If ser is a 6-digit number, it is the serial number of the
volume, which contains labels.
Section 9: IEF Messages - Job Scheduler
9-9
•
• If ser begins with L, the volume to be demounted is
unlabeled; the number after the L is an internal serial
number assigned by the system to an unlabeled volume and
is of the form xxxyy, where xxx is the data set number and
yy is the volume sequence number for the data set.
• If ser is absent from the message text, the volume is
unlabeled and is not being passed between job steps.
• PVT, PUB, and STR refer to the type of volume that was
used: private, public or storage.
If a DISPLAY SPACE command is active, the field
SPACE = cccc,tttt,aaaa/yyyy,zzzz is specified where:
cccc
Is the total number of free cylinders on the volume.
tttt
Is the total number of tracks in addition to the free
cylinders.
aaaa
Is the areas or extents dividing the cylinders and tracks.
yyyy
Is the maximum number of contiguous free cylinders of the
largest extent within the total remaining space.
zzzz
Is the number of tracks in addition to the free cylinders of
the largest extent within the total remaining space.
If an error occurred during the listing of the parameters in the
SPACE field, one of the following messages is specified:
• LSPACE-PERMANENT I/O ERROR
• LSPACE-NON-STANDARD OS VOLUME
• LSPACE-NOT A DIRECT ACCESS VOL
• LSPACE-INVALID PARAMETER
• LSPACE-UCB NOT READY
In the message text, jobname jjj may appear and step name
sss will be given if a stepname was specified on the EXEC
statement.
This message can occur if the volume does not have enough
available space to meet an allocation request or if a data set
already on the volume has the same name as the data set for
which space is to be allocated.
System Action: The system will name the device as 'not
READY'.
Operator Response: Demount the volume.
If K appeared, demount the volume and return it to the library.
If 0 appeared in the message text, use the volume later when
a scratch volume is requested.
If R appeared, retain the volume near the computer. If it is not
externally marked with its serial number, mark the 6-digit or
internally assigned number on the volume. (The internally
assigned number should appear externally on the volume in
case a subsequent step needs the volume; for the subsequent
mounting, the system will specify the volume by the internally
assigned number.) In the message, jjj is the name of the job
which needs the unit. When the job that has allocated the
retained volume ends, message IEF4711 will be issued listing
all retained volumes no longer needed by the job.
Problem Determination: If an error occurs again during the
listing of the parameters in the SPACE field, see Table I, items
2, 7c, 29.
IEF235D
III
555 WAITING FOR VOLUMES, TO CANCEL WAIT
REPLY 'NO'
Explanation: The system was unable to satisfy the volume
requests for a data set in step sss of job jjj.
System Action: The initiator for step sss will enter a wait state
until the requested volumes have been unallocated by
terminating tasks and are available for use. Other jobs
requiring the same volumes caflnot go through allocation until
9-10
VS2 System Messages (VS2 Release 3.7)
this wait has terminated and current allocation processing has
completed.
Operator Response: If desired, reply 'NO' to cancel the wait. If
the allocation was requested on a DO statement, the job will
be terminated. If the allocation was requested dynamically, a
return code will indicate to the requestor, that it was not
successful.
IEF2361
ALLOC. FOR jjj sss [ppp]
Explanation: This message identifies the job step and, if
applicable, the cataloged procedure for which devices were
being allocated. The IEF2371 messages, which follow this
message, describe the device allocations.
The devices were allocated for step sss of job jjj or for
cataloged procedure ppp, which was executed by step sss of
job jjj.
In response to a MONITOR JOBNAMES command, this
message will appear on the console only for the unit record
devices being allocated.
Operator Response: None.
IEF2371
ddd ALLOCATED TO ddn
Explanation: Device ddd is allocated to the data set defined in
the DO statement whose name field contains ddn.
If ddd is DMY, then a DO DUMMY was allocated. If ddd is JES,
a SYSIN or SYSOUT data set was allocated. If ddd is VIO, a
paging space data set was allocated. If ddd is TRM, a terminal
was allocated. If ddd is QNM, a QNAME data set was
allocated.
In response to a MONITOR JOBNAMES command, this
message will appear on thsconsole (only) for the unit record
devices allocated to data sets.
Operator Response: Check the unit record device to make sure
it is ready and has the proper input decks, cards, or forms.
IEF238D
jjj - REPLY [DEVICE NAME][,] ['WAIT'] OR
'CANCEL'
Explanation: The system cannot complete the allocation for
the current step of job jjj with the devices currently available.
Devices are needed for one or more of the DO statements in
the step for one of the following reasons:
• The DO statement specifically requested a unit or volume
which is currently allocated to another job and is not
shareable with this job.
• The devices which could be allocated for this DO statement
are not online and/or they are currently in use by another
job and are not shareable with this job.
This message permits the operator to respond to preceding
message IEF488 I or IEF489 I (and IEF2471).
System Action: The system action depends on the operator's
response as follows:
• A reply of WAIT requests the system to suspend processing
for this job until the required units and/or volumes are
released. The wait will not take effect, however, until all DO
statements that require devices for case two above have
been processed and the operator has responded to
message IEF433D. Message IEF4891 will be issued (or
repeated) for any remaining DO statements, followed by
message IEF2471 (if applicable) and this message.
• A reply of a device name that appeared in the device list of
message IEF247 I will cause the system to place the device
online and attempt to allocate using this device.
• A reply of CANCEL will cause the system to terminate the
job without further attempts to complete the allocation.
If the reply was not valid for the options given in this message,
message IEF4901 is issued and this message repeated.
/1..~
Operator Response: Refer to the installation procedure, choose
one of the options given in this message, and enter the
appropriate response as follows:
• REPLY xx, 'ddd', where ddd is a device address that
appeared in message IEF2471 and can be brought online. If
device ddd was listed as NOT ACCESSIBLE, a VARY .
CPU/CH/PATH command must precede the ddd response.
(The DISPLAY MATRIX command will provide information
concerning CPU and channel status.)
• REPLY xx,'WAIT' to cause the system to wait for devices
and/or volumes to be freed.
• REPLY xx, 'CANCEL' to terminate the job.
Note: One of the replies to to this message must be entered
before processing continues for this job. Although a CANCEL
command may be issued, the command will not take effect
until all the DO statements that still need devices have been
processed. (The reply may be specified in either upper-case or
lower-case letters.)
IEF2401
jjj 555 [ppp] - TASK I/O TABLE EXCEEDS 32K
IEF2441
[l
jjj
[ppp] - UNABLE TO ALLOCATE nnn UNIT(S)
AT LEAST nnn ALLOCATED UNIT(S) NEEDED
AT LEAST nnn OFFLINE UNIT(S) NEEDED
AT LEAST nnn ALLOCATED AND nnn OFFLINE
UNIT(S) NEEDED
555
}J
Explanation: The allocation for step sss of job jjj cannot be
completed with' the devices currently available (online and not
allocated). To recover from this situation a total of nnn units
must be varied online and/or become unallocated. Note that
this total may include allocated units containing volumes which
must be moved to an eligible unit to satisfy the allocation
requirements for this step.
If the second line of the message appears the system has
determined the minimum number of allocated and/or offline
units required.
System Action: The system issues more detailed messages
about each of the DO statements in this step that require
further allocation action. Messages IEF4881, IEF4891, and
IEF2471 can be issued following this message.
Operator Response: None.
Explanation: The Task I/O Table (TIOT), a system table built
'~
)
for each step, containing an entry for each DO statement and
for each unit associated with a DO statement, has exceeded its
maximum allowable size. The maximum number of DO
statements per step is 1635, if each is associated with only
one unit. The maximum is less if DO statements are associated
with multiple units. See the publication VS2 System
Programmer Library: Control Program Services for a discussion
of the TIOT size algorithm.
The maximum may be exceeded either because too many DO
statements and units are explicitly requested in the step JCL,
or because .the system has generated DO statements and units
beyond what is explicitly requested.
Additional DO statements are generated when:
• All members of a generation data group are requested. A
DO statement is generated for each member.
• A private catalog is needed to locate or catalog data set~ A
DO statement is generated for the catalog if it Wi;lS not
defined in a JOBCAT or STEPCAT DO statement.
• A VSAM data set requires multiple device types. A DD
statement is generated for each additional device type.
• JOBCAT or JOBUB DO statements are associated with the
step. DO statements are generated for either.
The system sometimes increases the total number of units
associated with a step by overriding JCL requests for volumes
to share the same unit. This occurs when one of the volumes
is not eligible for demounting:
• A volume has the permanently resident or reserved
attribute.
• A volume is required by multiple DO statements (unless
UNIT = AFF is specified for tape devices.)
System Action: The job is terminated.
Programmer Response: The total number of DO statements
and units for the step must be reduced. If all data sets are not
needed simultaneously, consider using dynamic allocation
facilities.
Problem Determination: Table I, items 1, 3, 4, 7c, 13, 29.
IEF2421
ALLOC. FOR jjj 555 [ppp] AT ABEND
Explanation: In the JOB statement, the allocation
MSGLEVEL = 0 was specified.
System Action: Since the problem program failed during
execution, the system has overridden the previous specification
and has assumed MSGLEVEL = 1.
Unit allocation messages IEF2371 will follow this message.
Programmer Response: None.
IEF2451
jjj S5S [ppp] ddn[ +xxx] - INCONSISTENT UNIT
NAME AND VOLUME SERIAL
Explanation: In a DO statement, the UNIT parameter specified
a device type; either the SER sub parameter of the VOLUME '
parameter specified the volume serial number of a volume that
was mounted on a device of a type inconsistent !lith the
device specified, or it specified the same volume serial number
as another DO statement but an inconsistent device type.
In the message text, +xxx refers to the relative position of a
concatenated DO in relation to the first DO in the
concatenated group ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Correct the
erroneous parameter, and submit the job again.
Problem Determination: Table I, items 1, 3, 4, 7c, 29.
IEF2461
jjj SS5 [ppp] ddn[ +xxx] - INSUFFICIENT SPACE ON
STORAGE VOLUMES
Explanation: In a DO statement that requires a storage volume
the SPACE parameter requested a greater quantity of tracks
than was available on any eligible direct access storage
volume.
In the message text, +xxx refers to the relative position of a
concatenated DO in relation to the first DO in the
concatenated group ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Check the track
quantity of the SPACE parameter for validity. If it is incorrect,
change it. Then submit the job again. Notify a system
programmer at your installation of the problem.
IEF2471
jjj ALLOCATION RECOVERY
[jjj ddd-list OFFLINE]
jjj ddd-list NOT ACCESSIBLE
Explanation: The system was unable to allocate a device to a
data set, as required for job jjj, and is attempting allocation
recovery. In the message text, ddd-list is a listing of the
devices.
In any system, device *ddd is a device that is pending offline
but which is currently online and possibly allocated to another
job. If the operator replies to message IEF238D with this
device address, the device will be allocated to job jjj only if
that device is eligible. When the device is not eligible, the
message sequence IEF2471 and IEF238D will be repeated if
there is another device offline or pending offline. Note: A reply
Section 9: IEF Messages - Job Scheduler
9-11
•
of a device that is pending offline (to message IEF238D)
counteracts the previously issued vary offline command.
In any system, device ddd could be allocated if the operator
could vary its status from offline to online.
In the message text, the first line always appears. The second
line appears for eligible devices that are currently offline or
that are pending offline (that is, devices which a VARY offline
command has recognized' but has not completely processed, in
which case ddd is preceded by an asterisk (*); this line may
appear more than once. The third line appears for eligible
devices that are hierarchically offline (paths or CPU is offline);
this line may appear. more than once.
System Action: The system action depends on the operator
response to message IEF238D, which follows this message.
Operator Response: Respond as indicated for message
IEF238D, which follows this message.
Note: If you want to bring one of the devices that was listed
as not accessible, online, you must issue the appropriate VARY
command to bring the CPU or path to the device online before
replying to message IEF238D.
Programmer Response: If the job was terminated, make any
changes indicated by other messages, and submit the job
again.
IEF2511
IEF2511
Hi
iii
sss [ppp] - JOB CANCELLED (in SYSOUT)
JOB CANCELLED (on console)
Explanation: In response to a CANCEL command or a CANCEL
response to message IEF238D, the system terminated job iii.
In the'SYSOUT message text, sss refers to the step and ppp to
the cataloged procedure under which the job was running.
Programmer Response: Correct any errors indicated by any
other messages, and submit the job again.
Operator Response: None.
IEF2531
iii
sss [ppp] ddn[ +xxx] - DUPLICATE NAME ON
DIRECT ACCESS VOLUME
Explanation: In DO statement ddn, the data set name in the
DSNAME parameter was the same as a data set name already
in the volume table of contents (VTOC) for the requested
direct access volume.
In the message text, +xxx refers to the relative position of a
concatenated DO in relation to the first DO in the
concatenated group ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. If the data set
being specified is a new data set, select a unique name for it.
If the DO statement intended to specify the data set that is
already on the direct access device, specify the OLD, SHR, or
MOD subparameter in the DISP parameter. Then submit the
job again.
Problem Determination: Table I, items 1, 3, 4, 7c, 25b, 29.
IEF2541
jjj sss [ppp] ddn[ +xxx] - NO SPACE IN VTOC
Explanation: DO statement ddn requested space on a direct
access volume for a new data set. The volume table of
contents (VTOC) for the requested volume did not have the
minimum number of format 0 data set control blocks '(DSCB)
required to allocate the data set.
In the message text, +xxx refers to the relative position of a
concatenated DO in relation to the first DO in the
concatenated group ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Submit the job
again, requesting space on a different volume.
Problem Determination: Table I, items 1, 3, 4, 7c, 25b, 29.
9-12
VS2 System Messages (VS2 Release 3.7)
IEF2561
iii
sss [ppp] ddn[ + xxx] - ABSOLUTE TRACK NOT
AVAILABLE
Explanation: In DO statement ddn, the ABSTR subparameter of
the SPACE request is asking that the data set be allocated in
absolute tracks. The requested tracks are not available.
In the message text, +xxx refers to the relative position of a
concatenated DO in relation to the first DO in the
concatenated group ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Check the
beginning track address and quantity subparameters for
validity. If they are correct, request different tracks or a
different volume. Then resubmit the job.
Problem Determination: Table I, items 2, 7c, 25a, 29.
IEF2571
jjj sss [ppp] ddn[ +xxx] - SPACE REQUESTED NOT
AVAILABLE
Explanation: In DO statement ddn, the SPACE parameter
requested a greater quantity of tracks than was available on
the direct access volume requested.
In the message text, +xxx refers to the relative position of a
concatenated DO in relation to the first DO in the
concatenated group ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Check the track
quantity of the SPACE parameter for validity. If it was
incorrect, change it. If it was correct, change the request to a
different volume. Then submit the job again.
Problem Determination: Table I, items 1, 3, 4, 7c, 25b, 29.
IEF2581
iii
sss [ppp] ddn[ +xxx] - INVALID RECORD LENGTH
SPECIFIED IN SPACE PARAMETER
Explanation: In DO statement ddn, the average record length
subparameter in the SPACE parameter specified a length
greater than the capacity of a track on the requested direct
access device or volume.
System Action: The job is terminated.
Programmer Response: Probable user error. Reduce the
lengths of the records to make the average length no greater
than the track capacity of the device or specify a device with a
greater track capacity. Then submit the job again.
Problem Determination: Table I, items 1, 3, 4, 7c, 29.
IEF2601
iii
sss [ppp] ddn[ +xxx] - WRONG DSORG OR DISP
Explanation: During allocation of an indexed sequential data
set, one of these error conditions was detected:
• A DO statement requiring that direct access space be
obtained was found concatenated to a DO statement that
indicated that the data set already existed.
I
Example: A concatenated DO statement specifies
DISP = (NEW,KEEP), and a preceding DO statement for an
ISAM data set specified DISP = (OLD, KEEP). Note that
secondary dispositions are not checked for consistency.
• A DO statement specifying DSORG = IS or ISU was found
concatenated to a DO statement (for the same data set)
that specified a DSORG other than IS or ISU.
• A unit other than direct access was specified on a DO
statement that specified DSORG = IS or ISU. ISAM data sets
can reside only on direct access devices.
In the message text, +xxx refers to the relative position of a
concatenated ISAM DO statement in relation to the first DO for
the ISAM data set ddn.
System Action: The job is terminated.
Programmer Response: Correct the DISP or DSORG
parameters that are in error and run the job again.
Problem Determination: Table I, items 2, 7c, 29.
IEF2611
iii
sss [ppp] ddn[ +xxx] - NO PRIME AREA REQUEST
FOR ISAM DATA SET
Explanation: None of the 00 statements defining an indexed
sequential data set specify DSNAME = name(PRIME).
In the message text, +xxx refers to the relative position of a
concatenated ISAM DO statement in relation to the first DO for
the ISAM data set ddn.
System Action: The job is terminated.
Programmer Response: Supply a DO statement that specifies
DSNAME = name(PRIME). List the volume table of contents
(VTOC) of each volume involved using the LlSTCAT command.
If the name of the data set appears in any VTOC, remove it
using the DEFINE and DELETE commands. Then rerun the job.
Problem Determination: Table I, items 1, 4, 7c, 14, 29.
IEF2621
iii
sss [ppp] ddn[ +xxx] - PRIME AREA MUST BE
REQUESTED BEFORE OVFLOW
Programmer Response: Probable user error. Eliminate one of
the duplicating DO statements. List the volume table of
contents (VTOC) of each volume that will contain the data set
using the L1STCAT command. If ~he name of the data set
appears in any VTOC, remove it using the DEFINE and DELETE
commands. Then rerun the job.
Problem Determination: Table I, items 2, 7c, 14, 29.
IEF2661
have been zeroed.
In the message text, +xxx refers to the relative position of a
concatenated DO in relation to the first DO in the
concatenated group ddn.
System Action: The job is terminated.
Programmer Response: Probable system error. Rerun the job.
Problem Determination: Table I, items 1, 4, 7c, 29.
Explanation: The control program is unable to allocate the
overflow area of a new indexed sequential data set because
the overflow area request appears before the prime area
request. That is, the control program read the DD statement
specifying DSNAME = name(OVFLOW) before the DO statement
specifying DSNAME = name(PRIME).
In the message text, +xxx refers to the relative position of a
concatenated ISAM DO statement in relation to the first DO for
the ISAM data set ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Insert the DO
statement specifying DSNAME = name(PRIME) before the DO
statement specifying DSNAME = name(OVFLOW). List the
volume table of contents (VTOC) of each volume that will
contain the data set using the LlSTCAT command. If the name
of this data set appears in any VTOC, remove it using the
DEFINE and DELETE commands. Then rerun the job.
Problem Determination: Table I, items 1, 2, 4, 7c, 14, 29.
IEF2631
iii
sss [ppp] ddn[ +xxx] - SPACE REQUEST WRONG
- MUST BE ON CYLINDER BOUNDARY
Explanation: The SPACE parameter of a DO statement defining
an indexed sequential data set is incorrect. In the absolute
track request (ABSTR), the beginning address subparameter
does not specify a cylinder boundary, or it does not specify, in
tracks, an integral number of cylinders.
In the message text, +xxx refers to the relative position of a
concatenated ISAM DD statement in relation to the first DD for
the ISAM data set ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Correct the
absolute track subparameter. List the volume table of contents
(VTOC) of each volume that will contain the data set, using the
L1STCAT command. If the name of this data set appears in any
VTOC, remove it using the DEFINE and DELETE commands.
Then rerun the job.
Problem Determination: Table I, items 2, 7c, 14, 29.
IEF2641
iii
sss [ppp] ddn[ +xxx] - DUPLICATION OF THE
DSNAME ELEMENT INVALID - SAME AREA
REQUESTED TWICE
Explanation: Two DO statements defining the same indexed
sequential data set are ,requesting space for the same area.
Both DO statements specify the same element in the DSNAME
parameter.
In the message text, +xxx refers to the relative position of a
concatenated ISAM DO statement in relation to the first DO for
the ISAM data set ddn.
System Action: The job is terminated.
jjj sss [ppp] ddn[ +xxx] - INVALID JFCB POINTER
Explanation: During allocation, a JFCB pointer was found to
IEF2671
iii
sss [ppp] ddn[ +xxx] - DIRECTORY SPACE
REQUEST IS LARGER THAN PRIMARY REQUEST
~xplanation:
In DD statement ddn, the space requested for the
directory was not allocated because the directory quantity
subparameter of the SPACE parameter requested more space
than the primary quantity subparameter.
In the message text, +xxx refers to the relative position of a
concatenated DO in relation to the first DO in the
concatenated group ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. Reduce the
directory quantity subparameter, or increase the primary
quantity subparameter. Then rerun the job.
Problem Determination: Table I, items 1, 3, 4, 7c, 25b, 29.
IEF2721
jjj sss [ppp] - STEP WAS NOT EXECUTED
Explanation: The control program did not execute step sss of
job Hi or cataloged procedure step ppp, for one of the
following reasons:
• An error appeared in a job control statement.
• A previous step abnormally terminated, but the current step
did not specify EVEN or ONLY in the COND parameter of
the EXEC statement.
• The step was being executed or terminated when system
restart was required. To confirm this reason, look for
message IEF2361 (ALLOCATION FOR jjj sss [ppp]) in the
system output listing following SYSOUT data set information
or following duplicatb allocation messages for the step.
• The job step required input/output devices, volumes, or
space that could not be allocated.
• The job containing the job step was cancelled by the
operator before the job step was initiated. To confirm this,
look for message IEF4501 on the console listing with a 222
ABEND.
System Action: When a job control statement contained an
error or where allocation could not be made, the job was
terminated.
Where system restart was required, the remainder of the steps
in the job were not executed.
Programmer Response: Probable user error. Correct any
errors, and submit the job or job step again.
Problem Determination: Table I, items 1, 3, 4, 7c, 29.
IEF2731
jjj sss [ppp] ddn[ +xxx] - INVALID USER LABEL
REQUEST
Explanation: In DO statement ddn, a user label track was
requested for a data set. However, the control program was
unable to allocate space for the data set for one of the
Section 9: IEF Messages - Job Scheduler
9-13
VS2.03.804
following reasons:
• The DSORG subparameter of the DCBparameter specified
PO or IS.
• The SPACE parameter included a directory quantity
subparameter.
In the message text, +xxx refers to the relative position of a
concatenated DO in relation to the first DO in the
concatenated group ddn.
System Action: The job is terminated.
Programmer Response: Probable user error. 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.
Problem Determination: Table I, items 1, 3, 4, 7c, 29.
IEF28I1
ddd NOW OFFLINE
Explanation: In response to a VARY command, device ddd has
been placed offline.
System Action: Processing continues.
Operator Response: None.
IEF2821
ddd NOW UNLOADED
Explanation: In response to an UNLOAD command, the system
has unloaded a volume from device ddd.
System Action: Processing continues.
Operator Response: None.
IEF2831
dsn NOT DELETED rc
VOL SER NOS = ser [z],ser [z],ser [z],ser [z],ser [z]
VOL SER NOS = ser [z],ser [z],ser [z].
Explanation: A DO statement specified DELETE as the
disposition of data set dsn, but the data set was not deleted
from the volumes whose serial numbers, ser, are listed in the
message text.
If the data set was not deleted from any of its volumes, the
volumes listed are all of the volumes on which the data set
resides. If the data set was partially deleted, message IEF2851
precedes this message in the SYSOUT data set and lists the
volumes from which the data set was deleted.
• If ser is 'a 6-digit number, it is the serial number of the
volume, which contains labels.
• If ser begins with a slash or L, the volume is unlabeled; the
number after the slash or L is an internal serial number
assigned by the system to an unlabeled volume. If ser
begins with L, the number after the L is of the form xxxyy,
where xxx is the data set number and yy is the volume
sequence number for the data set.
Five volume serial numbers are listed per line until all the
volumes involved are listed. The last volume serial number is
followed by a period.
The I-digit code, rc, explains why the data set was not
deleted.
rc
1
4
5
6
9·14
Explanation
The expiration date had not occurred. When the data
set was created, the expiration date was specified by
the EXPDT or RETPD subparameter in the LABEL
parameter of the DO statement.
No device was available for mounting during deletion.
Too many volumes were specified for deletion;
because of this, not enough storage was available to
perform the specified deletion. Deletion may be
accomplished in several job steps by specifying some
of the volume serial numbers in each step.
Either no volumes were mounted or the mounted
volumes could not be demounted to permit the
remaining volumes to be mounted.
VS2 System Messages :< or a DO DATA statement in an instream procedure.
• A null statement or a delimiter.
System Action: The job is terminated. The remaining job
control statements for the job were scanned for; syntax errors.
Programmer Response: Probable user error. Correct the
procedure by removing the invalid card. The invalidc~ud will
appear in the SYSOUT listing immediately before the error
message if MSGLEVEL = 1 is coded on the job statement.
Rerun the job.
Problem Determination: Table I, items 1, 3, 4, 7c, 29.
INCORRECT VOLUME LABEL OR I/O ERROR
Explanation: An error occurred when a volume label was being
IEF6031
read. The error can be one of the following:
• An uncorrectable inputj output error occurred.
• An unlabelled tape was mounted before it had been
requested.
• A non-standard label tape was mounted but the user
non-standard label handling routine rejected the label or no
user non-standard label handling routine was provided.
System Action: The volume is unloaded and message IEF234E
is issued.
Operator Response: Probable user error. If an uncorrectable
inputjoutput error was the problem and the message recurs
for the same volume, make sure the label is correct.
If an unlabeled volume had been mounted before it was
requested, this is the problem. Do not remount the volume
until it is requested.
If a non-standard label volume was being used, check with a
system programmer at your installation to make sure that a
non-standard label handling routine exists, and if so, that the
label is correct.
Problem Determination: Table I, items 2, 7c, 29.
Explanation: An uncorrectable inputj output error occurred in
IEF5061
iii
sss [ppp] ddn[ + xxx] - NOT ENOUGH AVAILABLE
STORAGE VOLUMES. 'VOLUME = PRIVATE'
ASSUMED.
Explanation: DO statement ddn of step sss of job
iii, or
cataloged procedure step ppp, requested allocation of space
for a new data set on a non-private volume; the statement did
not specify a volume serial number.
There were not enough storage volumes to satisfy the request.
The data set is allocated to a private volume.
9-24
VS2 System Messages (VS2 Release 3.7)
PROCLIB DEVICE I/O ERROR READING .FOR JOB
reading the procedure library (SYS1.PROCUB) during
processing of a job that requested a cataloged procedure.
System Action: The job being processed was terminated. The
job scheduler also wrote message IEF4171 on the console; in
response, the operator reentered the job through the input
stream.
Programmer Response: None.
IEF6051
UNIDENTIFIED OPERATION FIELD
Explanation: In a job control statement, either an operation
field could not be found or the operation field could not be
identified as JOB, EXEC, DO, or any valid operator command.
System Action: The job is terminated. The remaining job
control statements for the job were scanned for ~yntax errors.
Programmer Response: Probable user error. Check that the
operation field is spelled correctly and that it is· preceded and
followed by at least one blank .. After correcting the error,
submit the job· again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6061
MISPLACED DD STATEMENT
Explanation: A DO statement between· the JOB statement and:
first EXEC statement did not contain JOBUB or JOBCAT in. its
name field. Possibly, JOBUB or JOBCAT was misspelled or
mispunched. Possibly, the operation field of the first EXEC
statement w~s not correftly specified. .
.
System Action: The job 'is terminated. The remaining job
control statements for the job were scanned for syntax errors.
Programmer Response: Probable user error. Correct the DO or
EXEC statement, or place the DO statement in the job step in
which it belongs. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6071
JOB HAS NO STEPS
Explanation: The job control statements following a JOB
st~tement did not include an EXEC statement.
This message is also issued if the job contains a PROC
statement prior to any EXEC or SYSCHK DO statement but
contains no PEND statement.
System Action: The job is terminated. The remaining job
control statements for the job were scanned for syntax errors.
A dummy EXEC statement with EXECFAIL in its name field was
inserted.
If a PEND statement was omitted, the remainder of the job
was considered part of the in-stream procedure.
Programmer Response: Probable user error. Insert an EXEC or
PEND statement or correct an EXEC or PEND statement
containing errors that made it unrecognizable as applicable.
Submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6091
INVALID OVERRIDE KEYWORD xxx
Explanation: An EXEC statement containing a PROC parameter
specified two identical override keywords that both refer to the
same step in a cataloged or in-stream procedure.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control· statements for the job were scanned for syntax errors.
Programmer Response: Probable user error. Change the
override parameters. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6101
PROCEDURE HAS NO STEP
Explanation: The job control statements in a procedure did not
include an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job were scanned for syntax errors.
Programmer Response: Probable user error. Correct the
procedure by inserting an EXEC statement or correcting an
EXEC statement that contained errors that made it
unrecognizable. Submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6111
OVERRIDDEN STEP NOT FOUND IN PROCEDURE
a corresponding EXEC or DO statement in a cataloged or
in-stream procedure, specified a step name that could not be
found in the procedure. Probably, the step name was
misspelled or the DO override statements did not appear in the
same order as the corresponding statements in the procedure.
System Action: The job is terminated. The remaining job
control statements for the job were scanned for syntax errors.
Programmer Response: Probable user error. Correct the step
name in the EXEC or DO statement in the input stream, correct
the order of the step names in the EXEC statement in the
input stream, correct the order of the DO override statements
in the input stream, or correct the procedure. Then submit the
job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6121
PROCEDURE NOT FOUND
Explanation: The procedure specified in the first parameter of
an EXEC statement could not be found in the procedure library
(SYSl.PROCLlB) or in the in-stream procedure directory.
Possibly, the procedure name was misspelled or the PEND
statement ending the previous in-stream procedure was
omitted.
System Action: The job is terminated. The remaining job
control statements for the job were scanned for syntax errors.
Programmer Response: Probable user error. Correct the
procedure name in the EXEC statement in the input stream, in
the PROC statement in the input stream, or in the procedure
library. If the procedure name is correct, insert the missing
PEND statement. Also, check to make sure that the instream
procedure appears in the job before any of the EXEC
statements that call it. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6131
PROCEDURE WITHIN A PROCEDURE
Explanation: In a procedure, an EXEC statement contained a
PROC parameter or a procedure name, implying a procedure
within a procedure. A procedure cannot be specified within a
procedure.
System Action: The job containing the EXEC statement that
invoked the procedure is terminated. The remaining job control
statements for the job were scanned for syntax errors.
Programmer Response: Probable user error. Replace the
invalid EXEC statement with either (1) the procedure that it
called or (2) a valid EXEC statement containing a PGM
parameter. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6141
PROCLIB DEVICE I/O ERROR SEARCHING FOR
PROCEDURE
Explanation: An uncorrectable input; output error occurred in
searching the procedure library (SYSl.PROCLlB) during
processing of a job that requested a cataloged procedure.
System Action: The job being processed is terminated. The
job scheduler also wrote message IEF4171 on the console; in
response, the operator reentered the job through the input
stream.
Programmer Response: None.
IEF6151
EXCESSIVE PROCSTEP NAME xxx
Explanation: In an EXEC statement that specified a procedure,
the name of a step to be overridden was longer than 8
characters.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
Explanation: An EXEC or DO statement, which was to override
\
Section 9: IEF Messages - Job Scheduler
9-25
•
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the' error occurred. This phrase
usually occurs if the error was detected before any keyword
parameters were processed. (For' example, an error was
detected in the name field of a statement.)
• IN THEprm1 SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only, when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
,
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for, the job were scanned for syntax errors.
Programmer Response: Probable user error. Correct the step
name so that it consists of not more than 8 alphameric
characters, with the first character alphabetic. Then submit the
job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6161
SUBLIST WITHIN SUBLIST INCORRECT xxx
Explanation: In a job control statement, a subparameter list
was specified within a subparameter list. This arrangement is
invalid. Possibly, too many parentheses were used, so that'a
list appeared to be within a list.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error, occurred. This phrase
usually occurs if 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 prm1 SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword, parameter associated with major
keyword parameter prm2., (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if ~he error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the, field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job were scanned for syntax errors.
Programmer Response:' Probable user error. Correct the
subparameter. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
NO NAME ON FIRST DO STATEMENT AFTER EXEC
STATEMENT
Explanation: The first DO statement following an EXEC
statement did not contain a data definition name in its name
field; that is, column 3 of theDD statement was blank.
Possibly, the first statement for a concatenation of data sets
was omitted.
System Action: The job is terminated. The remaining job
control statements for the job were scanned for syntax errors.
Programmer Response: Probable user error. Either put a data
definition name in the name field of the DO statement or place
IEF6171
9-26
VS2 System Messages (VS2 Release 3.7)
it among other DO statements so that a proper concatenation
is defined. Then submit the job again.
'
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6181
OPERAND FIELD DOES NOT TERMINATE 'IN COMMA
OR BLANK
does
Explanation: In a job control statement, the operand field
not terminate with one of the following:
" ,
\
• A comma after the last parameter in the card image, ifthe
statement is to be continued in the next card image. The
comma must be before column 72.
• A blank after the last parameter, if the statement is not to;
be continued. The blank may be in column 72 or any
previous column.
System Action: The job is terminated. The remaining job
control statements for the job were' scanned for syntax errors.
Programmer Response: Probable user error. Correct the
operand field. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6211
EXPECTED CONTINUATION NOT RECEIVED
statem~nt, continuation was
indicated by a comma at the end of the operand or by a
nonblank character in column 72, or both. However, the
following card image was not a continuation.
System Action: The job is terminated. The remaining job
control statements for' the job were scanned for syntax errors.
Programmer Response: Probable user error. Provide the
missing continuation card, if it was lost. If no continuation was
intended, correct the card so that column 72 is blank and the
operand ends with a blank.
If the continuation card was present, correct it so that slashes
(f /) appear in columns 1 and 2, a blank' appears in column 3,
and the continuation of a comment begins anywhere after
column 3 or the continuation of the operand begins in columns
4 through'16.
Problem Determination: Table I, items 1, 4,7c, 29.
Explanation: In a job control
IEF6221
UNBALANCED PARENTHESIS xxx
Explanation: In a job control statement, one of the following
appeared:
• A valid left parenthesis not followed by a right parenthesis.
• A valid right parenthesis not preceded by a left parenthesis.
• A right parenthesis where it is not permitted~
In the message text, xxx is one of the following phrases:
• IN THE, prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prm1 SUBPARAMETER OF THE prm2 FIELD, where
prm1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)'
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement:
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the error.
Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6231
SOURCE TEXT CONTAINS UNDEFINED OR ILLEGAL
CHARACTERS xxx
Explanation: A job control statement contained one or more
invalid characters. All characters in a job control statement
must belong to the character sets defined in the publication
IBM System/360 Operating System: Job Control Language
GC28-6539.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prml is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: If the statement contains any invalid
characters, correct it. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6241
INCORRECT USE OF PERIOD xxx
Explanation: In a job control statement, a period appeared in a
parameter or field in which a period is not permitted.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prml is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is the most
recently encountered valid override keyword parameter on
an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
parameter or field. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6251
INCORRECT USE OF LEFT PARENTHESIS xxx
Explanation: In a job control statement, a left parenthesis
appeared in a parameter or field in which a left parenthesis is
not permitted.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prml is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
parameter or field. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6261
INCORRECT USE OF PLUS xxx
Explanation: In a job control statement, a plus sign appeared
in a parameter or field in which a plus sign is not permitted.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
parameter or field. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6271
INCORRECT USE OF AMPERSAND xxx
Explanation: In a job control statement, an ampersand
appeared in a parameter or field in which an ampersand is not
permitted.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
Section 9: IEF Messages - Job Scheduler
9-27
•
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prm1 SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
parameter or field. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6281
INCORRECT USE OF ASTERISK xxx
Explanation: In a job control statement, an asterisk appeared
in a parameter or field in which an asterisk is not permitted.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prm1 SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
parameter or field. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6291
INCORRECT USE OF APOSTROPHE xxx
Explanation: In a job control statement, an apostrophe was
used incorrectly.
Single apostrophes are used to enclose certain parameters
containing special characters or blanks. Two apostrophes
within a parameter enclosed in apostrophes are used to
represent an apostrophe.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD', where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if the error was detected before any keyword
parameters were processed. (For example, an error was
detected in the name field of a statement.)
9-28
VS2 System Messages (VS2 Release 3.7)
• IN THE prm1 SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the invalid
use of the apostrophe. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6301
UNIDENTIFIED KEYWORD xxx
Explanation: In a job control statement, the scheduler found
that:
• A character string followed a blank or comma and preceded
an equal sign, but could not be recognized as a valid
keyword. Either the keyword was misspelled, theetlual sign
was misplaced or, because of the absence of a right
parenthesis after the previous major keyword, a valid major
keyword was considered a minor keyword.
• A valid subparameter keyword appeared without the
corresponding parameter keyword; for example, SER without
VOLUME.
'
• A valid keyword was not consistent with the statement
operation code; for example, DSNAME in an EXEC
statement.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prm1 SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is the most recently encountered minor keyword
parameter associated with the major keyword parameter
prm2, which precedes the error.
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
statement. Then submit the job again.
Problem Determination: Table 11 items 1, 4, 7c, 29.
IEF6311
NUMBER OF DDNAMES EXCEEDS MAXIMUM
Explanation: In the DO statements for a step, the DDNAME
parameter appeared in 6 or more DO statements. This
parameter can appear in no more than 5 DO statements in a
step.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Change the DD
statements for the step so that 5 or fewer use the DDNAME
parameter. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6321
FORMAT ERROR xxx
Explanation: In a job control statement, the format of a
parameter was incorrect. For example:
• Too many or too few levels of qualification were specified.
• No enclosing parentheses appeared.
• An operator was missing in a COND parameter.
• The EVEN and ONLY subparameters were both specified in
the COND parameter of the EXEC statement.
• A comma, right parenthesis, ampersand, or blank did not
follow a right parenthesis in a SPACE parameter.
• The keyword specified is shorter than the required length.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
• IN THE prm FIELD, where the value specified for the
particular prm was less than the acceptable length.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
parameter. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6331
PROGRAMMER NAME MISSING xxx
Explanation: The programmer's name, established as an
installation requirement in the PARM parameter of the reader
procedure, was omitted from the JOB statement.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Specify a
programmer's name. If a programmer's name had been
specified, correct the order of the positional parameters. Then
submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6341
ACCOUNT NUMBER MISSING xxx
Explanation: The account number, established as an
installation requirement in the PARM parameter of the reader
procedure, was omitted from the JOB statement.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Specify an
account n4Jmber. If an account number had been specified,
check for a comma or a parameter before the account
number; if one appears, remove it. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6351
JOBNAME MISSING xxx
Explanation: The job name, which must appear in the name
field of a JOB statement, was missing.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr
• IN THE VALUE FIELD OF THE SYMBOLIC indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prml is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter. PARAMETER, if the error was
detected in th,e, field which ;:Jssigns a value to a symbolic
parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Section 9: IEF Messages - Job Scheduler
9-29
•
Programmer Response: Probable user error. Specify a job
name. Then submit the job again.
Problem Determination: Table I, items I, 4, 7c, 29.
IEF6361
MISPLACED JOBllB STATEMENT
Explanation: A DD statement,containing JOBLIB in its name
field appeared after an EXEC statement. Or a second JOBLIB
DD statement appeared in the control statements for a job.
A JOBLIB DD statement, which defines a job library.can
appear only immediately after a JOB statement and before the
first EXEC ~tatement in a job. Only one statement containing
JOBLIB in its name field can appear in the statements for a
job.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Place the JOBLIB
DD statement immediately after the JOB statement. If two or
more job libraries are to be used as one library, put blanks in
the name fields of the concatenated DD statements. Place the
concatenated DD statements immediately after the JOBLIB DD
statement. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6371
EXCESSIVE ACCOUNT FIELD lENGTH xxx
Explanation: In a JOB or EXEC statement, the accounting
information was longer than the 142 characters permitted.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2, (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Shorten the
accounting information. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6381
SPECIFIED NUMERIC EXCEEDS MAXIMUM AllOWED
xxx
Explanation: In a job control statement, a parameter or
subparameter value contains a valid number of digits, but
exceeds the maximum numeric limit.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prml is a minor keyword parameter associated with major
9-30
VS2 System Messages (VS2 Release 3.7)
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
.
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
parameter or subparameter value. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6391
INVALID CLASS DESIGNATION xxx
Explanation: In a job control statement, 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, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error. (For
example, CLASS = U is invalid since the acceptable class
names for the CLASS parameter are A through 0.)
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if the error was detected before any keyword
parameters were
• IN THE prm OVERRIDE FIELD, where prm is processed. (For
example, an error was detected in the name field of a
statement.)
• IN THE prml SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter. an override keyword parameter on an
EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the class
name. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6401
EXCESSIVE NUMBER OF POSITIONAL PARAMETERS
xxx
Explanation: A job control statement contained too many
positional parameters. A misplaced comma, a duplication, or a
null operand field could cause such an error.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
\
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
statement, and submit the job again.
Problem Determination: Table I, items I, 4, 7c, 29.
IEF6411
IMPROPER SUBPARAMETER LIST xxx
Explanation: A job control statement contains an incorrect
subparameter list for a positional parameter. Either such a list
is required and is missing, or is not permitted but is present.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred.· This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prnil is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
parameter. Then submit the job again.
Problem Determination: Table I, items I, 4, 7c, 29.
IEF6421
EXCESSIVE PARAMETER LENGTH xxx
Explanation: In a job control statement, a positional parameter
was longer than permitted.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prml is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Shorten the
parameter to the maximum permitted length or less. Then
submit the job again.
Problem Determination: Table I, items I, 4, 7c, 29.
IEF6431
UNIDENTIFIED POSITIONAL PARAMETER xxx
Explanation: In a job control statement, a positional parameter
that has certain permitted values was not recognized. It may
be invalid, misspelled, or mispunched.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prml is a minor keyword parameter associated with major
keyword parameter prm2. (For example; SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
erroneous positional parameter. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6441
INVALID NUMERIC xxx
Explanation: In a job control statement, an alphabetic or
special character appeared in a parameter that can contain
only numeric characters.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
erroneous parameter. Then submit the job again.
Section 9: IEF Messages - Job Scheduler
9-31
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6451
INVALID REFER BACK xxx
Explanation: In a job control statement, a parameter 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, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was' detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Check the spelling
and punching of the parameter containing the reference and of
the name in the statement to which it refers. Determine if the
parameter containing the reference can' validly contain a
reference. After correcting the error, submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6461
REQUIRED POSITIONAL PARAMETER MISSING xxx
Explanation: In a job control statement, a required positional
parameter or subparameter was not specified.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prml is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Insert the missing
parameter or subparameter. Then, submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6471
NON-ALPHABETIC FIRST CHARACTER OF NAME xxx
Explanation: In a job control statement, the first character in a
9-32
VS2 System Messages (VS2 Release 3.7)
name is not alphabetic. The name can be the name field a
procedure name in a parameter, or a program name in a'
parameter.
This message will also appear when a relative generation
number of a generation data group is used without a plus or
minus sign. For example, DSNAME = dsnanie( + 1) is correct,
whereas DSNAME = dsname(l) is incorrect.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs'if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the name
field. Then submit the job again. '
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6481
INVALID DISP FIELD - xxx SUBSTITUTED
Explanation: In a DO statement, a subparameter specified in
the DISP parameter is invalid:
• A dispo~tion of KEEP is invalid for a temporary data set. In
this case, xxx will appear as PASS. If a DSNAME parameter
references a data set which has a disposition of DELETE,
xxx will also appear as PASS.
• A disposition of CATLG is invalid for a data set whose data
set name is enclosed in apostrophes. (In this case, xxx will
appear as KEEP.)
•
System Action: The system changed the disposition of the
data set to xxx. Processing continued.
Programmer Response: Probable user error. If the job is to be
executed again, correct the invalid disposition.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6491
EXCESSIVE NUMBER OF DO STATEMENTS
Explanation: More than 1635 DO statements appeared in one
job step. Possibly, an EXEC statement is missing.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
The system printed the message with each DO statement after
the 1635th.
Programmer Response: Probable user error. Either remove the
excess DO statement(s) or add a missing EXEC statement.
Then submit the job again.
Problem Determination: Table I, items 1, 7c, 29.
IEF6501
INCORRECT USE OF SLASH xxx
Explanation: In a job control statement, a slash appeared in a
parameter or field in which a slash is not permitted.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control 'statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
parameter or field. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6511
INCORRECT USE OF MINUS xxx
Explanation: In a job control statement, a hyphen (or minus
sign) appeared in a parameter or field in which a hyphen is not
permitted.
In the message text, xxx is one of the following phrases:
• IN THE prm FIELD, where prm is the most recently
encountered keyword parameter preceding the error.
• ON THE cntr STATEMENT, where cntr indicates the job
control statement on which the error occurred. This phrase
usually occurs if 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 prml SUBPARAMETER OF THE prm2 FIELD, where
prm 1 is a minor keyword parameter associated with major
keyword parameter prm2. (For example, SER is a minor
keyword parameter that appears only when associated with
major keyword parameter VOLUME.)
• IN THE SYMBOLIC PARAMETER, if the error was detected in
the symbolic parameter.
• IN THE VALUE FIELD OF THE SYMBOLIC PARAMETER, if the
error was detected in the field which assigns a value to a
symbolic parameter.
• IN THE prm OVERRIDE FIELD, where prm is an override
keyword parameter on an EXEC statement.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
parameter or field. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6521
MUTUALLY EXCLUSIVE KEYWORDS - KEYWORD IN
THE prm FIELD IS MUTUALLY EXCLUSIVE WITH
KEYWORD ON THE cntr STATEMENT
Explanation: The job control statement indicated by cntr in the
message text was flagged for one of the following reasons:
• The keyword indicated by prm in the message text and
another keyword or positional parameter on the same
statement are either mutually exclusive or identical.
• The DLM keyword was detected on the statement before
the required asterisk (*) or DATA. Therefore, any other
major keywords that might appear on the statement, except
DCB, will be mutually exclusive with DLM.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the
statement in error and run the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6531
SUBSTITUTION JCL - xxx
Explanation: In a cataloged procedure statement, one or more
symbolic parameters were used. In the message text, xxx
represents the text that results from the symbolic parameter
substitution.
If DD DUMMY or DD DYNAM is used to override a JCL
statement in a cataloged procedure, the overridden parameters
in the message text will appear as DUMM = or DYNA = .
Programmer Response: None.
IEF6541
MULTIPLE DDNAMES REFER TO ONE DO
STATEMENT
Explanation: In the job control statements for a job step, two
DD statements contain ODNAME parameters that specify the
same name.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Either delete one
of the DO statements or change the name in one of the
duplicate DDNAME parameters. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6551
DSNAME INVALID WHEN SYSOUT SPECIFIED
Explanation: A DD statement contained a SYSOUT parameter
and a DSNAME parameter.
System Action: The DSNAME parameter is ignored. Processing
continues.
Programmer Response: Probable user error. If the job is to be
executed again, correct the statement by removing the
DSNAME or SYSOUT parameter.
Problem Determination: Table I, items 1, 4, 7a, 29.
IEF6571
SYMBOL NOT DEFINED IN PROCEDURE
Explanation: In an EXEC statement calling a procedure, or a
PROC card in a called procedure a value was assigned to a
symbolic parameter not defined for that procedure.
System Action: The job is terminated.
Programmer Response: Probable user error. Include the
symbolic parameter in the procedure or remove the value
assignment from the EXEC statement or PROC statement
Problem Determination: Table I, items 1, 3, 4, 7c, 29.
IEF6581
PROC VERB STATEMENT OUT.OF SEQUENCE
Explanation: A statement which specified PROC in its
operation field was not the first statement in a procedure. The
PROC statement is valid only as the first statement in a
procedure.
System Action: The job is terminated.
Programmer Response: Probable user error. If a PROC
statement is to be used, make sure that it appears only as the
first statement in the procedure.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6591
MISPLACED SYSCHK DO STATEMENT
Explanation: During execution of a deferred restart, it was
found that a SYSCHK DD statement preceded the first EXEC
statement in the resubmitted deck. However, the RESTART
parameter of the JOB statement did not specify a checkpoint
identification.
System Action: Restart is terminated.
Programmer Response: Probable user error. If checkpoint
restart is desired, specify a checkpoint identification in the
Section 9: IEF Messages - Job Scheduler
9-33
•
RESTART parameter of the JOB statement. If step restart is
desired, remove the SYSCHK DD statement.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6601
Programmer Response: If the PEND statement is unnecessary,
remove it. Otherwise, either supply a correct PROC statement
or remove from the in-stream procedure the data, DD '"
statement or DD DATA statement. Resubmit the job.
MISSING SYSCHK DD STATEMENT
Explanation: During execution of a deferred checkpoint restart,
IEF6691
it was found that the RESTART parameter of the JOB
statement specified a checkpoint identification. However, a
SYSCHK DD statement did not precede the first EXEC
statement in the resubmitted deck.
System Action: Restart is terminated.
Programmer Response: Probable user error. Place a SYSCHK
DD statement before the first EXEC statement. Then resubmit
the job.
Problem Determination: Table I, items 1, 4, 7c, 29.
Explanation: The system has encountered a DD statement in
IEF6611
found that the RESTART parameter of the JOB statement
specified a step name that could not be found either in the
resubmitted deck or in the specified cataloged procedure.
System Action: Restart is terminated.
Programmer Response: Probable user error. Correct the
RESTART parameter and resubmit the job.
Problem Determination: Table I, items 1, 4, 7c, 29.
INVALID LABEL ON THE jPROCt STATEMENT
1PEND ~
Explanation: The name in the name field of the PROC or PEND
statement, as indicated in the message text, either is too long
or contains an invalid character.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Correct the name
field of the statement. Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6631
NO LABEL ON THE PROC STATEMENT
Explanation: No name was specified in the name field of the
PROC statement for an in-stream procedure.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
Programmer Response: Probable user error. Specify a name in
the name field of the PROC statement. Then submit the job
again.
Problem Determination:. Table I, items 1, 4, 7c, 29.
IEF6651
EXCESSIVE NUMBER OF IN-STREAM PROCEDURES
Explanation: The job contains more than 15 in-stream
procedures.
System Action: The job was terminated. The remaining job
contol statements for the job were scanned for syntax errors.
Programmer Response: Probable user error. Make sure that no
more than 15 in-stream procedures are specified in the job.
Then submit the job again.
Problem Determination: Table I, items 1, 4, 7c, 29.
IEF6681
PEND VERB STATEMENT OUT OF SEQUENCE
Explanation: A PEND statement has been encountered which
does not terminate an in-stream procedure; that is, either it is
not preceded by a valid PROC statement, or the procedure
contains data, a DD '" statement, or a DD DATA statement.
The PEND verb is valid only as the last statement in the
in-stream procedure.
System Action: The job is terminated. The remaining job
control statements for the job are scanned for syntax errors.
9-34
which the DDNAME parameter specifies the name of a DD
statement that contains a DYNAM parameter.
System Action: The job is terminated. The remaining job
control statements are scanned for syntax errors.
Programmer Response: Probable user error. Either change the
reference in the DDNAME parameter or delete the DYNAM
parameter in the referenced DD statement. Submit the job
again.
Problem Determination: Table I, items 1, 4, 5a, 29.
RESTART STEP NOT FOUND
Explanation: During execution of a deferred restart, it was
IEF6621
INVALID REFER FORWARD TO DYNAM DATA SET
VS2 System Messages (VS2 Release 3.7)
IEF6701
NO VALUE ASSIGNED TO SYMBOLIC PARAMETER
ON PROC STMT VIA THE EXEC STMT
Explanation: A jobstep calling a cataloged procedure has not
provided a value in its EXEC statement for a symbolic
parameter contained in 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 job is terminated.
Programmer Response: Correct the error by giving the
symbolic parameter a default value on the PROC statement, by
making a value assignment for it on the EXEC statement, or by
changing the name of the symbolic parameter.
Problem Determination: Table I, items 1, 3, 4, 7c, 29.
IEF671 I
MISPLACED JOBCAT DD STATEMENT
Explanation: A JOBCAT DD statement appeared after an EXEC
statement, or a second JOBCAT DD statement appeared in the
control statements of the job.
A JOBCAT DD statement, which defines a user catalog for the
job, must precede the first EXEC statement in a job. Only one
statement containing JOBCAT in its name field may appear in
the control statements of a job. If a JOBLIB DD statement
appears in the same job, it must immediately precede the
JOBCAT statement.
System Action: The job is terminated. The remaining control
statements are scanned for syntax errors.
Programmer Response: Probable user error. Make sure that
the JOBCAT DD statement immediately precedes the first
EXEC statement. If two or more user catalogs are to be used
as one catalog, put blanks in the name field of the
concatenated DD statements, and make sure that the
concatenated DD statements immediately follow the JOBCAT
DD statement. Then run the job again.
IEF6721
DUPLICATE STEPCAT DD STATEMENT
Explanation: Only one STEPCAT DD statement may appear in
a job step; more than one was found.
System Action: The job terminates and the remaining control
statements are scanned for syntax errors.
Programmer Response: Probable user error. Remove all
duplicate STEPCAT DD statements. If two or more user
catalogs are to be used as one catalog, put blanks in the
name fields of the concatenated DD statements. Make sure
that the concatenated DD statements are immediately after the
STEPCAT DD statement and run the job again.
IEF6731
ADDRSPC = REAL INVALID ON THE cntr
STATEMENT
Explanation: An unauthorized user is attempting to acquire real
storage. Currently, TSO is the only unauthorized user. In the
message text, cntr is either JOB or EXEC.
System Action: The job is terminated. The remaining job
control statements are scanned for syntax errors.
Programmer Response: Probable user error. Either remove the
ADDRSPC keyword from the statement in error (allowing
ADDRSPC to default to VIRT) or specify ADDRSPC = VIRT. Run
the job again.
IEF6741
INVALID DYNUMBR VALUE - 0 SUBSTITUTED
Explanation: A non-numeric or value exceeding 1635 was
coded as an object of the DYNAMBR keyword.
System Action: A default of 0 is set and the job is allowed to
continue processing.
Programmer Response: Correct the value and resubmit the job
if necessary.
Problem Determination: Table I, items 1, 4, 7a, 29.
IEF6751
PERFORM VALUE INVALID OR OMITTED - SYSTEM
DEFAULT SUBSTITUTED
Explanation: An incorrect value was coded as an object of the
PERFORM keyword, or the PERFORM keyword was omitted.
The value was non-numeric or exceeded 255.
System Action: A system default is used (supplied by the
SRM). A default of one (1) is substituted for non-TSO jobs and
two (2) for TSO jobs. The job is allowed to continue.
Programmer Response: Correct the value and resubmit the job
if necessary.
Problem Determination: Table I, items 1, 4, 7a, 29.
IEF6161
PERFORM VALUE UNDEFINED TO SYSTEM DEFAULT SUBSTITUTED
Explanation: The value specified is not among the performance
group values defined by the installation.
System Action: A system default is used (supplied by the
optimizer). A default of one (1) is substituted for non-TSO
jobs and two (2) for TSO jobs. The jQb is allowed to continue.
Programmer Response: Correct the value and resubmit the job
if necessary.
Problem Determination: Table I, items 1, 4, 7a, 29.
IEF6771
WARNING MESSAGE(S) FOR JOB
iii
ISSUED
Explanation: While converting or interpreting the JCL for this
job, an error was detected, but a system default was set. jjj
identifies the jobname.
System Action: Warning messages are issued at the end of
the JCL for job jjj.
Programmer Response: Check the warning messages to
identify the default.
Problem Determination: Table I, items 1, 4, 7a, 29.
IEF6781
DEVICE I/O ERROR CONVERTING/INTERPRETING
JCL
Explanation: An uncorrectable input;output error occurred
while processing a JCL statement.
System Action: The job being processed is terminated when
the error occurs. Message IEF6791 is written to the console
and in response the operator reentered the job through the
input stream.
Programmer Response: None.
IEF6791
DEVICE I/O ERROR CONVERTING/INTERPRETING
JCL FOR JOB iii
Explanation: An un correctable input; output error occurred
while processing a JCL statement. jjj is the jobname.
System Action: The job is terminated and message IEF67Si is
written in the. SYSOUT data set to inform the programmer.
Programmer Response: Resubmit the job in the input stream.
Problem Determination: Table I, items 1; 2, 4, 7a, 29.
IEF6801
DEVICE I/O ERROR WRITING TO SYSTEM MESSAGE
DATA SET FOR JOB iii
Explanation: An uncorrectable input; output error occurred
while writing a JCL statement or diagnostic to a SYSOUT data
set.
System Action: The job is terminated.
Programmer Response: Resubmit the job in the input stream.
Problem Determination: Table I, items 1, 2, 4, 7a, 29.
IEF6811
INVALID COPIES VALUE - DEFAULT OF ONE
SUBSTITUTED
Explanation: A non-numeric or excessive value (greater than
255) was specified as the object of the COPIES keyword.
System Action: A default value of one (1) is substituted and
the job is allowed to continue.
Programmer Response: Correct the value and resubmit the job
in the input stream if necessary.
Problem Determination: Table I, items 1, 4, 7a, 29.
IEF6821
FREE VALUE INVALID - DEFAULT OF 'END'
SUBSTITUTED
Explanation: A value other than CLOSE or END was specified
as the object of the FREE keyword.
System Action: The default value, END is substituted and the
job is allowed to continue processing.
Programmer Response: Correct the value and resubmit the job
if necessary.
Problem Determination: Table I, items 1, 4, 7a, 29.
IEF6831
ccc TERMINATED DUE TO Scde ABEND
Explanation: An uncorrectable error occurred while processing
a JCL statement. cde identifies the system ABEND code; ccc
identifies either converter or interpreter.
System Action: The job is terminated.
Programmer Response: None.
Problem Determination: Table I, items 1, 4, 7a, 29.
IEF6841
HOLD VALUE INVALID - DEFAULT OF 'NO'
SUBSTITUTED
Explanation: An incorrect value was coded as the object of the
HOLD keyword (neither YES nor NO. was coded).
System Action: A default of 'NO' is set and the job is allowed
to continue processing.
Programmer Response: Correct the value and resubmit the job
if necessary.
Problem Determination: Table I, items 1, 4, 7a, 29.
IEF6851
ST ATIC PLUS DYNAMIC DO COUNT EXCEEDS MAX
DYNAMIC DO'S REDUCED
Explanation: In a job step, the number of DO's plus the
number of DO DYNAM's plus the value that is the object of
the DYNAMNBR keyword exceeds 1635.
System Action: The number of dynamic DO's is reduced
providing a maximum of 1635 total DO's for the job step. The
job is allowed to continue processing.
Section 9: IEF Messages - Job Scheduler
9-35
•
Programmer Response: Delete static DO's or DO DYNAM
statements, or correct the DYNAMNBR value and resubmit the
job if necessary.
'
Problem Determination: Table I, items 1, 4, 7a, 29.
IEF6871
jjj sss [ppp] ddn [+xxx] - REQUESTED VOLUME
MOUNTED ON JES3 MANAGED UNIT
Explanation: In a DO statement, the volume specified in the
VOLUME parameter or retrieved. from the catalog is mounted
on a JES3 managed unit and the unit parameter did not
specify the name of a group of units managed by JES3. In the
message text, ddn is the data definition name in the name
field of the' DO statement.
'
System Action: The job is terminated.
Programmer Response: Probable user error. Change the unit
parameter of the DO statement 'to specify the name of a JES3
managed unit. (This unit name may be obtained from the
system programmer.) Then resubmit the job again.
Problem Determination: Table 1 items 1, 3, 4, 7c, and 29.
IEF6881 jjj sss [ppp] ddn [xxxxx] - NULLFILE AND DSNAME
CONFLICT IN ISAM CONCATENATION
Explanation: A DO statement specifying DSORG = IS or ISU
and NULLFILE was found concatenated to a DD statement that
specified DSORG = IS or ISU and a dsname other than
NULLFILE. In the message text, xxxxx refers to the relative
position of a concatenated ISAM DO statement in relation to
the first DO for the concatenation.
System Action: The job is terminated.
Programmer Response: Make the dsname for the DO
, statements in the concatenation either all NULLFILE or all not
NULLFILE. Run the job again.
Problem Determination: Table I, items 2, 7c, 29.
IEF7001
jjj sss [ppp] - ENVIRONMENT CHANGED. NOW
UNABLE TO ALLOCATE
Explanation: A device which was available at the start of step
sss of job iii or cataloged procedure step ppp, is now in use
by a system function such as OLTEP, DSS, or a system utility.
System Action: The job is terminated.
Programmer Response: Probable user error. Resubmit the job
when the system function has completed.
Problem Determination: Table I, items 1, 2, 13, 29.
IEF7011
jjj sss [ppp] [ddn[ +xxx] - ERROR CHANGING
ALLOCATION ASSIGNMENTS
Explanation: It was necessary for device allocation to reassign
certain allocations for step sss or job jjj or catalog procedure
step ppp. During an attempt to unallocate a unit so that the
reassignment could be done, an error occurred.
In the message text, ddn refers to the data set for which' the
rearrangement was being done. +xxx refers to the relative
position of a concatenated DO in relation to the first member
of the concatenated group.
System Action: The job is terminated.
Programmer Response: Probable system error. Resubmit the
job.
Problem Determination:. Table I, items 1, 2, 13, 29.
IEF7021
jjj sss [ppp] ddn [txxx] UNABLE TO ALLOCATE
Explanation: The system was unable to allocate at least one
device to step sss of job iii or cataloged procedure step ppp.
ddn is the name of the DO statement that specified the device
collection, txxx is the relative position of the concatenated DO
to the first DO in the concatenated group (ddn).
9-36
VS2 System Messages (VS2 Release 3.7)
In a DO statement, or combination of DO statements, the UNIT
parameter(s) specified a device collection and specified more
than the numberof devices available within the collection.
System Action: The job is terminated.
Programmer Response: Probable user error. Check the UNIT
parameter(s) to ensure that the device collections can ·supply
the number of devices needed. If necessary, change the UNIT
parameters. Then resubmit the job.
Problem Determination: Table I, items 1, 3, 4, 7c, 29.
IEF7031
- Hi sss [ppp] ddn[ +xxx] - NEW DATA SETS NOT
ALLOWED ON STACKED PACK FORMAT DOS
VOLUME
Explanation: A new data set was requested on a DOS stacked
pack format volume by step sss of job jjj or cataloged
procedure step ppp. In VS systems, new data sets cannot be
created on such a volume. Only existing data sets may be
used.
In the message text, +xxx refers to the relative position of a
concatenated DO to the first DO in the concatenated group
(ddn).
System Action: The job is terminated.
Programmer Response: Probable user error. Specify a different
VOL = SER = parameter in DO statement ddn or make sure at
least one nonstacked pack format volume is available.
Problem Determination: Table I, items 1, 2,4, 7c, 29.
IEF7041
jjj sss [ppp] ddn[ +xxx] - UNABLE TO ACCESS
REQUIRED SYSCTLG DATA SET ON CONTROL
VOLUME
Explanation: A control volume required to locate a cataloged
data set could not be accessed for one of the following
reasons:
• No SYSCTLG data set was contained on the required
volume.
• A permanent I/O error occurred while catalog management
was attempting to open the catalog.
It was impossible to locate the data set.
In the message text, ddn is the name of the DO statement that
specified the cataloged data set name. +xxx refers to the
relative position of a concatenated DD to the first DO in the
concatenated group (ddn).
System Action: The job is terminated ..
Programmer Response: Probable user error. In the first case,
make sure that the correct SYSCTLG data set exists on the
control volume specified in the master catalog.
In the second case, the job should be rerun.
Problem Determination: Table I, items 1,2,4, 7a, 25b, 25d,
29 or 30.
IEF7101
Hi
sss ppp - MSS MOUNT FAILED FOR VOL ser ON
ddd - re.
Explanation: An attempt by allocation to mount Mass Storage
System (MSS) volume ser on device ddd failed. The attempt
was made on behalf of step sss in job jjj. In the message text,
rc is the MSS failure reason code. See OS/VS Message
Library: Mass Storage System (MSS) Messages, GC38-1000
for a defailed explanation of the code.
System Action: The job terminates.
Operator Response: Report the error to the system
programmer. If rc is 5, 6, 10, or 12, rerun the job when the
MSS volume is available. The system will notify you when the
volume is available.
Programmer R~sponse: See OS/VS Message Library: Mass
Storage System (MSS) Messages, GC38-1000 to determine
the cause of the error in MSS.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
VS2.03.804
IEF711 I
jjj 555 ppp - MSS UNLOAD FAILED FOR VOL ser ON
ddd - rc.
Explanation: An attempt by allocation to unload Mass Storage
System (MSS) volume ser from device ddd fai/ed. The attempt
was made on behalf of step sss in job jjj or an UNLOAD
command. In the message text, rc is the MSS· failure reason
code. See OS/VS Message Library: Mass Storage System
(MSS) Messages, GC38-1000 for a detai/ed explanation of the
MSS fai/ure reason code.
.
System Action: Processing continues. Even though there was
an MSS failure, the system will disassociate the volume from
the unit as indicated by message IEE7341.
Operator Response: Report the problem to the system
programmer.
Programmer Response: See OS/VS Message Library: Mass
Storage System (MSS) Messages, GC38-1000 to determine
the cause of the error in MSS.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IEF7121
jjj sss ppp - MSS VERIFY FOR VOL ser ON ddd reason.
Explanation: The system was unable to verify the label of
volume ser on device ddd. Reason is one of the following:
a. I/O ERROR - Input!output error reading the label of the
volume on device ddd. Volume ser was requested.
b. WRONG VOL - The label of the volume on device ddd
contains a serial number other than the one requested. This
condition can occur if the MSS volume has been associated
with another volume serial.
System Action: The job terminates.
Operator Response: Report the problem to the system
programmer. If the volume serial number in the message was
SCRTCH, vary the device offline and specify the PURGE option
at the next IPL of the system.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IEF7131
iii
sss ppp - MSS VOLUME NOT AVAILABLE.
reason code. The volume can not be accessed from the
specified device address. See OS/VS Message Library: Mass
Storage System (MSS) Messages, GC38-1000 for a detailed
explanation of the MSS reason code in IEF7101.
System Action: The job terminates.
Programmer Response: See OS/VS Message Library: Mass
Storage System (MSS) Messages, GC38-1000 to determine
the cause of the error. For reason code 8, resubmit the job
after correcting the JCL according to proper installation
procedure~. For reason" codes 10 and 12, resubmit the job
when the MSS volume becomes available.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IEF7161
Hi
555
ppp - UNABLE TO MOUNT MSS VOLUME.
Explanation: Refer to message IEF7101 on the JES job log for
the volume serial number and device address of the volume,
and for the failure reason code. Due to a Mass Storage
System (MSS) error, the system can not mount the volume.
See OS/VS Message Library: Mass Storage System (MSS)
Messages, GC38-1000 for a detailed explanation of the reason
code in IEF7101.
System Action: The job terminates.
Programmer Response: Report the problem to the system
programmer. Resubmit the job after the system programmer
has corrected the error indicated in IEF7101.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IEF7171
Hi
sss ppp - ""MSSVOLUME NOT MOUNTED. MSVGP
NAME DOES NOT EXIST.
Explanation: Probable user error. The virtual volume group
name (MSVGP) specified does not exist. See OS/VS Message
Library: Mass Storage System (MSS) Messages, GC38-1000
for a detai/ed explanation of MSS reason code X '207'.
System Action: The job terminates.
Programmer Response: Correct the MSVGP name and resubmit
the job.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
Explanation: Refer to message IEF7101 on the JES job log for
the volume serial number, the device address, and the failure
reason code. The requested volume is presently mounted with
the Exclusive attribute, or the Mass Storage System (MSS)
device is not shareable, and currently the volume is already
mounted and shareable. See OS/VS Message Library: Mass
Storage System (MSS) Messages, GC38-1000 for a detailed
explanation of the MSS reason code in IEF7101.
System Action: The job terminates.
Operator Response: Rerun the job when the MSS volume is
available.
Programmer Response: Resubmit the job when the MSS
volume becomes available. The operator will be notified when
the volume becomes available.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
lEF7141
iii
jjj sss ppp - MSS VOLUME NOT MOUNTED. SPACE
OR MSVGP REQUIRED FOR NON -SPECIFIC
REQUEST.
Explanation: Probable user error. Either SPACE or MSVGP
name must be specified on a nonspecific volume request to
the Mass Storage System (MSS). See OS/VS Message Library:
Mass Storage System (MSS) Messages, GC38-1000 for a
detai/ed explanation of MSS reason code X'225'.
System Action: The job terminates.
Programmer Response: Resubmit the job, adding either a
MSVGP name or SPACE specification to the request.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IEF7191
jjj 555 [ppp] ddn [+xxx] - DATA SET PREVIOUSLY
DEFINED ON THIS VOLUME.
555
ppp - MSS VOLUME NOT DEFINED.
Explanation: Probable user error. The Mass Storage System
(MSS) volume does not exist. See OS/VS Message Library:
Mass Storage System (MSS) Messages, GC38-1000 for a
detailed explanation of MSS reason code 7.
System Action: The job terminates.
Programmer Response: Correct the volume serial number and
resubmit the job.
Problem Determination: Table I, items 1, 2, 3, 4, 29.
IEF71SI
IEF7181
jjj sss ppp - MSS VOLUME INACCESSIBLE.
Explanation: Refer to message IEF7101 in the JES job log for
the volume serial number, device address and the MSS failure
EXplanation: A profile for the specified data set on this
volume already exists in the resource access control faciHty
(RACF) data set.
In the message text, +xxx indicates the relative position of a
concatenated DO in relation to the first DO in the
concatenated group ddn.
Note: This message is generated only in systems containing
the RACF facility.
System Action: The job is terminated.
Programmer Response: Probable user error. Change the data
set name or volume serial, or have the installation RACF
administrator delete (from the RACF data set) the profile for
the specified data set on this volume. Then, resubmit the job.
Section 9: IEF Messages - Job Scheduler
9-37
VS2.03.804
Problem Determinatiori: Table I,_!tems 1, 3, 4, 7c, 26b.
IEF7201
jjj sss [ppp] ddn [+xxx] - USER NOT AUTHORIZED
TO DEFINE THIS DATA SET.
Explanation: The user has been given the automatic data set
protection characteristic without being given authorization to
define data sets.
In the message text, +xxx indicates the relative position of a
concatenated DD in relation to the first DO in the
concatenated group ddn.
Note: This message is generated only in systems containing
the resource access control facility (RACF).
System Action: The job is terminated.
Programmer Response: Contact the installation RACF
administrator to either remove the automatic data set
protection characteristic from the user profile or authorize the
user to define data sets. Then, resubmit the job.
Problem Determination: Table I, items 1, 3, 4, 7c.
IEF7211
IEF7221
jjj sss [ppp] ddn [+xxx]- PROTECTION CONFLICT
IN ISAM REQUESTS.
Explanation: Automatic data set protection could not be
performed because a concatenated ISAM DD statement
contained one or more of the following errors:
• The data set status was not either NEW or MOD treated as
NEW.
• The data set disposition Ot conditional disposition was
DELETE.
• DSNAME specified a system-generated name.
In the message text, +xxx indicates the relative position of a
concatenated DD in relation to the first DD in the
concatenated group ddn.
Note: This message is generated only in systems containing
the resource access control facility (RACF).
System Action: The job is terminated.
Programmer Response: Ensure that the above conditions for
automatic data set protection are rriet by each DD statement
of the concatenation. Then, resubmit the job.
Problem Determination: Table I, items 1, 3, 4, 7c.
jjj - FAILED - SECURITY VIOLATION INVALID PASSWORD GIVEN
\EXPIRED PASSWORD GIVEN
NEW PASSWORD NOT VALID
USER NOT PART OF GROUP
USER PROFILE NOT FOUND
FAILED BV INSTALLATION
USER ACCESS IS REVOKED
Explanation: While job iii was being proce .. .,.~J, one of the
following conditions was detected by the resource access
control facility (RACF) program:
• The password supplied was not contained in the user's
profile.
• The user password has expired. A new password must be
provided for RACINIT to be successful.
• The new password is not valid or is the same as the old
password.
• The GROUP specified is not valid for the user.
• The user was not defined by the system resource
administrator.
• The job was failed by the installation exit routine taken
when the job was initiated.
• Although the user is defined and the password is correct,
the user's access has been revoked.
Note: This message is generated only in systems containing
the RACF facility.
System Action: The job is terminated, and no steps are
executed. No RACF-protected resources are accessed.
Programmer Response: In the first four cases, execute the job
again, specifying the correct value for PASSWORD or GROUP.
If the problem persists, contact the RACF administrator at your
installation.
In the last three cases, contact the RACF administrator for
assistance.
Problem Determination: Table I, items 1, 2, 3, 4, 7d, 29.
IEF8611
FOLLOWING RESERVED DATA SET NAMES
UNAVAILABLE TO Hi
iii requested the use of one or more data
sets that are currently unavailable. The data sets are reserved
for other jobs currently executing in the system. Message
IEF8631 follows, listing the data set names.
System Action: Processing of the job named iii is suspended.
Operator Response: None.
Explanation: Job
9·37.0
VS2 System Messages· (VS2.03.804)
/
Section 9: IE F Messages· Job Scheduler
9·37.1
IEF8631
DSN = dsn
Explanation: Data set name dsn is not available to the job
named in preceding message IEF8611. This message will
appear for each data set name that is not available.
System Action: One of the following messages will be issued
to explain the status of the job:
• IEF0991 JOB jjj WAITING FOR DATA SETS
• IEF4521 xxx JOB NOT RUN - JCL ERROR [TIME = hh.mm.ss]
message IEF4521 will be written if the job is a TSO LOGON,
which would have to wait for data sets.
Operator Response: None.
9-38
VS2 System Messages (VS2_03.804)
Section 10: System Generation Messages (lEI)
Component Name
lEI
Program Producing Message
Assembler program during expansion of system generation macro instructions.
Audience and Where Produced
For system programmer: assembler listing in SYSPRINT data set.
Message Format
s, * * * IElmacnnn text
s
Severity code:
Warning message; the condition indicated may cause errors in new system.
0
Error message; error is in coding of a· system generation macro instruction.
5
Error message; message is produced by GENERATE macro instruction.
7
mac
Indication of system generation macro instruction at which error was detected:
OAT DATAMGT
SCH SCHEDULR
AFFAFFINITY
SVC SVCTABLE
DTS DATASET
CHA CHANNEL
EDI EDIT
TSO TSO
CKP CKPTREST
CON CONSOLE
GEN GENERATE
UNI UNITNAME
CTR CTRLPROG
100 10DEVICE
nnn
Message serial number.
text
Message text.
Comments
None.
Associated Publications
OS/VS2 System Generation Reference, GC26-3792.
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IElmacnnn text
Explanation: Error: The error indicated by the message text is
a coding error in the system generation macro instruction,
mac. The message serial number, nnn, identifies the message.
For the CHANNEL, and IODEVICE macro instructions, the
message text begins with either the name field of the macro
instruction or, if the name field was omitted, the sequential
identification number provided by the system.
Examples of these messages are:
5,*** IEICHA102 CHANNEL2-ADDRESS VALUE NOT
SPECIFIED
5,*** IEICHA102 CHAN#2-ADDRESS VALUE NOT SPECIFIED
The first example illustrates a message for a CHANNEL macro
instruction. "CHANNEL2" is the name field of the macro
instruction.
The second example illustrates the same message, but in this
case, the name field was ommitted and "CHAN#2" was
supplied by the macro instruction.
System Action: The assembler program did not produce a job
stream in the SYSPUNCH data set. The program analyzed all
remaining system generation macro instructions and printed
any other required messages. Either message IEIGEN113 or
IEIGEN116 was printed, followed by the message:
GENERATION TERMINATED. Then the system generation
process was abnormally terminated.
Severity Code: 5
Programmer Response: Probable user error. Correct the errors
indicated and begin the system generation process from the
start of Stage I.
Problem Determination: Table I, items 17a, 29. Have the
hardware configuration available.
IEIGEN1l3 QUIT SWITCH PRIOR TO GENERATE MACRO
Explanation: One or more errors, indicated by messages, were
detected before the GENERATE macro instruction was
expanded.
Severity Code: 7
Programmer Response: Correct the errors indicated and begin
the system generation process from the start of Stage I.
IEIGEN1l6 QUIT SWITCH SET IN GENERATE MACRO
Explanation: One or more errors were detected during the
expansion of the GENERATE macro instruction.
Severity Code: 7
Programmer Response: Correct the errors indicated and begin
the system generation process from the start of Stage I.
7,'" * * GENERATION TERMINATED * * '"
Explanation: The system generation process was abnormally
terminated.
Severity Code: 7
Programmer Response: None. This message follows message
IEIGEN113 and/or message IEIGEN116.
Section 10: lEI Messages - System Generation
10-1
•
Warning Messages
Informative Messages
IElmacnnn text
*, text
Explanation: The message text indicates a condition in macro
Explanation: This type of message documents theopti<>ns
instruction mac that may cause errors in the new system. The
message serial number nnn identifies the message.
For example:
0,* * * IEIGEN940 CTRLPROG MACRO DEFAULTED
Explanation: The indicated macro instruction was not specified
and the default options were taken.
Severity Code: 0
Programmer Response: None.
0, ***IEIGEN933 CONSOLE MACRO, CONSOLE ADDRESS
xxx, DISPLAY AREAS DEFAULTED TO LENGTH 14
Explanation: The dimensions for the status displays for this
console were not specified; tHe default value was used.
Severity Code: 0
Programmer Response: None.
selected for the new system through the system generation
macro instructions. All options are described, whether the
selection was explicit or implicit.
.
10-2
V$2 System Messages (VS2 Release 3.7)
**macro name***component
name***component ID***
Explanation: A message of this type appears before any
PUNCH statements that were produced by the macro
expansion. The macro name is the name of the macro
instruction that produced any succeeding PUNCH statements.
The component name is the name of the component group
responsible for maintaining the particular macro expansion. The
component 10 is the identification to be used in reporting
trouble if a problem is isolated to the code produced by the
particular macro expansion.
Section 11: SMF Dump Program Messages (IFA)
Component Name
IFA
Program Producing Message
SMF Dump Program IFASMFDP.
Audience and Where Produced
For programmer: SYSPRINT.
Message Format
IFAnnns text
nnn
Message serial number.
text
Message text.
s
Type code:
Information; no operator action is required.
I
Action; operator must perform a specific action.
A
Associated Publications
OS!VS System Management Facilities (SMF), GC35-0004.
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IFAOOll
DCB OPEN FAILED FOR DUMPIN DATA SET
Explanation: The data set defined by the DUMPIN DD
statement failed to be opened successfully. Message IEC1301
is also issued if the DD statement is missing.
System Action: The job step is terminated.
Programmer Response: Probable user error. Provide a DD
statement if it is missing and run the job again.
Problem Determination: Table I, items 1, 4, 29, (if the DD
statement is present).
IFA006A
REQUEST MADE TO DUMP ACTIVE SMF DATA SET REPLY CANCEL
Explanation: The data set defined by the DUMPOUT DD
statement failed to be opened successfully. Message IEC1301
is also issued if the DD statement is missing.
System Action: The job step is terminated.
Programmer Response: Probable user error. Provide a DD
statement if it is missing.
Problem Determination: Table I, items 1, 4, 29, (if the DD
statement is present).
Explanation: The SMF Dump program is attempting to dump
the active SMF data set. This request is invalid and must be
canceled because SMF records would have been lost.
System Action: The SMF Dump program enters a wait pending
the operator's reply.
Operator Response: Enter REPLY xx, 'CANCEL' to acknowledge
the cancelation of the SMF Dump program. If the wrong SMF
data set was specified in the dump program, enter the
program to dump the correct data set.
To dump the currently active data set, enter the SWITCH SMF
or HALT EOD command from the console. Either command will
activate the inactive SMF data set if it is empty and free the
currently active one for dumping. If the inactive SMF data set
is full, it must be dumped prior to issuing the above commands
or data will be lost.
Problem Determination: Table I, items 2, 29. Have a copy of
the SMF Dump procedure.
IFA0041
IFA0071
IFA0021
DCB OPEN FAILED FOR DUMPOUT DATA SET
OUTPUT BLOCKSIZE IS SMALLER THAN INPUT
Explanation: The blocksize of the input data set is greater than
the blocksize of the output data set.
System Action: The job step is terminated.
Programmer Response: Make sure the output blocksize is not
smaller than the input blocksize.
Problem Determination: Table I, items 1, 4, 29.
IFAOOSI
PERMANENT I/O ERROR DIAGNOSIS err
Explanation: A permanent I/O error has occurred on the
DUMPIN or DUMPOUT data set. The error description portion
is error diagnosis produced by the SYNADAF error analysis
routine.
System Action: The job step is terminated.
Programmer Response: Correct the error condition indicated in
the message text.
Problem Determination: Table I, items 1, 13, 29.
SMF DUMP CANCELLED
Explanation: This message is issued to notify the operator that
a program attempting to dump the SMF data set has been
canceled.
System Action: The program IFASMFDP is canceled.
Operator Response: Enter the SMF Dump program to dump the
correct SMF data set. If a dump of the active SMF data set is
desired first enter a SWITCH SMF or HALT EOD command
from the console. Either command will activate the inactive
SMF data set if it is empty and free the currently active one
for dumping via the SMF Dump program IFASMFDP. If the
inactive SMF data set is full, it must be dumped prior to
entering the above commands or data will be lost.
Problem Determination: Table I, items 2, 29. Have a copy of
the SMF Dump procedure available.
•
Section 11: IFA Messages - SMF Dump Program
11-1
IFA0081
SMF DUMP CANCELLED - REQUEST MADE TO
DUMP ACTIVE DATA SET
Explanation: This message is issued to notify the programmer
that the SMF Dump program attempted to dump the· active
SMF data set and has been canceled.
System Action: The job step is terminated.
Programmer Response: If the wrong SMF data set was
specified in the dump program, enter the program to dump the
11-2
VS2 System Messales (VS2 Release 3.7)
correct data set. If you want to dump the currently active data
set, that data set must be made inactiv~ by the operator
before the request will be honored, (because SMF records
would be lost).
Problem Determination: Table I, items 1, 2, 4, 29. Have a copy
of SMF Dump procedures available.
,
I
I
I,
Section 12: Environment Recording Messages (IFB)
•
Component Name
IFB
Program Producing Message
Input/ output environment recording routines, OBR and SVC 76.
Audience and Where Produced
For operator: console.
Message Format
xx IFBnnns text
xx
Message reply identification (absent, if operator reply not required).
nnn
Message serial number.
s
Type code:
Decision; operator must choose an alternative.
D
Eventual action; operator must perform action when he has the time.
E
Information; no operator action is required.
I
text
Message text.
Comments
The first format of the message is used for I/O routines; the second format is used for the system routines.
Associated Publications
OS/VS2 System Programming Library: SYS1.LOGREC
Error Recording, GC28-0677
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IFB010D
ENTER 'IPL REASON, SUBSYSTEM 10' OR 'U'
Explanation: This message requests the operator to provide:
• The reason for the IPL.
• The device or program (subsystem) responsible for the IPL
restart. '
or
• U - to continue operation with default values.
System Action: ROE waits pending the operator's reply.
Operator Response: Enter a reply in the format REPLY xx, 'rr,ss'
where xx is the reply id, rr is the ROE IPL reason codl, and ss
is the subsystem 10 code. For an explanation of the IPL reason
codes and subsystem 10 codes, see OS /VS2 Programming
Library: SYSl.LOGREC Error Recording.
IFB0201
INVALID REPLY TO IFB010D
Explanation: The reply to message IFBOlOO is incorrect.
System Action: Message IFBOIOD is reissued to allow the
operator to reenter his reply.
Operator Response: Either enter the IPL reason code and
subsystem 10 code in the proper format or reply 'U' to select
default values, in response to message IFB0100.
IFB0301
SYS1.LOGREC I/O ACCESS
ERROR,sens,stat,hh.mm.ss
Explanation: Probable hardware (channel or device) error.
SYS.LOGREC was accessed either to read or write a record on
SYSl.LOGREC, and an uncorrectable input/output error
occurred. sens is the first two sense bytes for the error
condition, stat is the status portion of the channel status word
(CSW), and hh.mm.ss is the time in hours, minutes, and
seconds.
System Action: The SVC 76 routine does not attempt to retry
the I/O operation. If the routine was attempting to write the
record, the record is lost. However, SVC 76 does attempt any
subsequent I/O access attempts to read or write any
subsequent records on SYSl.LOGREC.
Operator Response: Execute the IFCEREPO service aid program
to dump SYS1.LOGREC and save its existing contents. Then
execute the IFCOIPOO service aid program to reinitialize the
SYSl.LOGREC data set.
Programmer Response: If the SYSl.LOGREC data set
reinitialization attempt failed, reallocate the data set on the
system residence volume, using the IFCOIPOO service aid
program.
Problem Determination: Table I, items 2, 30.
IFB0401
SYS1.LOGREC AREA IS FULL, hh.mm.ss
Explanation: The SYSl.LOGREC data set is full and cannot
contain further environment records. At least one record has
been lost.
System Action: Processing continues, but further environment
records will be lost.
Operator Response: Execute the IFCEREPO program to dump
and zero the SYSl.LOGREC data set.
IFBOSOI
SYS1.l0GREC FORMAT ERROR, hh.mm.ss
Explanation: The header record of the SYSl.LOGREC data set
is missing or invalid.
System Action: Processing continues.
Operator Response: Execute the IFCOIPOO service aid program
to rewrite the header record and reinitialize SYSl.LOGREC.
IFB060E
SYS 1.LOGREC NEAR FULL
Explanation: The SYSl.LOGREC data set has reached 90% of
its capacity for data.
System Action: Processing continues.
Operator Response: Execute the IFCEREPO service aid to dump
and zero the SYSl.LOGREC data set. Continued processing,
without the data set being dumped, may cause the data set to
become full. To compile a history of hardware failures, do the
following:
• Save the IFCEREPO output.
• Save the master console listing.
,.I
Section 12: IFB Messages - Environment Recording
12-1
12-2
VS2 System Messages (VS2 Release 3.7)
Section 13: Machine-Check Handler..\ Dynamic Device Reconfig!D"ation, Channel Check
.
Hanoler and Missing Interrupt Handler Messages (IGF)
Component Name
IGF
Program Producing Message
Machine-check handler program, dynamic device reconfiguration program, channel check handler, and missing
interrupt handler.
Audience and Where Produced
For operator: console.
Message Format
IGFnnns text
nnn
Message serial number.
s
Type code:
This message supplies information about the error recovery attempt.
I
W
The system has been placed in wait state by MCH.
E
This message supplies error recovery information and indicates that operator action is required, but
that the action may be delayed until convenient.
Type code (dynamic device reconfiguration program):
A
Action; operator must perform a specific action.
Decision; operator must choose an alternative.
D
E
Eventual action; operator must perform action when he has time.
I
Information; no operator action is required.
text
Message text.
Comments
None.
Associated Publications
OS!VS2 Recovery Management Support Logic, SY27-7250.
Problem Determination
Refer to Tables I and" at the back of this publication for problem determination instructions.
IGF0021
CHANNEL DETECTED ERROR ON ddd,pa,err,op,stat
Explanation: A channel-detected error occurred during the
operation of device ddd. In the 'message text the fields are:
ddd
device address. If the device address is not available to
CCH, ddd will be of the format cXX where c is the number
of the associated channel.
pa
processor address
err
error source:
CU
control unit
CHAN channel
PROC processor (CPU)
SCU
storage control unit
STOR
storage
op
failing command code
stat
channel and unit status from the channel status word (CSW)
System Action: A record of the error is queued by CCH for
recording onto the SYSl.LOGREC data set.
Operator Response: Probable hardware error. None.
Problem Determination: Table I, items 2, 18, 30.
IGF5001
IGF500D
}
SOPERATOR
) I/O ERROR
~ PAGING I/O ERROR
REPLY 'YES', DEVICE, OR 'NO'
SWAP xxx TO yyy
Explanation: The message is a repeat for verification of a
SWAP command entered by the operator or a request to move
a volume as a result of a permanent I/O error on device xxx.
•
PAGING I/O ERROR indicates that a duplexed paging request
has received an I/O error.
If the device address is not allowed in reply, device xxx is a
shared direct access storage device. It can only be removed
and replaced on a spare drive on the same control unit and
readied with the address plug xxx.
System Action: The system continues processing. The
operator-initiated request will not complete until the operator
responds to'the message. The 'YES' or 'DEVICE' reply invokes
the DDR function. The 'NO' reply causes a permanent I/O
error to be posted for device xxx, or the operator SWAP
command to be canceled as appropriate.
Operator Response:
• If a SWAP to device yyy is desired, reply 'YES'.
411
If a SWAP is desired, but device yyy is not acceptable,
enter the channel unit address of the device to which the
volume on xxx is to be moved. Make sure that the device
has an available path before entering this reply.
• If a SWAP is not desired, enter reply 'NO'.
• If PAGING I/O ERROR appears in the message text, one or
more jobs will almost certainly be terminated if a 'NO'
response is given.
Note: When continuing with the SWAP, either by answering
'YES' or a three-character device address, do not move the
volume until the 'PROCEED' message, IGF502E, is issued or
data set integrity may be lost.
Caution: If the volume is a direct access storage device, care
must be taken to insure that no head-disk interference ("head
crash") problem exists.
Problem Determination: Table I, items 2, 30.
Section 13: IGF Messages - MCH, DDR, CCH and MIH
13-1
IGF502E
PROCEED WITH SWAP OF xxx TO yyy
Explanation: DDR is waiting for the operator to swap volumes.
System Action: The system continues operation.
Operator Response: Move the volume on device xxx to device
yyy. If a volume is on yyy, move that volume to xxx. Make
both devices ready. If xxx and yyy are the same, make the
device not ready and then make it ready.
IGF5031
ERROR ON ddd, SELECT NEW DEVICE
Explanation: A permanent I/O error has occurred during DDR
tape repositioning which was in process in response to a
SWAP request to ddd. The error occurred positioning the tape
from load point on ddd. This message is followed by IGF509D
to allow the operator to respond.
System Action: The tape is rewound and unloaded. The
system continues operation.
Operator Response: Specify a new device address to replace
ddd in response to message IGF509D, or reply 'NO'. If the
reply is 'NO', the associated job must be canceled by the
operator since the tape is not positioned correctly.
IGF5051
SWAP FROM xxx TO yyy COMPLETE
Explanation: The tape SWAP requested for the volume
originally on xxx is now complete. This message does not
appear for direct access devices or for unit record devices.
System Action: The system continues operation.
Operator Response: None.
IGF5091
IGF509D
OPERATOR
}
I/O ERROR
PAGING I/O ERROR
REPLY DEVICE, OR 'NO'
SWAP ddd
{
Explanation: If OPERATOR appears in the message text, the
SWAP was requested by the operator. No valid 'TO' device is
known and a response is required. This message follows a
SWAP command when the 'TO' device is invalid for a SWAP.
If I/O ERROR or PAGING I/O ERROR appears in the message
text, the SWAP is a result of a permanent I/O error. The I/O
recovery procedures may be repeated on a new device.
PAGING I/O ERROR indicates that a duplexed request has
received an I/O error.
System Action: The system continues processing. The SWAP
will not complete until the operator responds with one of the
indicated replies.
Operator Response: If the DDR function is desired, reply with
the three-character primary device address of the same type
as ddd. An unallocated device on a different channel is usually
preferred. Make sure that the device has an available path
before replying to this message. If the DDR function is not
desired, reply 'NO'.
Note: If PAGING I/O ERROR appears in the message text, a
'NO' reply to the request will almost certainly result in an
abnormal termination for one or more jobs.
Note: When continuing with the swap by answering a
three-character device address, do not move the volume until
the 'PROCEED' message, IGF502E, is issued or data set
integrity may be lost.
Caution: If the volume is a direct access storage device, care
must be taken to insure that no head-disk interference ("head
crash") problem exists.
For tape swaps, if you reply 'NO' to this message and this
message was preceded by message IGF5031, DDR will unload
the tape; you should not re-ready this particular tape because
the system will not reposition it before writing a label on it
during CLOSE processing. A non-labeled scratch tape should
be mounted to satisfy CLOSE.
13-2
VS2 System Messages (VS2 Release 3.7)
IGF511A
WRONG VOLUME MOUNTED ON ddd, MOUNT ser,
~!:~t tnnn
{[SL] )
Explanation: In performing a swap, the volume that had been
on the "from" device was not put on ddd. This message
appears only for tape swaps.
System Action: The system continues operation.
Operator Response: Remove the volume on ddd and replace it
with the correct volume serial, label type (AL, NL, NSL, or SL),
and sequence number (nnn). This message can be repeated as
many as five times if a wrong volume is consistently mounted,
then IGF509D is issued allowing you to reply 'NO' to the swap
request or select another device.
IGF5121
SWAP FROM ddd TERMINATED NO USER FOUND
ERP IN PROGRESS
OPEN/CLOSE/EOV IN PROGRESS
BLOCKCOUNT UNRELIABLE
CANCELLED BY OPERATOR
INVALID USER EXIT
CATASTROPHIC ERROR
INVALID DEVICE
CANCELLED BY USER
JES3 ERROR
Explanation: During a swap, DDR has encountered a condition
that prevents successful completion of the swap request from
device ddd. The various conditions depend on the variable
portion of the message text. Following is a list of the possible
conditions and their meanings:
NO USER FOUND - DDR was unable to locate the user of the
tape after the swap commenced. The user of the tape has
terminated.
ERP IN PROGRESS - While attempting to rewind and unload
the "FROM" tape involved in an operator-requested swap, an
error recovery procedure (ERP) was found to be in progress.
OPEN/CLOSE/EOV IN PROGRESS - DDR has found that the
user of the "FROM" tape is in the process of OPEN, CLOSE,
or EOV. The position of the tape is not known.
BLOCKCOUNT UNRELIABLE - If the user of the tape is using
the EXCP macro for I/O, he did not code the REPOS = Y
parameter in his DCB macro. As a result, the blockcount is not
considered to be accurate and DDR cannot reposition the tape.
If the user of the tape is using the basic sequential access
method, DDR has encountered a condition where the tape is
open for the CNTRL macro format and the blockcount is zero.
As a consequence, DDR cannot determine the position of the
tape. This message also appears for all access methods if an
attempt is made to SWAP a NL tape opened for the MOD
disposition.
CANCELLED BY OPERATOR - This message is confirmation that
the operator has replied 'NO' to message IGF500D or
IGF509D. The swap from ddd is not completed.
INVALID USER EXIT - The installation-written NSLREPOS
routine has returned an invalid return code to DDR.
CATASTROPHIC ERROR - DDR has encountered a machine
check, program check, or ABEND which it cannot retry. The
current swap from ddd is terminated.
INVALID DEVICE - The device ddd entered as the "FROM"
device in th'e swap command is invalid.
CANCELLED BY USER - The installation-written NSLREPOS
routine has indicated that the swap is to be terminated.
JES3 ERROR - A terminating error has occurred in a
DDR/ JES3 subsystem exit routine. The c:urrent swap from ddd
is terminated.
System Action: Processing continues.
Operator Response: The response by the operator depends on
the text of the message. Responses to each of the .conditions
is detailed below:
NO USER FOUND - Issue a DISPLAY U command to determine
if the "FROM" tape is allocated. If it is not, no one is using
the tape and you need not use DDR to move the volume on it.
If the tape is allocated, reissue the swap command to retry the
swap. For a swap requested by the system as a result of a
permanent error, no further action is necessary.
ERP IN PROGRESS - If a system-initiated DDR request does
not occur as a result of a permanent error, reissue the SWAP
command to retry the swap.
OPEN/CLOSE/EOV IN PROGRESS - Reissue the SWAP
command after the OPEN, CLOSE, or EOV processing is
complete. This would involve making required volume mounts
prior to issuing the SWAP command.
BLOCKCOUNT UNRELIABLE - If the user is using EXCP level
I/O, he must correct the program so that it maintains an
accurate blockcount and ensure that the DCB macro is coded
with REPOS == YES. This will allow DDR to support the I/O for
both operator requests and upon the occurrence of errors.
If the user is known to be using BSAM, or the tape is NL,
opened for the MOD disposition, you may attempt to reissue
the SWAP command after tape motion has taken place.
CANCELLED BY OPERATOR - If the tape is an emulator tape,
no action is required since DDR does not support emulator
tapes.
INVALID USER EXIT - Contact the system programmer to make
sure that the NSLREPOS program is in the system. If it is,
make sure that a valid return code (0, 4, 8, 12, 16, or 20) is
being returned to DDR and that no programming errors exist in
NSLREPOS.
Problem Determination: Table I, items 2, Sa, 7d, 16, 18, 29.
INVALID DEVICE - Reissue the SWAP command using a valid
device for the "FROM" device.
CANCELLED BY USER - No action is required.
JES3 ERROR - If the swap was initiated through a SWAP
command, you may attempt to reissue the command. If,
however, the swap was requested by the system as a result of
a permanent error, the affected user has been posted with a
permanent error.
IGF5131
DEVICE ddd INVALID FOR SWAP MOUNT PENDING
UNIT REFERENCE INVALID
UNSUPPORTED USE
INCOMPATIBLE
NOT OPERATIONAL
NOT ALLOCATED
DEVICE TYPE INVALID
JES3 INCOMPATIBLE
Explanation: Device ddd was specified for a swap either in the
SWAP command or in response to message IGF500D or
IGF509D. However, the device cannot be used for one of the
reasons listed above. The meaning of each of the parameters
is as follows:
MOUNT PENDING - DDR found that the 'TO' device has a
mount outstanding for it. The device cannot be used as an
alternate for the 'FROM' device because of a conflict with
device allocation.
UNIT REFERENCE INVALID - A device was specified in
response to message IGF500D or IGF509D or was entered as
the 'TO' device in a SWAP command, however, no
corresponding device could be found in the list of devices
defined at system generation.
UNSUPPORTED USE - A. condition exists on device ddd which
temporarily prevents a swap from taking place, although the
indicated device is supported for a swap.
INCOMPATIBLE - The 'TO' device specified in response to
message IGF500D or IGF509D or in the original SWAP
command was not compatible with the 'FROM' device. The
device selected as the 'TO' device does not have the same
features as the 'FROM' device, or is not in the same device
class. This message also appears if an attempt is made to
swap a shared DASD to an address other than itself.
•
NOT OPERATIONAL - No paths were available to ddd or a
CC == 3 on an SIO was received from device ddd.
NOT ALLOCATED - The 'FROM' tape ddd in the SWAP
command is not allocated to any user.
DEVICE TYPE INVALID - Device ddd is of a device type not
supported by DDR for swaps.
JES3 INCOMPATIBLE - The 'TO' device specified in response
to message IGF500D or IGF5Q9D or in the original SWAP
command was not compatible with the 'FROM' device from
JES3's point of view.
System Action: The command is not executed; processing
continues.
Operator Response: The response depends on which one of
the operands appeared in the text of the message. Respond as
follows for each of the messages:
MOUNT PENDING - For swaps initiated by a SWAP command;
reenter the command after the mount request is satisfied if the
device is the 'FROM' device. If the device is the 'TO' device
for either swaps requested by the system or those initiated by
a SWAP command, reenter another device or 'NO' to the
IGF509D message which follows this one.
UNIT REFERENCE INVALID - Reenter a device address known
to the' system or 'NO' to the IGF509D message which follows
this one. You can determine what devices are known to the
system using the DISPLAY U command.
UNSUPPORTED USE - Reenter the SWAP command using a
supported device if ddd is the 'FROM' device. Otherwise,
reenter the address of a device supported by DDR to the
IGF509D message which follows this one or enter 'NO'.
DDR does not permit swaps under the following conditions:
• Offline 'FROM' device.
• Devices under control of OLTEP.
• Integrated Emulator tapes in original second-generation
format (RECFM == U) coded on DCB.
• NSL tapes if the user exit NSLREPOS is unavailable.
• Tape swaps where the 'TO' device is allocated.
• Unit record devices in ready status.
INCOMPATIBLE - Reply to message IGF509D which follows this
message with a device compatible to the 'FROM' device or
reply'NO'.
Compatible devices are:
Disk swaps supported:
2314 to 2314
2314 to 2319
2319 to 2314
2319 to 2319
3330 to 3330
3330 mod 11 to 3330 mod 11
3340 to 3340
Unit Record swaps supported:
1403 to 1403
1443 to 1443
2501 to 2501
2520 to 2520
2540 to 2540
3211 to 3211
3505 to 3505
3525 to 3525
Section 13: IGF Messages - MCH, DDR, CCH and MIH
13-3
The following tape swaps ar~ supported:
'
7 -track to 7 -track
9-track (single or dual density) to 9-track (single or dual
density), provided that the density in use on the xxx unit is a
valid density specification for the yyy unit.
Note: If a 7 -track tape drive is being used at 200 BPI, you
must assure that the 'TO' device has 200 BPI feature.
Note: Volumes on 3400 series tape drives may only be moved
to other 3400 series drives. However, volumes on 2400 series
tape drives may be moved to either 2400 series drives or
3400 series drives.
NOT OPERATIONAL - Make the physical change necessary to
have a path to the device. Then issue the appropriate VARY
command to allow the device to be reached. The reply to
message IGF509D which follows this one can only be entered
after performing these steps.
NOT ALLOCATED - Since the tape is not allocated, you need
not use DDR to move the tape.
DEVICE TYPE INVALID - Reply to the IGF509D messages with
the CUA of one of the following devices:
Tape:
2401, 2415, 2420, 3410, 3411, 3420 (all models)
Disk:
2314, 2319, 3330, 3330 mod 11, 3340
Unit Record:
1403, 1443, 2501, 2520, 2540, 3211, 3505, 3525
JES3 INCOMPATIBLE - Reply to message IGF509D (which
follows this message), supplying a device compatible to the
'FROM' device from JES3's point of view, or reply 'NO'. For
information on JES3 device compatibility refer to Operator's
Library: OS/VS 2 Reference (JES3), GC38-0226.
IGF910W
UNRECOVERABLE MACHINE FAILURE, RESTART
SYSTEM
Explanation: One of the following errors has occurred:
• A machine check interruption has occurred on the only
online CPU and the associated machine check interruption
code is either invalid or indicates that system damage has
occurred.
• A hard machine check, program check, or loop h.as been
detected on the only online CPU while a previous machine
check was being processed, and recovery is not possible.
System Action: The system enters a disabled wait state.
Operator Response: Probable hardware error. Restart the
system.
Problem Determination: Table I, items 11, 18, 30.
IGF9311
VS2 System Messages (VS2 Release 3.7)
EVENT - jSR tCPU = x
1DG\
CNT = nnn
MODE-{~~~~RD
}
RECORD = ALL
Explanation: The hardware error recovery status is presented
in response to the MODE STATUS command and contains the
following information:
• The event type is SR (for system recovery) or DG (for
degradation).
• The CPU x is the address associated with a processor for
that event.
• The mode is QUIET, RECORD, or RECORD = ALL. QUIET
mode indicates no recording of hardware failures. RECORD
mode indicates that recording of hardware errors will
continue until the count equals the threshold value, then
message IGF9311 will be written and the system will be
placed in QUIET mode for the respective event.
RECORD = ALL mode indicates that all hardware errors will
be recorded. Whenever the count equals a multiple of 4,
message IGF9311 will be issued.
• The· count nnn indicates the number of events that have
occurred since IPL or since the last MODE command issued
for this event and processor.
System Action: Processing continues.
Operator Response: None.
IGF9551
MODE {QUIET
}
RECORD = ALL
REOCRD = nnn
EVENTS ON CPU = ~ x t
1ALL \
FOR
Explanation: In response to a MODE command, the recording
mode of the indicated event class on the specified CPU was
changed to the indicated state.
System Action: Processing continues.
Operator Response: None.
·IGF9581
MODE COMMAND REJECTED, prm PARAMETER
INVALID
Explanation: The indicated parameter is invalid for the MODE
command as specified.
System Action: Processing continues; the MODE command is
rejected and has no effect.
Operator Response: Reissue the MODE command.
IGF9591
MODE COMMAND REJECTED, CPU SPECIFIED IS
~INVALID
t
nnn j SR
EVENTS HAVE OCCURRED ON CPU x,
1DGf
STATUS = ~QUIET t
1RECORD~
Explanation: The indicated number of machine check
interruptions of the system recovery (SR) or degradation (DG)
class have occurred on CPU x. The recording mode for that
class of interruptions is indicated. QUIET indicates that the
thresh hold value for RECORD = nnn mode has been reached
and that the recording mode of the indicated event has been
changed to QUIET. RECORD indicates that the count is equal
to a multiple of 4 and that the recording mode of the indicated
event remains RECORD = ALL.
System Action: Processing continues in the mode indicated.
Operator Response: Report this message to the system
programmer and run IFCEREPO and retain the output.
Problem Determination: Table I, items 18, 30.
13-4
IGF9531
t
10FFLlNE~
Explanation: The MODE command was rejected. Either the
CPU specified was invalid, (the CPU number was greater than
F), or the CPU specified was offline.
System Action: Processing continues; the MODE command is
rejected and has no effect.
Operator Response: Reissue the MODE command, specifying
the proper CPU.
IGF971 I
RECOVERY INITIATED FOR ~STORAGEt
[AT ADDRESS adr]
1SPF
\
FAILURE
Explanation: A storage error was detected or an error was
detected in the storage protect feature protection key for a
storage block. If the location of the failing portion of stora~e
can be determined, its address (in hexadecimal characters) is
indicated in the message.
System Action: The system schedules the appropriate
processing program's functional recovery routine to affect
recovery; processing continues.
Operator Response: Report this message to the system
programmer and run IFCEREPO and retain the output.
Problem Determination: Table I, items 18, 30.
IGF9721
RECOVERY INITIATED FOR PROCESSOR FAILURE ON
CPU x
Explanation: A machine check interruption has occurred on the
indicated CPU and the machine check interruption code
indicates that either instruction processing damage has
occurred or that the registers or PSW were not valid.
System Action: The system schedules the appropriate
processing program's functional recovery routine to affect
recovery; processing continues.
Operator Response: Report this message to the system
programmer and run IFCEREPO and retain the output.
Problem Determination: Table I, items 18, 30.
IGF991E
I
MOUNT AND CHANNEL END
DEVICE
CHANNEL END
DEVICE END
SWAP
PENDING FOR DEVICE ddd
1
Explanation: The Missing Interruption Handler has found one
of the above named conditions pending for device ddd for
more than an installation-specified period of time. (The default
time interval is 3 minutes.)
System Action: Processing continues.
Operator Response: The response depends on the condition
named in the message. The various conditions and the actions
to be taken are:
MOUNT - Ready device ddd. If the unit is ready, issue a Vary
Online command to generate a simulated device end so that
mount processing may continue.
NOTE - A MOUNT message may not yet have been issued to
device ddd. If this is the case, no action should be taken until
the MOUNT message has been issued.
SCHANNEL END
t
1DEVICE AND CHANNELEND~ - A hardware malfunction has
occurred. The I/O request requiring a channel end will be
scheduled for an I/O restart. It will be either posted with a
permanent error or a retry will be attempted.
DEVICE END - Examine device ddd for hardware malfunctions
such as the SELECT light on for a tape, or the SELECT LOCK
light on for disk devices. Check control or switching units for
proper connection. If the device was just rewound or mounted,
issue a Vary Online command to generate a simulated device
end. Issuing a Vary Online command at any other time is
inadvisable since file integrity may be lost. In non-mount
conditions, the jobs using device ddd should be canceled.
SWAP - Complete the action necessary to finish the DDR
swap, (mount the volume on device ddd).
Problem Determination: Table I, items 2, Sa, 16, 24, 29 or 30.
Section 13: IGF Messages - MCH, DDR, CCH and MIH
13-5
•
13-6
VS2 System Messages (VS2 Release 3;7)
Section 14: Checkpoint/Restart Messages (IHJ)
Component Name
IHJ
Program Producing Message
Checkpoint/ restart.
Audience and Where Produced
For operator: console.
Message Format
xx IHJnnns text
xx
Message reply identification (absent, if operator reply not required).
nnn
Message serial number.
s
Type code:
Action; operator must perform a specific action.
A
I
Information; no operator action is required.
text
Message text.
Comments
None.
Associated Publications
OS!VS Checkpoint/Restart, GC26-3784
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IHJOOOI
CHKPT
iii [ddn] NOT TAKEN (xxx)
During execution of a CHKPT macro instruction,
an error occurred before the checkpoint routine wrote any part
of a checkpoint entry.
In the message text, jjj is the jobname, ddn is the data
definition name of the checkpoint data set (which is omitted if
xxx is 001), and xxx indicates why the checkpoint entry was
not written:
xxx Explanation
001 A checkpoint parameter list error was encounterd.
(Return code - 08.)
002 An uncorrectable input/output error occurred or a DD
statement error was encountered while opening the data
control block (DCB) for the checkpoint data set. Possibly,
a DD statement was missing. (Return code - OC.)
003 Insufficient space was available for a work area. (Return
code - 08.)
005 The checkpoint data set key length was not equal to
zero. (Return code - 08.)
006 The checkpoint data set record format was not u.
(Return code - 08.)
007 The data control block (DCB) for the checkpoint data set
was opened for other than basic sequential access
method (BSAM) or basic partitioned access method
(BPAM) processing, or MACRF = w was not specified in
the DCB. (Return code - 08.)
008 The time interval specified in the STIMER macro
instruction had not elaps~d. (Return code - 08.)
009 The CHKPT macro instruction was issued in an exit
routine other than the end-of-volume exit routine.
(Return code - 08.)
010 A graphic data control block (DCB) has been detected
but is not supported in checkpoint restart. (Return code Explanation:
/
08.)
011 The current task was a subtask. (Return code - 08.)
012 The current task had subtasks. (Return code - 08.)
014 A reply to a WTOR macro instruction was not received.
(Return code - 08.)
015 An incorrect checkpoint identification length or format
was encountered. (Return code - 08.)
•
016 The checkpoint data set device type was not magnetic
tape or direct access. (Return code - 08.)
019 Either MACRF = W was not specified for the checkpoint
021
025
027
029
030
032
041
042
043
044
045
134
146
data control block (DCB), or the data control block was
opened by the user's program, but was not opened for
output. (Return code - 08.)
LABEL = AL or LABEL = AUL was coded in the DD
statement for the checkpoint data set. These values for
the LABEL parameter must not be used in a checkpoint
data set DD statement. (Return code - 08.)
An error occurred while reading a job control table (JCT)
from the scheduler work area (SWA). (Return code - ~C.)
Secondary allocation occurred while writing a checkpoint
data set entry on a direct access volume, or
end-of-volume occurred twice while writing the
checkpoint data set entry on tape. (Return code - 08.)
The OPTCD subparameter of the DCB parameter was
coded incorrectly. The value coded is not acceptable for
a checkpoint data set. (Return code - 08.)
An uncorrectable input/output error occurred while
quiescing pending input/ output requests. (Return code OC.)
DISP = SHR was specified for an ISAM data set at
checkpoint time. (Return code - OC.)
CHKPT was issued with a VSAM data set open for create
mode processing and no reposition specified.
An error occurred during repositioning for a VSAM data
set.
CHKPT was issued with an entry-sequenced data set
open for output, an immediate-upgrade set open over it,
and reposition required. NRE or NRC must be specified.
CHKPT was issued for a relative-record data set open
for create mode direct processing.
CHKPT was issued with a VSAM data set open with the
GSR option.
Insufficient storage was available for VSAM CLOSE
TYPE=T.
An I/O error was encountered completing I/O requests
for VSAM CLOSE TYPE = T.
Section 14: IHJ Messages - Checkpoint/Restart
14-1
147 The ACB is not for a valid data set, for VSAM CLOSE
TYPE = T.
159 An MSS (Mass Storage System) ACQUIRE/RELINQUISH
error occurred, for VSAM CLOSE TYPE = T.
200 Unsuccessful PURGE -- uncorrectable. (Return code OC.)
202 SETLOCK failed -- uncorrectable. (Return code - OC.)
206 VT AM data set open - - close all VT AM data sets prior to
issuing CHKPT. (Return code - 08.)
208 The new checkpoint data set presented by the user is
not empty. The integrity of this pre-data is uncertain and
therefore, unusable. (Return code - 08.)
209 Another user DCB is concurrently open to the new
checkpoint data set offered by the user. (Return code 08.)
210 The checkpoint data set offered by the user was defined
with DISP = SHR. (Return code - 08.)
211 An attempt to create a new checkpoint data set has
failed due to an insecure volume. (Return code - 08.)
212 The tape checkpoint data set offered by the user does
not have standard labels. (Return code - 08.)
213 The checkpoint data set offered by the user is a
subsystem data set. Subsystem data sets cannot be used
as checkpoint data sets. (Return code - 08.)
214 The new checkpoint data set offered by the user exists
on a shared direct access device. Concurrent opens
cannot be controlled; therefore, the data set is
unacceptable. (Return code - 08.)
224 SAM-SI(non-CI) data set open -- close all
SAM-SI(non-CI) data sets prior to issuing CHKPT.
(Return code - 08.)
240 Recovery environment could not be established when
checkpointing VSAM data sets. (Return code - OC.)
241 Uncorrectable error occurred when checkpointing VSAM
data sets. (Return code - OC.)
242 A machine check occurred while checkpointing VSAM
data sets. (Return code - OC.)
250 IMAGELIB data set open when checkpoint taken. (Return
code - 08.)
System Action: A checkpoint entry was not written. The
current checkpoint is not eligible for restart but all previous
checkpoints are eligle for deferred restarts, and the last valid
checkpoint entry is eligible for automatic restart.
If MOD is not the disposition of the checkpoint data set and if
this is the first issuance of the CHKPT macro instruction after
the data control block for the data set was opened, then all
checkpoint entries in the data set are lost. (The data control
block may have been opened by the programmer or as a result
of this checkpoint request.) However, if xxx is 001, no entries
are lost.
Operator Response: If xxx is 025, 030, 200, 202, 240, 241, or
242 and if the programmer indicated that the job was to be
canceled if it did not take checkpoints correctly, cancel the
job; otherwise, none. (The job may execute successfully and
not require restart.)
Programmer Response: If xxx is 025, 030, 042, 146, 200,
202, 240, 241, or 242, resubmit the job.
If xxx is other than 025, 030, 042, 200, or 202, probable user
error.
If xxx is 001, 002, 005, 006, 007, 010, 015, 016, 019, 021,
029, 041 043, 044, 045, or 147, correct the indicated error
and resubmit the job.
If xxx is 003, or 134, use a larger storage area, and resubmit
the job.
If xxx is 008, cancel the time interval before issuing the
CHKPT macro instruction, and restore the interval. Then
resubmit the job.
14-2
VS2 System Messages (VS2 Release 3.7)
If xxx is 009, make sure that the CHKPT macro instruction is
not issued in an exit routine other than the end-of-volume exit
routine. Then resubmit the job.
If xxx is 011, or 012, make sure that the CHKPT macro
instruction is not issued when multiple tasks (created by the
ATTACH macro instruction) exist. Then resubmit the job.
If xxx is 014, issue a WAIT macro instruction after the WTOR
macro instruction, but before the CHKPT macro instruction.
Then resubmit the job.
If xxx is 159, an MSS hardware error occurred. See associated
message IEC2521 for more details.
If xxx is 206, or 224, make sure that all VTAM and/or
SAM-SI(non-CI) data sets are closed prior to issuing CHKPT.
If xxx is 208, and the new checkpoint data set is a sequential
data set, the failure occurred as a result of the data set being
opened for MOD and residual data was found to exist. Either
remove the MOD disposition, reinitialize the data set to an
empty status, or reallocate the data set; then resubmit the job.
If the data set is a partitioned data set, the failure occurred as
a result of residual members existing in the directory. Either
scratch the members or r.eallocate the data set; then resubmit
the job.
If xxx is 209, it was determined that another data control block
was opened to a new checkpoint data set to be created (on
the occurrence of the first issuance of CHKPT to that data
set). Remove the logic that violates this restriction; then
resubmit the job.
If xxx is 210, change the JCL to reflect a disposition other
than SHR for the checkpoint data set; then resubmit the job.
If xxx is 211, the candidate volume for a checkpoint data set
was rejected by the operator as being insecure. Contact
installation personnel and verify the eligibility of the volume for
creating checkpoint data sets.
If xxx is 212, a tape data set to be used for creating a
checkpoint data set was not specified as having standard
labels. Correct the JCL and resubmit the job.
If xxx is 213, a checkpoint data set was found to be defined
as a subsystem data set (SYSIN/SYSOUT). Correct the JCL
and resubmit the job.
If xxx is 214, a checkpoint data set was found to be mounted
on a shared direct access device. Contact operations
personnel to make sure that this does not occur.
If xxx is 250, ensure that all IMAGELIB DCBs are closed prior
to issuing CHKPT.
Problem Determination: Table I, items 1, 3, 13, 29.
IHJ0011
iii (ddn,ddd,ser) INVLD checkid
(xxx)
Explanation: During execution of a CHKPT macro instruction,
an error occurred while the checkpoint routine was writing· a
checkpoint entry.
In the message text, jjj is the jobname, ddn is the data
definition name of the checkpoint data set, ddd is the unit
name, ser is the serial number of the volume containing the
data set, checkid is the checkpoint identification, and xxx
indicates why the checkpoint was invalid:
xxx Explanation
017 Execution of a STOW macro instruction was unsuccessful;
there was no space in the checkpoint data set directory.
(Return code - 08.)
022 An error occurred while reading system control blocks
from the scheduler work area (SWA). (Return code - OC.)
023 An uncorrectable input/ output error occurred while
writing the checkpoint data set. (Return code - OC.)
026 Execution of a STOW macro instruction was unsuccessful;
a permanent input/output error occurred. (Return code OC.)
'-.
)
027 End-of-volume occurred while writing a checkpoint data
set entry on a direct access volume and secondary
allocation was requested and allocated, or end-of-volume
occurred twice while writing a checkpoint data set entry
on tape. (Return code - 08.)
207 Failure in the subsystem interface when checkpointing
subsystem data sets. (Return code - OC.)
240 Recovery environment could not be established when
checkpointing VSAM data sets. (Return code - OC.)
241 Uncorrectable error occurred when checkpointing VSAM
data sets. (Return code - OC.)
242 A machine check occurred while checkpointing VSAM
data sets. (Return code - OC.)
System Action: A partial invalid checkpoint entry was written.
The current checkpoint is not eligible for restart, but all
previous checkpoints are eligible for deferred restarts, and the
last valid checkpoint entry is eligible for automatic restart.
Operator Response: If xxx is 017,022, 026, 207, 240, 241, or
242, and if the programmer indicated that the job was to be
canceled if it did not take checkpoints correctly, cancel the
job; otherwise, none.
If xxx is 023, and if the programmer indicated that the job was
to be canceled if it did not take checkpoints correctly, cancel
the job; otherwise, none. If the job is canceled or terminates
abnormally, and a rerun is attempted, then 1) if a nonspecific
volume was requested for the checkpoint data set, mount a
different volume during the rerun than was originally mounted,
or 2) vary offline the device originally containing the
checkpoint data set.
If xxx is 027, and if the programmer indicated that the job was
to be canceled if it did not take checkpoints correctly, cancel
the job; otherwise, none. If the job is canceled or terminates
abnormally, attempt a rerun only if the volume containing the
checkpoint data set was requested as a nonspecific volume.
During the rerun, mount a volume (tape or direct access)
containing more available space than was contained on the
volume used originally.
Programmer Response: If checkpoint identifications specified
by the programmer are being used in a sequential data set,
then a checkpoint identification different from checkid in the
message text must be specified for the next entry, to make the
next entry retrievable in a restart.
If xxx is 017, correct the checkpoint data set directory, and
resubmit the job.
If xxx is 022, 023, 026, 027, 207, 240, 241, or 242, resubmit
the job.
Problem Determination: Table I, items I, 3, 13, 29.
IHJ0021
jjj (ddn,ddd,ser) ERROR checkld (xxx)
restarts; however, deferred restarts are possible if the
VIO data sets are made DUMMY. An automati~ restart
cannot occur until a new and successful checkpoint is
taken. (Return code - OC.)
215 Unsuccessful RESTORE - uncorrectable. (Return code 18.)
System Action: A valid checkpoint entry that can be used to
perform a deferred restart was written.
Operator Response: If the programmer indicated that the job
was to be canceled if this message was issued, cancel the job;
otherwise, none.
Programmer Response: If xxx is 025, as desired, resubmit the
job or request that a restart be performed at the indicated
checkpoint.
If xxx is 204 or 205, an error occurred while checkpointing VIO
data sets to the job journal. Deferred restarts may be
accomplished on the subject checkpoint entry; however, the
VIO data sets must be made DUMMY.
If xxx is 215, an error occurred while restoring the purged I/O
operations. A checkpoint entry was successfully written;
however, continuation of the user's program may produce
errors.
Problem Determination: Table I, items I, 3, 13, 29.
IHJ0041
jjj (ddn,ddd,ser) CHKPT checkid
Explanation: A CHKPT macro instruction was executed
successfully; no errors occurred.
In the message text, iii is the job name, ddn is the data
definition name of the checkpoint data set, ddd is the unit
name, ser is the serial number of the volume containing the
data set, and checkid is the checkpoint identification.
System Action: A valid checkpoint entry was written. A restart
was requested.
Programmer Response: If a deferred restart is to be
performed, code the checkpoint identification (checkid in the
message text) in the RESTART parameter of the JOB
statement.
If multiple checkpoint data sets were used, use ddn in the
message text to determine the name of the data set containing
the desired checkpoint entry. Code the data set name in the
DSNAME parameter of the SYSCHK DO statement.
If the checkpoint data set is multivolume, indicate on the
SYSCHK DO statement that the volume containing the
checkpoint data set is the first (or only) volume containing the
data set. That is, code the serial number (ser in the message
text) in the VOLUME = SER parameter or, if the data set is to
be retrieved using the catalog, code the volume in the volume
sequence subparameter of the VOLUME parameter. Then
resubmit the job.
Explanation: During execution of a CHKPT macro instruction,
an error occurred. However, a checkpoint entry was written
successfully.
In the message t~xt, jjj is the jobname, ddn is the data
definition name of the checkpoint data set, ddd is the unit
name; ser is the serial number of the volume containing the
data set, checkid is the checkpoint identification, and xxx
indicates the cause of the error:.
xxx Explanation
025 An error occurred while writing the job. control table
(JCT) to the scheduler work area (SWA). (Return code OC.)
204 Unsuccessful WIJOURN - The checkpoint is unavailable
for automatic restarts; however, deferred restarts are
possible if the VIO data sets are made DUMMY. (Return
code - OC.)
205 Unsuccessful WIJOURN - This and previous checkpoints
taken during this step are ineligible for automatic
I
IHJ0051
jjj (ddn,ddd,ser) ENQS checkid
Explanation: A CHKPT macro instruction was executed
successfully. Although no errors occurred, the user's program
was enqueued upon resources. (The ENQ macro instruction
was issued by either the problem program, the BDAM READ
macro instruction with exclusive control, the RESERVE macro
instruction, or the BDAM WRITE macro instruction with
variable-length (V) or undefined (U) record format.) Note that
the enqueues will not be reestablished if restart occurs.
In the message text, iii is the jobname, ddn is the data
definition name of the checkpoint data set, ddd is the unit
name, ser is the serial number of the volume containing the
data set, and checkid is the checkpoint identification.
System Action: A valid checkpoint entry was written. A restart
was requested.
Programmer Response: Make sure that the program
reestablished. the enqueues upon restart.
Section 14: IHJ Messages - Checkpoint/Restart
14-3
IHJ0061
jjj RESTARTING AT xxxxxx yyyyyy
Explanation: During execution of a checkpoint restart for job
jjj, the virtual storage indicated in the message text was
requested.
)
In the message text, xxxxxx is the lowest address and yyyyyy
is the highest address in virtual storage.
System Action: If the requested areas are currently .
unavailable, restart is delayed until the areas are available.
Operator Response: Use the DISPLAY A command to
determine if the required areas are occupied by system tasks
or by other job step tasks.
If the area is occupied by another job step task, either allow
the system task to continue and terminate (if a reader), or
stop the system task (if a reader or writer).
If the area is occupied by another job step task, either allow
the job step task to continue and terminate, or cancel the job
step task.
IHJ0071
RESTART NOT SUCCESSFUL FOR jjjj (xxx,[dddD
Explanation: During execution of a checkpoint restart for job
jjjj, an error occurred.
In the message text, ddd identifies the unit address for tape
errors and xxx indicates why the restart was not successful:
xxx Explanation
002 The checkpointing job or step specified
ADDRSPC = REAL (V = R) and the restarting job or step
did not, or vice versa.
024 An uncorrectable error occurred while reading control
blocks from the scheduler work area (SWA).
028 An uncorrectable input/output error occurred in the
user's nonstandard label (NSL) routine.
034 A DO statement was missing for the restarted step.
038 An uncorrectable input/ output error occurred while
reading the checkpoint data set.
040 An uncorrectable input/output error occurred while
reading standard volume labels.
041 Wrong length record detected when reading checkpoint
data set.
044 Insufficient devices were available for restart.
048 An uncorrectable input/output error occurred while
reading a volume label on a direct access device.
049 An MSS (Mass Storage System) error occurred while
mount processing. See message IEC4661 for explanation.
052 A module, which was loaded in the link pack area and
was being used by job iii when the checkpoint was taken,
is either not in the area now or is in a different location
in that area.
060 An error occurred while repositioning to the correct data
set on tape.
064 Data set repositioning error occurred on tape.
072 An uncorrectable input/output error occurred while
reading a data set control block (DSCB). This message is
also issued if a data set was being scratched or deleted.
076 A direct access data set (other than the system input
data set) being processed for input did not occupy the
same extent as it did originally; that is, discrepancies
were found in comparing the space allocations described
in the data extent block (DEB) and the data set control
block (DSCB).
079 DUMMY was specified for an open data set and either
the data set was not being processed by the basic or
queued sequential access methods or the checkpoint at
which restart was to occur was established in an
end-of-volume exit routine for the data set.
082 The TCAM control program was not active at restart.
083 The QNAME = parameter's process entry is not the
name of a process entry in the terminal table.
14-4
VS2 System Messages (VS2 Release 3.7)
084 A QNAME = parameter's process entry is being used by
another user.
085 Core storage is not available in the mesage control
program to build necessary control blocks.
092 An error occurred during basic partitioned access method
(BPAM) processing. For example, an error was detected
after the convert routine or after reading the directory
blocks.
096 An error occurred during use of the STOW macro
instruction to delete a member from the directory.
132 The ddname for the VSAM data set was not found in the
TIOT.
133 An I/O error was detected while the system was reading
or writing the JFCB for a VSAM data set.
134 The storage requested by the OPEN or CLOSE routine
was not available.
136 An I/O error was detected while the system was reading
or writing a catalog entry for VSAM.
137 The VSAM catalog entry was not found.
138 An invalid password for the VSAM data set was
indicated.
140 The parameters specified for a VSAM ACB conflict with
previously specified parameters.
141 An I/O error was detected reading the volume label for
VSAM data set processing.
142 The VSAM data set was not available for use.
144 An attempt to fix pages in real storage failed.
145 The VSAM catalog does not exist or was not open.
146 An I/O error occurred while completing an I/O request.
147 The ACB is not for a valid data set.
148 An unusable data set was open for output.
149 Access to the data set is via an empty path alternate
index.
150 The format-4 DSCB indicates the volume is unusable.
153 The ACB indicates LSR (local shared resources) and the
data set is empty.
154 The ACB indicates LSR and the key length of the data
set exceeds MAXKEY in the BLDVRP macro.
155 LSR is indicated with BSPH (buffer space) too small.
157 The LSR VSRT does not exist.
158 RESET is specified for a non-reusable data set.
159 An MSS (Mass Storage System) ACQUIRE/RELINQUISH
error occurred.
160 There is a volume time stamp discrepancy and the ACB
is for output.
161 A catalog recovery area (CRA) volume was not mounted.
181 An error occurred during VSAM restart preformat routine.
182 An error occurred during VSAM restart verify routine.
183 An error occurred during VSAM restart put routine.
184 An error occurred during VSAM restart index put routine.
190 An error occurred/while attempting to obtain catalog
information for the cluster identified by the ddname in
message IHJ0091.
191 An error occurred while attempting to mount volumes for
the ddname identified by message IHJ0091.
193 Checkpoint was taken during create mode but at restart
time the data set was no longer in create mode.
194 The catalog entries for a VSAM upgrade path have been
altered since checkpoint.
195 Insufficient storage is available for a VSAM restart.
196 The catalog for one or more VSAM data sets has been
updated, indicating that another job successfully processed the
data set after the checkpoint was taken. Restart cannot
restore the data set to its checkpoint status.
198 A VSAM data set expanded to a new volume after the
checkpoint was taken.
199 An error occurred during BLDVRP processing in VSAM
restart.
VS2.03.808
VS2.03.810
201 PGFIX failed -- uncorrectable.
202 SETLOCK failed -- uncorrectable.
203 An illegal attempt has been made to invoke IEFRSTRT.
Only the scheduler may invoke IEFRSTRT.
207 A failure occurred in the subsystem interface -- retry.
216 Residual subpool allocations in the user's region have
prevented a successful reallocation of the user's
checkpoint-time region image.
217 FINOPAGE failed -- uncorrectable.
218 An attempt to restart using an old checkpoint data set
that is insecure (not the checkpoint data set that is currently
being used for the restart).
220 The data set control block (OSCB) address of a data set
to be repositioned has changed since the checkpoint was
taken.
221 The wrong password was given for a password-protected
data set that was to be repositioned.
222 The tape data set name, recorded in header labell, has
changed since the checkpoint was taken.
230 The checkpoint data set was found not to be secure.
231 An error occurred during dynamic allocation of the
checkpoint data set.
232 The checkpoint data set could not be successfully
opened.
233 The checkpoint data set is partitioned and the specified
entry could not be found.
235 A checkpoint entry record of undetermined type was
encountered, or an END record was not found when expected.
237 A specified checkpoint entry could not be found.
238 An error occurred during dynamic allocation or dynamic
deallocation for a private or implied catalog necessary for
DSDR processing.
239 During a deferred restart a non-DUMMY DD entry was
found for a VIO data set, or a dynamically allocated VIO data
set was unallocated after the checkpoint was taken.
240 Recovery environment could not be reestablished when
repositioning VSAM data sets.
241 An uncorrectable error occurred when processing VSAM
data sets.
242 A machine check occurred when repositioning VSAM data
sets.
243 An invalid SSCR record was encountered in the
checkpoint data set entry when repositioning VSAM data sets.
251 A data set which was not a checkpoint data set at
checkpoint time was found to be open to a secure checkpoint
data set at restart time.
255 A RACF processing error occurred during restart.
System Action: Restart for job jjj is terminated.
Programmer Response: If xxx is 002, make sure that the V = R
status of both the checkpoints and restarting job or step are
the same. That is, if ADORSPC = REAL was specified at
checkpoint time, it can only be specified, and must be
specified at restart time.
If xxx is 024, or 092, and if the restart was deferred, the
restart may be attempted again.
If xxx is 028, 040, 048, 060, or 072, and if the restart was
deferred, the restart may be attempted again. If a preceding
input; output error message for the restarted job identified the
device in error, vary the device offline before attempting the
restart again.
If xxx is 033, 034, 037, 044, 052, 076, 079, 193, 194, 203,
218, 220, 221, 222, or 223, probable user error.
If xxx is 033, or 037, make sure that the checkpoint
identification subparameter of the RESTART parameter of the
JOB statement specifies a checkpoint entry on the volume
specified by the SYSCHK DD statement. Then resubmit the job.
If xxx is 034, supply the missing DD statement. Then resubmit
the job.
If xxx is 038, and if the restart was deferred, the restart may
be attempted again. However, vary the device containing the
checkpoint data set offline before attempting the restart again.
If xxx is 038, 060, 064, or 096, either restart at an earlier
checkpoint or repeat the original execution, using a different
volume. Then resubmit the job.
If xxx is 044, make sure that the UNIT parameter of the DD
statement accurately reflects the device requirements for the
data set. Then resubmit the job.
If xxx is 052, make sure that the IPL parameters are the same
parameters that were in use when the checkpoint was taken.
If xxx is 072, make sure that no data set has been scratched
or deleted.
If xxx is 076, make sure that no input data set (other than the
system input data set) has been expanded, or rewritten, in its
original volume. Then resubmit the job.
If xxx is 079, make sure the DUMMY is specified only for data
sets being processed by the queued or basic sequential access
methods. Also, make sure that restart is not to occur at a
checkpoint that was established in an end-of-volume exit
routine for a data set that has been made DUMMY.
If xxx is 082, or 085, make sure that the TCAM control
program region is active and is large enough to add control
blocks. Resubmit the job.
If xxx is 083, or 084, make the necessary corrections to the
QNAME = parameter and resubmit the job.
If xxx is greater than or equal to 100 and less than 200, the
error is for VSAM only. For additional information, refer to the
description of message IEC1611 or IEC2521 if issued.
If xxx is 132, supply a DDNAME and rerun the job.
If xxx is 133, specify a different device for the catalog causing
the problem and rerun the job.
If xxx is 134, 141, 142, 144 146, 181, 182, 183, or 184,
resubmit the job.
If xxx is 137, make sure that the data set entry is contained in
the master catalog or a user catalog specified in a JOBCAT or
STEPCAT DD statement. Use the Access Method Services
LlSTCAT command to list the data set entries contained in a
specific catalog.
If xxx is 138, make sure that the correct password was
supplied in the ACB macro or by the system or TSO terminal
operator. Use the Access Method Services LlSTCAT command
to list the passwords for each data set in a catalog. (You will
need the master password for the catalog to do this.)
If xxx is 140, correct the ACB parameter in error, and rerun
the job.
If xxx is 145, or 190 make sure the correct catalog is open,
and rerun the job.
If xxx is 147, correct the indicated error as per the open/close
error message, and resubmit the job.
If xxx is 148, use the Access Method Services IMPORT
command to load a backup copy of the data set, or delete and
reload the data set.
If xxx is 149, use the Access Method Services BLDINDEX
command to build the alternate index defined under the path
that the OPEN was issued against.
If xxx is 150, use the Access Method Services CONVERTV
command to restore the unusable volume. Then rerun the job.
If xxx is 153, change the· ACB so that LSR is not specified
when the data set is opened for create, and rerun the job.
If xxx is 154, the length of MAXKEY in the BLOVRP macro
must be increased and the job rerun.
If xxx is 155, the largest buffer size in the BLDVRP macro
must be increased and the job rerun.
If xxx is 157, the BLDVRP macro has probably not been issued
or a failure was detected in BLDVRP. Make sure the BLDVRP
macro was executed correctly before trying to open the ACB
with LSR specified.
Section 14: IHJ Messages - Checkpoint/Restart
14-5
VS2.03.808
VS2.03.810
(~
If xxx is 158, correct the indicated error as per the open/close
error message, and rerun the job.
If xxx is 159, this is a hardware error. Proceed as specified
under the MSS return code shown in the preceding message.
If xxx is 160, the volume contents do not correspond with the
catalog contents for that volume. If the volume contents are
most current then the catalog should be restored. For further
information on catalog recovery, see OS/VS2 Access Method
Services.
If xxx is 161, ensure that a DO statement is provided for a
catalog recovery area (CRA) volume.
If xxx is 191, increase the number of units allocated for the
ddname specified in message IHJ0091.
If xx is 193, a restart is not allowed. Take the checkpoint after
the data set is loaded.
If xxx is 194, the immediate-upgrade set has been modified
and a restart is not allowed.
If xxx is 195, or 199, increase the available storage and rerun
the job.
If xxx is 196, override the condition, and allow restart by
coding AMP = CROPS = NCK in the DO statement for the data
set. Be aware, however, that changes might have been made
to the data between the time the checkpoint was taken and
when restart is attempted. A data set that has been extended
to span volumes since the checkpoint was taken, cannot be
restarted.
If xxx is 198, the checkpoint cannot be restarted. For a
deferred restart, resubmit the job selecting a checkpoint taken
after the data set expanded to the new volume.
If xxx is 201, 202, 207, 215, 216, 217, 231, 232, 240, or
242, resubmit the job.
If xxx is 203, remove either the JCL or program logic that
attempts to execute IEFRSTRT, then resubmit the job.
If xxx is 218, or 230, a checkpoint data set was found not to
be secure. Contact operations personnel to verify secure
status of the subject volume.
If xxx is 220,or 222, the data set has been moved or the data
set name has changed since checkpoint; therefore a restart
cannot be performed.
If xxx is 221, obtain the proper password for the
password-protected data set, then resubmit the job.
If xxx is 231, refer to the accompanying IKJ message for the
nature of the failure.
14-6
VS2 System Messages (VS2.03.808)
If xxx is 233 or 237, verify the accuracy of CHECKID for the
checkpoint entry in the RESTART parameter of the JOB
statement; then resubmit the job.
If xxx is 235, 241, or 243, resubmit the job, selecting another
checkpoint entry.
If xxx is 238, verify status and contents of all private and
implicit catalogs used by this job.
If xxx is 239, change VIO data sets to be DUMMY; then
resubmit the job.
If xxx is 251, ensure the proper data set volume was mounted
at restart time. Also, verify the status of the subject volume by
contacting the operations personnel.
If xxx is 255, see IHJl011 for information.
Problem Determination: Table I, items 1, 3, 13, 29.
IHJ0081
iii
RESTARTED
Explanation: A checkpoint restart for job jjj has completed
successfully.
System Action: Processing of job
Operator Response: None.
IHJOIOI
iii continues.
CHECKPOINT RESTART OF JOB jjj ABENDED
Explanation: Job jjj was being initialized for checkpoint/restart
and there was an abnormal termination while processing the
checkpoint data set.
System Action: A dump is taken to the SYSl.DUMP data set.
The job is flushed by the initiator.
Programmer Response: If the dump indicates a user error,
correct the error and resubmit the job. If the dump indicates a
system error, see the problem determination section below.
Problem Determination: Table I, items 1, 3, 4, 29.
IHJIOll
USER NOT AUTHORIZED TO DASD DATA SET
dsn,Yolser
Explanation: Although the user was authorized by RACF to
access the data set at the time it was opened, the user is not
authorized at the time of restart.
System Action: Restart will be terminated with a S13F abend.
Programmer Response: Obtain authorization to the data set
from the data set owner.
Problem Determination: Table I, items 1, 3, 5, 29, 36.
TSO Messages (IKJ)
Component Name
IKJ
Program Producing Message
Time Sharing Option.
Audience and Where Produced
For programmer: SYSOUT data set.
For operator: console.
Message Format
IKJnnnl text
(in SYSOUT)
xx IKJnnns text
(on console)
nnn
Message serial number.
text
Message text.
xx
Message reply identification (absent, if operator reply not required).
s
Type code:
Action; the operator must perform a specific action.
A
D
Decision; the operator must choose an alternative.
.
E
Eventual action; operator must perform a specific action when he has time.
I
Information: no operator action is required.
Comments
None.
Associated Publications
OS!VS2 TSO Terminal User's Guide, GC28-0645
Operator's library: OS/VS2 Reference (JES2). GC38-0210
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
TSO Programmer and Operator Messages
(IKJnnns)
IKJOOOI
/
cm userid
Explanation: The command verb and operand identified by cm
were entered from a TSO terminal by a user identified by
userid.
System Action: The command, em, is processed.
Operator Response: None.
IKJ0051
TS START REJECTED - MEMBER OF SYSl.PARMLIB
NOT FOUND
Explanation: The member name specified either explicitly by
the operator or by default could not be found in
SYSl.PARMLIB.
System Action: Time sharing initialization processing
terminates.
Operator Response: Reenter the MODIFY command and either
omit the member name or specify it correctly. Omitting the
member name causes the system to search for member
IKJPRMOO.
IKJ0061
I/O ERROR READING SYSl.PARMLIB
Explanation: An I/O error occurred when an attempt was
made to read a member of SYSl.PARMLIB.
System Action: Time sharing initialization processing will
continue using defaults for time sharing system parameter
values.
Operator Response: None.
Problem Determination: Table I, items 2, 4, 25c, 26c, 29.
IKJ0071
~ ..
TS START REJECTED - TIME SHARING IS IN
PROGRESS
Explanation: A TS = START MODIFY command was entered
when time sharing was already active.
System Action: The extra command is ignored.
Operator Response: None.
IKJ0191
•
TIME SHARING IS INITIALIZED
Explanation: Time sharing initialization is complete.
System Action: LOGONs will now be accepted.
Operator Response: None.
IKJ0211
TS STOP REJECTED - TIME SHARING IS NOT IN
PROGRESS
Explanation: A TS = STOP MODIFY command was entered
when time sharing was not active.
System Action: The command is ignored.
Operator Response: None.
IKJ024D
TS STOP IN PROGRESS - REPLY 'U', OR 'FSTOP'
Explanation: A TS = STOP MODIFY command was entered
when stop processing was already in progress from a previous
command.
System Action: Normal stop processing will continue until a
reply is received.
Operator Response: Reply AU' to allow time sharing to
complete normally. This will allow users to receive all
messages queued for them. If the system seems unable to
complete normally, reply 'FSTOP' and time sharing will
terminate immediately.
IKJ1391
BROADCAST DATA SET NOT USABLE, I/O SYNAD
ERROR
Explanation: An operator SEND command was issued which
required accessing the broadcast data set. However, in
accessing the data set a read/write failure was encountered.
System Action: Processing is terminated; messages mayor
may not have been saved in SYSl.B~ODCAST.
SYSl.BRODCAST -independent processing has been completed.
Operafor Response: Report this message to the system
programmer.
Programmer Response: Determine and remove the cause of
the I/O error.
Section 15: IKJ Messages - TSO
15-1
IKJl401 BROADCAST DATA SET NOT USABLE, CANNOT OPEN
DATA SET
Explanation: An operator SEND command was issued which
required accessing the broadcast data set. However,
SYS1.BRODCAST could not be opened.
System Action: Processing terminates and no messages are
saved in SYS1.BRODCAST. SYS1.BRODCAST -independent
processing is completed.
Operator Response: Report this message to the system
programmer.
Programmer Response: The master scheduler TIOT must
contain a DO entry for the broadcast data set. The ddname on
this entry must be SYSLBC.
IKJ1411
BROADCAST DATA SET NOT USABLE,
INSTALLATION MUST REFORMAT
Explanation: An operator SEND command was issued which
required accessing the broadcast data set. However, the
broadcast data set is not in release 2 format or has not been
iniUalized.
System Action: Processing terminates and no messages are
saved in SYS1.BRODCAST. SYSl.BRODCAST -independent
processing is completed.
Operator Response: Report this message to the system
programmer.
Programmer Response: Use the SYNC subcommand of
ACCOUNT to initialize the broadcast data set and synchronize
it with the UADS. The SYNC subcommand can be issued in the
foreground or in the background using the TMP in the
background.
IKJ1421
INVALID USERID(S) userid userid ... userid
subcommand of ACCOUNT. The ACCOUNT command may also
be used to authorize userids for TSO.
IKJ1451
IKJEFXSR ESTAE ERROR, CODE rc
Explanation: This message is issued if there is a non-zero
return code from ESTAE in IKJEFXSR, where rc is the return
code.
Return
Code
04
Explanation
ESTAE OV was specified with a valid exit address, but
the current exit is either nonexistent, not owned by
the user's RB, or is not an ESTAE exit.
08
BRANCH = YES was issued for the current SVRB with
a create request; the previous BRANCH = YES exit is
canceled and the new exit is made the current exit.
OC
Cancel· or an exit address equal to zero was specified,
and either there are no exits for this TCB, the most
recent exit is not owned by the caller, or the most
recent exit is not an ESTAE exit.
10
An unexpected error was encountered while
processing this request.
'
14
ESTAE was unable to obtain storage for an SCB.
System Action: IKJEFXSR returns to IEEVIPL with a return
code of zero.
Operator Response: None.
IKJ1461
mod NOT FOUND BY IKJEFXSR IN LPA.
Explanation: The specified module was not found in LPA.
System Action: Processing of IKJEFXSR continues normally.
Operator Response: Notify the system programmer.
IKJ1471
IKJEFXSR ABNORMAL TERMINATION, ABEND cde.
Explanation: A userid list, in an operator SEND command,
Explanation: IKJEFXSR terminated with an ABEND indicated by
contained an entry which was not a seven-character maximum
alphameric string.
System Action: Processing continues; the syntactically
unacceptable recipients specified in the insert are ignored. If
there are no other errors, the message will be sent to or
saved for valid reCipients.
Operator Response: Examine the text of the SEND command
for syntax errors. Issue another SEND command to route the
message to the intended recipi'ents who were ignored by the
original SEND command processing.
cde.
System Action: IKJEFXSR returns to IEEVIPL.
Operator Response: None.
IKJ1431
USERIDS AFTER 20TH IGNORED
Explanation: An operator SEND command was issued which
specified more than 20 valid userids. The first 20 userids will
be processed, but all others will be ignored.
System Action: Processing continues, but the message has not
been sent to or saved for userids after the 20th valid userid.
Operator Response: Issue another SEND command to route the
message to the intended recipients who were ignored by the
original SEND command processing.
IKJ1441
UNDEFINED USERID(S) userid userid ... userid
Explanation: An operator SEND command was issued which
required saving mail for a specific user; however, the specified
userids are not represented in the mail directory of
SYS1. BRODCAST.
System Action: Processing continues, but the message has not
been sent to or saved for the unauthorized users.
Operator Response: Report this message to the system
programmer.
Programmer Response: If the unauthorized user is represented
in the UADS (User Attribute Data Set), then the UADS and
broadcast data set should be synchronized; see SYNC
15-2
VS2 System Messages (VS2 Release 3.7)
IKJ4021
TCAM PROCEDURE DOES NOT SUPPORT TIME
SHARING
Explanation: The procedure used to start TCAM specifies a
message control program which will not support time sharing
or' a mixed-environment message control program which has
no time sharing terminals.
System Action: The request to modify TCAM to start time.
sharing is ignored.
Operator Response: To start time sharing, the current TCAM
procedure must be halted and a new one started which
supports time sharing. If such a procedure cannot be found,
notify the installation programmer.
IKJ4031
LINE GROUP FOR DO ddn NOT OPENED
Explanation: The IBM-supplied TSO-TCAM message control
program was unable to open the DCB for the line group data
set that specified ddn as its ddname.
System Action: Execution of the MCP continues with the
telecommunications lines defined in this line group unavailable
for use.
Operator Response: Check the JCL used to execute the MCP
to be sure that no desired DO statements are missing.
IKJ4041
TS START REJECTED - INSUFFICIENT COMMON
STORAGE AVAILABLE
Explanation: There was insufficient virtual storage available in
the common area to support time sharing.
System Action: The request to modify TCAM to start time
sharing is rejected.
Operator Response: The operator may wish to try his request
again later. Common storage usage may drop enough to
permit time sharing to be started. In any case, the installation
programmer should be informed of the problem.
Program Response: Determine if the heavy common storage
usage was due to some exceptional condition. If not, enlarge
the size of this area.
IKJ5511 NOT ENOUGH MAIN STORAGE TO
EXECUTE REFORMAT
REFORMAT USERID userid
Explanation: A GETMAIN request was unsuccessful.
System Action: For userid space failure, UADSREFM continues
processing any userids remaining in the UADS directory.
Otherwise, all UADSREFM processing terminates.
Operator Response: Rerun the job in a larger region.
IKJ5521
IKJ4051
TIME SHARING ENDED
Explanation: Time sharing support in TCAM has ended.
System Action: Time sharing is terminated.
Operator Response: None.
IKJ4071
INVALID TIOC PARAMETER - xxx
= yyy
- IGNORED
Explanation: The indicated parameter expression, is invalid on
a TIOC parameter record.
System Action: The invalid entry is ignored. If the intended
parameter value is not specified on any other entry, ~he
default value will be used.
Operator Response: The installation programmer should be
informed.
Program Response: The invalid entry should be inspected for
mis.spelling or conflict with other parameters and corrected
appropriately.
IKJ4081
MEMBER 'IKJPRMOO' NOT FOUND
Explanation: The default member name 'IKJPRMOO' could not
be fould on SYSl.PARMLIB.
System Action: Time sharing initialization processing continues
using defaults for time sharing system parameter values.
Operator Response: None.
IKJ4091
terminate.
System Action: A diagnostic dump is taken to the SYSl.DUMP
data set if this data set is available. Time sharing support is
then terminated.
Operator Response: Time sharing may be started again if
desired.
Program Response: Before calling IBM for programming
support, print the dump taken to SYSl.DUMP.
Problem Determination: Table I, items 2, 29.
IKJ4141
IKJ5531
USERIDS REFORMATTED
userid userid ... userid
Explanation: The specified modification has been accomplished
on the noted userid members.
System Action: Processing continues.
Operator Response: Enter the next command.
l
UNABLE TO EXECUTE REFORMAT +
SYSUADN RDJFCB FAILURE
SYSUADS RDJFCB FAILURE
NON IDENTIFIABLE BLOCKSIZE FOR IDENTICAL
SYSUADS /SYSUADN
SYSUADS BLOCKSIZE TOO SMALL
I
Explanation: An error occurred in allocation or in reading the
JFCB.
System Action: UADSREFM processing continues.
Programmer Response: Check the allocation and reallocation if
required. Rerun the job.
Problem Determination: Table I, item 30.
IKJ5541
jSYSUADN l
1SYSUADS f
DATA SET NOT USABLE+
CANNOT OPEN. DATA SET }
STOW I/O ERROR CODE rc
{ SYNAD ERROR synad info
UNABLE TO OPEN SYSl.PARMLIB
Explanation: The SYSl.PARMLIB data set either could not be
opened or could not be allocated.
System Action: Time sharing initialization processing continues
using defaults for time sharing system parameter values.
Operator Response: None.
Problem Determination: Table I, items 3, 25a, 29.
IKJ5501
A failure has occurred in a service function. A
code (nn) of 12 indicates an invalid parameter list was
supplied to the service routine. A code of nn represents an
•
invalid code with no assigned significance.
System Action: If the error is STAE, BPS, or ENQ on
SYSUADS, UADSREFM processing terminates. Otherwise,
processing for the current userid is terminated and UADSREFM
continues to process any userids remaining in the UADS
directory.
Programmer Response: Rerun the job.
Problem Determination: Table I, item 30.
Explanation:
SYSTEM ERROR - TIME SHARING TERMINATED
Explanation: A system error occurred, causing time sharing to
UTILITY SYSTEMERROR+
STAE
PUTLINE
ENQ
DEQ
ACCOUNT -READ
ERROR CODE nn
ACCOUNT-GETSPACE
ACCOUNT -WRITE
BACKSPACE
Explanation: A failure was encountered in a service function.
System Action: UADSREFM processing is terminated.
Operator Response: Rerun the job.
Problem Determination: Table I, item 30.
IKJ5551
UNABLE TO REFORMAT userid,
~ USERID IN USE
l
1BLOCKSIZE TOO SMALL f
Explanation: The specified member 'is currently in use or the
blocksize allocation is insufficient for the specified member.
System Action: Processing for the specified userid is
terminated. UADSREFM· continues to process any userids
remaining in the UADS directory.
Programmer Response: Attempt the reformat again after using
the ACCOUNT command functions to rebuild the specified
userid, individually.
~~:
,.
,j
Section 15: IKJ Messages - TSO
15-3
IKJ5561 USERID use rid NOT FOUND
Explanation: The service routines were unable to read the
specified name.
System Action: Processing for the specified userid is
terminated. UADSREFM continues to process any userids
remaining in the UADS directory.
Programmer Response: Cross-check for the correct name
(using the ACCOUNT -LIST or ACCOUNT -L1STIDS).
Problem Determination: Table I, items 30.
IKJ5571
UADSREFM ENDED DUE TO ERROR+
SYSTEM COMPLETION CODE cde
Explanation: An error resulting in an ABEND (cde) occurred
during UADSREFM member processing.
System Action: UADSREFM processing is terminated.
Operator Response: Rerun the job.
Problem Determination: Table I, item 29.
IKJ5581
UNABLE TO CLOSE
5SYSUADS ~
DATA SET
lSYSUADN)
Explanation: A failure occurred in the CLOSE function.
System Action: UADSREFM processing is terminated.
Operator Response: Rerun the job.
Problem Determination: Table I, item 30.
IKJ5701
SEND NOT SUPPORTED IN THIS SYSTEM
Explanation: A SEND command was issued; however, the time
sharing option was not included in the system at system
generation time. Therefore, the SEND command is not
operative.
System Action: The SEND command is rejected.
Operator Response: None.
IKJ5721
USER userid NOT LOGGED ON, MESSAGE
CANCELED
Explanation: In a SEND command which does not include the
LOGON parameter, a userid was specified which is not
currently logged on the time sharing system. The message
specified in the SEND command is not issued to the user with
the userid specified in the message text. The message is
issued to those users with userids which are logged on.
System Action: The message specified in the SEND command
is issued to the users, with userids specified in the SEND
command, who are currently logged on.
Operator Response: No response is required. If a message is
to be sent to users with userids which are not logged on, enter
the SEND command and include the LOGON parameter.
IKJ5731
SEND SYNTAX ERROR. COMMAND REJECTED
• The command contains embedded blanks.
• A delimiter is missing such as a comma after the message
text, an equal sign after the keyword 'USER', or a
parenthesis around the userid list.
• The command contains an unidentifiable keyword.
• Quotation marks around the message text are missing.
• The length of the message text is less than one character.
System Action: The SEND command is rejected.
Operator Response: Reenter the SEND command correctly.
IKJ5741
NO SPACE IN BROADCAST DATA SET FOR
S MAIL
~
1NOTICES)
Explanation: The portion of the Broadcast data set needed to
contain a SEND message record is full:
15-4
VS2 System Messages (VS2 Release 3.7)
1. MAIL -The SEND command specified 'USER' and 'LOGON',
but no free space is available in the user mail section of the
Broadcast data set to contain the SEND message.
2. NOTICES - The SEND command specified 'LOGON' and did
not specify 'USER', no free space is available in the
Broadcast notice section to contain the SEND message.
System Action: The SEND message is sent to all specified
users currently logged on. However, the message is not saved
in the Broadcast data set for those users not currently logged
on.
Operator Response: Case 1 is a temporary situation. Space will
be available in the mail section of the Broadcast data set as
soon as a user for whom a message is intended enters a
LOGON or L1STBC command. For case 2, it is necessary to
free a Broadcast message number by issuing a SEND
command with the 'DELETE' parameter specified.
IKJ5751
DATA SET SYS1.BRODCAST NOT USABLE
Explanation: A SEND command was issued but the Broadcast
data set could not be used for one of the following reasons:
1. The volume containing the SYS1.BRODCAST data set was
not mounted.
2. An input/output error occurred during SEND processing of
the SYS1.BRODCAST data set.
System Action: If 'USER' was specified in the SEND command,
the message is issued to the specified users currently logged
on to the time sharing system. Otherwise, processing in the
Broadcast data set is terminated at the point the error is
detected.
Operator Response: For case 1, make sure that the volume
containing the SYS1.BRODCAST data set is mounted. For case
2, reenter the SEND command.
Problem Determination: Table I, items 25a, 29.
IKJ5761
NO BROADCAST MESSAGE
Explanation: One of the following occurred when a SEND
command was issued:
• If the parameter msgno was specified, either there was no
Broadcast notice message for the particular message
number spe~ified, or the message number specified
exceeded the maximum value set at system generation time.
• If the LIST parameter was specified (without msgno) there
were no Broadcast notice messages in the Broadcast data·
set.
System Action: None.
Operator Response: None.
IKJ5781
BROADCAST MSGNO = nn
Explanation: A SEND command has been issued with the
'LOGON' para..meter specified. The SEND message text is
entered in the Broadcast data set with the message number
no.
System Action: A message is entered in the Broadcast data
set and is assigned message number nn.
Operator Response: None.
IKJ5791
CANNOT EXECUTE SEND
Explanation: The SEND command handling routines are unable
to perform their functions for one of the following reasons:
• There is an insufficient amount of storage available.
• An internal error has occurreQ in one of the SEND modules.
System Action: SEND processing is terminated at the point the
error is detected.
Operator Response: Reenter the SEND command.
Problem Determination: Table I, items 11, 29.
IKJ5801 MESSAGE TRUNCATED TO 115 CHARACTERS
Explanation: A SEND command specified message text that
was greater than the maximum of 115 characters allowed.
System Action: The message text is truncated to 115
characters.
Operator Response: None.
IKJ6001
TSOLOGON
ddn,
USER
11/0
OBTAIN
!
ERROR,DDNAME
OPEN
{userid
}, PROC
UNKNOWN
{ppp
}
UNKNOWN
Explanation: TSO LOGON was unsuccessful in performing one
of the indicated operations (I/O, OBTAIN, or OPEN). In the
message text, ddn refers to the DO statement defining the
data set being referenced when the error occurred. The
message text also includes the user identification (userid) of
the user being serviced when the error occurred and the
procedure name, ppp, which the user had selected unless they
are unknown to TSO LOGON at the time of the error.
System Action: The system disconnects the user from the TSO
subsystem after transmitting message IKJ564521 to the user's
terminal and invoking the TSO Dump facility to provide a dump
for error analysis.
Operator Response: Probable hardware error.
Problem Determination: Table I, items 2, 4, 7a, 29. Make sure
that a SYSTSDP DO statement was included in the time sharing
procedure. Execute the AMDPRDMP service aid for the dump
data set to obtain a formatted listing of the dump, and save
the output.
IKJ6011
TSOLOGON
1TERMINATED
PROCEEDING
!
ABEND cde,
ATTEMPTING RETRY
USER
/
use, rid
'}
{ UNKNOWN
PROC
{ppp
}
UNKNOWN
Explanation: Conditions leading to an abnormal termination
with a code of cde have arisen in a TSO LOGON module. In
the message text, use rid is the identification of the user being
serviced by TSO LOGON when abnormal termination occurred,
and ppp is the name of the procedure that the user requested.
If the userid or procedure name are not known, UNKNOWN
appears in the message text. Also in this message text is an
indication of whether LOGON can recover from the error via
RETRY, termination of the session is to occur, or the error was
not critical to user LOGON processing and LOGON will proceed
with this processing.
System Action: The system either terminates the TSO LOGON
function in which the abnormal termination occurred or
attempts to recover after transmitting message IKJ654521 to
the terminal on whose behalf TSO LOGON was operating. It
also provides a dump for error analysis and performs error
recording to the LOG data set.
Operator Response: Notify the system programmer of this
message.
Problem Determination: Table I, items 2, 13, 29.
IKJ6021
INCONSISTENT AUTHORIZATION DATA FOR userid
Explanation: A data or control field within the User Attribute
Data Set (UADS) for the user with the use rid specified in the
'message is incorrect. The authorization data cannot be used
for LOGON processing.
System Action: The system offers the terminal user the choice
of logging on with a different userid, or logging off.
Operator Response: For diagnostic purposes it is desirable to
freeze the UADS data for 'userid' until the cause of the
difficulty has been isolated. However, if rapid restoration of the
authorization data for 'userid' is necessary, it can be restored
by performing the following recovery operations:
• Use the DELETE subcommand of the ACCOUNT command
to purge the damaged data for 'userid' from the UADS.
• Use the ADD subcommand of the ACCOUNT command to
reenter valid authorization data.
Problem Determination: Table I, items 29. Execute the
AMASPZAP service aid to obtain a dump for the directory
blocks of the UADS and all members of UADS which contain
'userid' as the first characters of the member name. Execute
the LlSTIDR function of AMBLIST for SYSl.LlNKLIB and
SYSl.OMDLlB to obtain a list of all members with a PTF or
local fix. Have a listing available of any local programs or
procedures used to access or modify the UADS.
IKJ6031
TSOLOGON
TERMINATED
} INSTALLATION EXIT
{ ATTEMPTING RETRY
ABEND} cde
{ ERROR
Explanation: A routine provided by the installation's systems
programmer to augment or modify IBM's standard LOGON
processing has failed. If the failure took the form of a system
abnormal termination, the word ABEND appears in the
message text, and code cde is the system completion code
and an indication as to whether LOGON is attempting retry or
terminating because of the ABEND. Otherwise, the word
ERROR appears in the message text, code cde is the error
code developed by TSO LOGON upon analysis of the
parameters returned by an exit routine and LOGON will always
terminate. The error codes and their meaning are as follows:
CODE EXPLANATION
004
The address of the control switch buffer passed to the
preprompt EXIT was altered during exit execution.
008
The control switches buffer length passed to the
preprompt EXIT was altered during exit execution.
012
The length of the control switches returned by the
preprompt EXIT was longer than the buffer or less
than zero.
016
The address of the command buffer passed to the
preprompt EXIT was altered during exit execution.
020
The command buffer length passed to the Pre-Prompt
Exit was altered during exit execution.
024
The length of the command returned by the preprompt
EXIT was longer than the buffer or less than zero.
028
The address of the userid buffer passed to the
preprompt EXIT was altered during exit execution.
032
The userid buffer length passed to the Pre-Prompt
Exit was altered during exit execution.
036
The length of the use rid returned by the Pre-Prompt
Exit was longer than the buffer or less than zero.
040
The preprompt EXIT returned a zero length userid for
LOGON processor use.
044
The preprompt EXIT returned an unauthorized userid
for LOGON processor use.
048
The address of the password buffer passed to the
preprompt EXIT was altered during exit execution.
052
The password buffer length passed to the Pre-Prompt
Exit was altered during exit execution.
056
The length of the password returned by the pre prompt
EXIT was longer than the buffer or less than zero.
060
The preprompt EXIT returned an unauthorized
password for LOGON processor use.
064
The address of the account buffer passed to the
preprompt EXIT was altered during exit execution.
Section 15: IKJ Messages - TSO
15-5
•
VS2.03.813
068
072
076
080
084
088
092
096
100
104
108
112
116
120
124
128
132
136
140
144
148
152
156
160
164
168
172
176
180
184
188
15-6
The account buffer length apssed to the Pre-Prompt
Exit was altered during exit execution.
The length of the account returned by the Pre-Prompt
Exit was longer than the buffer or less than zero.
The preprompt EXIT returned an unauthorized account
for LOGON processor use.
The address of the procedure name buffer passed to
the preprompt EXIT was altered during exit execution.
The procedure name buffer length passed to the
preprompt EXIT was altered during exit execution.
The length of the procedure name returned by the
preprompt EXIT was longer than the buffer or less
than zero.
The preprompt EXIT returned a zero length name for
LOGON processor use.
The preprompt EXIT returned an unauthorized
procedure name for LOGON processor use.
The preprompt EXIT returned a region size outside the
bounds supported by TSO for LOGON processor use.
The preprompt EXIT returned an unauthorized region
size for LOGON processor use.
The address of the JCL buffer passed to the
pre prompt EXIT was altered during exit execution.
The JCL buffer length passed to the preprompt EXIT
was altered during exit execution.
The length of the JCL returned by the preprompt EXIT
was longer than the buffer or less than zero.
The preprompt EXIT returned less than two JCL card
images for LOGON processor use.
The preprompt EXIT returned a partial JCL card image
for LOGON processor use.
The address of the PSCB accounting data buffer
passed to the preprompt EXIT was altered during exit
execution.
The PSCB accounting data buffer length passed to the
preprompt EXIT was altered during exit execution.
The length of the PSCB accounting data returned by
the preprompt EXIT was longer than the buffer or less
than zero.
The address of the First Attribute buffer passed to the
preprompt EXIT was altered during exit execution.
The First Attribute. buffer length passed to the
preprompt EXIT was altered during exit execution.
The length of the First Attribute returned by the
pre prompt EXIT was longer than the buffer or less
than zero.
The address of the Second Attribute buffer passed to
the preprompt EXIT was altered during exit execution.
The Second Attribute buffer length passed to the
preprompt EXIT was altered during exit execution.
The length of the Second Attribute returned by the
preprompt EXIT was longer than the buffer or less
than zero.
The address of the Generic Group buffer passed to
the preprompt EXIT was altered during exit execution.
The Generic Group buffer length passed to the
preprompt EXIT was altered during exit execution.
The length of the Generic Group returned by the
preprompt EXIT was longer than the buffer or less
than zero.
The address of the UPT buffer passed to the
preprompt EXIT was altered during exit execution.
The UPT buffer length passed to the preprompt EXIT
was altered during exit execution.
The length of the UPT returned by the Pre-Prompt
Exit was longer than the buffer or less than zero.
The address of the ECT buffer passed to the
preprompt EXIT was altered during exit execution.
VS2 System Messages (VS2.03.813)
192
The ECT buffer length passed to the preprompt EXIT
was altered during exit execution.
196
The length of the ECT returned by the preprompt EXIT
was longer than the buffer or less than zero.
200
The address of the DEST userid buffer passed to the
preprompt EXIT was altered during exit execution.
204
The DEST userid buffer length passed to the
preprompt EXIT was altered during EXIT execution.
208
The length of the DEST userid returned by the
preprompt EXIT was longer than the buffer or less
than zero.
212
The pre prompt EXIT returned a zero length DEST
use rid for LOGON processor use.
216
The preprompt EXIT returned a DEST userid that was
not defined to the subsystem.
220
The preprompt EXIT returned a performance group
value which was not between 1 and 255 inclusive.
224
The preprompt EXIT returned an unauthorized
performance group value for LOGON processor use.
228
The pre prompt EXIT returned a performance group
value which was not defined to the system.
232
The subsystem encountered an error while attempting
to validate the DEST userid returned by the preprompt
EXIT.
236
The subsystem interface encountered an error while
attempting to validate the DEST userid returned by the
preprompt EXIT.
250
The address of the new password buffer passed to the
pre-prompt exit was altered during exit execution.
254
The new password buffer length passed to the
pre-prompt exit was altered during execution.
258
The length of the new password buffer returned by the
pre-prompt exit was longer than the buffer or less
than zero.
262
The pre-prompt exit returned an unauthorized new
password for logon processor use.
266
The address of the group identification buffer passed
to the pre-prompt exit was altered during exit
execution.
270
The group identification buffer length passed to the
pre-prompt exit was altered during exit execution.
274
The length of the group identification buffer returned
by the pre-prompt exit was longer than the buffer or
less than zero.
278
The pre-prompt exit returned an unauthorized group
identification for logon processor use.
System Action: The system issues message IKJ564521 to the
terminal of the user whose LOGON failed. A dump is taken for
error analysis and error recording is taken to the LOG data
set. The message text indicates whether LOGON will retry or
terminate.
Operator Response: Notify the system programmer of this
message.
Problem Determination: Table I, items 2, 13, 29.
IKJ6051
TSOLOGON TERMINATED. TO MANY
ATTEMPTS.
USER
{ userid
}
UNKNOWN
Explanation: TSO LOGON denied a user with the identification
userid access to the TSO subsystem because the user
exceeded the limit, specified at system generation time, of
attempts to enter a valid set of LOGON operands.
System Action: The system transmits message IKJ564281 to
the terminal of the user, and disconnects the terminal from the
TSO subsystem.
Operator Response: None required. However, if this situation
recurs frequently, inform your installation manager since some
individual may be attempting to obtain unauthorized access to
the TSO subsystem.
IKJ6061
TSOLOGON REJECTED. USERID, use rid, IN USE
Explanation: TSO LOGON denied a LOGON request of a user
for one of two reasons:
• Another user was currently logged on under the same
userid.
• A member of the installation management staff was using
the TSO ACCOUNT command to alter the authorization of
the user to utilize the TSO subsystem.
System Action: The system transmits message IKJ564251 to
the terminal of the user who was unable to log on.
Operator Response: None required. If your installation requires
that each individual using the TSO subsystem have his own
unique use rid, then the userid of the individual involved may
be in use by an unauthorized individual. If there is any reason
to suspect that this is the case, make sure that the installation
manager is informed of the incident.
I
1Ii\
)
Section 15: IKJ Messages· TSO
15-6.1
15-6.2
VS2 System Messages (VS2.03.813)
IKJ6081
TSOLOGON TERMINATED.
j srname tERROR
1mac 5
rC.USER ! userid
PROC
jppp
l
1UNKNOWN 5
1UNKNOWN 5
Explanation: The TSO service routine (srname) or the macro
instruction (mac) returned the abnormal return code rc, which
indicates that a situation had arisen from which TSO LOGON
could not recover. The use rid of the user being serviced by
TSO LOGON when the incident occurred and the name of the
procedure requested appear in the message text.
System Action: The system transmits message IKJ564541 to
the terminal for which TSO LOGON was operating. It then
disconnects the terminal from the TSO subsystem.
Operator Response: None.
Problem Determination: Table I, items 2, 4, 7a, 29. Make sure
that a SYSTSDP DO statement was included in the time sharing
procedure. Execute the AMDPRDMP service aid for the dump
t
data set to obtain a formatted listing of the dump, and save
the output.
IKJ6091 TSOLOGON TERMINATED REQUIRED DDNAMES,
MISSING: ddn ddn ... ddn
Explanation: The ddnames specified in the message are
required for LOGON processing. The following list of ddnames
is currently required:
SYSUADS - This ddname describes the user attribute data
set.
SYSLBC
- This ddname is used for access to the
broadcast data set.
System Action: The system issues message IKJ564521 to the
terminal for which TSOLOGON was operating. It then
disconnects the terminal from the TSO subsystem.
Problem Determination: Table I, items 1, 2, 4, 29.
•
Section 15: IKJ Messages - TSO
15-7
16-8
VS2 System Messages (VS2 Release 3.7)
TSO Tenninal Messages (IKJxxyyyn)
This section describes TSO messages directed to a terminal
user. These messages are self-documenting; therefore
message identifiers and message text are not listed for every
message.
Component Name
IKJ
Program Producing Message
Time Sharing Option.
Audience and Where Produced
For terminal user: at the terminal.
Message Format
IKJxxyyyn
xx
System module prefix (in decimal).
yyy
Message serial number identifying the program that issued the message.
n
Type code:
Action. The terminal user must perform the action specified in the message text.
A
I
Information; no action is required.
Comments
None.
Associated Publications
OS!VS2 TSO Terminal Message Directory, SY28-0654
Problem Determination
Refer to Tables I and" at the back of this publication for problem determination instructions.
Section 15: IKJ Messages· TSO
•
15-9
Prefix &
Serial No.
(xxyyy)
15-10
Command Processor or Problem Program
4
\,~
52300-52599
EDIT Command Processor
52600-52699
COpy Command Processor
52700-52799
MERGE Command Processor
52800-52899
LIST Command Processor
52900-52999
FORMAT Command Processor
54000-54999
Terminal I/O Controller
55000-55049
OPERATOR Command Processor
55050-55099
SEND Command Processor
56000-56049
CALL Command Processor
56050-56099
RUN Command Processor
56100-56149
ALLOCATE Command Processor
56150-56169
FREE Command Processor
56170-56219
CANCEL/STATUS Command Processor
56220-56249
DAIRFAIL Service Routine
56250-56289
SUBMIT Command Processor
56290-56299
VSAMFAIL Service Routine
56300-56349
OUTPUT Command Processor
56400-56499
LOGON/LOGOFF Command Processor
56500-56549
EXEC/WHEN/READ Command Processor
56550-56599
ACCOUNT Command Processor
56600-56649
Terminal Monitor Program
56650-56659
TIME Command Processor
56660-56669
ATTN Routines
56670-56679
PROFILE Command Processor
56700-56749
PARSE Service Routine
56750-56769
GETLINE/PUTLINE/PUTGET
56800-56849
HELP END Command Processors
56850-56900
DAIRFAIL Service Routine
56950-56959
LlSTBC Command Processor
57000-57099
TEST Command Processor
58000-58099
DELETE Command Processor
58100-58199
PROTECT Command Processor
58200-58299
RENAME Command Processor
58300-58399
LlSTALC Command Processor
58400-58499
LlSTCAT Command Processor
58500-58599
LlSTDS Command Processor
68000-68099
COBOL Command Processor
74000-74099
ASM Command Processor
76000-76099
LlNK/LOADGO Command Processor
78000-78099
FORT Command Processor
VS2 System Messages (VS2 Release 3.7)
VS2.03.807
IKJ562201 type name NOT operation, TOO MANY DATA
SETS +
IKJ562301 type name NOT operation, MEMBER OF
CONCATENATION
MAXIMUM NUMBER OF DATA SET ALLOCATIONS ALLOWED BY
YOUR LOGON PROCEDURE HAS BEEN REACHED, YOU SHOULD
FREE UNUSED DATA SETS
Dynamic allocation return code 045C.
The type, name, and operation inserts indicate. the requested
dynamic allocation function. An example is DATA SET name
NOT ALLOCATED.
Dynamic allocation return codes 0238 or 043C.
IKJ562211 type name NOT operation, VOLUME NOT
AVAILABLE+
VOLUME yolser Is ALLOCATED TO ANOTHER JOB OR USER,
TRY LATER
Dynamic allocation return .code 02220. If the request was for a
Mass Storage System (MSS) Yolume, the operator console will
receive message IEF7101, which contains the MSS failure
reason code.
VOLUME yolser NECESSARY TO SATISFY REQUESt NOT ON
SYSTEM AND CANNOT BE MOUNTED
Dynamic allocation return code 0218 or 0248. If the request
was for a Mass Storage System (MSS) volume the operator
console will receive message IEF7101, which contains the MSS
failure reason code.
VOLUME yolser CURRENTLY MOUNTED ON AN INELIGIBLE
DEVICE
Dynamic allocation return code 022C.
IKJ562241 INVALID SYSOUT CLASS
Dynamic allocation return code 032C.
IKJ562311 type name NOT operation, SYSTEM OR
INSTALLATION ERROR+
UNKNOWN 'routine' CODE -NOTIFY YOUR INSTALLATION
MANAGER OF ERROR CODE xxx
'routine' insert is DYNAMIC ALLOCATION, CATALOG, DADSM,
LOCATE, OBTAIN, or SCRATCH.
OBTAIN error codes 6710 and 6714 or DADSM error codes
4710 and 4730. (See note 3.)
Dynamic allocation return codes 1714, 171C, and 1720. (See
note 3.)
Dynamic allocation return code 77xx. xx is the scratch error
code. (See not!3 3.)
IKJEFF18 cannot identify error code. (See notes 2 and 3).
UNKNOWN 'routine' CODE -NOTIFY YOUR INSTALLATION
MANAGER OF RETURN CODE xxx
'routine" insert is DAIR or DYNAMIC ALLOCATION.
IKJEFF18 cannot identify return code. (See notes 1 and 2).
OBTAIN or DADSM I/O ERROR yolser
OBTAIN or DADSM error codes 670C or 470C. (See note 3).
TEXT UNIT number CONTAINS INVALID PARAMETER
Dynamic allocation return code 035C.
TEXT UNIT number CONTAINS INVALID KEY
Dynamic allocation retur.Q code 0360.
REQUEST BLOCK FORMAT INVALID
Dynamic allocation return code 036C.
TEXT UNIT'number CONTAINS INVALID NUMBER
IKJ562251 type ALREADY IN USE, TRY LATER+
Dynamic allocation return code 0374.
DATA SET IS ALLOCATED TO ANOTHER JOB OR USER
TEXT UNIT number CONTAINS DUPLICATE KEYS
Dynamic allocation return code 0210.
Dynamic allocation return code 0378.
TEXT UNIT number CONTAINS INVALID LENGTH
IKJ562261 INVALID DATA SET NAME, name EXCEEDS 44
CHARACTERS
Dynamic allocation return code 0334.
Dynamic allocation return code 037C.
ESTAE ENVIRONMENT COULD NOT BE ESTABLISHED
Dynamic allocation return code 047C.
IKJ562281 DATA SET dsname NOT IN CATALOG
LOCATE I/O ERROR
For DISP or 5710.
CATALOG SPACE EXHAUSTED ON CONTROL VOLUME yolser
OLD. Dynamic allocation error codes 1708, 5708,
IKJ562291 type name NOT operation, DADSM ERROR+
DUPLICATE DATA SET NAME ON VOLUME 'yolser'
Dynamic allocation return code 4704 and DADSM return code
04.
VOLUME yolser VTOC IS FULL
Dynamic allocation return code 4708 and DADSM return code
08.
RECORD LENGTH SPECIFIED IS GREATER THAN yolser TRACK
CAPACITY
Dynamic allocation return code 4718 and DADSM return code
18.
Dynamic allocation return code 1718.
Dynamic allocation return code 5714.
CATALOG I/O ERROR yolser
Dynamic allocation return code 5718 or 571C.
Note: Descriptions for 1) DAIR return codes are in OS/VS2 TSO Guide to Writing a
Terminal Monitor Program or a Command Processor,
GC28-0648.
2) Dynamic allocation return codes are in Appendix A OS/VS2
System Programming Library: Job Management, GC28-0627.
3) Catalog (ATLAS, CATALOG, LOCATE, and RDJFCB macros)
and DADSM (OBTAIN, RENAME, and SCRATCH macros) are
in OS/VS2 System Programming Library: Data Management,
GC28-3830.
type name NOT operation, CATALOG ERROR+
DATA SET NAME CONFLICTS WITH EXISTING DATA SET NAME.
RESPECIFY WITH A NEW UNIT NAME OR CHANGE; REQUESTED
LAST QUALIFIER.
For DISP - NEW. Dynamic allocation return codes 1708,
5708 or 5710.
Section 15: IKJ Messages· T80
15-11
•
VS2.03.807
IKJ562321 type name NOT ON VOLUME AS INDICATED IN THE
CATALOG +
PLEASE DELETE THE CATALOG ENTRY (USE DELETE
COMMAND WITH NOSCRATCH KEYWORD) AND RECREATE THE
DATA SET IF NECESSARY
Dynamic allocation return code 6708. The catalog information
is incorrect for one of the following reasons:
• Only a catalog entry was created. This could have been
done with a utility or through an incomplete creation of the
data set.
• The DELETE command had incomplete execution.
• The data set was scratched by a cleanup routine but never
uncataloged.
• The volume was restored to a level without the data set and
the catalog is not on the same volume.
IKJ562341 ATTR-LIST -NAME name NOT FOUND
Dynamic allocation return code 0454.
3) Catalog (ATLAS, CATALOG, LOCATE, and RDJFCB macros)
and DADSM (OBTAIN, RENAME, and SCRATCH macros) are
in OS/VS2 System Programming Library: Data Management,
GC28-3830.
.
IKJ562481 type NOT operation, REQUESTED AS NEW BUT
CURRENTLY ALLOCATED
Dynamic allocation return code 0448.
IKJ562491 type NOT operation, CURRENTLY ALLOCATED WITH
DISPOSITION OF DELETE
Dynamic allocation return code 044C.
IKJ568501 type operation, OVERRIDING DISPOSITION IGNORED
Dynamic allocation return code 0008.
IKJ568511 type operation REQUESTED
CATALOG/UN CATALOG/DELETE DISPOSTION
UNSUCCESSFUL
IKJ562351 MEMBER name SPECIFIED BUT dsname NOT A
PARTITIONED DATA SET
Dynamic allocation return codes 0021-0029, 0031-0039.
Dynamic. alloction return code 0330.
IKJ568521 type NOT operation, FILENAME NOT SPECIFIED
IKJ562361 FILE STEPLIB/JOBLIB/STEPCAT / JOBCAT INVALID,
FILENAME RESTRICTED
Dynamic allocation return code 0364.
IKJ562391 type NOT operation, name CURRENTLY ALLOCATED
AS A DUMMY+
FREE FILE name AND RE- ENTER COMMAND
Dynamic allocation return code 0304.
IKJ568531 type NOT operation, DECONCATENATION WOULD
RESULT IN DUPLICATE FILENAMES
Dynamic allocation return codes 0314 or 0424.
IKJ568541 INVALID FILENAME
Dynamic allocation return code 0318.
Dynamic allocation return code 410. DAIR return code 14.
IKJ568551 INVALID MEMBERNAME
IKJ562411 type NOT operatlon+
Dynamic allocation return code 031C.
DATA SET IS ALLOCATED TO ANOTHER JOB OR USER
Dynamic allocation return code 020C.
IKJ568561 INVALID DATA SET NAME
NO UNIT AVAILABLE
Dynamic allocation return code 0320.
Dynamic allocation return code 0214.
INVALID UNIT IN USER ATTRIBUTE DATA SET
Dynamic allocation return code 021C.
IKJ562441 type NOT operation, DIRECTORY LARGER THAN
PRIMARY QUANTITY
Dynamic allocation return code 4738 - DADSM code 38.
IKJ562451 type NAME NOT operation, NOT ENOUGH SPACE
ON VOLUME+
IKJ568571 INVALID SYSOUT PROGRAM NAME
Dynamic allocation return code 0324.
IKJ568581 INVALID SYSOUT FORM NUMBER
Dynamic allocation return code 0328.
IKJ568591 INVALID DISPOSITION
Dynamic allocation return code 0338.
USE DELETE COMMAND TO DELETE UNUSED DATA SETS
IKJ568601 type NOT UNALLOCATED, DELETE DISPOSITION
INVALID FOR DATA SET ALLOCATED AS SHARED
Dynamic allocation return code 4714 - DADSM code 14.
Dynamic allocation return code 0358.
IKJ562461 type name NOT ALLOCATED, FILE IN USE
IKJ568611 type NOT operation, DATA SET IS OPEN
Dynamic allocation return code 0410.
Dynamic allocation return code 0420.
IKJ562471 type NOT operation, IS NOT ALLOCATED
IKJ568621 type NOT operation, REQUEST DENIED BY
INSTALLATION EXIT
Dynamic allocation return codes 0438 and 0440. For all
requests except concatenation.
Note: Descriptions for 1) DAIR return codes are in OS/VS2 TSO Guide to Writing a
Terminal Monitor Program or a Command Processor,
GC28-0648.
2) Dynamic allocation return codes are in OS/VS2 System
Programming Library: Job Management, GC28-0627.
15-12
VS2 System Messages (VS2.03.807)
DAIR return code 52 (dec).
IKJ568631 type NOT operation, NOT ENOUGH STORAGE TO
EXECUTE COMMAND
Dynamic allocation return codes 0204 or 172C.
VS2.03.807
IKJ568641 type NOT operation, USER NOT AUTHORIZED FOR
FUNCTION SPECIFIED
IKJ568781 type NOT operation, REQUIRED PARAMETER
MISSING
Dynamic allocation return code 0368 or 0470.
Dynamic allocation return code 0388.
IKJ568651 FILE name NOT operation, FILE NAME CURRENTLY
ASSOCIATED WITH ANON-EXPLICIT ALLOCATION+
IKJ568791 type NOT operation, REFERENCED DATA SET NAME
IS A GDG GROUP NAME
FILE filename MUST BE FREED BEFORE USING EXPLICITLY
Dynamic allocation return code 0458.
Dynamic allocation return code 0434.
IKJ568801 type NOT operatlon+
IKJ568661 type NOT operation, CONCURRENT ALLOCATIONS
WOULD BE EXECUTED
NUMBER OF DEVICES REQUIRED CURRENTLY UNAVAILABLE
Dynamic allocation return code 0450.
VOLUME OR DEVICE IS CURRENTLY UNAVAILABLE FOR
SYSTEM USE
IKJ568671 type NOT operation, RELATIVE ENTRY NUMBER
SPECIFIED NOT FOUND
Dynamic allocation return coc:ie 0444.
IKJ568681 type NOT CONCATENATED, A FILENAME 'SPECIFIED
WAS NO.1 FOUND
Dynamic allocation return code 0308 or 0438.
IKJ568691 type NOT operation, A FILE NAME HAS BEEN
SPECIFIED MORE THAN ONCE+
FILENAMES SPECIFIED FOR CONCATENATION MUST BE
UNIQUE
Dynamic allocation return code 038C.
Dynamic allocation return code 0224.
Dynamic allocation return code 0228.
SPECIFIED DEVICE IN USE WITH A VOLUME THAT CAN NOT BE
DISMOUNTED
Dynamic allocation return code 0230.
A VOLUME SPECIFIED IS ALREADY MOUNTED ON ANOTHER
DEVICE
Dynamic allocation return code 0234.
Dynamic allocation return code 023C.
INSUFFICIENT NUMBER OF VOLUMES HAVE BEEN SPECIFIED
Dynamic allocation return code 0398.
UNIT AND VOLUME SPECIFIED ARE NOT SAME DEVICE TYPE
Dynamic allocation return code 039C.
GDG PATTERN DSCB COULD NOT BE FOUND
IKJ568701 type NOT operation, RELATIVE GENERATION
NUMBER EXCEEDS 35 CHARACTERS
~\
r
Dynamic allocation return code 0390.
Dynamic allocation return code 048C.
GDG PATTERN DSCB NOT MOUNTED
Dynamic allocation return code 0488.
(
IKJ568711 type NOT operation, RELATIVE GENERATION
NUMBER INCOMPATIBLE FOR .SPECIFIED STATUS
Dynamic allocation return code 0394.
IKJ568721 type NOT operation, DATA SET OR MEMBER IS NOT
ALLOCATED TO THE FILENAME SPECIFIED
Dynamic allocation return code 0460.
REQUIRED CATALOG VOLUME CURRENTLY NOT MOUNTED
Dynamic allocation return code 5704 (CATALOG return code 4
from DAIR).
IKJ568811 type NOT operation, DEVICE IS A CONSOLE+
DYNAMIC ALLOCATION OF A CONSOLE NOT SUPPORTED
Dynamic allocation return code 0240.
IKJ568731 type NOT operation, DATA SET NAME SPECIFIED IS
A PRIVATE CATALOG
IKJ568821 type NOT operation, TOO MANY VOLUMES+
Dynamic allocation return code 0464.
NUMBER OF VOLUMES SPECIFIED EXCEEDS LIMIT
Dynamic allocation return code 0480.
IKJ568741 type NOT operation, AN ERROR OCCURRED
ALLOCATING OR OPENING A PRIVATE CATALOG
Dynamic allocation return code 0468.
IKJ568831 type NOT operation, REQUEST CANCELED BY
OPERATOR
Dynamic allocation return code 0484.
IKJ568751 type NOT operation, DESTINATION UNDEFINED TO
SUBSYSTEM
Dynamic allocation return code 046C.
IKJ568841 type NOT operation, SUBSYSTEM UNABLE TO
SERVICE YOUR REQUEST
Dynamic allocation return code 0478.
IKJ568761 type NOT operation, MUTUALLY EXCLUSIVE
PARAMETERS SPECIFIED
Dynamic allocation return code 0380.
IKJ568771 type NOT operation, MUTUALLY INCLUSIVE
PARAMETER MISSING
Dynamic allocation return code 0384.
IKJ568851 type name NOT operation, MSS VOLUME NOT
ACCESSIBLE FROM UNIT +
IF YOU DID NOT SPECIFY UNIT NAME CALi.. YOUR SYSTEM
PROGRAMMER
Dynamic allocation return code 0498. Also, the operator
console will receive message IEF7101, which contains the Mass
Storage System (MSS) failure reason code.
Section 15: IKJ Messages - TSO
15-13
I
VS2.03.807
IKJ568861 type name NOT operation, MSS VOLUME DOES NOT
EXIST +
IF YOU DID NOT SPECIFY VOLUME NAME volume CALL YOUR
SYSTEM PROGRAMMER
Dynamic allocation return code049C. See the OS/VS Message
Library: Mass Storage System Messages publication for a detailed
description of Mas,s Storage System (MSS) reason code 7.
IKJ568871 type name NOT operation, MSVGP DOES NOT
EXIST +
IF YOU DID NOT SPECIFY MSVGP CALL YOUR SYSTEM
PROGRAMMER
Dynamic allocation return code 04AO. See the OS/VS Message
Library: Mass Storage System Messages publication for a detailed
15·14
VS2 System Messages (VS2.03.807)
explanation of Mass Storage System (MSS) reason code
X'207'.
IKJ568881 type name NOT operation, YOU ARE NOT
AUTHORIZED TO DEFINE THIS DATA SET TO
RACF+
NOTIFY YOUR INSTALLATION MANAGER
Dynamic allocation return code 47AC.
IKJ568891 type name NOT operation, YOUR RACF DATA SET
DEFINITION ALREADY EXISTS+
YOU CAN DELETE OR RENAME YOUR EXISTING DATA SET
Dynamic allocation return code 47 AS.
Section 16: PL/I Syntax Checker Messages (IKM)
Component Name
IKM
Program Producing Message
PL/I syntax checker.
Audience and Where Produced
For remote operator and programmer: terminal.
Message Format
IKMnnn 1111111 text
nnn
Message serial number.
11111111
Data set line number of the line in which the error was detected.
Leading zeroes and blanks are suppressed.
text
Message text.
Comments
Central operator may request that messages appear on his console.
Associated Publications
OS/VS2 TSO Terminal User's Guide, GC28-0645.
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IKM001
11111111 UNMATCHED STRING QUOTES IN THIS
STATEMENT
Explanation: The quotation mark at the end of a character or
bit string is missing. No more checking of the statement is
performed.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM002
11111111 UNMATCHED COMMENT BRACKETS IN
THIS STATEMENT
Explanation: The character pair
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM005
11111111 PREFIX NOT PERMITTED BEFORE xxx
Explanation: A condition prefix to an ELSE clause, or an
ENTRY or DECLARE statement, is not permitted.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I; items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM006
11111111 CHECK/NOCHECK PREFIX NOT
PERMITTED BEFORE THIS STMNT
marking the end of a
comment is missing. No more checking of the statement is
performed.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
Explanation: The prefixes CHECK and NOCHECK may precede
only a PROC or BEGIN statement.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM003
IKM007
OC< /
11111111 STATEMENT NOT RECOGNIZED
'11111111 P~EFIX OPTION FOLLOWS LABEL
Explanation: A statement (including prefixes) does not start
Explanation: A condition prefix follows a label prefix. This is
with an identifier, semicolon, decimal integer, or left
parenthesis; or, a statement (excluding prefixes) starts with a
non keyword identifier but does not contain an equal sign or
does not have an equal number of left and right paren,theses
on the left of the equal sign.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
not permitted under the rules of PL/1. A condition prefix must
always precede any label prefix.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM004
11111111 LABEL MISSING FROM xxx STATEMENT
Explanation: The label that should prefix an ENTRY,
PROCEDURE, or FORMAT statement is missing.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
IKM008
11111111 ILLEGAL STATEMENT FOLLOWS xxx
= ON: An ·on-unit consisting of an IF, ON,
DO, RETURN, PROCEDURE, DECLARE, END, or FORMAT
statement, or an ELSE clause, is not permitted.
xxx = IF or ELSE: A unit-lor unit-2 branch of an IF
statement consisting of an ON, DO, PROCEDURE, ENTRY,
DECLARE, END, or FORMAT statement, or an ELSE clause, is
not permitted. The illegal statement is not checked further.
Programmer Response: Probable user error. Correct any
Explanation: xxx
Section 16: IKM Messages - PL/I Syntax Checker
16-1
•
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I· statement as part of a valid PL/I program.
IKM009
11111111 INVALID LABEL BEGNG xxx
Explanation: A label is not an (conditionally subscripted)
identifier.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM010
11111111 INVALID PREFIX OPTION xxx
Explanation: A condition prefix contains an invalid condition
name. The checking continues after the next colon.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
11111111 LABEL NOT PERMITTED BEFORE xxx
IKM011
Explanation:
xxx
ON:
the on-unit in an ON statement may not have a
label prefix.
ELSE: a label to an ELSE clause must not precede the
xxx
word ELSE.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM012
11111111 INCOMPLETE IF STATEMENT, THEN NOT
FOUND WHEN EXPECTED
Explanation: In an IF statement, the keyword THEN, or the
entire THEN clause, is missing. The checking of the statement
is terminated.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
.
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of ,a valid PL/I program.
IKM013
11111111 ERROR IN xxx STATEMENT BEGNG yyy
Explanation:
xxx == ALLOCATE, FREE, DECLARE, OPEN, CALL, DO, GET,
or PUT statements.· An invalid symbol may be
contained in one of these statements.
xxx
BEGIN. The BEGIN statement is incorrectly written
(may have the option ORDER or REORDER in PL/I
Version 5).
'
xxx - THIS. Error in an unclassified statement. Checking of
the statement is terminated.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
16-2
VS2 System Messages (VS2 Release 3.7)
IKM014
11111111 INVALID CHAR xxx PRECEDING yyy
Explanation: The character is not a PL/I character. Checking
of this statement is terminated.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13,29. Compile your
PL/I statement as part of a valid PL/I program.
IKM015
11111111 INVALID CHAR IN BIT STRING BEGNG
xxx
Explanation: A bit string contains a character other than 0 or
1.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
ch~cker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM016
11111111 xxx MISSING AFTER yyy'
Explanation: A delimiter (comma, colon, or right parenthesis)
or an identifier is missing.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM017
11111111 MISSING EQUAL SIGN IN DO
SPECIFICATION
Explanation: A Type 3 DO statement or repetitive
specification must have the following general form: DO variable
- expression [ ... ]; . This error terminates the checking of the
DO specification.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker resean it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I stat~ment as part of a valid PL/I program.
IKM018
11111111 SURPLUS COMMA AFTER xxx
Explanation: A comma should not separate the options in a
GET, PUT, or DECLARE (ENVIRONMENT) statement.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKMO 19
11111111 A LETTER IMMEDIATELY FOLLOWS
CONSTANT BEGNG xxx
Explanation: A constant may only be followed by one of the
following: any of several special characters, e.g., a blank or
semicolon; an arithmetic operator, a comparison operator, or a
bit-string operator. This could not be internally translated so
no further checking of the statement is performed.
Programmer Response: Probable user error. Correct any
errors in your PLII source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM020
11111111 INVALID PREFIX OPERATOR xxx
PRECEDING yyy
Explanation: An expression begins with an operator other
... ,+, - or (or an operand other than an identifier, a
than
string-;Or a constant.
Programmer Response: Probable 'user error. Correct any
errors in your PL/lsource statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM026
Explanation: The exponent in a floating point constant
contains a decimal point.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM027
IKM021
11111111 CONSTANT BEGNG xxx IS TOO LONG
Explanation: A binary fixed point or integer constant has more
than 31 digits, or a decimal fixed point or integer constant has
more than 15 digits.
A binary floating point constant has more than 53 digits in the
mantissa part, or a decimal floating point constant has more
than 16 digits in the mantissa part.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM022
)
11111111 CONSTANT BEGNG xxx EXCEEDS
MAXIMUM VALUE
Explanation: A floating point constant exceeds the value
7.205,759,403,792,793E75, which is the highest value
allowed.
Programmer Response: Probable user error. Correct any
errors in your, PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM023
11111111 SOLITARY DECIMAL POINT FOUND IN
OPERAND POSITION
Explanation: A period appears invalidly in an expression in an
operand position.
Programmer Response: Probable user error. Correct any
errors in your PL/I'source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM024
11111111 EXPONENT MISSING IN CONSTANT
BEGNG xxx
Explanation: The letter E in a floating point constant is
followed by some character other than a digit, a plus or misus
sign, or a decimal point.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM025
11111111 EXPONENT TOO LONG IN CONSTANT
BEGNG xxx
Explanation: A binary floating point constant has more than ,3
digits in the exponent part, or a decimal floating point constant
has more than 2 digits in the exponent part.
Programmer Response: Probable user error. Correct any
errors in your PI/I source statement and let the syntax checker
rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
11111111 DECIMAL POINT IN EXPONENT OF
CONSTANT BEGNG xxx
11111111 CONSTANT BEGNG xxx HAS TOO MANY
DECIMAL POINTS
Explanation: A fixed point constant or the mantissa part of a
floating point constant contains more than one radix point.
Sterling constants are not checked.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM028
11111111 CONFLICTING op OPTION
Explanation: The option named conflicts with a previously
specified option.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM029
11111111 xxx OPTION REQUIRED
Explanation: The option named must be specified.
Programmer Response: Probable user error. Correct any
•
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statements as part of a valid PL/I program.
IKM030
11111111 INVALID OPTION BEGNG op
Explanation: The option named is not a valid option keyword.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM031
11111111 EXPRESSION, MISSING AFTER xxx
Explanation: An expression to the right of an equal sign or IF
is missing. Checking of the statement is terminated.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
IKM032
11111111 INVALID ARGUMENT SPECIFIED FOR xxx
Explanation: The attribute 'or option named has an invalid
argument or argument list.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
Section 16: IKM Messages - PL/I Syntax Checker
16-3
IKM033
11111111 ARGUMENT MISSING AFTER xxx
Explanation: The argument that must follow the attribute or
option named is missing, or the argument list is empty.
Programmer Response: Probable usef error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM034
11111111 MULTIPLE xxx yyy SPECIFIED
Explanation: The attribute or option named has been
previously specified in this statement.
Programmer Response: Probable user error. Correct any
errors in your PL/lsource statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM040
Explanation: An ISUB dummy variable appears outside the
context of a DEFINED attribute of a DECLARE statement; or
the LIKE attribute is specified in an invalid context.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM041
IKM035
11111111 NO FILE SPECIFIED IN OPEN/CLOSE
STATEMENT
Explanation: The FILE option in an OPEN or CLOSE statement
is missing. No more checking of the statement is performed.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM036
11111111 ILLEGAL USE OR INCORRECT FORMAT
OR REFER OPTION
Explanation: The REFER option is used in an illegal context or
is specified in an invalid format.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
11111111 FILE ORGANIZATION MISSING FROM
ENVIRONMENT OPTION
Explanation: The file organization is not specified in the
ENVIRONMENT option.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
identifier or a decimal integer constant; 2) the identifier is not
a valid format item keyword, or 3) the FORMAT item has an
invalid format. Checking continues after the format list.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
.IKM042
11111111 CR OR DB IN FLOATING FIELD OF
PICTURE BEGNG xxx
Explanation: The CR or DB symbols must not be specified for
the exponent of a floating field in a PICTURE specification.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM039
111111111 CONFLICTING xxx ATTRIBUTE
Explanation: The attribute named conflicts with a previously
specified attribute. For DECLARE and ALLOCATE statements,
checking goes on for the next level··one declare variable (i.e.,
if the conflicting attribute is inside a structure, no more
checking of this structure is performed).
16-4
VS2 System Messages (VS2 Release 3.7)
11111111 xxx MUST HAVE ENTRY ATTRIBUTE
Explanation: The identifier named must be declared with an
ENTRY. attribute.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
11111111 INVALID xxx ATTRIBUTE SPECIFIED FOR
keywd
.
Explanation: The attribute named is not a valid attribute
keyword.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker tescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM044
IKM038
11111111 ERROR IN FORMAT LIST BEGNG xxx
Explanation: Either 1) a format item does not start with an
IKM043
IKM037
11111111 xxx ATTRIBUTE NOT PERMITTED IN
THIS CONTEXT
11111111 ILLEGAL BASE FOR DEFINED ITEM xxx
Explanation: The item named is defined on an invalid base.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM045
11111111 ERROR IN INITIAL ATTRIBUTE LIST
BEGNG xxx
Explanation: The INITIAL attribute list does not begin with a
constant, a string, or a repetition factor; or a + or - sign is
not followed by a constant.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table i, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM046
11111111 INVALID CHAR xxx IN PICTURE BEGNG
yyy
Explanation: The picture specification identified contains one
or more invalid characters.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM047
11111111 ILLEGAL USE OF CHAR xxx IN PICTURE
BEGNG yyy
Explanation: The .character identified is valid but improperly
used in a picture specification.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM048
11111111 EXPONENT FIELD MISSING IN PICTURE
BEGNG xxx
Explanation: In the picture specification for a floating point
number, the exponent field is missing.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM049
11111111 EXPONENT FIELD TOO LARGE IN
PICTURE BEGNG xxx
Explanation: In the picture specification for a floating point
number, the exponent field has too many decimal positions.
Programmer Response: Probable liser error. Correct any
errors in your PL/I source statement and let the syntax
check~r rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM050
11111111 MORE THAN ONE SIGN CHAR IN
PICTURE BEGNG xxx
Explanation: The numeric picture specification identified
contains more than one (not drifting) sign character.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM053
11111111 NO SCALING FACTOR PARENTHESES IN
PICTURE BEGNG xxx
Explanation: The parentheses enclosing the integer of a
scaling factor in the picture specification identified are missing.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/,I statement as part of a valid PL/I program.
IKM054
11111111 INVALID REPETITION FACTOR IN
PICTURE BEGNG xxx
Explanation: The repetition factor in the picture specification
identified is not an integer. A repetition factor in a picture
specification must be a non-zero integer enclosed in
parentheses.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM055
11111 MULTIPLE USE OF CHARACTER xxx IN
PICTURE BEGNG yyy
Explanation: The characters E, K, and V may occur once only
in a numeric picture specification.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I,items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM056
111111 NO DIGIT POSITION BEFORE EXPONENT IN
PICTURE xxx
Explanation: A picture specification for a floating point
number makes no allowance for the digits of a mantissa
preceding the delimiter E.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination:. Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM057
IKM051
11111111 INVALID SCALING FACTOR IN PICTURE
BEGNG xxx
Explanation: In the picture specification for a fixed point
number, the scaling factor is invalidly represented.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
11111111 PICTURE BEGNG xxx LONGER THAN 255
CHAR
Explanation: The picture specification identified exceeds the
maximum length of 255 characters.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and .Iet the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM058
IKM052
11111111 INVALID USE OF SCALING FACTOR IN
PICTURE BEGNG xxx
Explanation: A scaling factor may occur only in the picture
specification for a fixed-point number.
11111111 STERLING CHAR FOUND IN
NON-STERLING PICTURE xxx
Explanation: One of the characters 8, 7, 6, P, G, H, or M is
found but the character G did not start this picture
specification.
Section 16: IKM Messages - PL/I Syntax Checker
16-5
•
Programmer Response: Probable user error. Correct any
errors in your PLjl source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PLjl statement as part of a valid PLjl program.
IKM059
11111111 ILLEGAL· LEVEL NUMBER xxx
Explanation: A major structure name must be declared with
the level number 1. Minor structures must be declared with
level numbers greater than 1. Level numbers must be decimal
integers.
Programmer Response: Probable user error. Correct any
errors in your PLjl source statement and let the syntax
checker rescan it;
Problem Determination: Table I, items 13, 29. Compile your
PLjl statement as part of a valid PLjl program.
IKM060
11111111 PRECISION EXCEEDS xxx FOR PICTURE
BEGNG yyy
Explanation: The precision implied by the picture specification
for a fixed or floating point number exceeds the maximum
default precision.
Programmer Response: Probable user error. Correct any
errors in your PLjl source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PLjl statement as part of a valid PLjl program.
IKM061
11111111 ILLEGAL ASTERISK AS SUBSCRIPT IN
DEFINING LIST
Explanation: An asterisk is not allowed as a subscript in a
defining list.
Programmer Response: Probable user error. Correct any
errors in your PLjl source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PLjl statement as part of a valid PLjl program.
IKM062
], 1111111 ELEMENT xxx IS ILLEGALLY DEFINED
WITH ISUB
Explanation: ISUB variables may not be used to define a
scaler variable on an array base.
Programmer Response: Probable user error. Correct any
errors in your PLjl source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PLjl statement as part of a valid PLjl program.
IKM063
11111111 POSITION ATTRIBUTE ILLEGAL FOR
DEFINED ITEM xxx
Explanation: A POSITION attribute may not be specified for a
data item defined by ISUB variables on a base identifier.
Programmer Response: Probable user error. Correct any
errors in your PLjl source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PLjl statement as part of a valid PLjl program.
IKM065
11111111 SUBSCRIPTED BASE ILLEGAL FOR
DEFINED ITEM xxx
Explanation: The base identifier on which a data item is
defined may not be a subscripted name.
Programmer Response: Probable user error. Correct any
errors in your PLjl source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PLjl statement as part of a valid PLjl program.
IKM066
11111111 FORMAT LIST MISSING
Explanation: The format in a GET, PUT, or FORMAT statement
is missing.
Programmer Response: Probable user error. Correct any
errors in your PLjl source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PLjl statement as part of a valid PLjl program.
IKM067
11111111 FORMAT LIST CONTAINS NO DATA
FORMAT ITEM
Explanation: The format list in a GET or PUT statement must
include a format item for the data item being transmitted.
Programmer Response: Probable user error. Correct any
errors in your PLjl source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PLjl statement as part of a valid PLjl program.
IKM068
11111111 FORMAT ITEM xxx PERMITTED WITH
OUTPUT ONLY
Explanation: The format item named may not be used in the
format list of a· GET statement.
Programmer Response: Probable user error. Correct any
errors in your PLjl source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PLjl statement· as part of a valid PLjl program.
11111111 ILLEGAL ISUB VALUE
Explanation: The value of an ISUB dummy variable is outside
the range 1-32.
Programmer Response: Probable user error. Correct any
errors in your PLjl source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PLjl statement as part of a valid PLjl program.
16-6
IKM064
VS2 System Messages (VS2 Release 3.7)
IKM069
11111111 FORMAT ITEM xxx IS INVALID
Explanation: The format item named uses invalid characters
or is incorrectly written. Checking continues after the end of
the format list.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13. 29. Compile your
PLjl statement as part of a valid PLjl program.
IKM070
~.
11111111 NESTING OF FORMAT LIST EXCEEDS 20
Explanation: A format list in this statement is nested to more
than 20 levels.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM071
11111111 NO DATA SPECIFICATION OR CONTROL
OPTION FOUND
Explanation: The data list and format list for a GET or PUT
statement are missing.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM073
11111111 *BOUNDS ARE MIXED WITH
BOUNDS
NON~:
Explanation: Variable array bounds (denoted by asterisks)
may not be mixed with non-variable bounds in a DECLARE
statement.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM075
Explanation: An external name may not exceed seven
characters in length.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
.
checker rescan ~.
Problem Determination: Table I, items 13, 29. Compile YQur
PL/I statement as part of a valid PL/I program.
IKM077
11111111 IDENTIFIER BEGNG xxx IS TOO LONG
Explanation: An Identifier has more than 31 characters.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM078
11111111 UNMATCHED PARENTHESES, xxx
MISSING
Explanation: The left and right parentheses in the current
statement are unbalanced; one or more left or right
parentheses are missing. The statement is not checked further.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: TAble I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
11111111 ARRAY BOUND FOR xxx IS TOO LARGE
Explanation: The upper and/or lower bound of one or more
dimensions of an array exceeds the maximum value.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM074
11111111 EXTERNAL NAME BEGNG xxx LONGER
THAN SEVEN CHAR
11111111 INVALID DATA ITEM BEGNG xxx
Explanation: The data item is not a valid identifier or is
incorrectly written.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM072
IKM076
1111111 LOWER BOUND GREATER THAN UPPER
BOUND FOR xxx
Explanation: An array is declared with a lower bound greater
than the upper bound or with a single upper bound equal to or
less than zero.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM079
11111111 LEFT PARENTHESIS REQUIRED AFTER
xxx
Explanation: The option named must be followed by one or
more arguments enclosed in parentheses.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM080
•
11111111 OPERAND MISSING BEFORE xxx
Explanation: An identifier or expression preceding the item
named is missing. This error terminates checking of the
expression in question.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker tescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM081
11111111 INSUFFIDIENT ARGUMENT SPECIFIED
FOR xxx yyy
Explanation: The number of arguments specified in the
statement named is insufficient.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
Section 16: IKM Messages - PL/I Syntax Checker
16-7
IKM082
11111111 ON CONDITION INVALID OR MISSING
Explanation: An ON condition is either missing or invalidly
specified. Checking of the ON statement is terminated.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checkerrescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM083
1111111 INVALID SET/IN CLAUSE SPECIFIED FOR
xxx
Explanation: The clause following the SET or IN option is
invalid.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM084
11111111 VARIABLE IN LOCATE STATEMENT
INVALID OR MISSING
Explanation: The LOCATE keyword is not followed by an
unscripted, unqualified identifier.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM085
1111111 FACTORING NOT PERMITTED ON
ALLOCATE STATEMENT
Explanation: An ALLOCATE statement contains a list of two or
more factored variables.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM086
11111111 POINTER QUALIFIER AFTER POINTER
QUALIFIER OR SUBSCRIPT
Explanation: A pointer in a pointer qualifier may not be
pointer qualified or subscripted.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM087
11111111 OPERAND MISSING AFTER xxx
Explanation: An identifier or expression following the item
named is missing. Checking is terminated.
Programmer Response: Probable user error. Correct any
errors in your Pl/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
Pl/I statement as part of a valid PL/I program.
IKM088
11111111 NO DIGIT POSITION IN PICTURE BEGNG
xxx
Explanation: A picture specification must contain at least one
digit position.
Programmer Response: Probable user error. Correct any
16-8
VS2 System Messages (VS2 Release 3.7)
errors in your Pl/I source statement and let the syntax
checker rescan it.
Probelm Determination: Table I, items 13, 29. Compile your
Pl/I statement as part of a valid Pl/I program.
IKM089
11111111 INVALID OPERATOR xxx
Explanation: The operator is not valid for use in an
expression.
Programmer Response: Probable user error. Correct any
errors in your Pl/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
Pl/I statement as part ofa valid Pl/I program.
IKM090
11111111 IDENTIFIER MISSING AFTER xxx
Explanation: An operator is missing after the item named.
This error terminates the checking of the expression in
question.
Programmer Response: Probable user error. Correct any
errors in your Pl/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
Pl/I statement as part of a valid Pl/I program.
IKM091
11111111 OPERATOR MISSING BEFORE xxx
Explanation: An operator is missing after the item named.
This error terminates the checking of the expression in
question.
Programmer Response: Probable user error. Correct any
errors in your Pl/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
Pl/I statement as part of a valid Pl/I program.
IKM092
11111111 ILLEGAL LEFT PART OF ASSIGNMENT
STATEMENT
Explanation: An invalid operand appears to the left of the
assignment symbol. Checking of the statement is terminated.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
Pl/I statement as part of a valid Pl/I program.
IKM093
11111111 INVALID DO SPECIFICATION
Explanation: The keyword TO or BY is multiply used, or the
DO specification contains an illegal symbol.
Programmer Response: Probable USer error. Correct any
errors in your Pl/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
Pl/I statement as part of a valid Pl/I program.
IKM094
11111111 xxx MISSING IN yyy STATEMENT
Explanation: For example, the keyword TO or the label in a
GO TO statement is missing.
Programmer Response: Probable user error. Correct any
errors in your Pl/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
Pl/I statement as part of a valid Pl/I program.
IKM095
11111111 SEMICOLON NOT FOUND WHEN
EXPECTED
Explanation: The semicolon marking the end of a logically
complete statement is missing, or no semicolon is found for
the last statement of the input buffets.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker· rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM099
Explanation: The ENTRY attribute may not apply to more than
three logical levels.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM100
IKM096
11111111 INVALID EVENT NAME BEGNG xxx
Explanation: In a WAIT or input/output statement, the event
name specified for the EVENT option is invalid.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM097
11111111 BREAK CHAR INVALID AT BEGNG OF
IDENTIFIER xxx
Explanation: The identifier may not begin with a break
character.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM098
11111111 INVALID FORM OF INITIALIZATION FOR
xxx
Explanation: The intialization specified in this statement does
not comply with the rules of PL/I syntax.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
11111111 MORE THAN 3 LEVELS OF ENTRY
NESTING
11111111 INVALID REPETITION FACTOR IN INITIAL
LIST
Explanation: The repetition factor, a decimal integer constant,
must be enclosed in parentheses and must precede the value
or character to which it relates.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
IKM101
11111111 MORE THAN 63 TRUE LEVEL NUMBERS
SPECIFIED FOR xxx
Explanation: A structurE: may have a maximum of 63 levels,
including the major structure number 1.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker rescan it.
Problem Determination: Table I, items 13, 29. ~ompile your
PL/I statement as part of a valid PL/I program.
IKM102
11111111 MORE THAN 32 DIMENSIONS SPECIFIED
FOR xxx
Explanation: An array may have a maximum of 32
dimensions.
Programmer Response: Probable user error. Correct any
errors in your PL/I source statement and let the syntax
checker res can it.
Problem Determination: Table I, items 13, 29. Compile your
PL/I statement as part of a valid PL/I program.
Section 16: IKM Messages - PL/I Syntax Checker
16-9
•
16-10
VS2 System Messages (VS2 Release 3.7)
VS2.03.8J3
Section 16A: TSO /VTAM Messages (IKT)
Component Name
IKT
Program Producing Message
TSO/VTAM time sharing.
Audience and Where Produced
For operator: console.
Message Format
xx IKTnnns Text
xx
Message reply identification (absent if operator reply not required).
nnn
Message serial number.
n
Type code:
A
Action; operator must perform a specific action.
D
Decision; operator must choose an alternative.
I
Information; no operator action is required.
Comments
IKT messages (and IKJ messages) are produced when TSO/VTAM is in operation.
Associated Publications
OS/VS2 TSO Terminal Messages Directory, SY28-0654
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IKT001D nnn USER(S) ACTIVE - REPLY 'U', 'SIC', or 'FSTOP'
Explanation: An operator START command was issued to
activate TCAS and nn users were found to be active from a
previous session. This situation can occur if TCAS previously
failed and users were not properly terminated.
System Action: The system waits for the operator to reply.
Operator Response: Reply 'U' to continue START processing
and to allow the active users to remain active. Reply 'SIC' to
cancel the active users normally, allowing any messages
queued for them to be received, after which START processing
will continue. Reply 'FSTOP' to force immediate cancellation of
the active users, after which START processing will continue.
Use 'FSTOP' only if 'SIC' is ineffective.
IKT002D
TCAS IS TERMINATING, REASON CODE
cde
Explanation: TCAS was unable to continue its normal
processing due to an error, indicated by code (cde):
Reason
Code
Explanation
04
The attempt to activate TCAS was invalid because
TCAS was already in the system.
The TCAS main task was unable to attach the VTAM
16
interface subtask.
The TCAS main task was unable to attach the user
20
interface subtask.
24
The TCAS main task was unable to attach the console
communication subtask.
28
TCAS was unable to obtain storage for the TCAS table
(TCAST) in the common service· area (CSA).
32
The TCAS main task abnormally terminated and was
unable to recover.
48
The VTAM interface subtask abnormally terminated
and was unable to recover.
52
The user interface subtask abnormally terminated and
was unable to recover.
56
The console communication subtask abnormally
terminated and was unable to recover.
System Action: TCAS terminates normally for codes 04, 48,
52, and 56. TCAS terminates abnormally for codes 16, 20, 24,
28, and 32.
Operator Response: A dump should be obtained by specifying
'DUMP' in response to TCAS termination message IKT012D.
Problem Determination: Table I, items 2, 4, 13, 16, 33.
IKT003D
TCAS UNABLE TO ACCEPT LOGONS, REASON CODE
== cde - REPLY 'RETRY' or 'TERM'
Explanation: TCAS issues this message when VTAM either fails
to open the TCAS AC8 or fails to accept logons to TSO. A
code (cd e) indicates the cause of the error:
Reason
Explanation
Code
16
The SETLOGON macro instruction, issued by TCAS to
allow VTAM to accept logons, failed.
A VTAM OPEN macro instruction could not be
20
processed because of a temporary shortage of
storage.
82
The network (system) operator issued a HALT VTAM
command and VTAM is shutting down.
84
Either the address supplied in the AC8's APPLIO field
lies beyond TCAS's addressable range, or no entry
could be found in the resource definition table (ROT)
tha~ matches the name indicated by the AC8's APPLIO
field. If the OPEN macro ihstruction was specified
correctly, your installation may have failed to include
TSO's application program 10 (which is TSO) during
VTAM definition.
A match for application program 10 TSO was found,
86
but it was for an entry other than APPL entry.
88
Another AC8, already opened by VTAM, indicates the
same application program 10 (TSO) that this AC8
does. The installation may have assigned the same
application program 10 to two different versions of
TSO. This is valid only if the programs do not run (or
are at least not open) concurrently.
No entry could be found in the resource defintion
90
table (ROT) that matches the name (TSO) indicated by
the AC8's APPLIO field. This error may have occurred
because the installation deactivated the APPL entry or
never created it.
VTAM has been included as part of the operating
92
system, but is inactive.
Section 16A: IKT Messages - TSOjVTAM
16A-1
I
VS2.03.813
96
An apparent system occurred. Either there is a defect
in VTAM's logic, or ther is an error in TCAS's of the
OPEN macro instruction that VTAM did not properly
detect.
System Action: Processing continues.
Operator Response: Reply 'RETRY' to cause TCAS to try again
to accept logons. Reply 'TERM' to cause TCAS to terminate.
IKT004D
INVALID PARAMETERS SPECIFIED - RESPECIFY OR
REPLY'U'
Explanation: One or more invalid parameters were specified
when attempting to start, modify, or stop TCAS.
System Action: The system waits for the operator to reply.
Operator Response: Respecify all the parameters, or reply 'U'
to cause the command to be ignored.
IKT0051
TCAS IS INITIALIZED
Explanation: TCAS initialization began in response to a START
TSO command, and is now complete.
System Action: Unless they are suppressed, logons to
TSO/VTAM time sharing are now accepted.
Operator Response: None.
IKT0061
TCAS ENDED
Explanation: TCAS has ended normally.
System Action: TSO/VTAM time sharing is terminated.
Operator Response: None.
IKT0071
TCAS ACCEPTING LOGONS
Explanation: Logon are unsuppressed because of an operator
START or MODIFY command.
System Action: Logons to TSO/VTAM time sharing are now
accepted.
Operator Response: None.
IKTOOSI
TCAS NOT ACCEPTING LOGONS
Explanation: TCAS has stopped accepting logons in response
to an operator's command. No new logons will be accepted
until requested by the operator.
System Action: Processing continues.
Operator Response: None.
IKT0091
TPEND HAS OCCURRED, TCAS TERMINATION IN
PROGRESS
Explanation: VT AM has notified TCAS of a TPEND situation
(that is, a HALT command was issued to stop VT AM or VTAM
has abnormally terminated), and TCAS is terminating.
System Action: TCAS performs termination processing.
Operator Response: None.
IKTOI0D
nn USER(S) ACTIVE - REPLY 'SIC' OR 'FSTOP'
Explanation: A STOP command was entered to stop TCAS and
nn terminal users are still active.
System Action: The system waits for the operator to reply.
Operator Response: Reply 'SIC' to cancel the active users
normally. This allows them to receive any messages queued for
them, and it allows TSO /VTAM to perform its normal
termination processing. Reply 'FSTOP' to force immediate
cancellation of the active users. The users will not receive any
messages queued for them, and TSO/VTAM will opt perform
its normal termination processing (that is, task resource
manager processing will be circumvented). 'FSTOP' should be
used only if 'SIC' is ineffective.
16A-2
VS2 System Messages (VS2.03.S13)
IKTOlll
TCAS UNABLE TO
{ACCEPT }LOGONS,
SUPPRESS
REASON CODE = cde
Explanation: TCAS issues this message in response to an
operator MODIFY command requesting that TCAS accept or
suppress logons. VTAM either failed to open the TCAS ACB or
failed to accept or suppress logons to TSO. A code (cd e)
indicates the cause of the error:
Reason
Explanation
Code
16
The SETLOGON macro instruction, issued by TCAS to
allow VTAM to accept or suppress logons, failed.
A VTAM OPEN macro in.struction could not be
20
processed because of a temporary shortage of
storage.
The network (system) operator issued a HALT VTAM
82
command and VTAM is shutting down.
Either the address supplied in the ACB's APPLID field
84
lies beyond TCAS's addressable range, or no entry
could be found in the resource definition table (RDT)
that matches the name indicated by the ACB's APPLID
field. If the OPEN macro instruction was specified
correctly, your installation may have failed to include
TSO's application program ID (which is TSO) during
VTAM definition.
A match for application program ID TSO was found,
86
but it was for an entry other than an APPL entry.
Another ACB, already opened by VTAM, indicates the
88
same application program ID (TSO) that this ACB
does. The installation may have assigned the same
application program ID to two different versions of
TSO. This is valid only if the programs do not run (or
are at least not open) concurrently.
90
No entry could be found in the resource definition
table (RDT) that matches the name (TSO) indicated by
the ACB's APPLID field. This error may have occurred
because the installation deactivated the APPL entry or
never created it.
VTAM has been included as part of the operating
92
system, but is inactive.
An apparent system error occurred. Either there is a
96
defect in VTAM's logic, or there is an error in TCAS's
use of the OPEN macro instruction that VTAM did not
properly detect.
System Action: Processing continues.
Operator Response: None.
IKT012D
TCAS TERMINATION IN PROGRESS - SPECIFY
OR 'DUMP'
'u'
Explanation: TCAS is terminating either normally or abnormally
and an SVC dump can be requested.
System Action: The system waits for the operator to reply.
Operator Response: Specify 'u' to continue termination
processing without a dump. Specify 'DUMP' to produce a dump
of virtual storage.
IKT0131
PARMLIB CANNOT BE OPENED, DEFAULT
PARAMETERS USED
Explanation: An error occurred while TCAS was attempting to
open parmlib causing TSO/VTAM time-sharing default
parameters to be used.
System Action: TCAS initialization continues.
Operator Response: None.
VS2.03.S13
IKTOI41
I/O ERROR READING PARMLlB, DEFAULT
PARAMETERS USED
Explanation: An I/O error occurred while TCAS was reading
TSOjVTAM time-sharing parameters from parmlib, causing
default parameters to be used.
System Action: TCAS initialization continues.
Operator Response: None.
IKTOISI
MODIFY COMMAND REJECTED, INVALID
PARAMETER(S) SPECIFIED
Operator Response: None.
IKTIOll
USERID userid CANCELED DUE TO RECONNECT
TIMER EXPIRATION
Explanation: A terminal user (userid) was in a reconnect state
and failed to reestablish connection (LOGON RECONNECT)
with TSOjVTAM time sharing within the specified time limit, or
the specified time limit was zero.
System Action: The terminal is disconnected from the system.
Operator Response: None.
Explanation: A MODIFY command issued to modify TCAS
IKTI021
specified one or more invalid parameters.
System Action: The command is ignored.
Operator Response: Respecify the command.
IKTOI6D
INVALID REPLY - RESPECIFY
Explanation: An invalid reply was made to a previous operator
message.
System Action: The system waits for the operator to reply.
Operator Response: Specif¥ a valid reply.
Explanation: A terminal user (userid) attempted to reestablish
connection (LOGON RECONNECT) with TSOjVTAM time
sharing, and in attempting to reestablish the session an
unrecoverable VTAM error was encountered.
System Action: The terminal is disconnected from the system.
Operator Response: None.
IKTI031
IKTOI71
FILE FOR PRINTING TSOjVTAM TIME SHARING
PARAMETERS CANNOT BE OPENED
Explanation: An error was encountered during TCAS
.initialization while attempting to open the file for printing
TSO jVT AM time-sharing parameters.
System Action: The parameters are not printed but TCAS
initialization continues.
Operator Response: None.
IKTOISI
I/O ERROR PRINTING TSOjVTAM TIME SHARING
PARAMETERS, PRINTING STOPPED
Explanation: An error was encountered during TCAS
initialization while printing TSOjVTAM time sharing parameters
from parmlib.
System Action: Printing of the parameters is stopped but
TCAS initialization continues.
Operator Response: None.
IKTOI91
TERMINAL termid CANNOT BE CONNECTED OR
RELEASED BY VTAM
Explanation: A user attempted to log on to TSO jVT AM time
sharing from terminal termid. VTAM was unable to connect the
terminal to TCAS, then was unable to release it.
System Action: Processing continues, but the terminal will be
unavailable for use until the next time TSO is started.
Operator Response: Notify the system programmer that the
problem has occurred.
TCAS
J
{VTAM INTERFACE
USER INTERFACE
CONSOLE COMMUNICATION
SUBTASK ABNORMALLY TERMINATED,
RECOVERY IN PROGRESS
Explanation: A TCAS subtask has abnormally terminated.
System Action: TCAS reattaches the terminated task.
Operator Response: None.
IKT0201
IKTIOOI
USERID userid CANCELED DUE TO UNCONDITIONAL
LOGOFF
Explanation:. A VTAM USS unconditional logoff command was
issued by a terminal user (userid), causing VTAM to disconnect
the terminal from TSO before TSO could do normal logoff
processing.
System Action: The terminal is disconnected form the system.
USERID userid CANCELED DUE TO RECONNECT
FAILURE
UNKNOWN CODE RETURNED TO TSOjVTAM
LOSTERM EXIT ROUTINE
Explanation: The return code given to the LOSTERM exit
routine of TSOjVTAM time sharing is not recognized. Either a
list of entry codes is outdated or there is a parameter list
error.
System Action: The code is written to SYS1.LOGREC and
processing continues.
Operator Response: Report the message to the system
programmer so that he can determine why it was issued.
IKTI041
TSOjVTAM ACB ERROR DUE TO INSUFFICIENT
STORAGE
Explanation: A user tried to log on to TSO jVT AM time sharing,
and TSO's attempt to open an ACB was unsuccessful because
sufficient storage was unavailable to VTAM.
System Action: The terminal user's address space is
terminated but system processing continues.
Operator Response: Report this message to the system
programmer.
IKTIOSI
LOGON REJECTED DUE TO INVALID APPLICATION
10
Explanation: TCAS assigned an invalid application program 10
to a terminal user attempting to log on to TSOjVTAM time
sharing.
System Action: The terminal user's address space is
terminated but system processing continues.
Operator Response: Report this message to the system
programmer.
Programmer Response Find the invalid application ID (offset 0
in TVWA) in the dump caused by the terminated user address
space. Valid IDs can be found in SYS1.VTAMLST.
IKTI061
LOGON REJECTED, CANNOT OPEN ACB
Explanation: A terminal user was unable to log on to
TSOjVTAM time sharing because of an OPEN ACB failure from
an unknown cause.
System Action: The user address space is terminated but
system processing continues.
Operator Response: Report this message to the system
programmer.
Programmer Response: Check the ERROR field of TSOjVTAM's
OPEN. ACB. The values that can be set in this field, and their
meanings, are listed in VT AM Macro Language Reference,
GC27-699S.
Section I6A: IKT Messages - TSOjVTAM
I6A-3
•
VS2.03.813
IKTI071
TSO/VTAM UNABLE TO DISCONNECT TERMINAL
ExPLANATION: A terminal user logged off from TSO/VTAM
time sharing and the VTAM ACB associated with the user was
closed, but a VTAM error has prevented the user's
disconnection from TSO.
16A-4
VS2 System Messages (VS2.03.813)
System Action: The user address space terminates with
ABEND code OAB (register 15 contains 0203). The terminal
that could not be disconnected is not available to other users.
Operator Response: Try to make the terminal available to other
users by varying it offline, deactivating it, and then reactivating
it.
VS2.03.807
Section 17: Auxiliary Storage Management Messages (ILR)
Component Name
ILR
Program Producing Message
ILRRIM03 (alias IEAVNPB4), ILRTMCOO.
Audience and Where Produced
For operator: console.
Message Format
ILRnnns text
nnn
Message serial number.
s
Type code:
I
Information; no operator action is required.
W Wait; processing stopped until action is determined and performed ..
text
Message text.
Problem Determination
Refer to Tables I and II at the back of this publicfltion for problem determination 'instructions.
ILR0011
DYNAMIC ALLOCATION OF SYS1.STGINDEX FAILED,
NO VIO JOURNALING
Explanation: ASM's task mode initialization routine was unable
to sucessfuily execute a dynamic allocation. request to create a
ddname of SYS1.STGINDEX. This operation is required to open
SYS1.STGINDEX.
System Action: ASM will issue message ILR022A before
continuing operation. If the operator enters REPLY xx, 'U', ASM
attempts to complete other non-VIO-related, initialization
procedures. Journaling requests for VIO data sets will be
rejected by ASM. If warm start had been requested, jobs
requiring VIO data sets journaled on the previous IPL will not
be able to be restarted.
Operator Response: Report this message to the system
programmer.
Programmer Response: Occurrence of this message indicates
that SYS1.STGINDEX was inaccessible to dynamic allocation .or
a system error occurred. If warm start had been requested, the
contents of SYS1.STGINDEX may still be retrievable if the
problem is corrected and re-IPL is performed before any reply
to message ILR022A.
In other cases, respond as indicated to message ILR022A,
which follows this message.
Problem Determination: Table I, items 2, 11, 18, 24, 28, 29,
30,34.
ILR0021
INITIALIZATION OF SYS1.STGINDEX FAILED, NO VIO
JOURNALING
Explanation: ASM's task mode initialization routine was unable
to fully initialize the SYS1.STGINDEX data set for CVIO
processing. To fully initialize SYS1.STGINDEX, ASM must:
• Open the data set.
• Write the timestamp record.
• Close the data set.
• Reopen the data set for normal processing.
If any of these operations fail, or if the ESTAE recovery routine
receives control during any of these operations, this message
is issued.
System Action: ASM will issue message ILR022A before
continuing operation. If the operator enters REPLY xx,'U' to
message ILR022A, ASM attempts to complete other
non-VIO-related initialization procedures. Journaling requests
for VIO data sets will be rejected by ASM.
Operator Response: Report this message to the system
programmer.
Programmer Response: Respond as indicated to message
ILR022A, which follows this message.
Problem Determination: Table I, items 2, 11, 18, 24, 28 29,
30,34.
ILR003A
WARM START FOR VIO FAILED. REPLY
INVOKE CVIO PROCE,SSING
'u'
TO
Explanation: ASM's task .(!lode initialization routine was unable
to restore the SYS1.STGINDEX data set and/or ASM control
blocks to reflect the stabts of journalled VIO data sets from
•
the previous IPL. To perform this function, ASM must:
• Open and verify SYS1.STGINDEX.
• Read all valid records containing ASPCTs.
• Update the PATs to reflect the external storage slots
allocated to journalled VIO data sets.
If any of these operations fail, this message is issued.
System Action: ASM waits for a response from the operator. If
the operator enters REPLY xx, 'U', system operation continues
and ASM switches to CVIO processing for SYS1.STGINDEX. If
ASM is sucessful, VIO journaling will be possible for this IPL.
However, any VIO data sets journalled on the previous IPL are
lost, and jobs requiring these data sets will not be able to be
restarted.
Operator Response: Report this message to the system
programmer. At his direction,· either take a stand alone dump
, and re-IPL,' or enter REPLY xx, 'u' to invoke CVIO processing.
Programmer Response: Occurrence of this message indicates a
problem with SYS1.STGINDEX or its contents. A stand alone
dump should reveal the problem. If SYS1.STGINDEX itself is
the problem, it may be possible to correct the problem and
re-IPL with the warm start option again, without losing the
contents of SYS1.STGINDEX.
Problem Determination: Table I, items 2, 11; 18, 24, 28, 29,
30,34.
ILR0041
ASM UNABLE TO BUILD DATA SET NAME LIST,
PAGEADD' COMMAND UNUSABLE
Explanation: ASM's task mode initialization routine was unable
to build the page and'swap data set name lists required for
the PAGEADD command processor. The PAGEADD command
will not be able to function.
System Action: System operation continues with the PAGEADD
command unusable.
Operator Response: Report this message to the system
programmer.
Section 17: ILR Messages - Auxiliary Storage Management
17·1
I
VS2.03.807
/~
Programmer Response: Occurrence of this message indicates
that ASM's task mode initialization routine was unable to
obtain subpool 241 space in the CSA. This situation may
indicate a larger system problem with the CSA or a problem in
the ILRTMIOO module. Correct the size of the CSA, if
necessary. Otherwise, notify your IBM programming support
representative.
Problem Determination: Table I, items 2, 18, 29.
ILR0051
PLPA PAGE DATA SET FULL, OVERFLOWING TO
COMMON DATASET
Explanation: The PLPA page data set has become full. All
subsequent writes for the PLPA will be sent to the COMMON
page data set.
System Action: Processing continues with PLPA pages on the
PLPA and COMMON page data sets.
Operator Response: Report this message to the system
programmer.
Programmer Response: Occurrence of this messasge indicates
that the size of the PLPA page data set is inadequate.
Increase the size,~f the PLPA page data set before the next
IPL, if desired.
Problem Determination: Table I, items 2, 18, 28, 34.
ILR0061
COMMON PAGE DATA SET FULL, OVERFLOWING TO
PLPA DATA SET
Explanation: The COMMON page data set has become full. All
writes for the COMMON page data set will be sent to the PLPA
page data set.
System Action: Processing continues with COMMON pages on
the COMMON and PLPA page data sets. All subsequent write
requests will be attempted to the COMMON' page data set and
only sent to the PLPA page data set if no space is yet
available on the COMMON page data set.
Operator Response: Report this message to the system
programmer.
Programmer Response:' Occurrence of this message indicates
that the size of the COMMON page data set is inadequate;
Increase the size of the COMMON page data set before the
next IPL.
Problem Determination: Table I, items 2, 18, 28, 34.
ILR0071
DUPLEX PAGE DATA SET
SUSPENDED
BAD ~DUPLEXING
{ FULLf
Explanation: Either the DUPLEX page data set has become full,
or the DUPLEX page data set has become unusable because of
permanent I/O errors on that volume.
System Action: Processing continues, but duplexing of PLPA
and COMMON pages has been suspended.
Operator Response: Report this message to the system
programmer.
Programmer Response: Occurrence of this message for a full
data set indicates that the size of· the page data set allocated
to the duplex storage is inadequate. Increase the size of the
DUPLEX page data set before the next IPL.
If the message wa~. issued for an unusable page data set,
correct or replace the unusable page data set before the next
IPL.
Problem Determination: Table I, items 2, 18, 24, 28, 29, 30,
34.
17·2
VS2 System Messages (VS2.03.807)
ILR008W{ PLPA
~PAGE DATA SET ON VOL ser BAD, ASM
COMMON UNABLE TO CONTINUE
LOCAL,
DUPLEX
.
Explanation: ASM is unable to continue, due to one of the
following reasons:
• The system is unable to access both the PLPA and DUPLEX
page data sets.
• The system is unable to access any user LOCAL page data
set. ALL LOCAL page data sets are unusable.
• The system is unable to access both the COMMON and
DUPLEX page data sets.
• The system is unable to access either the PLPA or
COMMON page data set, and duplexing was not active.
• The system is unable to access the DUPLEX page data set,
and both the PLPA and COMMON page data sets are full.
• The system is unable to access either the PLPA or
COMMON page data set, and the DUPLEX page data set
has become full.
• The PLPA and COMMON page data sets have become full,
and duplexing was not active.
System Action: The system is placed in a X'02E' or X'03C'
. wait state.
Operator Response: Report this message to the system
programmer.
Programmer Response: Determine which page data sets are no
longer usable, and correct or replace these data sets before
the next IPL.
Problem Determination: Table I, Items 2, 18, 24, 28, 29, 30,
34.
ILR0091
{SWAP
~ DATA SET ON VOL ser BAD
PLPA PAGE
COMMON PAGE
LOCAL PAGE
Explanation: ASM is unable to access a page or swap data set
for one of the following reasons:
.A permanent I/O error occurred.
• No 10RB-IOSB-SRB was available.
System Action: Processing continues without the unusable
data set.
Operator Response: Report this message to the system
programmer.
Programmer Response: Correct or replace the unusable data
set before the next IPL.
Problem Determination: Table I, items 2, 18, 24, 28, 29, 30,
34.
,ASM USING
ILROIOI {PLPA
} PAGE DATA {FULL}
COMMON
BAD
ONLY DUPLEX PAGE DATA SET
Explanation: ASM is l!sing the DUPLEX page data set ·for all
PLPA/COMMON reads and/or writes, due to one of .the
following reasons:
• Message ILROO91 has been issued for the PLPA or
COMMON page data set. All reads and writes for the PLPA
or COMMQN page data set will' be done from the DUPLEX
page data set.
• Message ILROO91 has been 'issued for the PLPA or
COMMON page data set, and now the PLPA or COMMON
page data set has become full. All writes for the COMMON
or PLPA page data set will be done to the DUPLEX page
data set.
,1
V$2~03~807
System Action: Processing using only the DUPLEX page data
set.
Operator Response: Report this message to the system
programmer.
Programmer Response: Correct or replace the unusable page
data set before tht} next IPL.
Problem Determination: Table I, items 2, 18, 24, 28, 29, 30,
34.
ASM ENQ FOR SYS1.STGINDEX FAILED. CVIO
REQUIRED NEXT IPL
Explanation: The task mode initialization. routine of ASM was
unable to successfully enqueue on the SYS1.STGINDEX data
set. The data set will not be exclusively accessible by ASM.
System Action: ASM will issue message ILR022A before
continuing operation. If the operator responds REPLY XX, 'U' to
message ILR022A, ASM will not close SYS1.STGINDEX and VIO
journaling will not be possible during this IPL. If warm start had
been requested, all journaled VIO data sets will be lost.
Operator Response: Report this message to the system
programmer.
Programmer Response: Respond as indicated to message
ILR022A, which follows this message.
Problem Determination: Table I, items 2, II, 18, 24, 28, 29,
30,34.
but ASM will not process VIO journaling requests. If warm start
had been requested, all journaled VIO data sets will be lost.
The data set name list will not have been built.
Operator Respor:tSe: Report this message to the system
·prbgrammer.
Programmer Response: Respond as indicated to message
ILR022A, which follows this message.
Problem Deter:mination: Table I, items 2, 11, 18, 24, 28, 29,
30,34.
ILR0201
ILR0211
UNEXPECTED ERROR DETECTED DURING VIO
INITIALIZATION PROCESSING
Explanation: An undetermined error occurred during execution
of ASM's task mode initialization routine, and ASM's recovery
routine (ESTAE) receivt}d control. VIO journaling and possibly
the PAGEADD command processor will not be functional this
IPL.
System Action: ASM will issue message ILR022A before
continuing operation. If the operator enters REPLY XX, 'U' to
message ILR022A, ASM's task mode initialization routine will
be bypassed. SYS1.STGINDEX mayor may not be left open,
ILR022A
REPLY 'U' TO CONTINUE WITHOUT VIO
JOURNALING
Explanation: ASM's task mode initialization routine or its
recovery routine (ESTAE) has detected one or more problems
that will prevent VIO journaling on ths IPL. Message ILROOll,
ILROO21, ILR020l, or ILR0211 precedes this message.
System Action: ASM waits for a response from the operator.
System operation continues only if the operator enters REPLY
xx/U' in response to this message.
If the operator does enter REPLY XX, 'U', the corresponding
system action is described under the message preceding this
message.
Operator Response: Report this message to the system
programmer. At his direction, either take a stand alone dump
and re-IPL, or enter REPLY xx, ·U'.
Programmer Response: Occurrence of this message and the
preceding message indicate a probable system error. If your
system does not require VIO journaling or the PAGEADD
command, system processing may be continued by the
operator responding REPLY xx, ·U'. However, it is recommended
that the operator take a stand alone dump and correct the
problem before the next re-IPL.
Notify your IBM programming support representative on all
occurrences of this message.
Problem Determination: Table I, items 2, II, 18, 24, 28, 29,
30,34.
Section 17: ILR Messages - Auxiliary Storage Management
17·3
I
17-4
VS2 System Messages (VS2.03.807)
Section 18: FORTRAN Syntax Checker Messages (IPD)
Component Name
IPO
Program Producing Message
FORTRAN syntax checker.
Audience and Where Produced
For remote operator and programmer: terminal.
Message Format
I POnnn xxxxxxxx yyyyyy text
nnn
Message serial number.
xxxxxxxx
Data set line number of the line in which the error was detected.
yyyyyy
Characters in error.
text
Message text.
xx
Message reply identification (absent, if operator reply not required).
Comments
Central operator may request that messages appear on his console.
Associated Publications
OS!VS2 TSO Terminal User's Guide, GC28-0645.
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IPDOOO
SYSTEM OR SYNTAX CHECKER FAILURE
Explanation: While scanning the last statement, the syntax
checker encountered a condition that should not occur. It may
be a hardware, syntax checker, or operating system error.
Problem Determination: Table I, items 3, 29.
'\
IPD002
UNRECOGNIZABLE STMNT OR MISSPELLED KEYWD
Explanation: The statement was not a recognizable FORTRAN
statement type, or a keyword of six or fewer characters was
misspelled. An assignment statement with errors to the left of
the ' - ' is unrecognizable.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD004
UNSIGNED INTEGER EXPECTED
Explanation: An invalid form, such as an integer constant
preceded by a plus or minus sign, was encountered in the
statement where (1) an unsigned integer is the only valid form,
or (2) an unsigned integer or unsigned variable is the only
valid form.
Programmer Response: Probable user error. Make the
correction as noted in the explanation and rerun the job or
jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD006
POSSIBLY TOO MANY SUBSCRIPTS PRECEDE
Explanation: A list of eight or more (four or more in
FORTRAN E) names within parentheses has been found
following a symbolic name on the left side of the equal sign in
an assignment statement or statement function definition. If
the statement is a statement function definition, the message
should be ignored.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD010
TOO MANY SUBSCRIPTS
Explanation: A list of eight or more (four or more in
FORTRAN E) expressions within parentheses has been found
following a symbolic name in a place where a subscripted
variable reference would be valid.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD012
) EXPECTED
Explanation: Either a required parenthesis was missing or
there was no right parenthesis to match a left parenthesis.
Programmer Response: Probable user error. Make correction
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
EXPRESSION EXPECTED
Explanation: An expression is either missing or invalid in the
statement where a valid one is expected. For example, each of
these statements would receive this message:
l.A=
lie".
IPD008
2. G (I,J) - C (I, )
3. X - Y+2.00( I11III2+6.28)
The source characters in error in the message would be: none
for statement 1; ")' for statement 2; 'I11III2+6.' for statement 3.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD014
ARITH IF REQUIRES STATEMENT NUMBER LIST
Explanation: There was a missing or invalid statement number
in the list of statement numbers after an arithmetic IF
statement (FORTRAN G and H only).
Programmer Response: Probable user error. Make correction
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
,I
jV'
Section 18: IPD Messages - FORTRAN Syntax Checker
18-1
IP0016
INVALID EXPRESSION IN IF STATEMENT
Explanation: The expression within parentheses after the IF
keyword of a logical or arithmetic IF statement was not
recognizable as either a valid logical or arithmetic expression.
(FORTRAN G and H only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IP0018
UNRECOGNIZABLE STNMT AFTER LOGICAL IF
Explanation: The statement following the IF (logical
expression) was not a recognizable FORTRAN statement type,
or there was something other than blanks between the right
parentheses at the end of the logical expression and the start
of the statement. Some errors in arithmetic IF statements will
cause this message to be issued. (FORTRAN G and H only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD020
NON-ZERO INTEGER EXPECTED
Explanation: The indicated numeric constant is zero, not an
integer constant, or both.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD022
ILLEGAL STATEMENT AFTER LOGICAL IF
Explanation: The statement following the IF(logical
expression) is not one of the statement types permitted after a
logical IF. The statement cannot be a DO, another logical IF,
any non-executable statement, nor any of the DEBUG
statements. (FORTRAN G and H only.)
. Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD026
DATA SET NUMBER EXPECTED
Explanation: An input; output statement had neither. an
unsigned non-zero integer nor a variable names in the correct
position for the data set reference numbers.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD028
LENGTH SPECIFICATION INVALID
Explanation: In a type-statement, a length specification was
missing or was incorrect for the type of statement specified for
the variables or function. (FORTRAN G and H only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD030
( EXPECTED
Explanation: A required left parenthesis is missing. This
message is not issued for statements where parentheses are
optional (assignment statements, for example), but is issued
where a pair of parentheses is mandatory (as in FUNCTION,
EQUIVALENCE, WRITE, etc.).
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
18-2
VS2 System Messages (VS2 Release 3.7)
IPD032
NAME EXPECTED
Explanation: A required name is missing or is preceded by
characters that cannot begin a name. For example, all these
statements will receive this message:
FUNCTION (A,B,C)
DIMENSION, X(20,30)
DEFINE FILE 8(10,20,U,3X)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD034
DUMMY ARGUMENT EXPECTED
Explanation: A SUBROUTINE or FUNCTION statement has an
argument that is invalid - a constant or an expression, for
example. (This also applies to the ENTRY statement in
FORTRAN G and H.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD036
ARRAY DIMENSIONS EXPECTED
Explanation: A DIMENSION statement gave either partial or
no dimension information for one of its array names, or invalid
characters were between the array name and the dimension
information.
Progarmmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Tabel I, items 3, 15, 22, 29.
IP0038
/ EXPECTED
Explanation: The first name in a NAMELIST statement was not
preceded by a slash, or a name or list of data preceded by a
slash was not followed by a slash. (COMMON, SUBROUTINE,
FUNCTION, ENTRY, NAMELlST, DATA, INTEGER, REAL,
LOGICAL, and COMPLEX statements in FORTRAN G and H
only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
IPD040
INVALID DATA TYPE
Explanation: Either the type of a datum in a type-statement
did not agree with the type declared by the statement, the
datum was missing, or, in an Implicit statement, the type
specification was invalid (e.g., IMPLICIT REEL (0».
(Hexadecimal and both types of literal data are allowed in all
type statements.) (FORTRAN G and H only.)
Programmer Response: Probable user error. Make corrections
as' noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD042
STATEMENT NUMBER EXPECTED
Explanation: A FORMAT statement was not numbered or a
form other than a statement number was encountered after
the 'GO TO' in an unconditional GO TO statement. (In addition,
in FORTRAN G and H, the invalid form could be in an ASSIGN
or a CALL statement.)
Programmer Response: Probable user error. Make correction
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD044
'TO' EXPECTED
Explanation: An ASSIGN statement did not have 'TO' in the
required place. (FORTRAN G and H only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD046
ARGUMENT EXPECTED
Explanation: A CALL statement has an invalid or missing
argument in its argument list.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD048
DATA LIST EXPECTED
Explanation: A data statement contains no data list or the
data list is separated from the variable list by invalid
characters. (FORTRAN G and H only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD050
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD060
, EXPECTED
Explanation: A FIND statement did not contain an apostrophe
to separate the data set reference number from the expression
describing the record to be found. This message is issued only
if the omission of the apostrophe leaves a valid data set
reference number. For example, 'FIND (10100)' would not
cause this message because 10100 is not a valid data set
reference number.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD062
INCORRECT PARAMETER - MUST BE E, L, OR U
Explanation: The data set control character in a DEFINE FILE
statement was not an E, L or U.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
RELATIONAL OPERATOR EXPECTED
IPD064
DEBUG PARAMETER EXPECTED
Explanation: In a logical expression, an arithmetic expression
was not followed by a relational operator. (FORTRAN G and H
only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or job~tep.
Problem Determination: Table I, items 3, 15, 22, 29.
Explanation: A valid parameter did not follow a comma after
a valid parameter in a DEBUG statement. (FORTRAN G only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD052
IPD066
, EXPECTED
SUBSCRIPT EXPECTED
Explanation: In a statement with a relatively rigid form, such
as EQUIVALENCE or DEFINE FILE, a comma was absent or
preceded by invalid characters.
Programmer Response: Probable· user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
Explanation: A subscript was missing, not in one of the valid
forms, or separated from the preceding comma or left
parenthesis by invalid characters. (FORTRAN E only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD054
IPD06,
OPERAND EXPECTED IN ARITH EXPRESSION
Explanation: An arithmetic operator was not followed by a
valid arithmetic operand, or two operators occur together (as
in A III -B).
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD056
OPERAND EXPECTED IN LOGICAL EXPRESSION
TOO MANY LEVELS OF PARENTHESES
Explanation: In a FORMAT statement, group repeat
specifications~ were too deeply nested. FORTRAN E does not
allow a group repeat specification within a group repeat
specification. FORTRAN G and H do allow this, but allow no
further nesting of group repeat specifications.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
Explanation: A logical operator was not followed by a logical
operand, or a logical operand was missing. An invalid logical
operator, such as '.NOT.. NOT.', also causes this message.
(FORTRAN G and H only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
Explanation: A numeric constant that was not an integer was
found where an integer is required.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD058
IPD074
I/O LIST ITEM EXPECTED
Explanation: A variable name did not follow a comma in the
list of a READ or WRITE statement (or in FORTRAN G and H, a
PUNCH or PRINT statement).
IPD072
INTEGER EXPECTED
COMPLEX NUMBER INVALID
Explanation: The two parts of a complex constant did not
agree in length, or one or both parts was not a real constant.
(FORTRAN G and H only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
Section 18: IPD Messages - FORTRAN Syntax Checker
18-3
•
IPD076
DELIMITER MISSING OR INVALID FORMAT CODE
Explanation: In a FORMAT statement, either a format code
was invalid, a delimiter (such as the required comma or
slashes between two literal format codes) was missing or the
right parenthesis at the end of the FORMAT was missing.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD078
EXPECTED IN FORMAT CODE
Explanation: There was no period as required in the 'w.d'
following the 0, E, or F format code in a FORMAT statement.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table i, items 3, 15, 22, 29.
IPD082
NAME TOO LONG
Explanation: A symbolic name contains more than six
characters, a keyword of seven or more letters at the
beginning of a statement is misspelled, or a misspelled
keyword follows the IF (logical expression) part of a logical IF
statement. A missing delimiter may cause this message to be
issued. Each of the following statements would produce this
message:
38
CONTINUE
SUBROUTINE X(ARG1 ARG2)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD084
STATEMENT NUMBER INVALID
Explanation: The statement number field (positions 1-5 of the
initial line of a statement) was zero or contained at least one
character that was neither a digit nor a blank. Within a
statement, this message is issued if a statement number is
zero of contains too many digits.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD086
H-LiTERAL INCOMPLETE
Explanation: The number of characters in the statement after
the 'H' was smaller than the count before the 'H' in the
H-literal.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD088
FIELD WIDTH NOT IN RANGE 1-255
Explanation: The field width specified in a format code was
not in the required range.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
18-4
LITERAL EXCEEDS 255 CHARACTERS
Explanation: The number of characters between the
apostrophes of a literal exceeds 255. In determining the
number of characters enclosed, two adjacent apostrophes
within the outermost apostrophes are counted as one
character.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
VARIABLE LIST EXPECTED
Explanation: In a DATA statement, a variable name (or list of
variable names) did not occur (1) as the first item of the data
statement, or (2) after a comma following a list of constants
enclosed in slashes. This message is also issued when there
are invalid characters between the DATA keyword or the
comma and the list of variables. (FORTRAN G and H only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD080
IPD090
VS2 System Messages (VS2 Release 3.7)
IPD092
STATEMENT ANALYSIS EXCEEDS TABLE LIMITS
Explanation: The statement was so complicated that the
syntax checker ran our ot space in its table. The statement
~annot be checked by the syntax checker.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD094
END REQUIRES BLANK LABEL & CONTIN FIELDS
Explanation: Positions 1-6 of an END statement must be
blank, and an END statement cannot have continuation lines.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD096
INVALID OR EXCESS SOURCE CHARACTERS
Explanation: The statement being checked completely
satisfies
the definition for that type of statement at some point before
the last non-blank character in the statement. This may occur
if a delimiter has been left out between elements of a
statement.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD098
INVALID RANGE IN IMPLICIT STATEMENT
Explanation: An IMPLICIT statement contains a range of
characters in which the last character of the range
alphabetically precedes the first character of the range. Note
that '$' follows 'z' in the alphabet. A character that is not
alphabetic will also cause this message to be issued.
(FORTRAN G and H only.)
Programmer Response: Probable user error. Make. corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD100
FIRST LINE IS A CONTINUATION
Explanation: The first line scanned did not have 'c' in
position one, nor did it have a blank or zero in position six.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD102
COMMENT LINE WITHIN STATEMENT
Explanation: A comment line was found between an initial line
and a continuation line or between two continuation lines.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD104
TOO MANY CONTINUATION LINES
Explanation: The statement consisted of an initial line
followed by more than 19 continuation lines.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD106
TOO MANY DECIMAL PLACES FOR FIELD WIDTH
Explanation: in a 0, E, F, or G format code, the fractional
portion ('d' of 'w.d') exceeded the total field width ('w' of
'w.d'). (G in FORTRAN G and H only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD108
DECIMAL PLACES MUST BE SPECIFIED
Explanation: In a 0, E, or F format code, fractional portion
('d' of 'w.d') was missing or was separated from the decimal
point by invalid characters.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD120
INTEGER TOO LARGE
Explanation: The magnitude of an integer constant exceeds
2147483647.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep ..
Problem Determination: Table I, items 3, 15, 22, 29.
IPD122
CLOSING ' EXPECTED
Explanation: The end of the statement was reached without
finding the closing apostrophe for a literal constant or literal
format code. The opening apostrophe of the literal is the
source character identified in the error message. (Only the
literal format code is allowed in FORTRAN E.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD124
DATA ILLEGAL FOR DUMMY ARRAY
Explanation: An array was dimensioned in a REAL, INTEGER,
IPDllOI
) REQUIRED FOR IMPLIED DO
Explanation: In the input or output list of an I/O statement, a
right parenthesis was not the first non-blank character after
the parameters of an implied DO.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD1l2
DO VARIABLE CANNOT BE SUBSCRIPTED
Explanation: In an I/O list, a subscipted variable was used as
I
IV
the DO variable within an implied DO loop.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD1l4
LOGICAL or COMPLEX type-statement. One of the dimensions
was a variable name, making the array a dummy array, but a
slash, indicating the start of a list of data, was then
encountered. Dummy arrays cannot be assigned initial data
values.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD126
REAL NUMBER EXPECTED
Explanation: A numeric datum of a type other than real was
written in a REAL type-statement. (FORTRAN G and H only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
DEBUG FACILITY NOT SUPPORTED
Explanation: One of the Debug Facility statements appeared
in a FORTRAN H program. These statements are allowed only
in FORTRAN G. They are diagnosed when FORTRAN H is being
checked since FORTRAN G and H use the same syntax table. If
FORTRAN E is being checked, these statements will be
diagnosed as unrecognizable or as beginning with too long a
name.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD128
INVALID CHARACTERS AFTER STOP OR PAUSE
•
Explanation: Characters other than digits, or too many digits,
follow the STOP or PAUSE in a STOP or PAUSE statement. (In
FORTRAN G and H, a literal is also permitted to follow PAUSE
and will not receive this diagnostic.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD130
REAL NUMBER OUTSIDE OF ALLOWABLE RANGE
Explanation: A real number's magnitude, taking the value of
IPOl16
EXPONENT MISSING OR INVALID
Explanation: The characters after the '0' or 'E' in a double
precision or real constant do not constitute a valid exponent.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
the exponent into account, is outside the range 1.0E-79 to 9.
(any fraction) E+ 75.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD132
IPD118
REAL CONSTANT MUST HAVE AT LEAST 1 DIGIT
In a place where a numeric constant might be
written, a decimal point was found followed by an E or 0
exponent, but there was no digit on either side of the decimal
point.
Explanation:
FORMAT STMNT NO. OR ARRAY NAME EXPECTED
In a PRINT, PUNCH, or READ statement, no
reference is made to a FORMAT statement or to an ·array
containing a FORMAT. (FORTRAN G and H only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
Explanation:
Section 18: IPD Messages - FORTRAN Syntax Checker
18-5
•
. IPD134
MISPLACED LENGTH SPECIFICATION flRECEDES
Explanation: A FUNCTION statement in which the 'FUNCTION'
is preceded by 'REAL', 'INTEGER', 'COMPLEX', or 'LOGICAL'
has a length specification between the type and 'FUNCTION'.
The length specification is invalid in that position and must be
moved to the end of the function name.
Programmer Response: Probable user error. Make corrections
as' noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD138
ARITH EXP EXPECTED AFTER RELATIONAL OP
Explanation: A relational operator in a logical expression was
not followed by a valid arithmetic expression. (FORTRAN G and
H only.)
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD140
INVALID COMMA IN DO
Explanation: An invalid comma was found after the statement
.
number in a DO statement.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD142
=
EXPECTED
Explanation: In a DO statement, in which the statement
number was followed by an invalid comma, the equal sign
expected after the DO variable was not found.
Programmer Response: Probable user error. Make corrections
as noted in the e)(planation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD144
LITERAL CONTAINS NO CHARACTERS
Explanation: The closing apostrophe of a literal constant or
literal format code occurred immediately to the right of the
opening apostrophe. (Only the literal format code is allowed in
FORTRAN E.)
Programmer Response: Probable user error. Make corrections
18-6
VS2 System Messages (VS2 Release 3.7)
as noted in the explanation and rerun the job or jobstep .
Problem Determination: Table I, items 3, 15, 22, 29.
IPD146
INVALID IF AFTER LOGICAL IF
Explanation: A statement after the IF (logical expression) part
ofa logical IF statement was recognized as an IF statement,
but was not a valid arithmetic IF statement as required.
(FORTRAN G and H only.)
Programmer Response: . Probable user error. Make corrections
as noted in the explanation and rerun the job or jobstep.
Problem Determination: Tabl,e I, items 3, 15, 22, 29.
IPD1S8
TOO MANY SUBSCRIPTS PRECEDE
Explanation: A list of eight or more (four or more in
FORTRAN E) expressions within parentheses has been found
following a symbolic name on the left side of the equal sign in
an assignment statement.
Programmer Response: Probable user error. Make corrections
as not~d in the explanation and rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPD160
'END' TOO FAR ON LINE
Explanation: The free-form END statement contains more
than 66 characters, not including trailing blanks. (This message
will not appear if the statement contains other errors.)
System Action: Processing continues.
Programmer Response: Probable user error. Make corrections
as noted in the explanation and! rerun the job or jobstep.
Problem Determination: Table I, items 3, 15, 22, 29.
IPDnnn
SYSTEM OR SYNTAX CHECKER FAILURE
(nnn = an even number from 162 through 254)
Explanation: While scanning the last statement, the syntax
checker encountered a condition that should not occur. It may
be a hardware, syntax checker, or operating system error.
Programmer Response: None.
Problem Determination: Table I, items 3, 19, 29.
Section 19: Dynamic Support System Messages (IQA)
Component Name
lOA
Program Producing Message
Dynamic Support System (DSS).
Audience and Where Produced
For programmer: master console.
Message Format
10A5nni text
5nn
Message serial number.
I
Information; no operator action is required.
text
Message text.
Associated Publications
OS!VS Dynamic Support System, GC28-0640.
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IQASOOI
DATA SETS NOT OPENED SUCCESSFULLY FOR
IQADVMOO
Explanation: The DSS utility, that runs as a step during Stage
II of system generation, could not open the SYS1.LlNKLIB or
SYSl.DSSVM data set.
System Action: The job step is terminated.
Programmer Response: Determine why the data sets were not
opened, correct the error, and rerun the job step.
Problem Determination: Table I, items 2, 3, 4, 16, 20, 29.
IQAS081
IQASI01
IQASOll
IQALANOO LOAD MODULE CSECTS NOT IN PROPER
ORDER
Explanation: The IQALANOO load module on the SYS1.LlNKLIB
data set was not link edited with the proper control
statements.
System Action: The job step is terminated.
Programmer Response: Correct the link edit control
statements, link edit the IQALANOO load module again, and
rerun the job step.
Problem Determination: Table I, items 26b, 29.
IQAS021
DSS CANCELED (INTERNAL LOGIC ERROR)
Explanation: During DSS initialization, the DSSerror exit
routine was called with no error indicated; that is, the error
exit routine cannot determine why it was called.
System Action: DSS returns control to OS/VS2.
Programmer Response: DSS software error. None.
Problem Determination: Table I, item 2, 29.
IQAS071
DSS CANCELED (PAGES UNAVAILABLE)
Explanation: DSS was canceled during initialization because
OS/VS did not have sufficient pages available to fix the DSS
control program.
System Action: The system dispatches the next ready task
and proceeds.
Programmer Response: If the user can reduce the number of
pages currently being used in the system, he should do so and
reirlVoke DSS by pressing the RESTART key.
Problem Determination: Table I, items 2, 4, 29.
DSS CANCELED (PAGING DEVICE NOT SUPPORTED)
Explanation: DSS was canceled during initialization because
the device specified for the DSS data set was not supported
by DSS.
System Action: The system dispatches the next ready task.
Programmer Response: If the programmer wants to use DSS,
he must ensure that the DSS data set (SYS1.DSSVM) is on a
supported device.
DSS CANCELED (NIP INITIALIZATION FAILED)
Explanation: During NIP processing, the DSS resource
initialization module, IEAVNPB6 was either unable to find
IQAENVOO in the LPA or unable to find SYS1.DSSVM.
System Action: DSS returned control to OS/VS2.
Programmer Response: If the programmer wants to use DSS,
he must re-IPL, making sure that IQAENVOO is in the LPA and
that SYS1.DSSVM is cataloged and available.
IQASlll
DSS CANCELED (UNABLE TO STOP CPUS)
Explanation: During initialization of DSS in multiprocessor
evnironment, DSS was unable to stop all of the CPUs.
System Action: DSS returned control to OS/VS2.
Programmer Response: If DSS cannot control .a CPU because
of a correctable condition (for example, the CPU is in the
stopped state), correct the condition.
Problem Determination: Table I, items 2, 29 or 30.
IQAS131
DSS CANCELED (NO ACCEPTABLE INTEGRATED
OPERATOR'S CONSOLE FOUND)
Explanation: DSS was unable to find an integrated operator's
console for one of the following reasons:
• None of the consoles listed in OS/VS2 module IEECUCM
are marked as integrated.
• None of the consoles marked as integrated has an I/O path
to the CPU on which system restart was issued.
• All of the consoles that are marked as integrated and have
an I/O path to the restart CPU are either allocated or
varied offline.
System Action: DSS returned control to OS/VS2.
Programmer Response: Either make sure that a console is
available to the restart CPU, or (in multiprocessing) activate
DSS on a different CPU.
Section 19: IQA Messages - Dynamic Support System
19-1
41
IQA5161
DSS CANCELED (NO DSS SAVE AREA)
Explanation: CSECT IQAIOCOO was unable to obtain a DSS
save area from CSECT IQARSSOO.
System Action: DSS returns control to OS/VS2.
Programmer Response: DSS software error. None.
19-2
VS2 System Messages (VS2 Release 3.7)
Problem Determination: Execute the AMDPRDMP service aid
program with the LPAMAP control statement to locate
IQAENVOO in the LPA. Then execute AMDPRDMP with the
PRINT STORAGE = control statement to print the contents of
IQAENVOO.
VS2.03.807
Section 20: ·System Resources Manager Messages (IRA)
Component Name
IRA
Program Producing Message
System Resources Manager.
Audience and Where Produced
For programmer: system log data set.
For operator: console.
Message Format
IRAnnnl text
nnn
Message serial number.
I
Information; no operator action is required.
text
Message text,
Associated Publications
OS/VS2 System Programming library: Initialization and Tuning Guide. GC28-0681
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IRA100I
SQA SHORTAGE
Explanation: The system has detected a shortage of virtual
system queue area.
System Action: The system ,will reject LOGON and START
commands until the shortage is relieved.
Operator Response: Report this message to the system
programmer.
Programmer Response: Occurrence of this message implies
that the default size for system queue area may be too small.
The default size may be increased by specifying the SQA
system parameter during system initialization.
IRA10ll
CRiTICAL SQA SHORTAGE
Explanation: The system has detected a critical shortage of
virtual system queue area.
System' Action: The system will reject lOGON and START
commands until the shortage is relieved. Jobs which request
more SQA than is available will be canceled.
Operator Response: I Notify the system ~programmer of this
message.
Programmer Response: Occurrence of this message implies
that the default size for system queue area may be too small.
The default size may be increased by specifying the SQA
system parameter during system initialization.
IRA1021
SQA SHORTAGE RELIEVED
Explanation: There is no longer a shortage of available
system queue area.
System Action: lOGON and START commands are again
permitted.
Operator Response: Report this message to the system
programmer.
IRA2001
AUXILIARY STORAGE SHORTAGE
Explanation: The system has detected a shortage of available
slots in the auxiliary storage paging space.
System Action: The system will reject ,LOGON, MOUNT, and
START commands until the shortage is relieged. Initiators
selecting new jobs and users with rapidly jncreasing auxiliary
storage requirements will be kept from running until the
shortage is relieved. Message IRA2031 will be issued to identify
the users with the most rapidly increasing auxiliary storage
requirements.
Operator Response: Report this message to the system
programmer.
Programme; Response: Since this message implies that the
size of the paging space may be inadequate, more auxiliary
storage should be allocated to the paging data sets during
system initialization or by using the page add facility. Examine
users of VIO and· other jobs that have heavy auxiliary storage
requirements for possible looping or extraordinary auxiliary
storage requirements.
IRA2011
CRITICAL AUXILIARY STORAGE SHORTAGE
Explanation: The system has detected a critical shortage of
available slots in the auxiliary storage paging space.
System Action: The system will reject lOGON, MOUNT, and
•
START commands until the shortage is relieved. Initiators
selecting new jobs and users with rapidly increasing auxiliary
storage requirements will be kept from running until the
shortage is relieveci. Message IRA2031 will be 'issued to identify
the users with the most rapidly increasing auxiliary storage
requirements.
Operator Response: Report this message to the system
programmer.
Programmer Response: Since this message implies that the
size of· the paging space may be inadequate, more auxiliary
storage should be allocated to the paging data sets during
system initialization or by using the page add facility. Examine
users of VIO and other jobs that have heavy auxiliary storage
requirements for possible looping or extraordinary auxiliary
storage requirements.
Section 20: IRA MeSlales - System Resources Manager
20-1
•
I
VS2.03.807
IRA2021
AUXILIARY STORAGE SHORTAGE RELIEVED
Explanation: There is no longer a shortage of auxiliary
storage slots in the auxiliary storage paging space.
System Action: LOGON, START, and MOUNT commands are
again permitted. Jobs delayed because of the shortage are
now allowed to execute.
Operator Response: Report this message to the system
programmer.
IRA203'1
nn% AUX,ILlARY STORAGE ALLOCATED TO uuu
Explanation: The system has detected a shortage of auxiliary
slots in the auxiliary storage paging space. In the message
text, uuu is the swappable user with the most rap.idly
increasing auxiliary storage requirements, and nn is the
percentage of auxiliary storage allocated to uuu.
System Action: User uuu will be swapped out until either the
shortage is relieved or there are no swappable users left in
storage.
Operator Response: Report this message to the system
programmer.
Programmer Response: Examine the validity of user uuu, and
determine whether or not he should continue.
IRA3001
IRA3001
IPS MEMBER mem INPUT ERROR NEAR COLUMN
nnn. TEXT FOLLOWS:
text
Explanation: The input scan of
IPS (installation performance specification) parameters in the
indicated member determined that a syntax error or parameter
value error exists in the specification. The input text location at
which the error was 'detected is displayed by the message. If a
parameter with multiple subparameters is in error, it is possible
that an error message may appear for each subparameter. The
syntax scan continues even after an error' had been detected,
and may produce additional error messages for the same .
specification, lbased on the rejection of the parameter
pre\'liously found to be in error.
System Action: The IPS parameter is not accepted. The
message is written to the system log data set.
Operator Response: Report this message to the system
programmer.
Programmer Response: Correct the errors in the IPS.
IRA4001
PA~EAB[E: ~TORAGE SHORTAGE
Explanation: The system has detected a shortage of pageable
real storage frames.
System Action: LOGON, MOUNT, and START commands will
be rejected, and initiators selecting new jobs will be kept from
running until the shortage is relieved. The current in-storage
user with the greatest number of fixed frames will be swapped
out. The user will remain swapped out until the shortage is
relieved and until there are sufficient frames available to
satisfy his current requirements. Message IRA4031 will be
issued identifying the heavy fixed page user.
Operator Response: Report the message to the system
programmer.
Programmer Response: Examine users of V= R storage and
other jobs that have heavy page fix requirements. for possible
looping or for extraordinary page fix needs.
IRA4011
CRITICAL PAGEABLE STORAGE SHORTAGE
Explanation: The system has detected a critical shortage of
pageable real storage frames.
System Action: LOGON, MOUNT, and START commands will
be rejected, and initiators selecting new jobs will be kept from
running until the shortage is relieved. The current in-storage
user with the greatest number of fixed frames will be swapped
out. The user will remain swapped out until the shortage is
relieved and until there are sufficient frames available to
satisfy his current requirements. Message IRA4031 will be
issued identifying the heavy fixed page user.
operator Response: Report the message to the system
programmer.
Programmer Response: Examine users of V = R storage and
other jobs that have heavy page fix requirements for possible
looping or for extraordinary page fix needs.
In the latter case, it may be necessary to adjust the RSM
constants PVTPEROK (the acceptable fixed frame threshhold
percentage) and PVTPERFX (the maximum fixed frame
thresh hold percentage). These constants are explained in
OS/VS2 System Programming Library: Initialization and Tuning
Guide.
IRA4021
PAGEABLE STORAGE SHORTAGE RELIEVED
Explanation: There is no longer a shortage of pageable real
storage frames.
IRA3011
IPS MEMBER mem MISSING
WORKLOAD LEVELS
REQUIRED PERF GRP nnn
PERF GRP nnn DURATION
System Action: LOGON, MOUNT, and START commands are
again permitted. Jobs delayed because of the shortage are
now allowed to execute. The heavy users of fixed frames that
were swapped will not be allowed to execute until there are
sufficient frames to satisfy their requirements.
Operator Re~nse: Report this message to the system
programmer.
PERF GRP nnn OBJECTIVE
IRA4031
DOMAINS IN FIRST PER OF PERF GRPS
.DOMAIN nnn CO,.~:rRAINT VALUE(S)
Explanation: The input scan of IPS (installation performance
specification) parameters in the indicated member determined
that a required par.ameter is missing from this specification.
The parameter, identified by the message text, either was not
specified, or was specified with input errors.
System Action: The IPS is not accepted; The message is
written to the system log data set.
Operator Response: Report this message to the system
programmer.
Programmer Response: Correct the errors in the IPS.
20-2
VS2 System Messages (VS2.03.807)
uuu - HEAVY FIXED PAGE USER
Explanation: The system has determined that at the time of a
pageable storage shortage, user uuu was the largest user of
fixed frames.
System Action: User uuu is swapped out and 'will not be
allowed to execute until the shortage is relieved, and until
there are sufficient frames available to satisfy his current
requirements.
Operator Response: Report this message to the system
programmer.
Programmer Response: Examine the validity of user uuu, and
determine whether or not he should continue.
The operator may quiesce other system activity and .allow user
uuu to be swapped in again. Once he is swapped in, user uuu
may be allowed to run to completion or may be canceled by
the operator.
Section 21: MF /1 Messages (IRB)
Component Name
IRB
Program Producing Message
MF/1
Audience and Where Produced
For operator: console.
For programmer: dynamically allocated SYSOUT data set and system message data set.
Message Format
IRBnnns text
nnn
Message serial number, which is coded to indicate condition which caused message:
Normal operational messages.
1xx Error messages associated with the control functions of M F/1.
2xx Error and conversational messages associated with the initialization of
3xx MF/1.
Error
messages associated with the formatting and writing of reports.
4xx s
Type code:
Action; operator must perform a specific action.
A
Decision; operator must choose an alternative.
D
Eventual action; operator must perform action when he has time.
E
Information; no operator action is required.
I
text
Message text.
Associated Publications
OS/VS2 System Programming Library: Initialization and Tuning Guide, GC2S-0SS1.
Problem Determination
Refer to Tables I and " at the back of this publication for problem determination instructions.
IRBI001
MF/1 IS ACTIVE
Explanation: MF/1 has been initialized and data is being
collected to form the first report/SMF record entry.
System Action: Performance and storage overhead will
increase according to the options selected.
Operator Response: None.
Operator Response: STOP or CANCEL the previous invocation
of MF/1 if desired, and reinvoke.
IRB2011
MF/1 TASK REINSTATED
j Ucde l
lScde ~
appears only if REPORT(REAlTIME) was specified as an input.
System Action: A report is formatted and written to SYSOUT
storage. The reports for this period will be printed according to
MF/1 priority and output class.
Operator Response: Start a writer to the MF/1 SYSOUT class
if printing of the report is desired.
Explanation: A catastrophic error in MF/1 was detected by
MF/1 or by another system component which was providing a
service for MF /1. Ucde is the user completion code and Scde
is the system completion code.
System Action: The resulting ABEND was intercepted by the
MF/1 recovery routines and the task was successfully
reinstated. Data being collected for the current reporting
interval was lost and data collection for the new interval has
been started.
Operator Response: None.
IRBI021
IRB2021
IRBI01l
MF /1 REPORT AVAILABLE FOR PRINTING
Explanation: A reporting interval has ended. This message
MF /1 TERMINATED
Explanation: MF/1 has terminated.
System Action: Performance and storage overheads are now
back to normal.
Operator Response: None.
IRBI031
MF/1 OPTIONS IN EFFECT
Explanation: All of the MF /1 options in effect following the
input merge are listed, one per line, in the keyword(value)
format.
System Action: Processing continues.
Programmer Response: None.
IRB2001
MF /1 IS ALREADY ACTIVE
Explanation: MF/1 is already active from a previous
invocation.
System Action: This invocation of MF/1 is ignored and the
request is terminated.
NO MF /1 MEASUREMENTS SELECTED
Explanation: The input options do not specify any
measurements to be made, reported, or recorded by MF/1.
System Action: MF/1 terminates.
Operator Response: Restart MF/1, supplying valid input
options which activate at least one MF/1 measurement.
Programmer Response: Provide valid MF/1 input options in
the library data set or in the EXEC statement PARM field which
activate at least one MF/1 measurement.
IRB3001
MF /1 SYNTAX ERROR IN OR FOLLOWING TEXT
BEGINNING xxx IN
[1~:~~ATOR1]
INPUT
LIBRARY
REPLY
Explanation: The syntax scan of control input parameters
determined that one or more errors existed in the text
beginning with xxx in the source indicated.
System Action: If the error was in PARM, LIBRARY, or REPLY
Section 21: IRB Messages - MF/1
21:-1
•
input, the valid parameters in that source will be accepted and
the rest ignored. Message IRB3091 is issued to list the optinos
accepted and the OPTIONS keyword is forced to allow the
operator to examine and/or change the options at the
completion of the input merge. The input merge and
initialization continues.
If the error was in START command syntax, (operator input),
message IRB30aD will follow.
Operator Response: If the error was in the START command
PARM field (operator input), reply to message IRB30aD, .which
follows.
If the error was detected in a previous reply, examine the list
of options assumed as listed by message IRB3091. If these
options are incorrect or incomplete, reply later to message
IRB306D to change the options.
Programmer Response: If the error was in PARM or LIBRARY
input, correct the input before the next execution of MF/1.
IRB3011
INVALID VALUES OR MUTUALLY EXCLUSIVE
OPTIONS APPEAR IN MF /1[i~::~ATOR1] INPUT
LIBRARY
REPLY
Explanation: Invalid values or mutually exclusive keywords
appear in the indicated source. If a specific source
(OPERATOR, PARM, LIBRARY, or REPLY) appears, then
mutually exclusive values of a single keyword have been
detected in that source, or one or more keyword values were
found to be out of the acceptable range.
If no specific source appears, upon completion of the merge of
all input sources, mutually exclusive values of different
keywords were detected.
System Action: If the source is PARM, LIBRARY, or REPLY
input, MF/1 ignores the first mutually exclusive parameter and
accepts the second. Values in error are modified and the
merge and initialization continues. MF/1 will force the
OPTIONS keyword to allow the· operator to examine or change
the modified values.
If the source is the START command PARM field (operator
input), message IRB30aD will follow.
If no source appears, MF/1 will modify the values in error and
force the OPTIONS keyWord to allow the operator to examine
or change the modified values.
Operator Response: If the error is in the START PARM field
(operator input), reply to message IRB30aD which follows.
If the error was detected in a previous reply, examine the list
of options assumed as listed by message IRB306D. If these
options are incorrect or incomplete, reply later to message
IRB306D to change the options.
Programmer Response: If the source is PARM or LIBRARY
input, correct the errors before the next execution of MF /1.
IRB3021
MEMBER IRBMFlnn NOT FOUND IN THE MF /1
LIBRARY
Explanation: Member name IRBMF1nn was generated as a
default or by recognition of MEMBER(nn) in the MF /1 input
stream. A member by this name does not exist in the library
21-2
VS2 System Messages (VS2 Release 3.7)
data set specified by the IEFRDER DO card. nn is the member
number specified in the control input as MEMBER(nn).
System Action: The library is ignored as a source of control
input. The input merge and initialization continues.
The OPTIONS keyword will Qe forced to allow the operator to
examine and/or change the MF/1 options upon completion of
the merge.
Operator Response: Examine the parameters following
message IRB30S1 when it appears and reply to message
IRB306D to modify any parameter chosen by the system
during the input merge.
Programmer Response: Create a member with the name
IRBMFlnn, if 'desired.
IRB3031
MEMBER KEYWORD SPECIFIED IN MF /1 LIBRARY
MEMBER IRBMFlnn
Explanation: The member keyword MEMBER(nn) appears in
the indicated library member. nn is the decimal field.
System Action: The member keyword in the library source is
ignored. The OPTIONS keyword will be forced to allow the
operator to examine and/or change the MF /1 options upon
completion of the merge.
Programmer Response: Delete the member keyword in the
indicated library member.
IRB3041
I/O ERROR WHILE PROCESSING MF /1 LIBRARY
DATA SET. [THE
SYNAD TEXT FOLLOWS. synad text]
Explanation: During MF/1 initialization, an uncorrectable I/O
error or OPEN error occurred while reading or searching for
the specified member in the MF/l library. The SYNAD text will
not appear if the error occurred while opening the data set or
finding a member.
System Action: The control input source is ignored and
processing continues with the input parameter merge and
initialization. The OPTIONS keyword is forced to allow the
operator to examine the options chosen by the system.
Operator Response: Examine the parameters following
message IRB30S1 when it appears and reply to message
IRB306D to modify any parameter chosen by the system
during the input merge.
Programmer Response: Recreate the library data set before
the next execution of MF/1.
Problem Determination: Table I, item 30.
IRB3051
MF /1 PARAMETERS
Explanation: This message is issued if a list of options was
desired upon completion of the input parameter merge. All of
the keyword parameters are listed following this message, one
parameter to· a line in the format keyword(value). Message
IRB306D follows, permitting changes to be made.
System Action: MF /1 initialization will not continue until the
operator has responded to message IRB306D.
Operator Response: Respond to message IRB306D.
IRB306D
REPLY WITH MF /1 VALUES OR GO
Explanation: This message follows message IRB3051 and
permits changes to be made in the parameters listed.
System Action: MF/l initialization will not continue until the
operator has responded to this message.
If the operator responds with new control parameters, only
those parameters will be changed. The system will reissue
message IRB306D repeatedly, allowing additional changes,
until the operator responds with GO.
If a syntax error, mutually exclusive values, or invalid values
are detected in the reply, message IRB3001 or message
IRB3011 and message IRB3091 will follow.
If the MEMBER(nn) or OPTIONS keywords are specified,
special processing occurs. MEMBER(nn) is ignored because at
this time the input option merge is complete and a particular
library member would have already been used. If OPTIONS is
specified, the MF /1 options will be listed following a
subsequent reply of 'GO'. Note that a syntax error, mutually
exclusive options, or invalid values in the reply will force the
OPTIONS keyword.
Operator Response: If changes are to be made, enter REPLY
xx,'keyword(value),keyword(value), .. .'. If changes are not to be
made, enter REPLY xx,'GO'.
IRB308D
\,\
RESPECIFY MF /1 OPTIONS OR REPLY IGNORE
Explanation: This message is issued if a syntax error, mutually
exclusive options, or invalid values were detected in the
operator START command input.
System Action: MF /1 initialization will not continue until the
operator has successfully responded to message IRB30aD.
Operator Response: Respecify the entire START command
option input in the form REPLY
xx,'keyword(value),keyword(value), .. .', or reply 'IGNORE'. If the
reply is IGNORE, MF/1 will assume that no options were
specified in the START command.
IRB3091
MF /1 OPTIONS ASSUMED FROM SOURCE IN
ERROR:
Explanation: This message follows messages IRB3001 and
IRB301l. It lists the options which MF/l was able to recognize
from the EXEC, LIBRARY, or REPLY source which contained
syntax errors, mutually exclusive options, or invalid values.
System Action: All of the keyword parameters assumed are
listed following this message, one keyword to a line in the
format keyword(value).
Operator Response: Examine the options assumed. If they are
incorrect or incomplete, reply later to message IRB306D to
change or add options.
Programmer Response: . If the source was the EXEC card or
LIBRARY data set, correct the source in error before the next
execution of MF/1.
IRB4001
I/O ERROR ON MF /1 WRITE. THE SYNAD TEXT
FOLLOWS.
Synad text
Explanation: An uncorrectable I/O error occurred while writing
to a report SYSOUT data set.
System Action: No further writes will be issued to the data
set. One retry will be performed by unallocating the data set
and allocating a new one. If the retry is successful, MF/1
continues with no data loss. If the retry is unsuccessful, MFII
continues, but the reports for this MF/1 interval are not
completed.
IRB4011
MF /1 REPORT SUBTASK FOR INTERVAL BEGINNING
hh.mm.ss
REINSTATED j Ucde
1 Scde ~
t
Explanation: An error was detected while formatting and
writing a report to a SYSOUT data set. hh:mm:ss is the
beginning of the report interval, Ucde is the user completion
code and Scde is the system completion code.
System Action: The data being processed is presumed intact.
The report subtask is reinitialized. The old data set is closed, a
new one is reallocated, opened, and the report will be written
to the new SYSOUT data set.
If a second error occurs, the subtask is terminated.
Programmer Response: Examine the dump provided and take
the action appropriate for the original completion code causing
the reinstatement.
IRB4021
MF /1 REPORT SUBTASK FOR INTERVAL BEGINNING
hh.mm.ss
ABENDEDj Ucde l
1Scde f
Explanation: An MF/1 subtask which was formatting data and
writing records to a SYSOUT data set abnormally terminated
with the completion code cde. hb:mm:ss is the time of the
beginning of the report interval, Ucde is the user completion
code and Scde is the system completion code.
System Action: MF/1 continues. The reports for data
collected for this interval are not completed. The SMF records
for this interval are written if the RECORD option is in effect.
They contain the data measurements collected for this interval.
Programmer Response: Take the appropriate action related to
the completion code.
•
Section 21: IRB Messages - MF /1
21-3
21-4
VS2 System Messages (VS2 Release 3.7)
YS2.03.801
Section 22: Virtual Telecommunications Access Method Messages (1ST)
Component Name
1ST
Program Producing Message
VTAM (Virtual Telecommunications Access Method).
Audience and Where Produced
For operator: console.
For programmer: console or SYSPRINT data set.
Message Format
ISTnnns text
nnn
Message serial number.
s
Type code:
A
Action; operator must perform a specific action.
I
Information; no operator action is require.9.
text
Message text.
Associated Publications
VTAM Macro Language Beference, GC27-6995
OS/VS2 System Programming Library: VTAM, GC28-0688
Operator's Library: VT AM Network Operating Procedures, GC27 -6997OS!VS VTAM Logic, SY28-0621
Problem Determination
Refer to Tables I and II at the back of this publication for problem determination instructions.
IST0011 VTAM START REJECTED- PAGE FIX FAILED
Explanation: VTAM initialization is terminated due to a failure
attempting to fix a page in storage.
System Action: The VT AM START command fails and VTAM
initialization terminates.
Operator Response: Retry the VTAM START command. If the
problem persists, follow the problem determination action.
Problem Determination: Table I, items 2, 29.
IST0021
xxxxxxxx IS AN INVALID START PARM - ALL
PARMS IGNORED
Explanation: An invalid START parameter keyword was entered
by the operator. Only the default START parameter list
ATCSTROO has been processed.
System Action: All the START parameters entered from the
console are ignored by VTAM. The operator will be reprompted
to enter valid START parameters.
Operator Response: Reenter all the START parameters
(correcting the invalid one) when prompted. If the LIST
keyword is entered, it will be processed prior to the other
keywords. If no START parameters are reentered, those
contained in ATCSTROO remain in effect.
IST0031
ABEND OCCURRED DURING NETWORK DEFINITION
OF CONFIG xxxxxxxx
Explanation: The VTAM network definition subtask has
abnormally terminated. Network definition is invoked either
during VTAM start processing to process the CON FIG keyword
or as a result of a VARY command.
System Action: The subtask is reinstated.
Operator Response: none
IST0061
VTAM START REJECTED - GETMAIN FAILED
• Respecify the value of the system parameter name CSA
• Reissue the START command.
Caution: Increasing the size of CSA reduces the size of each
address space's private area, possibly causing other jobs to
fail for lack of storage.
IST0091
VTAM IS ALREADY ACTIVE - START REJECTED
Explanation: VTAM is already active in the system. Therefore
the attempt to start VTAM again has been rejected.
System Action: The VTAM program that is running issues an
EOJ to terminate the invalid START command.
Operator Response: Probable user error. If you wish to start
VTAM again, first terminate the VT AM system that is already
running by issuing the network operator HALT NET command.
IST0101
xxxxxxxx COMMAND INVALID
Explanation: A VTAM command with the verb xxxxxxxx has
failed because of incorrect command format.
System Action: The command is ignored.
Programmer Response: None.
Operator Response: Reenter the command, using the correct
format.
IST0121
VTAM START REJECTED - CANNOT LOCATEmem
Explanation: VTAM initialization is terminated because the
member mem could not be found.
System Action: The VTAM START command fails and VTAM
initialization terminates. System continues processing.
Operator Response: Before attempting to restart VT AM, ensure
that the member is in the proper library.
Programme; Response: Probable user error. Check that the
proper cataloged procedure has been specified and that the
correct member (mem) is identified in the procedure.
Explanation: A request for storage failed during VTAM
\."
.,
initialization.
System Action: The VTAM START command is rejected .
System continues processing.
Operator Response: With the concurrence of your system
programmer:
• Re-IPL the system
IST0131
VTAM START REJECTED - I/O ERROR FOR mem IN
dsn
Explanation: VTAM initialization issued a BLDL macro
instruction for member mem in data set dsn and encountered
an I/O error.
System Action: VTAM initialization terminates. System
Section 22: 1ST Messages - VTAM 22-1
•
YS2.03.801
continues processing.
Operator Response: Probable hardware .error. Reissue the
VTAM START command with alternate devices and/or .volumes.
Problem Determination: Table I, items 2, 18, 30.
IST015A
ERROR PROCESSING LIST IDENTIFIER - ENTER LIST
10 OR BLANK
Explanation: VTAM detected an error when reading an
I
ATCSTRxx member of SYS1.VTAMLST.
System Action: VTAM initialization waits for the operator to
reply. If a list identifier is entered, VTAM attempts to read the
corresponding data set from SYS l.VTAM LST; if a blank is
entered, VTAM uses the default parameters (containe~ in
ATCSTROO, the default member), and any additional or
alternate parameters specified by the operator in response to
a previous request for parameters for the START command.
Operator Response: Enter the list identifier specified by your
installation (one or two characters) or enter a blank to use the
default sequence.
Programmer Response: Check that the identifier to be used is
valid and has been correctly communicated to the network
operator, or instruct the operator to respond with the default
sequence.
IST0161
VTAM START REJECTED - STAE FAILED
Explanation: A failure occurred during VTAM initialization when
trying to establish an error recovery environment. The failure is
due to one of the following:
• The STAE processing could not obtain storage for a STAE
control block.
• The STAE processing found invalid parameters.
System Action: The VTAM START command is rejected.
System continues processing.
Programmer Response: With the concurrence of your system
programmer:
• Re-IPL the system
• Respecify the value of the system parameter name CSA
• Reissue the START command.
Caution: Increasing the size of CSA reduces the size of each
address space's private area, possibly causing other jobs to
fail for lack of storage.
Problem Determination: Table I, items 2, 29.
IST0181
CON FIG COULD NOT BE INITIALIZED - VTAM START
CONTINUES
i~
Explanation: VTAM initialization is unable to initialize the
network to the configuration specified by the CON FIG
parameter in the VTAM START command because of an error
in member of the SYS1.VTAMLST data set.
System Action: VTAM initialization continues, but the
predefined network configuration is not activated.
Operator Response: To allow the network to be used while the
problem is being found, parts (or all) of the network may be
activated by using the network operator VARY NET command.
Programmer Response: Inspect and correct the member of the
SYS1.VTAMLST data set that is specified by the CONFIG
parameter. The network operator can then activate the entire
configuration by stopping and restarting VT AM.
IST0191
SYNTAX ERROR IN START OPTION: keywd - ENTER
WHEN PROMPTED
Explanation: A syntax error was encountered in the parameters
of the START command; keywd represents the keyword in
error.
System Action: The parameters that precede the syntax error
are processed. VTAM suspends further processing of the
22-2
VS2 System Messages (VS2.03.801)
parameters and prompts the operator for correct input by
issuing message IST125A.
Operator Response: Reenter all parameters following the last
valid one when prompted by message IST125A, or specify
default values by entering a blank.
IST0201
VTAM INITIALIZATION COMPLETE
Explanation: Initialization of VTAM is complete.
System Action: System continues processing.
Operator Response: You can now enter VTAM network
commands and/or start any VTAM application programs.
IST0251
BLDL FAILED FOR mem
Explanation: VTAM issued a BLDL that failed for member mem
on either SYS1.VTAMLIB or SYS1.LPALIB.
System Action: If member mem is critical to VTAM, another
message will be issued. Otherwise, VTAM continues processing.
Programmer Response: If mem does not exist and is needed,
add it to the appropriate library and restart VT AM.
IST0321
cm FAILED - FIRST CHARACTER OF keywd NOT
ALPHABETIC
Explanation: The command failed because the first character
of the specified keyword parameter value must be alphabetic.
System Action: The command is rejected. The system
continues processing.
Operator Response: Correct the parameter and reenter the
command.
IST0331
cm COMMAND CANCELED
I Explanation:
The specified command has been canceled
because an unexpected event occurred during command
processing. The cm command could be MODIFY, DISPLAY,
VARY, or HALT. One of the following has occurred:
• Recoverable machine checks.
• Resource unavailable; for example, lack of main storage.
• Recoverable program checks.
System Action: System continues processing. The command is
not executed.
Operator Response: Reenter command. If message persists,
follow the problem determination action.
Problem Determination: Table I, items 2, 18, 30.
IST0371
cm FAILED - SYNTAX ERROR
I Explanation:
The specified command does not have the
expected delimiters or punctuation, or has a parameter that
exceeds eight characters in length.
System Action: System continues processing. The command is
not executed.
Operator Response: Probable user error. Reenter command
with the correct format.
IST0381
cm FAILED - keywd NOT NUMERIC
I Explanation:
The specified command expects but did not find a
numeric value in keyword keywd.
System Action: System continues processing. The command is
not executed.
Operator Response: Probable user error. Reenter command
with the correct value.
IST0391
cm FAILED - UNIDENTIFIABLE KEYWORD
I Explanation:
The specified command contains an invalid
keyword parameter.
System Action: System continues processing. The command is
not executed.
VS2.03.801
Operator Response: Probable user error. Reenter command
with correct parameters.
IST0401
START PARAMETER SSCPID NOT PROCESSED REENTER WHEN PROMPTED
Explanation: No SSCPID START parameter has been made
available to VTAM. Since the SSCPID is required to continue
with VTAM initialization and it is not defaulted, specify the
SSCPID when prompted. The SSCPID START parameter assigns
an identification number to VTAM for its use in communicating
with various SNA terminals in the network.
System Action: The system continues processing. VTAM will
prompt the operator for additions or corrections to VTAM
START parameters.
Operator Response: When prompted, supply SSCPID as one of
the START parameters. Specify the SSCPID in the form of
SSCPID == n, with n as a decimal value between 0 and 85535.
IST041I
PPBUF SIZE TOO SMALL - 10BUF SIZE USED
Explanation: The buffer size specified or defaulted on the
PPBUF parameter oH:he START command was less than the
size of buffer pool IOBUF.
System Action: The size of buffer pool 10BUF is used. VTAM
initialization continues.
Programmer Response: Probable user error. The size of the
PPBUF buffer pool must be equal to or greater than the 10BUF
buffer pool size. Increase the PPBUF size on the START
command to equal the size of the 10BUF buffer pool.
IST0421
·cm FAILED - TOO MANY OPERANDS
Explanation: The specified command has more operands than
are allowed.
System Action: System continues processing. The command is
not executed.
Operator Response: Probable user error. Reenter command
with the correct number of operands.
Operator Response: If the threshold value required is higher
than the default value, specify the required number in the
START command. This number must not exceed the number of
buffers (bno) specified.
IST047I
BUFFER SIZE TOO SMALL - DEFAULT VALUE USED
I Explanation:
The buffer size (bsz) specified in the buffer
keyword of the START command is less than the default value
established for VTAM buffer pools at VTAM definition.
System Action: The default value for a minimum configuration
is used. Initialization continl,Jes.
Operator Response: The buffer sizes cannot be set lower than
the IBM default.
IST0481
VTAM START REJECTED - INSUFFICIENT STORAGE
FOR BUFFERS
Explanation: VTAM initialization is terminated because
sufficient storage is not available to establish the buffer pools
required by VTAM.
System Action: The VTAM START command fails and VTAM
initialization terminates. System continues processing.
Operator Response: Check that sufficient storage is made
available before restarting VTAM.
Programmer Response: With the concurrence of your system
programmer:
• Re-IPL the system
• Respecify the value of the system parameter name CSA
• Reissue the START command.
See "Tuning VTAM" in (OS/VS2 System Programming Library:
VTAM).
Caution: Increasing the size of CSA reduces the size of each
address space's private area, possibly causing other jobs to
fail for lack of storage.
IST0491
VTAM START REJECTED - OPEN FOR VTAM ACB
FAILED
E.xplanation: VTAM initialization is terminated because an
IST0431
cm KEYWORD VALUE INVALID: op
Explanation: The specified command has a keyword parameter
value that is specified incorrectly; op is the incorrect operand.
System Action: System continues processing. The command is
not executed.
Operator Response: Probable user error. Reenter command
with the correct keyword value.
IST044I
attempt to open the VTAM access method control block (ACB)
failed.
System Action: The VTAM START command fails and VTAM
initialization terminates. System continues processing.
Operator Response: Retry the START command.
Problem Determination: Table I, items I, 29.
IST0501
cm FAILED - INSUFFICIENT STORAGE
I command cannot
The command processor for the specified
obtain sufficient· storage for a work area.
Explanation:
System Action: System continues processing. The command is
not executed.
Operator Response: Free storage if possible by entering a
VARY NET,INACT command to deactivate some nodes, and
reenter the command. Or, wait for a short period until any
outstanding VTAM commands have completed processing, and
then reenter the command.
Programmer Response: This message indicates that'storage
requirements for VTAM were underestimated. Check storage
estimates and increase storage allocation where possible.
VTAM START REJECTED - CANNOT OPEN VTAM
DATA SET SYS1.VTAMLxx
Explanation: An attempt to open VTAM data set
SYS1.VTAMLIB or SYS1.VTAMLST was unsuccessful.
SYS1.VTAMLIB andSYS1.VTAMLST are required to continue
proce~ing.
System Action: The VTAM START command fails and VTAM
initialization terminates. System continues processing.
Operator Response: Probable user error. Review system
definition and VTAM definition output, and verify VTAM data
set construction and allocation. When the error condition has
been corrected, restart VTAM.
IST051A
ENTER VTAM START PARAMETERS
Explanation: VTAM is prompting the operator to enter
IST0461
THRESHOLD NUMBER EXCEEDS BUFFER NUMBER DEFAULT VALUE USED
Explanation: The threshold number (bth) specified in the buffer
keyword of the START command is greater than the number of
buffers (bno) specified.
System Action: The default value for a minimum configuration
is used. Initialization continues.
parameters for the START command. He can override the
default parameters stored in a member of SYS1.VTAMLST
(ATCSTRxx) or provide additional parameters.
System Action: VTAM processes the parameters entered in
reply to the prompt.
Operator Response: Either enter the parameters recommended
by the system programmer or contained in your installation
Section 22: 1ST Mella••• - VTAM 22-3
•
VS2.03.801
I
instructions, or enter a blank to indicate that the default
parameters are to be used.
CAUTION: A misspelled LIST keyword is ignored without an
opportunity to correct it.
Programmer Response: If the default parameters are
unsuitable for your purposes, select the parameters required
for. the START command and prepare instructions for their use
by the network operator.
IST0521
keywdlS AN INVALID START PARAMETER
KEYWORD - IGNORED
Explanation: The keyword keywd is· not a valid parameter for
the START command.
System Action: VTAM ignores the keyword. Other keywords of
the START command are processed.
Operator Response: Probable user error. When prompted by
message IST125A, enter the correct keyword and parameters
or enter a blank to indicate that no parameters are to be
entered.
IST0531
NETSOL = opt IS AN INVALID START OPTION PARAMETER IGNORED
Explanation: VT AM initialization encountered an invalid option,
opt, for the NETSOL parameter of the START command. YES
and NO are the only valid options.
System Action: VTAM initialization rejects the NETSOL
keyword but continue.s processing other parameters of the
START command.
Operator Response: Probable user error. Enter the correct
NETSOL option (either YES or NO) or enter a blank to default
to NO when prompted by message IST125A.
IST0541
keywd KEYWORD SEQUENCE ERROR IN START
PARMS - 10 IGNORED
Explanation: The keyword keywd was detected among the
parameters of the START command, but it was not preceded
by a TRACE or NOTRACE keyword as required. keywd can be
10 or TYPE, and must follow either TRACE or NOTRACE.
System Action: VTAM ignores the keyword and continues
processing the other parameters.
Operator Response: Probable user error. Determine the correct
keyword sequence, and enter your selection when next
prompted by message IST125A.
IST0551
xx IS AN INVALID CONFIGURATION 10 PARAMETER IGNORED
Explanation: An invalid configuration identifier xx was entered
I
in the CON FIG parameter of the START command. Either the
identifier does not have a corresponding member in
SYS1.VTAMLST, or is more than two characters in length. (If
more than three characters were entered, only the first three
are printed in the message.)
System Action: VTAM initialization processes the remaining
parameters before it prompts the operator for correct input.
Operator Response: Determine the correct identifier for your
installation, and reenter the parameter when prompted by
message IST125A..
IST056A
LIST
= xx IS INVALID - ENTER LIST 10 OR BLANK
Explanation: The list identifier, xx, specified for the LIST
parameter in the START command is invalid. Either the
identifier does not have a corresponding member in
SYSl.VTAMLST, or is more than two characters in length. (If
more. than three characters were entered, only the first three
are printed in the message.)
I
System Action: The LIST parameter is not processed. VTAM
waits for a reply to this message. If an identifier is entered,
VTAM attempts to process the parameters in the
corresponding member of SYSl.VTAMLST. If a default list is
selected, the operator is prompted to enter individual
parameters.
Operator Response: Enter a valid two character list identifier,
or enter a blank to invoke the d~fault. If the default list is
invoked, enter the desired parameters (excluding LIST == id,
which if entered, is ignored) when prompted by message
IST125A.
IST0571
KEYWORD MISSING AFTER TRACE/NOTRACE
OPTION ON START COMMAND
Explanation: A required keyword did not follow the TRACE or
NOTRACE option in the START command. Applicable keywords
are 10 = andTYPE - .
System Action: VTAM initialization does not process the
TRACE or NOTRACE parameter but continues to process the
remaining parameters on the START command.
Operator Response: Probable user error. Enter correct trace
parameters when prompted by message IST125A,or invoke
the default by entering a blank.
IST0581
keywd WILL NOT BE PROCESSED - INVALID START
PARAMETER
Explanation: The keyword represented by keywd in the START
command is not a valid keyword for the requested trace
function.
System Action: VTAM initialization does not process the
preceding TRACE or NOTRACE parameter but continues to
process any remaining parameters.
Operator Response: Probable user error. When next prompted
by message IST125A, either enter the correct trace
parameters, or invoke the default by entering a blank.
IST0591
TRACE/NOTRACE FOR 10 = xxx IGNORED INSUFFICIENT STORAGE
Explanation: The specified TRACE/NOTRACE option for node
xxx was not processed due to a failure to obtain· sufficient
storage.
System Action: The TRACE/NOTRACE option is ignored.
Remaining parameters are processed.
Operator Response: If the TRACE or NOTRACE option for the
specified node is essential, the system will have to be
restarted with a larger CSA.
Programmer Response: Increase the size of CSA if the TRACE
option is desired. Verify with system programmer if an increase
in CSA is feasible with the use of the TRACE option.
IST0601
VARY FAILED - LOGON
= xxx
UNKNOWN TO VTAM
Explanation: A VARY NET command was entered with the
LOGON option, but the application program identifier, xxx, is
not defined to VTAM. A null name, consisting only of blanks, is
also an invalid identifier.
System Action: Processing of the command is terminated.
SYstem status is unchanged.
Operator Response: Probable user error. Reenter the command
after the identifier is validated.
Programmer Response: Check the validity of the identifier and,
if necessary, correct the identifier or change the VTAM
definition to validate the command when reentered.
IST0611
VARY FAILED - 10 = xxx UNKNOWN TO VTAM
Explanation: A VARY NET command was entered but the
identifier or node name represented by xxx is not defined to
22-4
VS2 System Messages (VS2.03.801)
VS2.03.801
VTAM.
System Action: Processing of the command is terminated.
System status is unchanged.
Operator Response: Probable user error. Check the spelling of
the name, and reenter the command when the identifier is
validated.
Programmer Response: Check the validity of the identifier and,
if necessary, correct the identifier or change the VTAM
definition to validate the command when reentered.
VARY FAILED - LOGON = xxx IS NOT AN
APPLICATION
Explanation: A VARY NET command with the LOGON option
was entered, but the name represented by xxx is not an active
VTAM application program.
System Action: Processing of the command is terminated.
System status is unchanged.
Operator Response: Probable user error. Check that you have
entered the application program name correctly. If this is not
the cause of failure, check that the major node to which the
application program belongs has been activated. Then reenter
the VARY NET command.
I
I
IST0621
IST063I
IST0691
network control program xxx, an OPNDST macro instruction
was attempted on the communications controller that is
associated with the network control program., However, the
VTAM OPNDST failed.
System Action: Processing of the command is terminated.
System status is unchanged.
Operator Response: Retry the VARY NET,ACT command.
Problem Determination: Table I, items 2, 16, 18,' 29.
I
VARY FAILED - LOGON NAME NOT SPECIFIED
LOGON option, but a name was not supplied with the option.
System Action: Processing of the command is termina~ed.
System status is unchanged.
.
Operator Response: Probable user error. Reenter command
with a valid VTAM application program name.
'.
IST0701
VARY FAILED - TOO MANY OPERANDS
Explanation: A VARY NET command has been enter~d with too
many operands.
System Action: Process~ng of the command is terminated.
System status is unchanged.
Operator Response: Probable user error. Reenter command
with the correct number of operands.
IST0661
I
The specified command was entered with an
invalid operand.
System Action: Processing of the command is terminated.
System status is unchanged.
Operator Response: Probable user error. Reenter the command
with a valid operand.
IST0681
because the node type specified in the message is not
supported by the display processor routine.
System Action: The DISPLAY command is rejected.
Operator Response: Consult VTAM Network Operating
Procedures (GC27-0027) to determine the node types
supported by the display command processor.
VARY FAILED - xxx NODE ALREADY ACTIVE
SYSTEM ALLOCATION FOR NODE xxx
UNSUCCESSFUL
Explanation: During the processing of' a VARY NET command
to activate a higher-level node, the command attempted to
activate the associated subordinate nodes. Subordinate node
xxx could not be activated for one of the following reasons:
• The node is allocated to a program other than VTAM.
• The node has been associated with the wrong channel unit
address.
DISPLAY FAILED - NODETYPE OF xxxxxxxx NOT
SUPPORTED
Explanation: A DISPLAY command cannot be completed
Explanation: . A VARY NET command attempted to activate
node xxx and found that it was already active.
System Action: The command is ignored. System continues
processing.
Operator Response: Probable user error. Verify that the node
specified was the node you intended to activate. If it was not,
reenter the VARY NET command with the correct node name
specified.
VARY FAILED - UNABLE TO LOAD xxx 370X
Explanation: During processing of a VARY NET,ACT command,
the communications controller could not be loaded with the
network control program represented by xxx. Therefore, VTAM
cannot use the communications controller.
System Action: Processing of the command is terminated.
System status is unchanged.
Operator Response: Probable 3704/5 hardware error. Retry
the VARY NET command. If the retry fails, follow the problem
determination action.
Problem Determination: Table I, items 2, 18, 30.
IST0711
cm FAILED - INVALID OPTIONS
I Explanation:
IST067I
VARY FAILED - UNABLE TO OPEN 10 = xxx
Explanation: During a VARY NET command to activate the
Explanation: A VARY NET comma",d was entered with the
IST0651
• VTAM was unable to load channel-end appendages needed
for node (3270 or 370X).
• There were no available paths to the device (370X).
System Action: VTAM continues to activate other subordinate
nodes.
Operator Response: Probable user error. Enter a VARY
NET,ACT command for node xxx after the node is deallocated,
or after the channel unit address has been correctly specified
as shown below.
Programmer Response: Check that the correct channel unit
address was specified for node xxx in one of the following
operands:
• The CUADDR operand of the VTAM PCCU definition macro
instruction.
• The U = address operand of the VARY NET command.
IST0721
I
I
VARY FAILED DURING NETWORK DEFINITION OF
xxx
Explanation: An attempt to activate the network control
program in the communications controller xxx was unsuccessful
because a Resource Definition Table (ROT) segment could not
be built. The NCP definition is in error. Preceding messages
describe the error in detail.. VTAM cannot use the
communications controller~
System Action: The communications controller remains
inactive. Processing 'of the command is terminated. System
status is unchanged.
Programmer Response: Probable user error. Determine the
exact cause of the failure from preceding messages and alter
the NCP definition to overcome the problem before the
operator reenters the command.
Section 22: 1ST Messages - VTAM 22-5
VS2.03.801
IST073I
cm FAilED FOR ID = xxx BECAUSE IT IS BEING
DEACTIVATED
Explanation: The node named xxx specified in the cm
command· has a pending deactivation request; therefore, the
command cannot be executed.
System Action: Processing of the command is terminated.
SY$tem status is unchanged.
Operator Response: Monitor the progress of the deactivation
by using the DISPLAY NET command. When the node has been
deactivated, reissue the command.
num is the number of temporary errors counted for this
3704/5 or terminal.
1Both counts are clitmulative from the time that the 3704/5 or
terminal was last activated and are expressed in decimal.
xxx is the channel unit address of the communications
controller.
System Action: System continues processing.
Operator. Response: None.
IST0791
TERMINALS:
Explanation: This header line results from a DISPLAY NET
I
IST0741
cm FAilED FOR ID - xxx - INSUFFICIENT STORAGE
Explanation: The specified command was entered for the node
named xxx, but the command failed because VTAM was unable
to obtain a work area to process the· request.
System Action: Processing of the command is terl1)inated.
System status is unchanged.
Operator Response: Wait for a short period and then reenter
the command. In the event of repeated failure, report this
message to the system programmer.
Programmer Response: This message indicates that storage
requirements for VTAM were underestimated. Check storage
estimates and increase storage allocation where possible.
IST0751
VTAM DISPLAY - NODE TYPE - xxx, NAME - yyy,
STATUS - stat
Explanation: This is a header line of a VTAM display that
results from a DISPLAY NET command.
xxx is the type of node being displayed:
• TERM - a terminal.
• LINE - a communication line.
• APPl - an application program.
• 370X - a comunications controller.
yyy is the symbolic node name.
stat is the status of the node and can be:
ACT
which means that the specified terminal is active.
INACT which means that the specified terminal is not active.
ACT/B which means that the specified terminal is a logical
unit and a session is being established (a BIND is in
progress)
ACT/U which means that the specified terminal is a logical
unit and a session is being terminated (an UNBIND or
CLEAR is in progress).
INA/C which means that the specified node is a physical unit
and a CONTACT is in progress.
INA/A which means that an ACTIVATE is in progress for the
specified node.
System Action: System continues processing.
Operator Response: None.
IST0761
CTl PROGRAM
=
xxx, ATTACHMENT -
yyy
Explanation: This message results from a DISPLAY NET
I xxx
command that requests status of a communications controller.
is the symbolic node name of the network control
program associated with this communications controller.
is the type of attachment of the communications
controller, either LOCAL or REMOTE.
System Action: System continues processing.
Operator Response: None.
yyy
IST0771
510
=
nnn, ERROR CT = num, CUA = xxx
Explanation: This message results from a DISPLAY NET
command that requests the status,of a locally-attached
I terminal or a communications controller.
nnn is the number of start I/O operations counted for this
I communications controller or terminal.
22-6
VS2 System Messages (VS2.03.80l)
command requesting line or application status. The following
lines of display, message IST0801, indicate which terminals are
associated with the line or application.
System Action: System continues processing.
Operator Response: None.
IST0801
xxx stat xxx stat xxx stat
Explanation: This message results from a DISPLAY NET
command that requests line or application program status; it
follows message IST0791. It lists the terminals associated with
the line or application program, and gives their status. If more
than three terminals are involved, the message is repeated as
often as necessary.
xxx is the symbolic name of a terf11inal associated with the line
or application.
stat is a status indicator for the terminal named. It may be any
of the following:
• ACT - the terminal named is active.
• INACT - the terminal named is inactive.
• ACT/B - the terminal named is a logical unit and a session
is being established, (a BIND is in progress).
• ACT/U - the terminal named is a logical unit and a session
is being terminated, (an UNBIND or CLEAR is in progress).
• INA/A - an ACTIVATE is in ·progress for the specified node.
• LOGON - the terminal named is queued for the application
program being displayed but has not yet been connected.
System Action: System continues processing.
Operator Response: None.
IST08l1
LINE NAME = xxx, LINE GROUP = yyy
Explanation: This message is part of a terminal or line status
display that results from a DISPLAY NET command.
xxx is the symbolic name of the line to which the terminal is
connected.
yyy is the symbolic name of the line group to which the line
xxx belongs.
System Action: System continues processing.
Operator Response: None.
IST0821
DEVICE TYPE = devtyp, ALlOC TO
SIMLOGON - xxx
=
appl,
Explanation: This message is part of a terminal status display
that results from a DISPLAY NET command.
devtyp is the device type of the terminal.
appl is the symbolic name of the application to which the
terminal is allocated. If the terminal is not allocated, then
NONE is displayed.
xxx is the symbolic name of the application program (as
defined in the access method control block .. ACB) to which
the terminal is connected. If the terminal is not connected,
then NONE is displayed.
System Action: System continues processing.
Operator Response: None.
VS2.03.801
IST0831
ADJACENT 370X = xxxxxxxx, LINE == yyyyyyyy
= bbb,
ccc, ddd
DISPLAY command where the 10 is that of a remote
communications controller; xxxxxxxx is the name of the
adjacent communications controller to which this remote
communications controller is attached. yyyyyyyy is the name of
the line which connects the remote communications controller
to the adjacent communications controller.
System Action: Processing continues.
Operator Response: None.
command that requests the status of a line; it follows message
IST0841. The message lists the names of the nodes associated
with the requested node and gives their status. If more than
one node is associated with the request, the message is
repeated as often as necessary.
aaa is the symbolic name of the node associated with the line.
bbb is the node type, which may be CLUS for. a cluster control
unit, TERM for a terminal device or logical unit, or INTNOD for
an intermediate node or placeholder.
ccc is the status indicator for the node named. It may be one
of the following:
ACT
which means that the specified terminal is active.
INACT which means that the specified terminal is inactive.
ACT /B which means that the specified terminal is a logical
unit and a session is being established (a BIND is in
progress).
ACT /U which means that the specified terminal is a logical
unit and a session is being terminated (an UNBIND or
CLEAR is in progress.)
INA/C which means that the specified unit is either a physical
unit or an intermediate node, and a CONTACT is in
progress.
INA/ A which means that an ACTIVATE is in progress for the
specified' node, and that node may be a physical unit
or an intermediate node.
ddd is the symbolic node name of the remotely attached 370X
that is associated with node aaa. It is provided for
active intermediate network nodes only.
System Action: System continues processing.
Operator Response: None.
NETWORK NODES:
Explanation: This message is the first line of a display that
results from a DISPLAY NET command requesting status of a
line. Immediately following this message will be'message
IST0891, which details the nodes associated with the network.
System Action: System continues processing.
Operator Response: None.
IST0851
DISPLAY FAILED - INFORMATION NOT AVAILABLE
Explanation: A DISPLAY NET command cannot be completed
because VTAM failed to assemble status information. The
system facilities required by the DISPLAY processor are not
available.
System Action: The DISPLAY NET command is canceled.
System continues processing.
Operator Response: Reenter the command after waiting a short
period of time.
)/
aaa TYPE
Explanation: This message results from a DISPLAY NET
IST0841
~
IST0891
Explanation: This message is received in response to a VTAM
IST0861
DISPLAY FAILED - INSUFFICIENT STORAGE
Explanation: A DISPLAY NET command cannot be completed
because sufficient storage is not available.
System Action: The DISPLAY NET command is rejected.
System continues processing.
Operator Response: Reenter the command after waiting a short
period of time. If the command fails repeatedly, report this
message to the system programmer.
Programmer Response: This message indicates that storage
requirements for VTAM were underestimated. Increase storage
allocation where possible.
IST0871
LINE TYPE == xxx LINE GROUP == yyy
Explanation: This message is part of the line status display
that results from a DISPLAY NET command.
xxx is the line type, either SWITCHED or LEASED.
yyy is the symbolic name of the line group to which the line
belongs.
System Action: System continues processing.
Operator Response: None.
IST0881
DISPLAY FAILED - NODE NAME INVALID
Explanation: The node name specified in the 10 parameter of
the DISPLAY NET command is not defined to VTAM.
System Action: The DISPLAY NET command is rejected.
System continues processing.
Operator Response: Probable user error. Reenter the command
using the correct node name in the 10 parameter or, if the
node name appears to be correct, ask your system
programmer to validate the command before reentering the
command.
Programmer Response: Check the validity of the node name
and, if necessary, correct the node name or change the VTAM
definition to validate the command when reentered.
IST0901
VARY CANNOT ACTIVATE xxx - OFFLINE OR
ALREADY ALLOCATED
Explanation: The node named xxx cannot be allocated to
VTAM because it is either offline or allocated to another user.
VTAM cannot activate it.
System Action: The node remains inactive. VTAM attempts to
activate remaining nodes of the segment specified in the VARY
NET command.
Operator Response: Make the specified node allocatable either
by bringing the node online or by releasing it from the other
user. Then reissue the VARY NET,ACT command.
IST0911
VARY UNABLE TO ACTIVATE xxx - VARY COMMAND
CONTINUES
Explanation: A VARY NET command attempted to activate
node xxx and failed.
System Action: VTAM continues processing. The VARY NET
command continues for all other nodes affected by the
parameters of the VARY command. The node xxx remains
inactive.
Operator Response: Retry the VARY NET command after
checking whether the node name specified is correct.
Programmer Response: Make sure that the name is properly
defined in the VTAM definition library.
IST0931
xxx ACTIVE
Explanation: The specified node, xxx, was successfully
activated as a result of a VARY NET command.
System Action: System continues processing.
Operator Response: None.
IST0941
VARY FAILED - ID == xxx INVALID
Explanation: The ID parameter of the VARY NET command
Section 22: 1ST Messages - VTAM 22-7
•
VS2.03.801
contains an invalid node name, xxx. The invalid name is an
application name"a minor node name, or the name of a line
group, or it was ~ot defined during the network definition
process for VTAM.
System Action: Processing, of the command is terminated.
System status is unchanged.
Operator Response: Check the spelling of the node name
entered. If misspelled, correct and reenter; otherwise, obtain
an alternate valid name (or wait for VTAM to be redefined to
recognize the name you are using before reentering the
command).
Programmer Response: Either amend the definition of VTAM to
match the name used, or supply the network operator with the
correct name for reentry.
Operator Response: Probable user error. Reenter the command
with the correct parameter.
IST095A
OPTION TO DUMP xxx AVAILABLE - REPLY YES or
NO
IST1011
Explanation: This is a prompting message to the network
operator to find out whether or not the communications
controller associated with the network control program xxx is
to be dumped. The prompt occurs when the communications
controller has failed and the AUTODMP option was not
specified in the PCCU macro instruction. Therefore the
operator can choose whether or not to dump the contents of
the communications controller· by entering YES or NO.
System Action: VTAM waits for a valid reply.
Operator Response: Enter YES if you wish to dump the
contents of the communications controller, or NO if you do
not. Any other response causes the message to be reissued.
You, should be instructed as to which reply should be entered
at your console.
'Programmer Response: Ensure that your instructions to the
network operator indicate which response to enter.
IST1021
IST0961
cm FAILED - DUPLICATE prm PARAMETERS
SPECIFIED
Explanation: The prm parameter was specified more than once
in the cm command.
System Action: The command is rejected.
Operator Response: Probable user error. Reenter the command
as many times as necessary, but use only one prm option for
each command.
IST0971
cm ACCEPTED
Explanation: There were no errors detected in the specified
command. The command is accepted for processing.
System Action: The command is passed to the VTAM
command processor.
Operator Response: None.
IST0981
em FAILED - op INCORRECT LENGTH
Explanation: The op operand in the sp~cified command was
either too long or too short. The maximum and minimum
lengths depend on the specified operand.
System Action: The command is rejected. System continues
processing.
Operator Response: Probable user error. Reenter the command
using the correct operand length.
IST099I
em FAILED - prm NOT ALPHAMERIC
I Explanation:
The specified command was entered with the prm
parameter containing nonalphameric characters. Only
alphameric characters are acceptable.
System Action: The command is rejected. System continues
processing.
22-8
VS2 System Messages (VS2.03.801)
IST1001
cm FAILED - xxx 10 NOT REQUIRED
Explanation: An 10 parameter was entered on the specified
command when it was not required, or when it was the only
parameter. xxx is the value associated with the 10 parameter.
System Action: If the parameter is not required, it is
interpreted as a conflicting request. If it is the only parameter
entered, VTAM cannot interpret the request. The command is
rejected. System continues processing.
Operator Response: Probable user error. Verify the action to
be performed and reenter the command with the correct
parameters.
cm FAILED -
x~
NOT SPECIFIED
Explanation: The 10 parameter is required on the specified
command but one was not entered. xx is the 10 associated
with the parameter.
System Action: The command is rejected. System continues
processing.
Operator Response: Probable user error. Reenter the command
with the 10 parameter specified.
VTAM IS NOW INACTIVE
Explanation: VTAM is terminating. Either a HALT NET
command was issued or an abnormal condition caused VTAM
to halt itself.
System Action: VTAM terminates. System continues
processing.
Operator Response: None. To reinitialize VTAM, follow the
normal VTAM start procedure.
IST1031
VARY FAILED FOR 10 = xxx - APPLICATION NOT
QUIESCED
Explanation: During the processing of a VARY NET,INACT
command to deactivate a group of one or more application
programs in the major node named xxx, one or more of the
programs were found to be still connected to VTAM. All
application programs in the major node must disconnect (issue
CLOSE) before the VARY NET command can deactivate the
major node.
System Action: Processing of the VARY NET command is
terminated. System continues processing.
Operator Response: Check whether the application programs
must remain active. If so, wait for the application programs to
terminate normally. Then enter a VARY NET,INACT command
for the node named xxx. If the application programs do not
need to be active, enter CANCEL for the appropriate
applications, followed by a VARY NET,INACT command for the
node xxx.
IST1041
VARY FAILED FOR 10 = xxx - NODE ALREADY
INACTIVE
Explanation: An attempt to inactivate node xxx using a VARY
NET command failed; the specified node was already inactive.
System Action: Processing of the VARY NET command is
terminated. System continues processing.
Operator Response: Probable user error. If the wrong node
name was entered, reenter the comman~ with the correct node
name.
IST1051
xxx NODE NOW INACTIVE
Explanation: The specified node named xxx was successfully
deactivated by the VARY NET,INACT command.
System Action: System continues processing.
VS2.03.801
Operator Response: None.
IST1141
IST1061
Explanation: While reading member mem of the
SYSl.VTAMLST data set, a syntax error was detected in one of
the statements stored in that member.
System Action: A subsequent message describes which VT AM
function could not complete. System continues processing.
Programmer Response: Correct the specified data set member
using the information displayed in the next message.
MODIFY FAILED - NETWORK SOLICITOR ALREADY
ACTIVE
Explanation: A MODIFY procname command was entered to
start the network solicitor. The command failed because the
network solicitor is already active.
System Action: The command is rejected. System continues
processing.
Operator Response: None.
ISTl151
IST1071
TIME AND DATE NOT SET IN xxx DUE TO INVALID
TIMER IN HOST
Explanation: The time-of-day clock in the host processor is in
error or is not operational. As a result, the time and date were
I not set in the NCP represented by xxx after it was loaded.
I
System Action: Activation of the specified NCP is completed
normally with the exception of setting time and date.
Operator Response: If time and date are required, deactivate
the network control program, set the time-of-day clock in the
host, and reactivate the network control program.
IST1081
MODIFY FAILED - NETWORK SOLICITOR NOT
ACTIVE
Explanation: A MODIFY procname command was entered to
deactivate the network solicitor. The command failed because
the network solicitor is already inactive.
System Action: The command is rejected. System continues
processing.
Operator Response: None.
IST1091
NETWORK SOLICITOR IS NOW TERMINATED
Explanation: The network solicitor was successfully terminated
as a result of a MODIFY procname command.
System Action: System continues processing.
Operator Response: None.
IST1101
NETWORK SOLICITOR STARTED
Explanation: The network solicitor was successfully started as
a result of a MODIFY procname command.
System Action: System continues processing.
Operator Response: None.
IST1111
MODIFY FAILED - nnn VALUE LESS THAN 1
Explanation: The number nnn entered in a MODIFY procname
command to change the negative response to polling (in the
NEGPOLL operand), or the NCP session limit (in the SESSION
operand) was O. The value specified must be in the range 1
through 255.
.
System Action: The command is rejected. System continues
processing.
Operator Response: Probable user error. Verify the value to be
entered and reenter the MODIFY NET command using the
correct value in the NEGPOLL or the SESSION operand.
ISTl131
MODIFY FAILED - TEST ALREADY IN PROGRESS
Explanation: A request to initiate a TOLTEP test from the
system console via the MODIFY procname command failed. A
test is already in progress from the system console.
System Action: The command is rejected. System continues
processing.
Operator Response: Probable user error. Terminate the
previous TOLTEP tast before reentering the MODIFY procname
command.
SYNTAX ERROR IN mem MEMBER OF VTAM
DEFINITION LIBRARY
INSUFFICIENT STORAGE TO READ mem MEMBER
OF VTAM DEF LIB
Explanation: Because of insufficient storage, member mem of
the SYSl.VTAMLST data set was not completely read.
System Action: A subsequent message describes which VTAM
function could not complete. System continues processing.
Programmer Response: Correct the specified data set member
using the information displayed in the next message.
IST1161
MEMBER mem NOT FOUND ON VTAM DEFINITION
LIBRARY
Explanation: The search for member mem on the
SYSl.VTAMLST data set was not successful.
System Action: A subsequent message describes which VTAM
function could not complete. System continues processing.
Programmer Response: Correct the specified member of
SYSl.VTAMLST using the information displayed in the next
message.
ISTl171
I/O ERROR READING mem MEMBER OF VTAM
DEFINITION LIBRARY
Explanation: An I/O error occurred while reading the member
mem of the SYSl.VTAMLST data set.
System Action: A subsequent message describes which VTAM
function could not complete. System continues processing.
Operator Response: Probable hardware error. Respond to the
next message. If message recurs, follow the problem
determination action.
Problem Determination: Table I, items 2, 18, 30.
ISTl181
ERROR IN LIST = xx • ALL START PROCEDURE
PARAMETERS IGNORED
Explanation: xx is a two character identifier specified in the
LIST parameter of the START command. When VTAM
initialization processed the parameters in this list, an error was
encountered. That error is reported in a previous message. All
parameters in the "list and any entered at the console have
been lost.
System Action: The system prompts the operator to enter
parameters for the START command and begins processing the
parameters entered.
Operator Response: Do not enter a LIST parameter specifying
the same 10 or the error will recur. Reenter all the required
parameters individually.
Programmer Response: Correct the predefined list that caused
the error" before it is used again.
IST1191
SYNTAX ERROR IN START PARM prm - ALL PARMS
IGNORED
Explanation: The operator entered a parameter string
containing a syntax error in the keyword starting with prm. No
parameters have been processed.
System Action: The operator is prompted for correct input by
message IST125A and VTAM waits for the response.
Operator Response: Probable user error. Reenter the entire
line, correcting the syntax error, or default by entering a blank.
Section 22: 1ST Messages - VTAM 22-9
•
i1
/1
VS2.03.801
IST1201
LOGON COMPLETE FOR NODE xxx
Explanation: VTAM finished processing the LOGON portion of a
VARY NET,ACT command or a VARY NET,LOGON command for
node xxx.
System Action: System continues processing.
Operator Response: None.
IST1211
VARY FAILED - CANNOT LOGON xxx TO appl
Explanation: An attempt to connect terminal xxx or LUxxx to
application program appl failed due to one of the following:
• Application appl is not defined to VTAM or is not included
in an active major node.
• appl is not an application program name.
• Application appl has blocked all logons or is quiescing
(closing its ACB).
Insufficient buffers for UECB.
System Action: Processing of the command is terminated.
Operator Response: Probable user error. Verify that the correct
names are being used. If not, reenter with the correct ..,ames.
If the message recurs, wait until the error has been corrected
before retrying the command.
Programmer Response: Check the possible reasons for the
failure, and correct the error. Check that terminal operator
messages are not confirming the third cause above.
I•
IST1221
ATTACH OF A VTAM SUB TASK subttt FAILED
Explanation: One of the VTAM subtasks, subttt, could not be
attached because it could not be located on SYS1.LlNKLIB.
System Action: VTAM terminates. System continues
processing.
Operator Response: Probable user error. Ensure that the
subtask named subttt is on SYS1.LlNKLIB before attempting
another start of VTAM.
Operator Response: Enter corrected parameters (except LIST)
or enter a blank to indicate that default values are desired.
IST1261
IST1271
stop the network solicitor; it failed due to insufficient storage.
System Action: The command is rejected. System continues
processing.
Operator Response: Wait for a short period and then reenter
the command. In the event of repeated failure, notify the
system programmer of this message.
Programmer Response: This message indicates that storage
requirements for VTAM were underestimated. Check storage
estimates and increase storage allocation where possible.
IST1241
STOP COMMAND REJECTED - NOT SUPPORTED
FOR VTAM
Explanation: The STOP command entered for the VTAM task is
not supported by VTAM. The VTAM task cannot be stopped
without terminating all of VTAM.
System Action: The STOP command is rejected. System
continues processing.
Operator Response: In order to terminate VTAM, use a HALT
NET or HALT NET,QUICK command.
a
IST125A
ENTER CORRECTED VTAM OPTIONS - EXCEPT
LIST = - OR DEFAULT
Explanation: An error has been encountered while processing
the VTAM START command. The error was reported in a
previous message. The operator is now being prompted to
correct the errors by entering specific parameters.
System Action: Parameters entered in reply to this prompt are
processed. If a LIST parameter is entered, it is ignored.
22-10
VS2 System Messages (VS2.03.801)
appl STILL ACTIVE - VTAM TERMINATION WAITING
Explanation: VTAM cannot terminate because the application
program appl has not yet closed.
System Action: VTAM termination processing is delayed until
the application is closed. System continues processing.
Operator Response: Cancel the job that contains the
application program appl.
IST1281
HALT OF VTAM ALREADY IN PROGRESS
Explanation: A HALT NET command was issued to terminate
VTAM, but a previous HALT NET command is still in progress.
The only acceptable combination is a HALT NET command
followed by a HALT NET,QUICK command.
System Action: The command is ignored. VTAM is currently
terminating and continues in this state.
Operator Response: If you want to close down the VTAM
network at once, enter HALT NET,QUICK. Otherwise, allow the
normal HALT NET to continue the closedown.
MODIFY NETSOL FAILED - INSUFFICIENT STORAGE
Explanation: A MODIFY procname command was entered to
xxx MODE NOT SUPPORTED DUE TO LOADING
FAILURE
Explanation: A VTAM processing mode represented. by xxx,
which is normally supported, is not usable because a required
module cannot be loaded. VTAM cannot support mode xxx.
System Action: System continues processing.
Programmer Response: No action is necessary if the absence
of the indicated mode does not affect operations. Otherwise,
system libraries must be checked for the presence of a load
module named xxx. It must be included if not found.
IST1291
IST1231
\
UNRECOVERABLE ERROR ON NODE xxx - VARY
INACT SCHEDULED
Explanation: An unrecoverable error occurred in either a
communications controller or an SDLC cluster controller.
System Action: A VARY NET,INACT command is automatically
issued by VTAM for the controller.
Operator Response: Probable hardware error. No action is
necessary if the absence of the indicated node does not affect
operations. Otherwise follow the problem determination action.
Problem Determination: Table I, items 2, 18, 30.
IST1301
VTAM SUBTASK subttt NOT REATTACHED - ABEND
COUNT EXCEEDED
Explanation: A VTAM subtask, subttt, abnormally terminated
and has attempted by means of its STAE exit to be reattached.
Each time the STAE exit is entered, a count is incremented
and the subtask is reattached by VTAM. When this abend
count reaches a value of 5 (or 25 for the network solicitor),
VTAM does not reattach the'subtask.
System Action: No further attempts to attach the subtask are
made. System continues processing. VTAM continues without
the support of the subtask.
Operator Response: If the support of the subtask is required
for continued operation, try the appropriate MODIFY procname
command. If that fails, a HALT NET command followed by a
START command can be attempted.
Problem Determination: Table I, items 2, 16, 29.
IST1311
VTAM SUBTASK subttt NOT REATTACHED INSUFFICIENT STORAGE
Explanation: AVTAM subtask, subttt, abnormally terminated;
the storage required to reattach the subtask is not available.
~
VS2.03.801
System Action: The subtask IS not reattached. VTAM continues
without the support of the subtask.
Operator Response: If the support of the subtask is required
for continued operation, free storage if possible, then use the
appropriate MODIFY procname command to reattach the
subtask. If this fails, a HALT NET command followed by a
START command can be attempted.
IST1321
VTAM SUBTASK subttt NOT REATTACHED CANNOT BE FOUND
Explanation: A VTAM subtask, subttt, abnormally terminated.
An attempt was made to reattach it, but the subtask could not
be located on the system libraries.
System Action: The subtask is not reattached. VTAM continues
without the support of the subtask.
Operator Response: Ensure that the subtask is included in the
SYS1.VTAMLIB data set, then restart VTAM.
IST1331
VTAM TERMINATION IN PROGRESS
Explanation: VT AM is terminating because of an unrecoverable
error, or because a HALT NET command has been issued.
System Action: All VTAM processing is terminated. All VTAM
application programs must close their VTAM ACBs or be
canceled. After all application programs are closed, VTAM
terminates its own task(s).
Operator Response: This is an awareness message only. If the
message is the result of a HALT NET command, no response
is required. If it is caused by an abnormal termination, the
cause of the termination should be derived from preceding
messages.
IST1341
370X == xxxxxxxx
Explanation: This message is part of a VTAM display received
in response to a VT AM DISPLAY command. xxxxxxxx is the
name of the communications controller for the node specified
in the DISPLAY command.
System Action: Processing continues.
Operator Response: None.
IST1351
PHYSICAL UNIT == xxxxxxxX,YYYYYYY
Explanation: This message is part of a terminal display
resulting from a DISPLAY command with the ID of a logical
unit (LU).
xxxxxxxx is the name of the physical unit (PU) associated with
the logical unit.
yyyyyyy is the channel unit address of the physical unit and is
present only if the display is for a logical unit of a local major
node.
System Action: Processing continues.
Operator Response: None.
IST1361
xxxxxxxx SUBAREA = yyyyyyyy
Explanation: This message is part of a physical unit (PU) or
logical unit (LU) display resulting from a DISPLAY command.
xxxxxxxx is either SWITCHED or LOCAL and is the type of
subarea (major node) in which the logical unit or physical unit
exists (if defined in a local or switched major node.
yyyyyyyy is the name of the subarea (major node).
System Action: Processing continues.
Operator Response: None.
IST1371
CONFIG xxxxxxxx BYPASSED - LOCAL ADDR OF LU
yyyyyyyylNVALID
out of sequence. A local major node definition requires all LU
statements below thePU statement to which they apply to be
arranged in ascending order by local addresses.
System Action: The system continues processing. Logical unit
yyyyyyyy is not included in the VTAM network.
Operator Response: None.
Programmer Response: Correct the local major node definition
statements and refile them in SYS1.VTAMLST (using the same
member name originally assigned to that local major node).
When VTAM is again initialized or activated with the VARY
command, the logical unit will be included in the VTAM
network.
1ST 1381
3791 ERROR
Explanation: An error condition has been detected by the
TPIOS channel end appendage during communication between
VTAM and a locally attached 3791. The data provided is
represented as follows:
cua
control unit address
b.... b
error definition
ccw
d .... d
csws
csw status
ssss
sense bytes
System Action: The system takes various actions related to
the error definition information given in ·b.... b'.
Operator Response: Notify installation support personnel. Keep
a record of the occurrence of the message and the condition
causing it, for problem determination.
IST1391<
DISPLAY PATHS FAILED - NODETYPE OF xxxxxxxx
IS NOT PU IN SW SUBAREA
Explanation: A DISPLAY PATHS command was entered for the
node specified in the message, which was not a physical unit
(PU). Dial-out path information may only be obtained for a
physical unit of a switched major node.
System Action: VTAM rejects the DISPLAY PATHS command.
Operator Response: Correct the node ID and reenter the
DISPLAY PATHS command.
IST1401
VARY FAILED - NODE xxx IS INVALID
Explanation: An attempt to deactivate node xxx via a VARY
NET command failed. The node was invalidly defined in the
VTAM definition process. (A definition error caused the node
to be flagged as ·invalid').
System ACtion: Processing of the VARY NET command is
terminated. System continues processing.
Operator Response: Check the spelling of the node name. If
incorrect, retry with the correct name. If you are entering the
name correctly, wait until the name has been validated before
retrying.
Programmer Response: Probable user error. Either supply the
operator with an alternate, valid node name, or validate the
name xxx by amending the appropriate VTAM definition
statements.
IST1411
NODE xxx NOW DORMANT
Explanation: A VARY NET,INACT command to node xxx
proceeded to the pOint where all I/O operations to the node
are complete. The unit is logically disconnected from VTAM.
System Action: The VARY NET operation continues.
Operator Response: If the hardware was being deactivated to
allow for maintenance or physical switching, the operation can
now be performed.
Explanation: The LOCADDR value specified for LU yyyyyyyy is
Section 22: 1ST Messages - VTAM 22-11
VS2.03.801
IST1421
CONFIG xxxxxxxx BYPASSED PATH MACRO
yyyyyyyy ERROR REASON CODE n
System Action: The system continues processing.
Operator Response: None.
Explanation: The reason codes (n) are as follows:
IST1481
1. There is no dial number table or group name table built in
this segment. The MAXNO or MAXGRP value on the VBUILD
macro is zero or defaulted.
2. There is no path table built for this physical unit. The
MAXPATH value on the preceding PU macro is zero or
defaulted.
3. There is no more space in the path table of this PU for a
new path entry. The number of paths specified exceeds the
MAXPATH value of this PU statement.
4. There is no more space in the dial number table to store
the new DIALNO specified in this PATH macro. The number
of unique dial numbers exceeds the MAXNO value specified
on the VBUILD macro.
5. There is no more space in the group name table to store
the new GRPNM specified on this PATH macro. The number
of unique group names exceeds the MAXGRP value
specified on the VBUILD macro.
System Action: The system continues processing. The
configuration specified in the message will not be added to the
VTAM network.
Operator Response: Notify installation support personnel. Keep
a record of the occurrence of this message. After error
correction, use the VARY command to activate the
configuration again.
IST1431
Explanation: This message is part of a VTAM display in
response to a VTAM DISPLAY PATHS command. The message
specifies the name of the physical unit for which the paths are
being displayed.
System Action: The system continues processing.
Operator Response: None.
IST1491
IST1511
function, a request for storage was rejected. The function was
not performed. This node and its subordinate nodes are
unusable by VTAM and VTAM applications.
System Action: The system continues processing.
Operator Response: The operator may issue a VARY INACT,I
command against the 10, and when complete, ussue a VARY
ACT.
I
attempting to schedule error recovery procedures, storage was
not available. Error recovery was not scheduled.
System Action: The system continues processing.
Operator Response: The operator may issue a VARY INACT,I
against the 10, and when complete, issue a VARY ACT.
IST1461
LINE NAME = xxxxxxxx STATUS = yyyyy
Explanation: This message results when a DISPLAY command
is issued against a port. The message specifies the line
associated with the port.
System Action: The system continues processing.
Operator Response: None.
IST1471
PORT NAME = xxxxxxxx STATUS = yyyyy
Explanation: This message results when a DISPLAY command
is issued against a dial-in line. The message specifies the port
for tha~ line. yyyyy may be ACT or INACT.
22-12
VS2 System Messages (VS2.03.801)
change the parms delay of a line whose 10 is XXXXXXXX, but a
permanent I/O error occurred.
System Action: The command is rejected and the parm value
is unchanged. System continues processing.
Operator Response: Using the DISPLAY command, determine
whether any terminals attached to line xxxxxxxx are engaged in
active sessions with the communications controller. When the
active sessions cease, reissue the command.
IST1521
FUNCTION FOR 10 = xxxxxxxx REJECTED - NODE
UNUSABLE
Explanation: A failure has occurred on the specified 10. In
MODIFY LINE SCHEDULING PARMS FAILED FOR
10 = xxxxxxxx - I/O ERROR
Explanation: A MODIFY procname command was entered to
Explanation: A failure has occurred on a device associated
with the specified link.
System Action: The system continues processing.
Operator Response: Manually hang up the modem for the
specified link.
IST1451
TELEPHONE NO
response to a VTAM DISPLAY PATHS command.
LINE GRPis the line group from the GROUP statement in the
NCP definition.
TELEPHONE NO is the dial characters to be used when
initiating a connection with a physical unit over a
switched link.
PID
is the path identifier.
GID
is the path group identifier for a group of paths across
all physical units.
CNT
is the nu.mber of times the dial operation is to be
retried at the NCP.
System Action: The system continues processing.
Operator Response: None.
FUNCTION FOR 10 = xxxxxxxx REJECTED - NO
STORAGE
POTENTIAL OPEN CONNECTION ON 10 = xxxxxxxx
LINE GRP
PID GID CNT
Explanation: This message is part of a VTAM display in
Explanation: In an attempt to process a session services
IST1441
DIAL OUT PATH INFORMATION FOR PHYSICAL UNIT
xxxxxxxx
I
I
VARY INACTIVATE FAILED - I/O ERROR ON 370X
xxx
Explanation: A VARY NET,INACT command failed due to a
permanent I/O error on the communications controller
represented by xxx. The error caused the controller to be
removed from the network and therefore to be unavailable to
VTAM.
System Action: The VARY NET command is rejected. The
specified communications controller is removed from the VTAM
network. System continues processing.
Operator Response: Probable hardware error.
Problem Determination: Table I, items 2, 18, 30.
IST1531
PENDING INACTIVATE TO xxx OVERRIDDEN
Explanation: A previous VARY NET,INACT command had
placed node xxx in a deactivate pending status. A VARY
NET,INACT,I command (with the immediate operand) was
issued to remove the node from pending status and complete
the deactivation process.
System Action: The specified node is made inactive when the
deactivate processing completes.
Operator Response: None.
VS2.03.801
IST1541
ERROR RECOVERY FOR dey FAILED - INSUFFICIENT
STORAGE
Explanation: An I/O error occurred on device dev which is
allocated to VTAM. The VTAM error recovery procedure (ERP)
routines attempted to recover but could not complete due to
insufficient storage.
System Action: System continues processing. The device
specified is treated as unavailable to VTAM since it has been
neither recovered nor deactivated.
Operator Response: Deactivate the specified node using a
VARY NET,INACT,I command.
IST1561
UNABLE TO DEALLOCATE xxx - COMMAND
CONTINUES
Operator Response: No direct response to this message is
required. Follow instructions for subsequent messages.
IST162A
OPTION TO POWER OFF xxx AVAILABLE - REPLY
'YES' OR 'NO'
Explanation: A VARY NET,INACT command was issued for
network control program xxx. The power supply to the
communications controller containing this network control
program can be switched off remotely. The operator is being
invited to switch the power off or leave it on.
System Action: VTAM waits for a reply. If YES is entered, the
power supply to the communications controller is switched off;
if NO is entered, the power supply remains on.
Operator Response: Enter YES or NO.
Explanation: A VARY NET,INACT command was entered to
deallocate a higher-level node that includes a set of
subordinate nodes. During the processing of the command,
subordinate node xxx could not be deallocated.
System Action: The VARY NET,INACT command continues
deallocation processing on other subordinate nodes. Node xxx
is not deallocated.
Operator Response: Enter a VARY NET,INACT command for
node xxx to deallocate (deactivate) the node.
IST1571
370X COMMAND - 'DEACTIVATE PHYSICAL UNIT'
FAILED FOR xxx
Explanation: A VARY NET,INACT command was issued for a
higher-level node. During the internal processing for this
command, a deactivate-physical-unit command for. node xxx
failed.
System Action: The failure is signaled back to the VARY
command processor. Further messages are issued by VTAM
that describe any action taken as a result of this failure.
Operator Response: No direct response to this message is
required. Follow instructions for subsequent messages.
IST1581
370X COMMAND - 'SWITCH LINE' FAILED FOR xxx
Explanation: A network control program switch-line facility (to
switch a PEP line to the emulation mode) was invoked as part
of the processing for a VARY NET,INACT command. The
command failed for the line designated as xxx.
System Action: The line is not switched to the emulation
mode. Further messages are issued by VTAM that describe any
action taken as a result of this failure.
Operator Response: No direct response to this message is
required. Follow instructions for subsequent messages.
IST1591
MODIFY DUMP FAILED - QUIESCE COMMAND TO
xxx FAILED
Explanation: As a result of a MODIFY procname, DUMP
command, VTAM issued a Quiesce Control command to the
communications controller xxx, and the command has failed.
System Action: The MOD.IFY procname command terminates.
System continues processing.
Operator Response: Previously-issued console messages
describe the detailed cause of the failure. Retry the MODIFY
procname command since the status of the communications
controller has not yet changed.
Problem Determination: Table I, item 2.
IST1641
DUMP OF xxx TERMINATED - MODIFY CONTINUING
DEACTIVATION
Explanation: A MODIFY procname, DUMP command has failed
to yield a complete dump of the communications controller's
storage.
SYstem Action: The dump of communications controller xxx
terminates, but the MODIFY procname command continues to
deactivate the node since the original NCP has been
destroyed.
Operator Response: Previously-issued console messages
describe the detailed cause of the failure.
Problem Determination: Table I, item 2.
IST1671
NO DIAL OUT PATH FOR xxxxxxxx
Explanation: This message is part of a VTAM display in
response to the VTAM DISPLAY PATHS command. No dial out
paths exist for physical unit xxxxxxxx.
System Action: Processing continues.
Operator Response: None.
- 'RECORD DEVICE STATISTICS' FAILED FOR xxx
Explanation: The record-device-statistics (RDVSTAT) facility
was invoked as part of the processing for a VARY NET,INACT
command. The command failed for the node designated as xxx.
System Action: Device statistics are not gathered for node
xxx. Further messages are issued by VTAM that describe any
action taken as a result of this failure.
Operator Response: No direct response to this message is
required. Follow instructions for subsequent messages.
IST1611
IST1631
370X COMMAND - 'DEACTIVATE LINE' FAILED FOR
xxx
Explanation: A network control program deactivate line-facility
was invoked as part of the processing for a VARY NET,INACT
command. The command failed; line xxx is not deactivated.
System Action: The failure is signaled back to the VARY NET
command processor. Further messages are issued by VTAM
that describe any action taken as a result of this failure.
IST1681
xxxxxxxx tttlttttttttlttttttttttttttttttt ppp ggg ccc
aaa mmm
Explanation: This message is part of a VTAM display in
response to the VTAM DISPLAY PATHS command.
xxxxxxxxis the line group name for this path.
ttt...tt are the dial characters to be used in initiating a
connection with a physical unit over a switched link.
ppp
is the path identifier (PID).
ggg
is the group identifier (GID) for a group of paths
across all physical units.
ccc
is the number of times the dial operation is to be
retried at the NCP.
aaa
can be either AVA, meaning that the path is available
for use by VTAM, or NAV, meaning that the path is
not available.
mmm can be either MAN for manual dial, or AUT for
automatic dial.
System Action: Processing continues.
Section 22: 1ST Messages - VTAM 22-13
VS2.03.801
Operator Response: None.
IST1691
DISCONNECTION CAUSED VARY INACT FOR
PU ~ xxxxxxxx
Explanation: One of the following conditions has occurred:
1. DISCNT - YES was specified on a PU macro and all LU-LU
sessions (logical unit - VTAM application program) sessions
were ended.
2. DISCNT - NO was specified and either a Request Discontact
of an immediate type was received. from the physical unit,
or a Request Discontact of a ,normal type was received from
the PU and all LU-LU applications sessions ended.
3. All LU-LU application program sessions ended due to a
character-coded LOGOFF command with HOLD - NO
specified.
System Action,: The system continues processing.
Operator Response: None.
processor received invalid feedback from INQUIRE processor.
For an explanation of register values, refer to Appendix C of
VTAM Macro Language Reference GC27 -6995.
System Action: Not applicable.
Operator Response: Retry the command. If the situation
persists, notify installation support personnel.
IST1761
aaaaaaaa FAILED - xxxxxxxx AND yyyyyyyy ARE
CONFLICTING OPTIONS
Explanation: The specified command failed because the
options specified (xxxxxxxx and yyyyyyyy) are mutually
exclusive and should not appear on the same command.
System Action: The command is rejected.
Operator Response: Probable user error. Reenter the command
using only one of the options specified above, and verifying
that no other conflicting options appear.
IST1801
IST1701
LINES
=
Explanation: This' is a header line for a VTAM display of NCP
status. The following lines of display indicate which lines are
associated with the NCP.
System Action: Not applicable.
Operator Response: Not applicable.
SESSION
ACTIVE SESSIONS = xxxx
REQUESTS - yyyy
Explanation: This line is used to format a display of the
number of active sessions and logon requests for an
application.
XXX)( number of active sessions for the application.
yyyy - number of logon requests to the application.
System Action: Not applicable.
Operator Response: Not applicable.
IST1711
IST1721
NO xxxxxxxxxxxxx yyyyyyyy
Explanation:
xxxxxxxxxxxxx - either LINES, or NETWORK NODES, or
TERMINALS, or SESSIONS.
yyyyyyyy - either ACTIVE or INACTIVE or EXIST.
This line is in response to a VTAM display of an NCP, line,
cluster or application. No resources of the type named (lines,
network nodes, terminals or sessions) have the named status
(active, inactive, or none exist).
System Action: Not applicable.
Operator Response: Not applicable.
IST1741
WARNING: 10BUF THRESHOLD VALUE TOO LOW
FOR BUF UTILIZATION
Explanation: The threshold of the buffer pool 10BUF must be
at least as large as a maximum request for the buffers that will
hold I/O data. A smaller threshold may cause a large request
for storage to be deferred for an indefinite period of time. In
addition, a smaller threshold could enable a READ request to
be deferred while other storage requests (those used to handle
I/O to the NCP) are satisfied.
System Action: The system continues processing.
Operator Response: Either continue or notify installation
support personnel.
Programmer Response: Increase the threshold for 10BUF. (See
the VS2 System Programming Library: VTAM, GC28-0688.)
DISPLAY FAILED - VTAM ERROR. RO = xxxxxxxx,
R15 = yyyyyyyy
Explanation: Internal VTAM error. DISPLAY command
OPEN FAILED ON CKPT OS xxxxxxxx MAJ NODE
yyyyyyyy RTNCD - aa,bb
Explanation: The VSAM function (OPEN) failed for the
specified checkpoint data set.
xxxxxxxxis the checkpoint data set name.
yyyyyyyyis the major node name.
aa,bb are major and minor return codes from VSAM.
System Action: Checkpointing is terminated for this segment.
Operator Response: User response will be determined by the
VSAM return codes. (See OS /VS VSAM Programmers Guide,
GC26-3818.
IST1811
CLOSE FAILED ON CKPT DS xxxxxxxx MAJ NODE
yyyyyyyy RTNCD - aa,bb
Explanation: The VSAM function (CLOSE) failed for the
specified checkpoint data set.
xxxxxxxx is the checkpoint data set name.
yyyyyyyyis the major node name.
aa,bb are major and minor return codes from VSAM.
System Action: Checkpointing is terminated for this segment.
Operator Response: Probable hardware error. Refer to the
explanation of VSAM major and minor return codes in OS /VS
VSAM Programmers Guide, GC26-38l8.
IST1821
UNABLE'TO GET STORAGE FOR CKPT - xxxxxxxx
MAJOR NODE yyyyyyyy
Explanation: VSAM was unable to obtain storage for the
specified checkpoint data set~
xxxxxxxxis the checkpoint data set name.
yyyyyyyyis the major node name.
System Action: Checkpointing is terminated for this segment.
Operator Response: None.
ISTl83A
xxxxxxxx FOUND LOADED WITH yyyy - REPLY
YES/NO TO RE-IPL
Explanation: During the restart of a configuration, VTAM found
the specified 10 to be loaded with the indicated NCP.
AUTO-SYNCH - NO was specified on the restart command for
this 10. The operator may therefore decide to re-IPL the
specified NCP or continue with it as it is.
System Action: The system continues processing. If there is
no reply given, the message will be reissued.
Operator Response: If the operator wishes to re-IPL the
indicated NCP, he must reply YES. If no re-IPL is desired, he
must reply NO.
IST1751
IST1841
I/O ERROR ON CKPT DS xxxxxxxx MAJ NODE
yyyyyyyy, RTNCD = aa,bb
Explanation: An I/O error occurred for the checkpoint data set
22-14
VS2 System Messages (VS2.03.801)
YS2.03.801
specified.
xxxxxxxxis the checkpoint data set name.
yyyyyyyyis the major node name.
aa,bb are major and minor return codes from VSAM.
System Action: Checkpointing is terminated for this segment.
Operator Response: Probable hardware error. Refer to the
explanation of VSAM major and minor return codes in OS /VS
VSAM Programmers Guide, GC26-3818.
IST1851
LOGICAL ERROR OCCURRED ON CHECKPOINT DS
xxxxxxxx MAJOR NODE Y'IYYY'IYY
IST1911
xxxxxxxx SYNTAX ERROR
Explanation: The syntax rules for the specified VTAM
command have been violated.
System Action: The command is not executed.
Operator Response: Correct the syntax and retry the
command.
IST1921
POA MSG TRANSFER FAILED - INSUFFICIENT
STORAGE
Explanation: An incompatibility exists between the checkpoint
data set and VSAM system control blocks.
xxxxxxxxis the checkpoint data set name.
yyyyyyyyis the major node name.
System Action: Checkpointing is terminated for this segment.
Operator Response: Verify that the checkpoint data set is
appropriate for the major node being activated.
Explanation: VTAM was unable to allocate storage for a
message to be transferred to a programmed operator
application.
System Action: The message will be issued to the system
console.
Operator Response: Attempt to process message normally
from the system console and notify the remote operator.
Programmer Response: Review the amount of storage
allocated to VTAM and make any necessary adjustments.
IST1861
IST1931
xxxxxxxx ACTIVATED COLD - CHECKPOINT DATA
SET yyyyyyyy EMPTY
Explanation: The specified 10 has been activated cold since
the specified checkpoint data set is empty. A warm activation
requires that the segment be previously checkpointed.
System Action: The command continues with the segment
activated cold.
Operator Response: None.
IST1871
VARY FAILED FOR xxxxxxxx - CHECKPOINT DATA
SET yyyyyyyy EMPTY
REPLY xx IGNORED; REPLY TOO LONG FOR
REQUESTOR
Explanation: A REPLY xx command was entered and the reply
text was too long for the user's buffer.
System Action: The REPLY xx command is ignored. The
system continues processing.
Operator Response: Probable user error. Enter the REPLY
command again correctly.
IST1941
REPLY xx NOT OUTSTANDING
Explanation: A REPLY xx command was entered, however
Explanation: The specified 10 failed to activate since the
specified checkpoint data set is empty. A warm activation
requires that the segment be previously checkpointed.
System Action: The command is terminated.
Operator Response: Reenter the command without specifying
WARM.
there is no outstanding reply request with the identification xx.
Either the message request has already been answered or the
message reply identification xx is incorrect.
System Action: The REPLY xx command is ignored.
Operator Response: If the reply identification was entered
incorrectly, enter the command agai'n correctly.
IST1881
IST1951
VARY FAILED FOR xxxxxxxx - CHECKPOINTING
ERROR IN yyyyyyyy
Explanation: The specified 10 failed to activate because an
REPLY xx IGNORED; NON-DECIMAL 10
Explanation: A REPLY xx command was entered specifying a
error occurred during the use of the specified checkpoint data
set. An error of this type may effect the integrity of the
Resource Oefinition Table (ROT).
System Action: The command is terminated.
Operator Response: Reenter the command. If the problem
persists, notify installation support personnel.
non-decimal identification. The REPLY xx command must be
entered as decimal digits with or without a leading zero in
identifications 01 through 09.
System Action: The REPLY xx command is ignored. The
system continues processing.
Operator Response: Probable user error. Enter the REPLY
command again correctly.
IST1891
IST1961
xxxxxxxx ACTIVATED COLD - NO CHECKPOINT
DATA SET
Explanation: The indicated 10 has been activated cold since no
checkpoint data set was specified. A checkpoint data set is
required for a warm activation.
System Action: The command continues with the segment
activated cold.
Operator Response: None.
IST1901
VARY FAILED FOR xxxxxxxx - NO CHECKPOINT
DATA SET
Explanation: The indicated 10 failed to activate since no
checkpoint data set was specified. A checkpoint data set is
required for a warm activation.
System Action: The command is terminated.
Operator Response: Reenter the command without specifying'
WARM.
REPLY xx IGNORED; IMPROPER USE OF DELIMITER
Explanation: REPLY xx was invalid for one of the following
reasons:
• A closing apostrophe did not follow the text when the text
was preceded by an apostrophe.
• A comma did not immediately follow the identification.
System Action: The REPLY xx command is ignored. The
system continues processing. ,
Operator Response: Probable user error. Enter the REPLY
command again correctly.
IST1971
SAVED CONFIGURATION xxxxxxxx READ FROM
VTAMOBJ
Explanation: VTAM system definition has located a copy of the
configuration which was activated by a VARY command. It was
found on the VTAMOBJ data set. A copy of the configuration
was saved during a previous activation. The definition of this
configuration on the VTAMLST data set is not referenced.
Section 22: 1ST Messages - VTAM 22-15
(
\
VS2.03.801
IST2051
System Action: The system continues processing.
Operator Response: None.
NOTE: Any changes made to the definition of a configuration
Explanation: This message indicates that an invalid command
was scheduled to node xxx by an application program. The
message is also issued if the application program attempts an
invalid conversational reply. val is the hexadecimal value of the
NCP command code and modifier; aa is the hexadecimal value
of the NCP system response code; bb is the hexadecimal value
of the NCP extended response code.
System Action: System continues processing.
Operator Response: Probable user error. Follow the problem
determination action.
Problem Determination: Table I, item 2.
since .the first copy was saved on VT AMOBJ will not be in
effect.
IST2011
xxx CATASTROPHIC I/O ERROR val - NCP
RESPONSE = aa-bb
Explanation: This message indicates that an unrecoverable I/O
error occurred at node xxx. The node may be a terminal, line,
or communications controller. This message is issued for all
hardware check extended response status except equipment
check. val is the hexadecimal value of the NCP command code
and modifier; aa is the hexadecimal value of the NCP system
response code; bb is the hexadecimal value of the NCP
extended response code.
System Action: The application is informed that this device is
no longer usable. VTAM continues processing for other nodes.
Operator Response: Enter a VARY NET,INACT command for
this node.
Problem Determinations: Table I, items 2, 18, 30.
IST2021
IST2061
xxx PERMANENT I/O ERROR val - NCP RESPONSE
= aa-bb
IST2071
IST208A
xxx EQUIPMENT CHECK val - NCP RESPONSE
aa-bb
VS2 System Messages (VS2.03.801)
=
aa-bb
xxx INTERVENTION REQD val - NCP RESPONSE
= aa-bb
Explanation: The VT AM node xxx has had an
intervention-required situation detected by the 370X NCP. val
is the hexadecimal value of the NCP command code and
modifier; aa is the hexadeCimal value of the NCP system
response code; bb is the hexadecimal value of the NCP
extended response code.
System Action: VTAM continues processing for other nodes.
The application is notified of the intervention-required
condition.
Operator Response: Attempt to correct the
intervention-required condition. If unable to locate or correct
it, notify the system programmer.
Programmer Response: If the application program has leading
graphics or BSC status, it can issue a READ macro instruction
to get the device-ready status. Otherwise, it should issue a
RESET macro instruction and retry.
Explanation: This message indicates that an undeterminabie
22-16
xxx DATA CHECK val - BSC STATUS
xxx has detected a permanent data check error and has
posted it to the requesting application program. val is the
hexadecimal. value of the NCP command code and modifier; aa
is the hexadecimal value of BSC status byte 1; bb is the
hexadecimal value of BSC status byte 2.
System Action: VTAM continues processing. The application is
notified of the error cO{ldition.
Operator Response: Probable hardware error. If the message
recurs often, issue a VARY NET,INACT command to deactivate
the node.
Problem Determination: Table I, items 2, 18, 30.
xxx PERMANENT I/O £RROR val - BSC STATUS
= aa-bb
Explanation: An uncorrectable I/O error was detected for a
remote 3270 terminal represented as xxx. This message is
issued for data check, error BSC status, buffer pool end, or
lost data. val is the hexadecimal value of the NCP command
code and modifier; aa is the hexadecimal value of BSC status
byte 1; bb is the hexadecimal value of BSC status byte 2.
System Action: System continues processing. The application
is informed that this device is no longer usable.
Operator Response: Probable hardware error. If message
recurs often, enter a VARY NET,INACT command for the. node.
Problem Determination: Table I, items 2, 18, 30.
hardware malfunction has occurred on node xxx. It is issued
for NCP equipment check extended response. val is the
hexadecimal value of the· NCP command code and modifier; aa
is the hexadecimal value of the NCP system response code; bb
is the hexadecimal value of the NCP extended response code.
System Action: The application is informed that this device is
no longer usable. VT AM continues processing for other nodes.
Operator Response: Probable hardware error. Issue a VARY
NET,INACT command for the node.
Problem Determination: Table I, items 2, 18, 30.
aa-bb
Explanation: The VTAM remote 3270 terminal represented as
IST2031
I
=
data-check error and has posted it to the requesting
application program. val is the hexadecimal value of the NCP
command code and modifier; aa is the hexadecimal value of
the NCP system response code; bb is the hexadecimal value of
the NCP extended response code.
System Action: VTAM continues processing for other nodes.
The application is notified of the error condition.
Operation Response: Probable hardware error. If the message
recurs often, issue a VARY NET,INACT command to deactivate
the node.
Problem Determination: Table I, items 2, 18, 30.
uncorrectable I/O error for VTAM node xxx. The error may
have occurred at the device, the line, or in the
communications controller. This message is issued for data
check, error BSC status, buffer pool end, or lost data. val is
the hexadecimal value of the NCP command code and
modifier; aa is the hexadecimal value of the NCP system
response code; bb is the hexadecimal value of the NCP
extended response code.
System Action: System continues processing. The application
is informed that this device is no longer usable.
Operator Response: Probable hardware error. Enter a VARY
NET,INACT command for the node.
Problem Determination: Table I, items 2, 18, 30.
IST2041
xxx DATA CHECK val - NCP RESPONSE
Explanation: The VTAM node xxx has detected a permanent
Explanation: The communications controller detected an
I
xxx COMMAND REJECT val - NCP RESPONSE
= aa-bb
IST209A
I
xxx INTERVENTION REQD val - BSC STATUS
= aa-bb
Explanation: The VTAM remote 3270 terminal represented by
xxx has detected an intervention-required situation. val is the
hexadecimal value of the NCP command code and modifier; aa
VS2.03.801
is the hexadecimal value of BSC status byte 1; bb is the
hexadecimal value of BSC status byte 2.
System Action: VTAM continues processing for other nodes.
The application is notified of the intervention-required
condition.
Operator Response: Attempt to correct the
intervention-required condition. If unable to locate or correct
it, notify the system programmer.
.
Programmer Response: If the application program has leading
graphics or BSC status, it can issue a READ macro instruction
to get the device-ready status. Otherwise, it should issue a
RESET macro instruction and retry.
1512101
xxx UNSOLICITED DATA RECEIVED
Explanation: VTAM received data from node xxx without having
sent any requests for data to that node. The data is discarded
by VTAM.
System Action: VTAM continues processing. The data is
.
discarded and, except for this message, all request processing
continues.
Operator Response: Probable user error. Notify the user of
node xxx that the data being entered is being discarded. The
terminal user should stop entering data until he has
established a connection (via LOGON or some other procedure
established by the installation).
IST211 I
I
'"',
I
,,'
I
I
IST2141
I
I
IST2151
I
I
NCP SLOWDOWN INITIATED FOR xxx
I
I
= ~ up to
IST2161
xxx DIAL REQ'D DIALNO
IST2171
REMOTE MDR DATA RECORDING SUSPENDED
Explanation: A programming error was detected while
recording miscellaneous data recorder (MDR) data. Return
code 16 was received from the system recorder.
System Action: MDR recording is suspended. Any MDR data
received from remote devices is discarded. All other VTAM
processing continues normally.
Operator Response: After the programming error has been
corrected, VTAM must be restarted before MDR recording can
continue.
NETWORK SHUTDOWN STARTED VIA PANEL CMD
FOR xxx
IST2181
Explanation: This message indicates that the specified
communications controller has begun auto-network shutdown
due to a communications controller panel command. For
remotely attached communications controllers, xxx is the VTAM
node name.
System Action: Outbound I/O request scheduling (with the
exception of RESETS) is suspended. VTAM continues servicing
inbound processing until all current data is processed.
Operator Response: None.
15T2131
NETWORK SHUTDOWN COMPLETE FOR xxx
Explanation: This message indicates that the specified
communications controller has completed network shutdown.
For remotely attached communications controllers, xxx is a
VTAM node name.
System Action: All I/O requests to this 370X are quiesced
(purged). System continues processing.
Operator Response: Issue a VARY NET,ACT command to the
communications controller to reactivate the network.
32 dial digitst
~
NOT AVAIL 5
Explanation: This message is issued when the NCP has
selected a manual dial line for a call-out terminal represented
as xxx. DIALNO gives the number to be dialed (up to 32 digits)
or states that digits are not available.
System Action: System continues processing.
Operator Response: Perform the required dial operation.
Explanation: This message indicates that the specified
communications controller has entered system-slowdown
mode. For remotely attached communications controllers, xxx
is the VTAM node name.
System Action: Outbound I/O request scheduling is terminated
for the communications controller. VT~M .continues servicing
inbound processing from the communications controller.
Operator Response: No direct action required, but the system
programmer should be notified of this occurrence for possible
future system definition changes.
IST2121
NCP SLOWDOWN TERMINATED FOR xxx
Explanation: This message indicates that the specified
communications controller has terminated system-slowdown
mode. For remotely attached communications controllers, xxx
is a VTAM node name.
System Action: VTAM outbound I/O request scheduling is
resumed for the communications controller.
Operator Response: None.
NODE xxx REQUIRES MANUAL DIALING - DIAL
DIGITS UNDEFINED
Explanation: This message is issued when the NCP has
selected a manual dial line for a call-out terminal represented
as xxx, but the line is undefined in the host.
System Action: System continues processing.
Operator Response: If the dial digits and modem are known,
perform the required dial operation.
IST2191
AUTO NETWORK SHUTDOWN STARTED FOR xxx
xxx NCP CONFIGURATION IS INCOMPATIBLE WITH
VTAM
Explanation: During normal operations, the NCP detected an
incompatible host buffer, or VTAM detected an invalid resource
10.
System Action: The NCP is deactivated. If the error is
detected by the NCP, message IEAOOOI is also generated.
Programmer Response: Probable user error. Examine the
SYSGEN statements for NCP xxx and correct the invalid host
buffer specifications. If this is a VTAM-detected error, verify
that the NCP load module reflects the correct configuration.
Explanation: This message indicates that the specified
communications controller has begun auto-network shutdown.
For remotely attached communications controllers, xxx is the
VTAM node name.
System Action: Outbound I/O request scheduli~g (with th~ .
exception of RESETS) is suspended. VTAM continues servlc~ng
inbound processing from the communications controller untIl all
current data is processed.
Operator Response: No direct action required, but the system
programmer should be notified of this occurrence.
IST2201
I
xxx REMOTE 370X TRUNK-LINE FAILURE
Explanation: The NCP has incurred a permanent I/O error on
the trunk-line associated with remote communications
controller xxx.
Section 22: 1ST Messages - VTAM 22-17
VS2.03.801
System Action: VTAM automatically issues a VARY NET,INACT
I command to deactivate any and all communications controllers
attached to the failing trunk-line.
Operator Response: Probable hardware error. Issue a VARY
NET,INACT command for the failing trunk-line.
Problem Determination: Table I, items 2, 18, 30.
IST2671
RESTART OF xxxxxxxx FAILED
I
Explanation: A communications controller or SDLC cluster
I
I
controller with 'symbolic node name xxxxxxxx failed. VTAM has
attempted to restart it, but the restart failed. The previous
message indicates the reason for failure.
System Action: The communications controller or SDLC cluster
controller is deactivated.
Operator Response: Enter a VARY NET,ACT command for the
communications controller or the SDLC cluster controller
named xxx.
IST2681
IST2731
communications controller designated as xxx, but a permanent
I/O error was detected in communicating with the 370X. The
communications controller is unusable by VTAM.
System Action: System continues processing. VTAM rejects
the command and the communications controller remains
inactive.
Operator Response: Probable hardware error. Retry the loading
operation by reissuing a VARY NET,ACT command for this
node.
Problem Determination: Table I, items 2, 16, 18, 30.
IST2741
communications controller ERP has failed to load the
communications controller designated as xxx. The
communications controller should have been loaded with the
initial test program for the NCP, but a condition was
encountered that caused the operation to fail.
System Action: System continues processing. VTAM rejects
the command and the communications controller remains
inactive.
Operator Response: Probable hardware error. Reenter the
VARY NET command for this node.
Problem Determination: Table I, items 2, 18, 30.
RESTART OF xxx SUCCESSFUL
I
controller with the symbolic node name xxx failed, but was
successfully restarted by VTAM.
System Action: System continues processing~
Operator Response: None.
ATTEMPT TO ACTIVATE LINK xxx FAILED
I
Explanation: During ERP processing for a communications
IST2751
controller, an attempt was made to restart the NCP. The line
or link represented as xxx, which was previously active, could
not be activated.
System Action: Restart is terminated.
Operator Response: Issue a VARY NET,ACT command for the
NCP associated with this line or link. A previous message has
identified this NCP as being scheduled for restart.
IST2701
I an NCP reload after an ERP, the communications controller xxx
has been successfully loaded with the network control program
named mod.
System Action: System continues processing. The
communications controller is now ready for use.
Operator Response: None.
IN~UFFICIENT
STORAGE
Explanation: During a VTAM restart of an NCP, the restart
routines did not have sufficient storage to save registers.
System Action: Restart of the NCP is terminated.
Operator Response: Enter a VARY NET,ACT command for this
NCP. A previous message identified this NCP as being
scheduled for restart.
370X xxx NO INITIAL TEST - REPLY U TO BYPASS
- OR CANCEL
Explanation: A VARY NET,ACT command or the ERP attempted
to load the communications controller xxx, but the initial test
routine of the load utility program could not be used prior to
loading. The data set containing the initial test program was
inaccessible because of a permanent I/O error, or erroneous
or missing JCL.
System Action: VTAM waits for the user response. If the
response is U, the system attempts to load the
communications controller without .the initial test routine to
test the hardware. If the response is a blank, the load request
is canceled.
Operator Response: Enter U or blank.
Programmer Response: Check that the JCL for the VTAM start
procedure contains a DO statement with a ddname INITEST
and that the initial test program resides on SYS1.LlNKLIB.
IST2761
I
controller tried to restart the NCP, but an attempt to switch
the PEP line xxx to EP or NCP mode was unsucce·ssful because
of an I/O error.
System Action: Restart of the NCP is terminated.
Operator Response: Enter a VARY NET,ACT command for the
NCP associated with the line. A previous message identified
this NCP as being scheduled for restart.
IST2771
I
VS2 System Messages (VS2.03.801)
ATTEMPT TO SWITCH PEP LINE xxx to NCP FAILED
Explanation: The ERP procedures for a communications
IST272A
22-18
RESTART FAILED AVAILABLE
370X xxx NOW LOADED WITH LOADMOD mod
Explanation: In response to a VARY NET,ACT command, or to
I
370X xxx LOAD FAILED - INITIAL TEST HARDSTOP
Explanation: A VARY NET,ACT command or the
Explanation: A communications controller or SDLC cluster
IST2691
370X xxx LOAD FAILED - PERMANENT I/O ERROR
Explanation: The VARY NET command attempted to load the
ATTEMPT TO ACTIVATE LOGICAL UNIT xxx FAILED
During a VTAM restart of an NCP, an attempt to
activate the previously-active logical unit xxx has failed.
System Action: Restart of the SDLC controller is terminated.
Operator Response: Issue a VARY NET,ACT command for the
logical unit that failed to restart.
Explanation:
IST278A
I
INVALID REPLY FOR 370X xxx LOAD - ENTER U OR CANCEL
.
Explanation: The operator entered an invalid response to a
previous message (IST272A) asking whether the
communications controller xxx was to be loaded with a network
control program. The only valid responses are U (for use) or a
blank to cancel the request.
System Action: VTAM waits for a valid reply.
Operator Response: Probable user error. Examine the previous
messages about the specified communications controller and
then reply to this message with either U or a blank. Any other
reply causes this message to repeat.
VS2.03.801
IST282A
I
INVALID REPLY FOR 370X xxx DUMP - ENTER YES
OR NO
System Action: System continues processing. The dump
request is terminated.
Operator Response: Probable hardware error.
Problem Determination: Table I, items 2, 18, 30.
Explanation: The operator entered an invalid response to a
previous message (IST095A). The message informed him that
an ERP situation occurred on the communications controller
xxx and asked him whether he wanted a dump of that
communications controller. The only valid replies to this
message are YES and NO.
System Action: VTAM waits for a reply.
Operator Response: Enter YES if a dump is wanted, NO if not.
Any other reply causes this message to be reissued.
IST2831
IST2881
Explanation: In response to a MODIFY procname command
with the DUMP option, or before the reload of a failed network
control program, VTAM attempted to dump the NCP in the
communications controller xxx. The dump operation has
terminated because the data set named dsn cannot be opened.
System Action: VTAM continues processing. The dump request
is ignored.
Operator Response: Probable user error. Ensure that the
ddname dsn has not been misspelled and that the specified
JCt DD statement is included in the VTAM start procedure.
ATTEMPT TO SET TIME/DATE IN xxx FAILED
Explanation: During restart of the NCP, VTAM tried to set the
time and date in the NCP named xxx, but was unsuccessful.
System Action: Restart of the NCP is terminated. The NCP is
inactive.
Operator Response: Enter a VARY NET,ACT command for the
specified NCP.
IST284A
OPTION TO RELOAD 370X xxx AVAILABLE - REPLY
YES OR NO
I
Explanation: VTAM has found that the communications
I
I
IST2891
I
controller represented as xxx failed and requires reloading. The
operator may decide to reload or to proceed with the
communications controller inactive. If the controller remains
inactive, the part of the teleprocessing network that extends
outward from the communications controller is inoperative.
System Action: VTAM waits for a reply to this message. If the
reply is not valid, VTAM issues message IST290A and waits for
a reply.
Operator Response: If you want to reload the communications
controller to "attempt to recover from the ERP situation, press
the LOAD key on the communications controller and reply YES.
If not, reply NO.
I
IST2851
DUMP OF xxx COMPLETE
Explanation: The NCP named
xxx was successfully dumped to
the direct-access data set named by the DUMPDS parameter
of the PCCU macro instruction for that NCP. This occurred
either in response to a MODIFY procname command with the
DUMP option or before the reload of a failed network control
program.
System Action: System continues processing.
Operator Response: The dump may be formatted and printed
using the utility program IFLDUMP.
IST2861
Explanation: In response to a MODIFY procname command
with the DUMP option, or before the reload of a failing
communications controller, VTAM attempted to dump the NCP
with the network name xxx. The dump operation has
terminated because the output data set (specified as the
DUMPDS parameter of the PCCU macro instruction for the
specified NCP) is located on an unsupported device.
System Action: System continues processing. VTAM proceeds
normally except that the NCP dump is bypassed.
Operator Response: Probable user error. Ensure that the
designated data set resides on a direct access device.
IST290A
I
I
with the DUMP option, or before the reload of a failed network
control program, VTAM attempted to dump the NCP in
communications controller xxx. A permanent I/O error
occurred and a partial dump was created.
System Action: System continues processing. The dump
request is terminated.
Operator Response: The portion of the NCP dump that was
taken may be formatted and printed using the utility program
IFLDUMP.
INVALID REPLY FOR 370X xxx RELOAD - ENTER
YES OR NO
Explanation: "The operator made an invalid response to a
previous IST284A message. The message told him that an ERP
situation had occurred on the communications controller
represented as xxx and asked him whether he wanted to
reload and restart that communications controller. The only
valid responses to this and the previous message are· YES and
NO.
System Action: System continues processing. VTAM waits for
a reply.
Operator Response: Probable user error. Enter YES if a reload
and restart of the communications controller is wanted, NO if
the communications contr~lIer is to remain inactive. Any reply
other than YES or NO causes this message to be reissued.
IST2911
DUMP OF xxx TERMINATED - PERMANENT I/O
ERROR
Explanation: VTAM attempted to dump the communications
controller represented as xxx but encountered an
unrecoverable I/O error. The dump for thi~ 370X is a partial
one and is unusable.
370X xxx LOAD FAILED - NCP FAILURE IN 370X
I
Explanation: VTAM attempted to load the communications
I
controller represented as xxx with a network control· program,
but failed when an error was encountered.
System Action: System continues processing. VTAM
deactivates the communications controller.
Operator Response: Probable hardware error. Retry the VARY
NET,ACT command.
Problem Determination: Table I, items 2, 16, 18, 30.
IST2921
I
DUMP OF xxx TERMINATED - UNSUPPORTED
DEVICE TYPE
DUMP of xxx PARTIALLY COMPLETE
Explanation: In response to a MODIFY procname command
IST2871
DUMP OF xxx TERMINATED - dsn CANNOT BE
OPENED
370X xxx LOAD FAILED - ddn BLDL ERROR
I
Explanation: VTAM attempted to load the communications
I
controller represented as xxx but the operation failed; a BLDL
macro instruction issued for the library defined by the DD
statement ddn failed.
System Action: System continues processing. VTAM does not
activate the communications controller.
Section 22: 1ST Messages - VTAM 22-19
VS2.03.801
Operator Resonse: VTAM operations can continue with other
IST2971
nodes in the network.
Programmer Response: Look at the directory of the partitioned
data set defined by the specified DD statement. If it is the
NCP module library, ensure that the NCP being loaded into the
indicated communications controller is a member of that
library. The NCP name is defined by the NEWNAME operand
on the NCP BUILD macro instruction. If ddn defines the initial
test library, ensure that modules IFL3705D and IFL3705B are
members of that library.
Problem Determination: Table I, item 25c.
IST2931
370X xxx LOAD FAILED - ddn RECORD SIZE TOO
LARGE
Explanation: VT AM attempted to load a network control
program into the communications controller xxx, but the
operation failed because the NCP load module mod is too
large for the storage space in the communications controller.
System Action: System continues processing. VTAM
deactivates the communications controller.
Programmer Response: Probable user error. Check the NCP
generation for errors or unnecessary use of storage.
Regenerate the NCP so that it fits into the communications
controller.
IST2981
Explanation: VT AM attempted to load the communications
controller represented as xxx with a network control program,
but the operation failed because the format of the data
defined by the DD statement ddn is invalid.
System Action: System continues processing, but VTAM
deactivates the communications controller.
Operator Response: Notify the system programmer.
Programmer Response: Probable user error. Check the format
of the NCP load module and the NCP initial test data set. If
the record size is larger than 1024 bytes, re-link-edit with the
DC parameter.
IST2941
370X xxx LOAD FAILED - INVALID DEVICE TYPE
DEFINITION
370X xxx LOAD FAILED - mod TOO LARGE FOR
370X
370X xxx LOAD FAILED - PERMANENT I/O ERROR
ON ddn
Explanation: VTAM attempted to load the communications
controller represented as xxx, but failed when a permanent I/O
error occurred on the data set defined by the DO statement
ddn (either the NCP library or the initial test .library).
System Action: System continues processing. VTAM
deactivates the communications controller.
Operator Response: Reenter a VARY NET,ACT command for
the NCP associated with the specified communications
controller. If the error persists, notify the system programmer.
Programmer Response: Probable hardware error. Create the
NCP library or the NCP initial test library on a different disk
pack if possible, and retry the VARY NET command.
Problem Determination: Table I, items 2, 18, 30.
Explanation: VTAM attempted to load the communications
I
controller represented as xxx, but failed after checking the
communications controller UCB and determining that it had not
been defined during SYSGEN with a valid channel adapter type.
System Action: System continues processing. VTAM does not
activate the communications controller.
Operator Response: Probable user error. Check the CUA
specified for the communications controller to make sure it is
the correct address. If it is, the communications controller
might have been incorrectly specified during the operating
system generation.
I
IST2951
I
370X xxx LOAD FAILED - UNEXPECTED END OF
FILE ON dsn
370X xxx LOAD FAILED - ddn COULD NOT BE
OPENED
Explanation: VTAM attempted to load/restart the
communications controller represented as xxx, but failed
because the data set defined by the DO statement ddn could
not be opened.
System Action: System continues processing. VTAM
deactivates the communications controller.
Programmer Response: Probable user error. Make sure that
the DO statement ddn is included in the VTAM start procedure
and is specified correctly.
IST3001
opr OF xxx TERMINATED - INSUFFICIENT STORAGE
Explanation: VT AM attempted to load a network control
-Explanation: VTAM attempted the opr operation, which can be
program into the communications controller xxx, but failed
when an unexpected end-of-file occurred on data set dsn.
System Action: System continues processing. VTAM does not
activate the communications controller.
Programmer Response: Probable user error. Make sure the DO
statement that specifies the data set dsn is correct and that
the NCP being loaded is the right one for the communications
controller hardware.
to dump, load, or reload the NCP named xxx. The indicated
operation has terminated because of a lack of available virtual
storage.
System Action: If this message is the result of a MODIFY
procname or VARY NET command, th'e command is terminated.
If the message is the result of an NCP restart, the restart is
terminated. In all cases the NCP is deactivated.
Operator Response: If opr is DUMP, reissue the MODIFY
procname command with the DUMP option. If. opr is either
LOAD or RELOAD, enter a VARY NET,ACT command for node
I
IST2961
370X xxx LOAD FAILED - UNEXPECTED CODE rc
FROM IFLOADRN
Explanation: VTAM attempted to load a network control
I program into the communications controller represented as
I
IST2991
xxx, but failed when it received an unexpected return code rc
from the NCP load utility program IFLOADRN.
System Action: System continues processing. VTAM does not
activate the communications controller.
Operator Response: None.
Problem Determination: Table I, items 2, 29.
22-20
VS2 System Messages (VS2.03.801)
xxx.
Programmer Response: Probable user error. This message
indicates that storage requirements for VTAM were
underestimated. Check the storage estimates and increase
storage allocation where possible.
IST3021
INVALID DEFINITION TYPE IN MEMBER mem IN
VTAM DEFINITION LIBRARY
Explanation: mem is a member name on SYS1.VTAMLST which
contains a major node definiton of the same name. The
definition statement or macro instr:uction used was not a valid
VT AM definition type. Valid types are LOCAL, APPL and PCCU
only.
VS2.03.801
System Action: System continues processing. Major node mem
is not included in the VTAM network.
Programmer Response: Probable user error. Correct the invalid
macro instruction and update SYS1.VTAMLST to correct
configuration definition memo
IST3031
INSUFFICIENT STORAGE TO BUILD CONFIGURATION
xxx
Explanation: VTAM system definition -has terminated
processing on xxx which is a configuration definition on
SYS1.VTAMLST. Processing was terminated because the
storage required for internal VTAM tables associated with that
major node was not available.
System Action: System continues processing. Configuration xxx
is not included in the VTAM network.
Operator Response: Stop VTAM by a HALT NET command,
re-IPL and increase the size of CSA. Otherwise, wait until the
activity in VTAM has decreased; then attempt the operation
again.
Caution: Increasing the size of CSA reduces the size of each
address space's private area, possibly causing other jobs to
fail for lack of storage.
Programmer Response: Probable user error. This message
indicates that storage requirements for VTAM were
underestimated in association with the network required. Check
all estimates and increase storage allocation where possible, to
avoid repetition of the message.
IST3041
VTAMOBJ IS NOT OPEN - VTAMLST WILL BE USED
FOR CONFIGURATION
are invalid. Types of errors detected are incorrect length and
incorrect identifier.
System Action: System continues processing. VTAM system
definition continues by using SYS1.VTAMLST for this
configuration.
Programmer Response: Delete the specified member from
SYS1.VTAMOBJ. During the next execution of VTAM network
definition (called by VARY NET or START VTAM), a new entry
is created from the configuration on SYS1.VTAMLST.
IST3071
I/O ERROR ADDING MEMBER mem TO VTAMOBJ MEMBER NOT ADDED
Explanation: VTAM system definition attempted to add
member mem to the configuration definitions on
SYS1.VTAMOBJ. Because of a permanent I/O error, the
member was not added.
System Action: All VTAM and system processing continues
normally. Since member mem was not added to
SYS1.VTAMOBJ, VTAM uses the configuration definition on
SYS1.VTAMLST.
Programmer Response: Probable hardware error. All
processing can continue, but VTAM system definition would run
more efficiently if the preprocessed configuration were written
on SYSl.VTAMOBJ.
Problem Determination: Table I, items 2, 18, 30.
IST3081
NO SPACE IN VTAMOBJ DIRECTORY - MEMBER
mem NOT ADDED
Explanation: VTAM system definition attempted to add a
SYSl.VTAMOBJ for preprocessed configuration definitions
stored there, but SYS1.VTAMOBJ failed to open. VTAM
attempts to complete processing by using the unprocessed
definitions from SYS1.VTAMLST.
System Action: VTAM system definition continues by using
SYS1.VTAMLST for configuration processing.
Programmer Response: Probable user error. Either a
SYSl.VTAMOBJ data set was not provided, or the VTAM start
procedure does not contain an appropriate DO statement for
the data set. Although processing can continue using
SYSI.VTAMLST, the VTAM system definition processing would
be more efficient if SYS1.VTAMOBJ were available for use.
preprocessed configuration definition to SYS1.VTAMOBJ.
Because there was no space. in the directory of
SYS1.VTAMOBJ for the member mem, the configuration was
not added.
System Action: All VTAM and system processing continues
normally. Since the specified member was not added to
SYS1.VTAMOBJ, VTAM uses the configuration definition on
SYS l.VTAM LST.
Programmer Response: Probable user error. All processing can
continue, but VTAM system definition would run more
efficiently if the preprocessed configuration were written on
SYS1.VTAMOBJ. The installation should make space available
in the directory either by deleting unwanted entries or by
adding more space to the directory of SYS1.VTAMOBJ.
IST3051
IST3091
Explanation: VTAM system definition attempted to search
I/O ERROR ON mem MEMBER OF VTAMOBJ VTAMLST WILL BE USED
Explanation: VTAM system definition attempted to reference
member mem of SYSl.VTAMOBJ but failed because of an I/O
error. VTAM tries to continue by using SYSl.VTAMLST to
recreate the configuration definition skeleton which was stored
on SYS1.VTAMOBJ.
System Action: System continues processing. VTAM system
definition continues by using SYS1.VTAMLST for this
configuration.
Programmer Response: Probable hardware error. When a
member of SYS1.VTAMQBJis in error and the configuration is
obtained from SYSl.VTAMLST, a subsequent attempt is made
to add the new member on SYSl.VTAMOBJ. Follow the
problem determination action if the error recurs.
Problem Determination: Table I, items 2, 16, 30.
IST3061
INVALID ENTRY IN MEMBER mem OF VTAMOBJ VTAMLST USED
UNABLE TO LOAD MODULE mod FROM LIBRARY lib
Explanation: VTAM system definition attempted to load a
communications controller NCP module named mod from the
library lib, but th3 load operation failed. The commu.nications
controller associated with this module/library combination
cannot be activated. The last character of the module name is
either B or R and can be interpreted as follows:
• If B, this module contains the BHSET produced by the NCP
system generation.
• If R, this module contains the resource resolution table
(RRT) produced by the NCP system generation.
System Action: System continues processing. The major node
being processed is not included in the VTAM network.
Programmer Response: Probable user error. Inspect library lib
for missing or misnamed modules. If module mod is missing,
assume that the NCP system generation did not complete
sucessfully. Examine the NCP SYSGEN output, correct the
SYSGEN, and have the operator retry the operation.
I
Explanation: VTAM system definition attempted to use the
IST3101
preprocessed configuration that was stored in member mem of
SYS 1.VTAMOBJ and found that the contents of the member
Explanation: As a result of a VARY NET,ACT command, VTAM
INVALID SPACE REQUEST FOR CONFIGURATION xxx
is building a resource definition table (ROT) fQr major node
Section 22: 1ST Messages - VTAM 22-21
•
VS2.03.801
xxx. VTAM cannot proceed because an entry is encountered
which does not fit in the predetermined build area.
System Action: System continues processing. Configuration xxx
is not included in the VTAM network.
Operator Response: Probable software error. Retry the VARY
NET,ACT command on this configuration. If problem persists,
follow the problem determination action.
Problem Determination: Table I, items 6, 29.
IST3111
NCP .LOAD MODULE LIBRARY lib - FAILED TO OPEN
Explanation: VTAM attempted to open the communications
I
controller network control program load module library named
lib, but the open operation failed.
System Action: System continues processing. No
communications controller whose NCP SYSGEN output is on
the specified library can be activated.
Programmer Response: Find out why this library failed to open
and correct the problem before the operator issues a VARY
NET,ACT command for those communications contrQllers.
IST3121
VTAMOBJ NOT UPDATED FOR CONFIG xxx INSUFFICIENT STORAGE
Explanation: VT AM network definition, in attempting to add a
preprocessed configuration definition to SYS1.VTAMOBJ data
set, was unable to obtain storage for its I/O buffer for the
definition text.
System Action: VTAM and network definition continue
normally. The update to SYS1.VTAMOBJ is bypassed and a
subsequent VARY NET,ACT command to this configuration is
processed using the definition from SYS1.VTAMLST.
Operator Response: If recurrence of this message is causing
an operational problem, notify the system programmer.
Otherwise continue normal· operation.
Programmer Response: Probable user error. Check the system
sub pool allocation (not VTAM buffer pools) within the VTAM
partition for adequate storage.
IST3131
VARY FAILED FOR ID = xxxxxxxx - ACTIVATE
ALREADY IN PROGRESS
Explanation: An activate is already in progress and has not
completed prior to the issuance of a second activate
command.
System Action: The command is rejected;
Operator Response: None.
VTAM definition statement, update SYS1.VTAMLST to correct
the definition of the specified configuration.
IST3211
CONFIGURATION xxx DEFAULT TAKEN - yyy
Explanation: While activating the configuration represented by
xxx, VTAM encountEfred an error in an NCP generation macro
instruction or VTAM definition statement. The cause of the
error (represented· by yyy) is one of the following:
• INVALID PARAMETER
• INVALID VALUE
• MISSING PARAMETER
• EXTRA VALUE
• DUPLICATE PARAMETER
• COMBINATION ERROR
• EXTRA PARAMETER
A second message (lST3231) provides details of the error.
System Action: VTAM assumes the appropriate default(s) and
continues processing.
Programmer Response: Probable user error. Use the
information in this message and in IST3231 to correct the
macro statement in error.
IST3221
CONFIGURATION xxx ERROR IGNORED - yyy
Explanation: While activating the configuration represented by
xxx, VTAM encountered an error in an NCP generation macro
instruction or VTAM definition statement. The cause of the
error (represented as yyy) is one of the following:
• INVALID MACRO
• SYNTAX ERROR
• INVALID PARAMETER
• EXTRA VALUE
• EXTRA PARAMETER
• INVALID VALUE
• COMBINATION ERROR
A second message (lST3231) provides details of the error.
System Action: VTAM continues processing the macro
instruction or definition statement and disregards the error
situation.
Programmer Response: Probable user error. Use the
information in this message and in IST3231 to correct the
macro statement in error.
IST3231
LABEL: Usb - MACRO TYPE: mac - KEYWORD:
keywd
Explanation: This message supplements messages IST3201,
IST3201
CONFIGURATION xxx DEFINITION FAILED - yyy
Explanation: While activating the configuration represented by
xxx, VTAM detected an error in an NCP generation macro
instruction or VT AM definition statement. The cause of the
error (represented by yyy) is one of the following:
• INVALID PARAMETER
• INVALID VALUE
• SYNTAX ERROR
• DUPLICATE MACRO
• MISSING PARAMETER
• MISSING MACRO
• PARAMETER CONFLICT
• SEQUENCE ERROR
A second message (lST3231) provides details of the error.
System Action: System continues processing. The specified
configuration is not added to the VT AM network.
Programmer Response: Probable user error. Use the
information in this message and in IST3231 to correct the
macro statement in error. If the error is in an NCP generation
macro instruction, regenerate the NCP. If the error is in a
22-22
VS2 System Messages (VS2.03.801)
IST3211, and IST3221.
lab is the name or label of the macro instruction or statement
in error.
mac is the type of macro instruction or statement.
keywd is the actual keyword (or the first eight characters of
the keyword) that is in error.
System Action: The action carried out is given in the message
immediately before this (lST3201, IST3211, or IST3221).
Programmer Response: The response is given in the message
immediately before this (lST3201, IST3211, or IST3221).
IST3301
CONFIGURATION xxx BYPASSED - LOGTAB
INVALID
= yyy IS
Explanation: VTAM cannot load the interpret table named yyy
(as specified in the LOGTAB operand) from SYSl.LPALlB either
because the table does not exist or because an I/O error
occurred during the loading operation.
System Action: System continues processing. The
configuration represented as >Q
Source Exif Data:
File Type : PDF
File Type Extension : pdf
MIME Type : application/pdf
PDF Version : 1.3
Linearized : No
XMP Toolkit : Adobe XMP Core 4.2.1-c043 52.372728, 2009/01/18-15:56:37
Create Date : 2012:06:07 19:00:35-08:00
Modify Date : 2012:06:08 05:53:13-07:00
Metadata Date : 2012:06:08 05:53:13-07:00
Producer : Adobe Acrobat 9.51 Paper Capture Plug-in
Format : application/pdf
Document ID : uuid:47f080e7-aff9-41a9-819d-d2e8e5c7cb46
Instance ID : uuid:8cfc51fa-61c3-4811-ac56-c16785462c13
Page Layout : SinglePage
Page Mode : UseNone
Page Count : 458
EXIF Metadata provided by EXIF.tools