SC19 6204 4_VM_SP_System_Messages_and_Codes_Release_5_Dec86 4 VM SP System Messages And Codes Release 5 Dec86

User Manual: SC19-6204-4_VM_SP_System_Messages_and_Codes_Release_5_Dec86

Open the PDF directly: View PDF .
Page Count: 609

Download
Open PDF In Browser	View PDF

--..---- -----------------,,-.

Virtual Machine/
System Prod uct
System Messages and Codes
Release 5
SC 19-6204-4

Fifth Edition (December 1986)
This edition, 8C19·6204·4, is a revision of 8C19·6204·3, and applies to Release 5 of
the IBM Virtual Machine/System Product (VM/8P) and to all subsequent releases
until otherwise indicated in new editions or Technical Newsletters. Changes are
periodically made to the information contained herein; before using this
publication in connection with the operation of IBM systems, consult the latest
IBM System/370. 30xx. and 4300 Processors Bibliography, OC20·0001, for the
editions that Ilre applicable and current.

Summary of Changes
For a list of changes, see page 579.
Technical changes and additions to text and illustrations are indicated by a
vertical line to the left of the change.

References in this publication to IBM products, programs, or
services do not imply that IBM intends to make these available in
all countries in which IBM operates. Any reference to an IBM
licensed program in this publication is not intended to state or
imply that only IBM's licensed program may be used. Any
functionally equivalent program may be used instead.
Ordering Publications
Requests for IBM publications should be made to your IBM representabve or to
the IBM branch office serving your locality. Publications are not st()ck(~d at the
address given below.
A form for reader's comments is provided at the back of this publication. If the
form has been removed, comments may be addressed to IBM Corporation,
Information Development, Dept. G60. P.O. Box 6, Endicott, New York, U.S.A.
13760. IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
The form for readers' comments provided at the back of this publieation may also
be used to comment on the VM/SP online HELP facility.
© Copyright International Business Machines Corporation 1982. IH83, 1984, 1985,
19~6

Preface
This publication is a reference manual designed for all users. It contains
messages and codes produced by the IBM Virtual Machine/System Product
(VM/SP).
This publication contains three sections: Introduction, System Codes, and
System Messages.
The "Introduction" contains:
•
•
•

The format of messages VM/SP generates
Syntax conventions this publication uses
CP problem determination procedures

The "System Codes" are divided into the following categories:
•
•
•
•
•
•
•
•

Return Codes
CP wait state codes
Loader wait state codes
Stand-alone dump facility wait state codes
CP abend codes
CMS abend codes
GCS abend codes
TSAF abend codes.

The "System l\1essages" section of this publication is divided as follows:
•
•
•
•
•

Control Program (CP) Messages
Conversational Monitor System (eMS) Messages
Interactive Problem Control System (IPCS) Messages
Group Control System (GCS) Messages
Transparent Services Access Facility (TSAF) Messages.

Preface

111

VM/SP System Messages and Codes

Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VM/SP Message Format ......................................
VM/SP System Product Editor Messages .......................
Messages With 4nxx Identifiers ..............................
Unnumbered Responses ....................................
VM/SP Message Syntax Conventions ............................
Displaying Messages at the Terminal ............................
Displaying Messages in Other Languages ........................
CP Problem Determination ....................................
General User Action .......................................
System Operator Action ....................................

1
1
2
2
3
3
5
6
6
7
7

System Codes . . . . . . . . . . . . . . . . .
9
Return Codes .............................................. 9
Return Codes Produced by the CP DIRECT Command ............ 10
Sample Return Code from a CP Command ..................... 11
Return Codes Produced by the CMS DDR Command ............. 12
Return Codes Produced by IPCS ............................. 12
CP Wait State Codes ........................................ 13
Loader Wait State Codes .................................... 23
Stand-Alone Dump Facility Wait State Codes .................... 26
Stand-Alone Dump Program Generation Wait State Codes ......... 26
Stand-Alone Dump Program Execution Wait State Codes ......... 28
Normal Waits ........................................... 30
CP Abend Codes ........................................... 32
System Operator Action ................................... 32
System Programmer Action ................................ 33
CMS Abend Codes ......................................... 63
GCS Abend Codes .......................................... 69
Responding to Abends in GCS .............................. 69
Overview of Problem Determination Facilities .................. 69
TSAF Abend Codes ........................................ 101
>

Control Program (CP) Messages

•

••

. . . . . . . . . . . . . . . . . . . . . . . . . 105

Conversational Monitor System (CMS) Messages

. . . . . . . . . . . . 233

Interactive Problem Control System Extension (IPCS) Messages

473

Group Control System (GCS) Messages . . . . . . . . . . . . . . . . . . . . 491
Transparent Services Access Facility (TSAF) Messages

549

Other Messages

567
Contents

CMS EDIT Messages ......................................
DEBUG Messages .........................................
CMS EXEC Messages ......................................
EXEC 2 Messages .........................................
System Product Interpreter Messages ..........................

567
575
578
578
578

Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary of Changes to SC19-6204-4 for VM/SP Release 5 ..........
Addition .of messages from new VM/SP components .............
Other Additions and Enhancements .........................
Summary of Changes to SC19-6204-3 for VM/SP Release 4 ..........
Split of this Publication ..................................
Addition of messages from new VM/SP components .............
Other Additions and Enhancements .........................
Summary of Changes to SC19-6204-2 for VM/SP Release 3 ..........

579
579
579
579
581
581
581
581
582

Glossary of Terms and Abbreviations . . . . . . . . . . . . . . . . . . . . . 585
Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589

VM/SP System Messages and Codes

Figures
1.

2.
3.
4.

5.
6.
7.
8.
9.
10.
11.
12.

Types and Meanings of Severity Codes ...................... 2
Selected Message Variables ............................... 4
CP Error Message Numbers ............................... 6
Return Codes Produced by the CP DIRECT Command .......... 11
Example of a CP LINK Command ......................... 11
Return Codes Produced by the CMS DDR Command ........... 12
Return Codes Produced by IPCS .......................... 12
Wait Codes Upon Loader Termination ...................... ~3
CP Abend Codes ....................................... 34
CMS Abend Codes ..................................... 64
GCS Abend Codes ...................................... 71
TSAF Abend Codes .................................•.. 102

Figures

Vll

Vlll

VM/SP System Messages and Codes

Introduction
This section describes:
•

The format of messages VM/SP generates.

•

Syntax conventions used in this publication.

•

CP problem determination procedures.

VM/SP Message Format
Messages consist of a message identifier (for example~ DMKCQG020E) and
message text. The identifier distinguishes messages from each other. The
text is a phrase or sentence describing a condition that has occurred or
requesting a response from the user.
The message identifier consists of four fields: a prefix, a module code, a
message number, and. a severity code. The format of the message identifier
IS:

xxxmmm###s or xxxmmm####s
where:
xxx

is the prefix.
•
•

•
•
•
mmm

~Ilessages

are prefixed as follows:

CP messages -- DMK
C1\iS messages -- DMS
IPCS messages -- DMiv.l
GCS messages -- CSI
TSAF messages -- A TS.

is the module code. three characters that indicate which
module generated the message. This field is usually an
f1.bbreviation of the name of the module in which the error
:.·,~curred.

### or #### is the message number. three or four digits that are associated
with the condition that caused the message to be generated.

Introduction

is the severity code, a letter that indicates what kind of
condition caused the message. The definition of the severity
codes depends on the nature of the routine producing the
message.

Figure 1 summarizes the message severity codes for each of the four VM/SP
components.
Prefix
CP Commands (DMK)

CMS Commands (DMS)

Code
A
I
W
E
R
I

IPCS Commands (DMM)

GCS Commands (CSI)

TSAF Commands (ATS)

E
S
T
R
I
E
S
R
I
E
S
T
R
I

W
E
S
T
Figure 1..

Meaning
Immediate action required
Information only
Warning or System Wait
Error
Response
Information only
Warning
Error
Severe Error
Terminating error
Response
Information only
Error
Severe error
Response
Information only
Error
Severe error
Terminating error
Response
Information only
Warning
Error
Severe error
Terminating error

Types and Meanings of Severity Codes

VM/SP System Product Editor Messages
Error messages for the System Product Editor are located in the CMS
section of this publication. VM/SP System Product Editor messages are
spread between message numbers 497E and 700E. However, the messages
within the 500 range (DMSmmm500E - DMSmmm599S) are only System
Product Editor messages.

Messages With 4nxx Identifiers
All messages issued from the CMSBAM discontiguous shared segment, as
well as many of the messages issued from the CMSVSAM and CMSAMS
discontiguous shared segment are identified by a 4nxx prefix. The text of
these messages is inVSE format rather than the standard CMS format.
Explanations for these messages are not in this manual. The appropriate
message manual to be used for reference for 4nxx prefix messages is

VM/SP System Messages and Codes

determined by the associated acceR~ nethod. Messages relating to
Sequential Access Method (SAM) &.(e described in VSE/ Advanced
Functions Messages. Messages relating to Virtual Storage Access Method
(VSAM) are described in VSE/VSAM Messages and Codes.

Unnumbered Responses
All normal, unnumbered responses indicating the successful completion of a
command (such as ready messages) are included in the following
publications:

•
•

VM/SP CP Command Reference (CP commands) and
VM/SP C1vIS Command Reference (eMS commands).

Unnumbered responses can also be the result of executing system
generation macro instruction or service programs. These responses,
referred to as MNOTES, are documented in logic listings only.

VM/SP Message Syntax Conventions
The syntax used in the VM/SP messages as printed in this book is as
follows:
1.

For uppercase messages (some CP, some CMS, some TSAF, and all IPCS
messages), variables are denoted by lowercase; for mixed-case messages
(most CP, most eMS, most TSAF, and all GCS messages), variables are
denoted by italics. These variable names are replaced at execution time
with the information they describe.

Note: There may be situations where the same message is displayed in
both mixed and uppercase. This happens when many modules issue the
same message, but the case of the text is coded differently in each
module.
See Figure 2 on page 4 for a partial list of variables used in this
publication. (This table does not contain every message variable, just
those that might be a little more difficult to identify.)
2.

Any quote (') in message text in the manual will be displayed when the
message appears on your screen.

Anything within braces {... i... } indicates alternate text that will be
selected at execution time.

Anything within brackets [... J may be optionally left out, depending on
the condition arising.

Introduction

Variable
a ...
bbcchh
cc
cchhr
char
col
cm
cpuid
csw
date
devclass
devname
devtype
execname
exectype

Meaning
alphabetic or numeric information
bin, cylinder, and head
cylinder number
cylinder, head. record
character
column
command code, in hexadecimal
central processing unit identification
channel status word
system date
class of IBM device

fileid

mnemonic name for an IBl\tl device type
IBM device type
filename of an exec
file type of an exec
fn ft fHfm"

fm
fn
ft
hexloc
imagelib

filemode
filename
filetype
hexadecimal location
3800 printer image library

libname
lrecl
membername
mode

library name
logical record length
library member name
mode letter, or mode letter and mode
number
module name code
decimal information
node of a user

mmm
n ...
nodeid
page
pathid
prefix
psw
range
rdev

page number
virtual machine path identification
prefix subcommand or macro
program status word
range (of addresses or registers)

recfm

real device address (formerly 'raddr' or
'cuu')
record format

rid

resource identifier

Figure 2 (Part 1 of 2).

VM/SP System Messages and Codes

Selected Message Variables

Variable
routine
rr
rstor
segname
sense
spoolid
storarea
subl.book
svc
sysname
vdev
vname
volid
vstor
wname
x ...
yyyy

Meaning
CMS or GCS routine
record number
real storage address
segment name
sense bytes
spool file identification
storage area
a book of a sublibrary
supervisor call number
system name
virtual device address (formerly 'vaddr'
or 'cuu')
virtual screen name
volume serial number
virtual storage address
window name
hexadecimal information
reason code (GCS abend)

Figure 2 (Part 2 of 2).

Selected Message Variables

Displaying Messages at the Terminal
When you log on to VMjSP at your terminal, the default setting for the
display of messages is TEXT. This means that only the text portion of the
message appears when the message ,is displayed. The message identifier is
not displayed.
Since this book is organized by message numbers within component codes,
it wiU be difficult for you to find the explanations of messages if you search
through the book for the message text. Therefore, you should issue the CP
command SET EMSG ON after you log on. This command causes the
message id~ntifier to be displayed along with the text.

Note: If you do not use the SET EMSG ON command, you can still
determine the message identifier by referring to "Message Text-to-Message
Identifier Cross-Reference" in System Messages Cross-Reference. This
section has the messages listed in alphabetical order by message text, along
with the identifier.
In some cases, the text of a message is longer than a line on the display
screen. The message text may be divided in the middle of a word and
continued on the next line.

Introduction

Displaying Messages in Other Languages
All messages are documented in this book in American English;. however,
most messages are displayed at your terminal in the Janguage set for your
virtual machine. If your virtual machine is set to another language (either
by the SET LANGUAGE command or the OPTION LANG directory
statement), you will receive most VM/SP messages in that language.

CP Problem Determination
CP error messages are divided into several categories according to the
message number (nnn of the identifier xxxmmmnnns). See Figure 3 for a
complete list of message numbers and related functions.
Numbers Related Function
001-349
CP commands and console
functions
350-399

Nucleus loading

400-424

Paging

425-449

Spooling

450-474

Dispatching and service routines

475-499

Directory routine

500-549

Input/output error recovery

550-599

Input/output error recording

600-649

Machine check recovery

650-699

Reserved for IBM use only

700-729

DDR (dump restore) service program

730-749

FMT (format) service program

750-799

DIR (directory) service program

800-849

Reserved for IBM use only

850-899

DMM (VMFDUMP) service routine

900-999

Checkpoint. warm start, dump
initialization

Figure 3.

CP Error Message Numbers

VM/SP System Messages and Codes

Received By
General Users

Primary
System
Operators

System
Support
Personnel

General User Action
If in the normal use of CP commands error messages in the range of 001 to
349 persist., you should perform the following steps before contacting your
Rystem representative for programming assistance.
1.

Keep the terminal sheet that identifies the problem.

Attempt to reproduce the problem, making sure that the full error
message function is in effect by issuing t.he CP command:
SET EMSG ON

Obtain the virtual machine's current configuration by issuing the CP
command:
QUERY VIRTUAL

Where appropriate, and depending upon conditions, obtain a virtual
storage dump by issuing the CP command:
VMDUMP Q-END
or
DUMP Q-END

System Operator Action
System operators (classes A, B, C, and D) who observe problems with CP
commands should do the following:
1.

Keep the console output sheet identifying the problem.

Attempt to reproduce the problem with full error message by issuing the
CP command:
SET EMSG ON

Obtain the real machine's configuration status by issuing the CP
command:
QUERY ALL

Reissue the CP command that has been causing the errors. If the
problem recurs, force a CP ahend dump by pressing the REST ART key
(not RESET). This technique automatically suppresses tracing while
storage is being dumped. When the system restarts, use the VMFDUMP
command to format and print the dump.

Caution: This will cause a system restart and all users must log on
again. The advantage of using this technique is that it provides you
with a formatted dump.
If it is too disruptive to log off all users, you can obtain a dump using
the CP command DMCP, which allows all users to remain logged on.
Such a dump goes directly to the printer and is not formatted.

Introduction

Note: You must weigh the advantages and disadvantages of both
techniques.
5. If you use the DMCP command, first reissue the CP command causing
the problem. Then enter "alter/display" mode and display the following:
a.
b.
c.

DP - PSW
D G - General registers
D C - Control registers

Next, use the class A CP command MONITOR STOP CPTRACE to turn
off tracing. Otherwise, the dump would show the dumping activity in
the trace table.
Then obtain the dump by issuing:
DMCP O-END

Last, turn tracing back on by issuing the CP command MONITOR
START CPTRACE.

Note: If you do not have privilege class A, you ca.n stop tracing by
issuing the class C command STCP to store X'OOOO' at location X' 400'.
Resume tracing by storing X'FFFF' at location X'400'.
Refer to the VM/SP Library Guide, Glossary, and Master Index, GC19-6207,
for unfamiliar terms used in this publication.

VM/SP System Messages and Codes

System Codes

Return Codes
A return code of zero is passed to register 15 if no warning messages, error
messages, severe error messages, or terminal error messages are generated
during execution of a command.
If however, during execution of a command, a condition arises that results

in the display of a warning message, error message, severe error message,
or terminal error message, the command passes a nonzero return code to
register 15.
Commands that invoke program products pass a nonzero retu.rn code to the
user. This return code has been redefined by the program product or
compiler in operation.
The following list does not contain all return codes. Other return codes are
shown in the descriptive text of the issuing message.

Code

Meaning

-0001

No CP command with this name was found. (The CP error code of
+ 1 is converted by CMS to -0001 for commands entered from the
virtual console.)

-0002

An attempt was made to execute a CMS command while in CMS
subset mode, which would have caused the module to be loaded in
the user area (LOADMOD error code 32).

-0003

No CMS command issued from EXEC was found with this name, or
an invalid function occurred when the SET or QUERY command
was issuerl from EXEC with IMPCP active.

-0004

The LOADMOD failed (for example, there was an error in the
module).

-0005

A LOADMOD was attempt.ed in the wrong environment (for
example, the module was generated by thE' GENMOD command with
the OS option, and LOAD:rvIOD was attempted with DOS = ON
specified).

System Codes

The user did not specify all the conditions necessary to execute the
command as intended. Execution of the command continues, hut the
result mayor may not he as the user intended.

Device errors occurred for which a warning message is issued, or
errors were introduced into the output file.

Errors were found in the input file.

There was an invalid character in the fileid. Valid characters are:
0-9, A-Z, $, (~!, #, and a-z.

The user did not correctly specify the command line.

An error occurred while the system tried to access or manipulate a
user's files.

The user's file was not in the expected format, or the user's file did
not contain the expected information, or an attempt was made to
execute a LOADMOD command while in CMS subset mode. This
caused the module to be loaded in the user area.

An error occurred in the user's devices. For example, a disk was in
read-only status, and needed to be in write status in order to write
out a file.

The user failed to supply all the necessary conditions for executing
the command, or an end of file or end of tape was reached.

Insufficient storage was available for execution of the command.

A CMS system restriction prevented execution of the command, or
the function requested is an unsupported feature, or the device
requested is an unsupported device.

100

Input/output device errors.

104

A functional error for which the system is responsible occurred
during execution of the command.

256

An unexpected error for which the system is responsible (Terminal
Error) occurred during execution of the command.

Return Codes Produced by the CP DIRECT Command
Return codes produced hy the CP DIRECT command are listed in Figure 4.
xx is the CMS routine return code.

VM/SP System Messages and Codes

Code Meaning
1
Invalid filename, or file not found
2
Error loading the directory
Invalid option from CMS
3
Directory not swapped; user not class A, B, or C
4
Directory not swapped; system (old) directory locked
5
Directory not swapped; the directory in use by the system
6
is not the directory that was updated
lxx Error in the CMS RDBUF routine
2xx Error in the eMS TYPLIN routine
Figure 4.

Return Codes Produced by the CP DIRECT Command

Sample Return Code from a CP Command
Figure 5 shows an example of the CP LINK command invoked from CMS
mode. Commands or functions of commands passed to CP, in turn, pass the
return code (via CP) to register 15.

ipl ems
VM/SP CMS - mm/dd/yy hh:mm
cp link to * vaddr 1 as vaddr2 r

Figure 5.

Example of a CP LINK Command

The user has entered the CP LINK command to userid *. The user's own
directory will be searched for device vaddrl. Vaddr2 is the virtual address
assigned to the device for this virtual machine. Read~only access is
requested. No password is required because the user has linked to one of
his own disks.
The result will be one of the following:

R;
R(nnnnn);

a successful execution.
indicating an error (where 'nnnnn' is the return code).

Return codes can be used by system programmers in the DEBUG
subcommand and also in EXEC procedures. See the VMj SP eMS
Command Reference for a description of the &RETCODE special variable.
The return codes associated with each command directly correspond to the
message numbers. For example, if you received a return code of 22 when
executing the LINK command. you could look at the description for
message nUITlber 022:
DMKLNM022E Virtual device address missing or invalid

System Codes

Return Codes Produced by the CMS DDR Command
The CMS PDR command produces several return codes. These return codes
along with their meanings are listed in Figure 6. xx is the CMS routine
return code.
Code
1

2
3
4

lxx
2xx
3xx
4xx
20

Meaning
Invalid filename or file not found
Error running the program
Flagged DASD track
Permanent tape or DASD I/O error
Error in PRINTIO routine
Error in CONREAD routine
Error inRDBUF routine
Error in TYPLIN routine
Error in the decoding routine.

Figure 6.

Return Codes Produced by the CMS DDR Command

Return Codes Produced by IPCS
There. are two return codes produced by IPCS. These return codes along
with their meanings are listed in Figure 7.
Code
4
8

Meaning
An incorrectly entered .parameter.
System failure; a read/write error or an
invalid internal parameter.

Figure 7. Retu.. n Codes Produced by IPCS

VM/SP System Messages and Codes

CP Wait State Codes
001
Explanation: The machine check handler has encountered an
unrecoverable failure. Probable hardware error. Issued by module
DMKMCH and DMKMCT.
Note: This wait state is also loaded if a malfunction alert occurred on
the main processor.

Operator Response: Run CPEREP or the System Environment
Record Edit and Print (SEREP) program, depending on your processor
support, before restarting the system. To restart, clear storage and
IPL the system, specifying CKPT start. If the problem persists,
contact your system support personnel. Do not use the SEREP
program on 3081 and 4341 processors as you will get invalid results.

002
Explanation: The channel check handler has encountered an
unrecoverable failure. Probable hardware error. Issued by module
DMKCCH.
Operator Response: Run CPEREP or the System Environment
Record Edit and Print (SEREP) program, depending on your processor
support, before restarting the system. To restart, clear storage and
IPL the system, specifying CKPT start. If the problem persists,
contact your system support personnel. Do not use the SEREP
program on 3081 and 4341 processors as you will get invalid results.

003
Explanation: A system failure occurred during dump processing or
restart processing. Issued by module DMKDMP upon detecting one of
the following conditions:
1.

2.
3.
4.
5.

No printers defined in the system (DMKRIO) and dump trying to
go to printer.
All printers are offline and dump was trying to go to printer.
Unable to restart system - fatal I/O error condition on IPL device.
Fatal I/O error condition on dump device (tape or printer).
Abend was on non-IPL processor but system not genned for
AP/MP.

The specific failing condition can be found by looking at register 14 at
the time of' the wait. This register is a BAL register within DMKDMP
and is used when entering the wait state.
Operator Response: Reload (via IPL) the system. If the error
persists, check to see if error message DMK9081 appeared. If this
message did appear, it displays an abend code; look up this abend code
System Codes

in Figure 9 on page 34 and then follow the instructions in the 'Action'
column. If message DMK9081 did not appear, you can get the abend
code by looking in the CPABEND field of absolute page 0, location
X'374'; once you find the abend code, look it up in Figure 9 on page 34
and then follow the instructions in the 'Action' column.

004
Explanation: A console or an output device is not operational, or a
console or output device has produced an inexplicable error status.
Probable hardware error. Issued by module DMKDMP.
Operator Response: Reload (via IPL) the system. To restart, clear
storage and IPL the system, specifying CKPT start. If the problem
persists, contact your system support personnel.

005
Explanation: During CP initialization, no operational primary or
alternate console could be located, or a terminal error occllrred while
writing to the console, or a sense operation failed attempting to obtain
sense data for either a primary or any alternate consoles. Possible
hardware error. This wait state may also occur if the primary and
alternate console addresses are defined incorrectly during system
generation in DMKRIO, or if there is a discrepancy in the CONMODE
and DMKRIO console definitions when runni~g second level. Issued
by DMKCPJ, DMKOPE, and DMKTOD.
Operator Response: Verify that the console addresses are correctly
defined in DMKRIO. Reload the system via IPL. If the problem
persists, contact your system support personnel.

006
Explanation: This is a normal wait when a system shutdown is
completed. Issued by module DMKCPJ.
Operator Response: Follow normal operating procedures.

007
Explanation: A program check, a machine check, a permanent I/O
error, invalid warm start data, an invalid warm start cylinder, or a full
warm start cylinder was encountered by the checkpoint program.
Issued by module DMKCKP.
Qperator Response: For message DMKCKP901 W, run CPEREP or
SEREP, depending on your processor support, to document the
machine check, then contact your system support personnel. For
message DMKCKH902W, which indicates an unrecoverable I/O error,

VM/SP System Messages and Codes

move the SYSRES volume if possible and try to checkpoint the system.
For message DMKCKP910W. if more than one SYSRES volume is
mounted, check to see that the correct volume is loaded (via IPL) and
try a checkpoint operation. If the operation fails again use the
following procedure. This procedure is to be used for all other
DMKCKP messages as well.
1.

Dump the first 55,296 (hexadecimal DSOO) storage locations.

Dump the warm start cylinders.

Contact program support personnel.

To restart, clear storage and initialize the system, specifying CKPT
start.

The following storage locations contain information related to wait
state 007 for the non-V = R user.

Hexadecimal
Location Contents
10
Sense data up to 24 bytes
Channel status word (8 bytes)
40
48
Channel address word (4 bytes)
Length of error message (4 bytes)
FFS
FFC
Pointer to error message (4 bytes)
Cylinder address of the first nucleus cylinder (2 bytes)
1016
(CKD only)
lOIS
Cylinder address of the last nucleus cylinder (2 bytes)
(CKD only)
1000-6FFF Checkpoint program
7000-DSOO
Checkpoint work area
If the SYSRES device is FB-512 (RDEVTYPC = CLASFBA), the
contents of the following hexadecimal locations are changed:
1016
1022

Block address of the first page of the CP nucleus (4 bytes)
Block address of the last page of the CP nucleus (4 bytes)

An error message preceding the wait state mayor may not be
displayed, depending upon the status of the console. If the error
message is not displayed, location X'FF8' - X'FFB' contains the
message length and location X'FFC' - X'FFF' contains the message
address.

008
Explanation: Checkpoint and system shutdown are complete or
system recovery has failed. Issued by module DMKCKP.
Operator Response: If messages preceded the wait, follow normal
operating procedures prescribed by your installation after shutdown.
If messages did not precede the wait, either:

System Codes

The console printer was unavailable for some reason. Before
initializing a new system, make sure the console printer has been
made operational, or

The system is running from the alternate console. Messages
DMKCKH910W, DMKCKH911W, DMKCKP960I, and
DMKCKP961 W do not appear on the alternate console. Follow
normal operating procedures prescribed by your installation after
shutdown.

009

Explanation: An error condition occurred which prevents a warm
start. Issued by module DMK\VRM.
Operator Response: If the message is DMKWRM904W or
DMKWRM921W, immediately retry warm start system initialization. If
the error message recurs~ move the VM/SP SYSRES pack to another
location and try a warm start again. If message DMKWRM903W or
DMKWRM912W is encountered, ensure that all system volumes (no
duplicate labels) are correctly mounted, and then attempt a warm
start.
If warm start errors persist, force a system dump to the printer by
pressing the system console RESTART key, and save the results for
the installation support personnel.
If the message is DMKWRM920W, restart the system using CKPT
start. Otherwise, use a FORCE or COLD start.

OOA

Explanation: A machine check occurred while DMKSAV was
attempting to save or restore a page image copy of the nucleus on a
SYSRES device. Probable hardware error. Issued by module
D1VIKSAV.
Operator Response: Run CPEREP or the System Environment
Record Edit and Print (SEREP) program. depending on your processor
support, before reloading. If the problem persists, contact your system
support personnel. Do not use the SEREP program on 3081 and 4341
processors as you will get invalid results.

OOB

Explanation: A machine check error occurred during system
initialization. Probable hardware error.
Operator Response: Run CPEREP or the System Environment
Record Edit and Print (SEREP) program depending on your processor
support, before performing another IPL. If the problem persists,

VM/SP System Messages and Codes

contact your system support personnel. Do not use the S~~REP
program on 3081 and 4:341 processors as you will get invalid results.

ooe
Explanation: An IPL was performed on a system volume that had
never had a nucleus written on it.
Operator Response: Follow normal operating procedure.

OOD

Explanation: The generated system is larger than the real machine
size, or else a hardware malfunction has occurred which inhibits the
system from using the necessary storage. Issued by modules DMKSEG
and DMKOPE.
Operator Response: Take a standalone dump and notify the system
programmer.

OOE

Explanation: An error condition prevents a CKPT start. Issued by
module Dl\1KCKS.
Operator Response: If message DMKCKS915E is issued, try CKPT
start again. If the error persists, move the VMjSP SYSRES pack to
another DASD and try again. If message Dl\1KCKS916E is issued,
reload (via IPL) the system. using the FORCE option of the START
command. If message DMKCKSS03E or DMKCKS912E is issued,
ensure that all system volumes (no duplicate labels) are correctly
mounted, and then attempt a CKPT ~tart. If message DMKCKS917E is
issued, reload (via IPL) the sygtem via a COLD start.

OOF

Explanation: Hardware errors are being received on the system
paging device(s). Issued by module DMKPAG.
Operator Response: This wait state is preceded by message
DMKPAG415E CONTINUOUS PAGING ERRORS FROM DASD xxx

If there are multiple paging devices OIl the system, disable· the device
causing the error condition and reload (via IPL) the system. Or, move
the paging volume pack to another physical device. This error
condition results if the system paging volume has not been formatted
correctly.

System Codes

010
Explanation: A recoverable error occurred during a system nucleus
save operation. Issued by module DMKSAV.
Operator Response: This wait state is preceded by either the
message DMKSA V350W or DMKSAV351 W. Correct the problem
stated in the message and present an external interrupt to initiate a
retry.

011
Explanation: An unrecoverable I/O error occurred. Issued by module
DMKSAV.
Operator Response: This wait state is normally preceded by message
DMKSAV352W or DMKSAV353W, and it can occur while attempting
to read or write the nucleus. Correct the problem and save or restore
the nucleus again.

012
Explanation: This is a normal wait state on completion of a nucleus
load. Issued by module DMKSA V.
Operator Response: Follow normal operating procedure.

013
Explanation: The machine check handler encountered an
unrecoverable error on the attached processor. Probable hardware
error. Issued by module DMKMCT.
Notes:
1.

This wait state is also loaded if a malfunction alert occurred on the
attached processor and CP was in control.

This wait statei:; also issued by DMKA PI during Attached
Processor initialization: either because of a malfunction alert or
unrecoverable machine check on the attached (being varied on)
processor.

Operator Response: Run CPEREP or the System Environment
Record Edit and Print (SEREP) program. depending on your processor
Hupport, before restarting the ::;ystem. If the problem persists, contact
your Hystem Hupport personnel. Do not use the SEH,EP program on
3081 and 4841 JH'oces::;ors aH you will get invalid results.
To restart, clear storage and 1PL the system, specifying CKPT start.

VM/SP System Messages and Codes

Note: VIvi/SP cannot checkpoint and warm start after a machine
check error on System/370 Models 165 and 168. The inability to· warm
start is caused by running the 165 or 168 SEREP program.

014
Explanation: A failing storage frame was encountered during a CP
system save or check point operation. Issued by DMKSA V and
DMKCKP.
Operator Response: Run CPEREP or the System Environment
Record Edit and Print (SEREP) program, depending on your processor
support, before restarting the system. To restart the system; clear
storage and initialize (via IPL) the VM/SP system, specifying CKPT
start. If the problem persists, contact your system support personnel.

015
Explanation: A SIGP issued to the attached processor during system
initialization by DMKCPI or DMKAPI was unsuccessful. The
following information is made available:
•

RO = SIGP order code

•

Rl = SIGP status information when the SIGP condition code is 1

•

R2 = Processor address that was signalled

Note: The wait state PSW will contain the condition code rehirrted
from the SIGP. The PSW is in the BC format. Refer to the IBM
System/370 Principles of Operation for a functional description of the
SIGP instruction.

Operator Response: If hardware errors are present, run CPEREP or
the System Environment Record Edit and Print (SEREP) program,
depending on your processor, before retrying. If the status
information indicates an operator intervention, clear the condition on
the attached processor and reinitialize CPo If the status indicator of
the required microprogram is not loaded, load the microprogram and
reinitialize CPo If the problem persists, contact your system support
personnel. Do not use the SEREP program on 3081 and 4341
processors as you will get invalid results.

System Codes

016
Explanation: (1) The CP initialization module (DMKCPI) could not
connect the channel set to the main processor or the IPL device is not
accessible through any available channel set. Probable hardware
error. Issued by DMKCPI. (2) A hardware error occurred on the I/O
processor or the I/O processor was being varied offline. An attempt to
disconnect, then connect the channel set to the attached processor
failed. Probable hardware error. Issued by DMKCPU.
Operator Response: Run CPEREP or the System Environment
Record Edit and Print (SEREP) program, depending on your processor
support, before restarting the system. If the problem persists, contact
your system support personnel.
To restart, clear storage and initialize the VM/SP system, specifying
checkpoint start.

017
Explanation: An I/O error or any other type of program check
oCGurred while attempting to read page 2 of the DMKCKP module
from the system residence volume during an IPL or restart.
Operator Response: Correct the I/O error and re-IPL.

018
Explanation: Invalid TOD clock. The clock must be set before an
IPL can be completed. Issued by module DMKCPI.
Operator Response: Manually do a clock set; if that fails, call IBM
for hardware assistance.

019
Explanation: (1) This processor is being terminated, and its new
PSWs have been set up by the processor termination routine to load
disabled wait PSW s with code X'D19'. This processor then took an
interruption. (2) The processor termination routine was entered on
this processor while processor termination was in process for this
processor (issued by DMKMCT). (3) Processor termination was in
process for the other processor, but the other processor continued to
run and obtained a system lock (issued by Dl\1KCPP and DMKMCT.)
Operator Response: Usually caused by bad status received during a
SIGP, which initiates processor termination actions. The bad status
may have been caused by hitting the STOP button on one processor in
the configuration. If STOP is to be hit, both processors in the
configuration must be STOPed. If neither processor has been

VM/SP System Messages and Codes

manually stopped, there is probably an hardware error associated with
the SIGP function.

018

Explanation: A wrong or inconsistent allocation extent was found on
during IPL. Issued by DMKCPI.
Operator Response: Use IPL FMT program to check the allocation
extent map (use END statement only to display current status). In
case of error, correct it and IPL the system again.
Note: The problem can occur even when the allocation extent map
looks correct, if the system residence volume was restored or copied
from a different sized FB-512 device (for example, from 3370 to 3310).
Running IPL FMT's allocation function with END as the sole entry
will fix this.

Ole
Explanation: The device type code generated in the RDEVICE macro
of DMKRIO does not match the actual code obtained from the RDC
data during IPL of the SYSRES device.
Operator Response: Correct the DEVTYPE operand in the
RDEVICE macro of DMKRIO so that it matches the actual device
type. Then rebuild the CP nucleus and re-IPL.

OlF
Explanation: This wait state is preceded by message DMKSAV972E.
The CP nucleus you are trying to install is too big and cannot fit into
its designated area. As a result, the SYSNUC area of the target disk
is not updated. This problem could happen, for example, when service
is added to the system, causing the nucleus to grow beyond the defined
storage area. Issued by module DMKSAV.
Operator Response: Notify the system programmer and indicate the
number of PAGES or CYLINDERS (from DMKSAV972E) that would
be required for this nucleus.

027
Explanation: An unrecoverable I/O error occurred or system input is
incorrect. Issued by module DMKSSP.
Operator Response: Correct the input/output error or the system
input, and reload (via IPL) the starter system.

System Codes

028
Explanation: An· unrecoverable I/O error has occurred while trying
to write the warm start data area. Issued by module DMKOPE.
Operator Response: Clear the first record of warm start data and
re-IPL the system to attempt a CKPT (checkpoint), FORCE, or COLD
start.

VM/SP System Messages and Codes

Loader Wait State Codes
The loader (DMKLDOOE) is a service program that loads a CP or CMS
nucleus and produces a load map. The loader loads the object modules
(TEXT files) supplied with it, resolves CCW addresses, and resolves address
constants.
If the loader is terminated, one of the wait codes shown in Figure 8 is
indicated in the instruction counter.

Code
X'111111'

X'222222'
X'999999'
X'AAAAAA'

X'BBBBBB'
X'CCCCCC'
X'FFFFFF'

Figure 8.

Meaning
A program check occurred. When loading a nucleus with
a V = R area, the user area must include: loader +
nucleus that is being loaded + the V '--= R area = total
storage requirement. The area must be larger than this
total to use the loader. (Refer to the VM/SP Planning
Guide and Reference.)
A unit check occurred while the bootstrap routine was
reading in the loader.
An SVC was issued.
A failing storage frame was entered during loading of the
CP nucleus. This is a hardware error. If the problem
persists, contact your system support personnel.
A machine check occurred.
An I/O error occurred on the card reader.
An I/O error occurred for the console (X'OO' contains the
message UNRECOVERABLE ERROR), or the control card
for changing the default I/O addresses for the printer or
terminal is invalid (X'OO' contains the message BAD
DEVICE CARD or INVALID DEVICE SPECIFIED).

Wait Codes Upon Loader Termination

If the instruction counter contains X'999999', indicating an SVC wait state,
examine the interruption code (the third and fourth bytes of the supervisor
old PSW). The interruption codes (shown in hexadecimal below) indicate
the error condition.

64
Explanation: An error occurred during conversion of a value from
hexadecimal to binary format. This can be caused by invalid input in
one of the loader statements, or by an error in the loader.
Operator Response: Validate the copy of the loader you are
currently using against the copy on the original distribution tape. If
the current copy is no longer valid, replace it. If the input in the
statements is invalid, correct it. If the problem persists, contact your
system support personnel.

System Codes

Explanation: There is no more free storage available for the loader.
Operator Response: Define a larger storage size for the virtual
machine and reexecute the loader.

66
Explanation: A duplicate type 1 ESD (External Symbol Dictionary)
entry has been encountered. The loader cannot resolve this reference.
This may be the result of a duplicate text deck in the input stream, or
of having the same label in two different text decks in the same input
stream.
Operator Response: Close the printer to get the load map printed.
Look at the load map to see which text deck and which entry are
causing the problem. If you can correct the problem, do so; otherwise,
contact your system support personnel.

Explanation: The "name" in the LDT (Loader Terminate) statement
is undefined.
Operator Response: Verify that the name in the LDT statement is
correct; if it is, make sure that it is defined as an entry point in the
program to be loaded.

68
Explanation: The control section named in the lCS (Include Control
Section) statement was not found by end of file.
Operator Response: Verify that the control section name in the lCS
statement if) correct; "if it is, make sure that the control section is
defined in th(! program to be loaded.

69
Explanation: The loader attempted to add another entry to the
reference table: which would have caused the table to overflow. Since
the reference table supplied by VM/SP is large enough to allow the CP
nucleus to be generated, it must be assumed that the inclusion of local
additions to the CP nudeus have caused the excessive references to be
generated.
Operatol' Response: Inerease the size of the reference table by
changing thf~ !\L\XREF equate field in the source code for the loader
program, r(~a:3~f~m bling it, ~.lnd then reexecuting the loader. Once the

VM/SP System ~'1esBages and Codes

size of the reference table has been increased, error code 6A may
occur. In that case, define a larger storage size for the virtual
machine. If the problem persists, contact your system support
personnel.

6A
Explanation: The objf;ct modules being loaded are about to overlay
the loader.
Operator Response: Define a larger storage size for the virtual
machine. To see which module was about to overlay the loader, close
the printer to get the load map printed. The last line of the load map
indicates the last module that was loaded.

6B
Explanation: The object modules being loaded are about to overlay
an address between 0 and 100 (hexadecimal). This state can result if an
SLC card changed the address at which loading was to start.
Attempting to load an incorrectly-assembled text deck can also cause
this wait state to occur.

Operator Response: Check the SLC card to make sure it does not
specify an address between 0 and 100 (hex). If you must place data at
an address in that range, do not do so with the loader; instead use a
program containing a Move Character instruction after the loaded
system has started execution. The loaded program is responsible for
ir,itializing that part of storage.
If the wait state results from an attempt to load an
incorrectly-assembled text deck, the load map will indicate this. The
last deck in the load map will be flagged with an error message.

6D
Explanation: The loader is trying to release storage that is not on a
doubleword boundary. This is an internal loader error.
Operator Response: Reexecute the copy of the loader that is in your
reader. If the problem persists, regenerate the system to be loaded and
try to execute it again. If the problem still persists, the current copy
of the loader itself may be damaged; replace it with the loader on the
distribution tape. If the problem still persists, contact your system
support personnel.

System Codes

Stand-Alone Dump Facility Wait State Codes
Communications from the stand-alone dump facility to the user is done
through wait state codes in the psw. If the system enters the wait state
while generating or executing the stand-alone dump program, the user can
display the current psw to determine if the dump was successful or to
determine the cause of the error.
One set of wait states is used during generation of a stand-alone dump
program. Another set of wait states is used during execution of the
stand-alone dump program. Intervention required results in an enabled
wait state.
The following information may also be of value when error conditions are
detected:
•

The Channel Status Word is at location X'40'

•

The I/O address is at location X'BA'

•

32 bytes of sense data are at location X'2EO'

•

The starting and ending addresses of the CP Trace Table are stored in
the PSA at X'7BO' and X'7B4', respectively, in addition to the low
storage locations.

Stand-Alone Dump Program Generation Wait State Codes
912

Explanation: The stand-alone dump facility has been successfully
placed on the IPL device.
User Response: None.

991

Explanation: An error occurred while reading from the DASD.
Register 15 should contain the DIAGNOSE X'20' reason code for the
failure.
User Response: Display general register 15, which indicates what the
error condition is, then take the appropriate action to correct the
problem and retry the Stand-Alone Dump Utility.

VM/SP System Messages and Codes

992
Explanation: The name of the volume owner in the volume label on
record 3 is not CP370. This indicates that the volume is not CP
formatted.
User Response: CP format at least cylinder 0 and allocate it as
permanent space.

993
Explanation: The DASD is not a CP formatted volume with cylinder

o allocated as permanent space.

User Response: Allocate cylinder' 0 as permanent space.

994
Explanation: The DASD device type specified at the time the
Stand-Alone Dump Configuration deck was generated does not match
the DASD device at the address given as the IPL device.
User Response: Either obtain the DASD device type specified at the
time the Stand-Alone Dump was configured, or rebuild the
Stand-Alone Dump Configuration deck to match the current DASD
device type.

995
Explanation: The tape device type specified at the time the
Stand-Alone Dump Configuration deck was generated does not match
the device at the address given as the IPL device.
User Response: Either obtain the tape device type specified at the
time the Stand-Alone Dump was configured, or rebuild the
Stand-Alone Dump Configuration deck to match the current tape
device type.

996
Explanation: The device class specified at the time the Stand-Alone
Dump Configuration deck was created does not match the device class
at the address given as th~ IPL device.
User Response: Either obtain the proper device of the class specified
at generation time, or rebuild the Stand-Alone Dump Configuration
deck to match the current device class.

System Codes

997
Explanation: There is no device corresponding to the IPL device
address specified in the SAD MACRO.
User Response: You must obtain a device at the address specified at
generation time or build a new Stand-Alone Dump Configuration deck
to match the existing devices.

999
Explanation: An error occurred while writing the stand-alone dump
facility onto the IPL device. Register 15 should contain the
DIAGNOSE X'20' reason code for the failure.
User Response: Display general register 15, which indicates what the
error condition is, then tak.e the appropriate action to correct the
problem and retry the Stand-Alone Dump Utility.

Stand-Alone Dump Program Execution Wait State Codes
905

Explanation: A program check occurred during stand-alone dump
program execution.
User Response: This action should be the same as for a PRGOOl
abend. Examine the Program Check Old PSW to determine where the
problem occurred.

906

Explanation: A machine check occurred during stand-alone dump
program execution.
User Response: A possible hardware problem exists. You can
RESTART the Stand-Alone Dump Facility.

909
Explanation: Intervention required on the dump output device.
User Response: Correct the intervention required condition and the
Stand-Alone Dump will continue.

VM/SP System Messages and Codes

912
Explanation: Successful completion.
User Response: None.

913
Explanation: An operational dump device is not available.
User Response: Make one of the devices specified in the dump device
list, created at Stand-Alone Dump Configuration time, ready. Then
RESTART the Stand-Alone Dump Facility.
Note: Do NOT re-IPL the Stand-Alone Dump Facility, this will cause
the dump to dump itself.

914
Explanation: An error occurred while reading the pre-dumped pages
from the IPL device.
User Response: If there is something obviously wrong with the IPL
device, for example dropped power, correct the problem and RESTART
the Stand-Alone Dump Facility.
Note: Do NOT re-IPL the Stand-Alone Dump Facility.

915
Explanation: The dump output device is neither tape nor printer.
User Response: The Stand-Alone Dump Configuration deck indicates
that the dump output device is neither a tape nor printer. Reconfigure
the Stand-Alone Dump Facility.

916
Explanation: An unrecoverable I/O error occurred on tape.
User Response: Mount another tape to be used as the dump output
device and RESTART the Stand-Alone Dump Facility.
If the error occurs on the IPL tape, do not remove it; READY another
tape at one of the addresses specified in the dump device address list
and RESTART the Stand-Alone Dump Facility.

Note: Do NOT re-IPL the Stand-Alone Dump Facility.

System Codes

917
Explanation: An unrecoverable I/O error occurred while writjng a
record to tape.
User Response: If the error occurs on the IPL tape, do NOT remove
it; READY another tape at one of the addresses specified in the dump
device address list and RESTART the Stand-Alone Dump Facility.
If the error occurs on a tape device other than the one holding the IPL
tape, replace the output tape with another dump output tape and
RESTART the Stand-Alone Dump Facility.

Note: Do NOT re-IPL the Stand-Alone Dump Facility.

918
/'

Explanation: An unrecoverable I/O error occurred while printing.
User Response: READY another printer specified in the the dump
out list and make the printer causing the error not-READY. Then
RESTART the Stand-Alone Dump Facility.
Note: Do NOT re-IPL the Stand-Alone Dump Facility.

1909
Explanation: File Protect/Intervention required on the dump output
tape.
User Response: Place a write-ring in the dump output tape and ready
it.

Normal Waits
These are normal waits for I/O to complete and are for informational
purposes only. No action is required from the user.

920
Explanation: SIO resulted in condition code O.
User Response: None

VM/SP System Messages and Codes

921

Explanation: SID resulted in a condition code 1 with BUSY and
Status Modifier posted.
User Response: None

922
Explanation: SID resulted in a condition code 1 with BUSY posted.
User Response: None

923
Explanation: SID resulted in a condition code 2.
User Response: None

924
Explanation: An unsolicited Channel Available Interrupt was
received.
User Response: None

System Codes

CP Abend Codes
System Operator Action
When an abend occurs, the system operator must follow several steps:
1.

Collect information about the error.

Collect information about the system status.

Recover from the abend so processing can continue.

Collecting Information
Unless the operator has issued the SET DUMP command and changed the
default (which he generally should not do), the system is set for SET DUMP
AUTO CPo When an abend occurs, the dump will be written on disk as a
spool file. This spool file is automatically spooled to the virtual reader of
the operator who was designated at system generation time to receive all
dumps. This operator should then IPL CMS and issue the IPCSDUMP
command (see the VMjSP Operator's Guide). This moves the dump to the
operator's A-disk so that it can be processed by the following VMjSP IPCS
commands:
•
•

PRTDUMP to print a copy of the dump.
DUMPS CAN to display view the dump.

This procedure should be followed for every abend.
For problem determination, the operator should save and submit:
1.

The formatted dump.

The console sheet, as far back as the last IPL of the system.

The output of any monitor program running at the time.

If an APAR (authorized program analysis report) is to be submitted, the
documentation provided with it should include, in addition to the above, a
load map showing applied updates and resolved locations. You can obtain
as many copies of the load map as you need if, at system generation time,
you respond "RDR" to the prompting message:
ROUTE LOAD MAP TO PRINTER OR READER? -RESPOND (RDR\PRT)

This sends to your virtual reader a copy of the load map, which can be read
in as a eMS file named, for example, LOAD MAP.
To take a dump to tape and send the dump to another location (for example,
when submitting an APAR by mail), use the following procedure:

VM/SP System Messages and Codes

CP Abend Codes
1.

Allow the dump to be written to a spool file by issuing
SET DUMP CP

Format this spool file and write it onto a CMS disk by issuing
IPCSDUMP

Write this disk file on tape by issuing the CMS command
TAPE DUMP

You can then send this tape to another location, where the file can be
recreated on disk using the TAPE LOAD command.

Recovering from the Abend
The system usually reloads itself (self-IPL). If it does not, you must attempt
to warm start the system. You may get errors from which you can recover;
if so, correct the cause of the error and try again to warm start. If
unrecoverable errors occur, clear storage and try to checkpoint (CKPT)
start. If this fails, try to force start. If this also fails, as a last resort you
must cold start the system.

System Programmer Action
Figure 9 on page 34 describes the reasons for each of the CP abend codes
and discusses what the system programmer should do to locate and correct
the error that caused the abend.

System Codes

CP Abend Codes
Abend
Code
APIOOI

Reason for Abend
The global system lock or
the system operator's
VMBLOK lock could not
be obtained by the main
processor during .IPL.

Action
Check DMKLOKSY. If the attached processor
owns the system lock, check RI2 value in
DMKLOKSY + 4 to determine who obtained the
lock. If the global system lock is held by the
main processor, check the system operator's
VMBLOK to see if the VMBLOK is locked by
the attached processor. If so, VMLOCKER
contains the base address of the obtainer of the
lock and can be used to determine why the lock
was obtained.
Verify the Print Driver Machine is operational.
Check that the LPRTBLOK chain has not been
altered.

APSOOI

The LPRTBLOK chain
ended before finding the
LPRTBLOK with the
matching IUCV pathid.

ATSOOl

DMKATS was called to
make a shared named
system unshared.
However, the SHRT ABLE
associated with the shared
page that was changed
could not be located.
A shared page was
changed and the
corresponding VMABLOK
could not be found.
During the unshare of a
user from a shared named
system, DMKSNTBL was
brought back in to
reconstruct the
SWPT ABLE of the
violator. The named
system could not be found
in DMKSNTBL.

The SHRT ABLE may have been overlaid or the
shared page that was changed was altered by
another virtual machine. If the SHRT ABLE
was not overlaid, find out which virtual
machine altered the shared page and why it
was not detected.

During the unshare of a
user from a shared named
system, the system volume
containing the named
system could not be found.
During the unshare of a
user from a shared named
system, a shared
CORTABLE entry (R7
contains its address) was
found with the I/O lock
bit on.

The system name table ent.ry (R4 contains its
address), the SYSOWN list or the RDEVBLOKs
have been altered. Investigate the routine that
would allow alteration.

ATSOO2

ATSOO3

ATSOO4

ATSOO5

Figure 9 (Part 1 of 29).

CP Abend Codes

VM/SP System Messages and Codes

A shared page was altered by another virtual
machine without being detected. Investigate
the system routines that could allow an
undetected alteration of a shared page.
The SHRTABLE, SAVEWRK2 and SAVEWRK3
area of DMKATSs save area (R13 contains
address of save area) or DMKSNTBL (R4
contains its address) have been altered.
Investigate the routine that would allow
alteration.

The CORTABLE, SHRTABLE, PAGTABLE, or
ACCRETBL have been altered. Investigate the
routine that would allow alteration.

(

CP Abend Codes
Abend
Code
ATS006

Reason for Abend
The resident page count
in the VMBLOK
(VMP AGES) does not
match the number of
CORT ABLE entries.
R8 should contain a
pointer to the
RDEVBLOK for the user's
terminal. DMKBLDVM
attempts to create and
partially initialize a
VMBLOK for a user.
DMKBLDVM abnormally
terminates if R8 does not
contain a pointer to the
user.
Pages are being released
but the page invalid bit is
not on in the page table
entry.

Action
Inspect mod·ules that update VMPAGES for the
virtual machine. Check the routine to
determine why it is inconsistent with the
number of CORT ABLE entries assigned to this
virtual machine.
Verify that R8 points to an RDEVBLOK for a
terminal. If it does not, there is probably an
error in the calling program. Identify the
calling routine by means of the return address
and the base register in the save area pointed
to by R13. Then~ attempt to identify the source
of the incorrect RDEVBLOK address.

BLD003

A request was made to
build a page table for
more than 16 pages.

BLD004

The routine calling BLD
has not cleared all the
segment table activity
before calling BLD.

BLD005

An attempt is being made
to release a segment
whose page table has been
migrated.

CFGOIO

DMKCFGCL was called to
perform an unsupported
function. Supported
values are:

R13 points to a save area. SAVER13 contains
the base address of the module issuing the
request. SAVERI contains the beginning and
ending address range of the page table being
built. Examine the calling module to determine
why Rl is invalid.
Examine R6 to ensure that it contains the
address of a segment table entry. If it contains
the address of a segment table entry, R13
contains the address of the module calling
BLD. Examine this module to determine why
this segment table entry has not been cleared.
Examine R6 to ensure that it contains the
address of a segment table entry. If it contains
the address of a segment table entry, R13
contains the address of a save area. SA VER12
contains the base address of the module calling
BLD. Examine this module to determine why
the page table was migrated or why the
migration bit was not reset.
Identify the caller by the return address and
base register in the save area pointed to by R13
to identify the source of the unsupported
function request.

BLDOOI

BLD002

•
•
•

Examine the dump and determine why the page
was released without the page invalid bit
turned on.

X'Ol' LOAD SYS
X'02' FIND SYS
X'04' PURGE SYS

Figure 9 (Part 2 of 29).

CP Abend Codes

System Codes

CP Abend Codes
Abend
Code
CFROOI

CFROO2

CKSOOI

CKSOO2

CKSOO3

CKVOOI

CKVOO4

CLKOO3

Reason for Abend
An I/O task is waiting for
a RELEASE and the
CPEXBLOK for the
waiting task cannot be
found on the VRRCPEX
queue.
DMKSCNVU was unable
to locate all of the virtual
I/O control blocks for the
virtual unit address.

The map for a dynamic
check poin t was not
allocated prior to a call to
DMKCKSPL.
The spool file
identification in the map
and in the checkpoint
area do not match.
No function was specified
in the call to
DMKCKSPL.
The map for dynamic
checkpoint was previously
allocated prior to a call to
DMKCKVWM.
A spool file to be deleted
cannot be found on the
system printer, punch, or
reader file chains.
The system TOD clock is
not operational on the
main processor or
attached processor. The
wait state can only be
received when it is
configured with an
attached processor.

Figure 9 (Part 3 of 29).

CP Abend Codes

VM/SP System Messages and Codes

Action
Examine the dump and determine why the
virtual device block is marked as waiting for
access to the device but CPEXBLOK does not
exist on the VRRCPEX. Queue to resume the
task.
Determine whether the unit address in register
1 is valid for the user. Rll contains the address
of the user's VMBLOK. If invalid, the user's
virtual I/O configuration has been altered
because of the abend. Examine the dump to
determine how it was altered.
The map should be allocated via a call to entry
points DMKCKSIN or DMKCKVWM from
DMKWRM. Check DMKWRM for called entry
points and that they do allocate a map.
DMKCKVWM or DMKCKSIN did not set up
the map properly, a call to DMKCKSPL caused
the mismatch, or the SFBLOK was released but
the map was not updated.
Check SAVERTN in the save area pointed to
by RI3. This indicates which routine called
DMKCKSPL with insufficient data.
The map should not be allocated before
DMKCKVWM was called. Map pointer field is
probably being overlaid.
The SFBLOK for the file should have been
queued previously on by DMKCKVWM when
performing a CKPT start. Check for an error
in this logic.
Examine the CPABEND code in each
processor's PSA to determine the unit receiving
the clock error. Call IBM for hardware support
to fix the clock.

CP Abend Codes
Abend
Code
CPIOO2

Reason for Abend
A valid system directory
file could not be located.
You may have reallocated
the volume containing the
directory, but did not
reinitialize the directory.

CPIOO5

A valid CP message
repository could not be
found during system
initialization.

CPJOOI

The system TOD clock is
not operational.
DMKACRO returned a
nonzero condition code to
DMKCPO. A VARY
OFFLINE PROCESSOR
command was issued in
MP mode; prior to
accepting the VARY
OFFLINE command as
valid, DMKCPO verified
that online paths would
still exist to all mounted
system-owned devices.
Between that time and the
call to DMKACRCO, the
configuration has changed
and a path has been lost.
The system cannot
continue operation if
there are not paths to all
system-owned devices.
The user page count in
the VMBLOK was
incorrectly decreased to
less than zero.

CPOOO3

CPPOOI

Figure 9 (Part 4 of 29).

Action
Display the volume labels for all owned
volumes. If the volumes do not contain an
active directory pointer, run DMKDIR (the
standalone directory program) to recreate the
system directory on an owned volume. If an
active directory pointer is present in at least
one volume label, verify that the device is
online and ready before trying to IPL the
system. Verify that a valid allocation record is
present on the volume containing the directory.
Check the load map. If DMKMES is missing,
rebuild the system and ensure that DMKMES
is included in the nucleus when you build the
system. If DMKMES is found, then the
contents of the text deck may be invalid. A
valid message repository contains the identifier
"MSGREP" in the first six bytes of the text
deck. Obtain a valid message repository and
rebuild the system.
Call IBM for hardware support to fix the clock.
Examine the storage dump. From the list of
system-owned devices located by DMKSYSOW,
find the online path information for these
devices. The online path information in
REDEVPTHS may be overlaid.

Examine the storage dump. The VMBLOK has
probably been over laid.

CP Abend Codes

System Codes

CP Abend Codes
Abend
Code
CPP002

CPVOOI

Reason for Abend
During the VARY
processor offline function,
DMKSNTBL was brought
back in to reconstruct the
attached processor's
SWPT ABLE for shared
pages. The named system
could not be found in
DMKSNTBL.
The resident page count
in the VMBLOK
(VMPAGES) is reduced to
a negative value.

CQPOOI

DMSCNRA was called
and unable to determine
the device address in cuu
format from real device
block address in R6, R7,
and R8.

CQQOOI

DMSCNRA was called
and unable to determine
the device address in cuu
format from real device
block address in R6, R7,
and R8.
During QUERY
TERMINAL command
processing, VCONBRK in
the user's VMBLO K did
not contain a valid
terminal break k.ey value.
The system TOD clock is
in error or is not
operational.
The device code index in
the compressed DASD
address for the system
dump file points to an
RDEVBLOK for an
invalid DASD. The valid
DASDs are 2305,
2314/2319, 3330, 3340, 3350,
3375, and 3380.

CQU001

CVT001

DRD001

Figure 9 (Part 5 of 29).

CP Abend Codes

VM/SP System Messages and Codes

Action
Examine the storage dump. The SHRT ABLE or
DMKSNTBL has probably been overlaid.

Inspect modules that update VMPAGES for the
virtual machine. Check the routine to
determine why it is inconsistent with the'
number of CORT ABLE entries assigned to this
virtual machine.
Examine the storage dump. DMKSNRA
returns an error if it cannot find the address of
the real control unit block from the real device
block. The control unit block address in
register 7 probably invalid.
Examine the storage dump. DMKSNRA
returns an error if it cannot find the address of
the real control unit block from the real device
block. The control unit block address in
register 7 is probably invalid.
Examine the storage dump. The VMBLOK has
probably been overlaid.

Call IBM for hardware support to fix the clock.

Verify that the contents and order of the owned
list have not been altered since the dump was
taken. If these fields have not been altered, the
SFBLOK for the dump file may have been
destroyed. The owned list is specified by the
SYSOWN macro in DMKSYS.

CP Abend Codes
Abend
Code
DSPOO1

Reason for Abend
During I/O interruption,
unstack, and reflection~
DMKSCNVU could not
locate all of the virtual
control blocks for the
interrupting unit.

DSP002

The dispatcher
(DMKDSP) is attempting
to dispatch a virtual
relocate user whose
shadow segment tables or
virtual extended control
register 0 are invalid.

DSP003

The interval timer was
not incremented properly.
This is most likely a
hard ware error. The
dispatcher tests for
interval timer errors and
abnormally terminates if
such an error occurs.
Results would be
unpredictable if CP
continued when the
interval timer was in
error.
While tracing SIOs or I/O
interrupts, the virtual
device was detached.
Now, the VDEVBLOK
cannot be found.
During extend, a block is
found to be unstacked, but
the lock for the associated
VMBLOK is not available,
or count of priority
CPEXBLOKs in a
VMBLOK is less than 0,
but no priority
CPEXBLOK is found for
the virtual machine, or
during post-extend
processing, either the
expected processor-related
priority CPEXBLOK is
not found or the lock for
the associated VMBLOK
is not available.

DSP004

DSP005

Figure 9 (Part 6 of 29).

Action
The integrity of the user's virtual I/O
configuration has probably been violated. The
unit addresses or indexes in the virtual control
blocks are in error, or the virtual configuration
has been altered by ATTACH/DETACH while
I/O was in progress. Check for a device reset
failure in DMKCFQRD.
Most likely, a free storage violation has
occurred. First look at the DMKPRV and
DMKV AT modules. Examine the real, virtual,
and shadow translation tables for consistency
of entry size and format. Also compare page
and segment size.
Check the timer fields in real storage. The
value of the real interval timer is at real
storage location X'50'. The dispatcher loads
the value of the real interval timer in real
storage location X'54' when a user is
dispatched. The value of the real interval timer
is loaded into real storage location X'4C' when
an interrupt occurs. If the value stored at
X'4C' is not less than the value stored at X'54',
the dispatcher abnormally terminates. Check
the routines that control the value of the time
fields at X'4C', X'50', and X'54'.
Examine the operator's console sheet and the
user'minal sheet to see who detached the
device. Warn the person responsible that
devices should not be detached during I/O
tracing.
Rl contains the VMBLOK address at the time
of the a bend. Check VMLOCK to see if the
VMBLOK is locked by the other processor. If
this is the case, VMLOCKER gives the base
address of the obtainer of the lock and can be
used to determine wh v the lock was not
released. If the VMBLOK is not locked by the
other processor, check VMPRRCT, (the count
of priority CPEXBLOKs). If this is nonzero but
there are no priority CPEXBLOKs on the
dispatcher's stack, this field has probably been
overlaid and other methods must be used to
determine the cause of the overlay.

CP Abend Codes

System Codes

CP Abend Codes
Abend
Code
DSPOO6

EXTOO1

Reason for Abend
DMKDSPRU, the run-user
entry to the dispatcher
was entered when the
system was not in
attached processor mode.
A serial signal request has
been received and the
global system lock is not
held.

EXTOO4

A CPU timer interrupt
occurred either while the
system was in a wait state
or when an enable window
was opened.

FREOO6

A module is requesting a
block of storage whose
size (contained in RO) is
less than or equal to zero.

FRE010

A program is attempting
to extend free storage
while storage is being
extended. This can be
caused by I/O
interruptions or channel
programs involving
channels other than
channelO.
An extend was entered
while extending. The free
storage extend buffer is
unavailable.

FRE012

Figure 9 (Part 7 of 29).

CP Abend Codes

VM/SP System Messages and Codes

Action
Use the trace table to help determine the caller
of DMKDSPRU.

In the PSA of the abending processor, the
work/save area SIGSAVE contains the return
address of the caller of D MKEXTSP; this
address is at offset X'8' into SIGSAVE. At
offset 0 into SIGSAVE is the base address of
the caller.
Check CPST ATUS in the PSA to determine
whether the interruption occurred while in a
wait state or during an enable window. If the
interruption occurred while in a wait state
(CPWAIT on in CPSTATUS), the timer value at
the time of the interruption is stored in the
PSA's WAITEND. If the interrupt occurred
during an enable window (CPEX on in
CPSTATUS), the timer value is stored in the
first two words of PSA's TEMPSAVE. If the
timer value is negative, it is probably a
programming error. Try to determine why the
timer was set to a negative value. If the timer
value is positive, obtain hardware support to
determine why the interrupt occurred.
Using FREER14 and FREER12 in the PSA,
identify the module. Check for an error in
calculating the block size. Improper use of the
instructions ICM and STCM can cause
truncation of high order bits that result in a
calculation error.
If the storage requests that caused the abend
are due to channel activity, place the device
involved on channel 0, which is disabled during
free storage extension.

The system workload requires more free storage
than is available. Either: (1) Reassemble
DMKSYS with a larger value for FREE in the
SYSCOR statement and reinstall the CP
nucleus, (2) Restrict the number of users on the
system, or (3) Add more real storage.

CP Abend Codes
Abend
Code

Reason for Abend

Action

FRE014

DMKFRE must defer
satisfying a free storage
request when it is
necessary to call
DMKPRTFR and the
global supervisor lock
cannot be obtained. The
free storage extend buffer
reserved for this purpose
is not available.

Examine the internal trace table and storage
dump to determine why the free storage extend
buffer was not previously replenished.

FRTOOI

The size of the block
being returned (via RO) is
less than or equal to O.

Using FREER14 and FREER12 in the PSA.
identify the CP module releasing the storage.
Check for an error in calculating the size of the
block or for a modification to the stored block
size for variable-size blocks.

FRT002

The address of the free
storage block being
returned matches the
address of a block already
in the free storage chain.

Identify the CP module returning the storage
bv means of the return address and base
r~gisters (FREER14 and FREER12 in the PSA).
The most common cause of this type of failure
is a module that returns a free storage block
but fails to clear a pointer to the block that has
been saved else\vhere. All modules that return
blocks via a call to D:\IKFRET should first
verify that the sayed pointer is nonzero: after
returning the block. any saved pointers should
be set to zero.

FRT003

The address of the free
storage block being
returned overlaps the next
lower block on the free
storage chain.

FRT004

The address of the free
storage block being
returned overlaps the next
higher block on the free
storage chain.

A free storage pointer may have been
destroyed. Also. the module releasing the lower
(overlapped) block may have returned too much
storage. Examine the lower block and
determine its use and former owner. or identify
the CP module returning the storage by mean~
of the return address and base registers
(FREER14 and FREER12 in the PSA). The
most common cause of this type of failure is a
module that returns a free storage block but
fails to clear a pointer to the block that has
been saved elsewhere. All modules that return
blocks via a call to Dl\tlKFRET should first
verify that the saved pointer is nonzero: after
returning the block. any saved pointers should
be set to zero.
A free storage pointer may have been
destroyed. Also. the module releasing the
higher (overlapped) block may have returned
too much storage. or the module may be
attempting to release storage at the wrong
address.

Figure 9 (Part 8 of' 29).

CP Abend Codes

SY5tem Codes

CP Abend Codes
Abend
Code
FRT005

Reason for Abend
A module is attempting to
release storage in the
resident system nucleus.

FRT007

A module is attempting to
release a block of storage
whose address exceeds the
size of real storage.

FRT008

The address of the free
storage block being
returned matches the
address of the first block
in the subpool for that

Action
A module is probably attempting to release
location o. Check for the module picking up a
pointer to the free storage block without first
testing the pointer for o. Use FREER14 and
FREER12 in the PSA to identify the module.
A free storage pointer may have been
destroyed. Attempt to identify the owners of
the free storage blocks adjacent to the one
containing the pointer that was destroyed.
Check for moves and translation where initial
counts of zero have been decremented to minus
1, thus generating an executed length code of
X'FF', or an effective length of 256 bytes.
Identify the CP module returning the storage
by means of the return address and stored base
registers (FREER14 and FREER12 in the free
storage save area in the PSA).

SIze.

FRT009

The address of the free
storage block being
returned matches the
second block in the
subpool for that size.

The common cause of this type of failure is a
module that returns a free storage block but
fails to clear a pointer to the block that has
been saved elsewhere. All modules that return
blocks via a call to DMKFRET should first
verify that the saved pointer is nonzero; after
returning the block, any saved pointers should
be set to zero.

FRTOl1

A CP module has
attempted to return a
block of storage that is in
the user dynamic paging
area.

FRT013

The CP FRET Trap has
detected that a module is
attempting to release
storage and the trap
extension area cannot be
located.

Identify the program returning the storage by
means of the return address and stored base
registers (FREER14 and FREER12 in the PSA).
The common cause of this type of failure is a
module that returns a free storage block but
fails to clear a pointer to the block that has
been saved elsewhere. All modules that return
blocks via a call to DMKFRET should first
verify that the saved pointer is nonzero; after
returning the block, any saved pointers should
be set to zero.
Identify the module returning the storage by
means of the return address and base registers
(FREER14 and FREER12 in the PSA). The size
to return in FREERO or the free storage pointer
in FREER1 may have been destroyed. Also, the
extension may have been overlaid by the use of
more storage than was given. This may also be
an illegal attempt to return only a portion of
the original storage obtained.

Figure 9 (Part 9 of 29).

CP Abend Codes

VM/SP System Messages and Codes

CP Abend Codes
Abend
Code
FRT015

Reason for Abend
The CP FRET Trap has
detected that a module is
attempting to release
storage and the size in
FREERO does not match
the size found in the trap
extension area.

Action
Identify the module returning the storage by
means of the return address and base registers
(FREE14 and FREER12 in the PSA). If the
system running is UP generated or AP IMP
generated but not running, examine the
extension to the storage at FREERI + the
value of FREERO in bytes. Consult "Trapping
Improper Use of CP Free Storage" in the
VMI SP System Programmer's Guide for
problem determination information in the
extension. The value in FREERl is in error.
Examine the trace table for entries for storage
requests by the same VMBLOK that have not
been returned. Examine the code for
destruction of the free storage pointer in
FREERl.
If the system running is AP/MP, the abend

could have been caused by an illegal attempt to
return only a portion of the original storage
obtained. Examine storage for the ALLO tag at
FREERI the value of FREERO in bytes. If the
tag is found, examine the problem
determination information in the rest of the
extension. The free storage pointer in FREERl
could be incorrect or the abend could have
been caused by an illegal attempt to return the
back portion of the storage. If the ALLO tag is
not found at FREERl + FREERO, examine the
trap extension area at FREERI + the value of
FREERO in bytes + X'CO' bytes. The free
storage pointer in FREERl could be incorrect
or the abend could have been caused by an
illegal attempt to return the front portion of
the storage.
FRTOl6

The CP FRET Trap has
detected that a module is
attempting to release
storage that contains the
FRET tag in the trap
extension area.

Figure 9 (Part 10 of 29).

Identify the module returning the storage, by
means of the return address and base registers
(FREERl4 and FREER12 in the PSA). Examine
the extension to the storage at FREERI + the
value of FREERO in bytes. Consult "Trapping
Improper Use of CP Free Storage" in the
VMI SP System Programmer's Guide for the
problem determination information in the
extension area. The most common causes for
this type of failure are: the storage may have
been previously returned. or the free storage
pointer in FREERI may have been destroyed.

CP Abend Codes

System Codes

CP Abend Codes
Abend
Code

Reason for Abend

GRCOOI

DMKGRCUP was called
to generate the order
required to update the
3270 screen, but the
CONTASK supplied was
too small for the data
stream required.

HPSOOI

A routine process was
called to a device that was
not a logical device.
The user pointed to by
R11 issued a DIAGNOSE
instruction while
attempting to format the
I/O error, channel check,
or machine check
recording areas; the
SYSRES device is
unrecognizable.

HVDOOI

Action
The registers at entry to DMKGRCUP are
saved inBALRSAVE; the calling module can be
identified from BALR14, the input CONT ASK
address is in BALR6 and the input parameters
in BALR2 define the type of screen updating to
be done. See the GRTBLOK macro for
definitions of these parameters and of the
screen orders that are used.
Check the trace for activity to the device.

The RDEVBLOK for the SYSRES device was
probably destroyed, or a volume with the same
serial number as the SYSRES volume was
mounted. If a volume with the same serial
number was mounted, check the ATTACH
processing in the DMKVDB routine.

HVEOOI

The user pointed to by
R11 issued a DIAGNOSE
instruction while
attempting to format the
I/O error, channel check,
or machine check
recording areas; the
SYSRES device is
unrecognizable.

IOQ003

DMKIOQ is attempting to
remove an IOBLOK from
a queue, but that IOBLOK
contains an invalid
address.

Register 2 points to the RCHBLOK,
RCUBLOK, or RDEVBLOK from whose queue
the IOBLOK is being removed. Register 10
points to the IOBLOK. Use the CP internal
trace table to determine which module called
DMKIOS twice to start the same IOBLOK.

IOQ005

DMKIOQ was called to
find a channel path for an
IOBLOK dequeued from
the control unit. If the
I/O request was for a fixed
path and IOQ was not
entered on the requested
processor path, IOQ must
go to the requested
processor's channel index
table to calculate the
address of the requested
RCHBLOK. The abend
occurs when the index
value for the requested
channel is invalid
(X'FFFF').

Examine the IOBLOK to determine its
second-level interrupt handler (IOBIRA).
should make it possible to determine which
module was responsible for initializing fields in
the IOBLOK before the original call to lOS.
IOBRADD or IOBPROC may have been set up
incorrectly, or the IOBLOK may have been
overlaid.

Figure 9 (Part 11 of 29).

CP Abend Codes

VM/SP System Messages and Codes

CP Abend Codes
Abend
Code
IOQ006

IOQ007

10SOOl

10S002

IOS004

Reason for Abend
DMKIOS was called to
perform I/O to a device
that is logically online,
but for which there is not
available path online.
That is, the online path
status in RDEVPTHS does
not match the status
indicated by RDEVDISA.
In attempting to start an
I/O request, 10Q must
remove all alternate path
lOBs that exist on paths
to the device except the
one that is about to be
started. In scanning the
chain of these lOBs, two
were not marked as
mini-lOB, indicating two
real requests for the same
I/O.
The caller is trying to
reset an active 10BLOK
from the RCHBLOK
queue, but that 10BLOK
contains an invalid
address.
DMKIOS is attempting to
restart an IOBLOK from
the RCHBLOK queue, but
that 10BLOK contains an
invalid address.
DMKIOSHA was calied to
halt I/O associated with
an 10BLOK pointed to by
register 10. However,
register 10 points t.o an
IOBLOK that is marked
as a mini-lOB. A
mini-lOB is not allowed to
exist outside the control
ofDMKlOS.

Figure 9 (Part 12 of 29).

Action
Examine the trace table and storage dump to
determine what routine has incorrectly altered
either RDEVDISA or RDEVprrHS.

Examine the trace table to determine the
sequence of events that led to two lOBs being
passed to lOS and then having both lOBs occur
on the same request chain.

The 10BLOK may have been returned (via
DMKFRET) or destroyed. Verify that the
10BLOK was valid and use the 10BLOK and
RDEVBLOK to determine the last operation.

The 10BLOK may have been returned (via
DMKFRET) or destroyed. Verify that the
10BLOK was valid and use the 10BLOK and
RDEVBLOK to determine the last operation.
Examine the trace table in the storage dump
and determine what routine built and called
DMKIOSHA with 10BLOK marked as a
mini-lOB. That routine is in error.

CP Abend Codes

System Codes

CP Abend Codes
Abend
Code
IOS005

Reason for Abend
DMKIOS was called to do
a fixed path I/O request
and one of the following
occurred:

IOS009

IOS010

IUAOOI

IUCOOI
;

IUC002

The RDEVBLOK
located by using the
cuu address in
10BRADD is not equal
to the RDEVBLOK
poin ted to by R8 at
entry point DMKIOS.

In an MP
environment, the real
channel block
requested for the fixed
path could not be
located.

A Start I/O is attempted
for a sense CCW after a
short busy sequence from
a 3270. This causes the
IOBLOK to be queued.
The IOBSNSIO is on and
there is no 10ERBLOK
address in IOBIOER.
In attempting to restart
pending I/O requests. after
an I/O interrupt has made
an I/O unit available,
DMKIOS finds that the
current RCHBLOK does
not belong to the current
processor.

Examine the dump to determine why there is no
10ERBLOK address in 10BIOER.

A program check occurred
on the last
system-initiated IUCV
function.

Locate the last lUCY instruction from the trace
table and determine the type of lUCY function
requested. Determine what lUCY exceptions
are generated by that lUCY function (see the
VM/SP System Programmer's Guide).
Locate the path description for the specified
path ID. Then locate the corresponding path
ID for the target communicator and determine
why the entry has been marked invalid.

The path of the target
communicator contained
inconsistent or conflicting
status flags.
A pending connection for
the path specified could
not be found on the
pending connection chain.

Figure 9 (Part 13 of 29).

Action
Examine the trace table and determine who
called lOS to request fixed path I/O. Either an
incorrect call was made to DMKIOS, R8 did not
point to the correct real device block, or the
lOB that is pointed to by RIO was overlaid.

CP Abend Codes

VM/SP System Messages and Codes

Examine the CP trace table to find upon which
channel, control unit, and device path the I/O
interrupt occurred. Examine DMKIOT and
DMKIOS logic to see why DMKIOS is trying to
restart I/O on a different channel. If the trace
table shows that DMKIOS received control as a
result of a call, examine DMKIOS logic to see
how its internal indicators were changed to
show entry due to an I/O interruption.

Locate the path ID that was specified to
determine why no corresponding entry can be
found on the pending connection chain.

CP Abend Codes
Abend
Code
IUEOOI

IUGOOI

IUGOO2

IUJOOI

IUJOO2

IUJOO3

IUJOO4

Reason for Abend
On a Receive, lUCY has
located a message block
on the queue with the
specified message ID. The
path ID in the message
block is invalid (as
returned from
DMKIUAPD).
On a Reject, IUCV has
located a message block
on the queue with the
specified message ID. The
path ID in the message
block is invalid (as
returned from
DMKIUAPD).
No room was found for a
new path in the CCT.
When the CCT was built
(by the Declare Buffer
function), enough room
was allocated for all
possible connections.
The path of the target
communicator contained
inconsistent or conflicting
status flags.
A pending connection for
the path specified could
not be found on the
pending connection chain.
An error was encountered
on a IUCV Reject for a
message that is supposed
to be valid but was not
found on the message
queues.
An error was encountered
on a IUCV Purge for a
message that is supposed
to be valid but was not
found on the message
queues.

Figure 9 (Part 14 of 29).

Action
Locate the message block with the specified
message ID and determine the path ID that it
contains. Search the path description segment
for the corresponding path description and
determine why the entry has been marked
invalid.

Same as IUEOOl.

Compare the number of current connections
with the number of connections from the
directory. One possible reason for this error is
if the directory is modified dynamically and the
connection limit for a user is increased, the
space that was allocated for CCT is no longer
large enough.
Locate the path description for the specified
path ID. Then locate the corresponding path
ID for the target communicator and determine
why the entry has been marked invalid.
Locate the path ID that was specified to
determine why no corresponding entry can be
found on the pending connection chain.
Locate the message block that was to be
rej ected or purged and determine on which
queue it should be located. Search the message
queue to determine why it could not be located.

Locate the message block that was to be
rejected or purged and determine on which
queue it should be located. Search the message
queue to determine why it could not be located.

CP Abend Codes

System Codes

CP Abend Codes
Abend
Code
IULOOI

IUPOOI

LOKOOI

LOKOO3

MCTOOI

MHCOOI

Reason for Abend
On a Test Completion,
IUCV has located a
message block on the
queue with the specified
message ID. The path ID
in the message block is
invalid (as returned from
DMKIUAPD).
The path of the target
communicator contained
inconsistent or conflicting
status flags.
An OBTAIN request has
been made for a lock that
is held by the requesting
processor.

A RELEASE has been
issued for a lock that is
not owned by the
requesting processor.
DMKLOK does not get
control for a RELEASE
request.
Automatic Processor
Recovery (DMKMCTPR)
has received control on
the main processor
without the global system
lock and the lock could
not be obtained.
A MSSFCALL Diagnose
instruction was issued and
a nonzero condition code
was returned.
Note: Possible condition
codes are 0 and 2. A
condition code of 2
indicates that the MSSF
is busy. This condition
should not occur since CP
never issues a request if
an interrupt for the MSSF
is pending.

Figure 9 (Part 15 of 29).

CP Abend Codes

VM/SP System Messages and Codes

Locate the path description for the specified
path ID. Then locate the corresponding path
ID for the target communicator and determine
why the entry has been marked invalid.
Rl contains the lockword address at the time of
the abend. In the PSA of the abending
processor, the save area LOKSAVE contains
the return address of the caller at offset X'38'
and the entry point address into DMKLOK at
offset X'3C'.
Use the supervisor old PSW in the PSA of the
abending processor to identify the module
where the error occurred. Rl contains either
the lockword address (in the case of a global
lock) or the address of the VMBLOK (in the
case of a VMBLOK lock) at the time of the
abend.
Check DMKLOKSY to determine if the system
lock word has been overlaid. If the attached
processor owns the lock, check the R12 value in
DMKLOKSY + 4 to determine who obtained the
lock. The system should not be in automatic
processor recovery if the attached processor
was in supervisor state.
This is not an error condition. If the problem
persists, contact your system support personnel.

CP Abend Codes
Abend
Code
MHC002

MIA003

MNTOOI

NLEOOI

PGSOOI

Reason for Abend
An unsolicited MSSF
interrupt has been
received.
Note: Unsolicited MSSF
interrupts should not
occur.
An unrecoverable DASD
I/O error occurred on a
paging device.

The RDEVBLOK
corresponding to the
address of the IPLed
device cannot be located.
During execution of a
NETWORK DUMP
command, or during an
automatic dump of a 3704
or 3705, the system
detected sufficient DASD
spool space to contain the
information from the 3704
or 3705. The MODEL
operand of the RDEVICE
macro describing the 3704
or 3705 was not specified
correctly. VM/SP
determines the storage
size of a 3704 or 3705 by
the model specified on the
RDEVICE macro.
The resident page count
in the VMBLOK
(VMP AGES) is reduced to
a negative number.

Figure 9 (Part 16 of 29).

Action
This is an error condition, if the problem
persists, contact your system support personnel.

In most cases, location X'BA' will contain the
unit address of the failing device. For certain
errors, it may be necessary to scan the trace
table (from the current entry) looking for an
I/O interrupt from a paging device with a CSW
error. Call IBM hardware support.
Verify that an entry for the IPLed device has
been made in DMKRIO and that the defined
address matches the IPLed address.
Correct the RDEVICE macro specifying the
3704 or 3705, reassemble the DMKRIO module,
and regenerate the CP nucleus with the
corrected module.

Inspect module that updated VMPAGES for the
virtual machine. Check the routine to
determine why it is inconsistent with the
number of CORTABLE entries assigned to this
virtual machine.

CP Abend Codes

System Codes

CP Abend Codes
Abend
Code
PGTOOI

Reason for Abend
The number of cYlinders
in use stored in the
allocation block
(ALOCBLOK) is less than
the maximum but the
DMKPGT module was
unable to find available
cylinders.
Also see below.

PGTOOI

For FB-512 devices
(DMKPGT is allocating
on an FB-512 device) the
number of pages in use
(ALOFUSED) is less than
the maximum
(ALOFMAX), but
DMKPGT could not find a
RECBLOK containing an
available page.
Also see above.

PGTOO2

The count of pages in a
page allocation block
(RECBLOK) is less than
the maximum but the
DMKPGT module was
unable to find available
pages.

Figure 9 (Part 17 of 29).

CP Abend Codes

VMjSP System Messages and Codes

Action
The RDEV ALLN field of the RDEVBLOK is the
anchor for ALOCBLOK/ALOFBLOK chain for
the device in question and points to either the
ALOCPGFH (RECBLOK anchor for preferred
FH paging cylinders), ALOCPGMH (RECBLOK
anchor or preferred MH paging cylinders),
ALOCRECS (RECBLOK anchor for
non-preferred cylinders), or ALOCRECP
(RECBLOK anchor for temporary cylinders on
the page chain). Verify that a RECBLOK
exists for each cylinder marked and allocated
in the ALOCBLOK. If RECBLOKs for some
cylinders are missing, it is possible that the bit
map in the ALOCBLOK has been destroyed. If
all cylinders are accounted for, the updating of
the count field is in error.
Inspect the extents of TEMP space stored in
the ALOFBLOK. The ALOFBLOK has a
24-byte extension for each extent of TEMP
space pages on the volume. Anchored in this
extension are the RECBLOKs that describe the
availability of each page in this extent. Inspect
each RECBLOK to see if all the pages in each
RECBLOK are used. It is possible that the
RECBLOK chain or the ALOFBLOK extension
has been destroyed. If all pages are accounted
for, the number of available pages in all
RECBLOKs should add up to the number of
available pages stored in the ALOFBLOK
extension (ALOFNUMA). Also, the
ALOFNUMA fields of all ALOFBLOK
extensions should agree with the number of
available pages described in the ALOFBLOK
root ALOFMAX-ALOFUSED). If these count
fields do not agree, the updating logic in
DMKPGT is in error.
If the RECBLOK in question is in use for
paging, then locate a SWPT ABLE entry for
each page represented by this RECBLOK.
FB-512 RECBLOKs describe the range of page
numbers in fields RECSTRT and RECEND.
However, if the pages are in use for spooling, it
is possible that the RECBLOK itself has been
destroyed or that the updating of the use count
is faulty.

(

CP Abend Codes
Abend
Code
PGUOOI

Reason for Abend
The DASD page slot being
released is not marked
allocated.

PGU002

The dummy RECBLOK
indicating the spooling
DASD pages on the
cy linder that are to be
released contains a page
count greater than the
number of pages allocated
on the cylinder.

PGU003

A module is trying to
release a DASD page slot
on a cylinder or FB-512
extent for which no page
allocation block
(RECBLOK) exists.

PGU004

The last DASD page slot
in a RECBLOK has been
deallocated but the bit
representing the cylinder
in the cylinder allocation
block (ALOCBLOK) is not
currently set to one,
indicating that the
cylinder was not
allocated.

Action
Identify the module attempting to release the
page by means of the caller's return address
and base register stored in BALR14 and
BALR12 in the BALRSA VE save area in PSA.
Locate the source (control block or
SWPTABLE entry) of the DASD address being
released to verify that they have not been
destroyed. If the DASD page is in a spool file,
it is possible that the file or the RECBLOK
chain has been incorrectly checkpointed and
warmstarted after a system shutdown or a
system crasho
The spool file pointers may have been destroyed
while the file was being processed, or the
allocation chain may be in error. A cold start
may be necessary. If feasible, use the DASD
dump/restore program to print the DASD areas
containing the affected file, and try to locate
the incorrect pointers.
Use BALR14 and BALR12 in the BALRSA VE
save area of the PSA to identify the module
attempting to release the page. For
count-key-data DASD, verify that the DASD
cylinder address is valid for the device in
question. If it is and the rest of the DASD
address is valid, verify that the cylinder is in
the dynamically allocatable area. For FB-512
DASD, verify that the page number is valid and
in the dynamically allocated area. If these
restrictions are met, the DASD page must have
been used by more than one user.
The ALOCBLOK has probably been destroyed,
or the chain pointer in the RDEVBLOK is in
error.

Note: Because allocation
of pages on an FB-512
device does not use this
bit map, this code is not
applicable to FB-512
devices.
Figure 9 (Part 18 of 29).

CP Abend Codes

System Codes

51'

CP Abend Codes
Abend
Code
PGUOO5

Reason for Abend
The system's virtual
storage buffers have been
exhausted because of an
excessive number of open
spool files.

Action
Request users to close all spool files that are no
longer active.

PGUOO6

A module is trying to
release a page of virtual
storage in use by the
VM/SP control program
that has not been marked
allocated.

Use BALR14 and BALR12 in the BALRSAVE
save area of the PSA to identify the module
attempting to release the page. Locate the
control block containing the virtual page
address that is being released. It is possible
that the address has been destroyed, or a
pointer to a virtual page has been retained
after the page was destroyed.

PRGOOI

Program check (operation)
in the control program.
Program check (privileged
operation) in the control
program.
Program check (execute)
in the control program.
Program check
(protection) in the control
program.
Program check
(addressing) in the control
program.

Examine the old PSW and identify the module
having the program check.
Same as PRGOOl.

Program check
(specification) in the
control program.
Program check (data) in
the control program.
Program check
(fixed-point overflow) in
the control program.
Program check
(fixed-point divide) in the
control program.
Program check (decimal
overflow) in the control
program.
Program check (decimal
divide) in the control
program.
Program check
(exponential overflow) in
the control program.

Same as PRGOOl.

PRGOO2

PRGOO3
PRGOO4

PRGOO5

PRGOO6

PRGOO7
PRGOO8

PRGOO9

PRGOIO

PRGOll

PRG012

Figure 9 (Part 19 of 29).

CP Abend Codes

VM/SP System Messages and Codes

Same as PRGOOl.
Same as PRGOOl.

Same as PRGOOl.

Same as PRGOOl.
Same as PRGOOl.

Same as PRGOOl.

CP Abend Codes
Abend
Code
PRG013

PRG014

PRG015

PRG016
PRG017
PRG018

PRG019

PRG254

PRG255

PSAOO2

PSAOO3

Reason for Abend
Program check
(exponential underflow) in
the control program.
Program check
(significance) in the
control program.
Program check
(floating-point divide) in
the control program.
Program check (segment)
in the control program.
Program check (paging) in
the control program.
Program check
(translation) in the
control program.
Program check (special
operation) in the control
program.
A translation specification
exception has been
recei ved for a virtual
machine that is not in
extended control mode.
A PER (program event
recording) has been
received for a virtual
machine that is running
with PER disabled in its
virtual PSW.
The "System Restart"
console key was pressed.
The operator normally
takes this action when an
unusual system condition
occurs, such as a system
loop or slow machine
operation.
An unrecoverable DASD
error occurred on a
paging device, or the
paging device is offline.

Figure 9 (Part 20 of 29),

Action
Same as PRGOOl.

Same as PRGOOl.

Same as PRGOOl.
Same as PRGOOl.
Same as PRGOOl.

Same as PRGOOl.

If the set of translation tables pointed to by

RUNCRI is correct, a hardware failure has
occurred, possibly with dynamic address
translation. Otherwise, call IBM for software
support.
Retry the program causing the error; if the
problem persists, call IBM for software support.

Examine the resulting abend dump for a
dynamic picture of the system's status.

Check the trace table for a Start I/O in the
paging device with a condition code 3 to verify
device is offline. If offline, vary paging device
online. Check the unit address at X'B9' in the
PSA to find paging device in error. This is a
hardware error.

CP Abend Codes

System Codes

CP Abend Codes
Abend
Code
PSA004

PTR002

PTR003

PTR004

Reason for Abend
A CPU timer interrupt
occurred either while the
system was in a wait state
or when an enable window
was opened.

A program is attempting
to unlock a page frame
whose address exceeds
real storage size.
A program is attempting
to unlock a real storage
page frame whose
CORT ABLE entry is not
flagged as locked.
The lock count in the
CORT ABLE entry for the
page frame being
unlocked has been
decremented to a value
that is less than o.

Figure 9 (Part 21 of 29).

CP Abend Codes

VM/SP System Messages and Codes

Action
Check CPST ATUS in the PSA to determine
whether the interrupt occurred while in a wait
state or during an enable window. If the
interrupt occurred while in a wait state
(CPWAIT on in CPSTATUS), the timer value at
the time of the interrupt is stored in the PSAs
WAITEND. If the interrupt occurred during an
enable window (CPEX on in CPST ATUS), the
timer value is stored in the first two words of
the PSAs TEMPSAVEe If the timer value is
negative, it is probably a programming error.
Try to determine why the timer was set to a
negative value. If the timer value is positive,
obtain hardware support to determine why the
interrupt occurred.
Use the values of register 14 and register 12 at
the time of the abend to identify the module
attempting to unlock the page frame. Check
for the source of the invalid address.
Same as PTR002.

Check the routines that update the lock count
field and CORTABLE entry.

CP Abend Codes
Abend
Code
PTR007

PTR008

PTROI0

PTROll

PTR012

Reason for Abend
DMKFRE requested a
page for fixed free storage
but DMKPTR determined
that there were no pages
left in the dynamic paging
area.

A CORT ABLE entry on
the free list points to a
valid PTE (page table
entry), but the page is
allocated.
The count of the number
of resident reserved pages
incorrectly decremented
so that the count is now
less than zero.
A CORT ABLE entry to be
placed on the free list
points to a valid PTE
(page table entry), but the
page is allocated. An
abend occurs trying to
honor a deferred request.
A CORT ABLE entry to be
placed on the free list
points to a valid PTE
(page table entry), but the
page is allocated.

PTR014

DMKPRTFT was called to
put a page on the
FREELIST that is already
on the FREELIST.

PTR015

The core table entry for a
flush list page does not
contain a page table
pointer.

Figure 9 (Part 22 of 29).

Action
Examine the dump for one of the following
conditions:
Excessive amounts of free storage have
been allocated by CP and not released via
DMKFRET. Look for blocks of identical
data and determine which modules built
that data.
2. A block of storage greater that 4096 bytes
was requested. Requests for large blocks of
free storage require contiguous pages from
DMKPTR and as a result have a higher
probability of failure than requests for one
page or less. If possible, change the
application to reduce the size of storage
requests. Otherwise schedule the
application when storage is less fragmented.
Pages on the free list should not contain valid
PTEs. Examine the dump to determine which
module called DMKPTRFR. The module that
called DMKPTRFR probably contains an error.
1.

The field DMKPTRRC contains the number of
reserved pages. DMKPTRRC must always be
less than DMKDSPNP. Check the routines
that update these two count fields
(DMKDSPNP and DMKPTRRC).
Pages to be put on the free list should not
contain valid PTEs. Examine the dump to
determine why the page was not marked invalid
before the call the DMKPTRFT.

Pages on the FREELIST should not contain
valid PTEs. Examine the dump to determine
which module called DMKPTRFT, it probably
contains an error.
A page that is already on the FREELIST should
not be specified in a call to D:'MKPPTFT.
Check the FREELIST and flush list for validity.
Restart the system and~ if the problem persists,
call IBM for software support.
Examine the storage dump to determine either
how the page was placed on the flush list
without a PTE pointer or what module
subsequently modified the core table entry.

CP Abend Codes

System Codes

CP Abend Codes
Abend
Code
PTR018

PTR021

QCOOOI

I
RNHOOI

RNH002

Reason for Abend
The resident page count
in the VMBLOK
(VMPAGES) is reduced to
a negative value.
PTR was entered without
the global system lock,
but the VMBLOK already
has its deferred task
stacked. Some error has
occurred in failing to
obtain the global system
lock.
An I/O buffer is being
returned to FREE storage
but the CORFPNT for the
page does not contain the
character string CONB.
This means QCO is trying
to return a page to the
free list which was not
used as an I/O buffer for a
CONMODE'3270
SCRNSAVE operation.
An unrecoverable 1/0
error occurred during
read or write for the
3704/3705. Status
indicates program failure.
A response that should
not occur was received
from the 3704/3705 control
program.

:Figure 9 (Part 23 of 29).

CP Abend Codes

VM/SP System Messages and Codes

Action
Inspect modules that update VMPAGES for the
virtual machine. Examine the routine to
determine why is it inconsistent with the
number of CORT ABLE entries assigned to this
virtual machine.
Examine the SA VEAREA pointed to by R13 to
determine why PTR was called without the
global system lock.

Search the trace table to determine why the
storage being released does not have CONB in
CORPFNT. The page is obtained by a call to
DMKPTRFR and is released by a call to
D~IKPRTRFT.

Retry. If the problem persists, ensure that the
3704/3705 and channel hardware are
functioning correctly.

Verify that the 3704/3705 NCP is operating
correctly. Use the NETWORK TRACE
command to determine the exact cause of the
response.

CP Abend Codes
Abend
Code
RPAOOI
RPAOO2

Reason for Abend
For RP AOOI, the virtual
address supplied to
DMKRPAGT is outside of
the virtual storage being
referenced.
For RP A002, the virtual
address supplied to
DMKRAPT is outside of
the virtual storage being
referenced.

RPAOO3

The user page count in
the VMBLOK became
negative.

SCHOOl

The total number of
in teracti ve users pI us
batch users in the
scheduler"s queue is less
than zero. A counter was
probably decremented
incorrectly.
A call was made to
DMKSCHDL that resulted
in an attempt to drop a
user from a runable list,
but the global system lock
was not held by the caller.
RDEVDISA equals zero
but DMKSCNEP can find
no online path to the
device.
The VDEVLINK chain is
invalid. A VDEVBLOK
has a link field that points
to another VDEVBLOK
associated with the same
real device. The first
VDEVBLOK is not
pointed to by any other
link field in the chain.

SCHOO2

SCNOO2

SCOOOI

Figure 9 (Part 24 of 29).

Action
The virtual storage belongs either to the user
whose VMBLOK is pointed to by RII or, if R2
in the SA VEAREA indicates a P ARM of
SYSTEM, to the system VMBLOK. Identify
the calling program by means of the return
address and base registers in the SA VEAREA
pointed to by RI3. If the virtual address was
obtained from the system's virtual storage,
examine the virtual page allocation routine,
DMKPTRVG. If the virtual page refers to a
user's storage, attempt to identify the routine
that generated the incorrect address. Verify
that the VMSIZE in the relevant VMBLOK
reflects the correct storage size for the system
or user being referenced.
A module has attempted to release more pages
than it originally received. The module that
last called DMKRPA is probably the module in
error.
The field SCHNI is the count of the number of
interactive users and the field SCHN2 is the
count of the number of batch users. Check the
routines that update these two count fields
(SCHNI and SCHN2) to determine why their
sum was negative.
Examine the registers in BALRSA VE to find
the caller to DMKSCHDL. See why the caller
did not hold the global system lock.

Check trace table for activity to the device.
Try to determine why RDEVPATHS has no
online paths yet RDEVDISA indicates that the
device is online.
IPL to restart. If the problem persists, examine
the VDEVBLOKs in the link chain as well as
the one whose link field points into the chain
but is not in the chain. Determine what the
owner of the VDEVBLOK was doing at the
time.

CP Abend Codes

System Codes

CP Abend Codes
Abend
Code
SEGOOI

SEGOO2

Reason for Abend
N one of the devices
defined in DMKRIO and
available to the system
match the label defined in
the SYSRES macro in
DMKSYS.

The label on the IPLed
device does not match the
label defined in DMKSYS.

SEGOO3

An error occurred
attempting to page out
DMKVMI or DMKSYM,
or while attempting to
read in a pageable
module.

STKOOI

DMKSTK was attempting
to stack an IOBLOK, a
TRQBLOK, or a
CPEXBLOK for a
particular virtual machine
and the counter in the
VMBLOK overflowed its
half-word boundary
making the counter
appear negative. Since
this will happen only
when the counter exceeds
32,767, the probable cause
of this error is either a
program loop that
includes the stacking of a
CPEXBLOK, IOBLOK, or
TRQBLOK, or an overlay
of the VMBLOK.

Figure 9 (Part 25 of 29).

CP Abend Codes

VM/SP System Messages and Codes

Action
Verify that the SYSRES volume serial number
is the same as that specified in the SYSRES
macro. If it is not the same, it may have been
altered by the LABEL option of the FORMAT
function of the stand alone CP format program
(IPL FMT or DMKFMT). Otherwise, the image
of the nucleus saved on the SYSRES may have
been altered. Restore the nucleus to the
SYSRES volume from a backup copy and try to
IPL.
Since Abend Code SEGOOI did not occur, a
device with the correct label does exist. Verify
that the correct device was IPLed; otherwise,
verify that the· SYSRES volume serial number
is the same as that specified in the SYSRES
macro in DMKSYS. If it is not the same, it
may have been altered by the LABEL option of
the FORMAT function of the stand alone CP
format program (IPL FMT or DMKFMT).
Otherwise, the image of the nucleus saved on
the SYSRES may have been altered. Restore
the nucleus to the SYSRES volume from a
backup copy and try to IPL.
Try to determine whether the errors are being
caused by the paging device or by the paging
volume. If the device is failing, disable it and
reload (via IPL) the system; call IBM for
hardware support. If the volume is failing, try
reformatting it. If the error condition recurs,
discontinue using that volume and call your
system support personnel.
Verify that the counters in the VMBLOK
reflects the correct number of BLOKs stacked
for this virtual machine. If they do not,
determine who has overlaid either VMSTKCNT
(the count of IOBLOKs, TRQBLOKs, and
normal CPEXBLOKs) or VMPRRCT (the count
of processor related CPEXBLOKs). If the
VMBLOK counters are accurate, identify the
caller of DMKSTK by looking in SWTHSAVE
in the PSA of the abending processor. The R14
value in the save area contains the return
address of the caller of DMKSTK.

(

CP Abend Codes
Abend
Code
STROOI

STROO3

STROO4

STROO7

SVCOOI

Reason for Abend
LRA gets a translation or
length condition code for
a valid page.
An attempt is being made
to migrate a table into
storage for a segment that
is already valid.
An attempt is being made
to bring a page into
storage that does not
exist.
The save area stack chain
is invalid or the specific
request could not be found
on the chain.
No free storage is
available for save areas.

SVCOO2

A supervisor state SVC
was issued without the
global system lock.

SVCOO3

An unrecoverable DASD
I/O error occurred on a
paging device.

SVCOO4

Error in SVC 24
CPEXBLOK maintenance.
An SVC 24 has been
issued during the
EXTEND process. There
is no preallocated
CPEXBLOK available for
use by SVC 24. Most
likely the system is
attempting to enter
EXTEND while already
performing EXTEND
processing.

Figure 9 (Part 26 of 29).

Action
If the problem persists, obtain a dump and call
IBM for software support.
Same as STROOl.

Same as STROOl.

Try to identify the extreme load condition that
caused the problem. If the storage requests are
valid and the problem occurs regularly, alter
the DMKCPI module to allocate more than six
pages of free storage per 256K bytes of storage.
Use the supervisor old PSW in the PSA of the
abending processor to identify the module that
issued the SVC without the system lock.
In most cases, location X'B9' will contain the
unit address of the failing device. For certain
errors it may be necessary to scan the trace
table (from the current entry) looking for an
I/O interrupt from a paging device with a CSW
error. Call IBM for hardware support.
Examine the internal trace table to determine
why the two preallocated SWITCH
CPEXBLOKs have not been dequeued.

CP Abend Codes

System Codes

CP Abend Codes
Abend
Code
TDK001
TDK002

Reason for Abend
For TDK001, a program is
attempting to deallocate a
cylinder or FB-512
extent(s) of T.;disk space
for which no cylinder
allocation block
(ALOCBLOK) exists. For
FB-512 devices, the
allocation control block is
called ALOFBLOK.
For TDK002, A program is
attempting to deallocate
cylinder(s) of T-disk space
that are not marked
allocated.

TOD001
UDR001

UDR002

VCX001

VCX002

The system TOD clock is
not operational.
The user directory module
is looping trying to read
all of the UDIRBLOK
page buffers from the
directory device, or a
directory. containing over
10,816 users was loaded.
The resident page count
in the VMBLOK
(VMPAGES) is reduced to
a negative number.
DMKVCX issues this
abend if the
In ter-User-Communication
Vehicle (IUCV) paths for
SNA Console
Communications Services
(SNA CCS) are invalid.
DMKVCX issues this
abend if SNA Console
Communication Services
(SNA CCS) control block
structure is invalid.

Figure 9 (Part 27 of 29).

CP Abend Codes

VM/SP System Messages and Codes

Action
Verify that R8 points to a RDEVBLOK for a
CP-owned volume. If it does not, the error may
originate in the calling program. Identify the
caller by the return address and base register
in the SAVEAREA pointed to by R13, and try
to identify the source of the incorrect
RDEVBLOK address. If the RDEVBLOK is
valid, it may be that the cylinder number
passed is incorrect. The VDEVBLOK for the
device which the T-disk was defined may have
been destroyed. If the cylinder number appears
valid, examine the allocation record on the real
volume by running DMKFMT (Format
program), invoking the ALLOCATE option
without allocating any new space. If the
output shows deallocated cylinder falls within
an area defined for T-disk allocation, the
ALOCBLOK or ALOFBLOK chained to the
RDEVBLOK may be destroyed.
Call IBM for hardware support to fix the clock.
Use the DASD Dump Restore program to print
the UDIRBLOK page buffers from the directory
device. Determine whether the chain pointers
are valid.

Inspect modules that update VMP AGES for the
virtual machine. Check the routine to
determine why it is inconsistent with the
number of CORTABLE entries assigned to this
virtual machine.
Check the IUCV paths and SNA CCW control
blocks to determine what is in error.

Examine the control block structure and SAN
CCS trace table entry for the abend to
determine what is in error.

CP Abend Codes
Abend
Code
VDROO2

VDROO3

VDSOOI

VIOOO2

VIOOO3

VIOOC4

Reason for Abend
DMKSCNVU was unable
to locate all of the virtual
I/O control blocks for the
virtual unit address.

The DASD link chain is
invalid. In the case of
minidisks, detaching a
minidisk that points to an
RDEVBLOK whose count
of users is already zero
causes this abend.
A virtual device definition
has been requested for a
mini disk that is already
defined to the system
(either as a different
device to the user or a
device to another user on
the system). The
directory indicates that
the minidisk uses the
virtual reserve release
logic, but there is no
existing VRRBLO K.
DMKSCNVU was unable
to locate all of the virtual
I/O control blocks for the
virtual uni t address
associated with the
interrupt just stacked.

DMKIOS has returned an
10BLOK indicating a
condition code of 2 was
received from the START
I/O for the operation.
DMKSCNVU was unable
to locate all of the virtual
I/O control blocks for the
virtual unit address.

Figure 9 (Part 28 of 29).

Action
Determine whether the unit address in register
1 is valid for the user. RII contains the address
of the users VMBLOK. If invalid, the user's
virtual I/O configuration has been altered after
losing control. Examine the dump to determine
how it was altered.
IPL to restart. If the problem persists, examine
the RDEVSYS flag. If the RDEVSYS flag is off,
the problem is especially serious; print and
examine the dump. Examine the VDEVBLOK
and RDEVBLOK checking the link chain.

Examine the virtual blocks for the existing
links to the minidisk and determine why the
existing virtual device block pointed to by R3
does not point to a VRRBLOK.

Verify that the unit address in the field
10BVADD in the 10BLOK pointed to by RIO is
valid for the user who initiated the I/O. The
field 10BUSER contains the address of the
user's VMBLOK. If the address is valid, the
integrity of the user's virtual I/O configuration
has probably been destroyed. If the address is
not valid, the 10BLOK has been altered, or was
built incorrectly in the first place.
Condition code 2 should never be returned to
the virtual I/O interrupt handler. Its presence
indicates either a failure in the I/O supervisor
(DMKIOS), or that the status field in the
10BLOK (lOBST AT) has been destroyed.
Determine whether the unit address in register
1 is valid for the user. RI1 contains the address
of the users VMBLOK. If invalid, the user's
virtual I/O configuration has been altered after
losing control. Examine the dump to determine
how it was altered.

CP Abend Codes

System Codes

CP Abend Codes
Abend
Code
VMA008

VMEOOI

VSPOOI

VSVOOI

WRNOOI

Reason for Abend
The resident page count
in the VMBLOK
(VMPAGES) is reduced to
a negative value.

Action
Inspect modules that update VMPAGES for the
virtual machine. Check the routine to
determine why it is inconsistent with the
number of CORT ABLE entries assigned to this
virtual machine.

The dump chain anchored
DMKRSPDP has lost the
in-process VMDUMP.
The virtual spooling
manager could not locate
all virtual control blocks
for an interrupting unit.

Initialize the system to restart. If the problem
persists, notify the system programmer.

DMKVSVLD was called
to analyze a 3800 printer
op-code and the CCW
op-code in VSPCCW was
not a valid 3800 printer
Load CCW.
The map for a dynamic
checkpoint was not
allocated prior to a call to
DMKWRNPL.

Figure 9 (Part 29 of 29).

CP Abend Codes

VMjSP System Messages and Codes

Verify that the unit address (IOBV ADD) in the
IOBLOK is valid. If the address is valid, the
integrity of the virtual I/O configuration has
probably been destroyed. If the address is not
valid, the IOBLOK has been altered or was
built incorrectly.
Determine the caller of DMKVSRLD and see
why it was called when VSPCCW could not be
handled by this module.

The map should be allocated via a call to entry
points DMKCKSIN or DMKCKVWM from
DMKWRM.

(

CMS Abend Codes

CMS Abend Codes
When a CMS abend occurs, you must do the following:
1.

Either enter DEBUG mode and issue the DUMP subcommand, or get a
CP read on your terminal (or type #cp), and issue the DUMP command.
Either of these actions causes a storage dump. Do not issue the DUMP
command in CMS mode, because abend processing will take place
before the dump is performed and the indications of the error will be
lost.

Save the console sheet. If you are using a display terminal as your
virtual console, it is a good idea to spool your console output to the
printer by issuing the CP command SPOOL CONSOLE START either at
the start of the session or by having the command in your PROFILE
EXEC. Then if a problem does arise, a copy of your terminal activity
will be available for reference. If the session is uneventful, the
resulting printer file can be purged.

After the DUMP command is executed, the system automatically
initiates recovery procedures, so it should not be necessary to IPL CMS
again. If, however, an error message is displayed indicating that error
recovery has failed, you should reinitialize (via IPL) CMS.

To report a CMS problem, give the dump, the console sheet (or printed
console file, if it was spooled), and copies of the CMS files involved to
system support personnel.

Figure 10 on page 64 lists the CMS abend codes and the modules that issue
them, the cause of the abnormal termination, and the action the user
should take to recover and continue.

System Codes

CMS Abend Codes
Abend Module
Code
Name
001
DMSSCT

034

DMSVIP

035

DMSVIP

09F.

DMSITP

Cause of Abend
The problem program
encountered an input/output
error processing an OS
macro. Either the
associated DCB did not have
a SYNAD routine specified
or the I/O error was
encountered processing an
OS CLOSE macro.
The problem program
encountered an I/O error
while processing a VSAM
action macro under VSE/ AF
for which there is no OS
equivalent. An internal
error occurred in a
VSE/VSAM routine.
An error occurred in
VSE/VSAM processing
while running an OS/VSAM
program for which there is
no equivalent OS/VSAM
error code.
A vector operation
exception (program
interrupt code X'19')
occurred at a specified
location.

Action
Message DMSSCT120S
indicates the possible cause of
the error. Examine the error
message and take the action
indicated.

Refer to the VSE/ VSAM
Messages and Codes to
determine the cause of the
VSAM error.

Refer to the VSE/VSAM
documentation for the error
and return codes indicated in
the CMS error message
preceding the ABEND.
Type DEBUG to examine the
PSW and registers at the time
of the exception. Use the CP
DISPLA Y command to examine
the Vector Registers.
Refer to the IBM System/370
Vector Operations, SA22-7125
for a description of the vector
operation exception.

Figure 10 (Part 1 of 5).

eMS Abend Codes

VM/SP System Messages and Codes

CMS Abend Codes
Abend Module
Code Name
DMSITP
OCx

Cause of Abend
The specified hardware
exception occurred at a
specified location. "x" is
the type of exception:

Action
Type DEBUG to examine the
PSW and registers at the time
of the exception.

Type
Operation
Privileged operation
Execute
Protection
Addressing
Specification
6
7 Data
Fixed-point overflow
8
Fixed-point divide
9
A Decimal overflow
B Decimal divide
C Exponent overflow
D Exponent underflow
E Significance
F Floating-point divide
A special operation
exception (program
interrupt code X'13')
occurred at a specified
location.
A hardware exception
occurred at a specified
location.

x
1
2
3
4
5

OD3

DMSITP

OEO

DMSITP

OFO

DMSITS

Type DEBUG to examine the
PSW and registers at the time
of the exception.

Type DEBUG to examine the
PSW and registers at the time
of the exception. Bytes 2 and 3
of the BC Mode Program Old
PSW are the program interrupt
code. This indicates the type of
exception that occurred.

Insufficient free storage is
available to allocate a save
area for an SVC call.
I

Refer to the IBM System/370
Principles of Operation,
GA22-7000 or the IBM
System/370 Vector Operations,
SA22-7125 for a description of
the hardware exception.
If the abend was caused by an
error in the application
program, correct it; if not, use
the CP DEFINE command to
increase the size of virtual
storage and then restart CMS.
Refer to the IBJ.VI System/370
Principles of Operation,
GA22-7000 or the IBM
System/370 Vector Operations,
SA22-7125 for a description of
the hardware exception.

Figure 10 (Part 2 of 5).

eMS Abend Codes

System Codes

CMS Abend Codes
Abend Module
Code
Name
OF1
DMSITS
OF2

DMSITS

OF3

DMSITS

OF4

DMSITS

OF5

DMSITS

OF6

DMSITS

OF7

DMSFRE

OF8

DMSFRE

101

DMSSVN

104

DMSVIB

155

DMSSLN

Cause of Abend
An invalid halfword code is
associated withSVC 203.
The CMS nesting level of 20
has been exceeded.
CMS SVC (202 or 203)
instruction was executed
and provision was made for
an error return from the
routine processing the SVC.
The DMSKEY key stack
overflowed.
The DMSKEY key stack
underflowed.
The DMSKEY key stack
was not empty when control
returned from a command or
function.
Occurs when
TYPCALL = SVC (the
default) is specified in the
DMSFREE or DMSFRET
macro.
Occurs when
TYPCALL = BALR is
specified in the DMSFREE
or DMSFRET Macro calls.
The wait count specified in
an OS WAIT macro was
larger than the number of
ECBs specified.
The OS interface to
VSE/VSAM is unable to
continue execution of the
problem program.
Error during LOADMOD
after an OS LINK, LOAD,
XCTL, or ATTACH. The
compiler switch is on.

Figure 10 (Part 3 of 5).

CMS Abend Codes

VM/SP System Messages and Codes

Action
Enter DEBUG and type GO.
Execution continues.
None. Abend recovery take
place when the next command
is entered.
Enter DEBUG and type GO.
Control returns to the point to
which a normal return would
have been made.
Enter DEBUG and type GO.
Execution continues and the
DMSKEY macro is ignored.
Same as OF4.
Enter DEBUG and type GO.
Control returns from the
command or function as if the
key stack had been empty.
When a system abend occurs,
use DEBUG to attempt
recovery.

When a system abend occurs,
use DEBUG to attempt
recovery.
Examine the program for
excessive wait count
specification.
See the additional error
message accompanying the
abend message, correct the
error, and reexecute the
program.
See the last LOADMOD
(DMSMOD) error message for
error description. In the case
of an I/O error, recreate the
module. If the module is
missing, create it.

-CMS Abend Codes
Abend Module
Name
Code
DMSSLN
15A

160

DMSXSU

174

DMSVIB

177

DMSVIB
DMSVIP

Cause of Abend
Severe error during load
(phase not found) after an
OS LINK, LOAD, XCTL, or
ATTACH. The compiler
switch is on.
Xedit has failed because; an
error occurred while the
editor was reading from the
CMS console stack, or the
editor was unable to
allocate a save area.
The OS interface to
VSE/VSAM is unable to
continue execution of the
problem program.

200

DMSSFF
I

240

DMSSVT

400

DMSSVT

500

DMSTLB

704

DMSSMN

705

DMSSMN

The OS interface to
VSE/VSAM is unable to
continue execution of the
problem program.
There is an error in the
overlay process.
No work area was provided
in the parameter list for an
OS RDJFCB macro.
An invalid or unsupported
form of the OS XDAP macro
was issued by the problem
program.
A block count error was
detected when reading a SL
tape. User replied 'cancel'
to message 425R or the
user's program contained a
block count error routing
that returned a code of 0
under OS simulation.
An OS GETMAIN macro
(SVC 4) was issued
specifying the LC or L U
operand. These operands
are not supported by CMS.
An OS FREEMAIN macro
(SVC 5) was issued
specifying the L operand.
This operand is not
supported by CMS.

Figure 10 (Part 4 of 5),

Action
See last LOAD error message
(DMSLIO) for the error
description. In the case of an
I/O error, recreate the text deck
or TXTLIB. If either is
missing, create it.
Issue the XEDIT command
again. If the problem persists,
contact your system support
personnel.

See the additional error
message accompanying the
abend message, correct the
error, and reexecute the
program.
Same as 174.

Find out what caused the error
and rerun the job.
Check RDJFCB specification.

Examine program for
unsupported XDAP macro or
for SVC O.
Find out what caused the block
count error. Then reload CMS
and rerun the job.

Change the program so that it
specifies allocation of only one
area at a time.

Change the program so that is
specifies the release of only one
area at a time.

CMS Abend Codes

System Codes

CMS Abend Codes
Abend Module
Code Name
804
DMSSMN
80A

905
90A

DMSSMN

A05
AOA

DMSSMN

Cause of Abend
An OS GETMAIN macro
(804 - SVC 4, 80A - SVCIO)
was issued that requested
either zero bytes of storage,
or more storage than was
available.

An OS FREEMAIN macro
(905 - SVC 5, 90A - SVCIO)
was issued specifying an
area to be released whose
address was not on a
doubleword boundary.
An OS FREEMAIN macro
(A05 - SVC 5, AOA - SVC 10)
was issued specifying an
area to be released which
overlaps an existing free
area.

Figure 10 (Part 5 of 5).

CMS Abend Codes

VM/SP System Messages and Codes

Action
Check the program for a valid
GETMAIN request. If more
storage was requested than was
available, increase the size of
the virtual machine and retry.
If you ran out of storage while
trying to acquire a large
GETMAIN area, and your
virtual machine size is above
the start of the CMS nucleus,
you should IPL a CMS system
generated at a higher virtual
address than the one you are
using.
Check the program for a valid
FREEMAIN request; the
address may have been
incorrectly specified or
modified.
Same as 905 and 90A.

GCS Abend Codes

GCS Abend Codes
Responding to Abends in GCS
If an abend occurs in a Group Control System application program:
1.

The GCS supervisor will clean up the GCS system resources that the
failed application was using. In addition, the application can specify
exit routines to do further cleaning up and to try to resume processing.

2. If the application has no exit routines that try to restart it, the operator
must manually restart it. If the GCS system itself has failed, the
operator must re-IPL the system.
GCS provides several aids for diagnosing and correcting the problem that
caused the abend.
For some problems, you may find that Figure 11 on page 71 will provide all
the information you need. Entries in the table explain the causes of GCS
abends and list steps you can take to recover and continue. The table is
arranged numerically by abend code.
For more difficult problems, GCS provides trace and dump facilities,
interactive dump analysis under CMS, and interactive debugging under CPo
An overview of these facilities follows; for more detailed information, please
see the VM/ SP Group Control System Guide.

Overview of Problem Determination Facilities
GCS supports both internal and external tracing for error analysis.
Internally, the GCS trace table automatically records GCS supervisor
activity. With the ITRACE command and GTRACE macro, you can record
other activity in particular GCS virtual machines or in the GCS group as a
whole. External tracing, using the CP CPTRAP and GCS ETRACE
commands, records activity in a spool file. This file can then be formatted
for viewing using VM/SP's TRAPRED program.
If a GCS application program fails, GCS will automatically produce a dump
when:
1.

The GCS supervisor terminated the program by issuing the ABEND
macro.

The failing application program issued ABEND with the DUMP
operand.

The exit routine specified in an ESTAE, TASKEXIT, or MACHEXIT
macro requested a dump.

The dump will be sent to the designated dump receiver, if there is one, or to
the reader of the virtual machine in which the application failed. You can

System Codes

GCS Abend Codes
manually request a dump of GCS storage by issuing the GDUMP command
from the GCS console.
Your installation may want to set up application programs to produce
dumps automatically if they abend. Dumps produced during abend
processing may capture more information about an error than dumps
produced with GDUMP or VMDUMP, after abend processing has been
completed.
If a severe error occurs and the GCS supervisor abends, the GCS machine
termination module will try to take a dump of GCS storage. If the machine

termination module is unable to get the dump, you can use the CP
VMDUMP command to get it. The CP command SYSTEM RESTART will
also produce a dump of GCS storage.
Once storage has been dumped, you can interactively analyze the dump
using the VM/SP Interactive Problem Control System (IPCS).
If you are authorized to do so, you can also use CP debugging commands

such as BEGIN, DISPLAY, DUMP, PER, and STORE to trace GCS
execution interactively.

VM/SP System Messages and Codes

(

GCS Abend Codes
Abend Reason Module
Code
Code
Name
CSISCT
001

005

CSISQS,
eSISBS

OOA

CSISCT

010

CSISBS

Figure 11 (Part 1 of 30).

Cause of Abend
An input/output. error
occurred during BSAM or
QSAM processing.

An error occurred during
GET, PUT, READ, or WRITE
macro processing. A required
address was not specified or
was not valid. The required
address may have been the
DCB address, the
DCBRECAD address, the
DCBEOBAD address or the
area address.
An error occurred during
CHECK, NOTE, or POINT
macro processing. A required
address was missing or was
invalid. The required address
may have been the DCB
address or the DECB address.
An error occurred during
READ macro processing
because the SB option was
specified. This option is not
supported by GCS.

User Response
Error message CSI306S
(input errors) or CSI307S
(output errors) will have
preceded this abend
message. Look up the error
code from the error message
under message 306 or 307 in
the GCS message reference.
Use the error code tables for
'SER' or 'SCT' messages,
and respond accordingly.
Correct the invalid address

Correct the invalid address.

Remove the 'SB' option.

GCS Abend Codes

System Codes

GCS Abend Codes
Abend Reason Module
Name
Code
Code
CSISOP
013

Cause of Abend
An error occurred during the
execution of an OPEN macro
instruction.

014

CSISCL

An error occurred during
execution of a CLOSE macro
instruction.

035

CSIVIP

An error was detected by
VSE/VSAM for which there
is no equivalent OS/VS
VSAM error code.

036

CSIVIB,
CSIVSI

An error was detected while
trying to access the VSAM,
BAM, or VTAM shared
systems.

037

CSIDAS, A disk defined for use with a
CSIDOS, VSAM program could not be
CSIVIP used. The disk was in the
wrong format, was not
accessed, or was not
attached.

Figure 11 (Part 2 of 30).

GCS Abend Codes

VM/SP System Messages and Codes

User Response
Error message CSI308E or
CSI348E (OPEN errors) will
have preceded this abend.
Please see the 'User
Response' sections for those
messages and respond as
indicated.
Error message CSI309E or
CSI349E (CLOSE errors)
will have preceded this
abend message. Please see
the 'User Response' sections
for those messages and
respond as indicated.
A GCS error message will
have preceded this a bend
message. Please see the
'User Response' section for
the error message that
appeared and respond as
indicated.
A GCS error message will
have preceded this abend
message. Please see the
'User Response' section for
the error message that
appeared and respond as
indicated.
For modules CSIDAS and
CSIVIP, a GCS error
message will have preceded
this abend message. Please
see the 'User Response'
section for the error
message that appeared and
respond as indicated. There
is no preceding error
message when this abend is
issued from module CSIDOS.

GCS Abend Codes
Abend Reason Module
Code
Code
Name
038

039

03A

03B

CSIDOS

Cause of Abend
An I/O error occurred on a
disk being used for VSAlVI
processing.

CSIVIP, An internal error occurred
CSIDAS, during VSAM processing.
CSIDOS,
CSILDF

CSIVIP

C·SIVIP

Figure 11 (Part 3 of 30).

The number of exits defined
for use with VSAM exceeded
the limit of 128 exits.

An invalid address was
detected in a VSAM control
block or VSAM parameter
list. The address is not
located in storage that the
current program has access
to.

User Response
A GCS error message will
have preceded this abend
message. Please see th e
'U ser Response' section for
the error message that
appeared and respond as
indicated.
A GCS error message will
have preceded. this abend
message. Please see the
'User Response' section for
the error message that
appeared and respond as
indicated.
A GCS error message will
have preceded this abend
message. Please see the
'User Response' section for
the error message that
appeared and respond as
indicated.
A GCS error message will
have preceded this abend
message. Please see the
'U ser Response' section for
the error message that
appeared and respond as
indicated.

I
iI

I
I

GCS Abend Codes

System Codes

GCS Abend Codes
Abend Reason Module
Code
Code
Name
CSIITP
Oen

Cause of Abend
A program check has
occurred. The 'n' in the
Abend Code column for this
entry stands for the number
of the program check that
has occurred. on' should be
one of the following in your
message:
Code Meaning
A program check other
than 1-F has occurred.
Operation
1
2
Privileged operation
3
Execute
4
Protection
Addressing
5
Specification
6
Data
7
8
Fixed-point overflow
Fixed-point division
9
A
Decimal overflow
B
Decimal divide
C
Exponent overflow
D
Exponent underflow
E
Significance
Floating-point divide
F
An sve 202 or 203 routine
indicated that an error
occurred in processing the
sve, but no provision has
been· made for an error return
from the routine processing
the SVC.

User Response
Examine the Program Old
PSW at location 40 (X'28') to
find out the cause of the
program check.

OFa

eSIITS

Figure 11 (Part 4 of 30).

GCS Abend Codes

VMjSP System Messages and Codes

(

Find out why the error
occurred, or indicate that an
error return is desired. To
allow for an error return,
provide an error address for
the sve 202, or negate the
halfword code for the SVC
203 and reissue the
command.

GCS Abend Codes

)

Abend Reason Module
Code
Code
Name

Cause of Abend

User Response

OF8

CSIITS

A task has issued an SVC
202, but register 1 was
pointing to non-addressable
storage.

Find out why the contents
of register 1 were invalid·
and correct the problem.

OFA

CSIITS

GCS could not process an
SVC issued by a user
program that was running in
problem state. The failure
occurred because the DOS
bit-- a flag controlled by the
GCS supervisor--was on when
the SVC was issued. This bit
must always be off when a
problem state program issues
an SVC.

Find out why the DOS bit
was on and correct the
problem. The DOS bit may
have been turned on by
mistake by an authorized
GCS program, or the GCS
supervisor may have
malfunctioned.

101

CSIWAI

Invalid parameter list for the
WAIT macro. WAIT was
issued with other than 0 or 1
entered as the number of
events to be completed before
the waiting task can proceed.

Correct the WAIT macro
parameter specifying the
number of events. That
parameter must be either 0
or 1.

102

CSIWAI

A POST macro has been
issued with an invalid ECB
address. The user is not
authorized to access the
storage specified by the ECB
address.

Check to see that the ECB
address is correct. If you
are posting an ECB that is
part of an ECBLIST, check
that the task that issued the
WAIT is still authorized
over it's storage area. The
ECBLIST addresses may
have been overwritten.

106

CSILOS, The supervisor was unable to
CSIPMC, fetch the program requested
CSIPML in a LINK, LOAD, or XCTL
macro into virtual storage.
Register 15 contains a reason
code:

If the reason code is OB,
correct the cause of the I/O
errors. If the reason code is
OC, use a larger virtual
storage size, delete
unneeded modules, or take
other steps to make more
efficient use of storage.

Code
OB
OC

Meaning
I/O error while
loading the
module.
Insufficient virtual
storage available.

This abend can result when a
user program issues a LINK.
LOAD, or XCTL macro
directly. But the failure may
also occur when an ATTACH
macro or an OSRUN or
LOADCMD command is
issued, since these call LINK
or LOAD.
Figure 11 (Part 5 of 30).

GCS Abend Codes

System Codes

GCS Abend Codes
Abend Reason Module
Ca use of Abend
Code Code
Name
CSIPMB Invalid input was passed to a
112
BLDL macro. The problem
may have been that (1) the
start or end of the BLDL list
referred to an address that
was in a different key than
that of the calling program;
or
(2) the number of entries was
less than 1; or
(3) the length of a list entry
was less than 58 bytes.
CSIATT The task id that has been
12C
passed to a CHAP macro is
invalid for one of the
following reasons:

•
•
•

•
Figure 11 (Part 6 of 30).

The task id is associated
with a system task
instead of a user task.
That is, the task id was 1
or 2.
The task id does not
exist.
The task identified by the
task id is not an
immediate descendant of
the task that issued the
CHAP. A task must have
ATTACHed a sub-task in
order to issue a CHAP for
the sub-task.
The task identified by the
task id has already
terminated.

GCS Abend Codes

VM/SP System Messages and Codes

User Response
Check that the parameter
list is not being incorrectly
modified. Make sure that
the starting address, number
of entries, and
length-of-entry fields are
correct.

Correct the faulty CHAP
parameter. Make sure that
the task id address is a
fullword with the task id in
the two low-order bytes.
Make sure that the task id
matches the task id that was
returned when the ATTACH
macro was issued for this
sub-task.

GCS Abend Codes
Abend Reason Module
Name
Code
Code
12F
CSITIM

Cause of Abend
The time interval address
passed to the STIMER macro
is invalid for one of the
following reasons:

User Response
Correct the time interval
addresses.

•

The storage key for the
time interval address
differs from that of the
task that issued the
STIMER macro, and the
address is located in
fetch-protected storage.
The time interval passed
in the DINTVL or TOD
parameter was not in
unpacked decimal format.
CSIENQ The resource to be released
by a DEQ macro was not
previously obtained by an
ENQ from the same task, and
the RET = HAVE operand
was not coded in the call to
DEQ.
CSIENQ Two ENQ macros were issued
in the same task for the same
resource without a DEQ
macro call in between. The
second ENQ did not specify
TEST, USE, CHNG, or
HAVE in the RET operand.

•

130

138

13C

CSIABD

Figure 11 (Part 7 of 30).

An invalid parameter list was
specified on an ESTAE macro
by a problem state program.
The storage key for the
parameter list differed from
the storage key for the
problem state program.

Issue ENQ to obtain the
resource before issuing
DEQ, or include the
RET = HAVE operand as a
DEQ parameter.

Check to see if you intended
to use another resource
name for the second ENQ.
If not, you can (1) issue a
DEQ to release the resource
after the first ENQ; or (2)
specify TEST, USE, CHNG,
or HAVE in the RET
operand in the second ENQ
macro.
Check to see if the correct
parameter list was passed to
ESTAE.

GCS Abend Codes

System Codes

GCS Abend Codes
Abend Reason Module
Name
Code Code
13E
CSIATT

144

CSISER

Cause of Abend
A DETACH has been issued
for a sub-task that has not
yet terminated. The sub-task
has abnormally terminated
with this code. The
sub-task's ETXR (exit
routine) was not executed.

An error occurred during
execution of the SYNADAF
macro. An invalid access
method code was specified in
the high order byte of
register 15.

lCB

CSIITS

201

CSIWAI

202

CSIWAI

An unauthorized caller
issued an SVC 203. Either a
system-only SVC 203 was
requested, or a program
running in problem state
tried to issue the SVC 203.
An SVC 203 can only be
issued by a program running
in supervisor state.
The user is not authorized to
access the storage specified
by the ECB in aWAIT macro
parameter list.
The state block address in an
ECB that is being POSTed
does not refer to a state block
in the caller's task
block/state block structure.
The state block address
loaded into the WAIT ECB
may have been altered, or the
state block may have been
destroyed.
The POST routine will
reduce the state block's wait
count--allowing the waiting
program to move out of the
wait state--only if the state
block address that was loaded
into the WAIT ECB is still
valid.

Figure 11 (Part 8 of 30).

GCS Abend Codes

VM/SP System Messages and Codes

User Response
Be sure that the subtask
completes execution before a
DETACH is issued. To
synchronize the DETACH
with task completion, you
can use the ECB or ETXR
parameter on the ATTACH
macro. This ECB is posted
or the ETXR exit runs when
the sub-task terminates.
Make sure that the
ACSMETH parameter on
the SYNADAF macro is
correctly coded, or that the
high order byte of register
15 contains a valid access
method code, before SVC 68
SYNADAF is issued.
If a system-only SVC was
attempted, find out what
SVC should have been
issued and correct the
problem. Otherwise, find
out if the calling program
should have been running in
supervisor state or should
have issued another SVC.
Check the ECB address
entered in the WAIT macro.

Make sure that ECB
contents are not being
changed, and that the
waiting program state block
has not been destroyed.

(

GCS Abend Codes
Abend Reason Module
Code
Name
Code
CSIPMC,
206
CSIPMD,
CSIPML

20D

22A

22C

230

Cause of Abend
The parameter list address or
an address in the parameter
list (1) was undefined; or (2)
was in a different key than
that of the calling program
and was located in
fetch-protected storage.
CSIABD A subtask of the current
program has ended
abnormally with the STEP
parameter. STEP causes
GCS to abnormally end all
tasks and commands that are
related to the ABENDed
subtask.
CSIATT Invalid parameters were
passed to an ATTACH macro.
A share subpool value
greater than 127 was
specified on the SHSPV
parameter, or a share subpool
value greater than 127 was
included in a list whose
address was coded in the
SHSPL parameter.
CSIATT The storage key for the id
address passed to a CHAP
macro differs from that of the
task that issued the CHAP,
and the address is located in
fetch-protected storage.
CSIENQ A length of zero was specified
for the name representing a
resource in a call to the DEQ
macro.

Figure 11 (Part 9 of 30).

User Response
Make sure that no
parameter list is being
incorrectly modified.
Ensure that all addresses
are correct.

Correct the problem in the
subtask that failed.

Correct the SHSPV or
SHSPL parameter. Make
sure that the parameter
address is correct if an
SHSPL parameter is used.

Provide a valid task id
address.

First, check to see if the
RNAME LENGTH
parameter for the DEQ
macro is zero. If it is zero,
then the first byte of the
minor name field should
contain the length of the
minor name field and must
not be zero. Note that no
explicit length need be
coded; RNAME length
defaults to the assembled
length of RNAlVIE if the
value is not given
elsewhere.

GCS Abend Codes

System Codes

GCS Abend Codes
Abend Reason Module
Code Code
Name
Cause of Abend
233
CSIDUM A user program has called
the SDUMP macro with an
invalid parameter list
address.
CSIENQ A length of zero was specified
238
for the RNAME in an ENQ
macro parameter list.

23E

CSIATT

The address of the task id
supplied to the DETACH
macro is invalid for one of
the following reasons:

•

•
•
•

Figure 11 (Part 10 of 30).

The storage key for the
task id address differs
from that of the issuing
task and the address is in
fetch-protected storage.
The task id is zero.
The task id does not
exist.
The sub-task identified by
the task id is not a direct
descendant of the task
that issued the DETACH.
Tasks may DETACH only
tasks that they
ATTACHed.

GCS Abend Codes

VM/SP System Messages and Codes

User Response
Correct the user program to
pass a valid parameter list
address.
First, check to see if the
RNAME LENGTH
parameter is zero. If it is
zero, then the first byte of
the minor name field must
contain its length and must
not have a value of zero. A
non-zero length must be
coded in one of these fields.
Correct the parameter on
the DETACH macro. Make
sure that the task id address
is a fullword with the task
id in the two low- order
bytes. Also make sure that
this task id matches the task
id returned when the
ATT ACH macro was issued
for this sub-task.

GCS Abend Codes
Abend Reason Module
Code
Code
Name
244
CSISER

2CB

CSIITS

301

CSIWAI

305

CSIFSV

Figure 11 (Part 11 of 30).

Cause of Abend
The address of the caller's
savearea (in register 13) was
found to be invalid during
execution of the SYNADAF
macro.

An SVC 203 was issued, but
the halfword code issued with
the SVC did not match any
valid sve 203 function.
The wait flag is already on
for the ECB coded in a WAIT
macro parameter list.

An error occurred when (1)
an SVC 5 FREEMAIN tried
to release storage belonging
to an unsupported subpool; or
(2) an SVC 5 FREEMAIN
tried to release storage
belonging to a subpool
requiring authorization, and
the program that issued the
request is not authorized; or
(3) the storage being released
has a subpoolnumber
different from the number of
the subpool from which the
I
j
storage was obtained.

User Response
.!vIake sure that register 13
points to a register savearea
within user storage when
SYNADAF SVC 68 is issued.
If SYNADAF is issued from
a SYNAD routine, make
sure that register 13 has not
been altered since the
SYNAD routine was
entered, and that register 13
contained the address of a
valid register savearea when
the last data management
macro was issued.
Correct the halfword code so
that it specifies the desired
function.
Check to see if two WAIT
macros are unintentionally
being issued for the same
ECB. Zero out the ECB
before it is used by aWAIT
macro.
Check the FREEMAIN
causing the error and make
sure that the subpool
specified is correct.

GCS Abend Codes

System Codes

GCS Abend Codes
Abend Reason Module
Code
Code
Name
CSIFSV
30A

344

CSISER

378

CSIFSV

Figure 11 (Part 12 of 30).

Ca~se

of Abend
A program has issued an SVC
10 FREEMAIN, and one of
the following three errors has
resulted: (1) the task has
released storage belonging to
an unsupported subpool;
(2) the task has released
storage belonging to a
subpool for which
authorization is required, and
the program is not an
authorized program; or
(3) the storage being released
has a subpool number
different than the number of
the subpool from which the
storage was obtained.
An invalid DCB address or
DCB DEB (DCBDEBAD)
address was encountered
during execution of the
SYNADAF macro.

A program has issued an SVC
120 FREEMAIN and (1) has
tried to release storage
be longing to an unsupported
subpool;
(2) the task has tried to
release storage belonging to a
subpool for which
authorization is required, and
the task is not authorized; or
(3) the storage being released
has a subpool number that is
different from the number of
the subpool from which it
was obtained.
GCS Abend Codes

VMjSP System Messages and Codes

User Response
Make sure that the subpool
is coded correctly in the
FREEMAIN.

Correct the invalid address.
For QSAM, the DCB address
should be passed to
SYNADAF as the PARMI
operand on the SYNADAF
macro instruction. (For
BSAM and QSAM, the DCB
address is in register 1 on
entry to the user's SYNAD
routine.)
Make sure that the subpool
being passed to the
FREEMAIN is correct.

(

GCS Abend Codes
Abend Reason Module
Code
Code
Name
Cause of Abend
406
CSIPMC The module that was to be
LINKed, XCTLed,
ATTACHed or OSRUNed was
marked 'Only Loadable' by
the linkage editor. The
failure may have occurred
when the user program issued
a LINK or XCTL macro
directly. But the failure may
also have resulted when an
ATTACH macro or an
OSRUN command called the
LINK macro.
42A
CSIATT The ECB address specified in
the ECB parameter for an
ATTACH macro is invalid.
The address is in a different
storage protection key than
that of the program that
issued the ATTACH.
CSIENQ An invalid parameter list was
430
coded in a call to the DEQ
macro. The calling program
is not authorized to access
the storage area specified in
the parameter list.
CSIENQ An invalid parameter list was
438
entered in a call to the ENQ
macro. The calling task is
not authorized to access the
storage area specified in the
parameter list.
Figure 11 (Part 13 of 30).

U set Response
LOAD should be used to
bring a module marked
'Only Loadable' into storage
before other operations are
performed. If the module is
not only loadable, reI ink the
module to remove the
attribute.

Provide a valid address for
the ECB parameter.

Check the list address and
the addresses of major and
minor names in the DEQ
parameter list.

Check the list address input
parameter and the addresses
of major and minor names in
the ENQ parameter list.

GCS Abend Codes

System Codes

GCS Abend Codes
Abend Reason Module
Name
Code Code
CSIATT
43E

User Response
GCS system storage has
been modified since your
sub-task was attached.
Contact your system
programmer.

Cause of Abend
An invalid address was
passed to a DETACH macro.
The ECB address was valid,
but now is not in the same
storage key as the task that
issued the ATTACH.
An invalid DECB address
was encountered during
execution of the SYN ADAF
macro.

For BSAM, the DECB
address should be passed to
SYNADAF as the PARM2
operand on the macro
instruction. (The DECB
address is in register 0 on
entry to the user's SYNAD
routine.)

444

CSISER

530

CSIENQ A DEQ has been issued
before an ENQ for the same
resource could be filled. The
same task issued both the
ENQ and the DEQ, and
RET = HAVE was not coded
in the DEQ call.

604

CSIGSV

Figure 11 (Part 14 of 30).

The GETMAIN macro just
issued had (1) an invalid
address in the A or LA
operand; or
(2) an invalid parameter list
address. The address in the
A or LA operand was invalid
because it specified a
location outside the the
virtual storage assigned to
the task.
GCS Abend Codes

VMiSP System Messages and Codes

Try coding RET = HAVE as
a DEQ parameter. The DEQ
request will not be honored
and a return code will be
produced if the ENQ has not
been completed before the
DEQ is issued. But with
RET = HAVE, the task will
not abend.
Check the coding of the
GETMAIN macro
instruction, and re-execute
the program after correcting
the instruction.

GCS Abend Codes
Abend Reason Module
Code
Code
Name
CSIFSV
605

638

704

705

706

Cause of Abend
A program has issued an SVC
5 FREEMAIN (E-type or
V-type FREEMAIN), but the
FREEMAIN parameter lists
were protected by a storage
key that the issuing program
could not read from.
CSIENQ The storage requested by the
ENQ macro was not
available. GET MAIN could
not get the storage necessary
for control blocks.
CSIGSV, An uncorrectable machine,
CSIATT system or indeterminate error
occurred while processing a
GETMAIN macro call. An
improper mode byte may have
been sent to the GETMAIN
entry module, or there may
not be sufficient system
storage to process the
GETMAIN.
CSIFSV, There was not enough
CSIATT storage available to meet the
internal processing needs of
an SVC 5 FREEMAIN.
CSILOS The module requested in a
LINK, LOAD, XCTL, or
ATTACH macro, or OSRUN
or LOADCMD command
could not be used. Either the
module was marked as not
executable by the linkage
editor, or the module is an
overlay module, which is not
allowed in GCS.

User Response
Check to see that the
storage protection key for
the FREEMAIN parameter
lists is correct.

Re-execute the program.

Check to see if the mode
byte is correct if the user is
coding his own mode byte.
Otherwise, increase the size
of the virtual machine and
re-IPL it.

Increase the size of the
virtual machine and re-IPL
it.
Correct the problem in the
requested load module and
relinkedit it into a
LOADLIB.

This abend can result when a
user program issues a LINK,
LOAD, or XCTL macro
directly. But the failure may
also occur when an ATTACH
macro or an OSRUN or
LOADCMD command is
issued, since these call LINK
or LOAD.
Figure 11 (Part 15 of 30).

GCS Abend Codes

System Codes

GCS Abend Codes
Abend Reason Module
Code
Code
Name
70A
CSIFSV,
CSIGSV

72A

CSIATT

Cause of' Abend
An uncorrectable machine,
system or indeterminate error
occurred while processing an
R-type GET MAIN or
FREEMAIN (an sve 10
GETMAIN or FREEMAIN).
The abnormal end may have
occurred because an
improper mode byte was sent
to the GETMAIN entry
module, or because there was
not enough storage to process
the GETMAIN.
An address passed to the
ATTACH macro is invalid
because the storage key for
the address differs from that
of the calling program, and
because the address is in
fetch-protected storage. The
address is one of the
following:

User Response
Check to see that the mode
byte is correct if the user is
coding his own mode byte.
Otherwise, increase the
amount of storage and
re-IPL the virtual machine.

Provide a valid address for
the incorrect parameter.

(

•
•
•

778

the address of the
ATTACH parameter list
the EPLOC or DE
address
the SHSPL address (the
address is invalid or the
first byte in the list has a
value of zero).
CSIFSV, (1) An uncorrectable
CSIGSV, machine, system, or
CSIATT, indeterminate error occurred
CSITIM while processing an RU-type
GETMAIN or FREEMAIN
macro. The problem may
have occurred because an
improper mode byte was sent
to the GETMAIN entry
module, or because not
enough storage· was available
to complete the GETMAIN or
FREEMAIN; or (2) A
GETMAIN or FREEMAIN
issued by STn"fER or
ATT ACH has failed because
not enough storage was
available to complete the
GETMAIN or FREEMAIN.

Figure 11 (Part 16 of 30).

GCS Abend Codes

VMjSP System Messages and Codes

To correct the first problem,
make sure that the mode
byte is correct if the user
coded it himself. If the
mode byte is not in error,
increase the amount of
storage and re-IPL the
virtual machine. To correct
the second problem, increase
the amount of storage and
re-IPL the virtual machine.

GCS Abend Codes
Abend Reason Module
Code
Code
Name
CSIGSV
804

806

CSILOS

Cause of Abend
The length field passed to a
GETMAIN macro contained
either a negative or zero
length, or specified a length
that exceeded the available
virtual storage.

A LINK, LOAD, XCTL, or
ATTACH macro requested a
program that could not be
found, or an I/O error
occurred while processing the
request. Register 15 contains
a hexadecimal reason code:

Code Meaning
04
The program could not

Figure 11 (Part 17 of 30).

be found or no
LOADLIBs were
defined by the
GLOBAL command.
An uncorrectable I/O
error occurred when
the BLDL control
program routine
attempted ~o search
the directory.
CLOSE gave a
non-zero return code
after the module was
loaded.

User Response
Choose the appropriate
action from among the
following:
Check the coding of the
L V operand. Re-execute
the program after
making corrections.
2. Change the problem
program so that it
requests a smaller
amount of storage.
3. Increase the amount of
storage in the virtual
machine and re-IPL it.
If the reason code is 04, be
sure that you issued the
GLOBAL command with the
LOADLIB parameter and
the names of the LOADLIBs
which may contain the
requested module. If the
reason code is 08, correct
the cause of the I/O error.
Note that this is probably
not a user program error. If
the code is 10, rerun the job.
Note that this is probably
not a user program errOl'.
1.

GCS Abend Codes

System Codes

GCS Abend Codes
Abend!, Reason Module
Code
Code
Name
80A
CSIGSV

'
II
I
I

~
I
i
I,·

878

':\'1

I
I

•

Cause of Abend
The length field passed to an
R-type GET MAIN macro
contained either a zero
length or a value too large
for available storage.

User Response
Choose the appropriate
action from among the
following:

Check the coding of the
LV operand and
re-execute the program.
2. Change the problem
program so that it
requests less storage.
3. Increase the amount of
storage and re-IPL the
virtual machine.
-+-C-S-I-G-S-V-+--T-h-e-l-e-n-g-th-fi-e-ld-p-a-ss-e-d-t-o-an--+-C-h-o-o-s-e-t-h-e-a-p-p-r-o-p-ri-a-t-e----I
RU-type GETMAIN macro
action from among the
contained either a negative
following:
or zero value, or specified a
length too large for available
1. Check the coding of the
storage.
LV operand and
re-execute t e program.
2. Change the hproblem
program so that it
requests less storage.
3. Increase the amount of
storage and re-IPL the
I
virtual machine.
1.

:
I
r-:._---+.------r-------~--------------------------r_--------------~------~

19ut:"

CSIFSV

A task issued an SVC 5

FREEMAIN, but the address
of the storage being released
is not on a doubleword
boundary.

906

!
~

The Load and/or Use count
for the module requested by a
LINK, LOAD, XCTL, or
ATTACH macro is already
the maximum of 32767.

J<"'igurc 11 (Part 18 of 30). GCS Abend Codes

VMjSP System Messages and Codes

Correct the address
parameter for the
FREEMAIN.

Check for loops which cause
the same macro instruction
to be issued too often.

(

GCS Abend Codes
Abend Reason Module
Code
Code
Name
90A
CSIFSV

Cause of Abend
A task has issued an SVC 10
FREEMAIN, but the address
of the storage that is being
released is not on a
doublewol,d boundary.

User Response
Correct the address
parameters for the
FREEMAIN.

Make sure that register 13
points to the savearea
address that was provided
by SYNADAF. Also, make
sure that the user's savearea
address, (located 4 bytes into
the savearea pointed to by
the address in register 13),
has not been altered.
Correct the address
parameter being passed to
FREEMAIN.

944

CSISER

An invalid savearea address
was encountered during
execution of SYNADRLS.
The invalid address was
either the SYNADAF
savearea address in register
13, or the pointer to the
caller's sa vearea.

978

CSIFSV

A03

CSIATT

A05

CSIFSV

A task has issued an SVC 120
FREEMAIN, but the address
of the storage being released
is not on a doubleword
boundary.
This abnormal end occurred
during normal task
termination. The task that
was terminating had a
sub-task that had not been
DETACHed.
A task issued an SVC 5
FREEMAIN and (1) the
storage being released
overlaps storage that is
already free; or
(2) the storage being released
is on a page that has been
locked by PGLOCK.

Figure 11 (Part 19 of 30).

Make sure that all sub-tasks
are DETACHed before a
task terminates.

Check the parameters for
the FREEMAIN to make
sure that all addresses and
lengths have been coded
correctly. Also check to see
that any locked storage has
been unlocked before it is
released.

GCS Abend Codes

System Codes

GCS Abend Codes
Abend Reason Module
Code
Code
Name
Cause of Abend
A06
CSIPMC The current task is already
waiting for the serially
reusable module that has
been requested by LINK,
XCTL, or ATTACH.

AOA

A78

CSIFSV

Figure 11 (Part 20 of 30).

A task has issued an SVC 10
FREEMAIN, and (1) the
storage being released
overlaps storage that is
already free; or
(2) the storage being released
is on a page that has been
locked by PGLOCK.
A task has issued an SVC 120
FREEMAIN, and (1) the
task-related storage that is
being released over laps
storage that is already free;
or
(2) the storage that is being
r~leased is on a page that has
been locked by PGLOCJC
GCS Abend Codes

VM/SP System Messages and Codes

User Response
Do not allow an
asynchronous exit to
reference the same serially
reusable module as the task
it is running for, at the 'same
time as the task it is
running for. Also, do not
allow simultaneous
reference to 'the same
serially reusable module by
two asynchronous exits
running for the same task.
Finally, do not allow a
serially reusable module to
try to re-enter itself.
Make sure that the address
and length parameters
passed to FREEMAIN are
correct. Also check to see
that any storage that has
been locked is unlocked
before it is released.
Check to make sure that
ad4ress and length
parameters passed to
FREEMAIN are correct.
Also check to see that any
storage that has been locked
is unlocked before it is
released.

(

GCS Abend Codes
Abend Reason Module
Code Code
Name
B03
CSIATT

B04

CSIGSV

Cause of Abend
Normal termination of a task
has been interrupted because
the task that was terminating
still holds a common lock.
An invalid subpool number
was specified on an E- or
V-type GETMAIN macro.
The number may have been
invalid because:
A program running in
problem state tried to
access a subpool with a
number outside the 0-127
range; or
2. A program running in
supervisor state tried to
access an unsupported
subpool. (Supervisor
state programs can access
subpools with numbers in
the 0-127 range, PLUS
subpools 229, 230, 231,
241, 243, and 244.)
A subpool number greater
than 127 was passed to a
R-type GETMAIN macro. An
invalid subpool number was
specified on an E- or V-type
GETMAIN macro. The
number may have been
invalid because:

User Response
Make sure that all locks are
released before a task
terminates.
Check the coding of the SP
operand of the GETMAIN
macro.

BOA

CSIGSV

Figure 11 (Part 21 of 30).

Check the coding of the SP
operand of the GETMAIN
instruction.

A program running in
problem state tried to
access a subpool with a
number outside the 0-127
range; or
A program running in
supervisor state tried to
access an unsupported
subpool. (Supervisor
state programs can access
subpools with numbers in
the 0-127 range, PLUS
subpools 229, 230, 231,
241, 243, and 244.)

GCS Abend Codes

System Codes

GCS Abend Codes
Abend Reason Module
Code
Code
Name
B78
CSIGSV

Cause of Abend
A subpool number greater
than 127 was passed to a
RU-type GETMAIN macro.
An invalid subpool number
was specified on an E- or
V-type GETMAIN macro.
The number may have been
invalid because:
A program running in
problem state tried to
access a subpool with a
number outside the 0-127
range; or
2. A program running in
supervisor state tried to
access an unsupported
subpool. (Supervisor
state programs can access
subpools with numbers in
the 0-127 range, PLUS
subpools 229, 230, 231,
241, 243, and 244.)
Normal termination of the
current task has been
interrupted because the task
still holds resources through
ENQs.
A program tried to terminate
with resources still held by
ENQ.
A program has issued an SVC
5 FREEMAIN, and (1) the
task-related storage that is
being released is not owned
by the active task or by a
task that is sharing storage
with the active task; or
(2) the storage has had its
storage key changed since it
was obtained.

User Response
Check the coding of the SP
operand of the GETMAIN
instruction.

C03

CSIATT

D03

CSIFSV

D05

CSIFSV

Figure 11 (Part 22 of 30).

GCS Abend Codes

VM/SP System Messages and Codes

(

Make sure that all resources
have been released by DEQ
before a task terminates.

Make sure that all resources
are released by DEQ before
exiting the program.
Check to see that the
address and length
parameters of the
FREEMAIN are correct.
Also check to see that
storage keys that were
changed have been reset to
what they were when the
storage was obtained.
Lastly, make sure that the
task releasing the storage
owns the subpool specified
in the FREEMAIN macro,
or shares the subpool with
an ancestor.

GCS Abend Codes
Abend Reason Module
Code
Code
Name
DOA
CSIFSV

D23

Cause of Abend
A program has issued an SVC
10 FREEMAIN, and (1) the
task-related storage that is
being released is not owned
by the current task or by a
task sharing storage with the
current task; or
(2) the storage that is being
released has had its storage
protection key changed since
the storage was obtained.

CSIRPY

A validate was issued for the
reply buffer address specified
in the ORE (Operator Reply
Element) Data Area. The
return code from validate
indicates the address is
inaccessible to the user. The
task that issued the WTOR
will be abnormally
terminated.
CSIWTR One of two errors has
occurred: (1) An invalid
address was passed to a WTO
or WTOR macro. The
address or addresses passed
in the parameter list are
located in storage that the
user cannot access.
(2) A GETMAIN macro was
unable to get a WQE or ORE
buffer because not enough
storage was available.

Figure 11 (Part 23 of 30).

User Response
Check that the address and
length parameters passed to
the FREEMAIN are correct.
Make sure that a storage
key that has been changed
has been reset to its original
setting. Also make sure
that the task which is
releasing the storage owns
the subpool specified in the
FREEMAIN macro, or
shares the subpool with an
ancestor.
Specify a reply buffer
address within the range of
your virtual storage.

To correct the first problem,
make sure all parameter list
addresses are within your
range of storage. To correct
the second problem, either
increase the amount of
virtual storage available to
the program or reduce the
program7ssq.s storage needs.

GCS Abend Codes

System Codes

GCS Abend Codes
Abend Reason Module
Code
Code
Name
CSIFSV
D78

E04

CSIGSV

E05

CSIFSV

Cause of Abend
A task has issued an SVC 120
FREEMAIN, and (1) the
task-related storage that is
being released is not owned
by the active task or by a
task that shares storage with
the active task; or
(2) the storage key for the
storage that is being released
has been changed since the
storage was obtained.

A GETMAIN macro has been
called with an MVS
parameter that is not
supported in the GCS
environment. The
unsupported parameter is
either LC or LV mode.
A task has issued an SVC 5
FREE MAIN using an
unsupported MVS parameter.
The parameter is one of the
following:

User Response
Make sure that the address
and length parameters being
passed to FREEMAIN are
correct. Check to see that a
storage key that has been
changed is reset to its
original setting before the
storage is released. Also
make sure that the task that
is releasing the storage
owns the subpool specified
in the FREEMAIN macro,
or shares the subpool with
an ancestor.
Rewrite the problem
program so that it requests
allocation of only one
storage area at a time.

Change the macro call so
that it uses only supported
parameters.

•
•
•
•

EOA

CSIFSV

Figure 11 (Part 24 of 30).

EC
VC
LC
L
A task has issued an SVC 10
FREEMAIN, but (1) the SVC
10 was called without an LV
parameter; or (2) a zero
length was specified as the
LV parameter for the
FREEMAIN.
GCS Abend Codes

VM/SP System Messages and Codes

Change the macro call to
use an LV parameter with a
non-zero length.

GCS Abend Codes
Abend Reason Module
Code Code
Name
EOB
CSITIM

E23

Cause of Abend
A parameter that is not
supported by GCS was used
in a call to the TIME macro.
Unsupported parameters
include TU, MIC, STCK, and
ZONE=GMT.
CSIRPY A validate was issued for the
ECB address specified in the
ORE (Operator Reply
Element) Data Area. The
return code from validate
indicates the address is
inaccessible to the user. The
task that issue4 the WTOR
will be abnormally
terminated.
CSIWTR An invalid ECB or reply area
address has been passed to
the WTOR macro. The error
or reply area address is
located in storage that the
user program cannot access.
CSITIM The CANCEL parameter for
the TTIMER macro was not
specified, or a parameter'that
is not, supported by GCS was
passed to TTIMER.
Unsupported parameters
include TU and MIC.
CSITIM A parameter that is not
supported by GCS was passed
to the STIMER macro.
Unsupported parameters
include TASK, GMT,
TUINTVL, and MICVL.

User Response
Change the macro call so
that it uses only supported
parameters.

Specify a reply buffer
address within the range of
your virtual storage.

E23

E2E

E2F

Figure 11 (Part 25 of 30).

Make sure that the ECB or
replyarea address passed to
WTOR is within your
storage range.

Change the macro call so
that it uses only supported
parameters.

GCS Abend Codes

System Codes

GCS Abend Codes
Abend Reason Module
Code Code
Name
Cause of Abend
E30
CSIENQ A parameter that is not
supported in the GCS
environment was coded in a
call to the DEQ macro. The
parameter is one of the
following:

User Response
Change the macro call so
that it uses only supported
parameters.

•
•
•
•
•
•
•

E38

CSIENQ

GENERIC = YES
RMC=STEP
SYSTEM
SYSTEMS
TCB
DCB
Multiple requests in one
macro call.
A parameter that is not
supported in the GCS
environment was coded in a
call to the ENQ macro. The
parameter is one of the
following:

Change the macro call so
that it uses only supported
parameters.

•
•
•
•

E78

CSIFSV

Figure 11 (Part 26 of 30).

SMC=STEP
SYSTEM, SYSTEMS
TCB
Multiple requests with
one macro call.
A task has issued an SVC 120
FREEMAIN and (1) the SVC
120 was called without an LV
parameter; or
(2) A zero length was
specified in the LV parameter
and a zero address was
specified in the A parameter.
GCS Abend Codes

VM/SP System Messages and Codes

Change the FREEMAIN call
so that it uses an LV
parameter with a non-zero
length, and! or change the A
parameter to specify a
non-zero address.

GCS Abend Codes
Abend Reason Module
Code
Code
Name
Cause of Abend
CSICMD The GCS CMDSI service has
FCA
0300
been called with an invalid
parameter list. The return
code from a VALIDATE
issued on addresses in the list
indicates that (1) the
parameter list address or
addresses wi thin the
parameter list are not
accessible to the user; or
(2) the command length was
invalid.
C3IDUM A user program has invoked
FCA
0400
the GDUMP command with
an invalid parameter list
address.
FCA
CSIGIM The GENIO macro has been
0500
issued with an invalid
parameter list. Either the
parameter list address itself
is invalid, or an address
within the parameter list is
invlaid.
FCA
0501
CSIGIM GENIO ST ARTR is an
authorized function, and the
calling program was not in
supervisor state.
FCA
OCOO
CSIACC User is not authorized to
CSIARE access the storage specified
CSIGLB in the plist.
CSIOSR
FCA
OE01
CSIREX An invalid parameter list has
been passed to the REXX
processor. Either the
parameter list address itself
is invalid, or an address
within the parameter list is
invalid.
Figure 11 (Part 27 of 30).

User Response
Make sure that parameter
list addresses are within the
range of your storage, and
that a valid command length
is specified.

Correct the user program to
pass a valid parameter list
address.
Ensure that the parameter
list and any addresses
con tained in the parameter
list reside in storage
accessible to the issuing
program.
Make sure that the calling
program is in supervisor
state before GENIO
ST ARTR is issued.
Check the address in the
plist to make sure that fetch
access is possible.
Ensure that the parameter
list and any addresses
contained in the parameter
list reside in storage
accessible to the issuing
program.

GCS Abend Codes

System Codes

GCS Abend Codes
Abend Reason Module
Code Code
Name
FCA
OFOO
CSIFLD

FCA

1001

CSINXT

FCA

1101

CSIIUE,
CSIIUX

FCA

1200

CSIQRY

FCA

1300

CSIRPY

Cause of Abend
A user program issued a
FILEDEF command with an
invalid parameter list
address.
A FREEMAIN macro has
returned a non-zero return
code, indicating a failure to
release storage.
A GETMAIN issued by the
current task has failed.

The GCS QUERY command
has been called with an
invalid parameter list. The
return code from a
VALIDATE issued on
addresses in the list indicates
that the parameter list
address or addresses within
the parameter list are not
accessible to the user.
The GCS REPL Y command
has been called with an
invalid parameter list. The
return code from a
VALIDATE issued on
addresses in the list indicates
that the parameter list
address or addresses wi thin
the parameter list are not
accessible to the user.

Figure 11 (Part 28 of 30). GCS Abend Codes

VM/SP System Messages and Codes

User Response
Correct the program so that
it passes a valid parameter
list address.
Re-IPL the system. If the
problem persists, contact
your IBM support personnel.
First, try re-executing the
program in which the
failure occurred. If the
problem persists, increase
the size of the virtual
machine and re-IPL it.
Make sure that parameter
list addresses are within the
range of your storage.

Make sure that parameter
list addresses are within the
range of your storage.

GCS Abend Codes
Abend Reason Module
Code Code
Name
CSILDC
FCA
1400

FCA

1500

CSIYTE

FCA

1600

CSIYTG

FCA

1700

CSIDLB

FCA

1800

CSIDLB

Figure 11 (Part 29 of 30).

Cause of Abend
The GCS LOADCMD
command has been called
with an invalid parameter
list. The return code from a
VALIDATE issued on
addresses in the list indicates
that the parameter list
address or addresses wi thin
the parameter list are not
accessible to the user.
A user program has invoked
the ETRACE command with
an invalid parameter list
address.
A' user program has invoked
the ITRACE command with
an jp.valid parameter list
address.
An invalid address was
detected during SET
command processing.

An invalid address was
detected during DLBL
command processing.

User Response
Make sure that parameter
list addresses are within the
range of your storage.

Correct the user program so
that it passes a valid
parameter list address.
Correct the user program so
that it passes a valid
parameter list address.
A GCS error message will
usually have preceded this
abend message. Please see
the 'User Respo~se' section
for the error message that
appeared and respond as
indicated.
A GCS error message will
usually have preceded this
abend message. Please see
the 'User Response' section
for the er~or message that
appeared and respond as
indicated.

GCS Abend Codes

System Codes

GCS Abend Codes
Abend Reason Module
Code
Code
Name
FCB
0100
CSILAC

FCB

0601

CSILLK

FCB

OA01

CSISDX

FCB

OD01

CSIREX

Fxx

CSIITS

Figure 11 (Part 30 of 30).

Cause of Abend
An AUTHCALL macro was
issued, but the issuing
program did not have access
to the address of the name of
the authorized program.
A program tried to acquire
the common lock on GCS
common storage without first
getting the local lock on
resources in the program's
own virtual machine.
Not enough free storage was
available for GETMAIN to
secure an AEB for the
SCHEDEX macro.

Invalid shared variable
request block addresses were
passed to the EXECCOMM
routine.
The SVC number that was
issued is not supported. The
numbers replacing the 'xx' in
the abend code represent the
unsupported SVC number.
GCS Abend Codes

100 VM/SP System Messages and Codes

User Response
Correct the problem in the
application program.

Make sure the program
acquires the local lock
before requesting the GCS
common lock.

Check to make sure the
abend is not being caused by
an error in the application
program. Correct the
application program if it is
at fault. Otherwise,
increase the size of storage.
Make sure that the
addresses have been coded
correctly.
Correct the SVC number
and reissue the command.

TSAF Abend Codes

TSAF Abend Codes
When a Transparent Services Access Facility (TSAF) abend occurs, the
TSAF operator must follow several steps:
1.

Collect information about the error.
Save the console sheet or spooled console output of the TSAF virtual
machine. Save and process, via the IPCS MAP command and the
IPCSDUMP command, any dumps produced by TSAF. Save any
CPTRAP file that contains TSAF data.

Collect information about the system status.
The following information can be useful and even necessary in problem
determination:
•
•
•
•

the status of real and virtual devices in use by TSAF
the level of system load at the time of failure on any of the systems
using TSAF and the status of each system (e.g. did one abend?)
the types of applications that are using TSAF at the time and any
information about them that can be freely provided
the physical connection configuration of the systems in use.

Recover from the abend so processing can continue.
When an abend occurs in TSAF, either because TSAF issued an
ABEND or because a TSAF or CMS operation caused a program
exception, TSAF produces a dump via the CP VMDUMP command. The
dump is placed in TSAF's virtual reader. TSAF then issues a CP
SYSTEM RESET command. If the CONCEAL option is on, as
recommended, CP automatically IPLs CMS. Otherwise, operator
intervention is required to re-IPL CMS. Similarly, if TSAF is not
invoked from the PROFILE EXEC, the operator must restart it
manually.

Figure 12 on page 102 lists the TSAF abend codes and the modules that
issue them, the cause of the abnormal termination, and the action the user
should take to recover and continue.

System Codes

101

TSAF Abend Codes
Abend
Code
ATSOIO

ATS300

ATS302

Module
Name
ATSCTL

ATSIIN

ATSIHI

Cause of Abend
Error return from
ABNEXIT.
This is a system error. The
TSAF abend· exit was not
established, so no dump was
taken, nor will the normal
problem determination
information be displayed on
the console.
Error on the HNDIUCV
SET CMS function.
This is a system error.
TSAF was unable to
successfully issue all
HNDIUCV SET CMS
function during
initialization.
*CRM is already in use by
another virtual machine.
There is already another
virtual machine that has a
connection to the *CRM
system service. CP allows
only one virtual machine at
a time to be connected to
this system service.

ATS303

ATS304

ATSIIN

Not authorized to connect to
*CRM.
This virtual machine is not
authorized in the system
directory to connect to the
*CRM system service.
TSAF does not take a dump
on this abend.
Error on the CMSIUCV
CONNECT to *CRM.
This is a system error.
TSAF was unable to
successfully issue the
CMSIUCV SET necessary to
establish an IUCV path to
the *CRM system service.

Figure 12 (Part 1 of 2).

102

TSAF Abend Codes

VM/SP System Messages and Codes

Action
Save any problem information
that CMS or TSAF presents.
Issue a VMDUMP command to
dump the contents of the
virtual machine. Contact your
service representative.

Save any problem information
that CMS·or TSAF presents.
Con tact your service
representative.

(
Determine what other virtual
machine(s) are authorized to
connect to this system service.
Make the necessary corrections
to the system directory and
perform the local procedures
for starting these virtual
machines. Then restart TSAF
on the appropriate virtual
machine. If this does not
correct the problem, save any
problem information that CMS
or TSAF presents, and contact
your service representative.
Make any needed corrections to
the system directory, and
restart TSAF on the
appropriate virtual machine. If
this does not correct the
problem, save any problem
information that CMS or TSAF
presents, and contact your
service representative.
Save any problem information
that CMS or TSAF presents.
Contact your service
representative.

TSAF Abend Codes
Abend
Code
ATS888

ATS890

ATS999

Module
Name
ATSxxx

Cause of Abend
Unable to obtain required
storage.

ATSxxx

A specific TSAF module
requested free st.orage from
eMS. eMS diagnosed an
error on that request. The
problem may have occurred
because the TSAF virtual
machine was given
insufficient virtual storage.
Unable to release storage.

ATSxxx

A specific TSAF module
tried to return storage to
eMS. eMS diagnosed an
error on that request. TSAF
will have taken a dump and
reset the virtual machine in
order to cause a re-IPL of
eMS.
TSAF system error.
A TSAF module
encountered a condition
that should not have
occurred. TSAF will have
taken a dump and reset the
virtual machine to cause a
re-IPL of eMS.

Figure 12 (Part 2 of 2).

Action
Provide more storage for the
TSAF virtual machine, and
restart TSAF. If it fails again,
contact your system
programmer.

Save the problem information
and contact your system
programmer or service
represen ta ti ve.

Save the problem information
and contact your system
programmer or service
representative.

TSAF Abend Codes

Note: xxx represents any TSAF module that issues this message.

System Codes

103

TSAF Abend Codes

104

VM/SP System Messages and Codes

DMK

Control Program (CP) Messages
OOlE

Unknown CP command: command
Explanation: User has issued an
invalid CP command after logging on to
VM/SP.

User Response: Reissue the command
with a valid option.

004E

User Response: Reissue the command
in full, or in the proper abbreviated
form.

002E

Explanation: The hexadecimal
location is incorrect because of
nonhexadecimal data in the operand or
the operand is longer than six
characters. If the operand was not a
hexadecimal location, it was misspelled.

Invalid operand {operand Imessage}
Explanation: One of the operands was
incorrectly specified, missing, or found
in the wrong place on the command
line. This message is also displayed if a
MONITOR STOP command is issued
while data collection is inactive, or if a
MONITOR START command is issued
and data collection is already in
progress.

User Response: Reissue the command;
specify the operand correctly.

003E

Invalid option - option
Explanation: One of the options was
incorrectly specified or is invalid with
the particular variation of the
command. The option may be shorter
than the minimum abbreviation
required.
If your system has RACF installed, you

may not be authorized to send data to
the nodename on the TAG command.

Invalid hexdata - data

005E

Explanation: The data supplied either
contains nonhexadecimal characters or
is longer than eight characters.
User Response: Reissue the command;
specify the hexadecimal data.

System Action: The entire command
line is ignored.
User Response: Reissue the command
with a valid operand.

Invalid hexloc - operand

Invalid device type - devtype

006E

Explanation: The device type specified
is not recognized as a valid CP device,
or it is incorrect for the function
requested. Examples of conditions that
cause this message to be displayed are:
•

If a teletypewriter terminal user

issues a TERMINAL APL ON
command.

•

If the NOTREADY command is

issued for a device other than a
spooled unit record or console
device.

Control Program (CP) Messages

105

DMK
•

•

If the device specified with a
READY command is a virtual
channel-to-channel adapter that has
not yet been attached via the
COUPLE command to another
device. The virtual CTCA can be
made ready only by issuing the
COUPLE command.

The user has issued a SET
VMSA VE command for a DASD
type with the volid specified in the
NAMESYS macro. Module
DMKSNT is not supported for this
function.

•

The operator attempted to set
TERMINAL CONMODE 3270,
BREAKIN, SCRNSAVE, or
BRKKEY on a console that is not a
local non-SNA display unit with a
3270 compatible command set.

•

The operator attempted to set
TERMINAL CONMODE,
BREAKIN, SCRNSAVE, or
BRKKEY without a virtual console
defined.

008E

Invalid spoolid - spoolid
Explanation: The spooUd specified was
not a valid decimal number, or it was
larger than four digits.
User Response: Reissue t.he command
with a valid spoolid number.

009E

Invalid range - range
Explanation: The range of addresses or
registers specified is incorrect. For
instance, the end address may be
smaller than the starting address, too
many ranges were specified, or the
number of pages to be locked may be
equal to or greater than the number of
pages available in the dynamic paging
portion of real storage.
User Response: Reissue the command;
specify the range.

Invalid register - register

OIOE

Explanation: The register specified is
not in the range 0 through 15 or
hexadecimal 0 through F, or the register
specified is not 0, 2, 4, or 6 for a
floating-point register.

User Response: Reissue the command
with a valid device type. For some of
the requests, there can be no user
action because a real device does not
allow the option specified.

User Response: Reissue the command;
specify a valid register.
007E

Invalid userid - userid
Explanation: The userid contains more
than eight characters.
If your system has RACF installed, you
may have tried to SPOOL or
TRANSFER data to a user you are not
authorized to send data to.

106

Invalid device type - userid vdev

OllE

Explanation: The device type is
invalid. If this is a DIAL command, the
device specified is not a virtual low
speed line. If this is a COUPLE
command:

User Response: Reissue the command
with a valid userid.

•

The device specified is not a virtual
channel-to-channel adapter, or,

If you are trying to use the SPOOL or
TRANSFER command, contact your
system administrator and request
authorization to send data to the userid.

•

You tried to couple a 3088
channel-to-channel device to a
channel-to-channel adapter.

VM/SP System Messages and Codes

(

DMK
User Response: Ensure that the device
is the correct type for the function, and
reissue the command.

012E

Invalid PSW - psw

•

Conflicting options (optionl and
option2) are specified on the same
PER command line.

•

The DEST option was specified more
often than allowed by the command.

Explanation: The PSW (program
status word) specified by the STORE
command is invalid. An invalid PSW is
one where:

System Action: If the DEST option
was specified more often than allowed
by the command, then the command is
not processed.

•

The virtual machine is operating in
extended control mode and some of
the bits that are defined by the
architecture to be zero have been
turned on, or

User Response: Consult the VMjSP
CP Command Reference for the correct
specification of the command and the
allowed options, and reissue the
command.

•

The virtual machine is operating in
basic control mode, and the
extended control mode bit has been
specified.

013W

User Response: Change the PSW to a
valid format for the mode of the virtual
machine. If this is not done, attempting
to run the virtual machine with an
invalid PSW causes an invalid PSW
message to be issued from the CP
dispatcher.

013E

Explanation: An overriding option
conflicts with an existing option in the
PER traceset.
System Action: The overriding option
is applied to the trace element. The
conflicting option in the trace element
is reset so that a conflict does not exist.

Conflicting option - {optionloptionl
and option2}
Explanation: This message occurs
when:
•

The same option is specified twice in
the same command, or

•

The function required by the given
option is incompatible with a
previously specified operand.

User Response: Issue QUERY PER
ALL to see how the tracesets have been
changed.

014E

•

Only DSS is specified in a
VMDUMP command line or the
DIAGNOSE code X'94' parameter
list but no discontiguous saved
segments exist.
The function requested is
incompatible with the system.

Conflicting option - {NORUN
conflicts with PRINTER IPRINTER
conflicts with NORUNISTEP
conflicts with PRINTERIPRINTER
conflicts with STEP};
{BOTHIRUN} option forced

Tape rdeu dump tape capacity
exceeded
Explanation: On the SPTAPE
command with the DUMP option, the
tape defined by rdev has reached
end-of-reel before all spool files were
dumped.
System Action: The tape is file
marked at the last complete spool file,
the tape is unloaded, and the command
is terminated.

Control Program (CP) Messages

107

DMK
User Response: Use a larger tape reel
or dump by spool class or type.

015E

020E

Userid missing or invalid
Explanation: The userid is either
missing or invalid. It may be longer
than eight characters. This message is
issued if an attempt is made to attach a
logica:l device to the system. This
message is also issued if a user who does
not have privilege class D issues the
command QUERY FILES CLASS x
userid, because the userid operand is
valid only for class D users.

Command not valid before
LOGON: command
Explanation: User has issued an
invalid CP command before logging on
to VM/SP.
System Action: Displays a menu of
related CP commands to assist the user.

User Response: Reissue the command
wi th a valid userid.

User Response: Enter one of the
commands from the displayed menu.
021E
016E

Real device address missing or
invalid [rdev]

TAG invalid for specified file type
Explanation: The spool file cannot be
tagged. The splink (the data buffer)
does not leave space for tag information
(accounting, dump, and monitor files).

Explanation: The real device address
is either missing or invalid. Valid
device addresses:
•

Are no more than three hexadecimal
characters long, or

•

Begin with the character L followed
by three hexadecimal characters.

User Response: This is an invalid
command. No action possible.

017E

Insufficient screen space - clear
screen and re-dial
Explanation: A DIAL command was
issued from a local 3270 terminal with
an insufficient number of lines left on
the screen to display the command and
resulting message. If allowed to
proceed, the terminal would go into a
holding state. This would tie up the
terminal, because the processing of
DIAL disables the terminal from
unsolicited interrupts, thereby
preventing the release of the holding
state.
User Response: Clear the screen and
then reissue the command.

108

VM/SP System Messages and Codes

User Response: Reissue the command
with a valid real or logical device
address.

022E

Virtual device address missing or
invalid
Explanation: The virtual device
address is either missing or invalid. An
invalid virtual device address either:
•

Is longer than three characters, or

•

Contains nonhexadecimal data, or

•

Is greater than X'5FF' for a virtual
machine running in basic contr"l
mode, or

•

Is associated with an unsupported
device type (specified in the
command IPL vdev), or

(

DMK
•

Is associated with a virtual machine
that is in the process of logging off
(specified in the command 'LOCATE
userid vaddr'), or

name is missing or is not of the right
format. The DESTination name is a one
to eight character name your
installation assigns.

•

Was previously used to define a
device for your virtual machine.

System Action: The command is not
processed.
User Response: If DEST missing or
invalid, Consult the VM/ SP CP
Command Reference for the correct
specification of the command and the
allowed options. Reissue the command.

User Response: Reissue the command
with a valid virtual device address.
Note: If this message is issued in
response to the 'LOCATE userid vaddr'
command, it means that the virtual
machine designated as 'userid' is in the
process of logging off and that the
system can't determine if a virtual
device at 'vaddr' even exists.

Otherwise, reissue the command; specify
the number of cylinders, blocks, or form
number correctly.

025E
023E

024E

Storage missing or invalid

Volid missing or invalid
Explanation: The volume
identification is either missing or
invalid. A volid longer than six
characters is considered invalid.

Explanation: The amount of storage is
either missing or invalid. An invalid
storage specification contains invalid
digits or does not end with the letter K
orM.

User Response: Reissue the command
with a valid volume identification.

User Response: Reissue the command;
specify the storage requirement.

{CYLSIBLKSIFORM
NUMBERIDEST} missing or
invalid
Explanation: The number of cylinders
(or blocks if FB-512) must be specified
with the command, but it is missing or
invalid. An invalid cylinder
specification is one that is four or more
characters, or larger than the maximum
number of cylinders available on the
device type specified. An invalid block
number specification is one that is
seven or more characters, or larger than
the maximum number of blocks on the
device type specified. If 'FORM
NUMBER' appears in the message text,
the form number following the FORM
keyword is missing or it is over 8
characters long. The DESTination

026E

Operand missing or invalid
Explanation: A required operand is
either missing or invalid.
User Response: Reissue the command
with a valid operand.

027E

Spoolid missing or invalid
Explanation: The command requires
that a spoolid be supplied, but it is
either missing or invalid. An invalid
spoolid is one that contains nondecimal
characters.
User Response: Reissue the command
with a valid spoolid.

Control Program (CP) Messages

109

DMK
028E

Class missing or invalid
Explanation: The class value is either
missing or invalid. An invalid class is
one that is not in the range A through Z
or 0 through 9.

If the modifier is "extended FCB not

User Response: Reissue the command
using a valid buffer name, or a buffer
that is compatible with the device.

032E

User Response: Reissue the command;
specify the required filename and/or
filetype.

Distribution code missing or
invalid
Explanation: The distribution code is
either missing or invalid. An invalid
distribution code is longer than eight
characters.

Copies missing or invalid

030E

Explanation: The operand that
specifies the number of copies is either
missing or invalid. An invalid copy
specification is nondecimal, greater
than 255, or zero.

User Response: Reissue the command
with a valid distribution code.

033E

03lE

Hexloc missing or invalid
Explanation: The hexadecimal
location is either missing or invalid. An
invalid hexadecimal location is one that
contains nonhexadecimal characters or
is longer than six characters.

User Response: Reissue the command;
specify the required number of copies.

Buffer missing or invalid [modifier]
User Response: Reissue the command
with a valid hexadecimal location.

Explanation: The FCB or UCSB could
not be loaded. The modifier indicates
the reason for failure:
034E
•

110

•

System Action: The buffer has not
been transferred to the device.

Filename and/or filetype missing
or invalid
Explanation: The filename and/or
filetype is missing or invalid. An
invalid filename is larger than 24
characters. An invalid filetype is larger
than eight characters if the filename is
eight characters or less.

If the modifier is "FCB too long" it
means that the FCB is too long for
the printer.

supported," it means that an attempt
is being made to send an extended
FCB image to a printer that does
not support the extended FeB
format.

User Response: Reissue the command
with a valid class.

029E

•

If there is no modifier it means that
the buffer name is missing or
invalid. Valid buffer names are
established by the system
pfogrammer. Any buffer name
longer than eight characters is
invalid.

Vl\1/SP System :Messages and Codes

Channel missing or invalid
Explanation: The channel number is
either missing or invalid. An invalid
channel number either is longer than
one character or is nonhexadecimal.
User Response: Reissue the command
with a valid channel number.

DMK
035E

Device type missing or invalid

038E

Explanation: The command requires
that a valid CP spool device type be
entered as an operand, but it is either
missing or invalid. Valid device types
are READER (R, RDR), PRINTER (P,
PRT), and PUNCH (PU, PCH).

Explanation: FORMAT was specified
in a VMDUMP command without an
operand, the operand was longer than 8
characters, or the parameter for the
named option of a CP request was
missing or longer than allowed.

User Response: Reissue the command
with a valid spool device type.

036E

User Response: Reissue the correct
command.

Index missing or invalid
039E
Explanation: If INDEX MISSING is
the condition, the requested FCB (forms
control buffer) image in DMKFCB does
not have an index value, therefore one
must be supplied in the command. If
INDEX INVALID is the condition, nn
was not a number from 1 to 31, where
nn corresponds to the number of the
first print position.

)

System Action: The
ATTACH/DETACH CHANNEL
command is rej ected.

Tape rdev invalid for SPTAPE
comlnand

Operator Response: Reissue the
ATTACH/DETACH CHANNEL
command with a valid processor
address.

Explanation: On the SPT APE
command with the LOAD/SCAN
options, the tape specified by rdev was
not generated by SPT APE commands
and has and invalid tape format.
040E
System Action: The tape is unloaded
and the command is terminated.
User Response: Have the operator
verify that the tape was created by the
SPT APE command.

Processor address missing or
invalid
Explanation: An ATTACH CHANNEL
or DETACH CHANNEL command was
issued and the processor address was (a)
missing from the command (MP mode
only), or (b) an invalid address. While
the processor address is not required on
the ATTACH/DETACH CHANNEL
command in UP or AP modes, if
specified it will be checked for validity.
In AP mode, the processor address must
be that of the I/O processor.

User Response: Supply the value for
INDEX in the FCB image or ensure that
nn is a number from 1 to 31, whichever
is appropriate. Reissue the command.

037E

Parameter for option option
missing or invalid

Device {rdevlvdev} does not exist
Explanation: The device address
specified does not exist, or a TIO to that
device resulted in condition code 3. If
the device address is a real device, it is
not configured in the CP system, or the
device is configured in CP but is not
operational; if it is a virtual device
address the virtual device is not
configured in the virtual machine.
If the specified device address is valid,
this message may indicate a problem

Control Program (CP) Messages

111

DMK
with the Network Control Program
and/or the 370x.

043E

Explanation: The buffer name supplied
with the command is not known to the
CP system. The buffer does not exist if
it cannot be found in one of the
following CP modules:

If issued from DMKCPT after a VARY
ONLINE command was issued, and the
device is configured in CP as one of a
string of DASD (but not head of string),
then the device is either not operational
or not ready. The hardware will return
the same indication (CC1 with
intervention required in the sense) for
either condition. The user should
determine which condition applies. If
not operational, the device cannot be
varied online. If not ready, the user
must ready the device before it can be
varied online.

User Response: Reissue the command;
specify the required real or virtual
device address.

Buffer name does not exist

•
•

DMKFCB = 3211 Forms Control
Buffers
DMKUCB = 3211 UCS Buffers
DMKUCS = 1403 UCS Buffers
DMKPIA = 3289 Font Offset
Buffers

User Response: Reissue the command;
specify a valid buffer name.

044E

System sysname does not exist
Explanation: The system name
specified does not exist.

042E

{Spoolid nnnn does not
existlSPOOLID nnnn DOES NOT
EXIST OR IS HELD}

User Response: Reissue the command;
specify a valid system name.
r

Explanation: The spoolid number
specified does not exist within the
specified device type. If the spoolid
specified is an open reader file (in use
by the virtual machine), it cannot be
changed or purged. A CLOSE command
will purge an open reader file unless
SPOOL RDR HOLD is in effect.

~
045E

Explanation: The userid specified is
not logged on. The command cannot
execute properly unless the user
specified is logged on.
User Response: Reissue the command;
specify only users who are currently
logged on.

DMKTRR issues this message to
indicate that the file could not be
located. The reasons that DMKTRR
might not find the. file include:

•
•
•

046E
The file is not there.
The file is not a reader file.
The file is held.

User Response: Reissue the command;
specify only known and valid spoolids.

use rid not logged on

{Device ridldevtype rdev} offline
Explanation: The specified device or
resource is offline and is considered not
available to the CP system.
System Action: The command is
rejected.
User Response: If ~his message was
issued for DE V rid. issue the
NETWORK VARY command to vary the
resource online, and then reissue the
command. If the message was issued for

112

VM/SP System Messages and Codes

DMK
devtype rdev, issue the VARY command
to vary the device online, and then
reissue the command. If the command
was the VARY command, the device had
been forced offline and cannot be varied
online again. If the message was issued
for volid, the checkpoint program was
unable to access a CP owned volume
needed during system shutdown because
that volume was offline.
{userid {vdevlsegname} I The current
tracesetlThe traceset tracesetlA
saved traceset} does not exist

047E

048E

Explanation: The channel specified in
the ATTACH CHANNEL command is
not configured in the CP system on the
specified processor.
User Response: Reissue the command;
specify only valid and defined real
channel addresses.

049E

The device specified for the
particular userid does not exist in
that user's virtual machine
configuration. If the message is
issued for the DIAL or COUPLE
command, the particular device
specified with those commands is
not defined in the receiving user's
virtual machine configuration.

For DMKSEG, the segname does not
exist.

For the PER command, an action
was requested to be performed on a
traceset and the traceset does not
exist.

{Device rididevtype rdev} in use
Explanation: An attempt was made to
vary an active teleprocessing line or
graphic device offline; or to vary online
additional paths to a device for which a
real RESERVE may be outstanding.

Explanation:
L

Channel x [processor xx] does not
exist

System Action: The command is
rejected.
User Response: In a case of an attempt
to vary offline an active line, first
deactivate the line by using the
DISABLE command; then reissue the
VARY command.

050E

LOGO N unsuccessful--incorrect
password
Explanation: The password supplied is
incorrect.

User Response:
1.

System Action: Displays a menu of
related CP commands to assist the user.

Reissue the command; specify only
existing virtual device addresses for
the receiving virtual machine.

For DMKSEG, reissue the command
using a valid segname.

For PER, establish a traceset before
requesting an operation to be
performed on it.

User Respon.se: Enter one of the
commands from the displayed menu.

051E

Maximum virtual devices
exceeded in directory
Explanation: The logon cannot be
completed because the directory has
more virtual devices defined in it than
CP allows.
User Response: Notify the system
operator that you cannot complete your

Control Program (CP) Messages

113

DMK
given location. CP doesn't know the
actual location of the SNA terminal so
it uses the LUNAME of the terminal.

logon because of this error in your
directory.

052E

User Response: Log on specifying a
different userid, or send a message to
the operator or the logged-on user
requesting information on the logon
status.

Error in CP directory
Explanation: The link or logon cannot.
be accomplished because of a permanent
I/O error encountered while reading the
directory.
User Response: Send a message to the
system operator stating that you cannot
complete your link or logon because of
an error in the directory.

053E

055E

Explanation: One of the following
occl,lrred:
(1) The DIAL command has been issued
to a userid from a 270X terminal and
either that userid has no 270X lines, the
lines are not enabled, or the lines are
all busy.

use rid not in CP directory

Explanation: The userid supplied was
not found in the directory or the userid
has a password of NOLOG.

(2) The DIAL command has been issued
to a userid from a 3270 terminal and
either that userid has no 3270 lines or
the lines are all busy.

User Response: Reissue the command;
specify a valid userid.

054E

114

User Response: If you issued the DIAL
command from a 270X terminal, reissue
the command specifying a userid that
has enabled virtual 270X lines that are
not already servicing a user.

Already logged on
{{lineIGRAFILUNAMEILDEVldevice}
rdev Iline disconnected}
Explanation: The userid supplied in
the LOGON command is already logged
on at the given line address. line
indicates a line mode device and GRAF
indicates a display terminal. LDEV
indicates a logical device, device is the
device name and rdev is a real device.
Line disconnected happens when a user
is trying to log on to a userid that is in
the process of logging off. The terminal
is no longer associated with the user,
but a 'wait' is set on that momentarily
prevents the user from logging off. This
situation only exists for a short time.
but it is possible to receive the message.
For SNA termillals LUNAME indicates
that the userid supplied in the LOGON
command is already logged on at a

VM/SP System Messages and Codes

Line(s) not available on userid

If you issued the DIAL command from a
3270 terminal; reissue the command
specifying a userid that has virtual 3270
lines that are not already servicing a
user.

056E

Line vdev busy on userid
Explanation: The virtual 270X or 3270
line specified in the DIAL command is
busy.
User Response: Reissue the DIAL
command at a later time when the line
becomes available.

DMK
use rid not receiving;
{disconnected IMSG offl message
too largel SMSG offlnot
authorizedlWNG offlVMCF error
nnnlIUCV error nnni quiesced}

057W
~

v.1

Explanation: The userid specified in a
MESSAGE, SMSG, WARNING, or CMS
TELL command did not receive the
message due to one of the following
conditions:

•

•
•

•

)

•

The user is disconnected.
The user has SET messages, special
messages, or warnings OFF.
The user is not authorized to receive
the message.
The message being sent was too long
to fit into the user's message buffer.
This can happen if the CMS TELL
command or CP SMSG command is
used to send a large message to a
user at another node.
The user has not established the
proper VMCF or lUCY connection.

User Response: If the MSG TOO
LARGE condition occurs, shorten the
message text or split it into two shorter
messages; then reissue the command.

058E

CTC vdev busy on userid
Explanation: The virtual
channel-to-channel device specified in
the COUPLE command is busy on the
receiving userid's virtual machine.
User Response: Reissue the command;
specify an available virtual
channel-to-channel device.

059E

A UTO LOG failed for use rid message
Explanation: An AUTOLOG command
was issued for a user, but the command
could not be executed for one of the
following reasons:

IPL missing - there was no IPL
record in the user's directory entry.

IPL failed - the IPL did not complete
successfully.

accounting errors - the logon
accounting routine returned a
nonzero return code.

incorrect password - The password
from the autolog command does not
match the password in the directory.

I/O error on terminal - An error
occurred with Input/Output
processing on the user's terminal.

IPL failed; error in CP directory The Initial Program Load could not
be completed successfully because of
an error in the Control Program
directory.

System Action: The user is not logged
onto the system.
User Response: For reason 1, have
your system administrator place an
appropriate IPL record in the specified
user's directory.
For reason 2, log onto the userid in the
usual manner to determine the cause of
the IPL failure.
For reason 3, contact your system
programmer to verify the correct
password or reissue the autolog
command with the correct password.
For reason 4, contact your system
programmer for specific requirements of
your local acccounting procedures.
For reason 5, reissue the AUTOLOG
command. If the error persists, contact
the system administrator to correct the
terminal problem.
For reason 6, contact the system
programmer to check the specified
user's CP directory.

Control Program (CP) Messages

115

DMK
Dump failed; virtual printer
unavailable

060E

063E

Explanation: The virtual machine is
not running in extended control mode or
the virtual control register 1, or
segment or page table entries are not
architecturally valid.

Explanation: The virtual printer either
does not exist or is not ready.
User Response: If a virtual printer
exists. issue the CP READY command
for it and then reissue the DUMP
command. If a virtual printer does not
exist, use the CP DEFINE command to
create one and reissue the DUMP
command.

06lE

Note: If virtual machine assist is
available, the STFIRST option must be
specified in the user's directory.

System Action: The highest
virtual = real address is set to zero.
User Response: Use the SET
STBYP ASS command only after the
virtual relocate system has been
reloaded and is running.

[Dump failed;] virtual printer
error
Explanation:
1.

Either an I/O error occurred while a
dump was being spooled to DASD,
or spool space has been filled.

Shadow table bypass; not set

064E

Shadow table bypass; reset
Explanation:

For PER, a problem has occurred
while attempting to write PER
output to the user's virtual printer.

User Response:

062E

Notify the system programmer.

For PER, if a virtual printer exists,
issue the CP READY command. If a
virtual printer does not exist, issue
the CP DEFINE command.

ECMODE not set on

Virtual = Virtual USER: Either the
virtual operating system attempted to
map a virtual address, not equal to its
real address~ to an address below the
highest virtual = real address in the
virtual address space or the virtual
machine loaded a Be mode PSW or the
virtual system was reset.

Explanation: A SET STBYP ASS was
issued to a virtual machine without the
ECMODE option being in effect.

System Action: The SET STBYPASS
command has been SET OFF. Virtual
machine execution will continue.

System Action: The command is
terminated.

User Response: Use the SET
STBYPASS command only when
running a virtual relocation operating
system that does not violate the shadow
table bypass restriction.

User Response: Issue the SET
ECMODE ON command which will
reset the virtual machine. Then IPL the
virtual system and reissue the command.

116

Virtual = Real USER: The virtual
system was running with 'SET
STBYP ASS VR'. The virtual machine
attempted to run with translation tables
resident in the first 4K of storage.

VM/SP System Messages and Codes

(

DMK
Highest allowable high-water
mark value is xxxxxK

065E

Explanation: The password was
entered on the same line as the
command or a valid option was
misspelled.

Explanation: The value specified by
the 'SET STBYPASS nnn' command
exceeded the highest allowable
high-water mark value. The high-water
mark value will be set only if it is not
higher than the following:
•

the virtual machine size

•

a high-water mark value determined
from the virtual machine's page and
segment tables.

The highest allowable high-mark value
may not be the true water mark value
because the virtual translation tables
may have several pageable page frames
contiguous with the true high-water
mark.

066E

Command format not valid

067E

User Response: Reenter the command
omitting the password or reenter the
command with the correctly spelled
option.
Note: With the PROTECT option on,
the LOGON password may not be
entered on the same line as the LOGON
command. Enter the password as a
response to the "ENTER PASSWORD"
message.

SEND command failed; receiver
message

068E

System Action: The high-water mark
value is set to zero, turning off the
function.

Explanation: The receiver was
specified in the SEND command.
'message' is one of the following:

User Response: Determine the true
high-water mark value from the virtual
systems configuration. Then reset the
SET STBYPASS nnn command with the
high-water mark value.

•
•
•
•
•

STMULTI option CSEG reset
Explanation: The previously defined
value of the CSEG option of the
STMULTI command has been reset to
zero because the virtual machine has
been reset.

System Action: Text is not sent to
receiver in any situation.
User Response:
1.

Secondary user not in effect because
receiver is logged on at a terminal.

The sender must be specified as
secondary user of the receiver on
the CONSOLE directory control
statement.

Receiver requires a virtual console.

Receiving virtual machine must do a
console read for input that is
already waiting, then the SEND
command can be reissued.

System Action: The CSEG option of
the STMULTI command has been reset
to zero.
User Response: Issue the SET
STMULTI command with the desired
value of the CSEG specified.

is not disconnected
has not authorized sender
has no virtual console
has console input waiting
is executing a console function

Control Program (CP) Messages

117

DMK
5.

070E

Receiving virtual machine must
complete console function before
another CP command can be sent.

code X'078' subcode X'10' has been
issued.)
This message can be issued during
execution of any operation that initiated
MSS mount or demount activity.

Device not available - MSS
devices allocated

Note: This message will always be
followed by a message from the specific
control program routine that needed
MSS activity.

Explanation: User is logged on with a
minidisk defined on a system volume
that is not mounted. When attempting
to find an MSS volume with the correct
volid, an MSS 3330V is required. There
are no MSS 3330V s available to try a
voluine count.

System Action: The opera.tion failed.
User Response: Request that the
system operator makes the
communicator virtual machine available
or wait until the communicator virtual
machine can be initialized.

Note: This message is immediately
followed by the current DMKLNK108E
message specifying the referenced 'vdev'
and 'volid'.

System Action: The operation failed.

072E

U ser Response~ Determine whether the
'volid' required is an MSS volume or
standard 3330-1. If it is a standard
3330-1, follow the actions for message
l08E. If it is an MSS volume, notify the
system operator so that the volume may
be made accessible.

Device not available - rdev not
proper type
Explanation: A dedicate or attach
operation is in process for device 'rdev';
device 'rdev' is a 3330V. The 'rdev' is
not the proper type (VIRTUAL or
SYSVIRT).
System Action: The attach or dedicate
operation failed.

071E

Device not available - MSS cannot
be accessed

User Response: Reissue the command
with the correct 'rdev' or if the 'rdev'
was specified correctly, request that the
system operator use the DEFINE
command to reset the 3330Vs
characteristics.

Explanation: The control program has
attempted an operation that requires
MSS access. The routine to
communicate with the MSS (DMKMSS)
is not active because of one of the
following reasons:
073E

118

MSS device not available - MSS
error

•

The communicator virtual machine
has not been logged on.

•

The VM system has not yet been
initialized in the virtual machine.

•

The DMKMSS program has not
been started in the virtual machine.

Explanation: The control program has
determined that the only possible way to
satisfy a request for a virtual device is
to issue an MSS mount request. The
MSS accepted the request, but later
generated an error indication.

•

The communicator virtual machine
is no longer available (DIAGNOSE

System Action: The control program
command that initiated the MSS request

VMjSP System Messages and Codes

(

DMK
will produce a message to indicate the
eventcal result of the MSS error.

076E

The valid parameter is invalid
Explanation: The 'valid' parameter
was specified with a range or multiple of
real addresses on the ATTACH
command. This not a valid
combination.

User Response: Contact the system
operator to ensure that action is
underway to correct the MSS error.
Reissue the command when the error
has been corrected.

Systenl Action: No addresses are
attached.
0741

Missing interrupt - device vdev
Explanation: The virtual machine
started I/O to its device 'vdev', that is
an MSS 3330V in the control program.
A cylinder fault occurred on the 3330V
but the corresponding attention
interruption was not received in the
specified time interval.

)

User Response: Reissue the command
with a valid combination of operands.

077E

Explanation: A DEFINE command was
issued with the VIRTUAL or SYSVIRT
parameter for device 'nnn'. Device
'nnn' cannot be defined because it is
already the specified type or it is active
in its current state.

System Action: The original I/O
operation is restarted to the device so
that if the cylinder fault is satisfied, the
request will complete normally.

System Action: The status of the
device is not changed. No further
DEFINE command processing occurs.

User Response: If the message recurs,
it may indicate an error in the MSS
staging adapter. The pending I/O
request can be cleared by issuing the
RESET 'vdev' command.

075E

User Response: The QUERY command
can be used to determine the exact
status of 'nnn'. The operator can either
issue the DEFINE command with a
different address specification or wait
until the status of 'nnn' has changed.

Device valid is not available
Explanation: An ATTACH command
has been processed to attach a 'volid' to
the system. However, the 'volid' is a
SYSVIRT 3330V and that volume is
mounted and its serial number is not the
same as that specified on the 'volid'
parameter.
System Action: The specified 'valid' is
not attached.
User Response: Choose an available
SYSVIRT 'valid' and reissue the
command. The QUERY command can
be used to find an available 'valid'.

Invalid request for device nnn

0781

MSS mount proceeding for
volume valid
Explanation: The control program
mounted the system volume 'volid' while
processing an MDISK or DED directory
statement or a LINK or ATTACH
command. The MSS is now mounting
the volume.
System Action: RC = 160.
The alloeatian of the virtual device is
queued, pending the completion of the
mount. Any SIO instruction issued by
the virtual machine to the virtual
address corresponding to the MSS
volunw is trapped by VM/SP and queued
until the volume is mounted. Control is

Control Program (CP) Messages

119

DMK
not returned to the user until the
volume is mounted and the SIO has
been passed to the volume.

08lE

Explanation: The VMSAVE option is
specified in the directory but a valid
saved VMSAVE system already exists in
the DASD target area.

User Response: None. However, if a
SIO is issued to the virtual device before
the mount is complete, that SIO will be
queued by VM/SP and the virtual
machine processing will be suspended
pending the completion of the mount.
The user can cancel the SIO, rather
than waiting for the mount, by getting
into CP mode and issuing the RESET
command for the virtual address. This
will cause CP to dequeue the SIO and
generate a condition code 3.

079E

User Response: Verify that the
NAMESYS macro is specified correctly
for this VMSAVE target area. Use the
QUERY VMSAVE command to
determine when the system was saved.
Use the IPL command to load the
system or the SET VMSAVE ON
command to clear the area.

082E

User Response: Do not attempt to
issue CP commands in this environment.
It is not possible.

System Action: The VMSA VE option
is not enabled.
User Response: Verify that the
NAMESYS macro defining the target
area is specified correctly. If none is
present, add a NAMESYS macro
defining the target area in module
DMKSNT. Issue the SET VMSA VE ON
or SET VMSA VE area-name to enable
the option.

120

System Action: The VMSAVE option
is not enabled.
User Response: Issue a QUERY
VMSAVE command to determine what
areas are available and then issue a
SET VMSAVE area-name command to
enable the VMSAVE option.

No preallocated VMSA VE area
Explanation: The VMSAVE option
was specified in the directory at logon,
or a SET VMSA VE ON command was
issued, and there is no entry in
DMKSNT with a USERID =
specification for this user.

VM/SP System Messages and Codes

More than one VMSAVE area
allocated, must specify area name
Explanation: The VMSAVE option is
specified in the directory or the user has
issued a SET VMSA VE ON command
when he has more than one target
VMSAVE area available to the user.

System Action: The operation is
ignored.

080E

(

System Action: The VMSAVE option
is not enabled.

CP command via central server is
not possible
Explanation: A user issued a control
program command from the central
server VIRTSYS requiring action from
the central server.

VMSA VE area already in use,
must use SET command

083E

VMSA VE area does not contain
valid saved system
Explanation: The user has issued an
IPL command to a VMSAVE target
DASD area. The DASD area specified
does not cont.ain a valid system.
System Action: The IPL command is
terminated.
User Response: Ve:rify that the correct
name was specified 011 the IPL
command. Ensure that tbe NAMESYS

DMK
specification points to the correct DASD
area. Reissue the IPL command.

084E

0871

Device vdev is in the process of
being reset
Explanation: A RESET command has
been issued for a virtual device already
in the process of being reset.

VARY failed, device rdev busy or
reserved
Explanation: A vary command was
issued for the specified device (rdev) and
a perpetual busy was encountered. This
may be the result of the device being
reserved by another processor.

System Action: The second RESET is
not executed.
User Response: Reissue the command
when the previous reset is complete.

System Action: The vary fails.
Device vdev is in the process of
being detached

0891
Operator Response: Try the command
at a later time.

Explanation: A RESET command has
been issued for a virtual device that is
being detached.

)
085E

Vary failed, fatal I/O error, dev
rdev

System Action: The second RESET
command is not executed.

Explanat.ion: An I/O error occured on
the specified device when attempting to
perform a READ DEVICE
CHARACTERISTICS command (CCW
command code X'E4').
System Action: The device is placed in
offline status, and system operation
continues.
Operator Response: Contact your
system support personnel.

086E

I/O error on DASD
Explanation: The VMSA VE option
was specified and an error occurred on
the DASD.
System Action: The VMSA VE option
is not enabled.
User Response: Reissue the set
VMSA VE command to enable the
VMSA VE option.

User Response: No user action is
required; the device will be detached
when it is available.

Device vdev not defined; device
{rdevlvolid} not available

090E

Explanation: The virtual device has
not been defined in the virtual
machine's configuration because the
real device described in the directory
DEDICATE card is not available. A
real device is considered not available if
it is:
•
•
•

Already attached to another user, or
In use by the CP system, or
Offline.

User Response: Ask the system
operator about the status and
availability of the real device. The
operator can attach the required device
or an alternate device to the virtual
machine.

Control Program (CP) Messages

121

DMK
091E

virtual and real addresses on the
DEDICATE statement.

DASD vdev not defined; temp
space not available

User Response: Send a message to the
system operator stating the problem so
that the error in the CP directory can
be corrected.

Explanation: The virtual device has
not been defined in the virtual machine
configuration because the temporary
space requested is not available.
Temporary space is considered not
available if:
094E
•

No space has been allocated by the
installation for temporary use, or

•

The number of cylinders (or blocks
if FB-512 device) requestp.d cannot
be satisfied from the available space
remaining.

User Response: The space cannot be
defined if it has not been allocated. If
space has been allocated, issue the
DEFINE command requesting fewer
cylinders (or blocks if FB-512 device.)

092E

Explanation: The storage specified in
the DEFINE command exceeds the
maximum allowable as specified in the
CP directory.
User Response: Reissue the DEFINE
command specifying a smaller storage
size.

095E

Device vdev not defined; devtype
vdev already defined

093E

Device vdev not defined; error in
CP directory
Explanation: The requested virtual
device has not been defined within the
virtual machine configuration because
of an error in the CP directory. An
example of this condition is a dedicated
2305 device which did not specify the
first exposure address for both the

122

VM/SP System Messages and Codes

Device vdev not defined;
insufficient free storage
Explanation: Sufficient free storage
could not be acquired to define a virtual
device as a result of the logon process
or a DEFINE command.

Explanation: The virtual device
specified has not been previously
defined within the virtual machine's
configuration, or that address is already
defined within the virtual machine's
configuration.
User Response: Reissue the command;
specify a virtual device ~ddress that is
not already defined wi thin the virtual
machine configuration, or detach the
conflicting virtual device address before
reissuing the command.

Storage exceeds allowed
maximum

User Response: Reduce the number of
virtual devices in the user
configuration. The system programmer
may want to allocate more free storage
to the system.

097E

Device vdev2 not defined; device
vdevl has active I/O
Explanation: An attempt was made to
redefine a qevice at address 'vdev2'
while this device (now at address
'vdevl ') is busy with I/O, or while it was
in an "intervention-required" state.
System Action: The command is
rejected.
User Response: Reissue the command
after the I/O completes on the specified
device, or when the
"intervention-required" condition has
been satisfied.

DMK
098E

Device rid mode switch not
possible
Explanation: If this message was
issued in response to the DIAL
command, it indicates that the DIAL
command was issued from a terminal
connected to a 37xx that is running the
Network Control Program (NCP) or the
Partitioned Emulation Program (PEP),
and the terminal cannot be switched
from network control mode to emulation
mode.

User Response: This is a warning
message for information only and no
further action is required.

102W

Explanation: The virtual device
specified has been forced into read-only
status because other users on the system
already have access to the same disk
area in read/writ.e mode. If only one
user has read/write access, that user's
userid is displayed at the terminal.

System Action: Command execution is
terminated.
User Response: For the DIAL
command, verify that the correct 37xx
control program is active, and that the
specific resource in use was generated
with the mode switch capability. Note
that the DIAL command cannot be used
with the NCP, because the NCP does
not support the mode switching
function.

099E

User Response: This is a warning
message for information only and no
further action is required.

103W

Explanation: Environmental data was
found twice in the sense data fro the
specified device (raddr).

User Response: This is a warning
message for information only and no
further action is required.

System Action: System operation
continues.

101W

DASD vdev forced RIO; RIO by
{nnn users Iuse rid}
Explanation: The virtual device
specified has been forced into read-only
status because other users on the system
already are linked to the same device
with read-only access. If only one user
has read-only access, that user's userid
is displayed at the terminal.

DASD vdev forced RIO; R/W by
{nnn users Iuserid}, RIO by {nnn
users Iuse rid}
Explanation: The given virtual device
has been forced into read-only status
because the disk is in read/write use by
some users and read-only use by other
users linked to the same disk area. If
the number of users having read/write
or read-only access is one, the single
userid is displayed at the terminal.

VARY FAILED,
ENVIRONMENTAL DATA DEV
raddr

Operator Response: This is a
hardware error. Contact IBM for
hardware support.

DASD vdev forced RIO; R/W by
{nnn users Iuse rid}

104E

use rid vdev 110t linked; RIO by {nnn
users Iuse rid}
Explanation: The link to the user's
virtual device has not been
accomplished because that disk area is
already in read-only use by one or more
users. If the number of users is one, the
single userid is displayed at the
terminal.
User Response: Reissue the LINK
command, specifying the appropriate

Control Program (CP) Messages

123

DMK
alternate access to obtain a link to the
desired area in read or write mode.

lOSE

Explanation: The link to the user's
virtual device address has not been
accomplished because the virtual device
is defined on a volume that is not
currently mounted on the CP system.

use rid vdev not linked; R/W by
{nnn users Iuse rid}
Explanation: The link to the user's
virtual device has not been
accomplished because that disk area is
already in read/write use by one or more
users. If the number of users is one, the
single userid is displayed at the
terminal.
User Response: Reissue the LINK
command, specifying the appropriate
alternate access to gain a link to the
device in the required mode.

I06E

User Response: Send a message to
system operator asking that the
specified volume be mounted and
attached to the CP system. Reissue the
LINK command when the operator
confirms that the correct volume has
been mounted.

I09E

use rid udeu not linked; R/W by
{nnn usersl userid}, R/O by {nnn
users Iuserid}

107E

userid vdev not linked; not in CP
directory
Explanation: The link to the user's
virtual device has not been
accomplished because that virtual
device address is not defined in the
directory for the specified userid.
User Response: Reissue the LINK
command, specifying the correct virtual
device address or the correct userid.

124

VM/SP System Messages and Codes

use rid udeu not linked; invalid link
device
Explanation: The link to the user's
virtual device has not been
accomplished because the virtual device
defined in the user's CP directory entry
is not a minidisk to which a link can be
accomplished.

Explanation: The link to the user's
virtual device has not been
accomplished because the disk is in
read/write use by some users and
read-only use by other users. If the
number of users is one, the single userid
is displayed at the terminal.
User Response: Reissue the LINK
command, specifying the appropriate
alternate access required to gain the
correct link to the disk area.

use rid udeu not linked; volid volid
not mounted

User Response: Reissue the LINK
command with a valid userid and virtual
device address.

110E

userid vdeu not linked; devtype vdev
already defined
Explanation: The link to the user's
virtual device has not been
accomplished because this virtual
machine already has a device with the
same address defined in its
configuration. If a CTCA is defined in
the virtual machine's configuration, 16
virtual addresses are defined for that
CTCA and a link using one of those
addresses cannot be made.
User Response: Reissue the LINK
command requesting a different virtual
device address, detach the device with
the conf1icting virtual address from the
virtual machine, and then reissue the
LINK command.

DMK
IIIE

userid vdev not linked; no read
password

User Response: Reissue the LINK
command and specify the correct
password. On a system with RACF
installed, you must contact the owner of
the minidisk and request authorization
to link to that minidisk.

Explanation: The link to the user's
virtual device has not been
accomplished because no read access to
it is allowed.
User Response: Contact your system
programmer to request a directory
change.

112E

115E

Explanation: The AUTOLOG
command issued from a virtual machine
by a DIAGNOSE instruction is now
invalid because the user has entered
four incorrect passwords associated with
the AUTOLOG command during the
current terminal session.

use rid vdev not linked; no write
password
Explanation: The link to the user's
virtual device has not been
accomplished because no write access to
it is allowed.

The LINK command is now invalid
because the user has exceeded the limit
of ten incorrect passwords for access to
minidisks during the current terminal
seSSIon.

User Response: Contact your system
programmer to request a directory
change.

113E

User Response: You must logoff and
logon again to be able to LINK to any
minidisk. You may issue the
A UTOLOG command from the virtual
machine environment; however, you
must allow the CP system to prompt you
for the password rather entering it as
part of the input line. This error
condition from the AUTOLOG or LINK
command is designed to prohibit
password guessing by repetitive calls to
the command from within the virtual
machine.

userid vdev not linked; no multiple
password
Explanation: The link to the user's
virtual device has not been
accomplished because no multiple-access
password is specified for the user's
minidisk.
User Response: Contact your system
programmer to request a directory
change.

114E

use rid vdev not linked; mode or
password incorrect
Explanation: The link to the user's
virtual device has not been
accomplished because an incorrect
password or filemode was entered. On
systems with RACF installed, you may
not be authorized to link to the minidisk
you specified.

{AUTOLOGILINK} invalid;
excessive incorrect passwords

116E

use rid vdev not linked; CP
directory in use
Explanation: The userid to which you
are linking is either logging on the
system, or someone else is attempting a
link to the same userid at this time.
User Response: Reissue the LINK
command.

Control Program (CP) Messages

125

DMK
117E

lISE

userid use rid not linked; volid volid
conflict

120E

Explanation: The volume label in the
userts directory entry matches the
volume label on the real device, but the
device class and device type are not the
same.

Explanation: The real device has not
been attached to the specified userid
because that userid has already defined
a virtual device of the specified virtual
address.

User Response: Correct the error in
the directory for the device that cannot
be linked.

Operator Response: Reissue the
ATTACH command specifying a
different virtual device address for the
user. You should first send a message,
via the MESSAGE command, to the
user asking what action should be taken
and what virtual device should be
assigned. The user may wish to detach
the conflicting virtual device from his
machine configuration and ask the
operator to reissue the ATTACH
command.

userid vdev not linked; command
format not valid

Explanation: The LINK password was
entered on the same line as the LINK
command or a valid option was
misspelled.
User Response: Reenter the LINK
command omitting the password or
reenter the LINK command with the
correctly spelled option.

12lE

User Response: Reissue the DETACH
command specifying the correct device
address for the userid.

use rid vdev not linked; insufficient
free storage

122E
Explanation: Sufficient free storage
could not be acquired to satisfy the link
request for a virtual device.
User Response: Reduce the number of
virtual devices in the user configuration
or in other user configurations. The
system programmer may want to
allocate more free storage to the system.

1~6

devtype rdev not attached to use rid

Explanation: The real device has not
been detached from the specified userid
because it was not attached to that user.
Either the real device or the userid has
been incorrectly specified.

Note: With the PROTECT option on,
the LINK password may not be entered
on the same line as the LINK command.
Enter the password as a response to the
"ENTER PASSWORD:" message.

119E

devtype rdev not attached; use rid
vdev already defined

VM/SP System Messages and Codes

devtype rdev already attached to
use rid

Explanation: The requested real device
is already attached to another userid.
The operator has probably specified an
incorrect real device address.
Operator Response: Reissue the
ATT ACH command, specifying the
correct real device address.

DMK
123E

DASD rdev CP-owned

127E

Explanation: The command has not
been processed for the requested userid
because that device is owned by the CP
system. A CP-owned device is one that
is defined in the system-owned list and
is in use for paging or spooling space.

Explanation: The real device has not
been attached to the system because the
volid read from the label does not match
the one specified with the command.
Operator Response: Reissue the
ATTACH command specifying the
correct volid.

User Response: The command cannot
be specified for the real device because
that device must remain owned and in
use by the CP system.
128E
124E

)

125E

DASD rdev error reading
alloca tion record

DASD rdev in use by nnn users
Explanation: The command has not
been executed because the device is in
use by the stated number of users.

Explanation: The volume, which is a
CP-owned volume, has not been
allocated for CP use because the
allocation record could not be read.

User Response: The command cannot
be executed for the specified real device
until all users who have minidisks in
use on that device detach them.

Operator Response: Detach the device
from the system and reattach it to the
system, after checking that there are no
equipment failures.

DASD rdev volid volid already
!:lttached to system

129E

Explanation: The volid is already
mounted and attached to the system.

DASD rdev error reading volid
Explanation: The specified device
could :pot be attached to the system
because of an error in reading the
volume label.
Operator Response: Check that there
are no equipment failures; reissue the
ATTACH command.

Channel x [processor xx] devices
in use
Explanation: The ATTACH
CHANNEL command has not been
executed because the devices on that
channel (on the specified processor) are
already in use.

Operator Response: Reissue the
ATTACH command specifying the
correct volid. It may be necessary to
detach the real device from the system
that contains the duplicate volid before
attempting the ATT ACH co~mand
again.

126E

DASD rdev volid volid does not
match

Operator Response: Detach devices
from users and the system before
reissuing the ATTACH CHANNEL
command.

130E

Channel x [processor xx] not
attached to userid
. Explanation: The DETACH
CHANNEL command has not been
accomplished because (1) channel x is
not attached to the specified userid, or
(2) the channel is not attached on the
specified processor.
System Action: The DETACH
CHANNEL command is rejected.

Control Program (CP) Messages

127

DMK
Operator Response: Reissue the
command; be sure to specify the correct
channel (and processor) for the userid.

13lE

134E

Explanation: The command has not
been executed for the requested userid
because the user has attached a
dedicated channel with the same
channel number as the virtual channel
number specified in the ATTACH
command.

Insufficient free storage available
for {ATTACHILOGON} request
Explanation: An attempt was made to
acquire storage for virtual
device/control unit/channel blocks from
free storage. The storage request could
not be satisfied. In the case of
ATTACH, no devices are attached. In
the case of LOGON, logon processing is
accomplished but no virtual devices are
available in the user's configuration.

Operator Response: Verify that the
vdev in the ATTACH command is
correct.

13SE

User Response: Reduce the amount of
storage being requested by reducing the
number of virtual devices being
attached or logged on. The system
programmer may want to allocate more
free storage to the system.

132E

Operator Response: Request that the
user detach all devices from the
requested virtual channel and then
reissue the command specifying the
correct channel address.

devtype vdev not detached; channel
x dedicated

Explanation: The command has not
been executed because the device was
attached via the ATTACH CHANNEL
command.
Operator Response: If the channel is
no longer needed, issue the DETACH
CHANNEL command.

Channel x already defined by
usefid
Explanation: The userid's virtual
machine already has a channel with the
same address defined in the virtual
machine.

devtype vdev not attached; channel

x dedicated

136E

Device {vdev Irdev} not
{definedlvaried}; channel x
dedicated
Explanation: A VARY ONLINE
command for device rdev or a DEFINE
command for device vdev has been
issued and the channel to which the
device is attached is dedicated.
System Action: The command is
rejected.

133E

DASD rdev not ready
Explanation: An attempt has been
made to attach a DASD device that is
not ready.
Operator Response: Make the device
ready and reissue the command.

128

VMjSP System Messages and Codes

Operator Response: In order to vary
on or define more devices on channel x,
the channel must first be detached from
the userid to which it is attached.

DMK
l37E

DASD vdev not linked; channel x
dedicated

l4lE

devtype rdev not active

Explanation: The command has not
been executed because the device
specified was not performing any
spooling function.

Explanation: Channel x is dedicated to
this virtual machine. The vdev
appearing in the error message has a
virtual channel that is equal to the real
dedicated channel. Users of dedicated
channels are not permitted to link to
DASD device(s) where the virtual
channel equals the real dedicated
channel.

User Response: Reissue the command;
specify the correct real device, if
necessary.

l42E
User Response: Reissue the LINK
command using a diffe:.:ent virtual
channel address.

l3SE

Explanation: The command has not
been executed because the device
specified was not in a drained status.

Channel x [processor xx] not
attached; insufficient free storage
Explanation: Sufficient free storage
could not be acquired to satisfy the
attach channel request. The request
cannot be satisfied unless all devices on
the channel (on the specified processor)
can be attached.
User Response: Reduce the number of
virtual devices in the user
configuration. The system programmer
may want to allocate more free storage
to the system.

devtype rdev not drained

Operator Response: Drain the
specified device via the DRAIN
command, and reissue the command.

l43E

devtype rdev in use by system

Explanation: The specified device
either:
•
•

Is attached to the system, or
Is performing I/O activity.

System Action: The command is not
executed.
Operator Response:

l40E

devtype rdev attached to use rid

•

For any device other than a 37xx,
detach the device if possible, or wait
for the I/O activity to cease, and
then reissue the command.

•

For an active 37xx, the command
cannot be executed.

•

If a NETWORK DUMP is required,
use the 3704/3705 LOAD button to
activate automatic dump and reload
procedures.

•

If a NETWORK LOAD of a
8704/:n05 control program other
than the active one is required, use
the NETWORK DUMP command
with the OFF operand to suppress

Explanation: The device specified is
not under CP control but is attached to
the specified userid for its exclusive
control.
User Response: Reissue the command;
specify only devices under CP control.
The operator must detach the device
from the specified user in order to make
it available to another user.

Control Program (CP) Messages

129

DMK
automatic recovery, and then use
the subsequent NETWORK LOAD
command.

144W

User Response: Each installation will
have to define the specific action they
wish to take when this situation arises.
Since the situation is a possible attempt
to penetrate the system, it should not be
ignored.

devtype vdev RESET BY userid
Explanation: The HALT command was
used to terminate an active channel
program and that channel program was
associated with a specified virtual
device.

1461

Explanation: The system was unable
to supply the necessary spool file blocks
for the VMDUMP.

System Action: The real device is
halted and all pending interrupts are
cleared from the specified virtual device.
The virtual machine then enters CP
command mode.

System Action: The VMDUMP
request is canceled and any spool file
blocks are freed.
User Response: Do not reissue the
command until spool space is available.

Programmer Response: Ensure that a
valid channel program was started to
the specified virtual device.
147E
User Response: IPL the virtual system
to continue.

1451

VMD UMP failed; spooling error

Channel x [processor xx] not
attached; alternate paths defined
Explanation: An ATTACH CHANNEL
command has been issued to attach
channel x (to processor nn). There is at
least one device on the specified
channel that has an alternate path
generated.

USERID userid AT rdev WITH
INVALID {LINKILOGON}
PASSWORD NO nnn HAS
VIOLATED THE LIMIT OF limit
Explanation: The installation defined
threshold for invalid passwords has been
reached by "userid" or "rdev."

System Action: The ATTACH
CHANNEL command is rejected. The
ATTACH CHANNEL command is used
to dedicate all the devices on a real
channel to a specified virtual machine;
the one-to-one correspondence of virtual
devices to real devices cannot be
maintained if alternate paths to any of
the devices are genera ted.

rdev - address of terminal being used.
nnn - current invalid password count.
limit - current limit.
When the current limit is met, message
DMKJRL145I is sent.

Operator Response: None
If the optional information
"[,A = auserid]" is present, the message
is the result of an AUTOLOG command.
In this case "userid" is the userid
specified in the AUTOLOG command,
and "auserid" is the userid of the issuer
of the AUTOLOG.

148E

devtype rdev buffer load name failed

Explanation: The buffer load cannot
be accomplished because of an I/O
failure on the specified device, or the
I/O task has been reset.

Operator Response: None.
It could also mean that module

130

VM/SP System Messages and Codes

DMK
DMKUCS, DMKUCB, or DMKUCC has
exceeded a page boundary (4K).

1511

User Response: Reissue the command,
attempting to load the buffer as before.
lf the problem persists, there is probably
a hardware error. Call your system
support personnel for assistance.

149E

Explanation: Fc'llowing an ATTACH
command, the sYRtem issued 256 test I/O
instructions to the DASD and a busy
condition persisted.
System Action: The device is not
attached.

DEVICE PATH rdev PRESENTED
CC=3 ON I/O REQUEST

User Response: Use the IOBSTAT
with the IOBCSW + 4 statuse byte to
find out what caused the busy condition.

Explanation: An I/O operation has
found an offline path to a device. The
device will appear online to a QUERY
command.

Values

Operator Response: Make sure the
control unit and device switches are on.
lf all switches are on, a hardware
malfunction is probably the cause of
this offline condition. Notify your
system support personnel.

For the first three cases, check for a
possible shared control unit or a
reserved DASD operating in a shared
dasd environment. In all cases, reissued
the ATTACH DASD command once the
busy condition has been cleared.

User use rid has issued a {CPIVM}
read
Explanation: A disconnected user, for
whom this user is acting as the
secondary user, has issued a console
read, or CP has issued a console read on
behalf of the disconnected user.
System Action: The console read is
not actually performed, but a record of
it is kept in a queue.
User Resp0l1.se: A SEND command
must be issued to satisfy the console
read.

Meaning

IOBSTAT=Ol and short control unit
IOBCSW + 4 = 7000 busy
IOBSTAT=Ol and busy device
IOBCSW + 4 = 1000
IOBSTAT = 01 and busy control unit
IOBCSW + 4 = 0000
IOBST AT = 02 and channel or
IOBCSW + 4 = 0000 subchannel busy

System Action: The I/O operation was
started on another path if one exists. lf
anot~er path does not exist, an
unrecoverable error was posted to the
calling task for this I/O operation.

150A

DASD vdev not attached; busy
persists,IOBSTAT=xx,
IOBCSW+4=xxxx

152E

{PFCOPYIPFTAB} NOT
AVAILABLE
Explanation: VM/SP does not support
COpy or TAB function settings for
program function keys on TTY
terminals. You can set tabs using
appropriate hardware facilities. For the
3101, you ean use the PRINT keys
instead of the PFCOPY function if a
3102 is attached. See the related
hardware publications for the affected
device, listed in the preface.
System Action: Ignores the PF
request.
User Response: Do not use the PF
keys for COPY or TAB functions.

Control Program (CP) Messages

131

DMK
153E

User Response: Correct the RDEVICE
macro for device XXX by coding the
CL USTER = parameter. If a
CL USTER = parameter is coded, check
for an incorrect continuation from the
previous line. Ensure that (in the
DMKRIO listing for device XXX) the
RDEVBLOK contains a label for
RDEVNICL.

Device {vdevlrangelchannel x}
exceeds maximum number of
virtual devices
Explanation: An attempt was made to
create (via LINK, DEFINE, or
ATT ACH) a virtual device, a range of
devices or a channel which would have
resulted in the maximum number of
virtual devices for the user's virtual
machine.
1581

Explanation: The UCSB name given in
the LOADBUF UCS command does not
match the UCSB currently loaded in the
printer.

User Response: Detach a sufficient
number of existing virtual devices or
channels from the user's virtual
machine so that the total number of
virtual devices or channels will not
exceed the maximum allowable. Then
reissue the command or request that the
ATT ACH be re-attempted.

154E

System Action: None.
User Response: Verify that the correct
UCS image name is indicated on the
command line. If the name is correct,
verify that the band image loaded in the
printer is correct.

Device rdev VARY failed, VARY in
process
Explanation: A VARY command was
issued for the specified device (rdev)
while another VARY command was
being processed for that device.

159E

User Response: Reissue the VARY
command.

System Action: Network enable
command processing is terminated.

132

System Action: Execution of the
command is terminated.

'CLUSTER = ' parameter missing
from RDEVICE macro - device
rdev
Explanation: While attempting to
network enable a device for line XXX,
DMKNET found that there was no
cluster specified for the line
(RDEVNICL = 0).

VM/SP System Messages and Codes

SPMODE on - cannot unlock
Virtual = Real
Explanation: The user is attempting to
use the UNLOCK command to unlock
pages that are within the V = R region
while running an AP/MP configuration
with SPMODE set on.

System Action: The VARY command
is canceled.

157E

ues image name mismatch;
image name loaded is image

System Action: The command is
rejected.

User Response: Do not attempt to
unlock the V = R region in this
environment. It is not possible.

160E

Hexloc hexloc exceeds storage
Explanation: The hexadecimal
location specified exceeds the storage
size. If the hexadecimal location was a
virtual address. the address was beyond
the range of the virtual machine storage
size; if it was a real address, then the

DMK
address was beyond the range of the
real storage size.

162W

Explanation: The virtual machine is
running in extended control mode and
an attempt has been made to store the
reset value specified into the control
register specified. The store is
completed.

Note that. the storage created by a
virtual operating system running under
VM/SP is beyond the range of the
virtual machine storage size. Thus, the
virtual region of a VS operating system
running under VM/SP, for example,
cannot be displayed.

User Response: Verify your intention
to reset the specified control register
before continuing in extended control
mode.

User Response: Reenter the command,
using only valid hexadecimal locations
within the range of the real or virtual
storage size.
163E
I6lE

Invalid ECR x - xxxxxxxx

STORE exceeds maximum
register

Shared page hexloc altered by
Explanation: The STORE command
has been specified for registers with a
number of operands to be stored in
contiguous registers, and the number of
operands specified would place the store
beyond the valid register range.

use rid

Explanation: The operator has issued
an STCP (store CP) command for the
shared page at hexadecimal location
'hexloc'. This page has just been altered
by the currently dispatched user,
'userid', and it therefore will belong
solely to 'userid'. Another copy of the
shared page will be created at another
location for the other users sharing the
page before the next user is dispatched.
Since it is assumed that the operator
wishes to change the contents of the
shared page, not the individually-owned
page, the STCP command is not
executed.
Operator Response: If you want to
change the contents of the shared
segment, use the class A LOCK
command with the MAP operand to
determine the real address of the page,
and then reissue the STCP command
with the corrected shared page address.
If you want to change the contents of
the altered, individually owned page,
reissue the STCP command; this time it
will be executed.

System Action: The system has stored
up to and including the maximum
register allowed for the store function.
User Response: Verify that the STORE
command was entered correctly and that
the beginning register was correctly
specified. If they were not, reissue the
STORE command, specifying the correct
registers and operands.

164E

Hexloc hexloc non-addressable
storage
Explanation: The hexadecimal address
specified with the command lies within
a non addressable storage range.
Nonaddressable storage is storage
created by named systems such as
VSAM.
User Response: Reissue the command,
specifying a valid hexadecimal address.

Control Program (CP) Messages

133

DMK
1651

Page hexloc not locked; shared
page

1691

Explanation: The page user at
hexadecimal location "hexloc" cannot
be locked because it is a shared page.

Explanation: A VARY command was
issued to a 3480 tape device, which had
an outstanding intervention-required
condition.

System Action: The system skips this
page and continues to lock any
remaining unshared pages in the range
specified in the LOCK command.

System Action: The VARY command
is cancelled.
User Response: Take· appropriate
action to make the device ready.
Reissue the VARY command.

User Response: If more pages are to be
locked, the user must reissup- the LOCK
command specifying unshared pages.
170E
166E

Changed shared page not written
to auxiliary stora~e
Explanation: The store into a shared
page has been made, but a copy of the
change has not been written to backup
storage. The recompute bit is on and no
page slot is available. The change may
be lost if it is assigned later as a private
page.
User Response: Provide more paging
space.

168E

STATUS operand requires
ECMODE
Explanation: The virtual machine is
not running in extended control mode
and an attempt is made to store selected
data to virtual machine's low storage
locations.
System Action: The STORE command
is cancelled.
User Response: The virtual machine
must be in extended control mode and
reissue the STORE command.

134

VM/SP System Messages and Codes

VARY not performed, device rdev
not ready

System sysname exceeds storage
I'

Explanation: If this message was
issued in the response to the SAVESYS,
SET VMSAVE, or IPL command, the
system name specified uses a virtual
storage size larger than that defined for
the virtual machine.
If this message was issued in response to
a NETWORK command~ the specified
3704/3705 control program is larger than
the 3704/3705 storage (as specified by
the RDEVICE macro), and the control
program image cannot be loaded into
the specified 3704/3705.
User Response: For any of the above
commands, reissue the command,
specifying a system name that will fit
within the virtual machine storage size.
Optionally, redefine the virtual machine
storage size using the DEFINE
command, and then reissue the
command (except for the SET VMSAVE
command).
For NETWORK, reissue the command
specifying another control program that
will fit in the 3704/3705.

DMK
171E

System sysname volid volid not
mounted
Explanation: If this message was
issued in the response to the SA VESYS
or the SET VMSA VE command, the
system name cannot be saved because it
requires a volume that is not mounted.
This may be the volume on which the
named system was to be saved or the
volume that the saved system needs in
order to properly execute once loaded.

User Response: No action can be
directly taken by the user. Verify that
the system name you are trying to save
or IPL contains the correct virtual
device address and that that virtual
device address matches the extent on
the required owned volume for that
system.

If this message was issued in response to

Explanation: The system name
specified with a SA VESYS or IPL
command requires that the virtual
machine be using a direct access storage
device with the specified virtual
address.

the IPL command, the system name
cannot be loaded because it requires a
volume that is not mounted. This may
be the volume that contains the saved
system, or the volume that the saved
system needs in order to properly
execu te once loaded.

User Response: In the virtual machine
configuration, define the required DASD
address. Then reissue the command,
specifying the correct system name.

If this message was issued in response to

the SAVENCP command, the volume
specified by SYSVOL in the NAMENCP
macro in DMKSNT is not currently
available.

System sysname requires DASD
vdev

173E

Paging error - {I/Oladdress
exception}[: message]

174E

If this message was issued in response to

a NETWORK command, the Network
Control Program cannot be loaded
because the volume on which it resides
is not mounted.
User Response: Send a message to the
system operator stating which volume is
not mounted, and request that he mount
the desired volume and attach it to the
system. Reissue the command once the
operator has verified that the correct
volume is mounted and attached.

172E

Explanation: An paging error was
detected; either I/O or addressing
exception.
System Action: Defined in the
'message' text:
•

Checkpoint area invalidated:
Unable to read checkpoint page.
Another message (919) followed
describing the system action.

•

Command terminated: Command
terminated before completion of
requested functions.

•

IPL failed: IPL not complete

•

Page not locked: The loc"k was not
completed on that page.

•

Command complete: Portions of
the requested address range
encountered paging errors. A dump
has been created.

System sysname DASD vdev incompatible SYSRES
Explanation: The system name
specified cannot be saved or loaded (via
IPL) because the direct access storage
device address within the virtual
machine's configuration does not match
the DASD address and location specified
in the name table of the CP system.

Control Program (CP) Messages

135

DMK
•

No dump created: Every page or
portions of the requested address
range encountered paging errors.

176E

Explanation: The UNLOCK
VIRT = REAL function could not be
executed because the given userid is
logged on and occupying the
virtual = real area. If the virtual = real
area is in use by the system, the
virtual = real area has been unlocked
and is unavailable for virtual = real use
until the system is reloaded.

User Response: If the message resulted
from a warm start or checkpoint
processing, notify installation personnel
about the DASD I/O error; check the
operator response for message 919.
Otherwise, reissue the command; if the
failure persists, notify the system
operator.

174W

User Response: Request that the user
log off, or force the user to log off, and
then reissue the command specifying the
virtual = real area.

Paging error - I/O: default printer
logo will be used
Explanation: An I/O error occurred
trying to page DMKBOX into the
system to construct the
installation-defined printer logo.

177E

User Response: None required.

{RESERVElname} already in use
by use rid
Explanation: For RESERVE, the
RESERVED operand specified in the
SET command cannot be applied to the
specified user because that function is
already in use by the userid identified in
the error message.

System Action: The command is not
executed. System operation continues.
User Response: Reissue the IPL
command with not more than 'xx'
characters in the parameter string
following the P ARM option. If you
received this message while logging on
(LOGON). contact your installation
support group.

For name, the VMSAVE area specified
is in use by the userid identified.
User Response: For RESERVE, turn
uff RESERVED operand for the user
specified in the error message, and
reissue the SET command specifying the
new userid for the desired function.
178E
For name, send a message to the other
user asking him to release the area or
issue the QUERY VMSAVE command
to find out if any other areas are
available.

136

VM/SP System Messages and Codes

Parameter exceeds xx characters
Explanation: The PARM option on
your IPL statement is followed by a
parameter string longer than can be
passed to the system to be IPLed. The
value of 'xx' specifies the maximum
length of the string that can be passed.
The largest value 'xx' can have is 64. If
the value of 'xx' is less than 64, then the
named saved system specified by the IPL
command was defined by your
installation with a PARMRGS range of
less than 16 registers.

System Action: Printing continues
with default logo.

175E

Virtual = Real area in use by
{use rid Isystem}

System sysname exceeds available
DASD space
Explanation: The amount of DASD
space reserved by the NAl\tfENCP macro
is insufficient to contain both the
3704/3705 control program image and
the system control information.

DMK
User Response: Increase the amount of
DASD space reserved by the NAMENCP
macro, and reissue the command. Verify
that the extra pages required for the
system control information were
included when the DASD space was
assigned.

179E

ISlE

Explanation.: The virtual machine has
issued the CP commands STORE,
ADSTOP or TRACE and the address
targeted by the command is referencing
a shared named system page. The
shared named system is released and a
replacement of the named system is
made with a nonshared copy.

System sysname volid volid not
CP-owned

User Response: The virtual machine
continues to run but is now running the
shared named system in nonshared
mode. The user should be aware that
total system efficiency decreases as the
number of users running with
nonshared copies of a shared named
system increases. When the user no
longer needs his own copy of a
nonshared system he should attempt to
replace it with a shared copy. In most
instances this would mean reload (via
IPL) of the shared named system.

Explanation: The DASD volume
specified by SYSVOL in the NAMENCP
or NAMESYS macro is currently
attached to the VM/SP system, but it is
not a CP-owned volume, and therefore is
not a valid residence volume for the
saved system image.
User Response: Ensure that the
correct DASD volid was specified in the
NAMENCP or NAMESYS macro in
DMKSNT, and that the physical DASD
volume mounted is the correct volume.
Verify that the specified volid is
included in the SYSOWN macro in
DMKSYS, and reissue the SAVENCP
diagnose or the SAVESYS command.

180E

PER trace not in effect
Explanation: The user has tried to
perform an operation on a traceset and
no tracesets are defined.
System Action: None.
User Response: Establish a traceset
before trying to perform the operation
that caused this message to be issued.

180W

TRACE not in effect
Explanation: The TRACE END
function has been specified and the
TRACE function was not in effect.

Shared system sysname replaced
with non-shared copy

1821

PER trace is active
Explanation: 10,000 PER interrupts
have occurred without a display to the
terminal. Certain tracing may take
longer than others depending on the
events and ranges chosen for the trace.
This is related to the way that the
hardware recognizes a successful PER
event. The PER command allows
greater selectivity than the hardware
for the PER events that are displayed.
Therefore, some PER interrupts
generated by the hard ware are not
displayed due to the selectivity of the
PER command.
System Action: None.
User Response: You can prevent this
message by issuing the CP command
SET IMSG OFF.

User Response: This is a warning
message for information only and no
further action is required.

Control Program (CP) Messages

137

DMK
183E

VM assist not active

185E

Explanation: A SET ASSIST ON or a
SET ASSIST SVC command was issued.
However, the operator deactivated the
assist feature for the whole machine.
On an Attached Processor system, this
message indicates that the assist is not
active on any processor, unless the user
has affinity set on. If the user has
affinity set on, then the message
describes the state of the assist for the
affinity processor only.

CP assist level nnnn not
supported; CP assist disabled

Explanation: When VM/SP was
loaded, a mismatch was detected
between the hardware assist level and
the software. Errors might result if the
CP assist or the extended virtual
machine assist feature were used.
System Action: CP assist is set
unavailable.
User Response: Update the processor
or software support to an equivalent
level.

System Action: The user description is
updated to use the assist feature when
the operator activates it for the system.

(
\~

User Response: None.

184E

186E

Explanation: A SET CP ASSIST
command was issued but Extended
Control-Program Support is not
available on the processor, or there is a
mismatch between the hardware assist
level and the software.

VM assist not available [on
processor xx]
Explanation: A SET ASSIST or a SET
SASSIST command was issued but the
hardware assist feature is not available
on the indicated processor address. In
an Attached Processor system, the
response with an optional parameter
indicates the assist is not available on
either processor. The optional
parameter is provided for the SET
ASSIST command only if the user has
affinity set on, and the assist feature is
not available on the affinity processor.
System Action: If the assist feature is
not available on any processor,
execution of the command is terminated.
If the assist feature is available on the
other processor, the user VMBLO K is
updated to use the assist feature when
the user resets his affinity.
User Response: None.

CP assist not available

User Response: None.

187E

Timer assist not available
Explanation: A SET ASSIST TMR
command was issued on a processor that
does not have VM/370 Extended
Control-Program Support, or on a
processor on which virtual machine
assist has been temporarily disabled by
the operator.
System Action: If the processor does
not have this support, no further action
is taken. If the support is disabled, the
bit VMFVTMR is set, so that if the
support is enabled at a later time the
timer assist will be used (provided the
user has issued SET TIMER ON or SET
TIMER REAL and does not have
TRACE EXT active).
User Response: None.

138

VM/SP System Messages and Codes

DMK
188E

Specified processor unavailable

191E

Explanation: The processor specified
in the command is not online. This
message is issued in response to the
following commands: SET AFFINITY,
SET ASSIST, ATTACH CHANNEL, and
DETACH CHANNEL. If the command
issued was SET AFFINITY ON, the
processor in the user directory entry is
not online.

Explanation: Numerous attempts were
made to bring processor nn online and it
was found that processor xx was not
available to the system.
System Action: The command is not
processed.
Operator Response: Reissue the
command with the required processor
number.

System Action: The command is
rejected.
Operator Response: Reissue the
command; be sure to specify the address
of a processor that is online.

)
/

189E

AFFINITY not set, system in
uniprocessor mode
Explanation: The requested processor
is in use. Since only one processor is
being used, the requestor is always
executed on that processor.

Processor xx does not exist

192E

VARY PROCESSOR command
failed
Explanation: A VARY PROCESSOR
OFFLINE command was issued and one
of the following occurred:
•

The system is in uniprocessor mode.

•

The processor is not online.

•

The processor is the main processor
and the channel set switching
feature was not installed or did not
work.

User Response: None.

190E

No AFFINITY specified in
directory
Explanation: The SET AFFINITY ON
command could not be executed. The
user's directory was checked and no
affinity specification was found. No
affinity was set for the user.
User Response: Reissue the command
with an explicit processor address, or
update the directory entry for the user
to include AFFINITY.

A VARY PROCESSOR ONLINE
command was issued and one of the
following occurred:
•

The system is not generated for
attached processor mode.

•

The multiprocessor feature is not
installed.

•

The system is already in attached
processor mode.

System Action: The command is not
processed.
Operator Response: None.

Control Program (CP) Messages

139

DMK
PROCESSOR xx ONLINE

1931

196E

Explanation: The spBcified processor is
now online and operational.

Secondary user not in CP
directory
Explanation: A user who has specified
a secondary user logs on but the
secondary userid is not in the CP
directory.

System Action: None.

Operator Response: None.
System Action: Logon continues.
1941

User Response: If valid secondary user
is desired, add secondary user to CP
directory and logon again.

PROCESSOR xx OFFLINE
Explanation: The specified processor is
now offline and not being used.
System Action: None.

197E

Operator Response: None.

Explanation: Secondary user is either
disconnected or not logged on.
System Action: DISCONNECT
continues normally.

370E FEATURE UNAVAILABLE
ON PROCESSOR xx

195A

Explanation: Processor nn has been
varied online. (The system has gone
from attached processor mode to
uniprocessor mode.) The attached
processor does not have the 370E
hardware feature.

User Response: Logon the secondary
user if terminal services are required.

198W

User Response: If the 370E feature is
needed, a class A user should do the
following:
Issue the QUERY PROC command
to obtain the addresses of the
processors online.

Set affinity to the processor with the
370E feature (the address appearing
first in the QUERY PROC response).

Key in "begin" to continue.

System Action: System continues
operation in MP mode.
Operator Response: In order to vary
offline processor xx, a path to device
'rdev' from the other processor will have
to be brought online.

199E
All other users should notify the system
operator if the 370E feature. is still
needed. Otherwise, key in "begin" to
continue.

140

VM/SP System Messages and Codes

LAST PATH TO DEVICE rdev ON
PROCESSOR xx
Explanation: A VARY OFFLINE
PROCESSOR command has been issued
in a multiprocessing configuration; it is
being rejected because it would cause
the last online path to system-owned
device 'rdev' to be lost.

System Action: The user is placed in
console function mode.

Secondary user is not available

Command rejected; device rdev
pending offline
Explanation: A command has been
issued that would cause device 'rdev' to
be activated. The device is pending
offline due to a VARY OFFLINE PROC
command.

DMK
System Action: The command is
rejected.

he can issue the SHUTDOWN command
to allow users with the virtual = real
option to reclaim the area.

Operator Response: Reissue the
command, specifying a device that will
still be online when the VARY
OFFLINE PROC command completes.

200E

Virtual = Real area not available;
in use by {userid Isystem}

Note: System support personnel should
be notified that machine check record(s)
have been recorded that identify the
system's hardware malfunction.

Explanation: The virtual = real (V = R)
area is not available to the user logging
on because another user (identified in
the error message), or the system,
already has that area. The user logging
on is permitted to run as a virtual
machine without the use of the
virtual = real area.

Explanation: The virtual = real area is
not available to the user logging on
because:

User Response: If the priority of the
user logging on warrants the use of the
V = R area, the user now occupying the
area should log off. The user logging on
can then get the virtual = real area by
LOGOFF and LOGON or by issuing the
DEFINE STORAGE nnnnnk command.
However, if the area is in use by
SYSTEM, the V = R area has been
unlocked and is unavailable for V = R
use until the system is reloaded.

201E

Virtual = Real area not available;
damaged pages
Explanation: The virtual = real area is
not available to the user logging on.
Machine checks have occurred which
identified damaged pages within the
V = R area. The user logging on is
permitted to run as a standard virtual
machine without the use of the
virtual = real area.
User Response: Notify the system
operator that this message has occurred.
The system operator can issue the
UNLOCK VIRT = REAL command so
that CP can use the area for paging, or

Virtual = Real area not available;
insufficient storage

202E

•

The virtual = real area was not
generated at system generation time,
or

•

The virtual = real area is not large
enough to contain the virtual
machine size defined in the
directory for the user logging on.

User Response: If the virtual = real
area was not generated, no action can
be taken. Otherwise, issue the DEFINE
STORAGE command to redefine the
virtual machine storage size equal to or
smaller than the actual virtual = real
size that was generated.

203E

Virtual = Real area requires IPL
by device address
Explanation: A shared system or one
that uses discontiguous saved segments
cannot be loaded (via IPL) into a virtual
machine running in the virtual = real
area.
System Action: None.
User Response: Reissue the IPL
command, specifying the address of the
device on which a nonshared version of
the system resides.

Control Program (CP) Messages

141

DMK
204E

User Response: None required; the
Monitor is already active.

Invalid page(s) specified Virtual = Real area
Explanation: The user is attempting to
use the UNLOCK command to unlock
pages that are within the V = R region.

212E

Explanation: The MONITOR STOP
TAPE command was issued while
monitor data collection was not active.

System Action: Execution of the
command is terminated.
User Response: Reissue the UNLOCK
command with the VIRT = REAL
operand or specify pages not within the
V=R region.

System Action: Processing continues.
User Response: None required.

213E
206E

Monitor is not active

Cannot connect to host virtual
machine

Monitor CPTRACE is already
active
Explanation: The MONITOR START
CPTRACE command was issued while
the internal trace table was already
active.

Explanation: User attempted to
LOGON through a logical device to a
virtual machine that has created a
logical device, or to DIAL a logical
device to the host virtual machine that
created the logical device.

System Action: Processing continues.
User Response: None required.

System Action: The command is
ignored.
214E
User Response: DIAL or LOGON to a
valid virtual machine.

208E

Monitor CPTRACE is not active
Expl~nation:

The MONITOR STOP
CPTRACE command was issued when
the internal trace table was not active.

Printer rid not enabled
System Action: None.
Explanation: The resource specified
cannot be attached because it is not
enabled.
System Action: None.
User Response: Do a 'NET ENABLE
resource' or 'NET ENABLE ALL'.

211E

Monitor tape is already active
Explanation: The MONITOR START
TAPE command was issued while
monitor data collection was already
active.
System Action: Processing continues.

142

VM/SP System Messages and Codes

User Response: None required.

215E

Monitor active, DAST AP cannot
be enabled dynamically
Explanation: The MONITOR ENABLE
command was issued with the DAST AP
class when monitor data collection was
active.
System Action: None.
User Response: The DASTAP class
cannot be enabled dynamically. If the
DAST AP class is required, stop the
monit.or, enable the DASTAP class, and
then restart the monitor. Otherwise,

DMK
reissue the command without the
DAST AP class.

216E

2191

Explanation: An end-of-tape condition
has occurred on the monitor tape.

SYSPROF class is dependent on
schedule and DAST AP

System Action: Two tape marks are
written, the tape is rewound and
unloaded, and the tape drive is released.
Data collection stops and all classes are
disabled.

Explanation: The MONITOR ENABLE
command was issued with the SYSPROF
class, but without the SCHEDULE and
DAST AP classes.
System Action: None.

Operator Response: If you are not the
user who issued the MONITOR
command, consult with the person who
did. The user may want to mount
another tape. If so, reissue the
MONITOR ENABLE and MONITOR
START TAPE commands.

User Response: Both the SCHEDULE
and DASTAP classes must be specified
with the SYSPROF class.

217E

Monitor tape not started, no class
enabled
2201
Explanation: A MONITOR START
TAPE command was issued when no
classes of data collection were enabled.

System. Action: An attempt is made to
write a tape mark. The tape is released
and data collection stops.

User Response: Issue the MONITOR
ENABLE command specifying the
desired class or classes, and then reissue
the MONITOR START TAPE command.

Operator Response: If you are not the
user who issued the MONITOR START
command, consult with the person who
did. The user will probably want to
mount another tape. If so, reissue the
MONITOR ENABLE and MONITOR
ST ART TAPE commands.

Monitor not stopped, outstanding
I/O
Explanation: A MONITOR STOP
TAPE command was issued when the
data collector was attempting to recover
from an I/O error or was handling an
end-of-tape condition.

Error on monitor tape, monitor
stopped by system
Explanation: An uncorrectable I/O
error occurred on tape during data
collection.

System Action: The data collection
process is not started.

218E

End of monitor tape, monitor
stopped by system

221E

Monitor to spool is already active

System Action: The command is
rejected; however, the monitor tape is
stopped by the system because of either
the tape 1/0 error or the end-of-tape
condition.

Explanation: A MONITOR START
SPOOL command was issued when the
monitor was already running. It may
have started automatically according to
the SYSMON macro specifications in
DMKSYS.

User Response: None required.

System Action: None.
User Response: Review the current
automatic monitoring specifications in

Control Program (CP) Messages

143

DMK
DMKSYS as defined by the SYSMON
macro and make sure that they still
meet the daily monitoring needs.

222E

225E

Explanation: The userid specified is
not a valid userid in the system.
Monitor is not started.

TIME parameter specifies invalid
time

System Action: MONITOR is not
started.

Explanation: A MONITOR TIME
command was issued when the specified
start or stop time did not conform to the
required syntax.
Note: The stop time cannot be later
than midnight.

User Response: Reissue the command
with a valid userid.

226E

System Action: MONITOR automatic
start and stop times remain unchanged.

System Action: The automatic
monitoring start and stop times remain
unchanged.

Start tim.e must precede stop time
Explanation: The format of the start
and stop times, as issued in a
MONITOR TIME command, was
correct. However, the start time was
not earlier than the stop time.
Note: Stop time cannot be later than
midnight.
System Action: Monitor automatic
start and stop times remain the same.
User Response: Reissue the command.

224E

Limit must be between 10 and
50000
Explanation: A MONITOR LIMIT
command was issued sp8cifying a spool
file maximum record COUllt that was not
wi thin the allowed range.
System Action: Monitor automatic
spool file record count limit remains
unchanged.
User Response: Reissue the command
with the correct LIMIT specification.

144

VM/SP System Messages and Codes

'FOR' value spans midnight command invalid
Explanation: A MONITOR TIME FOR
command was issued specifying a period
of data collection that, when added to
the current time, will exceed midnight.

User Response: Review format of
MONITOR TIME command.

223E

Invalid monitor userid speciiied,
monitor not enabled.

User Response: Reissue the command
with a smaller FOR specification, or
manually start and stop the monitor as
needed.

227E

'FOR' option invalid with
AUTODISK off
Explanation: The MONITOR TIME
FOR command assumes that automatic
monitoring is in effect. (AUTO = YES
has been specified in the SYSMON
macro or the MONITOR AUTODISK
ON command has been issued.)
System Action: The TIME
specification is ignored and the
automatic monitoring start and stop
commands remain unchanged.
User Response: Issue a lVIONITOR
TIME command and reissue the
MONITOR TIME FOR command.

(

DMK
228E

'FOR' option inva.lid with monitor
on

231E

IPL TIO ERROR
Explanation: The IPL simulator
encountered an unexpected condition
code when executing a TEST I/O
instruction on the specified virtual
device.

Explanation: If monitoring is currently
active, data has already been collected
for some time. The MONITOR TIME
FOR command in effect says monitoring
should be started now and run for the
specified time. Therefore, the use of the
FOR option when monitoring is already
active would give performance data for
an unexpected period of time.

User Response: Verify that the device
is valid for IPL operation and that no
unexpected status conditions exist in
the device, and reissue the IPL
command.

System Action: Monitoring status is
unchanged.
232E
User Response: Review your
monitoring needs and resolve the
conflicts in your previous specifications.

2291

Explanation: During the IPL
simulation process, the specified IPL
device received an I/O interrupt with an
unit check condition.

User of monitor does not exist

User Response: Examine the CSW and
sense bytes to determine the possible
cause of the simulation failure. If no
equipment checks are present, reissue
the IPL command to the specified
device.

Explanation: The user of the monitor
specified in the SYSMON macro. does
not exist on this system.
System Action: The monitor is not
automatically started.
User Response: Check the specified
userid and start the monitor, using the
monitor commands, with the correct
userid.

230E

IPL SIO ERROR
Explanation: The START I/O
instruction for the initial IPL sequence
to the specified device received an
unexpected condition code, so the device
could not be properly started for the
IPL.
User Response: Verify that the device
type is valid for an IPL simclation and
that no unexpected status conditions
exist in the device, and reissue the IPL
command.

IPL UNIT ERROR; CSW = csw
SNS = sense

233E

IPL OVERLAY ERROR
Explanation: The IPL simulator was
about to perform a loading sequence
that would have overlaid the simulator
itself. In this particular case, the IPL
simulator cannot function in the
specified virtual machine at its current
storage size.
User Response: If VMSTOR is less
than 256K then increase the size of the
virtual machine so that the IPL
simulator will load in an area where it
will 110t be overlaid. Otherwise, correct
the system being loaded such that it
does not utilize address X'20000'. Then
reissue the IPL command.

Control Program (CP) Messages

145

DMK
234E

IPL SENSE ERROR

2371

Explanation: A unit check occurred on
the IPL device. A SENSE operation was
used to get the sense bytes and an
unusual condition occurred.

Explanation: CP was unable to
successfully issue an Assign CCW to a
3480 device during vary-on processing.
System Action: The device is marked
offline.

User Response: Verify that the device
is not malfunctioning and then reissue
the IPL command for the required
device.

2351

Device rdev varied online; unable
to establish a path group id for
channel path(s) rdev

Operator Response: Try to vary on
the device again.

2381

Explanation: CP successfully issued
Set Path Group ID CCW s to a 3480
device on some but not all channel
paths to the device. cuu represents the
channel path(s) that were
unsuccessfully grouped via the Set Path
Group ID CCW (e.g., 180, 280, 380)

Device rdev varied offline;
unassign failed
Explanation: CP was unable to
successfully issue an U nassign CCW to
a 3480 device during vary-off processing.
System Action: The device is marked
offline.
Operator Response: The device is
marked offline, but it may still be
assigned to the system. The operator
may have to physically unassign the
device to permit another system to
obtain assignment. Reloading the
control unit's microcode is one way to
cause the device to be unassigned. This
action will also cause all other devices
attached to the control unit to be
unassigned; it should not be done if
other devices are in use.

System Action: The failing channel
path(s) were marked offline.
Operator Response: The device has
been marked online even though not all
paths to the device are online. Try to
vary on the device again to bring the
failing paths online.

2361

Device rdev VARY failed; device
cannot be assigned

Device rdev VARY failed; unable
to establish a path group id for
device
2391
Explanation: CP was unable to
successfully issue Set Path Group ID
CCWs on all channel paths to a 3480
device during vary-on processing. 'rdev'
is the address of the device.
System Action: The device is marked
offline.
Operator Response: Try to vary on
the device again. If it cannot be varied
online, make sure it has been properly
system generated (e.g., a 3420 device has
not been generated as a 3480 device.)

146

VM/SP System Messages and Codes

Printer rdev drained; possible
FeB-forms mismatch
Explanation: The last file printed
contained an imbedded LOAD FCB
command. When the system FCB is
reloaded at the end of the print, there is
no assurance that the paper is still
aligned with the FCB.
This message is produced only if all of
the following conditions are true:
1.

The real printer is a 3211-type
device.

DMK
2.
3.

The printer was started with the
CFILEFCB option.
The last print file contained at least
one LOAD FCB command.

the CHANGE command) and release the
user hold. If the printer was drained,
ST ART the printer with a correct load
module (via the CHARS parameter on
the START command).

System Action: The printer has been
drained.
Printer rdev (3800), intervention
required, status code code

2421
User Response: Correct the forms
alignment, if necessary, and reissue the
ST ART command.

240E

)

Explanation: This message includes all
situations where the operator must
intervene in the 3800 printer's
operation. These situations include, but
are not limited to the following:

Printer rdev, FeB-forms
mismatch; fileid nnnn
{heldlpurged}

•
•
•
•

Explanation: There is a mismatch
between the forms control buffer (FCB)
and the forms in the 3800 printer.
System Action: Printing is held or
suspended. The file is held or purged.

End of forms
Stacker full
Toner supply empty
Replace developer

All relevant status codes are described
in the 3800 Reference Manual for the
3800 Printing Subsystem Model 1 and
the IBM 3800 Model 3 Printing
Subsystem Operator's Guide for the 3800
Printing Subsystem Model 3.

User Response: If held, specify correct
FCB and release the HOLD on the file.
If the file is purged, reenter the correct
matching information.

System Action: Printing is suspended.
241E

Printer rdev, invalid load module
mmmm specified, file nnnn
{heldlpurged}

Operator Response: Correct the
printer condition by examining the
status code or indicators on the printer.
Correct the condition and press the
RESET and READY buttons on the 3800
printer.

Explanation: An invalid load module
has been specified and the 3800 printer
file may be HELD or PURGED.
System Action: If an invalid load
module was detected in the body of the
print file, the file will be placed in a
user hold (or, if the PURGE option of
the START command was specified, the
file will be purged). If an invalid load
module was detected in a separator
page, the print file is not held or purged,
and the printer is drained.
Operator Response: If the file was
held, specify a correct load module (via

243E

FLASH missing or invalid
Explanation: For 3800 printer
operations, the FLASH operand in the
CP SPOOL or CHANGE command is
missing or invalid.
System Action: None.
User Response: Reissue the command
with a va.lid FLASH specification.

Control Program (CP) Messages

147

DMK
244E

245E

Image library missing or invalid

248E

SPECIFIED IM'AG E imagelib
NON-EXISTENT

Explanation: For 3800 printer
operations, the IMAGE operand in the
ST ART command is missing or invalid.

Explanation: The specified 'imagelib
TEXT' file was not found.

System Action: None.

User Response: Reissue the command
with a valid IMAGE specification.

User Response: Correct the erroneous
'imagelib TEXT' file and reissue the
command.

CHARS missing or invalid
ERROR LOADING IMAGE
imagelib

249E

246E

Explanation: For 3800 printer
operations, the CHARS operand in the
CP SPOOL, CHANGE, or START
command is missing or invalid.

Explanation: The 'imagelib TEXT' file
caused a LOAD error.

System Action: None.

User Response: Reissue the command
with a valid CHARS specification.

User Response: Correct the problem
that caused the LOAD error and reissue
the command.

FCB missing or invalid
370E feature is not available [on
processor xx]

250E
Explanation: For 3800 printer
operations, the FCB operand in the CP
SPOOL, CHANGE, or START command
is missing or invalid.
System Action: None.
User Response: Reissue the command
with a valid FCB specification.

Explanation: System/370 Extended
feature or the Extended facility is not
installed on the processor, or the user is
not in EC mode.
•

•
2471

3800 NAMED IMAGE imagelih
CREATED
Explanation: The data has been
successfully placed in the specified
image library.

System Action: Normal processing
continues.

System Action: None.

User Response: None.

148

•

The 370E parameter was indicated
in the user's directory via an
OPTION control statement.
A SET S370E ON command was
issued.
A SET 370E ON command was
issued.

VM/SP System Messages and Codes

DMK
251E

370E feature is not active
Explanation: The System/370 Extended
feature of the Extended facility feature
is installed on the processor. However,
the 370E feature is not enabled for
virtual machines.

ERROR SAVING imagelib; RC
nn

254E

Explanation: An error occurred while
saving the named image library.
Code Reason
The named system was not found.
The named system is currently
8
active.
The volume for the named system
12
is not CP-owned.
The volid is not mounted.
16
The size of the imagelib being
20
generated is too large for the
named system.
24
Paging error occurred while
processing this request.
4

System Action: The feature is enabled
for the virtual machine. However, CP
will not support 370E until a SET S370E
ON command is issued.
User Response: Notify a class A user
in order that a SET S370E ON command
can be issued.

2521

Printer rdev, file nnnn requeued
and held
Explanation: An error occurred on a
3800 printer which caused pages to be
lost; print files are requeued.

User Response:

System Action: The spool file is
removed from the delayed purge queue
and placed in the print queue with a
system hold.

Use another named system that
has been generated.

DRAIN any 3800 printers that are
using the named system and
reissue the command.

Check with the installation
manager to find out why the
volume is not CP-owned.

Have the correct volid mounted
and reissue the command.

Make the image smaller or put it
into a larger named system.

Check the named system to
determine that it is defined in
DMKSNT and that the cylinder
actually exists on the volume.
Also verify that it has been
previously formatted by CPo
Reissue the command. If the
problem persists, see your IBM
support personnel.

Operator Response: Examine the
output to see if file 'nnnn' printed
correctly; if this file needs to be
reprinted, remove the hold. Then
START the printer.

253E

System Action: None.

Code Explanation

MODIFY missing or invalid
Explanation: For 3800 printer
operations, the MODIFY operand in the
CP SPOOL or CHANGE command line
is missing or invalid.
System Action: None.
User Response: Reissue the command
with a valid MODIFY specification.

Control Program (CP) Messages

149

DMK
255W

370E feature now disabled

2581

Explanation: A class A user has issued
a SET 370E OFF command to disable
the 370E feature, or the system operator
has varied the processor with the 370E
feature offline.

All 3800 data checks will be
reflected
Explanation: The DATCK option of
the CP DEFINE command is used to
define a virtual 3800 printer.
System Action: None.

System Action: All 370E users will
enter console function mode on receipt
of the message.
User Response: Await availability of
the 370E feature. Attempts to continue
will result in the user being dispatched
without the 370E capability.

User Response: None. This message is
used to alert the user that a high
overhead simulation of virtual 3800
printer will be used.

259E

Note: If the 370E feature is no longer
needed, key in "begin" to continue.

256E

SIZE parameters missing or
invalid
Explanation: The SIZE keyword is
specified and the parameters are either
not specified or not valid 3800 printer
SIzes.

INSUFFICIENT VIRTUAL
STORAGE

System Action: None.
Explanation: The defined virtual
storage is insufficient.

User Response: Respecify the SIZE
parameters correctly.

System Action: None.
User Response: Define a larger virtual
machine, IPL CMS again and reissue
the command.

257E

RESIDUAL BYTE COUNT =
xxxxxxxx (HEX)
Explanation: This message is preceded
by message DMKNMT254E and is
issued when the return code in message
DMKNMT254E equals 20.
System Action: None.
User Response: Either define the
named system with a larger byte count
or decrease the imagelib byte count.

150

VM/SP System Messages and Codes

270E

Printer xxx, too many WCGMs
needed for 'CHARS', file nnnn
{held\purged}
Explanation: The collection of
character arrangement tables specified
in the spool file 'CHARS' requires more
WCGMs to be loaded than are available
for the 3800 Printing Subsystem.
System Action: Printing is held or
suspended. The file is held or purged.
User Response: If held, specify correct
'CHARS' and release the HOLD on the
file. If the file is purged, reenter the
correct information.

DMK
2721

User Response: None.

Printer rdev, 3800 IML occurred
Explanation: A 3800 Printing
Subsystem equipment check caused an
automatic IML (initial microprogram
load) or the 3800 Printing Subsystem
Model 3 was manually IMLed. The page
buffer contents are destroyed and the
page counters are reset. The backup
page count cannot be determined.

276E

Explanation: The DEFINE command
was issued and the rdev was not a 3330V
volume.
System Action: No action is taken and
processing continues.

System Action: The spool file is
requeued.
Operator Response: See message
DMK252I.

273E

rdev not a 3330V

User Response: None.

277E

Error demounting volume valid
Explanation: CP attempted to demount
a 3330V volume, but MSS encountered
an error.

DETACH rejected; virtual
machine tracing I/O

System Action: The volume is not
demounted and processing continues.

Explanation: A DETACH command
was issued while the virtual machine
was tracing I/O.

User Response: None.
System Action: The DETACH is
rejected and tracing continues.
278E
User Response: Issue 'TRACE END'
and reissue the DETACH.

274E

Device rdev not a DASD
Explanation: The device specified in
the DEFINE command is not a valid
DASD volume.

rdev has a mounted volume; MSS
task not available to demount it

System Action: Processing continues.
User Response: Reissue the DEFINE
command with a valid DASD.

Explanation: There is a 3330V volume
mounted on the rdev. The MSS
communicator is not active and the
volume cannot be demounted.
279E

DASD rdev not a VUA

System Action: Processing continues.
User Response: None.

275E

rdev already SYSVIRT

Explanation: The rdev is already
defined as a SYSVIRT 3~330V device.

Explanation: The DASD volume
specified in the DEFINE command was
not a valid MSS device.
System Action: Processing is
terminated.
User Response: Reissue the DEFINE
command with a valid MSS device.

System Action: The status remains
unchanged and the processing
continues.

Control Program (CP) Messages

151

DMK
280E

rdev already virtual

System Action: The DETACH is
rejected and processing continues.

Explanation: The rdev is already
defined as a VIRTUAL feature.

User Response: Reissue the command;
if above message is consistently
recei ved, inform your system
programmer that the user specified is
hung in logoff/force processing.

System Action: The status remains
unchanged and the processing
continues.
User Response: None.
2871
281E

MSS volume volid not linked;
demount in progress, retry

Printer rdev; page buffer
destroyed, backup page count
nnn
Explanation: The page buffer has been
destroyed on the 3800 printer.

Explanation: Volume dsklab has been
selected for demount and cannot be
linked at this time.

System Action: Printing is suspended.

System Action: None.

Operator Response: See message
DMKRSE252I.

User Response: Reissue the link
command.
288E
285E

LOGON from the initial screen
was unsuccessful

userid logging on, try again later

Explanation: Data was entered only in
the PASSWORD field on the logo screen
or the USERID was entered with one or
more blanks.

Explanation: A DETACH command
was issued by a class B user with the
'FROM userid' option. The userid
specified is currently in logon
processing.

User Response: Log on specifying
USERID and PASSWORD.

System Action: The DETACH is
rejected and processing continues.
!

User Response: Reissue the command;
if above message is consistently
received, inform your system
programmer that the user specified is
hung in logon processing.

286E

userid vdev NOT LINKED;
REQUEST DENIED
Explanation: The link to the user's
virtual device has not been
accomplished because the user is
unauthorized to issue a LINK to that
particular virtual device.

use rid logging ofi, try again later

Explanation: A DETACH command
was issued by a class B user with the
'FROM userid' option. The userid
specified is currently in logoff or force
processing.

152

298E

VMjSP System Messages and Codes

System Action: Execution of the
command is terminated.
User Response: Obtain the appropriate
authorization and reissue the LINK
command.

DMK
300E

Save request beyond virtual
machine size
Explanation: When the SA VESYS
command was issued, one or more
designated saved pages were in the
SYSPGNM operand of the NAMESYS
macro. These pages are beyond the size
of the virtual machine used.

TRAPRED is stopped.
User Response: Error is most likely
due to manipulating the reader files
since TRAPRED started.

303E

Explanation~ A condition code 2 was
encountered while attempting a
DIAGNOSE code X'14' operation
against a reader file.

User Response: Check the numbers of
the pages designated to be saved in the
N AMESYS macro. If they are correct,
increase the size of the virtual machine
before reissuing the SAVESYS
command.

System Action: TRAPRED is stopped.
User Response: The error is likely due
to manipulating the reader files since
TRAPRED started.

Requested file is not a CPTRAP
file

301E

Explanation: The requested file exists,
but it is not a CPTRAP file.

rdeu reader file not locatable

304E

CPTRAP is stopping, no input
allowed

System Action: The command is
ignored, TRAPRED has not been
started.

Explanation: The CPTRAP facility
was stopping when a CPTRAP command
was received.

User Response: Reissue a correct
command.

System Action: The total command
line is ignored.
User Response: Wait until CPTRAP
has stopped, then begin a new CPTRAP
run.

I/O error on OOC - message

302E

Explanation: 'message' can be one of
the following:
3051
•
•
•
•

device address invalid
device type invalid
device busy, not ready, or real
paging error on spool

A condition code 3 was received while
attempting a DIAGNOSE code X'14'
operation against a reader file: the
result of an IIO error, or the reader
changed status since TRAPRED was
started.

{CPTRAP selectivity
resetlTRAPRED SELECTIVITY
RESET}
Explanation: A (CPTRAP/TRAPRED)
subcommand redefined some existing
selectivity for typenum.
System Action: None. The new
selectivity is in force.
User Response: None. This message is
for information only.

System Action: RC = 3.

Control Program (CP) Messages

153

DMK
306E

first and only buffer in the CPTRAP
SPOOL file, then the CPTRAP SPOOL
file is not saved for a system warm start.

CPTRAP is already active
Explanation: CPTRAP allows only one
user at a time. This message is sent to a
second user who attempts to start
CPTRAP.

User Response: Results are unreliable.
This file may not have the information
you want. Start over with greater
selectivity of input.

System Action: The total command
line is ignored.
User Response: Wait until CPTRAP is
available.

3071

System Action: None. CPTRAP
continues without the data.
User Response: The data was not
included in the file. Start over with the
in-error interface corrected.

CPTRAP data lost
Explanation: The CPTRAP facility has
lost some data (not added it to the
output file) due to the buffers being full
or due to an I/O errol' during system
shutdown.
System Action: None. CPTRAP
continues without the data. For
message DMKCKP308I, if the I/O errol'
occurs while attempting to write the

154

VM/SP System Messages and Codes

Operand ignored; select table full
Explanation: The select table can
expand to allow 400 entries. This
request is for the 401st; it is not
accepted.

CPTRAP {CPlvirtual} code
interface data ignored
Explanation: The CPTRAP facility
received a CP or virtual machine
interface request with the data field
outside of either the virtual machine's
storage for a VIRTUAL interface, or the
real storage for a CP interface request.
The identifier will be CP code or
VIR1'UAL code; CP indicates that the
in-error interface was from CP, and
VIRTU AL indicates that the in-error
interface was from a virtual machine.
'code' is the individualizing CODE from
the interface parameter list.

3081

309E

System Action: The preceding
operands are accepted, but not the
in-error operand or any following
operands.
User Response: Either do not add any
more selectivity, or delete some and
then add more selectivity.

310E

Date date invalid; not changed
Explanation: The system date in CP
low storage contains invalid data and
hence cannot be updated for the
midnight date change. The invalid date
indicates a possible software system
failure since the date is automatically
set by the system initialization routine.
System Action: The date in low
storage is not changed; however, the
day of the week is changed and the
clocks are set to change the date at
midnight in 24 hours.
Operator Response: Contact the
system programmer at once. Careful
use of the STCP command can correct
the date 8Ct in storage. Notify IBM
software support personnel of the
problem and supply a dump of CP
storage if possible.

DMK
31lE

Maximum number of trace
elements exceeded
Explanation: The processing of this
PER command would cause more than
255 trace elements to exist for this user.
This message will be issued if the
intermediate processing of the trace
elements would require more than 255
trace elements to exist even if the end
result would be less than 255 elements.

3
4
5

User Response: No user error is
involved. You can reissue PER
commands, but all previous tracesets are
lost.

314W

System Action: The command is not
processed.

PER failure - code n, userid userid
Explanation: This message is issued to
the operator to indicate that some of the
storage used for the PER control blocks
cannot be returned to the system
because the pointers to those control
blocks have been lost. This storage is
lost to the system until the system is
re-IPLed.

User Response: Turn off some of the
existing trace elements and reissue the
command.

312E

Missing PERBLOK
Missing PEXBLOK
Missing TRACEBACK table

More than {8 rangesll PASSII
STEP} specified on a command
line

System Action: The PER trace for the
user involved is ended. As many PER
control blocks as possible will be
released. The values for the PER codes
are as follows:

Explanation: More RANGE, PASS, or
STEP options than are allowed have
been specified on a single PER
command line.

Code Meaning

System Action: The command is not
processed.

2
3

User Response: Reenter the command
line with a valid number of RANGE,
PASS, or STEP options.

Invalid PEXBLOK
Missing register save area
Missing PERBLOK
Missing PEXBLOK
Missing TRACEBACK table

User Response: Contact system
support personnel.
313E

PER failure - code n
Explanation: One or more of the
control blocks needed for PER can no
longer be found.
System Action: This message is sent
to the user. PER TRACE for the user is
ended. As many PER control blocks as
possible will be released. The values for
the PER codes are as follows:
Code Meaning
1
2

Invalid PEXBLOK
Missing register save area

316E

Command rejected;
LOGMSG/DUMP being updated
Explanation: The SET
LOGMSG/DUMP function cannot be
updated because a previous
LOGMSG/SET DUMP update is in
progress.
System Action: SET LOGMSG/DUMP
is not updated. The SET
LOGMSG/DUMP processor will not
allow parallel SET LOGMSG/DUMP
request.

Control Program (CP) Messages

155

DMK

317E

User Response: Retry the rejected SET
LOGMSG/DUMP request.

•
•

Operator Response: None.

System Action: The device is placed in
offline status, and system operation
continues.

CPTRAP terminated due to 1/0
error

Operator Response: Correct the
device type code in the RDEVICE macro
of DMKRIO so that it matches the
actual device type. Then rebuild the CP
nucleus and re-IPL.

Explanation: An error was
encountered while either reading in or
writing out a CPTRAP record.
System Action: CPTRAP terminates
and the existing spool file is closed and
checkpoin ted.
User Response: Reissue the command.

VARY failed
Device not mounted

331E

vdev not
{defined Iattached Ilinked Icreated}
- use a {sharedlnon-shared} VCU
instead

If the problem persists, there is a

possible hardware error. Call your
system support personnel for assistance.

329E

rdev improperly genned, device
cannot be used as SYSOWN

Explanation: The device type code
generated in the RDEVICE macro of
DMKRIO does not match the actual
code obtained from the RDC data.
System Action: System operation
continues, but the device is rejected for
system use.
Operator Response: To use the device
as SYSOWN, correct the DEVTYPE
operand in the RDEVICE macro of
DMKRIO so that it matches the actual
device type. Then rebuild the CP
nucleus and re-IPL.

Explanation: The requested device
cannot be created because the virtual
control unit (VCU) is already in use
with a conflicting subchannel protocol
(SHARED or NONSHARED). You can
only mix SHARED and NONSHARED
devices on the same VCU if the
VCUNOSHR option is present on the
directory OPTION statement.
vdev

- the virtual address intended
for the device.

process - the process that failed, it
could be one of the following:
1.

2.
3.
4.

330E

Message; Mismatched device types
at address rdev

Explanation: The device type code
generated .in the RDEVICE macro of
DMKRIO does not match the actual
code obtained from the RDC data.
The message issued is one of the
following:

156

VM/SP System Messages and Codes

ATTACHED for the
ATTACH or NETWORK
ATTACH command.
DEFINED for the DEFINE
command
LINKED for the LINK
command
CREATED for most
LOGO N processing

vcutype - the VCU protocol needed for
device 'vdev'. It is one of the
following:
1.

SHARED~ where a shared
subchannel is required
NONSHARED, where
nonshared subchannels are
required

DMK
System Action: As indicated in the
message, device 'vdev' is not created. If
the device was being moved (DEFINE
vdevl AS vdev2), then the device still
exists at its original address.

350W

Explanation: The volume label on the
pack mounted on drive rdev does not
agree with the volume label specified
during system generation.

User Response~ Your action should
depend upon the circumstances of the
error.
•

•

System Action: The system enters a
wait state (wait state code = 010).

LOGON PROCESSING - If this
message appears during LOGON,
the failing command is located in
your user directory entry. Inform
your system administrator of this
problem. Your system administrator
should then correct the CP directory
entry for your virtual machine.
COMMAND PROCESSING - If this
message appears in response to a CP
command (ATTACH, DEFINE,
LINK, NETWORK ATTACH) that
you have entered you must: (1)
select another device address for
this virtual device, or (2) detach all
other devices from the virtual
control unit and reissue the failing
command.

The virtual control unit (VCU) is
available for use in either mode
(SHARED or NONSHARED) until a
device is created. At this point the
VCU is defined as SHARED or
NONSHARED (to match the attached
device) and only those devices that use
the same protocol may be added to the
VCU. If all devices are removed from
the VCU, it is once again available for
use in either mode. If a particular
configuration is needed and your
application does not require SHARED
subchannel simulation, the VCUNOSHR
option can be used to prevent the
subchannel protocol conflict.
Refer to Appendix A in the VMjSP
Planning Guide and Reference for the
list of devices and protocol.

DASD rdev SYSRES VOLID NOT
VOLID

User Response: Check the SYSRES
macro in module DMKSYS to ensure
that the disk address and volume label
specified are valid.
Operator Response: Ensure that the
correct volume is mounted on disk drive
rdev and present an external interrupt
to initiate a retry of the operation.

351W

DASD rdev SYSRES NOT READY
Explanation: The disk drive specified
by rdev is not ready. Disk rdev was
specified as the SYSRES device in the
SYSRES macro in module DMKSYS.
System Action: The system enters a
wait state (wait state code = 010).
Operator Response: Make the device
ready and present an external interrupt
to initiate a retry of the operation.

352W

FATAL DASD I/O ERROR
Explanation: The system nucleus
cannot be written. Probable causes are:
•
•
•
•

The disk pack is not formatted
properly.
The disk pack is defective.
A disk hardware error has occurred.
The disk is in read-only mode.

System Action: The system enters a
wait state (wait state code = 011).

Operator Response: Use the FORMAT
program to reformat the pack. Attempt

Cont.rol Program (CP) Messages

157

DMK
to do a new system load. If the trouble
persists, try another pack on a different
drive. If the trouble still persists, call
IBM for hardware support. Obtain the
contents of general registers 0, 1, 3, 4, 5,
11, 13, 14, and 15.

353W

Requested language langidl is
unavailable. Language langid2
set. RC=rc
Explanation: You have the language
langidl specified in your directory
entry, but CP cannot get access to the
message repository for this language.

SYSRES DEVICE TYPE INVALID
Explanation: The device type specified
in the SYSRES macro in module
DMKSYS is not valid for system
residence.
System Action: The system enters a
wait state (wait sta.te code = 011).
User Response: Verify that the
operands specified in the SYSRES
macro in module DMKSYS define valid
system residence device characteristics.

361E

365E

System Action: The system sets the
installation default language (langid2)
for the user.
User Response: This is an installation
error. Notify the system administrator
and specify the return code that was
issued with this message. The return
code indicates the specific problem that
occurred:
X'4'

The DMKSNT entry for the
language specified does not
exist. The system
programmer must specify the
appropriate NAMELANG
macro in DMKSNT for this
language.

X'8'

The volid specified in the
DMKSNT entry for the
language is not a CP-owned
volume. The system
programmer must ensure a
CP-owned volume is specified
in the DMKSNT entry
generated by the
NAMELANG macro for this
language.

X'C'

The volid specified in the
DMKSNT entry for the
language is not mounted.
The system operator must
ensure that the appropriate
volume is mounted.

X'14'

A paging error occurred
during the set operation.

X'lC'

The DMKSNT entry for the
language was found; however,
the langid in this DMKSNT
entry does not match the
1angid in the saved message

LOGOFF/FORCE pending for user
userid
Explanation: One of the following CP
Commands was issued for a virtual
machine that is in the process of logging
off:
AUTOLOG
. FORCE
LOGON
QUERY
QUERY USER
System Action: The command ends
and no further processing takes place.
User Response: If the QUERY or
FORCE command was issued, no user
action is required. The message
indicates that the 'userid' in question is
in the process of logging off.
If the LOGON or AUTOLOG command
was issued, wait until VM/SP finishes
logging off the specified 'userid' and
then try to issue the command again.
This process can take anywhere from a
few seconds to a few minutes.

158

VM/SP System Messages and Codes

DMK
repository. The system
programmer must ensure that
the NAMELANG entries do
not specify overlapping areas
on DASD.

X'20'

X'24'

4001

a reader backlog exists, users should be
requested to read their files. In
addition, you may be able to determine
other spool file that can be selectively
purged. SPT APE could be used to dump
and restore spool files and reduce
system load. Logging off inactive users
reduces temporary disk space usage.

The "MSGREP" identifier
was not found on the first
page of the requested
message repository. CP looks
for this identifier to
determine if a valid message
repository is saved. The
system programmer must save
the appropriate CP message
repository.
No more virtual page buffers
are available.

User Response: If the message resulted
from processing a VMDUMP command,
purge unwanted dumps on the user
reader queue and retry. If still
unsuccessful, request the system
programmer to free temporary disk
space.

4011

System {temp spacelcheckpoint
area} full

Explanation: Ninety percent of all
temporary disk cylinders (TEMP
SPACE) is in use. Ninety percent of all
checkpoint space (CHECKPOINT
AREA) is in use.

Explanation: All temporary disk
cylinders indicate in use (TEMP
SPACE). All checkpoint space
(CHECKPOINT AREA) is in use.

System Action: System operation
continues.

System Action: When paging is
required, the system will first examine
the preferred paging area. If preferred
paging area is full, the system will use
temp space, if temp space is full the
system may be unable to continue and
reIPL will be required. If the request is
for spooling space, the system attempts
to continue but performance is severely
degraded. If temporary disk space
becomes full while putting VMDUMP
pages out to temporary space, the dump
is purged.
If the checkpoint area is full, the system
continues without checkpointing. U~ers
attempting to create spool files will
have their virtual spooling device made
"not ready."

Operator Response: Review temporary
and page space allocations. Review
system usage and take steps to reduce
the system load. Spool files should be
reviewed. Additional printers may be
started to reduce print spool backlog; if

System {temp spacelcheckpoint
area} 90 percent full

Operator Response: Review system
usage and take steps to reduce the
system load. Spool files should be
reviewed. Additional printers may be
started to reduce print spool backlog. If
a reader backlog exists, users should be
requested to read their files. In
addition, you may be able to determine
other spool files that can be selectively
purged. Logging off inactive users
reduces space usage.

410W

CP ENTERED; PAGING ERROR
Explanation: An I/O error occurred
during paging. Probable hardware
error.
System Action: System operation
continues. The virtual machine enters
CP command mode. If the virtual
machine was running disconnected, it is
logged off the system.

Control Program (CP) Messages

159

DMK
User Response: Reload the virtual
system to continue. If the problem
persists, notify the system operator.

411W

420E

Explanation: An unauthorized user
has attempted to issue the CP SET
SVCACCL command. To invoke the
SVCACCL support for IX/370 systems
running under VM/SP, the SVCACCL
paremeter must be included in the
OPTION control statement for the
specified virtual machine.

CP ENTERED; TRANSLATION
EXCEPTION WHILE IN NON-EC
MODE
Explanation: While running a EC
mode virtual machine, a translation
exception occurred. Probable CP error.

415E

User Response: Insert the SVCACCL
parameter of the OPTION control
statement in the directory and reissue
the CP SET SVCACCL ON command.

424E

CONTINUOUS PAGING ERRORS
FROM DASD rdev

System Action: If the error was
encountered while reading, no change
has resulted from the user's previous
TAG command. !f the error was
encountered while writing, the results
are unpredictable.

System Action: The system enters a
disabled wait state (wait state code =
OOF).

VM/SP System Messages and Codes

(
~

User Response: Reissue the command.
If the problem persists, regenerate the
spool file that is in error or call your
system support personnel.

425E

I/O error on spool device during
accounting
Explanation: A spooling I/O error
occurred while the system was writing
accounting data to the spooling device.
System Action: If the accounting
spool file has been previously
checkpointed, the file is closed and a

160

Reader file spool error; file
unchanged
Explanation: A paging I/O error
occurred while reading or writing a
spool file record on a CP spooling
device, for the purpose of querying or
updating TAG information associated
with that spool file.

Explanation: Unrecoverable errors are
being received from the paging device
(rdev). This condition is caused by
failure of either the paging volume or
the paging device. This condition can
occur if the paging volum~ has not been
formatted properly.

Operator Response: Along with the
System Programmer, try to determine
whether the errors are being caused by
the paging device or by the paging
volume. If the device is failing, disable
it and reload (via IPL) the system; call
IBM for hardware support. If the
volume is failing, try reformatting it. If
the error condition recurs, discontinue
using that volume and call your system
support personnel.

System Action: The system continues
without enabling SVCACCL.

System Action: System operation
continues. The virtual machine enters
CP command mode. If the virtual
machine was running disconnected, it is
logged off the system.
User Response: Reload the virtual
system to continue. If the problem
persists, notify IBM support personnel.

No SVCACCL specified in
directory

DMK
new file started. Otherwise, the file is
written using a different spool page.

check condition is returned to the
virtual machine, the virtual device is
made not ready, and the system
continues.

User Response: The closed accounting
spool file should be processed. If the I/O
error persists, call your system support
personnel.

426E

User Response: Inform the system
operator. An attempt must be made to
reduce the paging and spooling load on
the system as soon as possible. When
spool space is available, issue the
SPOOL CONSOLE START command to
resume console spooling, or issue the
READY command to resume printer or
punch spooling.

{ReaderITape} rdev system spool
space full; file purged
Explanation: System input spooling
space for the reader or tape at real
device address rdev is full.
System Action: The file just read is
purged and system operation continues.
Operator Response: Review system
usage and take steps to reduce the
system load. Inactive users should be
logged off the system. Spool files should
be reviewed. Additional printers may be
started to reduce print spool backlog. If
a reader backlog exists, request that
users read their files. In addition, you
may be able to determine other spool
files that can be selectively purged.
After reducing spool file usage, read the
file again.

428E

{PrinterIPunchIReaderITape} rdev
spool error; file {heldlpurged}
Explanation: A paging I/O error
occurred on the device at real address
rdev. This message indicates a DASD
error if it was issued from DMKSPS
while dumping or loading spool files to
or from tape.
System Action: If the file that was
being processed at the time the I/O error
occurred is a printer or punch file, the
file is put in HOLD status and system
operation continues.
If the file is a reader file, it is purged.

4271

{ConsoleIPrinterIPunch} vdev
system spool space full; file closed
Explanation: System spooling space on
the device at virtual device address vdev
is full. If the message refers to the
console, the console spool file has been
closed. If it refers to the printer or
punch, the printer or punch output file
has been closed.
System Action: If the console spool
file is closed, virtual console spooling
stops. The virtual machine continues to
execute but without console spooling.

Operator Response: If the file is a
printer or punch file, try to print or
punch it again when spooling activity
on the printer or punch is low. The
system operator must first take the file
out of HOLD status.
If the file is a reader file, reload the file

in the reader and retry.
If the file is a tape file, reposition the
tape and reissue the command.
If the problem persists, call your system

support personnel.
If the printer or punch output file is

closed, an intervention-required unit

Control Program (CP) Messages

161

DMK
4291

{Console IPrinter IPunch IReader}
vdev spool error; file {heldlpurged}

430A

{PrinterIPunch} rdev fatal I/O
error; now offline, file held

Explanation: A paging I/O error
occurred on the device at virtual
address vdev.

Explanation: An unrecoverable I/O
error occurred on the printer or punch
device at real address rdev.

System Action: If it is a console spool
file error, virtual console spooling stops.
The virtual machine continues to
execute but without console spooling.

System Action: The failing device is
varied offline, the file being processed is
put in hold status, and system operation
continues.

If it is a printer or punch spool file
error, a unit check condition is sent to
the virtual machine to stop the write
operation, the file is purged, and the
virtual device is made not ready.

Operator Response: Vary the device
rdev online and restart. To process the
file that failed, take the file out of hold
status. If the problem persists, call your
system support personnel.

If it is a reader file spool error, a unit
check condition is sent to the virtual
machine to stop the read operation. The
file is held. System operation then
continues.

431A

Explanation: The card just read in the
reader at real device address rdev was
not a valid ID card. Two formats are
acceptable:

User Response: For a console file,
issue a SPOOL CONSOLE START
command and retry the output
operation. After ten unsuccessful
retries, the entire opened spool file is
purged.

•
•

ID userid
USERID userid

Separator or blank cards are accepted
before an ID card; any other card
preceding the ID card is invalid.

For a printer or punch file, issue the
READY command to the virtual device
and retry the output operation.

Operator Response: Run out the cards
in reader rdev, correct the ID card
error, and make the reader ready with
the corrected deck in the hopper.

For a reader file, try again to read the
file.
In any case, if the problem persists,
inform the system operator of the
incident. The error is probably due to a
hardware malfunction. The system
operator may advise you to purge the
file or may decide to turn the machine
over to your system support personnel,
depending on the impact of the problem.

Reader rdev id card missing or
invalid

432A

Reader rdev id card; userid not in
CP directory
Explanation: The 'userid' specified on
an ID card in the reader at real device
address rdev is not in the directory.
System Action: System operation
continues.
Operator Response: Run out the cards
in reader rdev, correct the ID card
error, and make the reader ready with
the corrected deck in the hopper.

162

VMjSP System Messages and Codes

DMK
If the ID card appears valid, check with
the system programmer to determine
wny the userid does not exist in the
directory.

433A

435E

Explanation: A paging error occurred
while writing the system to be saved, or
the 3704/3705 control program image to
be saved, to a DASD volume.

Reader rdev id card; invalid data data

Note: The SA VESYS command requires
that the DCSS being saved is not
attached to or IPL'd by the virtual
machine. This error may also occur if
you are running with a previously saved
DCSS and attempt to save the system.

Explanation: The class specified on
the ID card in the reader at real device
address rdev is incorrect or the name
specified is invalid. The 'data' is the
information in error on the ID card. If
a class is specified, it must be one
character, A through Z or 0 through 9.
If no class is specified, the default is A.
If a name is specified, it must be a 1- to
8-character filename and a 1- to
8-character filetype, or a 1- to
24-character data set name. The fields
of the ID card are free form as follows:

System Action: Execution of the
command terminates. The system or
control program image is not saved.
User Response: Be sure you entered
the correct command -- e.g.,
IPL nnn
SAVESYS eMS

ID userid .. CLASS n NAME filename
filetype

where

System Action: System operation
continues.

nnn

Operator Response: Run out the cards
in reader rdev, correct the ID card
error, and make the reader ready with
the corrected deck in the hopper.

434A

System Action: System operation
continues.
Operator Response: Run out the cards
in reader rdev, make sure the first card
is a valid ID card, and make the reader
ready.
If the problem persists, call your system
support personnel.

is the 3-digit virtual address of
the disk that contains the CMS
system you created.

Try the command again, since the
situation that caused the error may
have been temporary. If the problem
recurs, check the DASD space allocated
to receive the saved system or control
program image. This space must be
formatted with the CP format program
(DMKFMT) and allocated as PERM
space.

Reader rdev fatal I/O error; file
purged
Explanation: An unrecoverable I/O
error was encountered on the reader at
real device address rdev. The input file
was purged.

Paging error writing saved
system

436E

INTERRUPT PENDING. TO
PROCEED, TYPE YES, TO END
TYPE NO.
Explanation: In processing the
SA VESYS command, the system
detected that an I/O interrupt is
pending.
System Action: If you enter YES, the
SA VESYS command continues to save
t.he system but the pending I/O

Control Program (CP) Messages

163

DMK

437E

interrupt(s) are lost. If you enter NO,
SAVESYS processing terminates.

than 2000 unique spool file IDs
available.

User Response: Enter YES or NO.

System Action: Checkpointing
continues but no spool files are created.
Users attempting to create spool files
will have their spooling device made
"not ready."

System paging space not
available, IPL terminated
Explanation: The IPL command
attempted to get a DASD page but none
was available.
System Action: The command is
termina ted.

Operator Response: Purge or process
existing spool and warn users not to
create spool files.

441E

User Response: Verify that the proper
volumes required for paging and
spooling are mounted. Reissue the
command.

438E

4391

System Action: The command is
ignored.
User Response: Wait for a few seconds
and reissue the BACKSPAC command.

450W

CP entered; disabled wait PSW
psw

System Action: The control program
command that initiated the MSS request
will produce a message to indicate the
eventual result of the MSS error.

Explanation: The virtual machine
loaded a disabled wait PSW, identified
by'psw'.

User Response: Contact the system
operator to ensure that action is
underway to correct the MSS error.
Reissue the command when the error
has been corrected.

System Action: System operation
continues. The virtual machine enters
console function mode. If the virtual
machine was running disconnected, it is
logged off the system.

Spool fileid limit exceeded
Explanation: All the unique spool file
IDs in the system are assigned. The
maximum amount of unique spool file
IDs is the lesser of either the 9900
system limit or when all the checkpoint
slots are taken. For example, if the
checkpoint cylinder number is equal to
one (1) for a 3330, there are slightly less

164

Explanation: A BACKSPAC command
has been entered for a specific unit
record output device before the previous
BACKSPAC command for the same
dev~ce has finished.

Device is not available for
ATTACH
Explanation: The control program has
determined that the device is offline,
already dedicated, selected for MSS
mount, has minidisk allocated, or
volume is already attached to the
system.

Not accepted; previous backspace
still being processed

VM/SP System Messages and Codes

Programmer Response: Examine the
PSW portion of the message. Ensure
that the program running in the virtual
machine has a valid LPSW halt. If not,
determine why the PSW loaded was not
masked for interrupts.
User Response: IPL the virtual system
again to continue. You can also refer to
"CP Wait State Codes" on page 13 or
"Loader Wait State Codes" on page 23.

(

DMK
452W

CP entered; external interrupt
loop

4541

Explanation: The line or device has
heen disabled due to a permanent I/O
error, or the operator issued a command
that disabled the line.

Explanation: The user's virtual
machine external new PSW is enabled
for an interrupt condition that will not
be cleared upon acceptance. It is
possible to receive an interrupt
condition from the CPU Timer and the
TOD Clock Comparator that produces
this loop.

System Action: System operation
continues.
Operator Response: If the message
was issued due to a permanent I/O error
on the line, to reactivate the line issue
the ENABLE or NETWORK command.
You may have to issue the VARY
ONLINE command for some device
types before CP will accept the
ENABLE command.

System Action: System operation
continues. The virtual machine enters
CP command mode. If the virtual
machine was running disconnected, it is
logged off the system.
Programmer Response: Determine
why the external interrupt new PSW is
enabled for an interrupt condition that
will not be cleared upon acceptance
(that is, the Timer is not expected to
contain a negative value).

{Line rdevlDevice rid} disabled

4551

Line rdev not operational;
{CC = 3 Icommand reject}
Explanation: Condition code 3 or a
command I'eject was received when a
ST ART I/O was issued to line 'rdev'.

User Response: IPL the virtual system
again to continue.

System Action: System operation
continues.

453W

CP ENTERED; PROGRAM
INTERRUPT LOOP

Operator Response: For CC = 3, verify
that the terminal control unit or
transmission control unit is enabled for
use. If the control unit is properly
enabled, but trouble persists, call your
system support personnel. For
command reject, a command was issued
to an unassigned subchannel for 37xx.

Explanation: A program interrupt
occurred at the address specified in the
virtual program new PSW while the
virtual machine was in basic control
mode.
System Action: System operation
continues. The program interrupt is
reflected to the virtual machine and the
virtual machine enters console function
mode. If the virtual machine was
running disconnected, it is logged off
the system.
Programmer Response: Determine
the cause of the program interrupt and
ensure that the program new PSW is
valid.
User Response: Restart the virtual
system via the BEGIN command, or
reissue the IPL command to continue.

456W

CP entered; sysname - shared page
hex Zoe altered
Explanation: The named system has
been altered by the virtual machine.
The hexloc is the first changed page
detected by the control program. The
changed page will be returned to free
storage. No other users on the system
are affected by this error.
User Response: The user may continue
by entering the CP command BEGIN.

Control Program (CP) Messages

165

DMK
The virtual machine is now operating in
nonshared mode.

457E

46tR

CTLR rdev IPL NOT REQUIRED;
ENTER 'YES' TO CONTINUE
Explanation: A NETWORK LOAD
command or a NETWORK DUMP
command was issued for a 3704/3705
that was not in the 'IPL Required' state.

Terminal SCRNSA VE
unsuccessful
Explanation: TERMINAL CONMODE
3270 SCRNSAVE ON was specified, but

User Response: Reply YES to continue
the load or dump process. Any other
response causes immediate command
termination.

the terminal screen could not be
completely read into a 40K buffer.
System Action: The screen is not
saved. CP mode is entered.
4621
User Response: Notify your system
programmer.

4581

CTLR rdev unit check; IPL
required
Explanation: The 3704 or 3705 at real
address 'rdev' has requested a dump or
reload by presenting a unit check to the
host processor, and the automatic dump
and restart facility is currently off.

A condition was detected that
should not occur. Line xxx will be
disabled.

Operator Response: If the 3704/3705
was active before the failure, issue the
NETWORK DUMP command with the
IMMED operand to obtain
documentation of the failure. Use the
NETWORK LOAD command to reload
the 3704/3705 with an appropriate
3704/3705 control program. The CMS
service program NCPDUMP should be
used to print the dump file created by
NETWORK DUMP.

Explanation: The Control Program
received an invalid response for the
reql.lest it issued, creating a condition
that may cause a VM abend. This
message is a warning that the line will
be disabled. An additional message is
issued when the line is disabled.
System Action: System operation
continues.
Operator Response: None.
4631
460E

CTRL rdev {loadldump} failed;
program check
Explanation: During execution of the
loader or dump bootstrap routines in the
3704/3705, a 3704/3705 program check
occurred, setting the 'IPL Required'
sense bit.
User Response: Reissue the command.
If the error persists, notify the system
programmer of a possible 3704/3705
problem.

CTLR rdev unit check; restart in
progress
Explanation: The 3704/3705 at real
address 'rdev' has requested a dump or
reload by presenting a unit check to the
host processor, and the automatic
dump/restart facility has been initiated.
System Action: If the 3704/3705 was
active before the failure, a dump is
automatically taken. The 3704/3705 is
re loaded (or loaded). Any previously
enabled lines or resources are
automatically reenabled.
Operator Response: Use the CMS
service program NCPDUMP to format

166

VM/SP System Messages and Codes

(

DMK
and print the 3704/3705 dump if one was
created.

4661

When a 3704/3705 Emulation Program is
automatically reloaded after a 3704/3705
failure, the system may loop after the
restart. The reissuance of this message
and the two responses:

Explanation: This message is issued in
addition to the response to a QUERY
command if the 37xx control program
has entered buffer slowdown mode.
Buffer slowdown mode is entered if the
37xx control program has less than
12-1/2 percent of its buffers available,
indicating a temporary overload.

CTLR xxx DUMP COMPLETE
CTLR xxx ncpname LOAD COMPLETE

indicate that the 3704/3705 has been
reloaded. If the system loops after the
second response, you must reset all
emulator lines from the 3704/3705
control panel. The IBM 3704 Control
Panel Guide, GA27-3086, and the IBM
3705 Control Panel Guide, GA27-3087,
describe the procedure for resetting
emulator lines from the 3704/3705
control panel.

4641

System Action: Processing continues.
User Response: None is necessary;
however, if this situation occurs
frequently, the storage requirements of
the 37xx configuration should be
re-examined.

467W

CTLR rdev CC = 3; press 3705
'LOAD' button

System Action: The ATTACH
command is completed; processing
continues.

System Action: None.
Operator Response: Press the LOAD
button on the 3704/3705 control panel.
This permits execution of the normal
VM/SP recovery mechanism.

LINE TRACE TERMINATED DUE
TO ERROR
Explanation: No data was returned in
the line trace response.

CTLR rdev emulator lines in use
by system
Explanation: 'rdev' is the real address
of the 37xx. The operator dedicated the
native address of a 37xx running a PEP
system, and one or more of the EP lines
is in use by VM/SP.

Explanation: The 3704 or 3705 at real
address 'rdev' has entered the "Hard
Stop" condition, indicating a 3704/3705
hardware or software failure.

4651

CTLR rdev IN BUFFER
SLOWDOWN MODE

Operator Response: None. This
message is a warning that the EP lines
in use may be affected by the virtual
machine to which the 37xx was
dedicated.

4681

CTLR rdev communications
scanner failure

System Action: Line tracing is
terminated.

Explanation: During NCP
initialization the scanner did not
properly enable. The device is left "not
ready."

User Response: None.

System Action: Processing continues.

Control Program (CP) Messages

167

DMK
469E

input/output error. volume is the
volume label of the CP-owned disk from
which it was being read.

CTLR rdev {loadldump} failed;
temp space not available
Explanation: There was not enough
temporary space available on the CP
system packs to satisfy the spool space
request for the 3704/3705 dump
processor.

System Action: The system tries to
continue.
If the error occurred while trying to
read the directory during system
initialization, CP will look (in SYSOWN
order) for backup directories. If one is
found, it will be used. Otherwise,
system initialization will try to proceed
using the portion (if any) of the
directory that was loaded before the
error occurred.

User Response: Ensure that enough
temporary CP spool space is available
and reissue the DUMP command.

470E

CTLR rdev {loadldump} failed;
paging I/O error

If you were trying to install overrides
during system initialization, part of the
command overrides may have been
applied before this error occurred.

Explanation: An unrecoverable I/O
error occurred while reading the
page-format image of the 3704/3705
control program (LOAD), or while
writing the dump spool file (DUMP)
onto a system volume.

Operator Response: Note the system
file type and volume label and call your
System Programmer or System
Administrator. To correct the problem,
it may be necessary to repeat the install
procedure for the directory or override
file.

User Response: Notify the system
programmer of a possible error on CP
paging packs or DASD device. Reissue
the command.

471E

Explanation: During execution of
NETWORK LOAD or NETWORK
DUMP, a unrecoverable I/O error
occurred on the 3704/3705 channel
adapter.
User Response: Reissue the command.
If the error persists, notify the system
programmer of a possible problem with
the 3704/3705 control unit.

4751

FATAL I/O ERROR TRYING TO
READ
{DIRECTORYIOVERRIDES}
FROM volume
Explanation: The current system
directory or overrides could not be read
because of an unrecoverable

168

The error recording area on SYSRES
will contain information on the
unrecoverable read errors.

CTLR rdev {loadldump} failed;
unrecoverable I/O error

VM/SP System Messages and Codes

4761

SYSTEM
{DIRECTORYIOVERRIDES}
LOADED FROM VOLUME volume
Explanation: This message confirms
that the system directory or overrides
was successfully loaded. volume is the
volume label of the CP-owned disk from
which it was loaded.
System Action: System operation
continues.
Operator Response: None. If your
installation maintains backup directory
or override files, however, you should
note the volume label of the CP-owned
disk for future reference.

DMK
5001

devtype rdev devname CMD
50lA
REJECT CMD = cm SNS = sense
CSW = csw USE RID = userid
[BBCCHH = bbcchh IBLOCK = nnnnnn]
Explanation: An error recovery
routine found an unrecoverable
command reject I/O error. The
"devtype" in the message indicates
which error recovery routine it was:
Devtype

Error Recovery
Routine
LINE
line
CONS,GRAF
terminal
DASD
disk
PRT,PUN,RDR spooling
tape
TAPE
The other variables in the message
are:
rdev

the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
cm
the command code, in
hexadecimal, of the
Channel Command Word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW), in
hexadecimal.
bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred.
nnnnnn - the block number where
the error occurred.
System Action: System operation
continues.
Operator Response: For all types
except DASD, none. For DASD, if this
message occurs during IPL from a 3330,
3350, or 3380, make sure the read/write
switch on the drive is in the write
position. If the message occurs after
IPL, no action can be taken.

devtype rdev devname INT REQ
[CMD = cm SNS = sense CSW = csw
USERID = userid
{BBCCHH = bbcchhl
BLOCK = nnnnnn}]
Explanation: An error recovery
routine encountered an
intervention-required condition on the
device specified.
The "devtype" in the message indicates
which error recovery routine it was:
Devtype

Error Recovery
Routine
LINE
line
DASD
disk
PRT,PUN,RDR spooling
TAPE
tape
The other variables in the message
are:
rdev

the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
cm
the command code, in
hexadecimal, of the
Channel Command Word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW), in
hexadecimal.
bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred.
nnnnnn - the block number where
the error occurred.
System Action: System operation
continues.
Operator Response: For a line error
condition, no action can be taken. For
all other devices, take appropriate
action to make the device ready.

Control Program (CP) Messages

169

DMK
If the printer or punch cannot be made
ready, to retrieve the active file on the
device do the following:
1.

Use the FLUSH command to flush
the device. (The FLUSH command
will not issue a response.)
Use the DRAIN command to drain
the device. The system varies the
device offline and requeues the file
on the system printer or punch
queue. The file has a system hold
status if the HOLD * was used on
the FLUSH command.

5021

devtype rdev devname BUSOUT
CK CMD = cm SNS = sense
CSW = csw USERID = userid
[{BBCCHH = bbcchhl
BLOCK = nnnnnn}]
Explanation: An error recovery
routine found an unrecoverable bus-out
check I/O error. It could also mean that
module DMKUCS, DMKUCB, or
DMKUCC has exceeded a page
boundary (4K).
The "devtype" in the message indicates
which error recovery routine it was.
Devtype

5011

{CONSIPRTIPUNIRDR} rdev
devname INT REQ [CMD = cm
SNS = sense CSW = csw
USERID = userid]
Explanation: The terminal error
recovery routine (CONS), or the
spooling error recovery routine (PRT,
PUN, or RDR) found an unrecoverable
intervention-required I/O error. The
substitutions in the message are as
follows:
rdev

the unit address of the
failing device.
devname - the device name.
cm
the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
sense - the sense bytes, in
hexadecimal, for the error
condition.
the failing channel status
csw
word (CSW) in
hexadecimal.

System Action: System operation
continues.
Operator Response: For the console,
none; for the reader, printer, or punch,
take appropriate action to make the
device ready.

170

VM/SP System Messages and Codes

Error Recovery
Routine
DASD
disk
CONS,GRAF
terminal
LINE
line
PRT,PUN,RDR spooling
tape
TAPE
The other variables in the message
are:
rdev

the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
cm
the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW), in
hexadecimal.
bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred.
nnnnnn - the block number where
the error occurred.
System Action: System operation
continues.
Operator Response: For CONS,
DASD, GRAF, LINE, and TAPE, none.
For RDR, purge the file and try to read

DMK
cm

the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW) in
hexadecimal.
bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred.
nnnnnn - the block number where
the error occurred.

it again. For printer or punch, take
appropriate action to correct the
problem. If the printer or punch is to be
made ready, do the following to retrieve
the active file on the device:

)

Use the FLUSH command to flush
the device. (The FLUSH command
will not issue a response.)

Use the DRAIN command to drain
the device. The system varies the
device offline and requeues the file
on the system printer or punch
queue. The file has a system hold
status if the HOLD * was used on
the FLUSH command.

System Action: System operation
continues.

If the problem persists, call your system

Operator Response: See note.

support personnel.

5031

Note: Because of the buffering of lines
in the 3262 printer, lines of data may be
lost. The BACKSPAC command can be
used to recover the missing lines of
data.

devtype rdev devname EQUIP CK
CMD = cm SNS = sense CSW = csw
USERID = userid
[{BBCCHH = bbcchhl
BLOCK=nnnnnn}]

5041
Explanation: An error recovery
routine found an unrecoverable
equipment check I/O error. The
"devtype" in the message indicates
which error recovery routine it was:
Devtype

Error Recovery
Routine
CONS,GRAF
terminal
LINE
line
DASD
disk
PRT,PUN,RDR spooling
TAPE
tape
The other variables in the message
are:
rdev

the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.

devtype rdev devname DATA CK
CMD = cm SNS = sense CSW = CSW
USE RID = userid
[{BBCCHH = bbcchh I
BLOCK=nnnnnn}]
Explanation: An error recovery
routine found an unrecoverable data
check I/O error. It could also mean that
module DMKUCS, DMKUCB, or
DMKUCC has exceeded a page
boundary (4K). The "devtype" in the
message indicates which error recovery
routine it was:
Devtype

Error Recovery
Routine
CONS,GRAF
terminal
LINE
line
disk
DASD
PRT,PUN,RDR spooling
tape
TAPE
The other variables in the message
are:

Control Program (CP) Messages

171

DMK
rdev

the unit address of the
failing device.
devname - the device name.
sense - the 6:~nse bytes, in
hexadecimal, for the error
condition.
the command code, in
cm
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
csw
word (CSW) in
hexadecimal.
bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred.
nnnnnn - the block number where
the error occurred.

devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
the command code, in
cm
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
csw
word (CSW) in
hexadecimal.
bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred.
nnnnnn - the block number where
the error occurred.
System Action: System operation
continues.

System Action: System operation
continues.
Operator Response: None, or take
appropriate action to correct the
problem. If the problem persists, contact
your system support personnel.

5051

devtype rdev devname OVERRUN
CK CMD = cm SNS = sense
CSW = csw USERID = userid
[{BBCCHH = bbcchhl
BLOCK = nnnnnn}]
Explanation: An error recovery
routine found an unrecoverable overrun
check I/O error. The "devtype" in the
message indicates which error recovery
routine it was:
Devtype
CONS
DASD
LINE
TAPE

Error Recovery
Routine
terminal
disk
line
tape

The other variables in the message
are:
rdev

172

the unit address of the
failing device.

VM/SP System Messages and Codes

Operator Response: None.

5061

DASD rdev devname TRKCOND
CK CMD = cm SNS = sense
CSW = csw USERID = userid
BBCCHH = bbcchh
Explanation: The disk error recovery
routine found an unrecoverable track
condition check I/O error. The
substitutions in the message are as
follows:
rdev

the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
the command code, in
cm
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
csw
word (CSW) in
hexadecimal.
bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred.

DMK
System Action: System operation
continues.

condition. The substitutions in the
message are as follows:

Operator Response: None.

5071

rdev

DASD rdev devname SEEK CK
CMD = cm SNS = sense CSW = csw
USERID = userid
BBCCHH = bbcchh
Explanation: The disk error recovery
routine found an unrecoverable seek
check I/O error. The substitutions in
the message are as follows:
rdev

the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
cm
the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW) in
hexadecimal.
bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred.
System Action: System operation
continues.
Operator Response: Reply "retry" or
"cancel."

System Action: System operation
continues.
Operator Response: None.

5091

DASD rdev devname
TRKOVERUN CMD=cm
SNS = sense CSW = csw
USERID = userid
BBCCHH = bbcchh
Explanation: The disk error recovery
routine found an unrecoverable track
overrun check I/O error. The
substitutions in the message are as
follows:
rdev

5081

{DASDIPRTIPUNIRDR} rdev
devname PERM ERROR
CMD = cm SNS = sense CSW = csw
USERID = userid
[BBCCHH = bbcchhJ
Explanation: The disk error recovery
routine (DASD) or the spooling error
recovery routine (PRT, PUN, or RDR)
found an unrecoverable permanent error

the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
em
the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW) in
hexadecimal.

Control Program (CP) Messages

173

DMK
rdev

bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred.

System Action: System operation
continues.
Operator Response: None.

5101

TAPE rdev devname CONVERT
CK CMD = cm SNS = sense
CSW = csw USERID = userid

System Action: System operation
continues.

Explanation: The tape error recovery
routine found an unrecoverable data
convert check I/O error. The
substitutions in the message are as
follows:
rdev

System Action: System operation
continues.
Operator Response: None.

5111

TAPE rdev devname COMPAT CK
CMD = cm SNS = sense CSW = csw
USERID = userid
Explanation: The tape error recovery
routine found an unrecoverable
compatibility check I/O error. The
substitutions in the message are as
follows:

174

VM/SP System Messages and Codes

Operator Response: None.

5121

TAPE rdev devname LOAD
POINT CMD = cm SNS = sense
CSW = csw USERID = userid
Explanation: The tape error recovery
routine found an unrecoverable load
point I/O error. The substitutions in the
message are as follows:
rdev

System Action: System operation
continues.
Operator Response: None.

(

DMK
5131

{DASDITAPE} rdev devname
FILE PROT CMD=cm SNS=sense
CSW = csw USERID = userid
[{BBCCHH = bbcchhl
BLOCK=nnnnnn}]

devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
the command code, in
cm
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW) in
hexadecimal.
bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred.

Explanation: The disk error recovery
routine (for DASD) or the tape error
recovery routine (for TAPE) found an
unrecoverable file protect I/O error.
The substitutions in the message are as
follows:
rdev

the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
the command code, in
cm
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW) in
hexadecimal.
bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred.
nnnnnn - the block number where
the error occurred.

)

System Action: System operation
continues.

System Action: System operation
continues.
Operator Response: Reply "retry" or
"cancel."

5161

devtype rdev devname BAD
SENSE CMD = cm SNS = sense
CSW=csw USERID=userid
[{BBCCHH = bbcchhl
BLOCK=nnnnnn}]
Explanation: An error recovery
routine encountered an error on a sense
operation. The "devtype" in the
message indicates which error recovery
routine it was:
Devtype

Operator Response: None.

5141

DASD rdev devname ADDMRK
CK CMD = cnl SNS = sense
CSW = csw USERID = userid
BBCCHH = bbcchh
Explanation: The disk error recovery
routine found an unrecoverable missing
address marker I/O error. The
substitutions in the message are as
follows:
rdev

DASD
LINE
TAPE

Error Recovery
Routine
disk
line
tape

The other variables in the message
are:
rdev

the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.

the unit address of the
failing device.

Control Program (CP) Messages

175

DMK
cm

the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
csw
word (CSW) in
hexadecimal.
bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred.
nnnnnn - the block number where
the error occurred.

5181

Explanation: While attempting
recovery, the disk error recovery
routine (for DASD) or the tape error
recovery routine (for TAPE)
encountered an error not associated
with the original error. Error recovery
cannot be continued. The substitutions
in the message are as follows:
rdev

the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
the comma:p.d code, in
cm
hexadecimal, of the
channel command word
(CCW) being executed
w hen the error occurred.
the failing channel status
csw
word (CSW) in
hexadecimal.
bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred.

System Action: System operation
continues.
Operator Response: None.

5171

{LINEITAPE} rdev devname
NOT/KNOWN CMD=cm
SNS = sense CSW = csw
USE RID = userid
Explanation: The line error recovery
routine (for LINE) or the tape error
recovery routine (for TAPE)
encountered an error that is considered
an impossible condition and must be
reported as such. The substitutions in
the message are as follows:
the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
the command code, in
cm
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
csw
word (CSW) in
hexadecimal.

System Action: System operation
continues.

rdev

System Action: System operation
continues.
Operator Response: None.

176

VM/SP System Messages and Codes

{DASD ITAPE} rdev devname
RECV ERROR CMD = cm
SNS = sense CSW = csw
USERID = userid
[BBCCHH = bbcchh]

Operator Response: None.

5191

TAPE rdev devname PE BURST
CMD = cm SNS = sense CSW = csw
USE RID = userid
Explanation: The tape error recovery
routine found an unrecoverable phase
encode burst I/O error. The
substitutions in the message are as
follows:
the unit address of the
failing device.
devname - the device name.

rdev

DMK
sense -

csw

the sense bytes, in
hexadecimal, for the error
condition.
the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
word (CSW) in
hexadecimal.

System Action: System operation
continues.
Operator Response: None.

5201

devtype rdev devname CHAN
ERROR CMD=cm SNS=sense
CSW = csw USERID = userid
[{BBCCHH = bbcchh I
BLOCK=nnnnnn}]
Explanation: An error recovery
rQutine encountered an unrecoverable
channel I/O error. The "devtype" in the
message indicates which error recovery
routine it was:

bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred.
nnnnnn - the block number where
the error occurred.
System Action: System operation
continues.
Operator Response: None.

5211

devtype rdev devname NO
DEVICE CMD=cm SNS=sense
CSW = csw USERID = userid
Explanation: An error recovery
routine received a reported error from a
device that is not in the system
configuration. The "devtype" in the
message indicates which error recovery
routine it was: The substitutions in the
message are as follows:
Devtype

Error Recovery
Routine
GRAF
terminal
PRT,PUN,RDR spooling
TAPE
tape

Devtype

Error Recovery
Routine
LINE
line
DASD
disk
PRT,PUN,RDR spooling
TAPE
tape
The other variables in the message
are:
rdev

The other variables in the message
are:
rdev

the unit address of the
failing device.
devname - the device name.
sense- the sense bytes, in
hexadecimal, for the error
condition.
the command code, in
cm
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
csw
word (CSW) in
hexadecimal.
System Action: System operation
continues.
Operator Response: None.

Control Program (CP) Messages

177

DMK
5221

TAPE rdev devname ERASE CK
CMD = cm SNS = sense CSW = csw
USERID = userid

System Action: System operation
continues.
Operator Response: None.

Explanation: The tape error recovery
routine found an unrecoverable erase
check I/O error. The substitutions in
the message are as follows:
the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
cm
the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW) in
hexadecimal.

5241

PRINTER rdev devname LOAD
CHECK CMD=cm SNS=sense
CSW = csw USE RID = userid

rdev

System Action: System operation
continues.
Operator Response: None.

5231

TAPE rdev devname CONTROL
CK CMD = cm SNS = sense
CSW = csw USERID = userid
Explanation: The tape error recovery
routine found an unrecoverable control
check on a tape. The substitutions in
the message are as follows:
rdev

178

VM/SP System Messages and Codes

Explanation: An attempt was made to
load an invalid buffer to the printer.
CMD = FB or F3 indicates an invalid
UCS buffer; CMD = 63 indicates an
invalid FCB was transmitted to the
printer. The substitutions in the
message are as follows:
/

rdev

System Action: System operation
continues. If the LOAD CHECK is
encountered during printing, the printer
is drained and the file is put in
SYSTEM HOLD.
Operator Response: Retry the
operation. If encountered during
printing and the message is due to an
invalid FCB image (CMD =63), send the
file to a printer that will accept the
image, or NOOP the command (for
example, 3211 type printer started with
the DEFFCB option).

DMK
5251

{GRAFIRDRIPRTIPUN} rdev
devname FORMAT CK CMD=cm
SNS = sense CSW = csw
USERID = userid

sense -

Explanation: The terminal error
recovery routine (for GRA F) or the
spooling error recovery routine (for
RDR, PRT, or PUN) encountered a
format error on a write RCE (Read
Column Eliminate) command. The
substitutions in the message are as
follows:
the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
cm
the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW) in
hexadecimal.

csw

System Action: System operation
continues.

rdev

System Action: System operation
continues.
Operator Response: Retry the
operation.

5261

TAPE rdev devname DSE
FAILED CMD = cm SNS = sense
CSW = csw USERID = userid
Explanation: A data security erase
operation has failed to complete
successfully, causing a timeout
condition to exist on communication
lines. The substitutions in the message
are as follows:
rdev

the unit address of the
failing device.
devname - the device name.

Operator Response: Activate the reset
and load-rewind buttons on the failing
device and restart the job.

5271

{LINEICONS} rdev devname
LOST DATA CMD=cm
SNS = sense CSW = csw
USERID = userid
Explanation: The line error recovery
routine (for LINE) or the terminal errOr
recovery routine (for CONS) found an
unrecoverable lost data I/O error. The
substitutions in the message are as
follows:
rdev

Control Program (CP) Messages

179

DMK
5281

{LINE ICONS} rdev devname
TIMEOUT CMD = cm SNS = sense
CSW = csw USERID = userid

Explanation: The line error recovery
routine (for LINE) or the terminal error
recovery routine (for CONS) determined
that problems causing a timeout
condition exist on communication lines.
The substitutions in the message are as
follows:
the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
cm
the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW) in
hexadecimal.

csw

System Action: System operation
continues.

rdev

Operatol'Response: None.

5301

rdev

Operator Response: None.

{GRAFIRDRIPRTIPUN} rdev
devname PARITY CK CMD = cm
SNS=sense CSW=csw
USERID = userid
Explanation: The terminal error
recovery routine (for GRAF) or the
spooling error recovery routine (for
RDR, PRT, or PUN) found an
unrecoverable parity check I/O error.
The substitutions in the message are as
follows:
rdev

the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.

180

VM/SP System Messages and Codes

GRAF rdev devname UNIT SPEC
CMD = cm SNS = sense CSW = csw
USERID = userid
Explanation: The terminal error
recovery routine found an
unrecoverable device-detected error.
The substitutions in the message are as
follows:

System Action: System operation
continues.

5291

the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
word (CSW) in
hexadecimal.

System Action: System operation
continues.
Operator Response: None.

5311

GRAF rdev devname CNTRL CK
CMD = cm SNS = sense CSW = csw
USERID = userid
Explanation: The terminal error
recovery routine found an
unrecoverable error. The addressed
device failed to perform a specified

DMI(
operation or respond to the control unit
within a specified period of time. The
substitutions in the message are as
follows:

Operator Response: None.

5331

rdev

Explanation: The FB-512 error
recovery routine encountered an
unrecoverable check data error. Th~
substitutions in the message are as
follows:
rdev

System Action: System operation
continues.
Operator Response: None.

5321

GRAF rdev devname OP CHECK
CMD = cm SNS = sense CSW = csw
USERID = userid
Explanation: The terminal error
recovery routine found an
unrecoverable error. The control unit
has received a valid command or order
that it cannot execute. The
substitutions in the message are as
follows:

System Action: System operation
continues.
Operator Response: None.

5341
rdev

DASD rdev devname CHECK
DATA CMD=cm SNS=sense
CSW = csw USERID = userid
BLOCK = nnnnnn

DASD rdev devname BKSIZE EX
CMD = cm SNS = sense CSW = csw
USERID = userid BLOCK = nnnnnn
Explanation: The FB-512 error
recovery routine encountered an
unrecoverable error. The substitutions
in the message are as follows:
rdev

the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.

System Action: System operation
continues.
Control Program (CP) Messages

181

DMK
cm

the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW) in
hexadecimal.
nnnnnn - the block number where
the error occurred.

5361

rdev devname reports disabled
interface; fault code = code; notify
CE
Explanation: Unit check has occurred
on an FB-512 or count-key-data I/O
request to a Director Module indicating
that a permanent error has occurred on
the companion Director Module. The
sense data indicates Alternate Interface
Disabled. (Sense byte 1, bit 3.) The
substitutions in the message are as
follows:

System Action: System operations
continues.
Operator Response: None.

rdev
code

5351

DASD rdev devname WR INHIBT
CMD = cm SNS = sense CSW = csw
USERID = userid BLOCK = nnnnnn
Explanation: The FB-512 error
recovery routine encountered an
unrecoverable error. The substitutions
in the message are as follows:
the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
cm
the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW) in
hexadecimal.
nnnnnn - the block number where
the error occurred.

device address on which
the error was reported.
fault symptoms code
obtained from the sense
data that will be used by
the CE to locate the
failing component.

System Action: The system logs the
error and retries the I/O request. This
retry should succeed since it is another
control unit that failed.

rdev

System Action: System operations
continues.
Operator Response: None.

User Response: Notify your service
personnel.

5381

DASD rdev devname PROG
ERROR CMD = cmd SNS = sense
CSW = csw USE RID = userid
Explanation: An error recovery
routine encountered an unrecoverable
programming error on a request for
control program I/O. The substitutions
in the message are as follows:
rdev

the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
csw
the failing channel status
word (CSW) in
hexadecimal.

System Action.: System operation
continues.

182

VM/SP System Messages and Codes

(

DMK
Operator Response: Notify the system
programmer of an error in a channel
program in the control program.

)

csw

5391

TAPE rdev devname BOT FAIL
CMD = cm SNS = sense CSW = csw
USERID = userid

userid -

Explanation: The tape error recovery
routine found an unrecoverable
beginning of tape fail I/O error. The
substitutions in the message are as
follows:
the unit address of the
failing device.
devname - the device name.
the command code, in
cm
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
sense - the sense bytes, in
hexadecimal, for the error
condition.
csw
the failing channel status
word (CSW) in
hexadecimal.

the command code, in
hexadecimal, for the error
condition
the failing channel status
word (CSW) in
hexadecimal.
associated userid, if any,
that performed the I/O
operation.

System Action: None. Printing
operations on the device continue.
Operator Response: Schedule
maintenance as soon as possible.

rdev

System Action: System operation
continues.
Operator Response: None

5401

PRINTER rdev devname MAINT
REQ CMD = cm SNS = sense
CSW = csw USE RID = userid
Explanation: Maintenance of the
printer is required. Performance of the
printer may be degraded. The message
is intended to warn the operator before
the problem becomes critical. The
substitutions in the message are as
follows:
rdev

the unit address of the
fai ling device.
devname - the device name.
sense - the sense bytes, in
hexadeci.mal, for the error
condition.

5461

Interruption {clearedlpending};
{devicelcontrol unit} rdev, CSW
csw, userid userid
Explanation: If PENDING appears in
the message text, the missing interrupt
handler has found device end pending
for device rdev for more than the
specified time period. The condition
cannot be corrected. If CLEARED
appears in the message text, the missing
interrupt handler has corrected the
missing interrupt condition. The device
remains operational. The substitutions
in the message are as follows:
rdev

csw
userid -

real device address or
control unit address (path
used by lOS)
last half of the csw of the
last I/O operation
associated userid, if any,
that performed the I/O
operation

System Action: This message is issued
to alert the operator of a possible error
condition. If the missing interrupt
handler is able to correct the condition
the device remains operational. If the
missing interrupt handler is unable to
correct the condition, manual
intervention is required.
The tiHle interval for each device class
is specifi(>d in the SYSl\HH macro. If
the device is still inoperative after the

Control Program (CP) Messages

183

DMK
initial message is issued, another
message will be issued every two time
intervals.

551E

Explanation: The error recording area
specified in the message is full. Further
errors of that type cannot be recorded.

Operator Response: If PENDING
appears in the message text, manual
action may be required to free the
device. Examine device rdev 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
userid is available issue a warning
message to the user making him aware
of the problem. If no apparent hardware
problem is found, issue the HALT
command to free the device.

547E

Missing interrupt monitoring not
available

System Action: System operation
continues, but no I/O errors, or machine
check and channel check errors, are
recorded.
Operator Response: Run the CPEREP
program to print the error records that
are on the error recording area that is
full, and then clear the area. Save the
printed output for your system support
personnel.

5521

System Action: None.
User Response: Add the missing
interrupt module DMKDID to the load
list. Then regenerate the CP nucleus,
reload and re-IPL the system.

System Action: System operation
continues.
Operator Response: Run the CPEREP
program to print the records on the
affected area, and then clear the area.
Save the printed output for your system
support personnel.

184

System Action: System operation
continues.
Operator Response: If you did not
expect this formatting to take place,
ensure that the allocation of the system
volume does not overlap cylinders or
disk space and then call your system
support personnel.

Error recording area 90 percent
full; run CPEREP
Explanation: The error recording area
specified in the message is 90% full.
This message is a warning to prevent
loss of error records.

VM/SP System Messages and Codes

Formatting error recording area
Explanation: The error recording area
was not in the proper format, so it is
now being rewritten in the correct CP
format. This should only occur at the
first IPL of a new system with a new
error recording area. If this message
appears at other times, it is probably
due to a hardware error.

Explanation: The SET MITIME
command was issued and the missing
interrupt handler module, DMKDID,
was not in the system.

550E

Error recording area full; run
CPEREP

5531

Error recording area cleared; user
userid
Explanation: DMKIOG has been
invoked by user 'userid' to clear the
error recording area specified in the
message. Error recording in that area is
reenabled.
System Action: System operation
continues.

DMK
Operator Response: None.

5581

DMSIOH559W is received for only
one of the SRF devices of a 3036
console - and both were specified on
the RIOGEN macro - no user action
is necessary.)

Unrecoverable I/O error; error
recording disabled
Explanation: Unrecoverable
input/output errors were encountered
while trying to read or write in the
error recording area at system
initialization time. Error recording has
been disabled. Probable hardware error.

System Action: Processing continues.
System will run, EREP data is collected.
Reports are unformatted.

System Action: System operation.
continues but error recording is not
being done.

User Response:

Operator Response: System operation
without error recording is not
recommended. Whenever possible, try
to restart the system, with the system
disk on another drive. If the problem
persists, call your system support
personnel.

Reassemble DMKRIO with the
proper address for the 7443 devices
and include "SRF =" on the
RIOGEN macro, refer to the VM/SP
Planning Guide and Reference.

Wait until the service support
console is available. Enable the I/O
interface. Select SRF mode from the
C1 frame by activating the SRF
(A2). (On the 3032, the SRF appears
disabled until it is accessed.) VARY
ON the SRF. Attach the SRF.
Rerun CPEREP CLEARF. Refer to
the 3033 Processor Complex
Operating Procedures, GC38-0031.

Rerun CPEREP when both console
stations are operational, generate
reports then run CPEREP CLEARF
to clear and obtain the frame
records.

SRF rdeu not accessible: frames
not on error cylinders

559W

Explanation: One of the following
conditions has occurred on a 3031, 3032,
or 3033 processor:
1.

SRF is not included in DMKRIO.

The service support console is
configured for diagnostics, remote
hook-up, or program frame. The
console is not in SRF mode. (Only
one of the two SRF devices of a 3036
console is accessible at any given
time by VM/SP control program.
Therefore, if both SRF devices of a
3036 are specified on the RIOGEN
macro at system generation, then
during initialization of the error
recording cylinders message
DMKIOH559W will be issued for one
of these SRF devices. Since both
SRF devices of a 3036 console
contain identical frame data, only
one SRF per 3036 need to be
successfully accessed during error
recording initialization. If message

The system is running in degraded
mode. (Only one console station is
operational. )

560W

Errors on SRF rdeu: frames not on
error cylinders
Explanation: A permanent I/O error
was encountered during an I/O
operation with SRF 'rdev'. The SRF
'rdev' frames are not placed on the error
recording cylinders or in the error
recording area.
System Action: Processing continues.
Operator Response: After the cause of
the error has been corrected, run

Control Program (CP) Messages

185

DMK
CPEREP with the CLEARF parameter
specified to clear the area. This will
cause the frames to be placed in the
error recording area.

5801

Explanation: A sense command was
issued with no outstanding unit check.
The substitutions in the message are as
follows:

More than 50 MCR or CCR frames
were read from SRF rdev

561W

Explanation: The maximum number of
frames of one type has been exceeded.
•

There is an error in the Service
Processor when responding to I/O
requests to the SRF, or

•

The last engineering change has
provided a set of frames larger than
the maximum number expected.

rdev

System Action: System operation
continues.

Operator Response: Processing of
MCH or CCH records by 50 frames may
result in an incomplete or erroneous
edit of logout information. Call IBM
Field Engineering for support.

Operator Response: None.

5811

I/O ERROR ADD = rstor,
USERID = userid
Explanation: The Vl\I/SP error
recording interface has determined that
a permanent or temporary 1/0 error has
occurred on a virtual machine. This
message also appears when VM/SP error
routines are invoked for recording
counter and buffer overflow statistics
for various devices, for recording
amounts, and for recording general
statistical data.
System Action: System operation
continues.
Operator Response: Run CPEREP to
document the error. If the problem
persists, call your system SUppOl·t
personneL

186

VM/SP System Messages and Codes

the unit address of the failing
device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
em
the command code, in
hexadecimal, of the channel
command word (CCW) being
executed when the error
occurred.
csw
the failing channel status
word (CSW) in hexadecimal.

System Action: The first 50 frameR
read will be accepted as valid and will
be written to the error recording area.

5751

TAPE rdev devname NO ERR SNS
CMD = cm SNS = sense CSW = csw
USERID = userid

TAPE rdev devname DISPLAY CK
CMD = cm SNS = sense CSW = csw
USERID = userid
Explanation: A LOAD DISPLAY
command was issued to a drive while
the cartridge was being loaded. The
substitutions in the message are as
follows:
rdev

the unit address of the
faiHng device.
devname - the device name.
sense - the sense bytes. in
hexadecimaL for the error
condition.
em
the command code, in
hexadecimal, of the
channel command word
(CeW) being executed
when the error occurred.
C8W
the failing channel status
word (C8W) in
hexadecimal.

DMK
System Action: System operation
continues.

Operator Response: None.
csw

5821

TAPE rdev devname WRITEID
CK CMD = cm SNS = sense
CSW = csw USERID = userid

System Action: System operation
continues.

Explanation: The format identification
mark could not be successfully written
at the beginning of the tape. The
substitutions in the message are as
follows:

Operator Response: None.

5841
the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
the command code, in
cm
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
csw
word (CSW) in
hexadecimal.

rdev -

the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
the command code, in
em
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
csw
word (CSW) in
hexadecimal.

rdev -

Operator Response: None.

TAPE rdev devname BUFF
ERROR CMD = cm SNS = sense
CSW = csw USERID = userid
Explanation: A control unit buffer
memory error has been detected, and
part of the buffer has been unusable.
The substitutions in the message are as
follows:
the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal! for the error
condition.
rdev -

TAPE rdev devname NOT
CAPABL CMD = cm SNS = sense
CSW = csw USE RID = userid
Explanation: The format identification
burst at beginning of tape could not be
read. The substitutions in the message
are as follows:

System Action: System operation
continues.

5831

the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
word (CSW) in
hexadecimal.

System Action: System operation
continues.
Operator Response: None.

5851

TAPE rdev devname TAPE VOID
CMD = cm SNS = sense CSW = csw
USERID = userid
Explanation: A read-type operation
was in progress, and no data blocks
were found on the tape. The
substitutions in the message are as
follows:

Control Program (CP) Messages

187

DMK
the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
the command code, in
cm
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW) in
hexadecimal.
rdev -

5871

Explanation: The tape inside the
cartridge is not the correct length. The
substitutions in the message are as
follows:
rdev -

System Action: System operation
continues.
Operator Response: None.

5861

TAPE rdev devname TENSION
CMD = cm SNS = sense CSW = csw
USE RID = userid

System Action: System operation
continues.

Explanation: The drive encountered
an error that caused a loss of tension on
the tape. The substitutions in the
message are as follows:
the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
cm
the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW) in
hexadecimal.

rdev -

System Action: System operation
continues.
Operator Response: The drive may
have to be unloaded manually.

188

VM/SP System Messages and Codes

TAPE rdev devname LENGTH CK
CMD = cm SNS = sense CSW = ~sw
USERID = userid

Operator Response: None.

5881

TAPE rdev devname PHYS EOT
CMD = cm SNS = sense CSW = csw
USERID = userid
Explanation: A command was
executing when physical end of tape was
encountered. The substitutions in the
message are as follows:
the uni t address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
the command code, in
cm
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
csw
word (CSW) in
hexadecimal.
rdev -

DMK
System Action: System operation
continues.

)

the command code, in
hexadecimaL of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
word (CSW) in
hexadecimal.

Operator Response: None
csw

5891

TAPE rdev devname BKW AT
BOT CMD = cm SNS = sense
CSW = csw USE RID = userid

System Action: System operation
continues.

Explanation: Beginning of Tape was
encountered while executing a
backward-type command. The
substitutions in the message are as
follows:

Operator Response: None.

5911
rdev -

)

Explanation: The tape could not be
positioned in front of the block/tape
mark requested by the LOCATE BLOCK
command. The substitutions in the
message are as follows:
the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
the command code, in
cm
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
csw
word (CSW) in
hexadecimal.
rdev

System Action: System operation
continues.
Operator Response: None.

5901

TAPE rdev devname UNLOAD
ERR CMD = cm SNS = sense
CSW = csw USERID = userid

System Action: System operation
continues.

Explanation: A cartridge was
manually unloaded. The substitutions
in the message are as follows:
t.he unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal. for the error
condition.

TAPE rdev devname NO RECORD
CMD=cm SNS=sense CSW=csw
USERID = userid

Operator Response: None.

rdev -

5921

TAPE rdev devname DRIV
ASGND CMD=cm SNS=sense
CSW = csw USERID = userid
Explanation: The drive is assigned, but
not to the channel path issuing the
failing command. The substitutions in
the message are as follows:

Cont.rol Program (CP) Messages

189

DMK
rdev

5941

Explanation: The control unit, or one
of the control units in a dual control
unit configuration, developed a severe
error condition. The substitutions in
the message are as follows:
rdev -

System Action: System operation
continues.
Operator Response: The drive may be
assigned to another system. The
cartridge should be removed to prevent
unauthorized access to data on the tape.

5931

TAPE rdev devname DRIV
OFFLN CMD = cm SNS = sense
CSW = csw USERID = userid

The control unit was able to reinitialize
itself sufficiently to continue processing.

System Action: System operation
continues.

Explanation: A command for drive
activity has been issued to a drive that
is not online. The substitutions in the
message are as follows:
the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
cm
the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW) in
hexadecimal.

TAPE rdev devname CU CKI ERR
CMD=cm SNS=sense CSW=csw
USERID = userid

Operator Response: None.

rdev -

System Action: System operation
continues.
Operator Response: None.

190

VM/SP System Messages and Codes

5951

TAPE rdev devname CU ERP ERR
CMD = cm SNS = sense CSW = csw
USERID = userid
Explanation: While attempting error
recovery, the control unit encountered
an error that was not associated with
the original error. The substitutions in
the message are as follows:
the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
rdev -

(

DMK
em

csw

the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
the failing channel status
word (CSW) in
hexadecimal.

5971

Explanation: A READ command failed
and the control unit was able to read
the data on the tape in the opposite
direction. The substitutions in the
message are as follows:

The drive may not be positioned next to
the block in error.

rdev -

System Action: System operation
continues.
Operator Response: None.

5961

TAPE rdev devname CU
INCOMPA CMD=cm SNS=sense
CSW = csw USERID = userid
Explanation: The drive requires
updates (patches) unknown to the
control unit, or the drive model is
incompatible with the control unit. In
either case, the drive and control unit
are incompatible. The substitutions in
the message are as follows:
the unit address of the
failing device.
devname - the device name.
sense - the sense bytes, in
hexadecimal, for the error
condition.
em
the command code, in
hexadecimal, of the
channel command word
(CCW) being executed
when the error occurred.
csw
the failing channel status
word (CSW) in
hexadecimal.

TAPE rdev devname RD OPP CK
CMD = em SNS = sense CSW = csw
USERID = userid

The data is located in the control unit's
buffer in reverse order.

System Action: System operation
continues.

rdev -

System Action: System operation
continues.
Operator Response: None.

Operator Response: None.

5981

TAPE rdev devname BLK ID SEQ
CMD = Cln SNS = sense CSW = csw
USERID = userid
Explanation: The block ID of a data
block shows that the block is out of
sequence. The substitutions in the
message are as follows:
rdev -

the unit address of the
failing device.
devname . the device name.
sense - the sen5e bytes. in
hexadecimal. for the error
condition.
em
the command code, in
hexadecimal of the
channel command word
(CCW) being executed
when the error occurred.
l

Control Program (CP) Messages

191

DMK
csw

the failing channel status
word (CSW) in
hexadecimal.

xxx - Channel, control unit, and device
address of the failing unit.
System Action: System operation
continues.

System Action: System operation
continues.

Operator Response: Probable
hardware error. If the problem persists,
call your system support personnel.

Operator Response: None.

60lE

Channel control check device xxx
6021
Explanation: A channel control check
occurred on the channel specified by
device xxx, where:

Explanation: An interface control
check occurred on channel specified in
device xxx, where:

xxx - Channel, control unit, and device
address of the failing unit.

System Action: System operation
continues.

Operator Response: Probable
hardware error. If the problem persists,
call your system support personnel.

~ll

Operator Response: Probable
hardware error. If the problem persists,
call your system support personnel.

CHANNEL CONTROL CHECK
DEVICE xxx; [USER userid]
603W

Explanation: A channel control check
occurred on the channel specified by
device xxx, where:
xxx - Channel, control unit, and device
address of the failing unit.
System Action: System operation
continues.
Operator Response: Probable
hardware error. If the problem persists,
call your system support personnel.

602E

CHANNEL ERROR
Explanation: A channel check
condition occurred from which the
channel check handler could not
recover.
System Action: The system enters a
wait state (wait state code = 002).
Operator Response: Probable
hardware error. Invoke CPEREP to
document the error condition before
restarting the system. If the problem
persists, contact your hardware support
personnel.

Interface control check device xxx
Explanation: An interface control
check occurred on channel specified in
device xxx, where:

192

INTER}'ACE CONTROL CHECK
DEVICE xxx; [USER userid]

VM/SP System Messages and Codes

To restart, IPL the system, specifying
CKPT start.

DMK
If the problem recurs, contact your
hardware support personnel.

CHANNEL CHECK RECORDING
FAILURE

6051

Explanation: This message appears:
611W

•

When an unrecoverable I/O error is
encountered while recording on the
error recording cylinder, or

Explanation: The machine check
handler has encountered an error that
cannot be diagnosed because of an
invalid machine check old PSW or
invalid machine check interrupt code
(MeIC). The integrity of the system at
this point is not reliable.

When the channel check recording
cylinder is full.

System Action: System operation
continues.

System Action: The system enters a
disabled wait state (wait state code =
001).

Operator Response: Run the CPEREP
program to write out the error records
and clear the channel recording
cylinder. If the error recurs, contact
your system support personnel.

609W

610W

Operator Response: Probable
hardware error. Invoke CPEREP to
document the error. Restart the system.
If the problem recurs, contact your
hardware support personnel.

MACHINE CHECK; PROCESSOR
CONTROLLER DAMAGE cpuid
Explanation: The machine check
handler has encountered an error in the
Processor Controller.

MACHINE CHECK; SYSTEM
INTEGRITY LOST cpuid

612W

MACHINE CHECK TIMING
FACILITIES DAMAGE

System Action: The system enters a
disabled wait state. (Wait state code =
001)

Explanation: An error has occurred in
the timing facilities. Probable hardware
error.

Operator Response: Contact your
system support personnel.

System Action: The system enters a
disabled wait state (wait state code
001).
Operator Response: Invoke CPEREP
to document the error. Restart the
system. If the problem recurs, contact
your hardware support personnel.

MACHINE CHECK; SUPERVISOR
DAMAGE cpuid
Explanation: The machine check
handler has encountered an
unrecoverable error within CPo This
message is also issued if a malfunction
alert occurs on the attached processor
and CP was in control.
System Action: The system enters a
disabled wait state (wait state code =
001 or 013).
Operator Response: Probable
hardware error. Invoke CPEREP to
document the error. Restart the system.

6131

SOFT MACHINE CHECK
RECORDING DISABLED cpuid
Explanation: The error reporting
interrupt mechanism for soft machine
checks has been disabled.
System Action: System operation
continues.
Operator Response: None.

Control Program (CP) Messages

193

DMK
6141

MACHINE CHECK; DAMAGED
PAGE NOW DELETED cpuid
Explanation: The machine check
handler has deleted a page of storage as
a result of storage data failures.
Probable hardware error.

Operator Response: Run the CPEREP
program to document the error. If the
problem recurs, contact your system
support personnel.

6171

System Action: System operation
continues.

Explanation: The Machine Check
Handler has encountered a buffer
storage or DLAT partially disabled.

Operator Response: The system
operator should note that the system is
operating with 4K bytes less storage
each time this message appears.

System Action: System operation
continues.

If the problem recurs, run the CPEREP
program to document the error, then
contact your system support personnel.

6151

MACHINE CHECK RECORDING
FAIL URE cpuid

Operator Response: Run the CPEREP
program to document the error. If the
problem recurs, contact your system
support personnel.

6181

Explanation: This message appears:
If an unrecoverable I/O error is
encountered while recording on the
error recording cylinder, or

Explanation: The SET MODE
command has placed the pro~essoI' in
the mode that is specified.
\

•

When the machine check recording
cy linder is full.

System Action: System operation
continues.

Operator Response: Run the CPEREP
program to print the error records and
clear the MCR recording cylinder. If the
problem recurs, contact your system
support personneL

MACHINE CHECK; USER userid
TERMINATED cpuid
Explanation: The user identified by
userid has encountered a machine check
error and the user's virtual machine has
been reset. Probable hardware error.
System Action: System operation
continues.

194

{INSTRUCTION RETRYIMAIN
STORAGE} NOW IN
{RECORDIQUIET} MODE cpuid

•

Operator Response: None.

System Action: System operation
continues.

6161

MACHINE CHECK; BUFFER OR
DLAT DAMAGE cpuid

Vl\1/SP System Messages and Codes

6191

MACHINE CHECK; OPERATION
TERMINATED cpuid
Explanation: The user has
encountered a machine check error and
the user's virtual machine had been
reset or terminated. If the virtual
machine was reset, the user must
reinitialize the system to commence
operation. If the virtual machine was
terminated, he must log on again to
commence operation.
System Action: System operation
continues.
Operator Response: Run the CPEREP
program to document the error. If the

DMK
problem recurs, contact your system
support personnel.

6201

622W

Explanation: During a machine check
interruption, a group of channels is
unavailable. The channels will not be
available until the system is reset.

MACHINE CHECK; ATTACHED
PROCESSOR NOT BEING USED
Explanation: The attached processor is
no longer being used by the system
because:
•

A malfunction alert was received
from the attached processor.

•

The machine check handler received
an unrecoverable error on the
attached processor while in problem
state,

•

An instruction processing error was
detected for the attached processor.

System Action: The system is
terminated by loading a disabled wait
PSW. The wait code in the PSW is
X'OOOOOOOl'.
Operator Response: Invoke CPEREP
and then reload the system via the IPL
process. If the problem recurs, contact
your hardware support personnel.

6231

System Action: System operates in
uniprocessor mode.

MACHINE CHECK; AFFINITY
SET OFF

System Action: Processing continues
on the attached processor in
uniprocessor mode.

Explanation: The attached processor is
no longer being used by the system
because of a malfunction alert, or an
unrecoverable machine check. Affinity
for the attached processor is no longer
valid.
System Action: System operates in
uniprocessor mode. The user is put in
console function mode (if user was not
disconnected) with affinity turned off.
User Response: Resume processing.
Continue to operate without attached
processor affinity. if possible.

CHANNEL SET CONNECTED TO
PROCESSOR NN
Explanation: A processor failure
occurred on the main processor and
automatic processor recovery succeeded
in connecting the channel set to the
attached processor; or the operator
issued a VARY OFFLINE CPU
command for the I/O processor and the
offline process succeeded in connecting
the channel set to the attached
processor.

Operator Response: Run the CPEREP
program to document the error and save
the output for your system support
personnel.

6211

MACHINE CHECK; MULTIPLE
CHANNEL ERRORS

Operator Response: When a processor
failure occurred, call IBM Field
Engineering for support. When the
problem is resolved, issue the VARY
ONLINE command.

6241

MACHINE CHECK; EXTERNAL
DAMAGE
Explanation: The machine check
handler has encountered external
damage. Damage has occurred to a
channel, channel controller. switching
unit or another unit external to the
central processing unit.

Control Program (CP) Messages

195

DMK
System Action: System operation
continues.

6281

Operator Response: Run CPEREP
program to document the error and save
output for your support personnel.

6251

Explanation: The processor has
reported 12 successful corrections of
double-bit errors in storage belonging to
the dynamic paging area. In each
instance, CP was unable to mark the
page frame offline because it was locked
in storage.

ALTERNATE PROCESSOR
RECOVERY SUCCESSFUL;
PROCESSOR xx OFFLINE

System Action: The error-reporting
interrupt mechanism for soft machine
checks will be disabled for
approximately one minute. System
operation continues. If the error occurs
again when soft machine checks are
enabled, CP will try to discontinue use
of the affected page frame.

Explanation: A hardware error has
occurred on processor xx which has
resulted in the system's varying of
processor nn (and its channels if an MP
configuration) offline. The remaining .
online processor has recovered from the
failure, and the system will continue
operation in uniprocessor mode.

Operator Response: If the problem
recurs, run the CPEREP program to
document the error. Then contact your
system support personnel.

System Action: Processing continues
in uniprocessor mode.
Operator Response: Run the CPEREP
program to document the error and save
the output for system support personnel.

6271

6291

Explanation: The processor has
reported 12 successful corrections of
double-bit errors in storage belonging to
either the control program or the
virtual-equals-real user. The storage
belongs to the program or user
identified as "userid."

System Action: System operation
continues.
Operator Response: None.

700E

Operator Response: The system
operator should note that performance
may he degraded. Run the CPEREP
program to document the error, and
contact your system support personnel.

196 VM/SP System Messages and Codes

SOFT MACHINE CHECK
REPORTING NOW ENABLED
Explanation: CP has enabled the
error-reporting interrupt mechanism for
soft machine checks.

MACHINE CHECK; STORAGE
DEGRADATION FOR userid

System Action: The error-reporting
interrupt mechanism for soft machine
checks is disabled. System operation
continues.

DEGRADATION; CP WILL TRY
RECOVERY IN 1 MINUTE

INPUT UNIT IS NOT A CPVOL
Explanation: The CPVOL operand was
specified for a DUMP or COpy
statement, but the last INPUT control
statement did not describe a device that
had been initialized with the
Format/ Allocate program.
System Action: If the input is from
cards or a CMS file, the program is
terminated after scanning the remaining
statements for syntax. Otherwise, the
correct statement is solicited from the
console.

(

DMK
User Response: Describe the proper
DASD device with the INPUT control
statement. If the proper input device is
defined, use the ALL operand or the
explicit cylinder operand for the DUMP
or COPY function.

701E

703E

Explanation: The above control
statement contains insufficient
informat.ion.
System Action: If the input is from
cards or a CMS file, the card image is
displayed before the message. The
prog:ram is terminated after scanning
the remaining statements for syntax.
Otherwise, the correct statement is
solicited from the console.

INVALID OPERAND - operand
Explanation: The specified operand is
invalid.
System Action: If the input is from
cards or a CMS file, the card image is
printed above the message, and the
program is terminated after scanning
the remaining statements for syntax.
Otherwise, the correct statement is
solicited from the console.

j
)

User Response: Provide the missing
operand and resubmit the job.

704E

User Response: Correct the operand
and resubmit the job.

702E

System Action: If the input is from
cards or a CMS file, the program is
terminated after scanning the remaining
statements for syntax. Otherwise, the
next statement is solicited from the
console.

Explanation: The control statement is
not in the proper sequence.

User Response: Place the control
statements in the proper sequence, or
correct the error, and resubmit the job.

DEVICE rdev NOT
OPERATIONAL
Explanation: rdev is the device address
of the unit that is not operational.

CONTROL STATEMENT
SEQUENCE ERROR

System Action: If the input is from
cards or a CMS file, the card image is
displayed above the error message. The
program is terminated after scanning
the remaining statements for syntax.
Otherwise, the correct statement is
solicited from the console. Note that all
DUMP, RESTORE, or COpy statements
must be delimited by an INPUT or an
OUTPPT control statement. When
multiple, explicit cylinder extents are
defined, the DUMP, COpy, and
RESTORE statements must not be
intermixed.

OPERAND MISSING

User Response: Either attach the
proper device to your system or redefine
the device in error. In either case, the
function control statement must be
reentered.

705E

I/O error rdev, CSW = csw,
sense = sense,
input = {bbcchhlnnnnnn},
output = {bbcchhlnnnnnn},

CCW=ccw
Explanation: An unrecoverable I/O
error has been detected on the input or
the output device, where:
rdev .
sense·

the unit address of the
device in error.
the sense bytes, in
hexadecimal, describing
the error.

Control Program (CP) Messages

197

DMK
channel status word from
the error.
bbcchh - the address (bin, cylinder,
and head), in
hexadecimal, where the
error occurred on the
input or output cylinder.
nnnnnn - the beginning block
number of the group of
blocks being read or
written when the error
occurred. Reference the
sense bytes to determine
the block in error.
ccw
the channel comm and
word from the error.

System Action: System operation
continues. The system operator is
notified. The user receives "NOT
ACCEPTED" at the display terminal.

csw

System Action: The job step is
terminated. If the output device is tape,
an attempt is made to write a trailer
label closing the output device. A
cylinder map is printed describing all
valid data that was dumped, restored, or
copied to the point of error.

User Response: None.

706E

Explanation: The command could not
be executed because the line address
specified was not enabled.
System Action: None.
User Response: Enable the line
address and reissue the command.

707E

System Action: The program loads a
disabled wait state PSW after
attemptipg to print the message.

User Response: Determine whether or
not the error was valid. If it was not
valid, resubmit the job. If the error
persists, call IBM for hardware support.

User Response: Invoke CPEREP to
document the hardware error for further
analysis of the problem. Attempt to
rerun the job. If the error persists, save
the output and contact your hardware
support personnel.

I/O error RESID = rid
status = status, line = rdev

708E
Explanation: For DMKRGA, an
unrecoverable I/O error has been
detected on the remote display station
or the remote printer.
rid

three bytes, in hexadecimal,
of the real resource
identifier.
status - two bytes, in hexadecimal,
of status/sense data
describing the error.
rdev - the unit address of the line
to which the remote station
is attached.

198

MACHINE CHECK
Explanation: A hardware error has
occurred while running in standalone
mode.

Note: This may be a valid condition if a
virtual user attempts to dump, restore,
or copy past the cylinder extents of the
minidisk with which he is working.

7051

Line rdev not enabled

VM/SP System Messages and Codes

INVALID INPUT OR OUTPUT
DEFINITION
Explanation: The INPCT and/or
OUTPUT statement is not defined or is
defined as the wrong device type. For
example, the DUMP statement must
have the input unit defined as a DASD
device and the output unit defined as a
tape device.
System Action: If the input is from
cards or a eMS file. the program is
terminated after scanning the remaining
statements for syntax. Otherwise, the

DMK
correct statement is solicited from the
console.

711R

User Response: Redefine the input or
output definition, or use the proper
function control statement.

709E

Explanation:
volidl - The volume serial number from
the input or output control
statement; volidl is displayed
only if it was entered.
volid2 - The volume serial number from
the VOLl label on the DASD
device specified by the control
statement.

WRONG INPUT TAPE MOUNTED
Explanation: The tape is invalid for
one of the following reasons:
•

There is no volume header record on
the tape.

•

The volume header record cylinder
identifier is higher than the cylinder
being searched for. If the tape was
produced from FB-5l2 data, the
volume header bloc kid is higher
than the block being searched for.

•

System Action: Waits for response.
If you respond "yes," the operation
continues.
If you respond "no," and the input is
from cards or a CMS file, the program is
terminated after scanning the remaining
statements for syntax. Otherwise, the
next statement is solicited from the
console.

The volume header record time
stamp is different from the preceding
volume trailer label time stamp.

System Action: The system rewinds
and unloads the tape; then it attempts
to read the next tape's volume header
record. If the wrong input tape is
mounted, the system rewinds and
unloads the tape, regardless of wh~ther
the REWIND, UNLOAD, or LEAVE
option was specified in the INPUT
control statement of the DASD Dump
Restore program.
User Response: Mount the proper
tape.

710A

DEV rdev INTERVENTION
REQUIRED
Explanation: rdev is the unit address
of the device that has become not-ready.
System Action: The program waits for
the specified device to become ready.
User Response: Make the specified
device ready.

VOLID READ IS volid2, NOT
volidl. DO YOU WISH TO
CONTINUE? RESPOND YES, NO,
OR REREAD:

If you respond "reread," the volume
specified is read again.
Note: A new volume may have been
mounted in the interim.

User Response: Respond "yes," "no,"
or "reread."

712E

NUMBER OF EXTENTS
EXCEEDS 20
Explanation: The DUMP or COpy
control statement has explicitly defined
more than 20 extents, or if CPVOL was
specified, the input unit has more than
20 physical extents defined.
System Action: If the input is from
cards or a CMS file, the program is
terminated after scanning the remaining
statements for syntax. Otherwise, the
next control statement is solicited from
the console.

Control Program (CP) Messages

199

DMK
User Response: Use the DUMP ALL
or COpy ALL statement, or perform the
job specifying no more than 20 extents,
and repeat DUMP or COpy if necessary
to complete the task.

713E

OVERLAPPING OR INVALID
EXTENTS
Explanation: The DUMP, RESTORE,
or COpy statement contains invalid or
overlapping explicit cylinder or block
extents.
System Action: If the input is from
cards or a CMS file, the program is
terminated after scanning the remaining
statements for syntax. Otherwise, the
correct statement is solicited from the
console.
User Response: Enter the proper
cylinder or block extent information.

714E

RECORD {bbcchhlnnnnnn} NOT
FOUND ON TAPE
Explanation: The given record was not
found on the tape.
bbcchh - the address (bin, cylinder, and
.
head), in hexadecimal, of the
missing track header record.
nnnnnn - the decimal block number of
the missir: o block.
System Action: The job step is
terminated. All data restored or copied
to that point is valid. If the input is
from cards or a CMS file, the program is
terminated after scanning the remaining
statements for syntax. Otherwise, the
next control statement is solicited from
the console.
User Response: Use the COPY ALL or
RESTORE ALL statement, or use the
correct explicit cylinder operand.

200

VMjSP System Messages and Codes

715E

LOCATION bbcchh IS A
FLAGGED TRACK
Explanation: The DASD device has a
flagged track.
bbcchh - the address (bin, cylinder, and
head), in hexadecimal, of the
flagged track.
System Action: RC = 3.
For the IBM 2314, 2319, and 2305, the
job step continues; for the IBM 3330 and
3350, the job is terminated. All data
dumped or copied to that point is valid.
The input and output devices are closed,
and a cylinder map of the data dumped
or copied is printed.
For the IBM 2305, 2314, 2319, and 3340,
flagged tracks are treated as any other
track; that is, no attempt is made to
substitute the alternate track data when
a defective primary track is read; tracks
are not inspected to determine if they
were previously flagged when written. It
is therefore recommended that volumes
dumped containing flagged tracks be
restored to the same volume.
DMKDDR715E is displayed each time a
defective track is dumped, copied, or
restored, and the operation continues.
For the IBM 3330 and 3350, flagged
tracks are automatically handled by the
control unit and should never be
detected by the program. However, if a
flagged track is detected DMKDDR715E
is displayed and the job step is
terminated.
User Response: Use the DUMP or
COpy statements with the explicit
cy linder operand to dump or copy
around the flagged track.

DMK
716R

NO VOL I LABEL FOUND FOR
volid. DO YOU WISH TO
CONTINUE? RESPOND YES, NO,
OR REREAD:'

Note: volid2 will only be displayed if it
was included in the output statement.
Also, if the output statement volid is not
the same as the target DASD volume or
the same as the input volid READ, the
volid2 in the 7l7R message may be
misleading as the origin of the volid2 is
from user responses, not a volume label
READ.

Explanation: For count-key-data, the
program was unable to find a record
with the key of VOLI on cylinder 0
track 0 and was not able to read record
3 on cylinder 0 track 0 for the specified
volume serial number (volid).

System Action: The system waits for a
response.

The volume serial number is displayed
only if specified in the INPUT or
OUTPUT control statement.

If you respond "yes," the restore
function continues.
If you respond "no" and the input is
from cards or a CMS file, the program is
terminated after scanning the remaining
statement for syntax. Otherwise, the
correct statement is solicited from the
console.

For FB-5l2 devices, block 1 on the
device could not be read.
System Action: The system waits for a
response.
If you respond "yes," the system
continues with the job steps.

If you respond "reread," the input tape
is backspaced to the start of the file,
and the volume header label is reread.

If you respond "no" and the input is
from cards or a CMS file, the program is
terminated after scanning the remaining
statements for syntax. Otherwise, the
next statement is solicited from the
console.
If you respond "reread," the program
attempts to reread the specified device.

User Response: Respond to the
message as indicated.

717R

DATA DUMPED FROM volid1 TO
BE RESTORED TO volid2. DO
YOU WISH TO CONTINUE?
RESPOND YES, NO, OR
REREAD:
Explanation:
volidl - The volume serial number of
the input tape.
volid2 - The volume serial n umber of
the output DASD device that is
to receive the data from volid1.

User Response: If the wrong input
tape is mounted, replace the tape and
respond REREAD. Otherwise, respond
in the appropriate manner.

718E

OUTPUT UNIT IS FILE
PROTECTED
Explanation: The output tape cannot
be written on.
System Action: RC = 1.
The program terminates. The tape
device is rewound and unloaded; the
system waits for the device to become
ready. When the unit is ready, the
system writes a volume header record
on the tape, and the operation
continues.
User Response: Replace the file
security ring in the tape reel, or mount
the proper tape.

Control Program (CP) Messages

201

DMK
719E

INVALID FILENAME OR FILE
NOT FOUND

721E

Explanation: This message can appear
only if DMKDDR is running under
eMS. A filetype was not entered from
the eMS command line, or the filename
and filetype entered could not be found
on the eMS files currently logged in.

Explanation: The record indicated by
cchhr was not found.
cchhr - the address (cylinder, head, and
record) of the record explicitly
descri bed by the PRINT or
TYPE function.
nnnnnn - the FB-512 block number of
the block described by the
PRINT or TYPE function.

User Response: Either omit all
operands on the eMS command line
defaulting to console input, or enter the
proper filename, filetype, and/or
filemode for the eMS file containing the
input control statements.

720E

RECORD {cchhrlnnnnnn} NOT
FOUND

System Action: The system terminates
the PRINT or TYPE function in process
and continues with the remaining job
steps unaffected.

ERROR IN routine
User Response: For count-key-data, if
the explicit record identifier is not
known, print or type on a cylinder or
track basis.

Explanation: "routine" is the name of
the eMS routine in error from the first
eight characters of the eMS parameter
list. The eMS return code generated by
the error is returned in the following
manner:
•

•

PRINTR--the eMS return code plus
100

For FB-512, correct the number and
retry.

OUTPUT UNIT NOT PROPERLY
FORMATTED FOR THE CP
NUCLEUS

722E

W AITRD--the eMS return code plus
200

•

RDBUF--the eMS return code plus
300

•

TYPE or TYPLIN--the eMS return
code plus 400

System Action: If the input is from
cards or a CMS file, the program
terminates after scanning the remaining
statements for syntax. Otherwise, the
program is immediately terminated.
User Response: Correct the error as
indicated by the return code, and
resubmit the job.

Explanation: The CP nucleus cannot
be restored or copied for one of the
following reasons:
•

The output volume was not
formatted using the Format/Allocate
program.

•

The volid of the original nucleus
volume is different from the volid of
the new nucleus volume.

•

The cylinders or pages on which the
nucleus will reside are not allocated
as permanent space in the allocation
record on the input device.

System Action: If the input is from
cards or a CMS file, the program is
terminated after scanning the remaining
statements for syntax. Otherwise, the

202

VM/SP System Messages and Codes

DMK
next control statement is solicited from
the console.

725R

User Response: Use th e
Format/Allocate program to prepare the
output disk as indicated above, and
resubmit the job.

723E

Explanation:
RESTORE FUNCTION--The number of
cy lin deI's or blocks on the original
DASD input unit is compared with the
number on the output device.

NO VALID CP NUCLEUS ON THE
INPUT UNIT
Explanation: If the input unit is tape,
then the tape does not contain a DDR
nucleus dump. If the input unit is disk,
then a CP nucleus was never loaded
onto that disk.
System Action: If the input is from
cards or a CMS file, the program is
terminated after scanning the remaining
statements for syntax. Otherwise, the
correct statement is solicited from the
console.
User Response: Mount the proper
input unit and resubmit the job.

724E

INPUT TAPE CONTAINS A CP
NUCLEUS DUMP
Explanation: The user is attempting to
restore a tape dump using the
NUCLEUS parameter by specifying
ALL or explicit extent parameters.
System Action: If the input is from
cards or a CMS file, the program is
terminated after scanning the remaining
statements for syntax. Otherwise, the
next control statement is solicited from
the console.
User Response: Use the RESTORE
NUCLEUS statement or mount the
proper tape.

DASD INPUT DEVICE WAS (IS)
LARGER THAN OUTPUT
DEVICE. DO YOU WISH TO
CONTINUE? RESPOND YES, NO,
OR REREAD.

COpy FUNCTION--The input device
contains more cylinders or blocks than
the output device.
Operator Response: Determine if the
copy or restore function is to continue;
respond either "yes" or "no."

726E

MOVING DATA INTO
ALTERNATE TRACK
CYLINDER(S) IS PROHIBITED
Explanation: An extent statement was
encountered that attempted either to
RESTORE or to COpy a cylinder of
data into the alternate track cylinder.
This is not permitted. The alternate
track cylinders of disks (except 2314 and
2319) are to be used only for alternate
tracks and not as a primary data area.
System Action: The program attempts
to read another control statement. or to
read another extent statement.
User Response: If the extent statement
contains a typographical error, correct
it. Otherwise, find some other
cylinder(s) to RESTORE or COpy the
data to. The REORDER operand of the
extent statement can be used to move an
entire minidisk to different cylinders.

Control Program (CP) Messages

203

DMK
727E

FLAGGED TRK track HAS NO
PROPER ALTERNATE;
SKIPPING THIS TRACK
Explanation: An attempt was made to
read from or write to a track that is
flagged as defective, but it has no
alternate track assigned; or it has an
alternate assigned improperly.
(Alternate does not point back to
defective track, alternate has defective
flag set, etc.)

System Action: The program ends.
User Response: Recreate the input. If
this is not possible, call your system
support personnel.

7291

System Action: The output dump tape
is created in the old format.

730E
DECODE ERROR
ENCOUNTERED:nn

System Action: If the input is from
cards. the card in error is printed and
the job step is terminated. If the input is
from the console, the proper device
address is requested from the user.

Return Codes:
First byte of input is 0 or is greater
than 5. This should not occur. It may
be caused by using a set of encoding
tables which do not match the
decoding tables which are supplied.

4 The decoding tables are malformed
or the compacted data was
incorrectly transmitted. The program
tried to decode a codeword which
could not be decoded within its first
21 bits.

204

VM/SP System Messages and Codes

DEV rdev NOT OPERATIONAL
OR NOT READY
Explanation: The device at address
rdev is not operational (SIO gave cc = 3)
or not ready (intervention required
indicated in sense data).

Explana.tion: DDR is unable to expand
data from compact format when
restoring to DASD from tape. 'nn' is the
return code from the decoding routine.

3 There is more data to be decoded, but
the output buffer is not big enough
to hold more. Decoding stopped when
the output buffer became full.

User Response: None. (This is an
informational message only.)

User Response: To restore the disk to
a usable condition, perform a disk
initialization using IBCDASDI.

FULL TRACK READ FEATURE
NOT A V AILABLE
Explanation: The FTR keyword has
been requested on the DASD
Dump/Restore DUMP control statement
but the FTR hardware feature is not
available. The output dump tape is
created in the old format.

System Action: In the case of DUMP,
RESTORE, or COpy the defective track
is skipped and processing continues
with the next track. In the case of
PRINT or TYPE, the home address and
the record zero from the defective track
are displayed.

728E

User Response: Ready the device,
attach the proper device to the system,
or specify the proper device in the
control statement.

7311

COMPACT OPTION IGNORED
FOR COpy OPERATIONS
Explanation: The COMPACT option
was specified on the INPUT control
statement or on the OUTPUT control
statement for the copy function of DDR.
System Action: The copy function
continues processing and the output

DMK
tape is in the same format as the input
tape.

)

734E

Explanation: While attempting to
allocate cylinders or extents, an invalid
control statement was encountered or
an invalid extent was specified. For
count-key-data devices, an invalid
cylinder or extent is any extent with a
starting location greater than the
ending location or greater than the
maximum number of cylinders for that
device type.

User Response: None.

732E

MACHINE CHECK
Explanation: A machine check
hardware error has occurred.
System Action: The program loads a
disabled wait state PSW after
attempting to print the message.

For FB-512 devices, the extents are
specified by page numbers. An invalid
extent is one in which the starting
number exceeds the highest page on the
volume. The valid control statements
are TEMP, PERM,TDSK, DRCT, or
END.

User Response: Invoke CPEREP to
document the hardware error so that
further analysis can be done. Attempt
to rerun the job. If the error persists,
save all output and contact your
hardware support personnel.

)

733E

System Action: If the input is from
cards, the card in error is printed and
the job step terminated. If it is console
input, the proper control statement is
requested from the user.

VOLID READ IS volidl, NOT
"Volid2
Explanation: The wrong volume is
mounted on the device described by the
ALLOCATE control statement.

User Response: Correct the control
statement or extent information and
resubmit the statement. It should be
noted that the allocation data overlays
the existing data within the allocation
record. Therefore, overlapping extents
are valid and any errors may be
corrected by resubmitting the proper
extents. If the END control statement
immediately follows the ALLOCATE
statement, the allocation table is printed
without any alterations.

volidl - the volume serial number as
read from the DASD device.
volid2 - the volume serial number from
the ALLOCATE control
statement.

Note: If volidl = "none," no record 3
was found on cylinder 0, track O.
System Action: If the input is from
cards, the card in error is printed and
the job step is terminated. If it is
console input, the proper volume serial
number is requested from the user.
User Response: Correct the
ALLOCATE control statement or mount
the proper volume on the device
described by the ALLOCATE control
statement. If "none" was given for
volid!, the pack must he formatted.

TYPE OR CYL INVALID

735E

FATAL DASD I/O ERROR.
CSW=csw
Explanation: An unrecoverable error
was encountered on the DASD being
formatted.
System Action: The job step is
terminated immediately and the next
control st.atement is read.
User Response: Check message
DMKFMT736E, displayed just prior to

Control Program (CP) Messages

205

DMK
~

this message, to determine the extent
and type of failure.

7S6E

console. When an interrupt is received
from either the card reader or the
console, that unit is solicited for the
next control statement.

10 ERROR rdev CCHHR = cchhr

SENSE = sense

User Response: Correct the error as
indicated on the card reader and make
the device ready, or switch to console
input by signaling attention.

Explanation: An I/O error has been
detected.
rdev - the unit address of the
device in error.
cchhr - the cylinder, head, and
record identification of the
record in error.
sense - the sense bytes, in
hexadecimal, describing the
error condition.
nnnnnn - the block number of the
block error.

739E

User Response: Resubmit the job. If
the error persists, call your system
support personnel.

System Action: Error messages
DMKFMT736E and DMKFMT735E
follow immediately. The CCHHR
address given in message
DMKFMT736E identifies the defective
track.

INVALID OPERAND
Explanation: An operand is in error; it
can be seen in the card image displayed
following the message.
System Action: A card image
containing the error is printed following
the message, and the job step is
terminated.
User Response: Correct the invalid
operand in the control statement and
resubmit the job.

738A

DEVICE rdev INTERVENTION
REQUIRED
Explanation: Intervention is required
on the device at address rdev.
System Action: The system waits for
an interrupt from the card reader or

206

VM/SP System Messages and Codes

FLAGGED PRIMARY TRACK
HAS NO ALTERNATE
ASSIGNED, 10 ERROR
FOLLOWS
Explanation: An I/O operation was
attempted on a track that is flagged
defective, but has no alternate track
assigned to it. Or an improper alternate
assignment exits as follows: The CCHH
pointer in record zero of either the
defective or the alternate does not point
to the other track of the pair. Or one of
the two tracks has bits 6 and 7 of the
home address flag byte improperly set.

System Action: The job step is
terminated and the next control
statement is read.

737E

(

User Response: To restore the disk to
a usable condition, perform a disk
initialization using IBDASDI.

(

I"
740E

PACK MOUNTED IS 3340-35, NOT
3340-70. MOUNT ANOTHER OR
RESPECIFY
Explanation: The user indicated that
the device i~ a 3340-70, but the sense
data indicates that a 3340-35 disk pack
is actually mounted. A 3340-35 pack has
fewer cylinders than a 3340-70 and
cannot be formatted as a 3340-70.
However, a 3340-70 can be formatted as
a 3:-340-a5.

System Action: If the input is being
entered from a console. the user is

DMK
prompted to reenter the device address
and device type. If the input is from
cards the card in error is printed and
the job step is terminated.

742E

Explanation: The label found on the
specified volume does not contain the
keyword 'CP370'.

User Response: Correct the unit
address or device type. Or mount a
3340-70 disk pack in place of the 3340-35.

741E

System Action: If input is from a
console, the user is prompted to re-enter
FORMAT or ALLOCATE. If input is
from cards, the card in error is printed
and the job is terminated.

DEVICE rdev IS devtypel NOT
devtype2 AS SPECIFIED.
RESPECIFY OR NOTIFY
SYSTEM SUPPORT

User Response: Format the volume
using FORMAT function, then allocate
the volume using the ALLOCATE
function.

Explanation: The incorrect device type
was entered.
rdev
devtypel

devtype2-nn

The unit address of the
device type in error
The device type that
should have been
specified
The device type and
model that was specified

ALLOCATION FUNCTION NOT
ALLOWED

DIAL function not available

743A

Explanation: The DIAL command
cannot be issued from this station or
terminal.
System Action: System operation
continues.

System Action: The following prompt
is displayed to allow the user to re-enter
the device address:

User Response: None.

ENTER DEVICE ADDRESS (CUU):

User Response: Check previously
entered device address. If it is correct,
re-enter the address. The following
prompt will then be displayed.
ENTER DEVICE TYPE:

message, please re-enter this
command

747A

Explanation: The multiple variations
of 'message' are explained below.
•

Device rdev vary in progress
Explanation: If a VARY OFF/ON
is in progress for this device, this
message is sent to the class Buser
and no SIO is issued.

•

Csw = (csw)[, Sense = (sense)]
Explanation: For some unknown
temporary error, the
channel-end/device-end status is not
presented~ and no other clue can be
found to determine the status of this
SIO. If the sense data is not
available. only the CSW data is
displayed.

Enter the device type indicated by
devtype in the message text.
If the previously entered device address

is incorrect, enter the correct device
address, and enter the correct device
type in response to the ENTER DEVICE
TYPE: prompt.
If error persists, check that the real
device matches the device type entered.
If it does, call system support personnel.

Control Program (CP) Messages

207

DMK
•

•

System Action: Directory updating
is not done.

Error encountered, no
IOERBLOK can be found
Explanation: A disk error
occurred, but no IOERBLOK can be
found.
Device unit check - no sense data
is found Explanation: This
message will be issued when a unit
check occurs for the device, but no
sense data is presented. (i.e.,
IOERLEN = 0).

User Response: Change the record
length of RPWLIST DATA to eight
and reissue the command.

750W

Explanation: The restricted password
file (RPWLIST DATA) is missing.

User Response: In each case, reissue
the QUERY STATUS command.

750E

RESTRICTED PASSWORD FILE
NOT FOUND

System Action: Directory processing
continues without checking for
restricted passwords. The directory is
updated.

RESTRICTED PASSWORD FILE
message

User Response: Determine if an
RPWLIST DATA file is needed. If
restricted password checking is desired
and the file is not found, refer to the
VM/ SP Planning Guide and Reference,
SC19-6201 to create one.

The following messages may be
issued:
, ERROR DURING READ
Explanation: An error occured
while attempting to read the file.
751E
System Action: Directory updating
is not done.
User Response: Contact your
system programmer.

INVALID OPERAND - operand
Explanation: This message was issued
because of one of the following reasons:
•

The indicated operand is invalid in
the preceding DIRECT or
OVERRIDE control statement.

Explanation: The RPWLIST DATA
file is variable format, but only fixed
format is allowed.

•

The profilename on the PROFILE
statement or the INCLUDE
statement exceeds eight characters.

System Action: Directory updating
is not done.

•

A profilename has been specified in
an INCLUDE statement for which
there is no corresponding PROFILE.

•

More than one profilename has been
specified on an INCLUDE statement
or PROFILE statement.

HAS BAD RECORD FORMAT

User Response: Change the record
format of RPWLIST DATA to fixed
and reissue the command.
HAS BAD RECORD LENGTH
Explanation: The RPWLIST DATA
file has a record length less than
eight.

System Action: The system displays
the statement in error immediately
preceding this message.
For the Directory program or Override
program, the system continues

208

VM/SP System Messages and Codes

DMK
processing the control statements but
does not write any data to disk or
install any overrides.

)

statement in a virtual machine
directory description.
•

User Response: Correct the invalid
operand in the control statement and
reissue the command.

System Action: The statement that is
out of sequence is displayed after this
message. Directory processing is
terminated after the remaining
statements are scanned for syntax.

STATEMENT SEQUENCE ERROR
FOLLOWING PROFILE/ USER
user

752E

Explanation: This message is issued
for one of the following reasons:
•

A USER definition control
statement was determined to be out
of sequence following the specified
user.

•

A CLASS statement was specified
after the USER statement but the
CLASS definitions are already
defined in the USER statement.

)

Note: The USER control statement
delimits each virtual machine directory
description. Therefore, the USER
statement must follow the last device
description statement, and each
OPTION, ACCOUNT, or IPL statement
must fall between the USER statement
and the first statement describing a
device. Each CLASS statement must
immediately follow the USER statement.

With the exception of dummy (NOLOG)
users, all users in the directory must
have at least one device.

For the Directory program, one of the
following happened:
•

•

User Response: Place the control
statements in the proper sequence or
correct the error, and resubmit the job.

An OPTION, ACCOUNT,
ACIGROUP, CLASS, SCREEN or
IPL statement was not between a
USER or PROFILE statement and
the first statement describing a
device for the virtual machine
directory description.
A PROFILE statement was
immediately following a USER
statement or another PROFILE
statement.

•

A PROFILE statement was
preceding the DIRECTORY
statement.

•

An MDISK or INCLUDE statement
was in a PROFILE directory
descri ption.

•

An INCLUDE statement did not
immediately follow the USER

A duplicate ACIGROUP or
INCLUDE statement was found in a
PROFILE or USER virtual machine
directory description.

If a CLASS statement is specified, an
asterisk ('*') must be in the CLASS field
of the USER statement.

753E

OPERAND MISSING
Explanation: Insufficient information
is contained in a DIRECT or
OVERRIDE control statement, or
password missing from user control
statement.
System Action: The card image is
displayed above the error message. The
program is terminated after scanning
the remaining statements for syntax.
User Response: Provide the missing
operand in the control statement and
reissue the command.

Control Program (CP) Messages

209

DMK
DEV rdev NOT OPERATIONAL

7S4E

756E

PROGRAM CHECK PSW

psw

Explanation: A program check has
occurred in the program, where psw is
the program check old PSW.

Explanation: The device at address
rdev is not operational.
System Action: The program is
terminated after scanning the remaining
statements for syntax.

System Action: The program goes into
a disabled wait state after attempting to
display the message.

User Response: Either
1.
2.

7SSE

Attach the proper device to the
system, or
Specify the proper device in the
DIRECTORY control statement (for
the DIRECT command) or the
DESTINATION control statement
(for the OVERRIDE command).

User Response: Take a stand-alone
dump, and call your system support
personnel.

757E

Explanation: A hardware error has
occurred while running in standalone
mode.

I/O ERROR rdev CSW csw SENSE
sense

System Action: The program loads a
disabled wait state PSW after
attempting to print the message.

Explanation: An I/O error has been
detected.

User Response: Invoke CPEREP to
document the hardware error, so further
analysis can be done. Attempt to rerun
the job. If the error persists, save all
output and contact your hardware
support personnel.

rdev - the unit address of the device in
error.
csw - the channel status word from
the error.
sense - the sense bytes, in hexadecimal,
describing the error condition.
System Action: If the error is from the
card reader, the program waits for the
reader to become ready again. If the
error is from the directory volume, the
program no longer attempts to write on
that volume (ensure that the program
has write access to the directory
volume). In either case, the program
attempts to scan the remaining cards for
syntax and then is terminated.
User Response: Resubmit the job. If
the error persists, call your system
support personnel.

MACHINE CHECK

7SSE

DUPLICATE UNIT DEFINITION
Explanation: The control statement is
defining a device with a device address
that was previously defined for the same
user.
System Action: The card image is
displayed above the message. The
program is terminated after scanning
the remaining statements for syntax.
Note that checking for duplicate devices
may be suspended for an individual user
after the first 90 device control
statements.
User Response: Remove or correct the
duplicate definition, and resubmit the
job.

210

VMjSP System Messages and Codes

DMK
760E

NOT ENOUGH SPACE
ALLOCATED FOR DIRECTORY

statement, or mount the proper volume
on the device described by the
DIRECTORY or DESTINATION control
statement.

Explanation: There is insufficient
space on the target volume to continue
building the directory or override file.
762E
System Action: The program is
terminated after scanning the remaining
statements for syntax. Writing is
suspended on the target volume. The
message is reissued for each additional
cylinder of count-key-data space needed
by the directory program. It is not
reissued for FB-512 devices.
User Response: Using the
Format! Allocate program, allocate more
DRCT space for a directory file, or
OVRD space for an override file. Note
that the Directory program always
starts building a new directory on a
fresh cylinder or separate extent and
does not overlay an existing directory
written on the directory volume. After
the directory is successfully updated,
the space used by the old directory is
marked as available for use by the next
directory to be created. The override
file normally requires only one cylinder
on a CKD device.

761E

VOLID READ IS volidl NOT
volid2 ON rdev
Explanation: The wrong volume is
mounted on the device described by the
DIRECTORY or DESTINATION control
statement.
volid! - the volume serial number from
the directory volume.
volid2 - the volume serial number
described by the DIRECTORY
statement.
rdev - the address of the device on
which the device is mounted.
System Action: The program is
terminated after scanning the remaining
statements for syntax.

DIRECTORY STATEMENT
MISSING
Explanation: The first control
statement detected by the program was
not a DESTINATION (for OVERRIDE
program) or DIRECTORY (for DIRECT
program) control statement.
System Action: The program is
terminated after scanning the remaining
statements for syntax.
User Response: For the DIRECT
program, place the DIRECTORY
statements in front of the other control
statements, and reissue the command.
For the OVERRIDE program, place the
DESTINATION statements in front of
the other control statements, and
ressi ue the command.

763E

INVALID FILENAME OR FILE
NOT FOUND
Explanation: The filename and/or
filetype and/or filemode specified on the
CMS command line could not be found
on an accessed CMS disk.
For the DIRECT program, the default
filename, filetype, and/or filemode is
'USER DIRECT *'.
For the OVERRIDE program the
filename is regular but the filetype
defaults to 'OVERRIDE' and the
filemode defaults to '*'.
If you are using the directory program,

an error occurred while reading the
RPWLIST DATA file or the directory
file was not found.
System Action: RC = l.
Execution is terminated.

User Response: Correct the
DIRECTORY or DESTINATION control
Control Program (CP) Messages

211

DMK
Exit from the program and return to the
CMS environment.

but does not write any directory data to
disk or install any overrides.

User Response: If the problem is an
invalid filename, reenter the command
with the proper name for the CMS file
containing the
DIRECTORY /OVERRIDE control
statements.

User Response: Correct the control
statement containing the incorrect class
value and reissue the command.

766E

If you are using the directory program,
check the RPWLIST DATA file for CMS
read errors.

764E

Explanation: A class was specified
more than once when the IBM-defined
classes were defined. Examples of when
this error occurs are:

ERROR IN routine

•

Explanation: 'routine' is the name of
the CMS routine in error from the first
eight characters of the eMS parameter
list. The CMS return code generated by
the error is returned in the following
manner:

•

System Action: The program is
terminated after scanning the remaining
statements for syntax.

User Response: Correct the control
statement which duplicates the class
value. After you have ensured that
class was specified only once, resubmit
the job.

User Response: Correct the error as
indicated by the CMS return code, and
resubmit the job.

INVALID CLASS DEFINITION
767W
Explanation: The class value is not in
the range A-Z or 1-6, or is not "*". This
class value is specified in the CLASS
field of the USER control statement, the
CLASS control statement, or, for the
OVERRIDE program, an override
control card.
System Action: The system displays
the statement in error immediately
preceding this message. The program is
terminated after the system scans the
remaining statements for syntax. The
system processes the control statements

212

A class was specified twice on a
USER control statement.
A class was specified twice on a
CLASS control statement.
A class was specified twice on an
OVERRIDE control statement.

System Action: The system displays
the statement in error immediately
preceding the message. The program is
terminated after the system scans the
remaining statements for syntax. The
system processes the control statements
but does not write any data to disk or
install any overrides.

RDBUF - the CMS return code plus 100.
TYPLIN - the CMS return code plus
200.

765E

DUPLICATE CLASS DEFINITION

VM/SP System Messages and Codes

PASSWORD CHANGED TO
NOLOG FOR userid
Explanation: The password for 'userid'
was found on the list of restricted
passwords. It has been changed to
NOLOG in the object directory.
Systeln Action: Directory processing
continues.
User Response: The password must be
changed to a non-restricted password
before the specified user will be allowed
to access the system.

DMK
768E

)

FOR userid - MOVE vdev TO A
(NON)SHARED veu

769W

Explanation: The failing directory
control statement (displayed above this
message) would have caused a mixture
of SHARED and NONSHARED devices
on the same Virtual Control Unit
(VCU). A previous directory control
statement has already reserved the
virtual control unit for use with a
conflicting subchannel protocol.

Explanation: During LOGON, some of
the devices specified in your CP
Directory Entry could not be created.
These devices may be important to the
operation of your virtual machine (e.g.
OOE is the CMS printer).
System Action: Previous messages
specify the action that has been taken
(i.e. at least one device was not created),
At this point the system only prints a
warning that the virtual machine is not
complete.

userid - the userid from the last USER
control statement
vdev

)

- the virtual device address
where the device would be
defined

User Response: Tell your local System
Administrator or System Support
department about this problem, and
describe each message that appeared
between your LOGON command and
this warning message.

vcutype - the VCU protocol needed for
device 'vdev'. It is one of the
following:
1.

SHARED, where a shared
subchannel is required
NONSHARED, where a
nonshared subchannels are
required

770E

'command~.

User Response: Examine all of the
devices for this userid that use the same
virtual control unit. Move conflicting
devices to separate virtual control units.

Refer to Appendix A in the VMjSP
Planning Guide and Reference for the
list of devices and protocol.

Override in valid for command
Explanation: During system
initialization, the system was unable to
implemment an override request for the
CP command or diagnose indicated by

System Action: Directory processing
continues, but no update is performed.

The virtual control unit (VCU) is
available for use in either mode
(SHARED or NONSHARED) until a
device is attached. At this point the
VCU is defined as SHARED or
NONSHARED (to match the attached
device) and only those devices that use
the same protocol may be added to the
VCU. If all devices are removed from
the VCU, it is once again available for
use in either mode.

Incomplete machine - tell your
system administrator

System Action: Processing continues
with the next OVERRIDE control
statement record.
User Response: Correct the invalid
control statement in your class override
source file and reissue the OVERRIDE
command. New overrides do not take
effect until the next IPL.

771E

RESTRICTED PASSWORD AND
NOLOG INVALID FOR userid
Explanation: A restricted password
was found on the user card for the
person issuing the Direct command.
This userid should not be NOLOGed as
there may be no other users capable of
issuing the Direct command. If this
user is NOLOGed, it is possible that

Control Program (CP) Messages

213

DMK
there could be no users able to logon to
modify the directory.

7821

System Action: Directory checking
continues, but no directory update takes
place.

Explanation: The DMSFREE routine
did not return the space correctly
during exit processing.

User Response: Change the password
to a non-restricted password so the
directory updates will be accepted.
Restricted passwords listed in the
RPWLIST DATA file should not be
used.

System Action: Exit processing
continues.
User Response: None.

800E
780E

Maximunl password attempts
exceeded, try again later

782E

Command rejected, other virtual
machines logged on
Explanation: Virtual machines, other
than the V = R machine and the system
operator's, were logged on.

Explanation: The user has entered an
invalid logon password more times than
is allowed by the installation.

System Action: None.

System Action: The user and terminal
are locked out for a length of time that
is specified by the installation before
another logon attempt is allowed.

Operator Response: Reissue the
command after establishing that only
the two valid machines are logged on
the system.

User Response: The user must wait
until the time lock expires before
attempting to logon. Otherwise, this
message will be issued again.

ERROR ATTEMPTING TO
RETURN FREE STORAGE

80lE

Explanation: Free storage cannot be
obtained for saving the CP PSA,
therefore, the transition was not made.

ERROR ATTEMPTING TO GET
FREE STORAGE

System Action: None.

Explanation: The DMSFREE routine
could not find the space necessary to
hold the restricted password list.
System Action: Directory updating is
terminated.
User Response: Reissue the command.
If it fails again, contact your system
support personnel.

Free storage page is not available

Operator Response: Reissue the
command when more free storage is
available.

802E

Command rejected, devices not
dedicated
Explanation: All devices (except the
console and virtual spooling devices)
must be dedicated devices.
System Action: None.
Operator Response: Reissue the
command after verifying that all devices
are dedicated.

214

VM/SP System Messages and Codes

(

DMK
803E

Operator Response: Reissue the
command after this condition is
corrected for the V = R virtual machine.

Command rejected, spool devices
not drained
Explanation: All CP spool devices
have not been drained.
807E
System Action: None.

Command rejected, VM/370
attached processor mode
Explanation: VMjSP was not in
uniprocessor mode.

Operator Response: Reissue the
command after all CP spool devices
have been drained.

System Action: None.
Operator Response: Issue the QVM
command when the system is in
uniprocessor mode.

Single processor mode ON
rejected

804E

Explanation: Single processor mode
was not established because of one of
the following:
1.
2.
3.

8081

The system is not in uniprocessor
mode.
There is no V = R area.
There is no multiprocessor feature

SINGLE PROCESSOR MODE
ACTIVE
Explanation: Whenever. single
processor mode is turned on, the value
loaded into to prefix register by the
system is displayed.

System Action: None.
System Action: None.
Operator Response: Use the SPMODE
ON command only when the proper
conditions are satisfied.

Operator Response: None.

809E
805E

Single processor mode OFF
rejected
Explanation: Single processor mode
has not been reset because V = R virtual
machine has a nonzero value.

Command rejected,
TRACE/ADSTOP/CCW
translation in effect
Explanation: The transition cannot be
made for the V = R virtual machine if
tracing. adstop. or CCW translation is
being used.

System Action: None
System Action: None.
Operator Response: Use the SPIVIODE
OFF command only if the proper
conditions are satisfied.

806E

Operator Response: Turn off tracing,
ads top, or CCW translation for the
V -:.-.:. R virtual machine and reissue the
(~V M command.

Command rejected. virtual
address not equal to real address
Explanation: The virtual devicl'
address was not the same a::; the real
device address.
System Action: None.

Control Progl'am (CP) Messages

215

DMK
812E

MSSF RESPONSE CODE TO
VARY CP {ONIOFF} IS nnnn

8501

UNABLE TO READ DUMP FROM
READER
Explanation: The VMFDUMP
command was unable to read the
3704/3705 dump or the system abend
dump from the CP spool file through the
CMS card reader. This could be
because:

Explanation: A vary processor on/off
was issued by the operator and the
MSSF returned an error code of nnnn to
the MSSFCALL VARY CP ON/OFF
operation.
where:

•
•

nnnn is the MSSF return code to VARY
CP ON/OFF command.

•
Code Meaning
0000
0040
0100
01FO
0200
02FO
0300

03FO
04FO
05FO
08FO

Invalid data block address
MSSF is unable to vary on the
control program (CP)
Data block address is not on a 2k
boundary
Invalid command or identification
byte
Data block length is not in 8-byte
increments
MSSF is busy with another task
Data field is not adequate for
amount of requested storage
information
Invalid CP identifier
CP assigned to another partition
CP assigned to a S/MR
configuration
For VARY CP ON code only. The
number of CP's in the
configuration equals maximum
number supported.

User Response: Verify that the virtual
machine configuration is correct for
performing a VMFDUMP operation and
that the card reader at OOC is a spool
card reader in closed status.

8511

Note: If this message is received for a
VARY processor online, the VARY
command fails and the system continues
to operate in UP mode.

216

VM/SP System Messages and Codes

TEN DUMP FILES ALREADY
EXIST
Explanation: The command has not
been executed because ten dump files
with names DUMPOO through DUMP09
already exist on the CMS disk being
accessed.
System Action: The command is
terminated.
User Response: Purge one or more of
the unwanted dump files or rename any
of the existing dump file using the CMS
RENAME command. Reissue the
command so that a dump file can be
automatically created.

System Action: Processing continues
for a VARY OFFLINE command. The
proce::;sor is logically offline to VM/SP.
For a VARY ONLINE command, the
system continues to run in UP mode.
Operator Response: None.

The reader is not at address OOC,
The reader at OOC is already in open
status from a previous operation, or
The device in the virtual machine at
OOC is not a CP spool card reader
device.

8521

FATAL 1/0 ERROR WRITING
DUMP
Explanation: An unrecoverable I/O
error occurred during the writing of the
3704/3705 dump or the system abend
dump on the CMS disk being accessed.
The message is preceded by CMS error
messages for the disk function.

DMK
User Response: Reissue the command
after taking action to bypass the I/O
errors on the CMS disk being accessed.

8531

NO DUMP FILES EXIST

User Response: Reissue the command;
specify only valid options as defined in
the command syntax.

8701

Explanation: The VMFDUMP
command was specified, and the return
from the CP interface indicates that no
dump files exist for this user.
User Response: Verify that the dump
files produced by the CP system have
the userid and the class required, and
that this user's userid and class on the
card reader match that of the dump, so
that a dump file can be read. If no dump
files exist, VMFDUMP does not have to
be issued. If the dump file exists under
a different userid, have the operator
transfer that file to the required userid,
so that it can be accessed. Also, verify
that the input class of the spool card
reader at OOC is class D, so that it can
read the dump file.

861E

DUMP FILE fn NOT FOUND
Explanation: The command was
specified requesting a printout of a
specific dump file, and that file could
not be found on the CMS disks that
were currently accessed.
User Response: Verify that the correct
dump file was specified and that the
correct disks are accessed by CMS.
Then reissue the command, requesting
the specified dump file.

8631

INVALID PARAMETER parameter
Explanation: The command was
specified with a list of options, one of
which is not recognized by the
command.
System Action: The command is not
executed.

UNABLE TO CREATE CONTROL
FILE FOR IFLDUMP
Explanation: FSWRITE command
failed to create the dump control file
DUMPnn SYSIN AI, that is associated
with the NCP dump file DUMPnn
NCPDUMP AI.
System Action: RC = 16.
The file is el'ased if it exists. The
program returns to the caller routine.
User Response: Correct the DUMPnn
SYSIN Al file and retry. If necessary,
contact support personnel.

900W

SYSTEM RECOVERY FAILURE;
PROGRAM CHECK
Explanation: The system checkpoint
routine encountered a program check
while trying to checkpoint or warm
start the system.
System Action: The system enters a
disabled wait state (wait state code 007).
Note: The program old PSW and the
program interrupt code are restored to
the values at the time of the program
check, and the general register values
are saved in TEMPSA VE before
entering the wait state.

Operator Response: This message
usually indicates severe system
problems with the spooling files, system
accounting data, or other system data
needed for warm start. It is usually
impossible to continue system operation
without clearing storage and performing
a checkpoint start. If a system dump to
printer or tape preceded this message,
the system programmer has enough
information to determine the cause of
the failure and the resultant program
check during system recovery, The first

Control Program (CP) Messages

217

DMK
55,296 bytes (hex D800) of storage
contain the checkpoint modules and
buffers used by checkpoint. This area
should be dumped using a standalone
dump. If ~ system dump to printer or
tape did not precede this message, do a
complete storage dump.

SYSTEM RECOVERY :FAILURE;
MAClIINE CHECK

901W

Expla.nation: During the system
recovery checkpoint or warm start
phase, a machine check occurred.
System Action: The system enters a
disabled wait state (wait state code 007).
Operator Response: IPL the system to
retry the checkpoint function. If the
failure persists, it usually indicates
hardware problems. Keep the SEHEP
output and call your local
representative for assistance. Do not
use the SEREP program on 308x, 9083,
and 4341 processors as you will get
invalid results.
Notes:
1.

902W

If the failure occurred during the
checkpoint phase (system shutdown,
systern crash or an IPL with an
active system in storage), a CKPT
start is required if storage is cleared
or overlaid.
If the failure occurred during an
attempt to warm start, ()KPT start,
or force start, the warm start data or
the warm start cylinder(s) remains
intact.

SYSTEM RECOVERY FAILURE;
FATAL I/O ERROR
{NUCLEUSIWARM} AREA
Explanation: During the system
checkpoint or warm start phase, an
unrecoverable input/output error
occurred on the system residence
volume.

218

VM/SP System Messages and Codes

NUCLEUS AREA
The warm start phase had an I/O
error on the system residence device
trying to read module DMKSA V
from the nucleus area.
WARlYl AREA
The checkpoint phase had an I/O
error on the system residence device
trying to read from or write to the
warm start area.

System Action: The system enters a
disabled wait state (wait state code 007).
Operator Response: IPL the system to
retry the checkpoint or warm start
function. If this is unsuccessful, move
the IPL volume, if possible, to another
drive and retry the IPL. If the problem
persists, dump the flrst 55,296 bytes
(hexadecimal D800) of storage using a
standalone dump.
For FB-512 devices, dump the first
55,296 bytes (hexadecimal D800) of
storage using a standalone dump.
Notify your system programmer to
determine the proper nucleus or warm
start area specified in module DMKSYS
(SYSRES statement) at system
generation time.
The nucleus or warm start area can be
dumped to tape or printed to the system
printer by using DDR (DASD Dump
Hestore program) with the DUlVIP or
PRINT option. The output should be
available before calling for hardware or
program assistance.
The foilowing ~torage locations cOlJ.tain
information relah~d to wait state 007 for
the non-V· . R systt'm.

Hexadecimal
Location
Contents
]0
Sense data up to ~4 bytes
Channel status word (8
40
bytes)
4H
Channel address word (4
bytes)

(

DMK
FFS
FFC
1016

lOIS

1000-6FFF
7000-DSOO

Length of error message
(4 bytes)
Pointer to error message
(4 bytes)
Cylinder address of the
first nucleus cylinder (2
bytes) (CKD only)
Cylinder address of the
last nucleus cylinder (2
bytes) (CKD only)
Checkpoint program
Checkpoint work area

•

The possible causes are:

If the SYSRES device is FB-512
(RDEVTYPC = CLASFBA), the contents
of the following hexadecimal locations
are changed:

1016

1022

If the nucleus area is reformatted, the
CP nucleus must be restored to the
system volume.

The status of the console can prevent
the display of message
DMKCKP960I and DMKCKP961lV.

903W

System recovery failure; volid
volid allocation error {cylinder
cclpage page}
Explanation: During a system warm
start or CKPT start phase, one of the
warm start or CKPT start data records
indicates allocation on a cylinder
(count-key-data) or page (FB-512) on a
system-owned volume that either:
•

Is not specified in the allocation
table as belonging to the system
temporary spool space allocation. or

A change in the system-owned list.
(New volumes must be added to the
end of the SYSOWN list when you
define the SYSOWN MACRO.)

•

A change to the allocation record on
a spooling volume from TEMP to
PERM, TDSK or DRCT
(Format/ Allocate program).

•

Duplicate labeled volume.

Operator Response: IPL the system
again to attempt another warmstart or
CKPT start. The start cannot complete
if the allocation error is due to a
software failure. This message, however,
could be issued if the volume identified
as being a spooling volume is invalid.
Verify that all system spooling volumes
are correctly mounted before attempting
another warmstart or CKPT start. If all
else fails, force a CP abend dump to the
printer by pressing the RESTART key.
IPL the system again, specifying CKPT
start.

Notes:
It may be necessary to format the
area in error using the Format
service program.

•

System Action: The system enters a
disabled wait state (wait state code 009).

Block address of the first
page of the CP nucleus (4
bytes)
Block address of the last
page of the CP nucleus (4
bytes)

Is already marked as allocated.

904W

System recovery failure; invalid
warm start data
Explanation: During a system
warm-start procedure, the warm start
module encountered invalid warm start
data from the warm start area on the
system residence volume.
System Action: The system enters a
disabled wait state (wait state code 009).
Operator Response: This message
indicates that severe problems have
been encountered with the warm start
information in the warm start area on
the system residence volume. You may
IPL the system again to retry operation.
It is likely that a software failure has

Control Program (CP) :Messages

219

DMK
occurred and that retrying the operation
will result in the same error. When this
happens, the only alternative is to IPL
the system and specify a CKPT start. If
the problem persists, do the following:
•

Force a CP abend dump to the
printer by pressing the REST ART
key.

•

Print the contents of the warm start
area located on the system residence
volume using the DASD Dump
Restore program with the PRINT
option.

procedures. Do not use the SEREP
program on 308x, 9083, and 4341
processors as you will get invalid
results.

907W

Explanation: During the system abend
dump procedure, an unrecoverable I/O
error occurred on the volume that is
holding the disk dump. The system
dump is unable to continue.
System Action: The system enters the
wait state.

Save this output and give it to the IBM
program support representative to
analyze.

905W

System Action: The system enters a
wait state.

906W

9081

SYSTEM FAILURE; CODE - code
PROCESSOR nn

Operator Response: The dump has
failed, and you must IPL the system
again after the abend dump and go

Explanation: The CP system has
encountered a severe software failure,
which caused Ii system dump. (Look up
the 'code' in Figure 9 on page 34 to see
why a system dump occurred.)

through normal system initialization
and warm start procedures.

Notes:
1.

Message will not print if the console
is busy or has been detached, but the
system abend dump will still
complete.

The processor address is displayed in
decimal format.

System Action: The system enters the
wait state.

The software failure can be caused by
a hardware problem.

Operator Response: Run the SEREP
program and keep the output before
calling IBM for hardware support;
reload the system and go through
normal initialization and warm start

System Action: This message is
immediately followed by a system abend
dump to the dump device, and then
automatic or normal restart procedures
are initiated.

SYSTEM DUMP FAILURE;
MACHINE CHECK
Explanation: During the system
ABEND dump procedure. a machine
check occurred.

220

Operator Response: No action can be
taken at this point to recover the system
dump data. You should reload the
system, go through the normal
initialization procedures, and perform a
system warm start.

SYSTEM DUMP FAILURE;
PROGRAM CHECK
Explanation: During the system abend
process, the dump routine encountered a
program check.

SYSTEM DUMP FAILURE;
FATAL I/O ERROR

VM/SP System Messages and Codes

(

DMK
Operator Response: On 4300
processors, verify that you did not IML
a VSE microcode load. Otherwise. save
the failure code printed at the console,
including the documentation of activity
prior to the problems with system
operation, and call IBM for software
support.

909W

System Action: The system enters a
disabled wait state (wait state code 007).
Operator Response: If more t.han one
VM/SP system residence volume is
mounted, make sure the correct volume
is loaded (via IPL) to checkpoint the
in-storage system. If the problem
pers.ists, the following should be done:

SYSTEM DUMP DEVICE NOT
READY

•

A dump of storage using a
standalone dump.

Explanation: It is not possible to write
on the system dump device because it is
not in a ready state.

•

A printout of record one of the

warm start cylinder of all VM/SP
system residence volumes mounted
(use the DDR PRINT function).

System Action: The system enters a
wait state.

•

Operator Response: Make the system
dump device ready; the dump operation
then continues.
91lW
910W

SYSTEM RECOVERY FAILURE;
INVALID WARM START AREA
Explanation: During a system
checkpoint phase~ the checkpoint
module reads record one of the first
warm start area and compares the
eight-byte clock value written by the
previous successful cold or warm start
against the in-storage value saved in
DMKRSPCV. If the values do not
agree:
•

The IPL volume is not the correct
volume to checkpoint the in-storage
system, or

•

The warm start area has been
altered since the last cold or warm
start, or

•

The value located at DMKRSPCV in
storage has been altered since the
last cold or warm start, or
The warm start area address at
DMKSYSWM has been altered since
the last cold or warm start.

To restart, clear storage and IPL the
VM/SP system, specifying
checkpoint start.

SYSTEM RECOVERY FAILURE;
WARM START AREA FULL
Explanation: During a system
checkpoint phase, the warm start area
could not contain all the warm start
data.

System Action: The system enters a
disabled wait state (wait state code 007).
Operator Response: This message
usually indicates either:
1.

A system problem with the spooling
files, system accounting data,
allocation records and other system.
data needed for the warm start area,
or

An insufficient number of cylinders
assigned for warm start (specified in
the DlVIKWRM option of the
SYSRES macro).

It is usually impossible to continue
system operation without clearing
storage and performing a system
checkpoint start. If a system dump to
printer or tape preceded this message, it
should give the system programmer

Control Program (CP) Messages

221

DMK
enough information to determine the
cause of the failure and the resultant
checkpoint failure. The first 55.296
bytes (hexadecimal D800) of storage
contain the checkpoint module, work
area, and a 4096-byte buffer used by
checkpoint (DMKCKP).

PRINT option. The address of the
warm start cylinder(s) or area can
be located by the system
programmer in the SYSWRM
operand of the SYSRES macro; the
address of the checkpoint start
cylinder(s) or area is in the SYSCKP
operand.

For FB-512 devices, the first 55,296 bytes
(hexadecimal D800) of storage contain
the checkpoint modules, work areas,
and I/O buffers.
If the problem persists, call your system
support personnel.

912W

Save this output and c~ll IBM for
software support.

9131

Explanation: 3850 support makes no
provision for using 3330V volumes for
CP-owned volumes. 3330V volumes
cannot be used for paging or spooling.

System recovery failure; volid
volid not mounted
Explanation: During the system warm
start 01' checkpoint start procedures, the
warm start or checkpoint start data
indicates that spool files are allocated
on a system volume and that the
requested volume is not mounted.

System Action: After a 3330V volume
label has been read and determined to
be CP-owned, an informational message
is issued. The
RDEVBLOK/RCUBLOK/RCHBLOK is
marked available and processing
continues with the next device. The
message notifies the user that DMKCPI
does not chain the 3330V RDEVBLOK
into the preferred list for paging or
spooling.

The possible causes are:
•
•

Volume not mounted.
Allocation record (record 4) missing
or invalid.

System Action: The system enters a
disabled wait state (wait state code 009).
Operator Response: Mount the
specified volume required for CP warm
start or checkpoint start procedures and
IPL the system again. If this is
unsuccessful, you may IPL the system
again and specify a cold start. If the
problem persists, do the following:

222

•

Force a CP abend dump to the
printer by pressing the REST ART
key.

•

Print the contents of the warm start
or checkpoint start cylinder(s) or
area located on the system residence
volume, using the DDR (DASD
Dump Restore) program with the

VM/SP System Messages and Codes

CP-owned volid volid invalid for
3330V

User Response: None.

9141

Trace table is smaller than
requested
Explanation: Failing storage frames
were detected during CP initialization.
This is a hardware error. This
condition made it impossible to allocate
the requested number of contiguous
trace table pages. Message 9231 and
probably message 9241 were received
prior to this message.
System Action: The system has
allocated a smaller trace table. The
system will continue to operate
normally.

/
\

DMK
Operator Response: Notify your
system support personnel of this
problem.

916E

Explanation: In attempting to follow
the chain of DASD buffers foI' a spool
file, an error was encountered in trying
to read one of the buffers.

Permanent I/O error on
checkpoint area

915E

Error allocating spool file buffers

System Action:
Explanation: An I/O error has
occurred while trying to read or write
the checkpoint area.

If CKPT was specified, the system

enters a disabled wait state, with
wait state code X'OOE'.

System Action:
2.
1.

If FORCE was specified, the file on

which the error occurred is deleted
and the system continues to recover
from the checkpoint cylinder or
area.

If this occurs during a warm or

CKPT start, the system issues
message DMKCKS919E and enters a
wait state with wait state code
X'OOE'.

Operator Response:
2.

If it occurs while the system is

operating normally, dynamic
checkpointing is terminated.

If the system enters the 'OOE' wait

state, attempt an IPL with the
FORCE option.

Operator Response:
2.
1.

If this is the first time you have
initialized this system, check the
DMKRIO deck to make sure you
have specified the proper device type
for the system residence volume.

If this is not the first IPL of'this

not allow any users to log on to the
system. The system should be
devoted to reclaiming and putting
out as many spool files as possible.
Note that at least one spool file was
not recovered properly. Use SPTape
to make a copy of your spool files,
then reinitialize the system with the
cold (COLD) start option.

system, try to IPL the sY8tem again.
If this fails, move the VM/SP

SYSRES volume to another device
and reload (via IPL). If this IPL
fails, perform a cold start.
3.

At this point, checkpointing has
been terminated, so the system is
running without a dynamic
checkpoint capability. Quiesce the
system and issue a normal
SH UTDOWN command, then
attempt a warm start. If the error
persists, reformat the checkpoint
cylinders or area with the FORMAT
service program and try again to
warm start. If this fails, a cold start
is required.

If FORCE was specified, you should

917E

Checkpoint area invalid; clear
storage and cold start
Explanation: The CKPT cylinder or
area contains no valid information for
recovery.
System Action: Th~ system en tel'S a
disabled wait: state (wait state code OOE).
User Response: ThE're is no valid
eheckpoint data and. if there is no warm
start data, storage must be cleared and
a cold start performed.

Control Program (GP) Messages

223

DMK
9181

SYSTEM DUMP FAILURE;
STATUS NOT STORED FOR
ABENDING PROCESSOR

System Action: If possible, the
operator will be prompted for the type of
start to perform. Otherwise, the system
enters a disabled wait state (wait state
code 009).

Explanation: A STOP-STORE status
operation could not be successfully
completed. The status from the
non-abending processor will be zeros or
invalid. The dump will continue to
process.

Operator Response: Try to reinitialize
the system with the CKPT start option.

921W
System Action: None.
User Response: None.

919E

Checkpoint area is i.nvalid;
checkpointing terminated
Explanation: The CKPT area has been
invalidated and checkpointing will no
longer be performed. The reason should
have appeared in a previous message.
System Action: Checkpointing cannot
resume until the system is reloaded (via
IPL).
Operator Response: With knowledge
that a subsequent CKPT start will fail,
the operator should follow installation
procedure in this matter. Probably, the
safest procedure is to quiesce the system
and perform a normal shutdown. Then,
a subsequent warm start will reinitialize
the CKPT cylinder or area so that
checkpointing can resume. Note that
continued system operation and a
subsequent failure to shut down
normally makes a cold start mandatory.

920W

No warm start data; checkpoint
start for retry
Explanation: The operator has
specified a warm start and the warm
start cylinder of the system residence
volume has no warm start data. This
message is usually issued when an IPL
is performed on a new CP system for the
first time, or when the last checkpoint
was not successful.

224

VM/SP System Messages and Codes

System recovery failure;
unrecoverable I/O error
Explanation: During the system warm
start phase, an unrecoverable
input/output error occurred on the
system residence device while the
system was either trying to write record
one of the first warm start cylinder or
area or trying to read warm start
information from the warm start area.
System Action: The system enters a
disabled wait state (wait state code 009).
Operator Response: IPL the system
again to retry the warm start function.
If this is unsuccessful, the IPL volume,
if movable, could be moved to another
drive and the IPL retried.
Warning: A volume should never be
moved if it is visibly damaged;
discontinue use of this volume and
device and call IBM for hardware
support.
If this second IPL is unsuccessful, you
may IPL the system again and try a
CKPT, FORCE or COLD start, in that
order. The Dl\IKDAS5xxI error message
preceding this message gives the
command op-code, device address, sense
data and channel status word associated
with this error. If the problem persists,
force a CP dump to the printer by
pressing the system console REST ART
key. Save the output and call your
system support personnel to determine
whether the problem is hardware or
software. Then call IBl\1 for the
appropriate support.

DMK
Note: The warm start cylinder(s) or
area(s) may have to be reformatted
using the FORMAT service program to
prevent unrecoverable I/O errors during
the next system checkpoint.

922W

9231

Explanation: The system has detected
a failing storage frame. This is a
hardware error. 'rstor' is the real
address of the failing storage frame.

System recovery failure; invalid
spooling data

System Action: System operation
continues.

Explanation: During the system
checkpoint phase, the checkpoint
module encountered an invalid spool
allocation record in storage.
System Action: The system enters a
disabled wait state (wait state code 007).
Operator Response: This message
usually indicates severe system
problems with the system spooling
allocation records. It is usually
impossible to continue system operation
without clearing storage and performing
a checkpoint start. If a system dump to
printer or tape preceded this message, it
should give the system programmer
enough information to determine the
cause of the failure and the resultant
checkpoint failure. The first 55,296
bytes (hexadecimal D800) of storage
contain the checkpoint module, work
area and a 4096-byte buffer areas, and
I/O buffers used by checkpoint
(DMKCKP). This area should be
dumped using standalone dump
procedures.
For FB-512 devices, the first 55,296 bytes
(hexadecimal D800) of storage contains
the checkpoint module, work areas, and
I/O buffers used by checkpoint
(DMKCKP). This area should be
dumped using standalone dump
procedures.
If a system dump to printer or tape did
not precede the message, the complete
storage should be dumped.

Failing storage frame at location
rstor

Operator Response: Notify your
system support personnel of this
problem.

9241

xxxx additional failing storage
frames exist

Explanation: The System has detected
unusable page frames. This is a
hardware error. Message 9231 has been
issued four times prior to this message.
xxxx -

the number, in hexadecimal, of
failing storage frames less four.

System Action: System operation
continues.
Operator Response: Notify your
system support personnel of this
problem immediately.

9251

Systenl auto dump reallocated to
DASD rdev
Explanation: The system dump has
been reallocated on the DASD rdev.
This condition occurred due to either
the operator processing or purging an
existing dump file or issuing the
command 'SET DUMP AUTO'.
System Action: The system continues
normal operation.
Operator Response: None. However,
the operator has an option to SET the
dump to the printer or tape.

Control Program (CP) Messages

225

DMK
928W

Permanent 1/0 error in warm
start data area

attach them to the system for normal
CP usage. This message usually
indicates that a normally required
volume for paging or spooling either is
not formatted or is not available at IPL
time. Make sure that all volumes are
moun ted and ready before loading the
CP system. It may be necessary to bring
the system to an orderly shutdown,
remedy the situation. and IPL the
system again~ using normal
initialization and warm start
procedures.

Explanation: An unrecoverable I/O
error has occurred while trying to write
the warm start data area.
System Action: The system enters a
disabled wait state (wait state 028).
Operator Response: Clear the first
record of the warm start data and re-IPL
the system to attempt a CKPT
(checkpoint), FORCE, or COLD start.
9521

950A

Operator not logged on; explicit
LOGON required
Explanation: The operator has not
been automatically logged on. The
reason may be given in one of the logon
failure messages that preceded this
message.
System Action: The system enters a
normal wait state while waiting for the
operator to reply to the console and
perform a normal logon.

System Action: The system continues
normal operation.

System Action: System processing
continues.
Operator Response: No operator
action is explicitly required at this time;
however, you may have to mount and
make ready specified system volumes
later during system operation and

If the CPU is a 4331 or a 4341, control
storage may have overflowed into main
storage. This then makes some main
storage unavailable for Vl\1 and can
cause this message to be outputted.

CP volid volid not mounted
Explanation: One of the volumes
specified in the system-owned list is not
mounted at system initialization time.

226

Explanation: During the system IPL
procedure, the system determined that
the amount of real storage available is
not the same as the amount of storage
specified for the system at system
generation time.

Operator Response: Determine that
no unusual hardware reconfiguration
has taken place, and bring the message
to the attention of your system
programmer so that he can verify that
normal system operation is in effect. He
should also verify that the RMSIZE
operand, specified in the SYSCOR
macro of the DMKSYS module during
system generation, is correct. If it is
not, regenerate the system with the
correct storage size, so that this
message will not he issued during
normal operation of the system. If the
RMSIZE operand is correct, real storage
may hav8 been damaged due to a
hardware problem; call IBM for
hardware support.

Operator Response: Perform a normal
logon as specified in the VM/SP
Operator's Guide, entering the required
password. The system can then resume
normal operation.

9511

nnnnnnK system storage

VM/SP System Messages and Codes

(

DMK
9531

Unable to allocate system auto
dump

956A

Explanation: During the system IPL
procedure, the CP system was unable to
find enough contiguous disk space to
hold a possible CP abend dump.

Explanation: A DASD volume was
swapped while in use by the system (CP
owned or attached to the system), and
the volid on the new volume is different
from the volid of the previously
mounted volume, or the volid could not
be read.

System Action: The system continues
normal operation
Operator Response: No action on the
part of the operator is necessary. The
system dump has been set to the default
of the system printer. The operator may
change the dump to another printer or
tape drive but may not specify AUTO
since it has not been allocated.

)

954E

System Action: The DASD is made
pnavailable offline. Any I/O activity to
the device results in a condition code of
3 being reflected to the caller.
Operator Response: Mount the
desired volume and issue the CP
command VARY with the ONLINE
operand (with the exception of a
system-owned or dedicated device).

DASD rdev volid volid not
mounted; duplicate of DASD rdeu
Explanation: During the system IPL
procedure, duplicate volume IDs were
identified on two disk volumes. The
message indicates that it was a
duplicate of a previous volume label
read on an earlier device.
System Action: The system continues
normal operation.
Operator Response: Immediately
verify that the correct volume is
mounted as the one accepted on the
specified device. If it is not, severe
system errors could occur since CP may
perform incorrect allocation on the
volume specified. Immediately stop the
system, bring it to an orderly shutdown,
and remove the incorrect duplicate
volume from the system. This message
and the duplicate volumes usually occur
after a system restart when users have
attached and mounted on the system
volumes with labels similar to those of
other users or similar to the CP system
volumes. This should be avoided
wherever possible.

DASD rdev VOLID volid NOT
MOUNTED; NOW OFFLINE

9571

STORAGE SIZE = xxxxxK,
NUCLEUS SIZE = xxxK,
DYNAMIC PAGING SIZE =
xxxxxK, TRACE TABLE SIZE
xxxK, FREE STORAGE SIZE =
xxxxK, VIRTUAL = REAL SIZE
xxxxxK
Explanation: This message is issued at
system initialization time by DMKCPJ
and provides a general map of VM/SP
system storage. This map is accurate to
within one page (4K) and is rounded to
page boundaries.
STORAGE SIZE
amount of storage being used.
NUCLEUS SIZE
amount of storage being used by the
VM/SP nucleus:
DYNAMIC PAGING SIZE
size of the VM dynamic paging area.
TRACE TABLE SIZE
size of t.he trace table.
FREE STORAGE SIZE
size of the fixed free storage area.

Control Program (CP) Messages

227

DMK
If the system is generated with attached

VIRTUAL=REAL SIZE
size of the virtual = real area.

processor support and this feature is not
installed, no message is issued.

System Action: The system continues
normal operation.
9601
Operator Response: None. This
message is for information only.

9581

Explanation: For DMKCKP, this
message indicates that the warm start
data has been successfully saved on the
system residence volume and is ready
for a system warm start.

ATTACHED PROCESSOR NOW
OPERATIONAL

This message is immediately followed by
message DMKCKP961 W.

Explanation: The real machine
initialization routine, DMKCPI and
DMKAPI, have completed the necessary
processing to support the attached
processor. This message will only be
received when the installation has
reque~ted attached processor support
via system generation.

System Action: The system enters the
wait state after issuing message
DMKCKP961W.
Operator Response: None. This
message is for information purposes
only.

System Action: The system begins
utilization of the attached processor.
Operator Response: None.

961W

Note: If this message is received, the
8K required for system prefixing will
not appear in the storage map of
message 957I.

959W

System Action: The system enters the
wait state. The wait state code is 8; see
"CP Wait State Codes" on page 13 for
an explanation.

Explanation: The installation
requested attached processor support
during system generation. DMKCPI
determined during IPL, that the unit
was not online.

Operator Response: Reinitialize CP if
the attached processor is required.
Note: Since the intent of this message
is to provide a warning to the attached
processor user, it will only be issued
when the multiprocessing feature is
installed.

228

VM/SP System Messages and Codes

System shutdown complete
Explanation: The system has been
brought to a successful orderly
shutdown.

Attached processor not online

System Action: Processing continues
without the attached processor.

System warm start data saved

Operator Response: No explicit action
is necessary. You may now or at a later
time re-IPL your CP system and restore
the saved warm start data.

9621

CP-owned DASD rdev volid volid;
invalid allocation record
Explanation: No valid allocation was
found on the CP-owned volume
indicated. If the message is issued by
DMKVDE, an ATTACH TO SYSTEM as
a system owned device cannot be
fulfilled, because of errors or
inconsistencies detected in the
allocation extent map. The device can

DMK
be used as a DASD containing
minidisks.

or MP (multiprocessor) system. This
message will only be received when the
installation has requested AP or MP
support via system generation; where

System Action: The volume is not
mounted as a system-owned volume.
Operation continues. If the DASD is
the system resident device, the message
is not issued at the operator's console,
but is pointed to by register l. The
system enters a disabled wait with a
wait state code of X'OlB'.

where:
xx is the ID (address) of the IPLed
processor.
yy is the ID (address) of the non-IPLed
processor.

Operator Response: If the volume is
to be used by VM/SP, a valid allocation
record must be written with the
Format/Allocate Service Program. See
the note and follow the instructions
described in the explanation of wait
state code X'OlB'.

963W

System Action: The system begins
utilization of both processors.
Operator Response: None.
Note: If this message is received, the
8K required for system prefixing will
not appear in the storage map of
message 9571.

Second processor not online
Explanation: The installation
requested multiprocessor support during
system generation. DMKCPI
determined during IPL that only one
processor was available.

9661

Explanation: The real machine
initialization routine(s), DMKCPI (and
others), have completed the system
initialization necessary to support the
running of virtual machines and the
execution of operator commands.

System Action: Processing continues
without the second processor.
Operator Response: Reinitialize CP if
the second processor (in an MP
configuration) is required.
Note: Since the intent of this message
is to provide a warning to the
multiprocessor user, it will only be
issued when the multiprocessor feature
is installed. If the system is generated
with multiprocessor support and this
feature is not installed, no message is
issued.

9641

Processor xx IPLed; processor .YY
initialized
Explanation: The real machine
initialization routines. DMKCPI and
DMKAPI, have completed the necessary
processing to support the second
processor of an AP (attached processor)

Initialization complete

System Action: DMKCPI passes
control to the dispatcher to start
fielding interrupts and LOGON
requests.
Operator Response: None.

9671

Disconnect use rid - system
restarted (mmmnnnishutdown) and
system console not VM operator
console
Explanation: This message is issued at
system restart, after a CP system failure
or SHUTDOWN REIPL command, if the
system operator was not logged on to
the primary system console at the time
the system failure or SHUTDOWN
REIPL occurred.
where:

Control Program (CP) Messages

229

DMK
userid
mmm
nnn

is the userid of the system
operator
is the module issuing the abend
is the abend number

9711

System is {uniprocessorlattached
processorlmulti-processor}
generated

SHUTDOWN is inserted if the restart
resulted from a SHUTDOWN REIPL.

Explanation: This message is issued at
system initialization time by DMKCPI
and identifies the system generation
mode specified within module DMKSYS.

System Action: The operator virtual
machine is disconnected. The system
console displays the VM logo and
awaits a LOGON command. Console
spooling is automatically initiated for
the operator virtual machine.

System Action: Having identified the
hardware configuration that this system
is generated to run on, DMKCPI
continues initialization.
Operator Response: None.

Operator Response: No action is
required. You may wish to reconnect to
the operator virtual machine by
entering a LOGON command specifying
the operator's userid and password. The
LOGON command may be entered from
any enabled terminal (including the
system console).

9681

System shutdown requested

•

the hardware does not have the
multiprocessor feature

Explanation: A shutdown start was
requested during initialization.

•

the configurations have the second
processor offline.

System Action: The system enters the
wait state after issuing message
DMKCPJ961W. Since a warm start has
not been performed, the warm start
cylinder from a previous shutdown is
still valid.
User Response: None. This message is
for information only.

970W

TOD CLOCK SYNC CHECK
RECEIVED
Explanation: The TOD clocks are out
of synchronization.
System Action: The system
resynchronizes the clocks and continues
processing.
Operator Response: Press the TOD
Enable Set key when instructed by the
system.

230

Note: This message does not always
reflect the way the system will be
initialized. Uniprocessor generated
systems will always be initialized in
uniprocessor mode. Attached processor
and multiprocessor generated systems
will be initialized in uniprocessor mode
when:

VMjSP System Messages and Codes

972E

NUCLEUS AREA IS TOO SMALL;
IT IS NOT UPDATED. THIS
NUCLEUS REQUIRES nnnnnn
{CYLINDERSIPAGES}
Explanation: This message is issued
during the install process if the CP
nucleus is too big to fit into its defined
area on disk storage. nnnnnn indicates
the number of cylinders (for CKD
storage devices) or pages (for FB-512
storage devices) that are needed to hold
the nucleus.
System Action: The system enters a
disabled wait state (wait state code OlF).
Programmer Response: Review the
SYSRES macro in the DrvIKSYS
ASSEIVIBLE file. lVlake sure the values
used for SYSVOL. SYSRES, and
SYSTYPE correctly describe the target

DMK
disk. If these values are correct. t.hen
review the space allocation on the
target disk to find a contiguous area as
large as this message specifies. If
necessary. change the values used for
SYSNUC. After you correct the
problem, re-1P1. and continue with the
install process.

9731

)

No directory file on IPL volume
volume
Explanation: This message is issued at
system initialization time if the IPL
volume (also called the SYSRES
volume) does not cont3in an active
directory file. volume identifies the
volume label of the IPL volume.
System Action: System operation
continues. The directory will be loaded
from the first SYSOWN volume with a
valid directory file.
Operator Response: None. However. if
you normally load the directory from

the IPL volume, notify your System
Programmer or System Administrator
that it was not loaded from the IPL
volume this time. Maintenance may be
required for the directory.

9741

No valid override file; using
system defaults
Explanation: This message is issued at
system initialization time if the
directory volume does not contain a
command override file.
System Action: System operation
continues. The IBM default classes are
used for commands and diagnose codes.
Operator Response: None. However, if
you normally load the override file,
notify your System Programmer or
System Administrator that the command
override file was not loaded this time.
Maintenance may be required for the
override file.

Control Program (CP) Messages

231

DMK

(

232

VM/SP System Messages and Codes

DMS

Conversational Monitor System (CMS) Messages
OOlE

No {filename Iname names}
specified
Explanation: The command requires
that you specify at least one filename.
For the EXEC command, specify the
name of the EXEC file.
For the EXPAND command, specify
the name of the input text file.
For the MACLIB command, specify
at least one filename in addition to
the library name.
For the OSRUN command, no
LOADLIB member name was
specified.

002E

[Input IOverlay]
{File[(s)] IDatasetlNote} [fn [it
[im]]] not found
Explanation: The specified file was not
found on the accessed disk(s). Either
the file does not reside on this disk, the
file identification was misspelled, or
incomplete identification was provided
to cause the appropriate disk to be
searched, or system disk was not
accessed as a read-only extension of the
A-disk.
For the PRELOAD command, either
the loadlist EXEC, the CNTRL file,
or one of the in pu t text files could
not be found.

For the PRELOAD command,
specify the name of the loadlist
EXEC file.

For SETPRT command, the module
represented by 'fn ft' does not exist
in the current CMS Disk Search
Order.

For the VMFTXT command, you did
not specify the filename of the
TXTLIB you want to build.

For the ST ATEW command, the file
may exist, but it is not on any of the
user's read/write disks.

For the ZAP command, if you
specify a LOADLIB or TXTLIB file
you must specify one to three
library names.

For the ZAP command, either none
of the libraries specified for a
TXT LIB or LOAD LIB could be
found, or the INPUT filename could
not be located via the STATE
macro.

For the ZAPTEXT command, specify
the name of the text file.
System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the command
and specify the filename(s), library
name(s), or member name.

For the ZAPTEXT and EXPAND
commands, the input text file or
INPUT filename could not be
located via the ESTATE command.
For the VMFLKED command, either
you specified a file that cannot be
found on a minidisk in the CMS
search hierarchy, or you specified a
Conversational Monitor System (CI'vlS) Messages

233

DMS
filename on a %CONTROL
statement as the name of a CNTRL
file and that file was not found.
For the CONVERT command, the
input DLCS file you specified was
not found.
See the VM/SP eMS Command
Reference for a description of the file
identification required by each
command and the search procedure
used. For the ASM3705, ZAP,
ZAPTEXT, and EXPAND commands, see
the VM/SP Installation Gu.ide.

System Action: RC = 28.
Execution of the command is
terminated. The system status remains
the same.
For DMSSPR, nothing has been sent to
the virtual 3800.
For DMSLIO, some loader information
fields have been initialized, but they
should not interfere with a subsequent
LOAD command.
For the CONVERT command,
conversion stops.

For DMSSPR, access the disk having
the required module or respecify a
different module in the calling sequence
and then reissue the SETPRT command.
For a DMSROS TEXT file, ensure that
the file is accessible and reissue the
command.
For the VMFLKED command, make
certain that the proper disks are
accessed and check the name of the
specified file. If the name was specified
incorrectly, re-issue the command with
the correct name.
For VMFTXT:
If the filetype is EXEC, make sure that

a memberlist EXEC file exists and that
the filename of the member list and the
libname parameter are spelled the same.
Correct the error and reissue the
command.
If the filetype is CNTRL, make sure that

the specified CNTRL file exists and is
correctly spelled. Correct the error and
reissue the command.
If the filename and filetype pair is one

of the following:
RC=--=44.

For the VMFPLC2 command, the STOP
option has been specified with the
LOAD function, and the file was not
found in alphabetic sequence. The tape
is positioned immediately before the
next file.
For the VMFLKED and VMFZAP
commands, processing ends.

234

VMFMSGS EXEC
VMFDATE MODULE
VMFTXT DATA
contact your system programmer and
arrange to have these files installed
again on the CMS system disk as
filemode 2 files.

For the VMFMERGE command, other
required files are checked and then
processing ends.

For the VMFZAP, VMFMERGE, and
VMFREMOV commands, see if the
proper disks are specified in the
VMFPARM file and then re-issue the
command.

User Response: Find or create the
desired file. To make sure that the file
exists, issue STATE~ fn ft * or LISTFILE
fn ft *. Correct and reissue the
command.

For the CONVERT command, correct
the file name or access a disk where the
file ean be found.

VMjSP System Messages and Code8

(

DMS
File fn [TXTLIBILOADLIB] not
found

0021

Explanation: The specified TXTLIB or
LOADLIB file was not found on the
accessed disk(s). Either the file does
not reside on this disk, the file
identification was misspelled, or
insufficient identification was provided
to cause the proper disk to be searched.
This message will also occur in the
following situations:
•

•

a user issues a GLOBAL command
for a TXTLIB or LOAD LIB and then
1) erases or renames the TXTLIB or
LOADLIB, or 2) releases the disk on
which it resides,
if the CMS segment is not available
when the user accesses an OS disk
or DMSSVT.

System Action: RC = 0
TXTLIB file could not be found.
Execution of the command continues.
RC = 28
LOADLIB file could not be found.
Execution of the command is
terminated. The system status remains
the same.
User Response: If 'fn TXTLIB' or 'fn
LOADLIB' is required for command
execution, make sure that it exists and
is on a disk that is accessed. Otherwise,
ignore the message.

002W

File fn ft (fmJ not found
Explanation: The specified file was not
found on the accessed disk(s). Either
the file does not reside on this disk, the
file identification was misspelled. or
incomplete identification was provided
to cause the appropriate disk to be
searched. (See the VM/SP CJ\rfS
Command Reference for a description of
the file identification required by each
command and the search procedure
used.)

Also, a program may have modified the
fileid in the FST. See "CMS Routines
U sed to Access the File System" in the
VM/ SP System Logic and Problem
Determination Guide Volume 2 (CMS)
for a description of the SET HASH
command.
For the VMFLKED command, the input
control file indicated that filename
filetype (filemode) was to be included in
the link edit. The file was not found
and the %)IGNORE option was not in
effect.

System Action: DMSGLB issues RC
28; all other modules issue RC = 4.
Execution of the command continues.
For DMSGLB, the old MACLIB or
TXTLIB list is cleared and the new list
contains all specified libraries except
those that are not found.
For DMSGND, there will be no entry in
the directory for the file not found.
For DMSLBM, the file not found will
not be in the MACLIB. Processing
continues with the next filename if one
exists.
For DlVISLBT, processing continues
with the next filename if one exists.
For DMSZAP, if a library name was
specified, the next library name (if one
is present) is used. If a MODULE file
was specified, all control records
encountered until the next NAME~
DUMP, or END control record are
ignored.
For the VMFLKED command, the
current module is not link edited but
processing continues with the next
module in the input control file.
For the VMFREMOV command, if no
Service Control File was found. then
processing of the PTF being removed
ends. Processing continues for the next
PTF to be removed.

Conversational Monitor System (eMS) Messages

235

DMS
User Response: To make sure the file
exists, issue STATE fn ft * or LISTFILE
fn ft *. Make sure that the disk on
which the file resides is accessed.

004E

Explanation: The specified book,
module, phase, or procedure was riot
found on the accessed disk(s) as a result
of a FETCH (SVC 1 or SVC 2).

For DMSGND, if you must have the file
not found in the directory, take steps to
supply the file. Correct and reenter the
command.

System Action: RC = 28.
Execution of the command is
terminated. The system status remains
the same.

For DMSLBM, if the MACLIB exists
after execution of the command, use the
MACLIB ADD command to add the file
to the library.

User Response: To make sure the file
exists, issue the command DOSLIB MAP
against all DOSLIB files. If the file
resides on a DOS-formatted disk, a
DSERV will help locate it.

For DMSLBT, supply the necessary file
using the TXTLIB ADD command.
For the VMFLKED command, make
sure that the proper minidisks are
accessed. Re-issue the command (if
appropriate, use the MODULE option so
that only the module in error is link
edited).

003E

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
For DMSLIO, some option processing
may have caused user storage to be
cleared or the location counter set, etc.
This should not interfere with a
subsequent LOAD command.
For the VMFLKED command,
processing ends.
User Response: Correct and reenter
the command.

236

004W

VM/SP System Messages and Coded

Warning messages issued
Explanation: The language processor
returned completion code 4.
System Action: RC = 4.
The system status remains the same.

Invalid option: option
Explanation: The specified option is
invalid. It may have been misspelled or,
if the option is truncatable, it may have
been truncated improperly, or it may
conflict with another option in the
command line.

{Book IModule IPhase IProcedure}
name not found

User Response: Look for additional
messages that may have been issued by
the compiler.

005E

{No option [parameter]
specifiedlNo application id
specified}
Explanation: The indicated option or
the application id was entered in an
incomplete form.
For the VMFLKED command, the
format you issued is invalid. Either you
issued the command without the
filename of an input control file, or you
specified the MODULE option without a
module name.
System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.

DMS
User Response: Reenter the command,
specifying the required data for the
option.

006E

No read/write {disk\diskmode disk}
accessed {for fn ft}
Explanation: The user does not have
access to a read/write disk on which the
command can write its output or utility
files. If the message displayed is NO
READ/WRITE 'A' DISK ACCESSED,
the command, in order to be executed,
requires that the A-disk be accessed in
read/write mode. For RECEIVE,
SENDFILE, or DISCARD (which is
equivalent to RECEIVE issued with the
PURGE option) the LOG option was in
effect, and no read/write disk was
accessed.

System Action: RC = 32.
Execution of the command is
terminated. The system status remains
the same.
For the UPDATE command, the
following may have occurred:
•

ftype" existed on the output disk
before the command was entered,
this file may have been erased.
•

For the CONVERT command,
conversion stops.
User Response: Access a read/write
disk and reissue the command, or issu,e
the CP LINK command to reset the
A-disk to read/write mode, access the
A-disk again, and reissue the command.
For the CONVERT command, access a
disk where the table can be built in
read/write mode and reissue the
commmand.

007E

File fn It fm is not fixed,
SO-character records

If the DISK option was in effect and

a file with the fileid "fname
UPDLOG" existed on the output
disk before the command was
entered, this file may have been
erased.
•

If the CTL option was in effect and

a file with the fileid "fname
UPDATES" existed on the output
disk before the command was
entered, this file may have been
erased.

For the CONVERT command, the
program tried to find a read/write disk
for the table, but was unsuccessful.
System Action: RC = 36.
Execution of the command is
terminated. The system status remains
the same.

If a file with the fileid "$fname

•

If UPDATE processing began before

the error was detected, any or all of
the following files may have been
created on the output disk:
UPDATE CMSUTI
$fname ftype
fname UPDLOG
(if the DISK option was in effect)
fname UPDATES
(if the CTL option was in effect)
User Response: It is possible that an
incorrect fileid was specified in the
command line. In this case, reissue the
command. If, however, the fileid was
correct but the file is in the wrong
format or does not contain SO-character
records, change the file's format and/or
record length with the COPYFILE or
EDIT command.

Explanation: The specified file must
have fixed-length, SO-character records
in order for the command to be
executed.

Conversational Monitor System (eMS) Messages

237

DMS
008E

Device vdev {invalid or
nonexistent lis an unsupported
device type}

009E

Explanation: The column specified lies
outside the logical record length of the
file.

Explanation: The virtual machine does
not have a virtual 1403 or 3211 printer,
punch, or reader.

System Action: RC = 24 for
COMPARE, SORT, TYPE and XEDIT
SORT. RC = 5 for SET TRUNC and SET
VERIFY.
Execution of the command is
terminated. The system status remains
the same.

For the VMFZAP, VMFMERGE ·and
VMFREMOV commands, the disk
address you specified in the VMFP ARM
file does not have any disk linked.
System Action: RC = 36.
Execution of the command is
terminated. The system status remains
the same.
For VMFMERGE and VMFREMOV,
the status of all disks specified in the
VMFP ARM file is· checked and then
processing ends.
User Response: Use the CP DEFINE
command to provide a suitable virtual
device and reissue the command.
For VMFZAP, check that the disk
address on the specified record is
correct. If so, make sure that the proper
disk is linked at that address. Re-issue
the command.
For VMFMERGE and VMFREMOVE,
make sure you have the correct disks
linked. Reissue the command.

008W

Error messages issued
Explanation: The language processor
returned completion code 8.
System Action: RC = 8.
The system status remains the same.
User Response: Look for additional
messages that may have been issued by
the compiler.

238

VM/SP System Messages and Codes

Column [col] exceeds record
length [(nn)]

User Response: Reissue the command,
specifying the correct column.

(
OlOE

Premature EOF on file {in it
[fmllnumber nn}
Explanation: For DMSCl\1P, an end of
file occurred on one of the files b2ing
compared before the end of file was
received on the other.
For DMSTPJ, a tape mark was
encountered on the file before the file
was completely loaded. Since the FST
is the last record of the file, the fn and
ft of the file in error are not available so
the number of the file being read is
given. This number represents how
many files have been read since the last
tape command was issued.
For the VMFLKED command, the end
of the input eontrol file was reached
while reading Linkage Editor control
records before a NAME record was
found.
System Action: RC =-~ 40.
Execution of the command is
terminated. The system status remains
the same.
For DlVlSTPE, a temporary file called
"TAPE Cl\lSUT1" containing the data
has been created on the A-disk or on the
disk specified by the user. "TAPE
CMSUTI ,. contains fixed-length,
800-byte record::;.

DMS
User Response: For DMSCMP, t.his
normally indicates that the files being
compared had an unequal number of
records. If the command was properly
specified, no action is necessary.

OllE

Explanation: The filetypes specified do
not have the same record format; that
is, one is fixed-length and one is
variable-length, or the record lengths
differ.

For DMSTPE, the file may have to be
dumped to tape again.

System Action: RC = 32.
Execu tion of the command is
terminated. The system status remains
the same.

For VMFLKED, correct the input
control file and re-issue the command.

OIOW

User Response: Change the record
format with the COPYFILE command.

Premature EOF on file in it im
[--sequence number seq no not
found]
Explanation: The update file contained
an error. A control card specified a
search for a sequence number which
exceeded the value of any sequence
number in the file being updated. As a
result, a premature end of file occurred
on the input file being updated, before
the sequence number specified in the
con trol card could be found.
System Action: RC = 12.
Update processing continues, and, if the
CTL option was specified, additional
update passes are made.
If several warning messages are
generated during the updating process,
the final return code when the UPDATE
command has finished processing is the
maximum of all return codes (4 or 8 or
12) associated with the generated
warning messages. The REP option, if
it was specified, is ignored, and the final
update deck has the fileid '$fname
ftype'.

See the explanation of message
DMS177I for further information on the
meanings of the UPDATE warning
return codes.

Conflicting file formats

012W

Severe error messages issued
Explanation: The language processor
returned completion code 12.
System Action: RC = 12.
The system status remains the same.
User Response: Look for additional
messages that may have been issued by
the compiler.

013E

Member membername not found [in
library libnamelin file in it]
Explanation: The specified member
was not found in the library.
System Action: RC = 32.
Execution of the command is
terminated. The system remains in the
same status as before the command was
entered.
User Response: Use the MACLIB
MAP, TXTLIB MAP, or LOADLIB LIST
command to display the names of library
members.

User Response: Correct the invalid
control card in the update file, and
reenter the UPDATE command.

Conversational Monitor System (eMS) Messages

239

DMS
{MemberIPhase} name not found
in library lib name

013W

command could. be found with
the name entered.

Explanation: The member or phase
specified was not found in the specified
library. If REPLACE was specified, the
new member is added.

UNKNOWNCMSCOMMAND
indicates that no CMS
command, eMS or user EXEC
filel or user MODULE file
exists by the name entered.

System Action: RC = 4.
Processing continues with the next
filename.

UNKNOWN CP/CMS COMMAND
indicates that no CP or CMS
command could be found with
the name entered.

User Response: None.

INVALID CMS COMMAND
indicates that an error has
occurred in LOADMOD.

Invalid {function functionlkeyword
keyword}

014E

Explanation: The function 'function'
specified is misspelled or invalid. For
the DEFAULTS command, a function
other than SET or LIST was specified.

INVALID SUBSET COMMAND
indicates that the loader has
tried to load a routine at an
address equal to or higher than
X'20000'. The command you
issued may be a valid CMS
command, but not a valid
su bset command.

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same, with the following exceptions:
•

For DMSOVR, SVCTRACE is
turned off if it was previously on.

•

For DMSTPI, if the DEN, TRTCH,
7TRACK, 9TRACK, or 18TRACK
options were specified, the modeset
byte has been set for the specified
device (TAPn, where n is a
character from 0 to 9 or A to F; the
default is TAPl).

User Response: Reissue the command.
specifying a valid function.

015E

{Unknown {CP/CMSICMSICP}
IInvalid {CMSlsubset}} command
Explanation:
UNKNOWN CP COMMAND
indicates that IMPCP (implied
CP) was on so the command
was passed to CP, but no CP

240

VM/SP System Messages and Codes

System Action: A positive return code
is passed if an error occurs in CP
processing. A negative return code is
passed if the command entered is
considered an invalid CMS command.
The system status remains the same.
User Response: Enter a command.

016E

No private CORE IMAGE
LIBRARY found
Explanation: The private Core Image
Library called does not exist on the
accessed disk, or the DLBL was
incorrect.
System Action: RC = 28.
Execution is terminated. System status
remains the same.
User Response: Access the proper disk
or alter the invalid DLBL.

(

DMS
016W

Terminal error messages issued

018E

Explanation: The language processor
returned completion code 16.

Explanation: The module file was
created with the NOMAP option of
GENMOD or is a transient area routine.

System Action: RC = 16.
The system status remains the same.

System Action: Re = 40.
Execution of the command is
terminated. The system status remains
the same.

User Response: Look for additional
messages that may have been issued by
the compiler.

017E

User Response: Regenerate the module
file with the MAP option and reissue
the command.

Invalid device address vdev
Explanation: The device address was
not specified correctly, or the device
was not accessed.

Explanation: The fileids specified in
the command line are identical.
System Action: RC =24.
Execution of the command is
terminated. The system status remains
the same.

For the VMFMERGE, and
VMFREMOV command, the remaining
records in the VMFPARM file are
checked and then processing ends.

For the VMFZAP command, determine
which disks are really needed to apply
ZAPs to this product. M~ke the
necessary corrections to the BASE,
MERGE, and ZAP records of the prodid
VMFPARM file, correcting the entry in
error. Re-issue the command.
Note: For a virtual machine with
ECMODE on, a valid vdev is within the
range X'OOl' through X'FFF'.
Otherwise, a valid vdev is within the
range X'OOl' through X'5FF'.

Identical file ids

019E

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.

User Response: Check the specified
device address and reissue the
command.

No load map available

User Response: Reissue the command,
specifying two different fileids.

Invalid {PDUMPIIDUMP} address
ustor: no DUMP operation
performed

020W

Explanation: The address specified in
the PDUMP or IDUMP macro is invalid
for one of the following reasons:
•

addr2 must be greater than addrl.

•

addrl cannot be negative.

•

addrl cannot be greater than ppend
(the end of the virtual partition).

•

addr2 cannot be negative.

System Action: The macro results in
no operation. No dump is provided;
processing continues. If you have
requested a return code on an IDUMP,
the return code is passed in register 15.
User Response: None.

Conversahonal Monitor System (eMS) Messages

241

DMS
021E

Entry point name not found

021W

Explanation: For DMSGND, the
specified directory name was not found
in the loader tables.

Explanation: A request was made to
display a transient directory, but
neither a private core image library nor
a system residence library was assigned.

For DMSLIO and DMSNCP, an entry
point name specified either with the
START command or on an LDT card
could not be located in the loaded TEXT
files.

System Action: RC = 4.
Execution of the command continues
until all specified directories are
processed.

For DMSMOD, the name used with the
FROM or TO option of the GENMOD
command does not occur in the
currently loaded files.
System Action: RC = 40.
Execution of the command is
terminated. The system status remains
the same.

No transient directory

User Response: Ensure that the proper
libraries are assigned and reissue the
command.

022E

No directory name specified
Explanation: A directory name was
not entered with the command.

For DMSLIO and DMSNCP, no
execution takes place for LDT. Loading
stops. Loader clean-up has been
processed for the loaded files. A
subsequent START command should not
be affected.

System Action: RC = 24.
Execu tion of the command is
terminated. The system status remains
the same.
User Response: Reissue the command
with a directory name.

For DMSMOD, the module is not
created.
022W
User Response: For DMSGND, reload
the auxiliary directory and reissue the
command.
For DMSLIO and DMSNCP, reissue the
START command with the proper entry
point or control section name, or
asterisk (*). Correct the LDT card with
the CMS Editor.
For DMSMOD, correct the GENMOD
command line or add the requested
name as an external name in the files
being generated.

242

VM/SP System Messages and Codes

No core image directory
Explanation: A request was made to
display a core image directory, but
neither a private core image library nor
a system residence library was
available.
System Action: RC = 4.
Execution of the command continues
until all specified directories are
processed.
User Response: Ensure that the propel'
library is assigned and reissue the
command.

(

DMS
023E

No filetype specified
Explanation: The command requires
that you specify both filename and
filetype.
For the DLBL command, both are
required if you specify the CMS
operand.
System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
For DMSTPI, if the DEN, TRTCH,
7TRACK, 9TRACK, or 18TRACK
options were specified, the modeset byte
has been set for the specified device
(T APn, where n is a character from 0 to
9 or A to F; the default is TAPI).

)

User Response: Reissue the command,
specifying the filename and filetype.

023W

. No relocatable directory
Explanation: A request was made to
display a relocatable directory, but
either no private or system relocatable
library was available or no active
entries were present on the appropriate
directory.
System Action: RC = 4.
Execution of the command continues
until all specified directories are
processed.
User Response: Ensure that either the
proper library is assigned or that active
relocatable entries are available in the
directory and. reissue the command.

024E

File fn lft fm} already exists [;
specify REPLACE option]
Explanation: The specified file already
exists.
For DMSEDI, the Editor work file,
EDIT CMSUTl, already exists as

the result of a previous edit session
ending abnormally.
For DMSXIN. the XEDIT work file,
XEDTEMP CMSUTI AI, already
exists as a result of a previous edit
session that ended abnormally.
For DMSUPD, a file with the fHeid
'UPDATE CMSUTI' already exists.
This usually indicates that the
UPDATE command was executed
previously and was terminated
abnormally, and that it left a work
file on the output disk at that time.
For DMSUTL, the file ID for
SYSUT2 specifies an existing file.
This is not allowed for the COpy
function because neither the
MODIFY or REPLACE option was
specified.
For the RECEIVE command,
RECEIVE was issued and a file
exists. You may have also specified
NOREPLACE as an option and a
file already exists.
For the VMFTXT command, a
previous invocation of VMFTXT
ended abnormally.
System Action: RC = 28.
Execution of the command is
terminated. The system status remains
the same, with the following exception:
For DMSCPY, if you were creating
multiple output files, several output
files may have been created before the
error was discovered.
User Response: You can use the TYPE
command to examine the existing file.
If you decide you want to keep it, use
the RENAME command to give it a new
fileid. If the file is invalid or incomplete,
erase it and reissue the command; or for
Dl\ISCPY, reissue the command and
specify the REPLACE option.
For DMSUTL, reissue the command
specifying MODIFY or REPLACE, or

Conversational Monitor System (eMS) Messages

243

DMS
reissue the command without a file ID
for SYSUT2.

For NCP or PEP -- The maximum
resource ID exceeds 4086 bytes.

For the RECEIVE command, use
RECEIVE with the REPLACE option,
specify RECEIVE with a unique fileid,
or issue RECEIVE with the
FULLPROMPT option. Using the
FULLPROMPT option, you can
interactively receive (and optionally
rename) each incoming file in the spool
file. For information on the RECEIVE
command format, see the VM/ SP eMS
Command Reference or issue the HELP
command.

For NCP or PEP -- The first resource is
not the 370X.
System Action: RC = 16.
Execution of the command is
terminated.
User Response: Make sure that the
370X control program has been
generated with the correct parameters
and that the correct CAMOD operand
value was used on the SA VENCP
command. For the correct parameters
for :370X control program generation
and proper specification of the CAMOD
operand on the SA VENCP command,
refer to the VM/SP Planning Guide and
Reference and the FM/SP Installation
Guide.

For the VMFTXT command, if you do
not need the files VMFTXT TEXT
and/or VMFTXT TXTLIB for problem
diagnosis, then you can erase them.
You should not erase the VMFTXT
CMSUTI file. Look at the VMFTXT
CMSUT2 file, and issue the command
shown. Then erase both CMSUTx files.
025W
024W

No source statement directory
Explanation: A request was made to
display a source statement directory,
but either a private source statement
library or a system residence library
was not available or there were no

No procedure directory
Explanation: A request was made to
display a procedure directory but no
system residence library was assigned.

source statement entries in the library
System Action: RC:= 4.
Execution of the command continues
until all specified directories are

available.
System Action: RC = 4.
Execution of the command continues
until all 'specified directories are
processed.

processed.
User Response: Ensure that the
system residence library is assigned and
reissue the command.

025E

User Response: Ensure that either the
proper library is assigned or that active
source statement entries are present in
the directory and reissue the command.

Invalid data in 370X control
program
Explanation: One of the following
conditions has occurred:
For specified EP or PEP -- The implied
or channel vector table, as designated
by the CAMOD operand on the
SAVENCP command, was not found.

026E

Invalid [parameter parameter for
function functionlvalue value for
Iwyword keyword]
Explanation: The data specified for the
given function is misspelled, missing or
incorrect.
System Action:

244

VMjSP System Messages and Codes

Re -= 24.

DMS
Execution of the command is
terminated. The system status remains
the same.

027W

Explanation: A request was made to
display the core image directory of a
private core image library, but no
entries were present.

User Response: Reissue the command,
specifying valid data for the function.

026W

System Action: RC = 4.
Execution of the command continues
until all specified directories are
processed.

phase not in library

Explanation: A request was made to
display a certain entry or entries in a
core image directory but the entry or
entries were not in the library.
System Action: RC = 4.
Execution of the command continues
until all specified directories are
processed.

User Response: None.

028E

No {devicellogical unit} specified
Explanation: You must specify either a
logical unit or a device when you use
one of the following commands:

User Response: Reissue the command,
specifying the proper phase name.

027E

No private core image library

ASSGN
FORMAT
RELEASE.

Invalid device devtype [for SYSaaa]
System Action: RC = 24.
Execution of the command terminates.
The system status remains the same.

Explanation: The device type specified
is invalid, or, if the message is
INVALID DEVICE 'devtype' FOR
'SYSaaa', the device associated with the
specified logical unit is not supported by
the processor.
System Aotion: Re ~ 24, except for
DSERV, which issues Re = 28.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the command,
specifying a valid device type. Or, for
DMSERV, use the command LISTIO
SYSaaa to verify the device to which
the logical unit is assigned. Reassign
the logical unit to a valid device and
reissue the command.

User Response: Reissue the command
and supply either the logical unit you
want assigned or the device you want
formatted or released.

028W

No {privatelsystem} transient
directory entries
Explanation: No directory entries were
present on the specified transient
library.
System Action: RC = 4.
Execution of the command continues
until all specified directories are
processed.
User Response: None.

Conversational Monitor System (eMS) Messages

245

DMS
Invalid parameter parameter [in
the [option] option field]

029E

the same, with the following exceptions
for DMSCPY:

Explanation: The data entered
following the specified option was
invalid.
System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.

•

If the APPEND option was specified,
and if the copying process had
begun before the error was
discovered, then records are
appended to the output file.

•

If the NEWFILE (the default),
REPLACE or OVLY option was
specified, and if the copying process
had beg'un before the error was
discovered, then COPYFILE
CMSUT1, on the output disk,
contains the records copied so far.

•

In multiple output file mode, several
output files may have been created
before the error was discovered.

For DMSLIO, some option processing
may have altered loader information.
This should not affect a subsequent
load.
User Response: Check the format of
the field and reissue the command,
specifying the data after the option.

029W

Explanation: This message is
indicative of either:
1.

A system type error.

A user invoking the SYSPROF exec
directly (which is not its intended
use) specifying the parameters
incorrectly.

System Action: Invalid parameter is
ignored and continuation of
initialization is attempted.
User Response: None.

030E

File fn ft fm already active
Explanation: A file could not be
referenced because it was already
active. For example, this message
appears if you try to append a file to
itself, or if you try to rename the EXEC
file you are executing.
System Action: RC = 28.
Execution of the command is
terminated. The system status remains

246

User Response: Use another method of
execution, or close the file and reissue
the command.

Invalid parameter parameter found
during eMS initialization

VM/SP System Messages and Codes

031E

Loader tables cannot be modified
Explanation: If you are trying to
increase the number of loader tables,
the system storage below the loader
tables is in use.
If you are trying to decrease the number
of loader tables, either the loader is
using more tables than you specified, or
the system storage below the loader
table is in use.

System Action: RC = 40.
Execution of the command is
terminated. The system status remains
the same.
User Response: The number of loader
table pages should be modified before
other storage is allocated. The
command should be issued immediately
after IPL.
Note: If you have exceeded storage on
the A-disk, reload (via IPL) without
accessing the A-disk.

(

DMS
032E

Invalid filetype {t

executing. For return code 32,
execution is terminated.

Explanation: The filetype entered was
not valid for the command.

For DMSPRT, DMSPUN, and DMSTYP,
a return code of 32 is issued. Execution
of the command is terminated. The
system status remains the same.

For DMSMOD, the filetype must be
MODULE.
For DMSSYN, the filetype must be
SYNONYM.

User Response: For DMSSVT, check
for an invalid library or an invalid fileid
specification in the FILEDEF command.

For DMSUTL, the filetype must be
LOADLIB.
System Action: RC c= 24.
Execution of the command is
terminated. The system status remains
the same.

For DMSPRT, DMSPUN, and DMSTYP,
specify a library or omit the MEMBER
option.

034E

User Response: Correct the filetype
and reenter the command.

033E

Explanation: The specified file must
have fixed-length records in order for
the command to be executed.

File {n {t {m is not a library

System Action: RC 32.
Execution of the command is
terminated. The system status remains
the same.
0::-'

Explanation: For DMSSVT, the file
specified in the message cannot be
updated or read because the file is an
invalid library.

User Response: You may change the
record format of the file by using the
COPYFILE command with the RECFlVI
option. Then reissue the command.

For DMSPRT, DMSPUN, and DMSTYP,
the MEMBER option is invalid because
the file specified is not a library.
System Action: For DMSSVT, the
following return code is idsued:
RC==8
(if the FIND macro was issued)
RC:.-o:I0
(if thfA STOW macro was issued)

RC"'32
(if OS LOADER waK executing)
Return code 8 or 10 is passed to the user
program and the program continues

File {n {t {m is not fixed length

035E

Invalid tape mode
Explanation: An invalid combination
of tape options was specified. For
example: 9TRACK. DEN 200.
System Action: Re = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Correct the tape
options and reissue the command.

ConvPI':-;ational Monitor System (eMS) Messages

247

DMS
036E

Open error code nn on ddname

Explanation: An error occurred during
an OS OPEN. The possible error codes
are described below:

An error occurred saving the
BPAM directory for update, or an
error occurred while doing a FIND
for the member name specified in
the FILEDEF command or CMSCB
macro.

Code Meaning
1

Either the RDBACK option of
OPEN is specified; the data set
organization is not BSAM, QSAM,
BPAM or BDAM; or, the DCB
MACRF option does not agree
with the processing mode that is
specified on the OPEN macro.
The default FILEDEF for the DCB
'ddname' displayed in the message
failed.
The RECFM of the specified DCB
does not agree with the format of
the existing file, that is, one
RECFM is variable-length and the
other is fixed-length.
A DCB, BLKSIZE, LRECL, or
BUFL option is missing or invalid.

RECFM is variable-length
spanned, and either the acc(~ss
method is not BSAM or the
filemode is not 4.

The DCB specifies output, BDAM
or a key length for an OS data set
or DOS file.

An error occurred while
attempting to position a tape with
label type specified as BLP or NL.

I/O option 'UPDATE' is invalid for
file found on read-only disk.

A tape which was specified as NL
contained an IBM standard VOL1
label as its first record.

The file is an unsupported OS data
set or DOS file, or an I/O error
occurred accessing an OS or DOS
disk.

System Action: The program
continues executing, but the DCBFLGS
OPEN bit is not turned on and the DCB
is not initialized.

The DCB BLKSIZE is not a
correct multiple of the DCB
LRECL, or the DCB specifies
writing blocked output, but only
unblocked records are permitted.
RECFM is fixed-length and LRECL
does not agree with the record
length of the existing file or, if the
filemode is 4, the BLKSIZE does
not agree with the record length of
the existing file, or RECFM is
variable-length and BLKSIZE is
not 4 bytes greater than the record
length of the existing file, ... , or
BLKSIZE is not a multiple of
LRECL whether the filemode is
equal to 4 or not.

User Response: Noting the error code
and ddname displayed in the message,
check the associated FILEDEF
command and DCB macro for invalid or
missing DeB options.

037E

[Output1 Disk mode[(vdev)) is
accessed as read/only [; A must be
R/W for DISK LOAD1
Explanation: The filemode of the
output file specifies a disk which cannot
be written on. Either the disk is
read-only or it is not correctly formatted
for the command issued. (For example,
the command is trying to write a
CMS-formatted file on an OS-formatted
disk.)
For the RECEIVE command, either:

248

VM/SP System Messages and Codes

DMS
1.

a filemode was specified on the
RECEIVE command and this mode
is READ/ONLY and the file cannot
be written onto this disk.

In a MAINT run for both DOS and OS
users, the PTF decks read from the
reader are also written on the CMS
A-disk.

RECEIVE attempted to read in a file
sent using the DISK DUMP
command (or SENDFILE with the
'OLD' option) and in order to use
DISK LOAD to read the file in, the
A-disk must be accessed in
READ /WRITE mode.

System Action: RC = 12 or 36.
Execution of the command is
terminated. The system status remains
the same.

For DMSUPD, there was no read/write
disk available for the UPDATE output
files. The following steps are taken to
determine the disk on which the
UPDATE output files are to be placed
(the search stops as soon as one of the
following steps is successful):
•

If the OUTMODE option was
specified, then the output files are
placed on the disk specified.

•

If the disk on which the original
source file lies is read/write, the
output files are placed on that disk.

•

If that disk is a read-only extension
of a read/write disk, the output files
are placed on that particular
read/write disk.

•

The output files are placed on the
A-disk, if it is read/write.

If all of the above steps fail, and the
A-disk is read-only, then the message
DISK 'A' IS READ/ONLY

is displayed.
If this message occurs during
VSAl\IIGEN EXEC processing, it
indicates that the CMS A-disk is
accessed in read-only mode. But the
VSAMGEN EXEC procedure requires
that the CMS A-disk be accessed in
read/write mode so that the CMS
DOSLIB files can be written on it. Also,
for an OS 'INSTALL', the VSAM and
Access Method Services object modules
will be copied to it for future updating.

If this message is issued in response to a
prompt, there is no return code and the
prompt is reissued.
If this message occurs during
VSAMGEN EXEC processing, the
VSAMGEN EXEC procedure terminates
and the system returns to the CMS
command environment.

For DMSCPY, in multiple output file
mode, several output files may have
been created before the error was
discovered.
For DMSDSK, the reader is closed with
the HOLD option.
For DMSMOD, loader cleanup has been
performed on loaded files.
For DMSTPJ, if the DEN, TRTCH,
7TRACK, 9TRACK, or 18TRACK
options were specified, the modeset byte
has been set for the specified device
(T APn, where n is a character from 0 to
9 or A to F; the default is TAPl).
User Response: If the disk is
read-only, issue the CP command LINK
to reset the disk to read/write status;
then access the disk again and reissue
the command. If the disk does not have
the correct format, reissue the
command, specifying the filemode of a
disk with the correct format.
If you received this message in response
to a prompt and you currently have
have no disks accessed in read/write
mode, terminate the command by
entering 2 (or quit), access a disk in
read/write mode and reissue the
command ..

Conversational Monitor System (eMS) Messages

249

DMS
For DMSBDP, ensure that the
appropriate disk is being associated
with the DTF being opened, and reissue
the command.

038E

039E

System Action: RC = 40.
The command is not executed. The
system status remains the same.
User Response: Verify that you have
specified the correct filename with the
ASM3705, ASSEMBLE, or IOCP
command. If it is correct, in the first
case above, issue a FILEDEF ddname
CLEAR command for the file, or issue a
FILEDEF command that sets the
filetype correctly. In the second case,
either use a different filename for the
input file, or erase the existing disk file.

User Response: None.

040E

No files loaded
Explanation: The user has not
previously issued a LOADMOD or
LOAD command, or the module consists
of zeros.
System Action: RC = 40.
Execution of the command is
terminated. The system status remains
the same.

the user issued a FILEDEF
command for reader or tape input
and the specified filename already
exists on disk as 'fn IOCP'.
the user issued a FILEDEF
command for input from disk with a
filetype other than IOCP and there
exists a file 'fn IOCP' on this disk.

System Action: RC = 32.
Execution of the command is
terminated. The system status remains
the same.

For the IOCP command. either:
1.

Explanation: The library specified
contains no members.

Fileid conflict for DDNAME
{ASM37051 ASSEMBLE ISYSIN}
Explanation: The file specified with an
ASM3705 (or ASSEMBLE) command
has been previously defined by a
FILEDEF command, but its filetype was
not defined as 'ASM3705' (or as
'ASSEMBLE'), or you have issued a
FILEDEF command for a reader or tape
input file and specified a filename that
is already defined as a disk file with the
filetype ASM3705 (or ASSEMBLE).

No entries in library

User Response: Load files via the
LOAD or LOADMOD command.

041E

Input and output files are the
same
Explanation: One of the following
errors was detected:
•

The same ddname was specified for
input and output.

•

The input ddname and output
ddname specify the same disk file.

•

The input ddname and output
ddname specif~r the same tape unit.

System Action: Re =: 40.
Execution of the command is
terminated. The system titatus remains
the samc.
User Response: Reissue the FILEDEF
and lVIOVE.F[LE commands correctly.

250

VlVl/SP System Messages and CouPs

DMS
042E

No {fileid(s)lexecid} specified

044E

Explanation: At least one file or exec
identification is required in order for
the command to be executed.

Explanation: The record length given
exceeds the maximum record length
allowed. For more information on the
maximum record lengths allowed by the
EDIT, PRINT and PUNCH commands,
refer to VM/SP CMS Command
Reference.

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the command,
specifying at least one fileid or execid.

042W

System Action: RC = 32.
Execution of the command is
terminated. The system status remains
the same.

No {fileidlexecid} specified
User Response: For DMSEDI, reissue
the command with an acceptable record
length.

Explanation: At least one file or exec
identification is required for the EXEC
to be loaded into the DCSS.

For DMSPRT, you can change the
record length with the COPYFILE
command, and then reissue the
command. You can also redefine the
virtual printer (by using the CP
DEFINE command) to one that handles
the longer record length.

System Action: The EXEC is not
loaded into the DCSS, the error is
recorded in the DCSS 'dcssname
DCSSMAP' file, and a prompt
(DMS298R) is issued asking if you want
to save the DCSS.

For DMSPUN, you can change the
record length with the COPYFILE
command, and then reissue the
command.

User Response: Correct the DCSSGEN
load list entry that caused the error.

043E

Record [length] exceeds allowable
maximum

{TAPn(vdev)lmode[(vdev)] is file
protected

045E
Explanation: The tape cannot be
written on.
System Action: RC = 36.
Execution of the command is
terminated. If the DEN, TRTCH,
7TRACK, 9TRACK, or 18TRACK
options were specified, the modeset byte
has been set for the specified device
(T APn, where n is a character from 0 to
9 or A to F; TAPI is the default).
User Response: Send a message to the
operator to insert the write enable ring
in the tape and retry the command.
For DMSCLS, verify that the correct
tape is mounted.

Unsupported 370X control
program type
Explanation: The 3705 control
program type is not an Emulation
Program (EP), Partitioned Emulation
Program (PEP) or Network Control
Program (NCP).
System Action: RC = 16.
Execution of the command is
terminated.
User Response: Make sure that 370X
control program has been generated
with correct parameters. For the
correct parameters for the 370X control
program generation, refer to the VM/ SP
Planning Guide and Reference.

Conversational Monitor System (eMS) Messages

251

DMS
No library name specified

•

The mode number, if specified, is not
between 0 and 6.

Explanation: The command was
entered without a library name.

•

More than two characters were
specified for the mode.

•

A null line was entered as the first
specification with the MULT option
of the DLBL command.

•

The mode specified with a LISTDS
command was not the mode of an as
or DOS disk.

•

The mode specified with a LIST FILE
command was not the mode of a
CMS-formatted disk.

•

For XEDIT, if a filemode number is
not specified, a '1' may be appended
to the invalid file mode.

046E

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the command.
specifying the library name.

047E

No function specified
Explanation: A function must be
specified in order for the command to be
executed.
System Action: RC = 24.
Execution of the command is
terminated.

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.

For SVCTRACE, SVCTRACE is turned
off if it was on.
For DMSTPI, if the DEN, TRTCH,
7TRACK, 9TRACK, or 18TRACK
options were specified, the modeset byte
has been set for the specified device
(TAPn, where: n is a character from 0 to
9 or A to F; T API is the default). The
system status remains the same.

For DMSTPI, if the DEN, TRTCH,
7TRACK, 9TRACK, or 18TRACK
options were specified, the modeset byte
has been set for the specified device
(T APi, where: i = 1, 2, 3, 4) or T API.

User Response: Reissue the command
with the filemode specified correctly.

User Response: Reissue the command
with the desired function.
049E
048E

Invalid {filemodelmodeloutput
filemode} [mode]
Explanation: This message can occur
for anyone of the following reasons:

252

•

The mode was not specified
correctly.

•

For most CMS commands, filemode
's' is an invalid mode.

VM/SP System Messages and Codes

Invalid line number nn
Explanation: The specified line
number is either non-numeric, zero, or
outside the limits of the file.
System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Examine the file and
reissue the command with a correct line
number.

DMS
050E

Parameter missing after va lue

052E

Explanation: A parameter that is
required by the command was not
specified.

Explanation: The maximum number of
characters that can be used to specify
options for this command is 100. More
than 100 characters were used.

For the ASSG N command, the dj sk
mode must be specified for the SYSaaa
logical unit.

For the OSRUN command, more than
100 characters were used in the P ARM
field.

For the DLBL command, the disk mode
or DUMMY or CLEAR must be
specified after the ddname.

System Action: RC = 24.
The command is not executed. The
system status remains the same.

For the FILEDEF command, the device
name or DUMMY or CLEAR must be
specified after the ddname.

User Response: Reissue the command,
using 100 or fewer characters to specify
the options, or parameters. Use
abbreviations if necessary.

)
For the SET command, a required
parameter that must follow a function is
mIssIng.
For the XMITMSG command, one of the
options required a value to follow it, but
the end of the parameter list was
reached.

053E

Invalid sort field pair defined
Explanation: Either an ending
character position was not specified for
a sort field, the starting position is
greater than the ending position, the
fields contain nondecimal characters, or
the sort field exceeds the maximum of
253 characters.

System Action: RC=24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Correct and reissue
the command.

051E

More than 100 characters of
options specified

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.

Invalid mode change
Explanation: The filemode letter
specified for the old fileid is not the
same as the filemode letter specified for
the new fjleid.
System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Correct and reissue
the command.

User Response: Correct and reissue
the command.

054E

Incomplete {fileidlexecid}
specified
Explanation: You must specify the
filename and filetype or execname and
exectype in order for the command to be
executed. In addition, for some
commands you must specify the
filernode.
System Action: RC == 24.

Conversat.ional .Monitor System (eMS) Messages

253

DMS
Execution of the command is
terminated. The system status remains
the same.

User Response: If no file was
previously loaded, issue the LOAD
command specifying the files to be
loaded. If files are loaded, check them
for incorrect SLC or entry cards.

User Response: Check the description
of the command, correct the command
line, and reissue the cornman d.
056E
054W

Incomplete {fileid Iexecid}
specified
Explanation: You must specify the
filename and filetype or execname and
exectype for the EXEC to be loaded into
the DCSS.
System Action: The EXEC is not
loaded into the DCSS, the error is
recorded in the DCSS 'dcssname
DCSSMAP' file, and a prompt
(DMS298R) is issued asking if you want
to save the DCSS.
User Response: Correct the DCSSGEN
load list entry that caused the error.

055E

No entry point defined
Explanation: For the START command
or the START option of the FETCH,
LOAD, or INCLUDE command, either
the initial execution address is zero, or
there is no executable code at the
execution address, or nothing has been
loaded.
This message is also issued if a START
command (or FETCH command with the
START option) is issued following a
SET DOSPART command, resetting the
size of the DOS partition. Redefining
t:p.e partition size causes storage to be
reinitializedand any previous loads or
fetches must be reissued.
System Action: RC = 40.
Execution of the command is
terminated. Loader cleanup has been
performed on loaded files. This should
not interfere with a subsequent START
command.

254

VM/SP System Messages and Codes

File fn ft contains invalid
[namelaliaslentrylESD] record
formats
Explanation: For DMSLBM and
DMSNCP (GEN, ADD, REP), the
specified file is not in the expected
format. MACRO and MEND cards must
be included in the MACRO files, and the
prototype card must be specified with a
name that does not exceed eight
characters. If an © statement
appears, it must contain a name. A
MACLIB must contain 'LIB' in columns
4-6 of record one.
For DMSLBT, the specified file has
more than 255 entry points (ESD only),
or has records which are incompatible
or missing. The NAME field in the
CSECT instruction of the specified file
must have a valid symbol or label.
For DMSLIO, an invalid condition was
found in a TEXT or TEXTLIB file.
TXTLIB files created on EDF disks must
have "PDS" in columns 4-6 of record
one. TXTLIB files created on non-EDF
disks must have "LIB" in columns 4-6 of
record one. RLD data must be
compatible with the TEXT file or
TXTLIB member to which is belongs. If
an ICS statement was submitted, the
specified name was previously defined,
or the initial length of the CSECT was
not found in the ESD card.
For DMSSYN, the specified file is not in
the expected format. The SYNONYM
file must contain 80-byte records in free
form format, with columns 73-80
ignored. The data consists of a command
name followed by a blank and the user
synonym. This may optiunally be
followed by a count which is preceded
by at least one blank.

DMS
For DMSZAP, either the header record
for TXTLIB or LOAD LIB was invalid, or
the pointer to the directory or module
map was in errol'.

TXTLIB VMFTXT ADD
membername < (FILename < ) > >
RENAME VMFTXT TXTLIB A
libname TXTLIB A

For the VMFTXT command, the
memberlist EXEC file was not in the
required format.

commands. If the filetype is not TEXT,
then erase VMFTXT TXTLIB A and
then reissue the command.

System Action: RC = 32.
Execution of the command is
terminated. The system status remains
the same. For DMSGLB, the library is
not globaled and the operation
continues for any other libraries named
in the command.

For DMSZAP, recreate the library or
module.
Then reissue the command.

057E

For the VMFTXT command, the invalid
record is ignored. Processing continues
for any remaining records in the file.

Explanation: For the TAPE command,
a record that was read was not in TAPE
DUMP format. For the TAPE MAC
command, the tape was not in the
IEHMOVE unloaded PDS format, or the
PDS logical record length is not 80.

User Response: For DMSLBM and
DMSNCP, issue the MACLIB COMP
command, then check the MACLIB with
a MACLIB MAP command. Correct the
format error.

System Action: RC =- 32.
Execution of the command is
terminated. For the TAPE command, if
the DEN, TRTCH, 7TRACK, 9TRACK,
or 18TRACK options were specified, the
modeset byte has been set for the
specified device (1' APn, where n is a
character from 0 to 9 or A to F; the
default is T API).

For DMSGLB, the specified library does
not have "LIB" in columns 1-3 or 4-6 of
the first record. One possible cause is
the library may be in packed format.
Correct the library and reissue the
command.
For Dl\IISSYN, correct the format of the
file.

User Response: For the TAPE
command, rewrite the file onto tape
using the TAPE DUMP command. For
the TAPEMAC command, recreate the
file on tape using the as IEHMOVE
utility program. Then reissue the
command.

For DMSLIO, recreate the TXT LIB or
TEXT file.
For DMSLBT, if the message specifies
ESD. check for more than 255 entry
points for a member; otherwjse, check
for invalid or missing records. If the
NAME field in the CSECrr instruction
was left blank, enter a valid symbol or
label.
For the VMFTXT command, correct the
invalid entry in the memberlist EXEC
file. If the member specified in the
invalid record has a filetype of TEXT,
you may issue the:

Invalid record format

058E

End-of-file or end-of-tape [on
TAPn]
Explanation: The end of the file or
tape was reached.
For DMSTPJ, an end-of-tape condition
was encountered while doing a write,
WT1\,1 (write tape mark). or ERG (erase
gap) operation.

C()l1vt>rsat.ional Monitor System (eMS) Messages

255

DMS
System Action: RC = 40.
Execution of the command is
terminated. For DMSTPI, the last
operation is not completed. The tape is
positioned at the end. If the DEN~
TRTCH, 7TRACK, 9TRACK, or
I8TRACK options were specified, the
modeset byte has been set for the
specified device (T APn, where n is a
character from 0 to 9 or A to F; T API is
the default).

060E

Explanation: The files requested were
not on the specified disk or if the disk
contains no files and you accessed it
R/O~ your access fails; therefore, the
disk is not accessed. If another disk
was already accessed as mode "fm," it is
released.
System Action: RC = 28.
Execution of the command is
terminated. The system remains in the
same status as before the command was
entered.

User Response: For DMSTPD, you
may space the tape forward and
continue, or rewind the tape and quit;
this can be an information message
rather than an error condition,
depending on the circumstances.

User Response: Check to see that the
fileid is specified correctly, and reenter
the command.

For DMSTPJ, if the position of the tape
is not as expected, use the appropriate
TAPE control function to reposition it.

06lE
For DMSBOP, ensure that the proper
tape has been mounted. If so, rewind
and reposition the tape and retry.

System Action: RC = 36.
Execution of the command is
terminated. The system status remains
the same.
User Response: If you wish to access
the specified device in read-only mode,
first release the disk by issuing the
RELEASE command and then reissue
the ACCESS command.

256

System Action: RC = 24.
Execution of the command is
terminated. The translate table remains
unchanged.

vdev already accessed as
read/write mode-disk
Explanation: You are trying to access
the specified device in read-only mode,
but you have already accessed it
read/write mode. You cannot have a
disk accessed as both read-only and
read/write, because the read-only file
directory would not reflect any updates
you made until the next time you
accessed the disk.

VM/SP System Messages and Codet-;

N 0 translation character specified
Explanation: A SET INPUT or SET
OUTPUT command was issued without
a translation character.

For DMSCLS, rewind and reposition the
tape and reissue the command.

059E

File {n [It [{m]] not found; disk
mode(vdev) will not be accessed

User Response: Reissue the command
with the appropriate translation
character.

062E

{Invalid {character [char] I*} in
[output] fileid Un {t IlmJJ ISO and
SI are invalid fileid characters}
Explanation: The character specified
whether an asterisk (*), equal sign (=),
or other was invalid in the fileid in
which it appeared.
System Action: RC = 20.
Execution of the command is
terminated. The system status remains
the same, with the following exceptions
for the COPYFILE command:

(
\

DMS
•

•

If the APPEND option was specified
and the copying process began
before the error was discovered,
then records were appended to the
output file.

System Action: RC = 40.
Execution of the command is
terminated. The system status remains
the same.

In multiple-output-file mode, several
output files may have been created
before the error was discovered.

If an asterisk is specified as the
filename, either the filetype must be
omitted or it must be specified as an
asterisk

Invalid [character]
'[ = 1*lcharlchar],in fileid ['in it
[frn]']
Explanation: The character specified,
whether an asterisk (*), equal sign (=),
or other, was invalid in the fileid in
which it appeared.
Systenl Action: The EXEC is not
loaded into the DCSS, the error is
recorded in the DCSS 'dcssname
DCSSMAP' file, and a prompt
(DMS298R) is issued asking if you want
to save the DCSS.
User Response: Correct the DCSSGEN
load list entry that caused the error.

No [sortltranslationlspecification]
list {enteredlgiven}
Explanation: A list was requested in
response to the SORT command, or to
the SPECS option or TRANSLATE
option of the COPYFILE command, but
a null line was entered in response. The
XEDIT subcommand SORT was entered
with no sort fields specified.

If the NEWFILE (the default),
REPLACE, or OVL Y option was
specified, and the copying process
began before the error was
discovered, then COPYFILE
CMSUTl, on the output disk,
contains the records copied so far.

User Response: Check the description
of the command format and reissue the
command.

062W

063E

User Response: Reissue the command,
and enter the list when it is requested.

Invalid [translate] specification at
or near list

064E

Explanation: An invalid specification
was included in the list entered when
either the SPECS option or the TRANS
option was specified. "list" is the
portion of the list you entered that is in
error. Some of the errors that can cause
this message to appear in conjunction
with the SPECS option are the
following:
•

A source specification was entered
with no target specification.

•

An invalid decimal number was
entered for an input or output
column.

•

An input file specification of the
form "nn-mm" was given, but mm
was smaller than nn.

•

A string was specified without an
ending delimiter.

•

A zero length string was specified.

•

An invalid hexadecimal number was
specified. or an odd number of
hexadecimal digits followed the "H"
of such a specification.

Conversational Monitor System (eMS) Messages

257

DMS
•

The continuation code (-+- + ) was
specified in the middle of a
specification, rather than at the
beginning of one.

User Response: Correct and reissue
the command.

067E
Some of the errors that can cause this
meRsage to appear in conjunction with
the TRANS option are the following:
•

An invalid hexadecimal number was
entered.

•

An odd number of characters was
entered.

•

The continuation code (+ +) was
entered in the middle of a character
pair.

Combined input files illegal with
PACK or UNPACK options
Explanation: An attempt was made to
combine several files at the same time
that the PACK or UNPACK option was
used. This message appears if there is
more than one input fileid, or if there is
an asterisk in the first fileid in single
output file mode.

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.

System Action: RC:::.-: 24.
User Response: Correct the command

Execution of the command is
terminated. The system status remains
the same.

User Response: Reissue the command

line and reissue the command.

068E

and enter the correct specification list
when it is requested.

065E

Explanation: The specified input file is
not in packed format, and was specified
in an UNPACK operation.

option option specified twice

Explanation: The option was specified
more than once in the command line.

System Action: RC = 32.

Execution of the command is
terminated. The system status remains
the same.

Execution of the command is
terminated. The system status remains
the same, except that in multiple output
file mode, several output files may
already have been created before the
error was discovered.

User Response: Reissue the command,

User Response: Correct the command

specifying the option only once.

line and reissue the command.

System Action: RC = 24.

066E

option1 and option2 are conflicting
options

Explanation: The specified options are
mutually exclusive and must not be
specified in the same command.

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.

258

Input file fn ft fm not in packed
format

VM/SP Hystem Messages and Codes

069E

Disk mode[(udev)] not accessed
Explanation: Either the specified disk
has not been accessed, or it is not·
correctly formatted for the command
issued. (For example, the command is
trying to write a CMS-formatted file on
an OS-formatted disk.)
For the RgCEIVE command, either:

(

DMS
1.

a filemode was specified on the
RECEIVE command and this mode
is READ/ONLY and the file cannot
be written onto this disk.

0691

Explanation: The disk specified in the
FILEDEF command has not been
accessed.

For the VALIDATE command, the
identifier is valid and the filemode is
not accessed.

System Action: This message is for
information only. Execution continues.
User Response: None.

070E

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same, with the following exception
for the TAPE command:

For the CONVERT command, the input
DLCS file disk you specified was not
found.
System Action: RC = 36.
Execution of the command is
terminated. The system status remains
the same.

If the DEN, TRTCH, 7TRACK, or
9TRACK options were specified, the
modeset byte has been set for the
specified device (TAPi, where: i = 1, 2,
3,4) or TAP1.

If this message is issued in response to a
prompt, there is no return code and the
prompt is reissued.

If you received this message in response
to a prompt and you currently have no
disks accessed in read/write mode,
terminate the command by entering 2
(or quit), access a disk in read/write
mode, and reissue the command.

Invalid {parameter
parameter Iargument argument}
Explanation: An invalid operand, or
too many or extraneous operands, were
specified in the command line or EXEC
statement.

For DMSDSL, the A-disk must be
accessed when the DOSLIB MAP
function is performed and the output is
directed to disk.

User Response: Access either the
specified disk or a disk with the correct
format, and then reissue the command.

[Output] Disk mode is not
accessed

User Response: Correct the command
line and reissue the command.

070W

Invalid {parameter
parameterlargument argument}
Explanation: An invalid operand, or
too many or extraneous operands, were
specified in the command line or EXEC
statement.
System Action: The EXEC is not
loaded into the DCSS, the error is
recorded in the DCSS 'dcssnaroe
DCSSMAP' file, and a prompt
(DMS298R) is issued asking if you want
to save· the DCSS.
User Response: Correct the DCSSGEN
load list entry that caused the error.

Conversational Monitor System (eMS) Messages

259

DMS
071E

ERASE

* * [fm I*] not allowed

•

Explanation: You cannot erase all files
on all disks using the ERASE command.
You can enter asterisks for the filename
and filetype, but you must specify the
filemode letter and number.

MAX DEPTH OF LOOP
NESTING EXCEEDED
RC=805
No more than four nested loops may
be specified.

•

System Action: RC = 24
Execution of the command is
terminated. The system status remains
the same.

ERROR READING FILE
RC=806
An 1/0 error occurred while an
EXEC file was being read.

•

INV ALID SYNTAX
RC=807
The syntax of the indicated
statement is invalid.

•

INV ALID FORM OF CONDITION
RC=808
This can occur from previously
unassigned variables. The final
result after the line is interpreted is
syntactically invalid.

•

INVALID ASSIGNMENT
RC=809
An attempt was made to assign a
value to an unspecified field; for
example,

User Response: Issue the FORMAT
command to erase all files on a disk, or
use the ACCESS command with the
ERASE option (all files on the disk are
erased the first time you write a new file
on the disk).

072E

Error in EXEC file /,n, line nnn:
message
Explanation: The EXEC interpreter
has found an error in file 'fn'., at line
'nnn'. 'message' may be anyone of the
following:
•

•

260

FILE NOT FOUND
RC=801
The specified file was not found on
the accessed disks. This message
can be issued when you try to
invoke an EXEC from within
another EXEC.
&SKIP OR &GOTO ERROR
RC=802
A request was made to move to a
statement above the beginning of
the file, or to a nonexistent label.
BAD FILE FORMAT
RC=803
The file is not in the required
format. For instance, it is packed
rather than unpacked, or the record
length is greater than 130.
TOO MANY ARGUMENTS
RC=804
A maximum number of 30 arguments
can be passed to an EXEC file.

VM/SP System Messages and Codes

•

MISUSE OF SPECIAL
VARIABLE
RC=810
Incorrect use of a special variable
was attempted. For example, an
attempt was made to assign a value
to &EXEC or to &TYPEFLAG.

•

ERROR IN &ERROR ACTION
RC=811
An &ERROR control statement
specified a eMS command that also
resulted in an error.

•

CONVERSION ERROR
RC=812
A variable in the line must be
converte~butcannotbe,becauseU

is a character value, it is not in the
proper format, or it has not been
initialized. For example,

DMS
A positive arithmetic variable
exceeded 8 digits.

'&IF &FLAG EQ 944'

If &FLAG was not previously

initialized, it is "null" or blank and
will cause a conversion error when
being converted to decimal. This
message is also issued if a
nonhexadecimal number is specified
after the characters "X" on the
right-hand side of an assignment
statement (for example, &A =
X'12AG'); or if a nondecimal number
is specified after the characters "X"
in any statement other than an
assignment statement (for example,
&TYPE X'120AO').
•

•

System Action: The file is logically
executed up to the point where the etTor
was detected.
User Response: Correct the EXEC file
and reexecute it.

TOO MANY TOKENS IN
STATEMENT
RC=813
More than 19 tokens appeared in a
single &READ VARS statement.
MISUSE OF BUILT-IN
FUNCTION
RC=814
One of the EXEC built-in functions
(for example, &CONCAT,
&DATATYPE, etc.) was used
incorrectly.
EOF FOUND IN LOOP
RC=815
An end of file occurred before the
command completed the requested
operation.
INVALID CONTROL WORD
RC=816
An invalid control word was
encountered in the input deck and
cannot be read.
EXEC ARITHMETIC
UNDERFLOW
RC=817
A negative arithmetic variable
exceeded 8 digits including sign.
EXEC ARITHMETIC
OVERFLOW
RC=818

SPECIAL CHARACTER IN
VARIABLE SYMBOL
RC=819
A special character was used in a
variable symbol. Only numeric and
upper case alphabetic characters are
to be used. The asterisk in the
special variable &* is an acceptable
character.

Note: For a tutorial description of the
CMS EXEC facility, see the VMjSP
CMS User's Guide. For a description of
the CMS EXEC control statements, see
the VMj SP CMS Command Reference.

I 073E

Unable to open file {ddnamelfn}
Explanation: CMS was unable to open
the specified ddname. An explanatory
message should appear with this
message.
For DMSMGC, the message compiler
tried to open a text file, but was unable
to do so.

System Action: RC = 28.
Execution of the command or program
is terminated. The abend code is loA
for LINK, LOAD, ATTACH, and XCTL
failures.
For DMSMGC, RC = 16.

User Response: If this message came
from the message compiler (DMSMGC),
contact your system programmer.
Otherwise, verify the ddname and
reissue the command. If you are using
the OS Loader, verify that the
LOAD LIB libraries in the GLOBAL list
exist.

Conversational Monitor System (CMS) Messages

261

DMS
074E

Error {resettinglsetting} auxiliary
directory

076E

Explanation: The auxiliary directory
could not be set or reset. This can
occur, for example, if the disk on which
the auxiliary directory resides is not
accessed when the command is issued,
or if it is accessed as a filemode other
than the one specified for it with a
previous GENDIRT command.
System Action: RC = 40.
If the error occurred on an attempt to
set the auxiliary directory, execution of
the command is terminated. The system
status remains the same. If, however,
the error occurred on an attempt to
reset the auxiliary directory, the
assembly has already been done, and
execution continues.

Explanation: An existing file has a
record length greater than the record
length entered in the command line.
System Action: RC = 40.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the command,
specifying a larger record length with
the LRECL option.

077E

[Device] devtype {invalidlillegal}
for input
Explanation: The device specified for
the input or output ddname is invalid.
This message will appear if the input
device specified is DUMMY, PRINTER,
or PUNCH, or if the output device
specified is READER, CRT, OS DISK, or
DOS DISK.
System Action: RC = 40.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the FILEDEF
command and specify the correct
input/output device.

End card missing from input deck
Explanation: Since the end card is
missing, the input file is not complete.
The deck is probably invalid.

User Response: Consult the system
programmer to find out what disk the
auxiliary directory is on and by what
filemode that disk should be accessed.
(It should have the filemode that was
specified for it with the GENDIRT
command.) Access the disk with the
proper filemode and reissue the
command.

075E

Actual record length exceeds the
one specified

System Action: RC = 32.
Execution of the command is
terminated. The card file is lost from the
reader.
User Response: The DISK DUMP
command must be issued to recreate the
file.

078E

Invalid card in {reader decklinput
decklinput file tn tt}
Explanation: For DMSDSK, a card
that was not punched by DISK DUMP
was encountered in the input deck. The
deck cannot be read by DISK LOAD.

For DMSGRN, an invalid card was
encountered in the input deck. The
deck cannot be processed by the
GEN3705 command.
System Action: RC = 32.
Execution of the command is
terminated. The system status remains
the same.
For Dl\ISDSK, the READER file closed
with the HOLD option.

262

VM/SP System Messages and Codes

DMS
User Response: For DMSDSK, reissue
the command in case there are valid
DISK DUMP cards followin~~ in the file.
If the same error occurs. nither retry.
use the READCARD command to load
the file, or use the CP PURGE command
to erase the reader file.

option was either not numeric or was a
greater number than allowed.
System Action: For DMSINI, message
DIVIS609R is reissued.
For DMSMGX, RC = 24; execution of the
command is terminated.

For DMSGRN, use the card image in
the error message to correct the card,
and reenter the command.

078W

For DMSMGX, correct and reissue the
XMITMSG command.

Sequence error detected loading
fn {t--expected seqnol found seqno2
Explanation: The sequence number
found is not the next sequential number.

)

User Response: For DMSINI, refer to
message DMS609R.

08lE

(NO)

System Action: RC.:;.-.: 32.
The file continues to be loaded.

Explanation: The only valid responses
to the query are "YES," "1," "NO," or
"0." None of these reponses was entered.

User Response: Check the filp after it
has been loaded for possible
transmission errors.

079E

On the SENDFILE screen, something
other than "YES" or ;'NO" was entered
in the fields reserved for choosing
options.

Invalid device address; reenter
System Action: Message DMS607R or
DMS610R is reissued.

Explanation: The device address
entered was specified incorrectly. that
is, it is not a valid hexadecimal
character or is not in the range of X'OOI'
to X'6.FF'.

For the SENDFILE menu, no system
action is taken.
User Response: See DlVlS607R or
DMS610R.

System Action: Message DIvlS606R or
DMS608R is reissued.

For SENDFILE, enter only "YES" or
"NO" in the options fields.

User Response: See DMS606R or
DMS608R.
082E
080E

Invalid reply; enter 1 (YES) or 0

IPL device error; reenter

Invalid {CYL/BLKloption} number
Explanation: For ClVIS initialization
(DMSINI), the CYL/BLK value entered
was not a valid decimal number.

Explanation: The device is not
currently defined, or it is not in
read/write status, or it is an
unsupported device type.

For the XMITMSG command
(DMSMGX), the value for the specified

System Action: Message DMS608R is
reissued.
User Response: See DMS608R.

Conven;ational Monitor System (eMS) Messages

263

DMS
083E

Nucleus CYL/BLK specification
unacceptable; error x
Explanation: The cylinder or FB-512
block number specified for the nucleus
start address does not meet the
requirement indicated by the error code.
Code Meaning
1
The nucleus will overlay CMS files
on the minidisk.
2
The nucleus start address is
beyond all formatting.
3
The starting FB-512 block number
is not on a 256-block boundary.
4
A total of 1060 FB-512 blocks are
not available, including the
starting block number.

Error in in it im, line nnn: message

085E

Explanation: The EXEC 2 interpreter
has found an error in file "fn ft fm," at
line "nnn." "message" may be anyone
of the following:

•

file not found
RC = 10001
The input file was not located on an
accessed disk.

•

wrong file format
RC=10002
The line length exceeds 255 bytes.

•

word too long
RC = 10003
An attempt was made to assign more
than 255 bytes to a variable, or a
word in a line is longer than 255
bytes.

•

statement too long
RC = 10004
The length of the statement exceeds
255 bytes.

•

invalid control word
RC = 10005
A word with a leading ampersand
was found where a control word was
expected, but it is not recognized as
a control word.

•

label not found
RC = 10006
During a scan for a label, the label
was not located.

System Action: Message DMS609R is
reissued.
User Response: If RC = 1, respond to
DMS609R with a larger cylinder value
or FB-512 block number. If RC = 2,
specify a smaller value. If RC = 3,
specify a multiple of 256. If RC = 4,
specify a lower location for the nucleus.
In any event, use of the FORMAT
command with the RECOMP option may
be necessary.

084E

Invalid use of FROM and TO
options
Explanation: The 'FROM' location
exceeds or is equal to the 'TO' location.
System Action: RC = 24.
Execution of the command is
terminated. The syst.em status remains
the same.

•

invalid variable name
RC = ]0007
A word without a leading ampersand
was found in a place where a
variable was expected.

•

invalid form of condition
RC= 10008
Either the conditional operator is
invalid or one of the operands has a
null value.

•

invalid assignment
RC = 10009

User Response: Correct and reissue
the command.

264

VM/SP System Messages and Codes

(

DMS
)
•

•

)

RC =:= 10020
An attempt was made to assign a
value to an argument when the
number of that argument exceeded
&N. For example,

An operator in an assignment
statement is not (+), or (-), or 'of'
does not follow the function name.

missing argument
RC= 10010
A required argument is missing.
invalid argument
RC = 10011
An argument has an invalid value.
conversion error
RC=10012
An error has occurred in converting
from a string to a numeric value.

•

numeric overflow
RC=10013
A number has overflowed the
defined system limits: (2**31)-1 or
-(2**31).

•

invalid function name
RC=10014
If the function name starts with an
ampersand, it is not a predefined
function, or if it starts with a dash,
it is not a label in the file.

•

end of file found in loop
RC=10015
The end of the file was found before
the end of the loop.

&ARGS ABC
&4=D

would cause this error.

•

statement out of context
RC = 10021
&RETURN was encountered when
no subroutine was active.

•

program interrupted
RC = 10094
The system interrupted execution of
your EXEC 2 program. The 'HI'
(halt interpretation) immediate
command was probably issued.
Certain utility modules may force
this condition if they detect a
disastrous error condition.

•

fatal error while handling
SHARE subcommand
RC=10095
The error 'insufficient storage'
occurred while handling a share
subcommand.

•

insufficient storage available
RC = 10097
Insufficient storage to complete the
statement.

division by zero
RC=10016
A divisim} by zero was detected.
invalid loop condition
RC = 10017
The conditional expression in an
&LOOP statement has an invalid
format.
error return during &ERROR
action
RC = 10019
An error has occurred during
execution of the action specified on
an &ERROR statement.
assignment to unset argument

This mav be caused by &STACK,
assignm~nt to a variable, or other
actions that require additional
storage.

file read error nnn
RC = 10098
The operating system was unable to
read the file or some part of the file.
The return code "nnn" indicates one
of the following condition.s:
Code Meaning
1

The file was not found.

Conversational Monitor System (eMS) Messages

265

DMS
2

The 'HI' (halt interpretation)
immediate command was probably
issued. The message could also
result from a utility module error.

The address of the huffer was
not within virtual storage
limits.

A permanent disk error
occurred. This may occur if
you link to and access another
user's disk, then try to read a
file that wa~ refiled by its
owner after you issued the
ACCESS command. Reissue
the ACCESS command and try
to read the number again.
5

The number of records is less
than 0 or greater than 32768.

The fixed/variahle flag is not F
or V.

System Action: The file is logically
executed up to the point where the error
was detected.
User Response: Correct the EXEC 2
file and reexecute it.
Note: For information on EXEC 2, see
the VM/ SP EXEC 2 Reference.

086E

The specified file is· open for
writings; it must be closed and
opened for reading.

The number of records is
greater than 1 for a
variable-length file.

The end of the file was
reached.

An invalid displacement
appears in the AFT for a
variable length file.

An invalid character appears
in the filename.

An invalid character

•

266

System Action: RC 0= 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the command
with a valid ddname. With the DLBL
command. use a ddname of seven
characters or less. If you are an as
user. enter the first seven characters of
your program's ACB ddname. If these
seven characters are not unique within
the program (that is, the eighth
character distinguishes two ACBs in the
same program), recompile the program
using different ddnames.

086W

DLBL ddname DUMMY invalid for
VSAM

appf.~ars

in the filetype.
•

Explanation: The ddname specified
with the command is invalid.

The record read is longer than
the buffer.

Invalid DDNAME ddname

trace error nnn
RC ~:= 100H9
A command or subcommand issued
as an action of &TRACE returned
the error code 'nnn'. Execution of
the current EXgC 2 file is
terminated.
Program Interrupted
RC=10196

VM/SP System Messages and Codf>s

Explanation: The ddname in the ACB
being opened was specified in a previous
DLBL command with the DUMMY
operand, which is invalid for VSAM.
Systenl Action: RC-=-, 8.
This message accompanies a DOS/VS
VSAl\f open error code X'1l'. The as
user is restricted from using a DUMMY
VSAM data set. An attempt to do so
will cause unpredictable results at
OPf~N time. An additional message

DMS
from the program product being used
may follow.

Explanation: An attempt was made to
open or close a DTF table of a type not
supported by CMS.

User Response: Reissue the DLBL
command specifying a mode for this
ddname, and then restart the program
that caused the error.

087E

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.

Invalid assignment of SYSaaa to
device devtype
Explanation: The ASSGN command
that was entered violated a restriction
on the assignment of SYSaaa to a
virtual device. The ASSGN command
restricts the assignment of logical units
to virtual devices as follows:
Logical Units Valid Assignment
SYSOOO-SYS241 to any device as
specified by the ASSG N
command.
SYSLOG
to terminal and printer
SYSLST
to printer, disk, and
tape
SYSIPT
to reader, disk, and tape
SYSPCH
to punch, disk, and tape
SYSRDR
to reader, disk, and tape
SYSCAT
to disk
SYSCLB
to disk
SYSRLB
to disk
SYSSLB
to disk
SYSIN
to reader, tape, and disk
SYSOUT
to tape

Unsupported DTF type dtftype

088E

User Response: None; CMS/DOS only
supports those DTF types identified in
the CMS/DOS publications.

{Open IClose} error code nn on
{fnISYSaaaITAPn}

089E

Explanation: The error code in the
message identifies the error situation.
Code Meaning
1

The logical unit (SYSaaa) in the
DOSCB does not match the logical
unit in the DTF table.

CMS/DOS does not support writing
to as or DOS disks. All files must
be written to CMS disks.

An attempt was made to open or
close a sequential disk file, VSAM
file, or private source statement
library, but no DLBL command
was issued with the DLBL ddname
equal to the DTF ACB filename.
CMS/DOS requires a user-issued
DLBL for all sequential disk files,
VSAM input and output files, and
private libraries.

An attempt was made to open or
close a DTFCD or DTFPR with
ASOCFLE/FUNC operands
specified in the DTF macro. These
operands are not supported under
Cl'vIS/DOS.

An attempt was made to open an
input sequential disk file from an
as disk, but no extent information
was found in the OSFST associated
with the file.

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the ASSGN
command, specifying a valid
combination of logical unit and virtual
device.

Conversational Monitor System (eMS) Messages

267

DMS
6

An attempt was made to open a
sequential disk file for input, but
the file was not found on any of
the accessed disks.

The device type in the DTF being
opened or closed is incompatible
with the PUB device type for the
specified unit.

The system or programmer logical
unit is unassigned (PUB pointer in
LUB = X'FF').

There is no CMS/DOS support for
reading tapes backward. When
the operand READ = BACK is
specified on the DTFMT macro, a
flag is set in the DTF at
compilation time indicating this
condition. CMS/DOS supports
tape processing only in a forward
direction.

268

An attempt was made to open or
close a DTFMT (tape data file) and
'ASCII = YES' was specified in the
DTF macro. This operand is not
supported.
An attempt was made to open a
DTFCP or DTFDI tape file with
'FILABL = STD' specified.
However, no VOL1/HDR1 was
encountered.
PUB information for the tape
logical unit being opened (track
mode indicator or density) is
incompatible with the tape drive.
The tape is a 3420 tape drive but
an invalid tape drive model
number (valid model numbers are
3,4, 5, 6, 7, and 8).
While opening a DTF associated
with a file on an OS or DOS disk~
an I/O error occurred while
reading the extent information for
the specified data set.

VM/SP System Messages and Codes

SYSIPT /SYSRDR is assigned to
tape and the record length is not
80 or 81 bytes.

An unexpected error situation was
encountered while performing a
tape I/O operation.

The SAM OPEN/CLOSE (in the
CMS/DOS environment) routines
have returned with an error
indicating that the DTF currently
being processed could not be
opened because of a lack of virtual
storage.

An attempt was made to OPEN a
SAM file in VSAM space. This
feature is not supported in
CMS/DOS.

An attempt was made to fetch an
invalid or unsupported VSE/AF
OPEN transient area.

For MOVE FILE to process a DOS
input file on FB-512 devices, the
RECFM and BLOCK must be
specified on the input FILEDEF
for nn. For a fixed block RECFM,
the LRECL also must be specified.

An attempt was made to open a
non VSAM file on the OS- or
DOS-formatted 3380 DASD
specified by SYSaaa. CMS/DOS
supports the 3380 fOl' VSAM files
only.

System Action: RC=36.
Execution of the command is
terminated. The system status remains
the same.
User Response: Correct the error and
reissue the command.
For error code 22, if the file you are
trying to access is a VSAM file, use an
ACB to open it. If it is anon VSAM file,
you cannot open the file under
CMS/DOS.

DMS
090E

Invalid device class deuclass for
deutype

093E

Explanation: The device class
information returned from the CP
DIAGNOSE request (code 24) conflicts
with the device being assigned.

MVCOM macro attempted to alter
positions other than 12-23 of
COMREG
Explanation: The specified MVCOM
macro is attempting to alter a position
other than the allowed positions 12 to 23
of the communications region.

System Action: RC = 36.
Execution of the command is
terminated. The system status remains
the same.

System Action: RC = 100.
Execution of the command is
terminated. The system status remains
the same.

User Response: Reissue the command.
If this fails, call IBM for software
support.

User Response: Correct the
specification of the MVCOM macro and
retry.

)

(

09lE

Save area address in partition PIB
not equivalent to LTA save area
address

094E

Explanation: The current save area
address in the PIB (Partition
Information Block) is not the same as
the save area in the LT A (Logical
Transient Area).

Explanation: The address specified in
the MVCOM macro is not within the
range of the virtual machine.
System Action: RC = 100.
Execution of the command is
terminated. The system status remains
the same.

System Action: RC = 100.
Execution of the command is
terminated.

User Response: Correct the address
specified and retry.

User Response: Reissue the command;
if the problem persists, call IBM for
software support.
095E
092E

STXIT save area address invalid
Explanation: The specified save area
address in a STXIT operation is not
within the address range of the virtual
machine.
System Action: RC = 100.
Execution of the command is
terminated. The system status remains
the same.
User Response: Verify the save area
address and reissue the command.

FROM address on MVCOM macro
invalid

Invalid address ustor
Explanation: The specified address is
not within the range of the virtual
machine, is not a valid storage address,
or is not equal to or greater than
X'20000'.
System Action: RC = 100.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the command
with a valid address.

Conversational Monitor System (eMS) Messages

269

DMS
096E

File fn ft data block count
incorrect
Explanation: The number of data
blocks read from tape (for file 'fn ft')
does not match the number in the model
file status table written on the tape
when the file was dumped.

User Response: Use the "SET DOS ON
mode" command to activate a SYSRES
disk, and reissue the command.

098E

Explanation: The command requires
the specification of a phase name or
procedure name.

System Action: RC = 32.
Execution of the command is
terminated. The portion of the file 'fn
ft' loaded exists on disk as tape
CMSUTl.

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.

User Response: To ensure that the file
is properly loaded, reposition the tape to
the beginning of the. file and reissue the
TAPE LOAD command.

096S

Unsupported function in a LIOCS
routine for command
Explanation: A Logical IOCS routine
was called to perform a function which
the routine was not generated to
perform.
System Action: RC = 100.
Execution of the command is
terminated. The system status remains
the same.
User Response: Verify that all logical
functions to be performed are supported
by the Logical IOCS routine linked with
your program.

097E

User Response: Reissue the command
supplying a phase name or procedure
name.

099E

{CMS/DOS environment [not]
activelIOERROR reading fn}
Explanation: If the message is
CMS/DOS ENVIRONMENT NOT
ACTIVE, the CMS/DOS environment
must be active in order for the command
to execute.
If the message is CMS/DOS
ENVIRONMENT ACTIVE, the
CMS/DOS environment must not be
active in order for the command to
execute.
If the message is I/O ERROR READING
fn, an I/O error has occurred while
reading the specified file.

No SYSRES volume active
Explanation: No system residence disk
(SYSRES) is active; therefore, no
procedure library or relocatable library
is active.
System Action: RC = 36.
Execution of the command is
terminated. The system status remains
the same.

270

No {PHASEIPROCEDURE} name
specified

VM/SP System Messages and Codes

Systenl Action: RC = 40.
Execution of the command is
terminated. The system status remains
the same.
User Response: Use the SET DOS
command to activate or deactivate the
eMS/DOS environment and reissue the
command. For IOERROR, correct the
cause of the 1/0 error and reissue the
command.

/
~

DMS
099W

Generation parameters
incolnpatible with VM/370
Explanation: The parameters specified
on the HOST macro in the stage one
input stream for an NCP or PEP control
program were not equal to the values
required by VM/SP. The control
program may not operate correctly if
used by VM/SP. (This message does not
prohibit saving or loading the control
program. It may not indicate an error if
the VM/SP generation and load
procedures are used for a 8704/3705
control program intended for use by a
virtual machine system other than
VM/SP.)

)

even if the disk was not specifically
altered; the RELEASE command will
rewrite the directory.
System Action: For S-ST AT, the
S-ST AT is built in user storage. For
Y-ST AT, the Y-disk is accessed using
the CMS ACCESS command.
User Response: Call your system
support personnel.

lOlE

Batch not loaded
Explanation:
1.

The CMSBATCH command was
issued after the first carriage return
following IPL, or

The CrvISBATCH module
encountered errors trying to load
the DMSBTP TEXT S2 file (Batch
processor). See the LOAD command
for possible errors, or

The CMSBATCH module could not
locate the DMSBTPAB entry point
in Dl\:1SBTP while searching the
loader tables. At this point
DMSBTP has already been loaded.

Systenl Action: For DMSNCP,
RC=99.
Processing continues.
User Response: None.

IOOE

No batch processor available
Explanation: The CMSBATCH module
could not find the DMSBTP TEXT S2
file (Batch processor) on any system
disk.
System Action: RC = 40.
At this point, the operator has a normal
CMS interactive machine, not a hatch
machine.
User Response: Contact your system
support personnel.
Routing: This message is displayed at
the Batch Facility console at Batch
initialization time.

lOOW

Shared {S-STATIY-STAT} not
available

System Action: RC = 88.
At this point, the operator has a normal
CMS interactive machine, not a batch
machine.
User Response: If the explanation is
(1) follow start-up procedure (starting
with IPL). If it is (2) or (3), contact your
system support personnel.
Routing: This message is displayed at
the Batch Facillty console at Batch
initialization time.

Explanation: The S-disk or Y-disk
directory has been re-written to disk
since the CMS system was last saved.
This can occur if either disk was
accessed in R/W mode and then released

Convel'sational Monitor System (eMS) Messages

271

DMS
lOIS

SPECS temp string storage
exhausted at storarea

Error nn reading file fn ft fm [from
{diskIXEDIT}]

104S

Explanation: A specification list was
so long that the storage area reserved
for storing specification strings was
exhausted.

Explanation: An unrecoverable error
occurred while reading the file from
disk. nn indicates the nature of the
error; it may be one of the following:

System Action: RC = 8.
execution of the command is terminated.
The system status remains the same.

Code Meaning
1
2

User Response: Copy the file twice,
possibly using the OVL Y option a
second time, so that less string storage
is needed each time.

102S

Too many file ids
Explanation: Too many input fileids
were specified.
System Action: RC = 88.
Execution of the command is
terminated. The system status remains
the same.

5
7

User Response: To correct this
situation, use two COPYFILE
commands, specifying the APPEND
option with the second one.
9

103S

Number of SPECS exceeds
maximum nn

Explanation: More than 20
specifications were entered.
12
System Action: RC = 88.
Execution of the command is
terminated. The system status remains
the same.
User Response: Use more than one
COPYFILE command, possibly
specifying OVL Y after the first one.

272

VMjSP System Messages and Codes

The specified file was not found.
The buffer area is not within user
storage limits.
A permanent disk read error
occurred. This may occur if you
link to and access another user's
disk, and try to read a file that was
refiled by its owner after you
issued the ACCESS command.
Reissue the ACCESS command and
try to read the file again.
The number of records is less than
zero or more than 32768.
The fixed/variable flag in the file
status table entry is not F or V.
The given storage area was smaller
than the actual size of the records
read. (This error is valid if
reading the first portion of a large
record into a small buffer. It does
not cause the function to
terminate.)
The file is open for writing and
must be closed before it can be
read.
Only one record can be read for a
variable-length file. In this case,
the number of records is greater
than 1.
An unexpected end of fil e occurred
(the record number specified
exceeds the number of records in
the file).
A variable-length file has an
invalid displacement in the active
file table.
An invalid character was detected
in the filename.
An invalid character was detected
in the filetype.

(

DMS
19

25
26

An I/O error occurred on a FBA
device. This was indicated by a
non-zero condition code from a
DIAGNOSE code X'20'. Error
detected in module DMSDIO.
Insufficient virtual storage is
available.
Requested item number is
negative, or item number plus
number of items exceeds file
system capacity.
An attempt was made to update a
variable-length item with one of a
different length.

System Action: RC = 100 or RC = Inn
('nn' described above)
Execution halts. The system remains in
the same status as before the command
was entered.
For DMSEDI, the edit session is
terminated. If the error occurred during
a RENUM operation, the workfile is
erased and the file being edited remains
unchanged.
For DMSEXL, the file specified in the
EXECLOAD command was not loaded
into storage. The execution of the
command is terminated.
For DMSDSL, the condition of the
DOSLIB file is unpredictable.
For DMSGLO, no global variable
table(s) were created
For DMSLBM, the condition of the
MACLIB file is unpredictable.
For DMSGLB, t~lat library is not
globaled but the operation continues for
any other libl'aries nRmed in the
command.
For DMSXGT, if t.he error occurred
during a G ~~T operation, the
subcommanJ is terminated and the
editing session continues.
For DM;:;XIN, the execution of the
command or subcommand is terminated.
If multiple files were being edited, the
editing session continues for those files.

For DMSXRE, if the error occurred
during a RENUM operation, the
subcommand is terminated and the
editing session continues.
For the TAPE command, if the DEN,
TRTCH, 7TRACK, 9TRACK, or
ISTRACK options were specified, the
modeset hyte has been set for the
specified device (TAPn, where n is a
character from 0 to 9 or A to F; the
default is T API). Some records may
have been written on tape.

User Response: If you can determine
the problem from the "Explanation" and
remedy the condition, reissue the
command. If not, retry the command and
if the problem persists, call your system
support personnel.
For DMSDGL, verify DOSLIB integrity
with the DOSLIB MAP command.
For DMSGLB, RDBUF has returned a
RC other than 0, 1, or S. RC = 1
indicates it is an OS/DOS DISK and
RC = S occurs if the LRECL is greater
than SO. Either of these conditions is
acceptable.
For DMSLBM, verify MAC LIB integrity
with the MACLIB MAP command.
For DlVfSLIO and DMSMOD, reissue the
entire LOAD/INCLUDE sequence after
checking the error conditions.
The problem may be that the in-core
directory for the M-disk that contains
the file being loaded, does not match the
actual directory. The real disk
directory may have been changed since
the disk was last accessed, or if on the
system disk, the saved system may need
resavIng.
For error code '09', issue an FSCLOSE
macro for the file. If a permanent disk
read error occurs (code 3), it may be the
result of the user having detached a
virtual disk without releasing it. CMS,
not realizing that the disk is no longer

Conversational Monitor System (eMS) Messages

273

DMS
part of the virtual machine, assumes
that the disk is still active and
encounters an error when it tries to
read or write the file.

15
19

Error nn reading file In It {m [from
{diskIXEDIT}]

l04W

Explanation: An error occurred while
reading the file from disk. nn indicates
the nature of the error; it may be one of
the following:

27
Code Meaning
1
2

7
8

274

The specified file was not found.
The buffer area is not within user
storage limits.
A permanent disk read error
occurred. This may occur if you
link to and access another user's
disk, and try to read a file that was
refiled by its owner after you
issued the ACCESS command.
Reissue the ACCESS command and
try to read the file again.
The n urn bel' of records is less than
zero or more than 32768.
The fixed/variable flag in the file
status table entry is not F or V.
The given storage area was smaller
than the actual size of the records
read. (This error is valid if
reading the first portion of a large
record into a small buffer. It does
not cause the function to
terminate.)
The file is open for writing and
must be closed before it can be
read.
Only one record can be read for a
variable-length file. In this case,
the number of records is greater
than l.
An unexpected end of file occurred
(the record number specified
exceeds the number of records in
the file).
A variable-length file ha~ an
invalid displacement in the active
file table.
An invalid character was detected
in the filename.

VM/SP System Messages and Codes

An invalid character was detected
in the filetype.
An I/O error occurred on a FBA
device. This was indicated by a
non-zero condition code from a
DIAGNOSE code X'20'. Error
detected in module DIviSDIO.
Insufficient virtual storage is
available.
Requested item number is
negative, or item number plus
number of items exceeds file
system capacity.
An attempt was made to update a
variable-length item with one of a
different length.

System Action: The EXEC is not
loaded into the DCSS, the error is
recorded in the DCSS 'dcssname
DCSSMAP' file, and a prompt
(DMS298R) is issued asking if you want
to save the DCSS.
User Response: Correct the DCSSGEN
load list entry that caused the error.

l05E

No job card provided
Explanation: The first record of the
user job was not a IJOB card.
System Action: The batch facility has
flushed the user job and continued with
the next user joh.
User Response: Resubmit the job to
the batch facility with the first record of
the job in batch facility IJOB format.
Routing: This message is displayed at
the Batch Facility console during user
job execution.

105S

Error nn writing file {n It {m [{on
disklto XEDIT}]
Explanation: An unrecoverable error
occurrpd while writing on disk. nn
indicate::; the nature of the error; it may
be one of the following:

(

DMS
Code Meaning
2
4
5
6
7

8
9
10
11
12
13

17
18
19

20
21
22
25
26

The virtual storage address is O.
The first character mode is invalid.
The second character mode is
invalid.
The number of records in the file is
too large; it cannot exceed 65,533.
An attempt has been made to skip
over an unwritten variable-length
item.
The number of bytes was not
specified.
The file is already active for
reading.
The maximum number of CMS files
(3400) has been reached.
The fixed/variable flag is not F or
V.
The disk is not a CMS read/write
disk.
The disk is full (recoverable error)
or insufficient storage is available
for writing to XEDIT.
The number of bytes to be written
is not integrally divisible by the
number of records to be written.
The length of this record is not the
same as that of the previous
record.
The fixed/variable flag is not the
same as that of the previous
record.
A variable-length record is greater
than 65K bytes.
The number of records is greater
than 1 for variable-length file.
The maximum number of data
blocks per file (16060) has been
reached.
An invalid character has been
detected in filename.
An in valid character has been
detected in filetype.
Virtual storage capacity has been
exceeded.
Insufficient virtual storage is
available.
Requested item number is
negative, or item number plus
number of items exceeds file
system capacity.
An attempt was made to update a
variable length item with one of a
different length.

System Action: RC = 100.
Execution of the command terminates.
The system status remains the same.
For DMSDSK, the reader file is saved.
The status of the output file is
unpredictable.
For DMSEDI, the edit session
terminates. The status of the file is as it
was before the edit session or at the
execution of the last SAVE subcommand
or automatic save. The RENUM
workfile is erased. A workfile, EDIT
CMSUT1, may have been created on the
input disk.
For DMSEXL, the file specified in the
EXECLOAD command was not loaded
into storage. The execution of the
command is terminated.
For DMSDSL, the condition of the
DOSLIB file is unpredictable.
For DMSLBM, the condition of the
MACLIB file is unpredictable.
For DMSLBT, DMSLST, DMSMOD,
DMSSRT, DMSTPD, and DMSUPD, the
status of the output file is
unpredictable.
For DMSRDC, the reader is closed with
a HOLD status to preserve the file.
However, if nn = 13 and the error occurs
while writing the last block of the file to
disk, then the file will have already
been purged before the reader is closed.
For DMSTPI, if the DEN, TRTCH,
7TRACK, 9TRACK, or 18TRACK
options were specified, the modeset byte
has been set for the specified device
(T APn, where n is a character from 0 to
9 or A to F; the default is TAPl). The
status of the output file is
unpredictable. The tape may not be in
the same position as before the
command was entered.
For DMSXCP, the EXCP request fails
wi th the return code nn. Check the

Conversational Monitor System (eMS) Messages

275

DMS
attributes of the file specified in the
DTF and DLBL.

For DMSXFD, if the error occurred
during a FILE or SAVE, at temporary
work file, XEDTEMP CMSUTL may
have been created on the input disk.

System Action: The batch facility
flushes the user job and continues with
the next user job.

For DMSXPT, if the error occurred
during a PUT (D) operation, the
subcommand is terminated and the
editing session continues.

User Response: Resubmit the job to
the batch facility with a valid userid
and an account number in the batch
facility IJOB card.

For DMSXRE, if the error occurred
during a RENUM operation, the
subcommand is terminated and the
editing session continues.

Routing: This message is displayed at
the batch facility console during user
job execution.

User Response: If you can determine
the problem from the "Explanation"
above and remedy the condition, reissue
the command. If not. reissue the
command and if the problem persists,
call your system support personnel.

106S

For DMSLIO, reissue the
LOAD/INCLUDE sequence from the
beginning, after checking the above
error conditions.

106E

/JOB card format invalid
Explanation:
1.

The batch facility detected a missing
or invalid userid or missing account
number on the user ,!.JOB card, or

The userid (if provided) does not
exist in the directory, or

VM/SP System Messages and Codes

System Action: RC = 88.
The system tries to write the dictionary
up to and including the previous text
deck; then it terminates execution of the
command.

For DMSLBM, use the MAC LIB MAP
function to verify MACLIB integrity.

For DMSXCP, specify a smaller
partition with the SET DOSP ART
command, or use the CP define storage
command for a larger machine and IPL
CMS.

Number of member names
exceeds maximum of 2000; file
TEXT not added

Explanation: The number of entries in
the dictionary has exceeded the
maximum of 2000.

For DMSDSL, use the DOSLIB MAP
function to verify DOSLIB integrity.

276

A user IJOB card exit routine
(BATEXIT2) returned a nonzero
return code in general register 15.

User Response: Either delete
unnecessary members from the library
and retry, or start another library.

107E

CP /CMS command command not
allowed
Explanation: The named CP or CMS
command is not allowed under the eMS
batch facility. If it is a CP command,
the device type is also displayed. If it is
a CP LINK command, more than 26
LINK commands have been issued
without compensating DETACH
commands or a possible error has
occurred in the LINK command itself.
System Action: CMS eontinues with
the next command in the user job.

DMS
User Response: Do not resubmit this
command with any batch job. If this
was a LINK command reject, check to
be sure the LINK command is correct or
not more than 26 LINK commands have
been issued without compensating
DETACH commands. Reissue the LINK
command after detaching another disk.
A PASSWORD is always required, even
if the PASSWORD is 'ALL' The
PASSWORD must be coded' ALL' when
the disk being linked does not have an
access mode PASSWORD.

Routing: This message is displayed at
the batch facility console during user
job execution. It appears on the spooled
console output sheet.

108S

Explanation: No more than 63
MACLIB, TXTLIB, DOSLIB, or
LOADLIB library names may be
specified with a GLOBAL command.
System Action: RC = 88.
Execution of the command is
terminated, and any previous library list
of the specified type is cleared.

Routing: This message is displayed at
the batch facility console during user
job execution. It will appear on the
spooled console ou tpu t sheet.

User Response: Combine some
libraries to reduce the number of
libraries required for this terminal
seSSIOn.

Disk mode( vdev) is full

107S

Explanation: There is not enough
space on the specified disk to write the
file.

More than nn libraries specified

109E

System Action: RC = 100.
Execution of the command is
terminated. Some records of the output
file may have been written out.

{CPUIPrinterIPunch} limit
exceeded
Explanation: A user job exceeded the
named limit during execution. The limit
was determined either by the user job
through a ISET control card or by
default to the installation settings.

User Response: Erase some files from
the disk and reissue the command.

System Action: The user job is flushed
and the next batch job is started.
/SET card format invalid

lOSE

User Response: If the results are
unexpected, debug the job before
resubmitting it to batch.

Explanation: The batch facility
detected invalid information on user's
ISET card. Possible errors include:
•
•
•
•

No blank delimiters between en tries
Invalid keywords
Noninteger values for settings
Values for settings greater than
installation limits.

System Action: The user job is flushed
and the next batch job is started.
User Response: Correct the jSET card
and resubmit the job to the Batch
Facility.

109S

{Virtual storage capacity
exceededlStorage
exceededlInsufficient free storage
available}
Explanation: There is no more space
available in your virtual machine to
successfully complete execution of the
command. Subsequent execution of
certain CI'vIS commands may cause the
same problem.

Conversational Monitor System (eMS) Messages

277

DMS
For DMSACC, insufficient free storage
remains to access the specified disk.
For DMSAMS, Access Method Services
was unable to obtain free storage for the
terminal buffer to read the tape
ddnames.
For DMSBWR, a write buffer operation
attempted to write beyond the limits of
the virtual machine's storage.
For DMSLBD, not enough storage is
available to build a LABSECT or
VOLSECT for LABELDEF information.
For DMSFCH, either the phase being
fetched would exceed FREELOWE, or in
the case of fetching a $$B transient
phase, the transient routine would
exceed the end of the transient area.
For DMSGLB, not enough storage is
available to contain the list of specified
libraries and their associated directory
pointers.
For DMSHLP, not enough storage was
available to either load the DMSHLD
communication module or acquire buffer
space to format the HELP text file.
For DMSLBM, not enough virtual
storage was available to contain the
MA CLIB dictionary.
For DMSLIO, the loading of text files
has caused either the transient area or
user area limit to be exceeded. Text fIle
sizes are determined by the length fields
of ESD statements. An incorrect value
in the length field of an ESD statement
may cause this condition.
For DMSPIO, not enough virtual
storage is available to process the
FORM = parameter of the PRINTL
macro request.
For DMSSOP, the storage to be used for
saving the original DCB is not
available.

278

VM/SP System Messages and Codes

For DMSPRE, either the initial request
for a large block of storage failed, or
storage was exhausted during
suballocation of the block while
processing normally.
For DMSTPE, a buffer the size of the
LRECL of the file could not be obtained.
This happened while trying to load a
sparse file onto disk from tape.
For DMSQRF, DMSQRG, DMSQRH,
DMSQRS, DMSQRT, DMSQRU,
DMSQRV, DMSQRW, DMSWRX, and
DMSQRY, the stack and/or FIFO or
LIFO option was chosen, but there was
not enough storage to stack the result.
For DMSMOD, either storage could not
be obtained for a buffer to read a record,
or not enough virtual storage was
available to contain the requested
module.
For DMSGLO, GLOBALV was unable to
get a work area. GLOBALV
initialization functions could not
proceed.
For DMSSFD, DMSFREE failed because
no free storage was available for the
staging area or the label buffer.

System Action: DMSBWR passes a
return code of 22 to the program that
called it, which then passes a return
code of 104. DMSSMN is terminated
abnormally with abend code X'804' or
X'80A'. DMSVIP abends with CMS
abend code X'177'. All other modules
that issue this message pass a return
code of 104; execution of the command
is terminated, and the system status
remains the same.
For DMSACC, the disk is not accessed.
Any disk already accessed at the
specified point in the search order is
released, but not detached.
For DMSLBD, return code 24 is passed.
Execution of the command is
terminated. The system status remains
the same.

(

DMS
For DMSEXI, not enough storage was
available to successfully complete
execution of the EXECLOAD command.
Execution of the command is
terminated.

longer need; then reissue the original
command. To increase the size of your
virtual machine, use the DEFINE
command; then re-IPL CMS and reissue
the original command.

For DMSGLB, execution of the
command is terminated, and any
previous library list of the specified type
is cleared.

Alternatively, you can do the following:

For DMSOVR, SVCTRACE is turned off
if it was on.
For DMSLBM, if additions were being
made to the MACLIB (GEN, ADD, or
REP functions), it contains all
successful additions made before storage
was exceeded.
For DMSPIO, the print request is ended
with a return code of 104.
For DMSWVL, the command is
terminated with a return code of 104.
For DMSSOP, opening of the file is
terminated.
For DlVISTPE, the failure occurred
before any records were written out to
disk. Therefore, no file is created.
TAPE processing terminates with a
return code of 104. All files previously
loaded are retained.
'
For DMSQRF, DMSQRG, DMS(~RH,
DMSQRS, DMSQRT, Dl\.fSQRU,
DlVISQRV. DMSQRX, and DMSQRY,
RC:.-= 109. The execution of the
command is terminated.
For DMSMOD, the command is
terminated with a return code of 104.
For DMSSF'D, the command is
terminated with a return code of 41.

User Response: You mUHt either free
some virtual Htorage or increaHv the Hiz(:
of your virtual machine. To free ::;ome
virtual storage, issue the l~ELEASE
command for any minidisks that you no

For DMSARN, DMSSMN, and
DMSTPD, reduce the size of the
program and retry.
For DMSDLB and DMSLBD, clear old
definitions that are no longer needed,
and retry.
For DMSEXI, drop any storage resident
EXECs that are not needed, and retry
the EXECLOAD command.
For DMSLBM, issue the MACLIB MAP
command to determine the contents of
MACLIB. Define additional storage with
a CP DEFINE command. Continue
processing with the remaining
additions.
For DMSLIO, redefine loading locations
(origin) or redefine the virtual storage
size using the CP command DEFINE.
Reissue the entire LOAD/INCLUDE
sequence.
For DMSPIO, issue the CP DEFINE
STORAGE command to increase the size
of the virtual machine and IPL eMS, or
issue the CMS RELEASE command for
any disks no longer needed and restart
your program.
If you ran out of storage while trying to
acquire a large GETMAIN area, and
your virtual machine size is above the
start of the C.l\1S nucleus, you should
IPL a ClVIS system generated at a higher
·. .,irtual address than the one you are
using.
For DMSSFD. if you increase the size of
virtual machine, make sure that
your virtual machine size is below the
address of the DeSS where the FSTs are
going to be ~aved.

~Tour

Conven.;ationul Monitol' System (eMS) Messages

279

DMS
109T

Virtual storage capacity exceeded

character from 0 to 9 or A to F; T API is
the default). The tape may not be in the
same position as before the command
was entered.

Explanation: There is insufficient
virtual storage available for file
management control blocks.

User Response: If the tape is attached,
make sure that it is the correct tape;
rewind the tape via the TAPE REW
command, position the tape, and retry.
If the error persists, check the format of
the tape for parity errors, missing tape
marks, etc. For the TAPEMAC
command, if the problem persists, use
the OS utility IEHMOVE to create the
PDS again on another tape.

System Action: The virtual machine is
placed in a disabled wait state and the
disk is not updated.
User Response: Issue the CP command
DEFINE to increase the size of the
virtual machine, IPL CMS again and
reenter the command.
If you ran out of storage while trying to

acquire a large GETMAIN area, and
your virtual machine size is above the
start of the CMS nucleus, you should
IPL a CMS system generated at a higher
virtual address than the one you are
using.

110E

111E

Explanation: Errors occurred when
trying to load (using the Loader) CMS
text decks into the discontiguous saved
segment.

CORRECT FORM IS: DOSGEN
LOCATION (SEGNAME)

System Action: RC = 36.
Execu tion of the command is
terminated. The system status remains
the same.

Explanation: An invalid form of the
DOSGEN command was specified.

User Response: Print or display the
file on the A-disk with filename and
filetype 'LOAD MAP', which contains
diagnostic messages. In some cases,
Loader messages may precede this
message. If this occurs, refer to the
Loader message and follow the user
action given.

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Correct and reissue
the command. 'segname' is optional; if
you do not specify it, it defaults to
CMSDOS for DOSGEN.
IllS
110S

Error reading TAPn[(vdev))
Explanation: A permanent 1/0 error
occurred while reading the specified
tape, or the tape is not attached.

DOSGEN failed due to load errors

Error writing TAPn(lldev)
Explanation: A permanent 1/0 error
occurred when writing the specified
tape.
System Action: RC = 100.
If the DEN, TRTCH, 7TRACK,

System Action: RC = 100.
Execution of the command is
terminated. For the TAPE command, if
the DEN, TRTCH, 7TRACK, 9TRACK.
or l8TRACK options were specified, the
modeset byte has been set for the
specified device (TAPn, where n is a

280

VM/SP System MessageH and Codes

9TRACK. or 18TRACK options were
specified, the modeset byte has been set
for the specified device (T APn, where: n
is a character from 0 to 9 or A to F;
TAPl is the default), The tape may not
be in the same position as before the
command was entered.

(

DMS
User Response: Reissue the command.
If the error persists, contact your system
support personnel.

112S

If the specified device is a printer,
punch, or reader, use the CP command
DEFINE to attach it to your virtual
machine.

mode(vdev) device error

Explana tion: An error was
encountered in trying to access the disk,
either because it is an unsupported
device, or because an I/O error occurred
while reading in the master file
directory from the device.

If the specified device is a tape drive,
ask the system operator to attach or
mount the tape and ready the device.

Then reissue the command.

114E

program not loaded; eMS/DOS

environment [not] active
System Action: RC = 100.
Execution of the command is
terminated. The system status remains
the same unless another disk was
replaced by this access, as indicated by
message DMSACC724I.

Explanation: Either the CMS/DOS
environment is active and you are
trying to load a program that uses OS
macros, or the CMS/DOS environment
is not active and you are trying to load
a program that uses DOS macros.
Neither of these situations is allowed.

User Response: If this is the first time
that you are using this CMS disk, use
the FORMAT command to format it.
Reissue the command. If the problem
persists, contact your system support
personnel.

113S

{mode IDevice IDisk IPrinter IPunch I
ReaderlTAPnlTapeinlTapout}
[(vdev)] not attached

Explanation: The specified device is
not attached to the virtual machine. If
the message is issued for a tape, it also
may mean that the tape has not been
mounted or the device is not ready.
System Action: RC = 100.
Execution of the command is
terminated. The system status remains
the same unless another disk was
replaced by this access, as indicated by
message DMSACC724I.
User Response: If the specified device
is a disk, issue the CP command LINK
to attach the disk to the virtual
machine, or ask the system operator to
attach the disk to your virtual machine.

System Action: RC = 40 or 0005.
The command is not executed.
User Response: Use the CMS
command SET to set DOS on or off, and
reissue the command.

114S

Device vdev is an unsupported
device type, or requested
BLKSIZE is not supported for the
device
Explanation: VM/SP does not support
either the attached device or the
requested block size.
System Action: RC = 88.
Execution of the command is
terminated. The system status remains
the same.
User Response: Attach a device that is
supported by VM/SP, or issue the
command with a valid block size for the
device.

ConversationaJ Monitor System (eMS) Messages

281

DMS
115E

Phase load point less than vstor

117S

Explanation: During a System Product
Editor session, an error occured when
XEDIT was writing to a virtual screen
or when eMS was writing to a display
terminal.

Explanation: The phase load point is
less than the beginning of the user area.
8ystem Action: RC = 40.
Execution of the command is
terminated. The system remains in the
same status as before the routine was
entered.

During an EDIT session, an I/O error
occurred when a DIAGNOSE command
was issued to write to a display
terminal.

User Response: Ensure that the phase
load point is greater than or equal to
the beginning of the user area by
altering linkage-editor control
statements.

1158

System Action: RC = 100.
For a System Product Editor session,
the terminal is set to typewriter mode,
and the editing session continues.
For an EDIT session, the session is
terminated. The virtual machine is
placed in CMS mode.

{Conversionl{719118}-trackl{800116001
6250} BPIITranslationlDual
density} feature not supported on
device vdev

User Response: For the System
Product Editor, issue the SHOW
WINDOW command for whatever
window XEDIT is using, and then issue
the subcommand SET TERMINAL
DISPLA Y to return the editor to display
mode. If the problem persists, contact
your support personnel.

Explanation: The user has specified a
tape mode setting that requires a
feature not supported by the attached
real device.
System Action: RC = 88.
The system remains unchanged; the tape
device has not been repositioned.
User Response: Reissue the command
using mode options (nTRACK, DEN,
TRTCH) appropriate for the attached
device; or attach a device with the
appropriate features.

1168

Loader table overflow
Explanation: There are t.oo many
entry-point or control-section names in
the loader table built during loading.
System Action: RC = 104.
Loading is terminated.
User Response: IPL eMS again,
redefine the number of loader tables
with the SET command, and issue the
LOAD/INCLUDE sequence (for
DMSLIO) or the LOADMOD command
(for DMSMOD).

282

VM/SP System Messages and Codes

Error writing to display terminal

For the EDIT session, retry the session.
If the problem persists, contact your
system support personnel.

1188

Error punching file
Explanation: An input/output error
occurred while punching the file.
System Action: RC = 100.
Some of the file may have been
punched. The file being read is closed
and an attempt is made to close the
punch before terminating the command.
User Response: Reissue the command.
If the problem persists, contact your
system support personnel.

(

DMS
1198

Unsupported form of name macro
Explanation: An unsupported or
invalid form of the macro or sve listed
in the message has been executed by a
user program.
System Action: CMS is terminated
abnormally with an abend code of
X'400'.
User Response: Check your program
for an invalid or unsupported form of
the macro listed in the message.

1208

{InputIOutput} error [code] nn on

ddname
Explanation: The indicated error code
was returned from an OS READ,
WRITE, GET, or PUT macro.
The error code in the message is
supplied only if the error was an INPUT
or OUTPUT error, not if it was a FIND,
POINT, BSP, or some other type of
operation error. Error codes differ for
the various types of devices. Error code
meanings are listed below.
For DMSSCT, CMS issues this message
if an I/O error is encountered by an OS
CLOSE macro or if an I/O error is
encountered by an OS CHECK, GET, or
PUT macro and a SYNADAF routine is
not specified by the user.

For DMSSVT, the program continues to
execute.
For DMSFCH, RC = 100 and execution
of the command is terminated.
User Response: Use the error code to
determine the correct message and
possible cause of the error.
For BPAM access, check the integrity
of the library (i.e. LOADLIB) directory.
If the file '$PDSTEMP LOADLIB' exists
on your disk, do not erase it! For
example, if you issue a LOAD LIB COpy
or COMPRESS command into an
existing loadlib and it terminates with a
DMS120S message, examine your disk to
determine if the $PDSTEMP LOADLIB
exists. It will contain the updated
directory for the loadlib. Re-issue
another LOADLIB COPY or
COMPRESS command where the
modified output loadlib is the SYSUTI
data set and omit the SYSUT2data set
from the command input. If the
command is successful, the loadlib's
directory will be restored.

ALL DEVICES
Code Meaning
254

BSAM, BPAM, or BPAM-CHECK
was called with an un posted ECB
specified.

DISK INPUT
For DMSSVT, this message is built by
the simulation routine for the
SYNADAF macro; it is issued by a user
SYNAD routine. If the message is
printed by an OS program product
SYNAD routine, the SYNAD routine
usually places a message number of its
own in front of the message number
listed above and append some
information of its own to the end of the
message.

Code Meaning
1
2

System Action: For DMSSCT and
DMSSBS, CMS is terminated
abnormally with an abend code of 1.
5

The file was not found.
The virtual storage area was not
within the limits of the virtual
machine.
A permanent disk error occurred.
This may occur if you link to and
access another user's disk, and try
to read a file that was refiled by its
owner after you issued the
ACCESS command. Reissue the
ACCESS command and try to read
the file again.
The number of items was zero.

Conversational MonitoI' System (eMS) Messages

283

DMS
7
8

9
11
"

25
26

80
82
255

The fixed/variable flag in FST
entry was not F or V.
The given storage area was smaller
than the actual size of the item
read. (Recoverable error; the
number of bytes corresponding to
the size of the buffer have been
read.)
The file is open for writing; it must
be closed before it can be read.
The number of items is greater
than 1, for a variable-length file.
An unexpected end of file occurred
(the item number specified exceeds
the number of items in the file).
A variable-length file has an
invalid displacement in the active
file table.
Insufficient virtual storage is
available.
Requested item number is
negative, or item number plus
number of items exceeds file
system capacity.
An I/O error occurred while
reading an OS data set or DOS file.
The OS data set or DOS file is not
BPAM, BSAM, or QSAM.
BDAM or BSAM (CREATE)either:
A specification error
occurred, or
2.
An I/O error occurred while
reading or writing KEYS, or
3.
The XTENT option was not
specified in the FILEDEF
command, or the XTENT was
too small.
BP AM - An I/O error occurred
while reading in the directory
of a MACLIB or LOADLIB
file.

1
2
4
5
6
7

8
9

10
11
12
13
14

15
16

18
19
20
21
22

Note: All errors except 8 (above) cause
execution of the command to terminate.
Error 8 is valid if reading the first
portion of a large record in to a small
buffer.

DISK OUTPUT

Code Meaning

284

VM/SP System Messages and Codes

The filename or filetype was not
specified, or is invalid.
The virtual storage address is zero.
The first character mode was
invalid.
The second character mode was
invalid.
The number of records in the file is
too large; it cannot exceed 65,533.
An attempt was made to skip over
an unwritten variable-length item
or an update was attempted to a
file on a read only extension disk.
The number of bytes was not
specified.
The file was already active for
reading.
The maximum number of CMS files
(3500) was reached.
The fixed/variable flag was not F
or V.
The mode is S (system) or other
read-only disk.
The disk is full.
The number of bytes to be written
is not integrally divisible by the
number of records to be written.
The length of this item is not the
same as the previous item.
The fixed/variable flag is not the
same as that of the previous
record.
A variable-length item is greater
than 65K bytes.
The number of items is greater
than 1 for variable-length file.
The maximum number of data
blocks per file (16060) was reached.
An invalid character was detected
in the filename.
An invalid character was detected
in the filetype.
V irtual storage capacity has been
exceeded.
Insufficient virtual storage is
available.
Requested item number is
negative, or item number plus
number of items exceeds file
system capacity.
An attempt was made to update a
variable length item with one of a
different length.

DMS
255

BDAM or BSAM (CREATE)either:

Code Meaning
1
2

The buffer size is too large.
Channel 12 was sensed (virtual
3211 only).
3
Channel 9 was sensed (virtual 3211
only).
4
Intervention required on printer.
5
An unknown error occurred.
100 The device is not attached, or
intervention is required.

A specification error
occurred, or
2.
An I/O error occurred while
reading or writing KEYS, or
3.
The XTENT option was not
specified in the FILEDEF
command, or the XTENT was
too small.
BP AM - An I/O error occurred
while writing out the
directory of a MACLIB or
LOADLIB file.
1.

CARD READER
Code Meaning

CONSOLE INPUT

TAPE INPUT AND OUTPUT

The file was not read.
An unknown error occurred.
The device is not operational.
4
The count was not equal to the
5
requested count.
The given storage area was smaller
8
than the actual size of the item
read. (Recoverable error; the
number of bytes corresponding to
the size of the buffer have been
read.)
12
End of file was reached.
100 The device is not attached.

Code Meaning

CARD PUNCH

Code Meaning
2
12

Invalid code - no read was issued.
A null line or end-of-file condition
was encountered.

CONSOLE OUTPUT
None.

3
4

5
6

8
12

An invalid function or option list
was encountered (for example, a
FILEDEF specified a DENsity
incompatible with the mounted
tape device or, in alternate tape
drive processing, the alternate
drive is not compatible with the
primary drive--the device
associated with the specified
logical unit is not a tape drive).
A permanent I/O error occurred.
An invalid device identification
was specified.
The tape was not attached.
The tape is file protected.
A serious tape error occurred.
Incorrect length error.
An end-of-file or end-of-tape
condition was encountered.

PRINTER

Code Meaning
2

An unrecoverable unit check
occurred.
3
An unknown error occurred.
4
The device is not operational.
36
The device is not a valid input
device.
100 The device is not attached.

1218

{Unsupported [function function
of] IInvalid form of} 8VC suc (HEX
xx) called from ustor
Explanation: The caller issued an
SVC, specifying a number that was not
recognized by the CMS or CMS/DOS
SVC handler.
The eMS SVC handler recognizes the
following SVC numbers:

Conversational Monitor System (eMS) Messages

285

DMS
•

•

SVC 202 (X'CA') and SVC 208
(X'Ca') are always recognized by the
CMS SVC handler, since these SVCs
are used to specify CMS system
functions and commands.

System Action: Processing of the
VMFNLS command stops. No TXT files
are generated.

Certain SVC numbers are supported
by the OS macro simulation
routines. There are two types of
these simulation routines. The SVC
numbers supported by the
storage-resident CMS nucleus are
always recognized by the SVC
handler. Those supported by the
disk-resident transient library are
recognized by the SVC handler only
if the file DMSSVT module can be
found.
Certain SVC numbers are supported
by the DOS macro simulation
routines. The SVC numbers
supported by the shared segment
resident routine are always
recognized by the SVC handler.

User Response: To stop execution of
the program, type HX. You can remove
the specified SVC call from the caller~s
program, or use the CMS SVC handler
function (HNDSVC) to provide your
own routine to handle the specified
SVC.

VM/SP System Messages and Code:::;

Return code rc from routine
Explanation: The routine that
VMFNLS called (either GENMSG,
CONVERT COMMANDS, or VMFASM)
could not properly execute. This
routine issues a non-zero return code
(rc).

A program may specify an SVC
handling routine by means of the
HNDSVC function. Until cleared,
these SVC numbers are recognized
by the SVC handler.

System Action: After the error
message is displayed, no further action
is taken. Control returns to the routine
that made the SVC. For DMSDOS, RC
= 100, and execution of the command
terminates.

286

122E

User Response: Error messages from
routine (GENMSG, CONVERT
COMMANDS, or VMFASM) should
have appeared before this message.
This book contains explanations for
those messages.
Refer to the VM/ SP CMS Command
Reference for information about
GENMSG and CONVERT
COMMANDS; refer to the VM/SP
Installation Guide for information about
VMFASM.

1228

Error in call to routine from vstor,
error code nnn (HEX xxx xxx )
Explanation: A CMS SVC (202 or 203)
instruction was executed, and no
provision was made for an error return
from the routine processing the SVC.
Nonetheless, an error occurred. "nnn"
is the return code, in decimal, issued by
the routine given in the message;
"xxxxxx" is the same return code, in
hexadecimal.
System Action: The system is
terminated abnormally with abend code
X'OF3'.
User Response: If you enter DEBUG
and type GO. control returns to the
point to which a normal return would
have been made. Register 15 contains
the error code.:

(

DMS
123S

Error nn {printinglpunching} file
fn ft fm

using 2K blksize, it is probable that the
error occurred due to a defective track
on the disk. (VM does not provide
alternate track recovery 3340/3344 disks
when overflow records are
involved--CMS uses overflow records on
3340/3344 for 2K blksize.)

Explanation: An I/O error was
encountered while attempting to print
or punch a record. Refer to message
DMSxxx120s for an explanation of error
codes.
System Action: RC = 100.
The output device is closed and
execution of the command is terminated.

1268

Explanation: An unrecoverable I/O
error occurred on the specified disk.

User Response: Use the error code to
determine possible cause of error.
Reissue the command, and if the error
persists, contact your system support
personnel.

124S

System Action: RC:= 100.
Execution of the command is
terminated. The system status remains
the same.

Error reading card file
Explanation: A permanent
input/output error occurred when
reading a specified file.

User Response: Contact your system
support personnel.

127S

System Action: RC = 100.
Execution of the command is
terminated. The reader is closed with
the HOLD option to attempt to preserve
the file.

Unsupported device for file
Explanation: The command does not
support the device specified for the
given ddname.
System Action: RC = 100.
Execution of the command is
terminated. The system status remains
the same.

User Response: Reissue the command.
If the error persists, contact your
installation support personnel.

125S

Error {readinglwriting} label on
disk mode(vdev)

User Response: Reissue the FILEDEF
command. specifying the correct device
type. and retry the command. If the
error persists, call your system support
personnel.

Permanent unit check on disk
mode(vdev)
Explanation: An unrecoverable I/O
error occurred on the specified disk.
128S
System Action: Re 100.
Execution of the command is
terminated. Some cylinders may have
been formatted. If so, the number is
indicated by message DMSFOR7321.
=:=

User Response: Contact your syst('m
support personnel.
Note: If the message results while
doing a Cl\1S format of a :1;340/:3344 disk

I/O error on input after reading
nnn records; input error ('ode on
ddname
Explanation: The SYNAD exit was
taken in n'sponse to an OPEN, GET, or
CLOSE macro on the DCB for the
specified ddname. The meaning of the
errol' code can be found in the
explanation of message D.MSmmm120S
in this manual.

Cc.>n\'prsational :Vlonito}" S~'stem (eMS) MeHsages

287

DMS
User Response: Specify a blocksize of
nine or greater, and retry.

System Action: RC = 100.
Execution of the command is
terminated. The system status remains
the same.
131S
User Response: Correct the condition
causing the I/O error, and reissue the
command.

129S

Explanation: An un correctable I/O
error occurred while writing the
nucleus.
System Action: The system continues
as if the user had responded "no" to
DMSINI607R.

I/O error on output writing record
number nnnn; output error code
on ddname

User Response: Make sure that the
nucleus cylinder number is not larger
than the size of the disk. If it is,
perform an IPL and specify the correct
cylinder number. If it is not, call your
system support personnel.

Explanation: The SYNAD exit was
taken in response to an OPEN, PUT, or
CLOSE macro on the DCB for the
specified ddname. The meaning of the
error code can be found in the
explanation of message DMSxxx120S in
this manual.
System Action: RC == 100.
Execu tion of the command is
terminated. The system status remains
the same.

132S

System Action: RC = 88.
Execution of the command is
terminated. The system status remains
the same.

Note: A block of a variable length
(V-format) file begins with a four byte
field giving the size of the block.
Furthermore, each logical record within
the block begins with a four byte field
specifying the size of that logical record.
For that reason, a V-format file cannot
have a blocksize less than nine.
System Action: RC = 88.
Execution of the command is
terminated. The system status remains
the same.

288

User Response: Split the file, or use
the CP command DEFINE to increase
the size of the virtual machine, and
reissue the command.

Blocksize on V -format file ddname
is less than 9
Explanation: The FILEDEF for the
ddname specifies a record format
(RECFM) of V, but the specified
blocksize (BLOCK) is less than nine.

VMjSP System Messages and Codes

File fn ft fm too large
Explanation: The specified file is too
large for the user's virtual machine.

User Response: Correct the condition
causing the IiO error, and reissue the
command.

130S

IPL device write I/O error

133S

Invalid GETMAIN or FREEMAIN
specification
Explanation: Either the user passed
invalid parameters or the GETMAIN or
FREEMAIN chain has been destroyed.
System Action: The system is
terminated abnormally with abend code
X'704', X'705', X'804', X'80A', X'905',
X'90A', X'A05', or X'AOA'.
User Response: Check for possible
GETMAIN or FREEMAIN specification
errors in the user program.

DMS
134S

Unsupported SVC 203 code nn
called from vstor

User Response: Veri(y whether
sufficient virtual storage is available to
run Access Method Services under
CMS/VSAM. If not, define a larger
virtual machine, IPL eMS again. and
reissue the command. If sufficient
storage was available, contact your
system support personnel.

Explanation: SVC 203 was executed,
and the halfword code following it was
not recognized by the system.
System Action: The system is
terminated abnormally with abend code
X'OF1'.
136T
User Response: If you enter DEBUG
and type GO, control returns to the
point following the SVC call.

135S

SVC call from vstor illegally
re-enters INTSVC; re-IPL CMS
Explanation: The CMS nucleus has
failed. An SVC instruction was
executed unexpectedly by the CMS
nucleus before interpretation of the
preceding SVC call had been completed.

Maximum SVC depth nnnn has
been exceeded with call at vstor
Explanation: SVC recursion occurs
when one SVC handling routine
executes an SVC instruction which
invokes another SVC handling routine
which, in turn, executes an SVC
instruction. This can happen, for
example, when EXEC files make nested
calls to other EXEC files.

System Action: The system is
terminated by loading a disabled wait
state PSW.
User Response: Issue the CP DUMP
command to get a dump of virtual
storage, save the output, and call IBM
for software support. Then IPL CMS
again.

The CMS system does not allow the
nesting level of SVCs to exceed 'nnnn'.
137S
System Action: The system is
terminated abnormally with abend code
X'OF2'.
User Response: Type in the next
command; this will cause ahend
recovery to take place.

136S

Unable to load IDCAMS
Explanation: The command has not
been executed because Access I\1ethod
Services could not successfully load the
DOS/VS IDCAMS Access .Method
Services program.
System Action: RC = 104.
Execution of the command is
terminated. The system status remains
the same.

Error nn on STATE for fn ft fm
Explanation: An error occurred while
attempting to determine if a 'fn ff exists
that must be erased before continuing to
load the tape.

nn indicates the nature of the error; it
may be one of the following:
Code Meaning
20
An invalid character appeared
in the fileid.
36 The disk is not accessed.
System Action: RC = 100.
The t.ape is positioned within the data
file.
User Response: If you can determine
the problem from the "Explanation" and
remedy the condition. reissue the
command. Otherwise. reissue the

Conversational Monitor System (eMS) Messages

289

DMS
command and if the problem persists,
contact your system support personnel.

System Action: The system is
terminated abnormally with abend code
X'OF4'.

137T

Call to routine from vstor destroyed
system save area; re-IPL CMS
Explanation: A critical system control
block was found to contain invalid
information upon return from a function
or command.

User Response: If you enter DEBUG
and type go, execution continues and
the DMSKEY macro is ignored.

139S

Explanation: Nine CMS MACLIBs
have already beeh created and there is
still more data on the tape.

System Action: The system is
terminated by loading a disabled wait
state PSW.

System Action: RC = 104.
Execution of the command is
terminated; the tape is positioned within
the data file.

User Response: IPL CMS again.

138S

Error nn erasing fn ft before
loading tape

User Response: If possible, increase
the ITEMCT value in order to create
larger cMs files. If this is not possible,
it may be necessary to use the T APPDS
command to load each member as a
different file on the disk and then create
the MACLIBs from the individual files
using the MACLIB command.

Explanation: After determining that
there was a file named 'fn ft' on the
A-disk, an attempt was made to erase it
before continuing the PDS load from
tape. However, the erase failed for the
specified reason.
Code Meaning
24 The disk is read-only, or the
option, parameter, mode, or fileid
is invalid. Erase is not allowed.
28 The file was not found.
36 The disk is not accessed.

Tape file exceeds 9 CMS MACLIB

139T

DMSKEY RESET from vstor
underflows key stack

System Action: RC = 100.
Execution of the command is
terminated. The t.ape is positioned
within the data file.

Explanation: The DMSKEY key stack
was empty and a program routine tried
to delete one more key from it. For a
complete description of the DMSKEY
key stack, see the description of the
DMSKEY macro in the VM/ SP CMS for
System Programming.

User Response: Access the A-disk in
write mode and reissue the command.

System Action: The system is
terminated ahnormally with abend code
X'OF5'.

138T

DMSKEY call from vstor overflows
key stack, with maximum depth n
Explanation: The DMSKEY key stack
overflowed. For a complete description
of the DMSKEY key stack, see the
description of the DMSKEY macro in
the VM/ SP CMS for System
Programming.

290

VM/SP System Messages and Codes

User Response: If you enter DEBUG
and type "go," execution continues and
the DMSKEY macro is ignored.

DMS
140S

{function function(s)!SEOV/FEOV
macro} not supported [in
eMS/DOS]
Explanation: CMS/DOS does not
support the specified macros or
functions.
System Action: RC = 100.
Execution of the command is
terminated.
User Response: Eliminate the
unsupported macros or functions from
the user program and reissue the
command.

140T

routine routine called from vstor
did DMSKEY with no reset
Explanation: When control returned
from a command or function, the
DMSKEY key stack for that command
or function was not empty. For a
complete description of the DMSKEY
key stack, refer to the description of the
DMSKEY macro in the VM/ SP eMS for
System Programming.
System Action: The system is
terminated abnormally with abend code
X'OF6'.
User Response: If you enter DEBUG
and type "go," control returns from the
function or command as if the key stack
were empty.

141S

DOSGEN failed due to SA VESYS
errors
Explanation: Errors occurred while
trying to issue the CP SA VESYS
command to save the discontiguous
shared segment.
System Action: RC = 100.
Execution of the command is
terminated. The system status remains
the same.

User Response: A CP error message
was issued before this message. Locate
the CP error message and follow the
user action given.

141T

{exception exception! Program
interrupt Xxx} occurred at vstor in
routine routine
Explanation: The specified hardware
exception occurred at the specified
location.
System Action: The system is
terminated abnormally with an abend
code. For program interrupt codes 1
through F, this abend code is computed
by taking the interrupt code and adding
it to X'OCO'. Program interrupt X'13'
produces abend code X'OD3'; Program
interrupt X'19' produces abend code
X'09F'; All other program interrupts
that occur in CMS produce abend code
X'OEO'.
"exception EXCEPTION" is issued for
program interrupt codes 1 through F;
"PROGRAM INTERRUPT X'xx'" is
issued for program interrupt codes that
are higher than F.
The following list shows program
interrupt codes 1 through F along with
their meanings:
n Type
1 Operation
2 Privileged operation
3 Execute
4 Protection
5 Addressing
6 Specification
7 Data
8 Fixed-point overflow
9 Fixed-point divide
A Decimal overflow
B Decimal divide
C Exponent overflow
D Exponent underflow
E Significance
F Floating-point divide

Conversational Monitor S~Tstem (eMS) Messages

291

DMS
To find the meaning of program
interrupt codes greater than F, refer to
the IBM System/370 Principles of
Operation, GA22-7000.

The following list shows program
interrupt codes 1 through F along with
their meanings:
n Type
1. Operation
2 Privileged operation
3 Execute
4 Protection
5 Addressing
6 Specification
7 Data
8 Fixed-point overflow
9 Fixed-point divide
A Decimal overflow
B Decimal divide
C Exponent overflow
D Exponent underflow
E Significance
F Floating-point divide

User Response: Enter DEBUG mode to
examine the PSW and registers at the
time of the exception.

142S

Saved system name sysname
invalid
Explanation: The name specified with
the SET command was not the same as
one of the labels in the SYSNAMES
table; that is, it was not CMSDOS,
CMSAMS, or CMSVSAM.
System Action: RC = 24.
Execution of the command is
terminated.

To find the meaning of program
interrupt codes greater than F, refer to
the IBM System/370 Principles of
Operation, GA22-7000.

User Response: Reissue the command,
specifying a valid name.

142T

User Response: Enter DEBUG mode to
examine the PSW and registers at the
time of the exception.

{exception exception IProgram
interrupt Xxx} occurred at vstor in
routine routine during SPIE exit
routine

143S
Explanation: The specified hardware
exception occurred during a SPIE exit
routine.
System Action: The system is
terminated abnormally with an abend
code. For program interrupt codes 1
through F, this abend code is computed
by taking the interrupt code and adding
it to X'OCO'. Program interrupt X'13'
produces abend code X'OD3'; Program
interrupt X'19' produces abend code
X'09F'; All other program interrupts
that occur in CMS produce abend code
X'OEO'.
"exception EXCEPTION" is issued for
program interrupt codes 1 through F;
"PROGRAM INTERRUPT X'xx'" is
issued for program interrupt codes that
are higher than F.

292

VM/SP System Messages and Codes

U nahle to load module
Explanation: An EDMAIN load
module is not available.
System Action: RC = 40.
Execution of the command is
terminated. The system status remains
the same.
User Response: Access a disk with an
EDMAIN MODULE.

143T

{exception exception IProgram
interrupt Xxx} occurred at vstor in
system routine routine; re-IPL
CMS

Explanation: The specified hardware
exception occurred in a eMS system
routine.

(

DMS
System Action: The CMS system halts
by loading a disabled wait state PSW.
"exception EXCEPTION" is issued for
program interrupt codes 1 through F;
"PROGRAM INTERRUPT X'xx'" is
issued for program interrupt codes that
are higher than F.

144S

Explanation: The fileid specified in the
EDIT command line is that of a file
currently in use, or in active status. The
read pointer for the file may be at any
record in the file, which would cause
that record to be read into storage by
the Editor as the first record in the file.
A subsequent FILE or SAVE command
would result in loss of records prior to
the first record read into storage. This
problem could exist if an EXEC is being
executed which includes an EDIT
command specifying the fileid of the
EXEC.

The following list shows program
interrupt codes 1 through F along with
their meanings:
n Type
1 Operation
2 Privileged operation
3 Execute
4 Protection
5 Addressing
6 Specification
7 Data
8 Fixed-point overflow
9 Fixed-point divide
A Decimal overflow
B Decimal divide
C Exponent overflow
D Exponent underflow
E Significance
F Floating-point divide

System Action: Execution of the
command is terminated. The system
status remains the same.
User Response: Ensure that the file is
not active when the EDIT command is
issued. In the EXEC example, change
the EXEC and issue the EDIT command
separately.

144T
To find the meaning of program
interrupt codes greater than F, refer to
the IBM System/370 Principles of
Operation, GA22-7000.
User Response: You may continue
processing (with DEBUG) by using the
CP command STORE PSW to turn off
the wait state bit in the virtual PSW,
leaving the address field unmodified;
then type BEGIN.
Note, however, that the exception may
have occurred in a vital system
function, and so the system may no
longer function properly. You may even
lose your read/write disks. If this
happens, IPL CMS again.

Requested file is in active status

{exception exception IProgram
interrupt Xxx} occurred at vstor in
routine routine while UFDBUSY =
xx; re-IPL eMS
Explanation: A program exception
occurred in a routine that updates the
user file directory for a read/write disk.
The UFDBUSY flags are set. The
UFDBUSY flags are defined in the
FVSSECT of the VM/SP Data Areas
and Control Block Logic Volume 2
(eMS).
System Action: The CMS system halts
by loading a disabled wait state PSW.
"exception EXCEPTION" is issued for
program interrupt codes 1 through F;
"PROGRAM INTERRUPT X'xx'" is
issued for program interrupt code8 that
are higher than F.
The following list shows program
interrupt codes 1 through F along with
their meanings:

Conversational Monitor System (CMS) Messages

293

DMS
n
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F

Type
Operation
Privileged operation
Execute
Protection
Addressing
Specification
Data
Fixed-point overflow
Fixed-point divide
Decimal overflow
Decimal divide
Exponent overflow
Exponent underflow
Significance
Floating-point divide

To find the meaning of program
interrupt codes greater than F, refer to
the IBM System/370 Principles of
Operation, GA22-7000.
User Response: You can continue
processing by using the CP command
STORE PSW to turn off the wait state
bit in the virtual PSW, leaving the
address field unmodified: then type
BEGIN.
Note, however, that the exception may
have occurred in a vital system
function, and so the system may no
longer function properly. You may even
lose your read/write disks.

1458

Intervention required on
{printer Ipunch}

selected. This error occurs with the
CMS PRINT command because the
heading line is too long. For the
PRINTL macro~ the specified
duplication offset is invalid for the
given line length. or the line is too
long to be duplicated.
•

Data errors have occurred. For
example, the character arrangement
tahle (CAT) has not been loaded.

System Action: RC = 100.
If the punch or printer was not ready,
the system status remains the same. If
spooling space was exhausted, the file
has been punched or printed up to the
point where the space ran out, and the
system operator has been notified of the
condition.
If the extended FCB duplication feature
was invalid, then the file has been
printed up to the point that the invalid
duplication was encountered.

User Response: Ready the punch or
printer via the CP READY command.
If spooling space was exhausted, ask the
system operator when spooling space
will be available for punching or
printing the file again.
If the extended FCB duplication feature
was selected and the CMS PRINT
command was issued, then load an FeB
that does not have the duplication
feature on the printer.

Explanation: This message is issued if:
•

The punch or printer is not ready.

•

Spooling space is exhausted while a
file is being punched or printed.

•

FCB (3203/3211) does not mat.ch
carriage control

• ' The printer has an extended FeB
with the duplication feature

294

VM/SP System Messages and CodeR

If the PRINTL macro Was issued, then
adjust the line length and/or the
duplication offset. or disable the
duplication feature.
If the character arrangement table has
not been loaded. use the CMS SETPRT
CHARS command to load the proper
CAT into the virtual 3800.

DMS
1461

IDUMP for identifier mmjdd/yy
hh:mm:ss

149T

Explanation: This message is issued to
inform the operator that an IDUMP was
taken on the virtual printer. The
identifier is the jobname in bytes 24-31
of the Partition Communication Region
at the time of the IDUMP request.

Explanation: In attempting to recover
from a system abend, the abend recovery
routine discovered invalid data in some
critical system storage area.
System Action: The CMS system halts
by loading a disabled wait state PSW.

System Action: This message is for
information only. Processing continues.

User Response: If you wish to
continue abend recovery, use the CP
STORE command PSW to turn off the
wait state bit, leaving the address field
unmodified; then type BEGIN.
However, the system may be unable to
continue operating properly, and, in the
worst case, you may destroy your
read/write disks.

User Response: None.

147E

Message not in ascending
sequence
Explanation: The message id for the
previous message was higher than the
current message id, and the CP option
was specified.
lS0W
System Action: RC = 8.
User Response: Correct the line
numbers and retry.

148T

nnn (HEX xxx) doublewords of
system storage were not
recovered
Explanation: In attempting to recover
from a system abend, not all system
storage was recovered.

System abend xxx called from
vstor

System Action: Abend recovery
proceeds as if storage recovery had been
successful.

Explanation: The system detected a
condition that made it impossible to
continue execution of your program or
command.

User Response: You may continue
processing; your program should be
executed correctly. Note, hpwever, that
the amount of storage available to your
program is reduced by the amount
shown in the message.

System Action: The system clears any
stacked input lines and allows you to
enter your next command.
If you enter the DEBUG command,
DEBUG mode is entered with the PS\V
and registers set as they were when the
abend occurred. If you enter any other
command, the abend recovery routine
releases all your virtual storage and
reinitializes the command handling
mechanism before executing your next
command.

nnn (HEX xxx) doublewords of
system storage have been
destroyed; re-IPL CMS

ISlE

3278 MODS display terminal not
supported by old CMS editor
Explanation: The 3278 MOD 5 is a new
display device and is not supported by
the old CMS editor.
System Action: The EDIT session is
terminated.

User Response: Enter a valid
command.

Conversational Monitor System (eMS) Messages

295

DMS
User Response: The 3278 MOD 5
display device may be used under the
system product editor in edit
compatibility mode. For details, refer. to
th~ System Product Editor Command
and Macro Reference.

152T

154T

Explanation: Insufficient free storage
is available to allocate a save area for
an SVC.
System Action: The system is
terminated abnormally with abend code
X'OFO'.

System abend xxx called from
vstor
while UFDBUSY = xx; re-IPL
CMS
Explanation: A system abend occurred
in a routine that updates the user file
directory for a read/write disk. The
UFDBUSY flags are set. The
UFDBUSY flags are defined in the
FVSSECT of the VMjSP System
Product Editor Command and Macro
Reference.

User Response: If the abend was
caused by an error in the application
program (such as an unending loop), fix
the program and retry. If not, use the
CP DEFINE command to increase the
size of YOllr virtual storage, IPL CMS
again, arid reissue the command.

155T

System Action: The system is
terminated by loading a disabled wait
state PSW.

System and User Action: The system
clears any stacked input lines and
allows you to type in your next
command.
If you enter the DEBUG command,
DEBUG mode is established with the
PSW and registers set as they were
when the abend occurred. If you enter
any other command, the abend recovery
routine releases all your virtual storage
and reinitializes the command handling
mechanism before executing your next
command.

HX during abend processing was
ignored
Explanation: 'HX' was typed while the
abend processing routine was in
progress.
System Action: The system ignores
the 'HX' and continues abend
processing.
User Response: None.

User abend nnnn called from vstor
Explanation: An abend macro was
executed at the specified location.

User Response: If you wish to
continue abend recovery, use the CP
command STORE PSW to turn off the
wait state bit leaving the address field
unmodified, and type BEGIN. However,
the system may be unable to continue
operating properly, and, in the worst
case, you may destroy your read/write
disks.

153W

Save area for SVC call from vstor
cannot be allocated

156E

{FROMIRecord} nnn not
found--[the] file Un ft fm] has only
nnn records
Explanation: The FROM: option was
given in the command line or set up by
the DEFAULTS command to specify the
starting record of the copying operation,
but the specified input file does not
contain that many records.
System Action: RC = 32.

296

VM/SP System Messages and Codes

DMS
Execution of the command is
terminated. The system status remains
the same, with the following exceptions:
•

•

If the APPEND option was specified
and the copying process began
before the error was discovered,
records have been appended to the
output file.

CMSUTl, on the output disk,
con tains the records copied so far.
User Response: Reissue the command,
specifying a valid label.

157S

If the NEWFILE (the default),

Explanation: While files were being
added to a MACLIB, either the
maximum CMS file size (65533 items)
was exceeded or the MACLIB disk space
was filled. If the error was detected
while writing the first member to a
MACLIB, the last part of the message is
omitted and message DMSLBM213W is
also issued. Otherwise, the member
name of the last successful addition is
displayed.

REPLACE, or OVL Y option was
specified and the copying process
began before the error was
discovered, then COPYFILE
CMSUTl, on the output disk,
contains the records copied so far.
•

If in multiple-output-file mode,
several output files may have been
created before the error was
discovered.

System Action: RC = 88.
Execution of the command is
terminated. All successful additions
made before the limit was exceeded are
contained in the MACLIB.

A GET VSCREEN command or XEDIT
subcommand was issued that specified a
record number beyond the end of file.
User Response: Reissue the command,
specifying a valid starting record.

Label label not found in file in

157E

User Response: Issue the LISTFILE
command to determine if the number of
MACLIB items is approaching 65533. If
so, no more macros may be added to the
MACLIB; it is at the CMS file size ~imit.
Generate another MACLIB.

It 1m

Explanation: The FRLABEL option
was specified in the command line, but
the given label was not found in the
specified input file.

Issue the QUERY command to see if the
MACLIB disk is approximately 97
percent full. If so, more disk space must
be found. Issue the MACLIB MAP
command to determine the contents of
MACLIB.

System Action: RC = 32.
Execution of the command is
terminated. The system status remains
the same, with the following exceptions:
•

•

If the APPEND option was specified
and the copying process began
before the error was discovered.
records have been appended to the
output file.

If the NEWFILE (the default),
REPLACE, or OVL Y option was
specified and the copying process
began before the error was
discovered, then COPYFILE

MAC LIB limit exceeded [, last
member added was membername]

158E

No CMS/DOS procedure library
support
Explanation: eMS/DOS does not
support the reading or writing of the
DOS/VS procedure library from the user
program.
System Action: RC = 100.
Execution of the command is
terminated.

Conversational Monitor System (CMS) Messages

297

DMS
User Response: Correct the ten-byte
field passed to DMSOPL ($$BOPNLB) to
indicate source library processing.
Then reissue the command.

System Action: RC = 100 is given if
CMS initiated the cancel. Otherwise
the appropriate return code (from 0 255) will be passed back to the user (this
is the return code passed from the user
to DMSDOS). If the return code passed
to DMSDOS is greater than 255, then
Dl\fSDOS passes a special RC = 101.

Insufficient storage available to
satisfy DMSFREE request from
vstor

159T

User Response: If the cancel was
initiated by the user's request, no action
is needed. If an error message precedes
this message, follow the user action of
the preceding message.

Explanation: A DMSFREE request
from the specified location could not be
satisfied. If the request was variable,
then even the minimum request could
not be satisfied.
System Action: The system makes no
further attempt to allocate storage, and
takes further action depending on the
type of DMSFREE call that was made:
•

If the call was conditional (the
ERR = option was specified), a
return is made to the caller with a
return code of 1.

•

If the call was unconditional and
was made via SVC 203, a system
abend OF7 occurs.

•

If the call was unconditional and
was made by specifying
TYPCALL=BALR in the
DMSFREE macro, a system abend
OF8 occurs.

User Response: In the case of
conditional requests, the programmer
has presumably anticipated an error
situation, and no further action is
required. In the case of a system abend,
issue the DEBUG command to attempt
recovery from the situation.

160S

Invalid DMSFREE call from vstor
Explanation: An invalid DMSFREE
request was made. One of the following
has occurred:
•

The number of double words
requested was zero or negative.

•

For variable requests, the minimum
request was greater than the
maximum. (Note that this error is
never detected if the maximum
request can be satisfied. This point
can be important where a program
that has run successfully suddenly
fails when less storage is available.)

System Action: The system makes no
further attempt to allocate storage, and
takes further action depending on the
type of DMSFREE call that was made:
•

If the call was conditional (the
ERR =-7_ option was specified), a
return is made to the caller with a
return code of 4.

•

If the call was unconditional and
made via SVC 203, a system abend
OF7 occurs.

•

If the call was unconditional and
was made by specifying
TYPCALL = BALR in the
DMSFREE macro, a system abend
OF8 occurs.

Job cancelled due to program
request
Explanation: The job has been
canceled either by a CANCEL macro
issued from the user's program, or from
the CMS/DOS routine when an error
was encountered during execution.

298

160T

VMjSP System Messages and Codes

DMS
10

User Response: In the case of
conditional requests, the programmer
has presumably anticipated an error
situation, and no further action is
required. In the case of a system abend,
use the DEBUG command to attempt a
recovery from the situation.

11
12

161S

Unexpected error code nn on
SYSaaa
Explanation: An error occurred during
an EXCP (SVC 0) request or during
OVTOC, PVTOC, or CVTOC macro
processing. Error codes 1-9 are for
EXCP error codes; 10-20 are for OVTOC,
PVTOC, and CVTOC.

Note: OVTOC, PVTOC, and CVTOC
are internal DOS macros which are used
in the common VTOC handler. They
are not user macros, therefore, they are
not in any available DOS source library
unless the optional feature tapes are
installed in private source libraries.

15
16

19
20

The error code indicates the type of
error that occurred:
Code Meaning
1
No channel program(s) (CCW)
address was specified in the CCE.
2
The logical unit specified in the
CCB is unassigned.
3
The device specified for the logical
unit in the CCB is unsupported.
·4
An invalid CCW command code
was found.
The logical unit specified in the
5
CCB is assigned to an unknown
disk.
An attempt has been made to write
6
to a DOS-formatted disk.
7
A specified CCW command is
unsupported in ClVIS/DOS.
An attempt has been made to read
8
from a disk not in Cl\1S. DOS, or
OS format.
9
End-of-extent encount.ered before
end-of-filp on a nos formatted
disk.

No DOSCB was found for the file
associated with this request.
The disk associated with this
logical unit is not accessed.
The disk associated with this
request is not in a recognizable
format (for example, OS, DOS,
CMS).
In attempting to find the real
Common VTOC Handler for a DOS
formatted disk, the CMSBAM
segment was not found.
The real Common VTOC Handler
was not found in the CMSBAM
DCSS.
The attempted PVTOC request is
not supported.
No free storage available to
process this request.
The specified logical unit is not
assigned.
Incorrect Fl label address specified
on a PVTOC READ by address or
PVTOC WRITE by address
request.
The CMS file specified for this
request was not found.
The physical device assigned to
this logical unit is not the same as
the device specified for this logical
unit in the DOSCB.

System Action: RC = 100.
Execution of the routine is terminated.
User Response: Use the' error code to
determine and correct the possible cause
of error.

Invalid DMSFRET call from vstor,
error number n

161T

Explanation: An invalid DMSFRET
request was made from the specified
address. The error number indicates the
type of error that occurred:
n

Meaning

The number of cioublewords
specified was zero or negative.

Conversational Monitor System (eMS) Messages

299

DMS
The block of storage being
released was never allocated by
DMSFREE. Such an error is
detected if one of the following is
found:

In the case of a system abend, use
DEBUG to attempt to recover from the
situation.

162T

•

The block does not lie
entirely within those sections
reserved for DMSFREE
storage.

Explanation: A free storage
management pointer in NUCON has
been destroyed. The system cannot
continue. The error code indicates the
type of error that occurred:

The block crosses a page
boundary that separates a
page allocated for
TYPE = USER storage from a
page allocated for
TYPE = NUCLEUS storage.

Code Meaning
84 The current low EXTEND value
(FREELOWE) is greater than
VMSIZE.
85 The current low EXTEND value is
below the beginning user of the
area.
86
Bytes in FREET AB are not within
the valid range.

The block overlaps another
block already on the free
storage chain.

The address given for the block
being released is not doubleword
aligned.

System Action: The system is
terminated by loading a disabled wait
state PSW.

System Action: The system makes no
further attempt to release the storage
block, and takes further action
depending on the type of DMSFRET call
made:
•

If the call was conditional (the

ERR = option was specified), a
return is made to the caller with
a return code of5, 6, or 7.
•

If the call was unconditional and

was made via SVC 203, a system
abend OF7 occurs.
•

If the call was unconditional and

was made by specifying
TYPCALL= BALR in the
DMSFREE macro, a system
abend OF8 occurs.
User Response: In the case of
conditional requests, the programmer
has presumably anticipated an error
situation, and no further action is
required.

Vital free storage pointers
destroyed (internal error code nn);
re-IPL CMS

User Response: IPL CMS again.

163T

{LowIHigh}-CORE user chain has
been destroyed (internal error
code nn)
Explanation: The chain of all storage
elements, from which DMSFREE
storage with TYPE = USER (the default)
is allocated, has been destroyed.
Since these storage pointers are
unprotected, a user program may
inadvertently destroy them without
getting a protection violation. The
"internal error code" in the error
message is for error analysis by system
programmers.
System Action: The system first
displays message DMSFREi65T.
Next, the system attempts to recover
sufficiently 80 that processing can

300

VM/SP System Messages and Codes

(

DMS
continue at least to the point where
abend recovery can be performed. It
does this by zeroing out the chain
header pointers for the destroyed chain.
This effectively "loses" any storage that
is on that particular chain, but it allows
processing to continue. (Note that
abend recovery will later recover all
"lost" TYPE = USER storage.)

storage, and save the output for your
system programmer. Then IPL CMS
again.

165T

Explanation: This message appears in
conjunction with messages
DMSFRE163T and DMSFRE164T. It
indicates the contents of the DMSFRE
chain header block for the destroyed
chain.

Further system action depends on the
type of DMSFREE or DMSFRET call
that was made:
•

System Action: See "System Action"
for messages DMSFRE163T and
DMSFRE164T.

If the call was conditional (the

ERR = option was specified), a
return is made to the caller with a
return code of 2.
•

User Response: See "User Action" for
messages DMSFRE163T and
DMSFRE164T.

If the call was unconditional and

was made via SVC 203, then a
system abend OF7 occurs.
•

If the call was unconditional and

166T

was made by specifying
TYPCALL = BALR in the
DMSFREE macro, a system abend
OF8 occurs.

System Action: The system is
terminated by loading a disabled wait
state PSW.

In the case of a system abend, use the
DEBUG command to attempt a recovery
from the situation.

User Response: Issue the CP DUMP
command to get a dump of virtual
storage, and save the output for your
system programmer. Then IPL CMS
agaIn.

{LowIHigh}-CORE nucleus storage
pointers destroyed (internal error
code nn); re-IPL CMS
Explanation: The chain of free-storage
elements, from which DMSFREE
storage with TYPE = NUCLEUS is
allocated, has been destroyed.
System Action: The system is
terminated by loading a disabled wait
state PSW.
User Response: Issue the CP DUMP
command to get a dump of virtual

Unexpected error in free storage
management routine (internal
error code nn); re-IPL CMS
Explanation: The DMSFRE routine
had an unexpected internal error.
Furthermore, a check showed that all
internal free storage pointers were
valid.

User Response: In the case of
conditional requests, the programmer
has presumably anticipated an error
situation, and no further action is
required.

164T

Chain header at vstor: vstor

167S

. Previous MAC LIB function not
finished
Explanation: A MACLIB GEN, ADD,
REP, or DELETE function issued for
this MACLIB was ended (for example
via a HX command) prior to normal
completion.
System Action: RC = 88.

Conversational Monitor System (CMS) Messages

301

DMS
program area (between
FREELOWE and FEEUPPR).

The current command is not executed.
The system status remains the same.
User Response: The MACLIB status is
unpredictable. Use the MACLIB GEN
command to reconstruct the MACLIB.

167T

Free storage management error
(internal error code n)
Explanation: An error occurred in the
free storage management routine that
handles DMSFRES, DMSFREE, and
DMSFRET requests.

•

The block crosses a page
boundary that separates a page
allocated for user storage from
a page allocated for nucleus
type storage.

•

The block overlaps another
block already on the free
storage chain.

(DMSFRET) The address given for
the block being released is not
doubleword aligned.

(DMSFRES) An invalid request
code was passed to the DMSFRES
routine. Since all request codes
are generated by the DMSFRES
macro, this error code should
never appear.

Code Error
1

(DMSFREE) Insufficient storage
space is available to satisfy a free
storage request or the minimum
request could not be satisfied on a
variable request.

(DMSFREE or DMSFRET) User
storage pointers destroyed.

(DMSFREE, DMSFRET, or
DMSFRES) Nucleus storage
pointers destroyed.

System Action: The system begins to
check all free storage pointers for
consistency to see if any have been
destroyed. The system displays further
diagnostic messages when
inconsistencies are discovered.

(DMSFREE) An invalid size was
requested. This error exit is taken
if the requested size does not
exceed zero. For variable requests,
the minimum request exceeds the
maximum request. (However, the
latter error is not detected if
DMSFRE is able to satisfy the
maximum request.)
(DMSFRET) An invalid size was
passed to the DMSFRET macro.
The specified length is not
positive.
(DMSFRET) The block of storage
that is being released was never
allocated by DMSFREE. One of
the following errors occurred:
•

302

For return codes greater than 8 an
unexpected and unexplained error has
occurred in the free storage
management routine.

The block was not within
either the low storage free
storage area or the user

VM/SP System Messages and Codes

User Response: Check the "User
Action" for the further diagnostic
messages that are produced.

168S

Pseudo register table overflow
Explanation: (ST ART or
LOAD/INCLUDE START). The pseudo
register index table is full. There are
too many pseudo registers (external
dummy sections) in the loaded files.
This is a system restriction.
System Action: RC'-: 104.
Execution of the command is
terminated. The system status remains
the same.

(

DMS
User Response: Correct the Assembler
program and try again.

User Response: IPL CMS again.

172E

169S

Explanation: The TOLABEL and
FRLABEL options were specified.
Either hoth labels were equal, or the
TOLABEL was an initial substring of
the FRLABEL label (as "ABC" is an
initial substring of "ABCD"). This is an
error condition because it implies that
no records whatsoever are to be copied
to the output file.

Explanation: The ESD identifier in the
TXTIREPIRLDIEND card has not
previously been read. It should have
been read by this time.
System Action: RC = 32.
Execution of the command stops. The
system status remains the same.
User Response: Recreate the TXTLIB
or TEXT file. Then reissue the
command.

170S

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.

Disk mode(vdev) has maximum
number of files
Explanation: 3400 files have been
written. If any additional files were
written, the disk area that contains the
file status table blocks would overflow.
System Action: RC = 10.
The file is not written. The system
status remains the same.
User Response: Erase some files from
the disk.

171T

TOLABEL label {equalslis an
initial substring of} ~'RLABEL
label

{ESDID table overflowlESD data
referenced by name card is
missing}

Permanent console error[; re-IPL
eMS]
Explanation: Either the terminal is
not operational (for example, Start I/O
trouble has occurred) or the status of
the termin'al is unexpected (for example,
channel errors. or bad interrupt
sequence).
System Action: The system is
terminated liy loading a disabled wait
state PSW. The wait state PSW
contains the eMS nucleus address
where the error occurred.

User Response: Correct and reissue
the command.

No records were copied to output
file fn ft fm

173E

Explanation: The options specified for
the input files caused no records to be
copied. This will happen, for example, if
the FRLABEL label appears in the first
record of each (or the only) in pu t file
being copied to the output file.
System Action: RC = 40.
Execution of the command is
terminated. The system status remains
the same, with the following exceptions:
•

If the APPEND option was specified
and the copying process began
before the error was discovered,
records have been appended to the
output file.

•

If the NEWFILE (the default),

REPLACE, or OVLY option was
specified and the copying process
began before the error was
discovered, then COPYFILE
CMSUT1, on the output disk,
contains the records copied so far.

Conversational Monitor System (CMS) Messages

303

DMS
•

If in multiple output file mode,
several output files may have been
crea ted before the error was
discovered.

175E

Explanation: An error has been
detected in the parameter list to
DMSEXE.

User Response: Correct and reissue
the command.

174W

System Action: RC = 10000.
Execution is terrr:inated at the point of
the error.

Sequence error introduced in
output file: seqnoi to seqno2
Explanation: The updating procedure
caused a sequence error to be
introduced into the output file. That is,
in the output file there were two records
(with the sequence numbers shown in
the warning message) such that the
sequence number in the first record was
equal to or exceeded the sequence
number in the second.
System Action: RC = 8.
The invalid sequence numbers are left
in the records, which are written to the
output file. Update processing
continues, and, if the CTL option was
specified, additional update passes are
made.
If several warning messages are
generated during the updating process,
the final return code passed by the
UPDATE command will be the highest
return code (4, 8, or 12) associated with
the warning messages. The REP option,
if it was specified, will be ignored, and
the final update deck will have the fileid
"$fname ftype."

See the explanation of message
DMSUPD1771 for further information
on the meanings of the UPDATE
warning return codes.
User Response: Probably. the
resequencing field following the "$" in
the last update control card contained
invalid data. Correct the invalid
control card in the update file, and
reissue the UPDATE command.

Invalid EXEC command

User Response: Correct the parameter
list and re-execute the EXEC.

176W

Sequencing overflow following
sequence number seqno
Explanation: When the resequencing
increment was added to the sequence
number shown~ the result overflowed
the maximum sequence number. If the
SEQ8 option is in effect, the maximum
sequence number is 99999999. If the
NOSEQ8 option is in effect, however,
the maximum sequence number is 99999.
System Action: RC = 8.
The new sequence number is truncated
on the left to 8 or 5 digits (depending on
the status of the SEQ8 option). A
sequencing error is introduced into the
output file.
Update processing continues, and~ if the
CTL option was specified, additional
update passes are made. If several
warning messages are generated during
the updating process, the final return
code passed by the UPDATE command
is the highest of the return codes (4 or 8
or 12) associated with the warning
messages.
The REP option, if it was specified, is
ignored. and the final update deck has
the fileid "$fname ftype. "
See the explanation of message
Dl\fSUPD177I for further information
on the meanings of the UPDATE
warning return codes.
User Response: Probably, the
resequencing field following "$" in the

304

VM/SP System Messages and Codes

(
\

DMS
last update control card contained
invalid data. Correct the invalid
control card in the update file, and
reissue the UPDATE command.

1771

Warning messages issued
(severity = nn)[; REP option
ignored]
Explanation: Warning messages were
issued during· the updating process. The
severity shown in the error message in
the "nn" field is the highest of the
return codes associated with the
warning messages that were generated
during the updating process. The
warning return codes have the following
meanings:

1781

{Updating fnlApplying fn ft fm}
Explanation: The specified update file
is being applied to the source file. This
message appears only if the CTL option
has been specified in the command line.
System Action: The updating process
continues.
User Response: None.

179EMissing or duplicate MACS card
in control file fn ft fm
Explanation: The CTL option was
specified, but the control file did not
contain exactly one 'MACS' control
card.

Code Meaning
4

Sequence errors were detected in
the original source file being
updated.
Sequence errors that did not
formerly exist in the original
source file being updated were
introduced in the output file
during the updating process.
Any other nonfatal error detected
during the updating process has a
return code of 12. Such errors
include invalid update file control
cards and missing PTF files.

System Action: The severity value is
passed back as the return code from the
UPDATE command. In addition, if the
REP option was specified in the
command line, it is ignored, and the
updated source file has the fileid
"$fname ftype," as if the REP option had
not been specified.

For the VMFTXT command, VMFTXT
did not find a MACS record in the first
non-commented line in the control file,
or multiple MACS records were found.

System Action: RC = 32.
Execution of the command is
terminated. The system status remains
the same, with the following possible
exceptions:
•

If a file with the fileid "$fname
ftype" existed on the output disk
before the command was entered,
this file may have been erased.

•

If the DISK option was in effect, and
if a file with the fileid "fname
UPDLOG" existed on the output
disk before the command was
entered, this file may have been
erased.

•

If the CTL option was in effect, and
if a file with the fileid "fname
UPDATES" existed on the output
disk before the command was
entered, this file may have been
erased.

•

If update processing had begun
before the error was detected, any or
all of the following files may have

User Response: Refer to the warning
messages that were issued and correct
the errors.

Conven~ational Monitor System (CMS) Messages

305

DMS
been created on the output disk by
the UPDATE command:

See the explanation of message
DMSUPD177I for further information
on the meanings of the UPDATE
warning return codes.

UPDATE CMSUTI
$fname ftype
fname UPDLOG - if the DISK option
was in effect
fname UPDATES - if the CTL option
was in effect
For the XEDIT command, the updating
process continues.
User Response: Correct the invalid
control file and reissue the UPDATE, or
VMFTXT command.

1791

Comparing in it im with in it im
Explanation: The specified files are
being compared.
System Action: Processing continues.
User Response: None.

180W

Missing PTF file

in it im

Explanation: An AUX file indicated
that the specified PTF file was to be
applied as an update file, but the file
could not be found. Either the AUX file
contains invalid data, or a PTF file is
missing.
System Action: RC =--= 12.
Application of'the PTF file js skipped.
Update processing continues, and, if the
CTL option was specified, additional
update passes are made.
If several warning messages are

generated during the updating process,
the final return code passed by the
UPDATE command is the highest of all
return codes (4 or 8 or 12) associated
with the warning messages.
The REP option~ if it was specified, is
ignored, and the final update deck has
the fileid "$f'name ftype."

306

VMjSP System Messages and Codes

User Response: Correct the invalid
data in the A UX file, or use the
ACCESS command to access the disk
containing the missing PTF file.

l8lE

No update files were found
Explanation: The CTL option was
specified, but none of the update and
PTF files specified by the control file
and the AUX file(s) were found. As a
result, no updates at all were applied to
the original source file.
System Action: RC = 40.
Execution of the command is
terminated, since no updating can be
performed. If the STK option was
specified, the two lines of stacked data
were placed on the stack before this
error, so that they will still be available
to an EXEC that invoked the UPDATE
command.
This situation mayor may not be an
error situation. The return code, 40, is
unique in that no other UPDATE error
message hasthat value as a return code.
Thus, the same EXEC can be used to
assemble source files that have updates
against them, and those that have no
updates against them. The latter
situation can be detected by testing for
a return code of 40, and by assembling
the "fname" file rather than the
"$fname" file.
User Response: If this is not an error
condition, no action need be taken. If
this is an error condition, it is the result
of either missing update or PTF files, or
invalid data in the control file. Either
correct the invalid data or recover the
missing files, and reissue the command.

DMS
182W

Sequence increment is zero
Explanation: A sequence increment of
zero was specified either in a ".1 S"
control card, or in the "$" field of a ".1
I" or ".1 R" control card.
System Action: RC = 8.
Although the warning message is issued,
the sequence increment of zero is
actually used, in case that was what the
user wanted. Update processing
continues, and, if the CTL option was
specified, additional update passes are
made.

before the command was entered,
this file may have been erased.
•

If the DISK option was in effect, and

if a file with the fileid "fname
UPDLOG" existed on the output
disk before the command was
entered, this file may have been
erased.
•

If the CTL option was in effect, and

if a file with the fileid "fname
UPDATES" existed on the output
disk before the command was
entered, this file may have been
erased.

If several warning messages are

generated during the updating process,
the final return code issued by the
UPDATE command is the maximum of
all return codes (4 or 8 or 12) associated
with the generated warning messages.

)

The REP option, if it was specified, is
ignored, and the final update deck has
the fileid "$fname ftype."
See the explanation of message
DMSUPD177I for further information
on the meanings of the UPDATE
warning return codes.
User Response: Unless you
intentionally specified a sequence
increment of zero, correct the invalid
update control card and reissue the
UPDATE command.

183E

Invalid {CONTROLIAUX} file
control card
Explanation: An invalid control card
was found in an AUX file or a control
file.
System Action: RC = 32.
Execution of the command is
terminated. The system status remains
the same, with the following possible
exceptions:
•

•

If update processing had begun

before the error was detected, then
any or all of the following files may
have been created on the output
disk:
UPDATE CMSUT1
$fname ftype
fname UPDLOG - if the DISK option
was in effect.
fname UPDATES - if the CTL option
was in effect.
For the XEDIT command, the execution
of the command or subcommand is
terminated. However, if multiple files
were being edited, the editing session
continues. In addition, the following
information is displayed for both AUX
and CONTROL files:
'FN FT': 'INVALID CARD'
RECORD 'NN' ---- > > *
where the asterisk (*) is
positioned under the invalid
character in the 'invalid card'
displayed in the preceding line
User Response: Correct the invalid
control card and reissue the UPDATE,
or VMFTXT command.
For DMSPRE, correct the invalid
control card and reissue the PRELOAD
command.

If a file with the fileid "$fname

ftype" existed on the output disk

Conversational Monitor System (CMS) Messages

307

DMS
184W

.f S not first card in update
file--ignored

processing continues, and, if the CTL
option was specified, additional update
passes are made.

Explanatioll: A "./ S" control card was
encountered in the update file, but it
was not the first noncomment card in
the update control file.

If several warning messages are

generated during the updating process,
the final return code issued by the
UPDATE command is the maximum of
all return codes (4 or 8 or 12) associated
with the generated warning messages.

System Action: RC = 12.
The invalid card is ignored. Update
processing continues, and, if the CTL
option was specified, additional update
passes are made. If several warning
messages are generated during the
updating process, the final return code
issued by the UPDATE command is the
maximum of all return codes (4 or 8 or
12) associated with the generated
warning messages. The REP option, if it
was specified, is ignored, and the final
update deck has the fileid "$fname
ftype." See the explanation of message
DMSUPD177I for further information
on the meanings of the UPDATE
warning return codes.

XEDIT command, the edit session is
terminated when an invalid sequence
field in the source file is detected. If the
error is detected while editing multiple
files, the editor terminates processing of
the specified file and returns to the file
which was current when the XEDIT
subcommand was issued.

User Response: Correct the update file
by moving the"./ S" control card to the
beginning of the update file. Then
reissue the UPDATE command.

185W

User Response: In the case of return
code 12, correct the invalid control card
in the update file, and reenter the
UPDATE command.

{InvalidlNon numeric} character
in sequence field seqno
Explanation: An update file control
card specified a sequence number that
contained an invalid character. Only
the digits 0 through 9 may be used to
specify a sequence number.

In the case of return code 32, reissue the
XEDIT command or subcommand
specifying a properly seriallzed source
file. To serialize your source file witout
placing alphabetic idetifiers in the
sequence fields, use the XEDIT
subcommand 'SET SERIAL ALL'.

If issu~d from DMSXUP the message is

a warning that the source file to be
edited is not properly serialized. The
error may have resulted from a
sequence field that contains alphabetic
identifiers or from an attempt to update
source data within a MACLIB file.
System Action: RC = 12.
The invalid update control card is
ignored. Furthermore, any cards
following it, up to the next".f" card in
the update file, will be ignored. Update

308

VM/SP System Messages and Codes

186W

Sequence number [seqno] not
found
Explanation: A sequence number
specified by an update file control card
could not be found in the input file. An
input sequence number higher than the
one specified was found.

DIVIS
System Action: RC = 12.
The input file is positioned at the record
whose sequence number exceeds the
sequence number being searched for.

See the "Explanation" of message
DMSUPD177I for further information
on the meanings of the UPDATE
warning return codes.

•

User Response: Correct the invalid
control card in the update file, and
reenter the UPDATE command.

If the invalid sequence field was the
first argument of a ".1 R," ".1 I," or
".1 D" operation, all records
encountered up to that point were
copied to the output file.

187E
•

If the invalid sequence field was the
second argument of a ".1 R" or ".1
D" operation, records encountered
up to that point were not copied,
and so were, in effect, deleted.

Explanation: The STK option was
specified with the UPDATE command.
This option requires the CTL option,
but CTL was not specified in the
command line.

In any event, no further deleting or
inserting takes place for that
control card, and any cards
following this card, up to the next
".1" card in the update control file,
are ignored. Update processing
continues, and, if the CTL option
was specified, additional update
passes are made.
•

If several warning messages are
generated during the updating
process, the final return code issued
by the UPDATE command is the
maximum of all return codes (4 or 8
or 12) associated with the generated
warning messages.

The REP option, if it was specified,
is ignored, and the final update deck
has the fileid "$fname ftype."
For the XEDIT command, the execution
of the command or subcommand is
terminated. However, if multiple files
were being edited, the editing session
continlles. In addition, the following
information is displayed for both A UX
and CONTROL files:
'FN FT': 'INVALID CARD'
RECORD 'NN' ---- > > *
where the asterisk (*) is
positioned under the invalid
character in the 'invalid card'
displayed in the preceding line

Option STK invalid without CTL

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the command,
specifying the CTL option.

188W

SYSUT2 header record is invalid
because of blocksize
incompatibility; user action
required
Explanation: The specified file is not
in the expected format.
For DMSUTL, a LOADLIB COPY was
performed whereby the SYSUT2 data set
already existed and its blocksize is less
than the SYSUT1 blocksize. The
SYSUT2 blocksize was increased to
equal the SYSUT1 blocksize. However,
the new blocksize was not posted in the
SYSUT2 header record. User action is
now required to prevent unpredictable
results.
System Action: RC = 4.
Processing continues.
User Response: To rebuild the
SYSUT2 data set correctly, issue
another LOADLIB COPY command.
Specify the modified output LOADLIB
as the SYSUT1 data set and omit the

Conversational Monitor System (CMS) Messages

309

DMS
SYSUT2 data set from the command
input.

189E

191W

Explanation: The VER or REP
displacement, or.:the DUMP start or end
address, did not fit completely within
the CSECT or MODULE.

The LIST function of the
LOADLIB command does not
support concatenated SYSUTI

System Action: RC = 4.
Execution of the command continues.
All REP control records are ignored
until the next NAME or END control
record is encountered.

Explanation: Fileidl, which is referred
to as the SYSUTI data set, is
concatenated in the file definitions.
A LOADLIB LIST was performed during
which the SYSUTI data set was
concatenated. This is not supported,
because if the same member name was
used in more than one of the loadlibs
being concatenated, a loop would result
during list processing.

User Response: Correct the
displacement field or the start or end
address of the control record and
reissue the command.

(
192W

System Action: RC = 24.
User Response: Change file definitions
so that SYSUTI is no longer
concatenated. Then issue a LOADLIB
LIST for each loadlib individually.

190W

310

Odd number of digits; set NO GO
switch
Explanation: Either an address or a
data field of a control record had an odd
number of digits.
System Action: RC = 4.
Execution of the command continues.
All REP control records are ignored
until the next NAME or END control
record is encountered.

Invalid control record or NO GO
switch set
Explanation: Either the input control
record was invalid or the NO GO switch
was previously set. If the NO GO
switch was not previously set, the input
control record is invalid, and this
causes the NO GO switch to be set at
this time.

Patch overlaps; set NO GO switch

User Response: Enter an even number
of digits and reissue the command.

193W

Preceding control record flushed
Explanation: The NO GO switch was
set by a previous control record and has
not been reset.

System Action: RC = 4.
Execution of the command continues.
All REP control records are ignored
until the next NAME or END control
record is encountered.

System Action: RC =; 4.
Execution of the command continues.

User Response: Determine the cause of
the error and correct it; then reissue the
command.

User Response: A previous error
message was issued. Check the "User
Action" for that message.

VMjSP System Messages and Codes

DMS
1945

Book subl.book contains bad
records

1961

Printer OOE setup complete
Explanation: The virtual 3800 printer
setup has been completed.

Explanation: The book being copied
contains invalid source statement
library records.

System Action: All the LOAD
commands specified in the SETPRT call
have been issued and the current spool
file remains open for printing of data in
that spool file.

System Action: RC = 100.
Execution of the command is
terminated. The system status remains
the same.

User Response: None.
User Response: Recatalog the book on
the system or private source statement
library and reissue the command.

194W

1975

CSECT not found in {member
membernamelmodule module}; set
NO GO switch

Explanation: An undiagnosed error
occurred while trying to perform I/O to
the device.

Explanation: The specified CSECT was
not found in a library member or a
module loader table.

System Action: RC = 100.
None.
User Response: Use the CP DETACH
command to detach the 3800 that has
something wrong in its definition. Then
redefine it via the CP DEFINE
command and try to reissue the
command.

System Action: RC = 4.
Execution of the command continues.
All control records are ignored until the
next NAME or END control record is
encoun teredo
User Response: The control record
with the invalid CSECT name has been
printed at the printer or displayed at
your terminal. Check the member or
module for the proper CSECT name and
reissue the command.

195W

Base value invalid; set NO GO
switch
Explanation: The BASE address did
not match the CSECT address.
System Action: RC:= 4.
Execution of the command continues.
All REP control records are ignored
until the next NAME or END control
record is encountered.

Undiagnosed error from printer
OOE

198E

SETPRT ·load check; sense = sense
Explanation: A load check was caused
by the SETPRT command.
System Action: All output to the 3800
(up until the LOAD CHECK occurred)
has been placed on the spool file.
User Response: Find out why the
particular module caused a Load Check
(possibly by interpreting the returned
sense bytes and correct the problem or
specify a different module. In any case,
close the virtual 3800 with the PURGE
option and reissue the SETPRT
command with the correct parameters.

User Response: Insert the proper
address in the BASE control record and
reissue the command.

C()nver~ational Monitor System (eMS) Messages

311

DMS
1995

Printer OOE not a virtual 3800
Modell or 3
Explanation: The 'OOE' printer was not
defined as a virtual 3800 Model 1 or 3
printer.

references and issue the INCLUDE
command.

202W

Explanation: A CSECT or entry point
name was encountered more than once
in the input stream to the loader.

System Action: No output in the spool
file.
User Response: Redefine the virtual
printer as a virtua13800 Modell or 3.
Then reissue the SETPRT command.

200W

System Action:RC = 4.
Only the first CSECT is loaded.
Program execution may not proceed as
expected. All references are resolved to
the first name.

Verify reject; set NO GO switch
Explanation: For DMSZAP, the data
on the VER or VERIFY control record
is not exactly the same as the data at
the specified location in the specified
file.

User Response: Reassemble the
program with a different identifier
substituted for the duplicate.

203W

System Action: RC = 4.
Execution of the command continues.
All REP control records are ignored
until the next NAME or END control
record is encountered.

Syst~m Action: RC = 4.
The card is ignored.

User Response: None; or check the
name on the SLC card.

204E
The following names are
undefined: name list
Explanation: A list of names of
unresol ved external references is
displayed.

Note: A name entered with the
command is considered an unresolved
external reference if no text file with
that name can be located.
System Action: RC = 4.
Loading is completed.
User Response: None; or obtain access
to the files containing the unresolved

312

VM/SP System Messages and Codes

SET LOCATION COUNTER name
name undefined
Explanation: A name was specified on
an SLC card in the loader input stream
and that name had not yet occurred as
an external name in the loader text file.

User Response: Determine the proper
control information and correct the
VER control record. Delete from the
input stream any other VER-REP pairs
that were processed successfully, and
then reissue the command.

201W

Duplicate identifier identifier

Too many WCGMs needed for
CHARS
Explanation: The collection of
Cha..:~ ;I.!ter A:'~!"t~lgBm(;nt Tables specified
in the comm;:ind line denote more
WCGMs to be loaded than are available
for the virtual 3800. (4 if 4WCGM is in
effect and 2 otherwise).
System Action: Nothing is transferred
to the virtual 3800.
User Response: Reissue the command
with a collection of CHARS values that
will fit into the WCGM space for the
virtual 3800.

DMS
205E

No files in your reader
Explanation: There were no files in
your virtual reader.
System Action: RC = 28.
Processing is terminated.

207W

Invalid update file control card
Explanation: An invalid control card
was found in the update file. Some of
the errors that cause this message to be
issued are:
•

The first card in the update file was
not a control card.

•

The first card following a "./S" or a
"./D" or a "./*" was not a control
card.

•

The operation field was missing,
invalid, or contained more than one
character.

•

The label field of a "./S" card
contained more than three
characters.

•

An invalid sequence field was
specified, or a required sequence
field was missing.

•

In a "./D" or "./R," the delete or
replace ending specification was
smaller than the starting
specification.

User Response: None.

205W

Reader empty or not ready
Explanation: Either the card reader
contains no files, or it has not been
readied.

)

The card reader may contain a file
spooled from a virtual punch or printer
that contains CCWs only, and no data.
Thus, this message is issued even
though the file contains no data.
System Action: RC = 8.
Execution of the command is
terminated. The system status remains
the same.
User Response: Close the card reader
and reissue the command, if the reader
contains any files.

206W

Pseudo register alignment el'ror
Explanation: A pseudo register with
the same name as a previous pseudo
register but with more restrictive
alignment was encountered.
System Action: RC = 4.
Processing continues. All references to
the particular pseudo register will have
the less restrictive alignment.
User Response: None.

System Action: RC = 12.
The invalid sequence fields are ignored,
and processing continues. However, an
incorrectly sequenced source file cannot
always be properly updated.
Update processing continues, and, if the
CTL option was specified, then
additional update passes are made. If
several warning messages are generated
during the updating process, the final
return code when the UPDATE
command has completed all processing
is the maximum of all return codes (4 or
8 or 12) associated with the generated
warning messages. The REP option, if it
was specified, is ignored, and the final
update deck has the fileid "$fname
ftype." See the "Explanation" of
message DMSUPD1771 for further
information on the meanings of the
UPDATE warning return codes.

Conversational Monitor System (eMS) Messages

313

DMS
For XEDIT, the execution of the
command or subcommand is terminated.
However, if multiple files were being
edited, the editing session continues. In
addition, the following information is
displayed for both AUX and CONTROL
files:

210E

Explanation: The specified file or
library is on a read-only disk and must
be on a read/write disk.
System Action: RC = 36.
Execution of the command is
terminated. The system status remains
the same.

'FN FT': 'INVALID CARD'
RECORD 'NN' ---- > > *
Where the asterisk (*) is
positioned under the invalid
character in the 'invalid card'
displayed in the preceding line.

For LANGGEN, the DCSS and/or the
CP repository have been saved.

User Response: Correct the invalid
control card in the update file, and
reenter the UPDATE command.

208E

User Response: Verify that the correct
file or library was specified in the
command. If it was, either access the
disk in read/write mode, or erase the
existing file or library with the same
name. Reissue the command.

File fn ft is not variable record
format

For LANGGEN, copy the SYSTEM
LANGUAGE file from the system disk
to your A-disk. Issue the LANGGEN
command again.

Explanation: The specified file did not
have a variable record format.
System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Verify that 'fn ft' is
the desired file. If it is, use the
COPYFILE command to change the
record format of the file.

209W

210W

Input file sequence error: seqnol
to seqno2
Explanation: In reading the input
source file, two records were found, with
the displayed sequence fields, such that
the sequence number in the first was
equal to or greater than the sequence
number in the second.

F'Ues do not conlpare
Explanation: The two files the user
requested compared on a line-for-line,
column-for-column basis, do not match.
System Action: RC .=c 4.
The comparison of the files is
completed. The lines that do not match
are displayed at the terminal.
User Response: You can correct the
file containing the incorrect lines using
the EDIT command.

314

{Library libnamelFile fn ft} is on
a read! only disk

VM/SP System Messages and Codes

System Action: RC = 4.
The invalid sequence fields are ignored,
and update processing continues.
However, an incorrectly sequenced
source file cannot always be properly
updated.
If the CTL option was specified, then
additional update passes are made. If
several warning messages are generated
during the updating process, the final
return code when the UPDATE
command has completed all processing
is the maximum of all return codes (4 or
8 or 12) associated with the generated
warnlng messages.

DMS
The REP option, if it was specified, is
ignored, and the final update deck has
the fileid G'$fname ftype."

212E

Explanation: The storage size of the
virtual machine is not large enough to
contain the size and number of sort files
specified.

See the "Explanation" of message
DMSUPD1771 for further information
on the meanings of the UPDATE
warning return codes.

System Action: RC = 40.
Execution of the command is
terminated. The system status remains
the same.

For module DMSXUP: Both the input
and updated source files are checked for
proper serialization. If the serialization
is in error, execution of the command or
subcommand is terminated. XEDIT
requires the updated source file to be
properly serialized so update files can be
created.

User Response: Compute the storage
size required for this sort using the
format given in the description of the
CMS SORT .command in the VM/ SP
eMS Command Reference. Redefine
storage as large as necessary using the
CP DEFINE command, and issue the
SORT command again.

User Response:
For module DMSUPD: Correct the
invalid source file and reissue the
UPDATE command.
213W
For module DMSXUP: Correct the
invalid source or update file and reissue
the XEDIT (sub)command.

Column fields out of sequence

211E

Explanation: One of the following
conditions has occurred.
•
•

Start column number exceeds end
column number.
Column number entry overflows the
eight~position option field.

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Correct and reissue
the command.

Maximum number of records
exceeded

Library libname not created[, or
erased if empty]
Explanation: None of the files to be
included in the library file could be
found, or the last active member of a
library was deleted.
System Action: RC = 4.
Execution of the command is
terminated. The system status remains
the same. The new library is not
created. Also, for DMSLBM and
DMSLBT, the library is erased if the
last active member has been deleted.
User Response: For DMSLBM and
DMSLBT, obtain access to the desired
file and/or correct the spelling of the
names and reissue the command if you
were doing a generation function. If
delete was the last function, no action is
necessary. For DMSDSL. no action is
necessary.

Conversational Monitor System (eMS) Messages

315

DMS
214W

Cannot recompute without loss of
data; no change

220R

Explanation: A command was entered
with the? or DSN ? operand. The
command expects an OS data set name
or DOS fileid to be entered.

Explanation: The number of cylinders
specified in the FORMAT command
cannot contain all the data on the disk.
System Action: RC = 8.
Execution of the command is
terminated. The system status remains
the same.

System Action: The system waits for a
response.
User Response: Enter an OS data set
name exactly as it appears in the data
set (in the form q1 < .q2.qn > where q1,
q2, and qn are the qualifiers of an OS
data set name). Or enter a DOS fileid
exactly as it appears in the file.

User Response: Either. erase some of
the files on the disk or increase the
number of cylinders to be formatted and
reissue the command.

215T

No virtual console attached;
re-IPL eMS

221E

Explanation: An invalid OS data set
name or DOS file-id was specified in the
command line.

System Action: The CMS system uses
a special interface with CP to display
this message. It is then terminated by
loading a disabled wait state PSW.

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.

User Response: Redefine a virtual
console with the CP DEFINE command,
and IPL CMS again.

User Response: Reissue the command
with a valid data set name.

Insufficient blocks on disk to
support CMS disk structure
Explanation: The user has requested
the formatting of a mini disk area that is
not large enough to contain the
essential CMS disk structure.
System Action: RC = 100.
Execution of the command is
terminated. The disk is unchanged.
User Response: Acquire a larger
minidisk and reissue the command; or if
the disk is large enough, specify a
larger number of blocks to be formatted
in the FORMAT command.

316

Invalid dataset name

Explanation: The user has
disconnected his virtual console.

222E
216E

Enter dataset name:

VM/SP System Messages and Codes

I/O error reading datasetname from
{fm IOS IDOS} disk
Explanation: An I/O error occurred
while reading the specified OS data set
or DOS file from an OS or DOS disk.
For DMSLDS, an I/O error occurred
while reading the member directory in
DMSROS.
System Action: RC = 28.
Execution of the command is
terminated. The system status remains
the same.
User Response: Correct the cause of
the I/O error and reissue the command.

DMS
223E

Execution of the command is
terminated. The system status remains
the same.

No filemode specified
Explanation: A filemode was not
specified in the command line.
System Action: RC = 24.
,Execution of the command is
terminated. The system status remains
the same.

User Response: Correct the command
line and retry.

2261

User Response: Reissue the command,
specifying a filemode.

224E

Explanation: The last member of the
PDS (partitioned data set) has been
moved successfully to a CMS file.
System Action: Execution of the
command is terminated. The system
status remains the same.

Fileid already in use
Explanation: A dataset name exists in
an outstanding FILEDEF with a
'different ddname but with the same
fileid, or a dataset name was specified
for a fileid previously defined under a
different ddname.

End of PDS move

User Response: None.

2271

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.

Processing volume nn in dataset
datasetname
Explanation: The specified as data set
or DOS file is multivolume. The number
of the volume being processed is
specified in the error message. End of
volume is treated as end of file and
there is no end-of-volume switching.

User Response: Clear the existing
fileid before reissuing the command or
specify a different fileid.

System Action: Execution continues.
2251

PDS member membername moved
Explanation: The specified member of
an as PDS (partitioned data set) has
been moved successfully to a CMS file.
System Action: MOVEFILE continues
moving PDS members to CMS files until
the end of the file is reached.

User Response: None.

227W

Invalid extent found for
datasetname on fm disk
Explanation: The high extent for the
subject data set indicates a relative
track number lower than that for the
low extent of the data set.

User Response: None.
System Action: RC = 4.
Execution continues.
226E

No dataset name allowed with
FREE option
Explanation: A data set name must not
be specified with the FREE option of the
LISTDS command.

User Response: For further
investigation, use the CMS command
DDR to locate and dump the DSCB
containing the invalid extent.

System Action: RC = 24.

Conversational Monitor System (eMS) Messages

317

DMS
228E

No DDNAME entered

Explanation: When prompted for the
ddname corresponding to the "dname"
entry for the tape dataset in the Access
Method Services control statement, the
user entered a null line.

82
83

System Action: RC = 24.
AMSERV does not execute the Access
Method Services job. The system status
remains the same.

System Action: RC = 80, 81, 82, or 83.
Execution of the command is
terminated. The system status remains
the same.

User Response: Find the "dname"
entries for the tape dataset(s) in the
Access Method Services jobstream and
, reissue the AMSERV command.

2281

User Response: If the error code is 81,
82, or 83, you cannot use CMS as
access to read the as data set or DOS
file. If the error code is 80, make sure
the accessed as or DOS disk is
attached, or determine the cause of the
error. If the OS data set or DOS file is
valid, reissue the command.

User labels bypassed on dataset
datasetname
Explanation: The specified as data set
or DOS file has a disk user label. The
user labels are automatically skipped
and the DCBEXLST routine, if specified,
is ignored. This message is issued when
the 08 File Status Table (FST) is
created. This occurs during the
execution of the first FILEDEF
command defining the as ddname.
Reissuing the same FILEDEF command
without reaccessing the disk does not
create a new as FST, and the message
is therefore not issued again.

2291

Unsupported OS dataset, error nn
Explanation: The specified as data set
or DOS file is not supported by eMS as
access routines. The error code
meanings are:
Code Meaning
80

318

An I/O error occurred while an as
data set or DOS file was being read
or an as or DOS disk was
detached without being released.

VM/SP System Messages and Codes

No members found
Explanation: No members exist in a
partitioned data set.
System Action: None.
User Response: Determine whether the
data set you specified is the correct one
and if so, why it contains no members.
Correct the condition and reissue the
command.

System Action: Execution continues.

229E

The file is an OS
read-password-protected data set or
a DOS file with the input security
indicator on.
The as data set or DOS file is not
BPAM, BSAM, or QSAM.
The as data set or DOS file has
more than 16 user labels or data
extents.

230E

Number ofVSAM exit routines
has exceeded maximum of 128;
unable to continue
Explanation: The number of exit
routines for VSAM data sets (both
active and inactive) has exceeded the
maximum of 128 for the run unit.
System Action: The system is '
terminated abnormally with abend code
X'177'.

DMS
supported' for spanned records, provided
the filemode number is 4 and the data
set is physical sequential (BSAM)
format.

User Response: Reduce the number of
exit routines for VSAM data sets and
re-execute the program.

230W

O/S disk--fi'eid and/or options
specified are ignored

2331

Explanation: The specified as or DOS
disk has been accessed, but the specified
fileid and/or options are not valid and
have been ignored.

Explanation: All tracks on the
specified disk are allocated.

System Action: RC = 4.
Execution of the command continues.

User Response: If the disk is an as or
DOS disk, use one of the OS or DOS
utilities to reformat the disk (if you no
longer need any of the data on it) or
delete some data sets. If it is a VSAM
disk, use Access Method Services to
delete some clusters and data spaces.

System Action: None.

User Response: None.

231E

I/O error reading VTOC from
{fm/OS/DOS} disk
Explanation: An I/O error was
encountered while reading the VTOC
from the specified disk.
System Action: RC = 28.
Execution of the command is
terminated. The system status remains
the same.
User Response: Correct the cause of
the I/O error and reissue the command.

232E

No free space available on fm disk

Invalid RECFM--spanned records
not supported
Explanation: The MOVEFILE
command uses the GET and PUT
macros in locate mode. The GET and
PUT macros are not supported for use
with spanned records.
System Action: RC = 88.
Execu tion of the command is
terminated.
User Response: The user will have to
provide a utility/program to process the
file. The READ and WRITE macros are

234E

Error in LOAD LIST file fn ft fm[:
no input]
Explanation: During processing of the
load list EXEC file, an invalid statement
was encountered. Input must consist of
valid EXEC control words (that are
ignored) and names of input text files in
the form
&1 &2 filename [filetype]
Filename and filetype (if specified) must
not be more than eight characters in
length. A "NO INPUT" condition exists
if after the scan of the load list, no
filename filetype entries were found.
System Action: RC = 8.
Execution of the command is
terminated. The system status remains
the same.
User Response: If you can determine
the problem from the "Explanation"
above and remedy the condition, reissue
the command. If not, reissue the
command and if the problem persists,
call your system support personnel.

Conversational Monitor System (CMS) Messages

319

DMS
235E

{Error n in input text file fn ft
fmlError 5 on entry symbol name}

The PRELOAD command has completed
processing. Program execution of the
output text file may not proceed as
expected.

Explanation: An error was detected
within the data contained in the input
text file. 'n' indicates the nature of the
error; it may be one of the following:
n
1

2
3
4
5
6
7

Meaning
File named did not contain an
ESD card. LANGGEN needs
this card.
Invalid ESD type code.
Invalid RLD record.
Invalid ESD LD ID.
ESD LD entry precedes its
position entry.
Invalid TXT record ESD ID.
No valid END record.

User Response: Correct the input, if
necessary.

237E

Explanation: A CSECT or entry point
name was encountered more than once
in the input stream to the preloader.
The duplicate symbols are listed in the
MAP file.
System Action: RC = 8.
The PRELOAD command has completed
processing. Program execution of the
output text file may not proceed as
expected.

System Action: RC = 12.
Execution of the command is
terminated. The DCSS is not saved.
The system status remains the same.
User Response: If you can determine
the problem from the "Explanation"
above and remedy the condition, reissue
the command. If not, reissue the
command and if the problem persists,
call your system support personnel.
The error may have been caused by
invalid output from an assembler or
compiler. Reassemble or recompile the
source for the text file in error and
reissue the PRELOAD, EXPAND, or
ZAPTEXT command. Errors also may
result if the user incorrectly modifies
the text file with XEDIT or other CMS
commands. If the error is 1, supply a
valid text deck for the file named or
remove it from the control file; then
reissue the command.

236E

Unresolved external reference(s)
encountered
Explanation: Unresolved external
references have been encountered.
These are listed in the MAP file.
System Action: RC = 4.

320

VM/SP System Messages and Codes

Duplicate external symbol(s)
encountered

User Response: Reassemble the source
for the text file in error with a different
identifier substituted for the duplicate
and reissue the PRELOAD command.

238E

Preloader processing error
Explanation: An internal error was
detected during preloader processing.
This may have been caused by invalid
input.
System Action: RC = 16.
Execution of the command is
terminated. The system status remains
the same with the exception that partial
output files may have been created.
User Response: Reissue the command,
ensuring that a valid load list file (and
optional CNTRL file) are specified.
Insure that the input files contain valid
data. If the problem persists, call your
system support personnel.

DMS
2411

{Press PF10 for detail
information; PF11 for related
information.IPress PF10 for detail
information.IPress PF11 to get
related information.}

244W

Requested HELP section
unavailable; option option
assumed.
Explanation: A user requested subset
information, and no information in the
requested categories was found. The
information corresponding to the option
indicated in the message was printed
instead.

-Explanation: BRIEF HELP has been
displayed, and there is more detail and
related information available.
System Action: None.

System Action: The section(s)
corresponding to the indicated option
are displayed to the user.

User Response: Press PFIO to get more
detail information. Press PFll for
related information.

User Response: None.
2421

This HELP file in it has not been
converted to the current release
format or contains an invalid
format word.

245S

Explanation: An unrecoverable error
occurred when writing a line to the
printer, and an error code was passed to
the calling module from DMSPIO. nnn
indicates the nature of the error; it may
be one of the following:

Explanation: The file which contains
the HELP information you requested
still contains Script control words from
a previous VM/SP release, or the file
contains an invalid format word.

Code Meaning
4
An intervention is required.
5
An unknown error occurred.
100 The printer is not attached.

System Action: File in it comes up on
your screen, but it could be unformatted
or contain extra format words.

2431

Error nnn on printer

User Response: File in it needs to be
formatted with the CMS HELPCONV
facility. For more information, refer to
the eMS User's Guide.

System Action: RC = 100.
Execution of the command is
terminated. The output files contain all
changes made up to the last control
record operation.

RELATED information is not
available.

User Response: If you can determine
the problem from the above information
and correct the condition, reissue the
command; otherwise reissue the
command and if the error persists,
contact your system support personnel.

Explanation: A HELP command was
issued with the RELATED option
specified. There is not a RELATED
section in the HELP file.
System Action: RC =c 32.
Execution of the command is
terminated.
User Response: Reissue the command
with another option.

246W

No loader table present for
module in; set NO GO switch
Explanation: A CSECT name was
specified for a module that was
generated with the NOMAP option.
System Action: RC = 4.

Conversational Monitor S:vstem (eMS) Messages

321

DMS
Execution of the command continues.
All REP control records are ignored
until the next NAME or END control
record is encountered.

2491

Explanation: Under the ZAP
command, a successfully completed REP
was not followed by a LOG control
record. In lieu of a user-defined entry, a
dummy log entry 'NONAME' was
written.

User Response: Either regenerate the
module with the MAP option, or do not
use a CSECT name; then reissue the
command.

247W

Dummy log entry in file fn
ZAPLOG fm

System Action: Execution of the
command continues.

Member membername not found;
set NO GO switch

User Response: None.
Explanation: The specified member
was not found.
2508
System Action: RC = 4.
Execution of the command continues.
All control records are ignored until the
next NAME or END control record is
encountered.

Explanation: An I/O error has
occurred on the user terminal trying to
display a HELP text file. An error
message should have been issued by
CMS or CP to describe the condition.

User Response: Reissue the command
with a valid member name.

248W

System Action: RC = 100.
Execution of the command is
terminated. The system remains in the
same status as before the command was
entered.

Invalid VER/REP displacement;
set NO GO switch

User Response: Take appropriate
action as described by the CMS or CP
error message.

Explanation: The displacement
specified in a VER or REP control
record includes an area that is
undefined, for example, a Define Storage
(DS) area.
251E
System Action: RC = 4.
Execution of the command continues.
All REP control records are ignored
until the next NAME or END control
record is encountered. If the operation
is REP, the file being operated on may
be modified.
User Response: Verify that
instructions or data are at a specific
displacement and reissue the command.

322

VM/SP System Messages and Codes

I/O error or device error

HELP processing error, code nnn:
description
Explanation: An error occurred during
the formatting of a HELP text file,
indicating an error in the file text. The
error code indicates the type of error
that occurred:
Code Meaning
801

A number outside the permissible
limits for a HELP format word was
found. The limits are based
primarily on 80 characters per line
in HELP.

DMS
B02

An alphabetic parameter was
found for a HELP format word
that requires a numeric parameter.

System Action: RC = 20.
Execution of the command terminates.
For LANGGEN, the DCSS is not saved.

B03

A line was read that started with a
period, but could not be recognized
as a valid HELP format word.

User Response: Correct the filename
and reissue the command.

B04

You omitted a required parameter
for this format word.

B05

HELP does not recognize the
parameter specified on the format
word line displayed.

B06

The execution of a .IN,.IL~ or .OF
HELP format word would cause
the left margin to move to the left
of character position one.

B07

HELP has calculated a negative
space count based on the format
words contained in the test file.

253E

Explanation: The specified file
contains more than 65536 items, and
thus cannot be handled with a normal
ST ATE parameter list. This is because
the normal parameter list uses
halfwords to describe the characteristics
of the file, and a file this large cannot
be described with halfwords. The
extended parameter list (which uses
fullwords to describe the file) must be
used to execute the STATE function in
this case.

The 'description' part of the message is
a short summary of an error code
meaning listed above.

System Action: RC = BB.
Execution of the user program is
terminated.

System Action: RC = 12.
Execution of the command continues
and the line in question is ignored.

User Response: Change the user
program parameter list to the
extended-parameter-list format. If the
FSST ATE macro was used, change the
FSCB to the extended form (if used) and
add the FORl\f = E option to the
FSST ATE macro instruction.

User Response: None at execution
time, however you should correct the
file in question to prevent future
messages or errors.
254E
252E

File fn ft fm cannot be handled
with supplied parameter list

Invalid filename fn
Explanation: A filename specified in
the LANGMERG control file is
incorrect, or the control file specified on
the LANGMERG command is invalid.
For SPGEN, an invalid filename was
specified in either the SPGEN
PROFILE, or on the command line when
invoking SPGEN.
For SPLOAD, an invalid filename was
specified in either the SPLOAD
PROFILE, or on the command line when
invoking SPLOAD.

Help cannot find the requested
information. If not misspelled,
enter HELP for menu assistance
or HELP HELP for the HELP
command.
Explanation: The file specified by your
HELP request was not found on the
accessed disk(s), or in the file directory
of the 's' disk and 'y' disk (if accessed).
The request may have been misspelled
or incomplete.
System Action: RC ,= 28.
Execution of the command is terminated
and system status remains the same.

Conversational Monitor System (CMS) Messages

323

DMS
User Response: Correct the entry if in
error or use the commands specified to
obtain available HELP files.

255T

System Action: RC = 41 (Code 1 only)
RC = 256 (all others). ESERV program
execution is terminated.
User Response: If error code 1 occurs,
make sure a larger amount of virtual
storage is available for ESERV program
execution. For all other errors, contact
your system support personnel.

Insufficient storage for Exec
interpreter
Explanation: There is insufficient
storage for the System Product
Interpreter to initialize itself.
257T
System Action: RC = 10096.
Execution is terminated at the point of
the error.

Explanation: This message is issued
when a system error has been detected
which may have been caused by storage
that was overwritten.

User Response: Redefine storage and
reissue the command.

2568

System Action: CMS is placed in a
disabled wait state and CP is entered.

E8ERV execution error, code nn
Explanation: An error occurred during
ESERV program execution. The error
code indicates the kind of error that
occurred.
Code
1

5
6

324

Meaning
Not enough virtual storage
available for ESERV
processing.
Unsupported library macro
issued by the ESERV
program.
Invalid FIND request
generated as a result of an
LBRFIND request issued by
ESERV.
Invalid GET request
generated as a result of an
LBRGET request issued by
ESERV.
An error occurred in opening
the source statement library.
An LBRGET request was
issued by ESERV but the
source statement library was
not OPEN.
An I/O error occurred
accessing the source
statement library.
An LBRGET request was
issued by ESERV without a
previous LBRFIND.

VM/SP System Messages and Codes

Internal system error at address
address (offset offset)

User Response: Log off and log back
on to verify that the problem is not due
to overwritten storage. If it persists,
notify IBM programming support.

258E

The variations of this message are
explained below.
System Action: In each case, the
system action is:
RC=28.
For this application, no remaining
tables are updated.

User Response: In each case, the user
response is:
Either turn translation synonyms
OFF when turning translations
OFF, or turn translations ON when
turning translation synonyms ON.

MESSAGES:
•

{U8ERISYSTEM} translation
synonyms can not be set ON
unless {USERISYSTEM}

DMS
translations are also set ON,
application id: applid
Explanation: You attempted to set
translation synonyms ON when
translations are OFF. This is not
allowed.
•

User Response: Verify that you are
using the correct disk. For RESERVE,
reformat the disk with a block size of
512, 1K, 2K, or 4K.

260T

{USERISYSTEM} translations
can not be set OFF unless
{USERISYSTEM} translation
synonyms are also set OFF,
application id: applid

Explanation: The CMS nucleus is
designed to be used as a saved, shared
system. An attempt has been made to
use the CMS system in non-shared mode
by IPLing by device address.
Insufficient virtual storage is available
to do this.

Explanation: You attempted to set
translations OFF when translation
synonyms are ON. This is not
allowed.

259E

System Action: The virtual machine
enters CP by loading a wait PSW.
User Response: IPL the saved CMS
system by its 'system name, or redefine
your virtual storage to exceed the
ending location of the CMS nucleus.
IPL by device address again.

Disk blocksize of IPL device is too
small to save the nucleus
Explanation: An attempt was made to
write the CMS nucleus to a CMS
minidisk, but the block size of the
mini disk is too small.
261E
System Action: The CMS nucleus is
not written to the minidisk. The system
continues.

System Action: RC = 24.
None.

Note: Do not issue the FORMAT
command with the RECOMP option to
change the number of cylinders on the
mindisk.

User Response: Respecify the macro
with the correct name.

262E
Disk not properly formatted for
{RESERVEISAVEFD}
Explanation: The disk has an 800-byte
block size or is not a CMS disk.
RESERVE and SAVEFD only support
EDF disks.
System Action: RC = 16.
Execution of the command is
terminated.

No immediate command name
was specified
Explanation: The IMMCMD command
was issued with SET, CLEAR, STATUS,
or QUERY, but no immediate command
name was specified.

User Response: Increase the block size
of the CMS minidisk by using the CMS
FORMAT command; then rebuild the
CMS nucleus.

260E

Virtual machine size too small to
IPL non-shared copy of eMS

Immediate command command not
found
Explanation: The immediate command
name specified with CLEAR, STATUS,
or QUERY is not in effect.
System Action: RC = 44.
None.
User Response: None.

Conversational Monitor System (eMS) Messages

325

DMS
263E

Specified immediate command is
a nucleus extension and cannot
be cleared

Explanation: The user can discontinue
processing of the tape volume switch by
entering the immediate command
"CANCEL".
System Action: Execution continues.

System Action: RC = 48.
The specified immediate command is not
cleared.

User Response: If the user wants the
tape volume switching discontinued he
may do so by entering "CANCEL."

2671

System Action: Execution continues.
Operator Response: Do not mount the
tape.

2681

System Action: RC = 24.
The command is not loaded as a nucleus
extension.

Explanation: An end-of-volume
condition has been detected for the
specified FILEDEF and another tape
volume is required.
System Action: Execution continues.
User Response: None.

Message sent to userid userid:
message
Explanation: The message that follows
has been sent to the specified userid.

User Response: None.

Attempting to change tape
volume for DDNAME ddname

Tape mount for volume valid on
virtual nnn was canceled by the
user
Explanation: The user is requesting
that a tape mount be canceled.

command is not a valid command
to be established as a nucleus
extension by DMSLMX
Explanation: The bootstrap module
(DMSLMX) has been genmoded with a
command name which is not in its
internal table of valid commands to
nucxload.

2651

To cancel the tape volume switch,
type CANCEL

Explanation: The immediate command
name specified on IMMCMD CLEAR is
a nucleus extension and can only be
cleared with the NUCXDROP command
or NUCEXT CANCEL function.

User Response: Use the NUCXDROP
command or the NUCEXT CANCEL
function to clear the immediate
command.

264E

2661

System Action: System status remains
the same.

2691

Mount tape volume valid on
virtual nnn
{withlwithout} a write ring;
request number n
Explanation: A request has been made
for a different tape volume to be
mounted on tape drive nnn.
System Action: The user's system
waits until tape mounted.
Operator Response: Mount the
requested tape.

326

VM/SP System Messages and Codes

(

DMS
2701

Wait time for tape volume switch
has almost expired; to continue
waiting, type EXTEND

273E

Explanation: The tape volid was
checked and it does not match the
requested volid.

Explanation: The system is sti 11
waiting for the l'equp:-;ted tape to be
mounted and the time allotted to wait is
almost over.

System Action: The tape is rewound
and dismounted and execution of the
command continues.

System Action: Continues waiting for
the tape.

Operator Response: Mount the
requested tape volume.

User Response: To give the tape
operator additional time to mount the
tape, type 'EXTEND'.
274E
2711

Wait time for tape volume switch
has expired; tape volume switch
for volume valid on virtual nnn
canceled

System Action: The tape is rewound
and dismounted and execution of the
command continues.
User Response: Insert a write ring and
mount the tape.

System Action: Execution of command
terminates.

272E

Tape on virtual nnn, volume valid,
requires a write ring
Explanation: The tape was checked for
a write ring and it does not have one
although one was requested.

Explanation: The time allotted to wait
for the tape volume switch is over. The
request for the tape volume switch has
been canceled.

User Response: None.

Tape on virtual nnn is volume
valid--wrong tape

275E

Tape on virtual nnn is not a
standard label tape

Tape on virtual nnn, volume valid,
has
a write ring--no write ring was
requested
Explanation: The tape has a write ring
although no ring was requested.

Explanation: The tape label was
checked and it does not have an IBM
standard label.

System Action: The tape is rewound
and dismounted and execution of the
command continues.

User Response: Remove the write ring
and mount the tape.

Operator Response: Mount the
requested standard label tape.
276E

Invalid language id langid
Explanation: The language id·specified
was longer than five characters long.
(Five characters is the maximum for a
language id.)
System Action: RC = 24.

COTlv(:'rsational :Monitor System (eMS) Messages

327

DMS
Execution of the command terminates.
•
•

For LANGGEN, the DCSS is not
saved.
For SET LANGUAGE, the language
requested cannot be set and the
language setting remains
unchanged.

User Response: Correct the language
id and reissue the command. A list of
valid language ids for that virtual
machine is available from the QUERY
LANGLIST command.

277E

The ncss is located partially or
entirely inside the virtual
machine

set the language that CP was set to
before the language request failed.
If the requested language is not

available, you may have mistyped the
langid.
Otherwise, one of the following caused
the error:
•
•
•

•

the DCSS for the specified langid
was a non-language DCSS
the LOADSYS for the DCSS failed
the DCSS for the specified langid
did not contain DMS as an
application id
no virtual storage is left for a
LANGBLK to be allocated.

System Action: RC = 4 or 104.
Explanation: The virtual address of
the beginning of the DCSS is less than
the size of your virtual machine. The
virtual address of the end of the DCSS
mayor may not be less than the size of
your virtual machine.
System Action: RC = 88.
CMS does not allow a DCSS to be
loaded within the user's virtual
machine. This makes it impossible to
load the DCSS with the language
requested in it. The language setting
remains unchanged.
User Response: Use the CP DEFINE
command to decrease the size of your
virtual machine so that the virtual
address of the beginning of the DCSS is
greater than the size of your virtual
machine; then re-IPL CMS and reenter
the command.

If the message does not contain "forced

by CP ... ," the language that is forced is
either:
•
•

the original language (RC = 4), or
if the original language could not be
reset, the default language
(RC =104).

If the message does contain "forced by

CP ... ," the language remains unchanged,
and RC =4 or 104.
User Response:
If the message does not contain "forced

by CP, ... ," clear some storage or re-IPL.
If the requested language is not

available, issue the QUERY LANGLIST
to see the available languages.
If the message does contain "forced by

278E

{Unable to set requested
language: langid.1 The requested
language: langid is not available;}
[langid2 forced [[by CP) , condition
code code, return code rcll
Explanation: If the message contains
"forced by CP, ... ," CP could not set the
language that was requested; so, CMS

328

VM/SP System Messages and Codes

CP, .... " this is an installation error.
Notify the system administrator and
specify the condition code that was
issued with this message. The condition
code indicates the specific problem that
occurred; it is one of the following:
4

The DMKSNT entry for the
language specified does not exist.
The system programmer must
specify the appropriate

(

DMS
NAMELANG macro in DMKSNT
for this language.
8

)
I

System Action; RC = 28.
The addition of the application
LANGBLK stops. The DCSS (or system
information) for this application was not
added.

The volid specified in the
DMKSNT entry for the language
is not a CP-owned volume. The
system programmer must ensure a
CP-owned volume is specified in
the DMKSNT entry generated by
the NAMELANG macro for this
language.

The volid specified in the
DMKSNT entry for the language
is not mounted. The system
operator must ensure that the
appropriate volume is mounted.

A paging error occurred during
the set operation.

The DMKSNT entry for the
language was found; however, the
langid in this DMKSNT entry
does not match the langid in the
saved message repository. The
system programmer must ensure
that the NAMELANG entries do
not specify overlapping areas on
DASD.

User Response: If the applid was
entered incorrectly, then reissue the
command with the correct applid.
Otherwise, the application does not use
the NLS support provided by CMS.
You can make user additions to the
parser and synonym tables without the
SYSTEM information--just rename the
text files containing the SYSTErvI
information and load them as user
additions.

2791

279E

Explanation: The application specified
by 'applid' on the SET LANGUAGE
command does not have a language
segment in the DCSS. Options ADD and
ALL must have been specified for this
error to occur.
System Action: The application
LANGBLK is added, but only user
information is loaded.

The "MSGREP" identifier was
not found on the first page of the
requested message repository. CP
looks for this identifier to
determine if a valid message
repository is saved. The system
programmer must save the
appropriate CP message
repository.
No more virtual page buffers are
available.

Application applid not found in
the language ness
Explanation: The application specified
by 'applid' on the SET LANGUAGE
command does not have a language
segment in the DCSS. Options ADD and
SYSTEM must have been specified for
this error to occur.

Application applid not found in
the language ness

User Response: If the applid was
entered incorrectly, then reissue the
command with the correct applid.
Otherwise, there is no system
information stored in the language
DeSS for that application.

280E

Application applid not active
Explanation: A request was made for
an applid that was not active.
System Action: RC = 28 or RC = 26.
The request or command is ignored and
nothing is updated.
User Response: Verify that the
requested application is indeed correct
and make any necessary changes, or

Conversational Monitor System (eMS) Messages

329

DMS
verify whether SET LANGUAGE was
issued correct.ly for the requested
application.

281E

Application DMS cannot be
dpleted
Explanation: A Df~LETE request was
made for an appl1d of DMS with
SYSTEM or ALL specified. This is not
allowed since eMS must have the DMS
LANGBLK active at. all times.
System Action: RC ~7_ 24.
If ALL was specified, t.he user additions
to the parser tahle and message
repository are deleted; however, the
system information is not deleted.
User Response: None.

Error(8) occurred while creating
In {t {m; check In It 1m for details

2R2E

The name DeSS could not be
{foundlloadedlsaved}; [condition
code cc,] return code rc from
{FINDSYSILOADSYSISAVESYS}

283E

Explanation: This message was issued
for one of the following reasons:
•

If the condition code is 2 and the
return code is 44, then the DCSS has
not been defined on a NAMESYS
macro in CP/s System Name Table.
•

The DCSS name for FSTs was not
defjned in DMKSNT.

•

The specified DCSS was found, but
it could not be loaded.

•

The specified DCSS could not be
saved by the SA VESYS command.
You prohably do not have the
appropriate privilege class.

Explanation: One of the following
occurred:
1.

The control file for LANGMERG
had errors in it.
The fi1e(8) specified were not found,
or
Errors occurred while reading a file
that. was specified in the control file.

Examine the LANGMAP to see why
LANGMERG failed.
System Action: RC = 32.
Depending on when the error occurred,
the merge file mayor may not be
created. If the merge file is created,
however, it may be incomplete.
User Response: Examine the
LANGMERG map to see why the errors
occurred and determine whether they
are relevant to you. If so, correct the
errors and reissue the command.

330

VM/SP System Messages and Codes

The FINDSYS function (DIAGNOSE
code X'64') did not find the specified
DCSS.

See the Vi\! System Facilities for
Programming for a complete description
of the FINDSYS, LOADSYS, and
SA VESYS functions and their return
codes.
System Action: RC = 128.
Execution of the command terminates.
For LANGGEN, the DCSS and the CP
repository are not saved.
User Response: Respond according to
why the message was generated:
•

For SET LANGUAGE, if the langid
has been specified correctly, notify
your system administrator.

•

For LANGGEN. if the langid and
levelid have been specified correctly,
check to see that CP's System Name
Table properly specifies the DCSS
on the N Al\tlESYS macro.

DMS
•

For SA VEFD, define the DCSS for
FSTs and then reissue the SA VEFD
command.

•

If the return code was generated
from LOADSYS, refer to
DIAGNOSE code '64' in the VM

User Response: Examine the return
code. It should be one of the following:
Code

Meaning and Action

The DMKSNT entry for the
language specified does not
exist.

The volid specified in the
DMKSNT entry for the
language is not a CP-owned
volume.

The volid specified in the
DMKSNT entry for the
language is not mounted.
The operator must mount this
volume.

The repository is too large to
be saved in the area reserved
on DASD. The compiled
listing gives the number of
pages for the repository; the
NLSPGCT parameter in
NA1IELANG must specify a
page count greater than or
equal to that number.

A paging error occurred
during the save operation.

An error occurred while
attempting to write a page of
the repository to DASD.

The langid specified with the
DIAGNOSE does not match
the langid in the repository
you want to save. Either the
wrong text deck was loaded
into virtual storage. or the
wrong langid was specified on
the DIAGNOSE instruction.

The message repository is
invalid. The text loaded int.o
virtual storage to be saved is
not the message repository.

System Facilities for Programming
for details.
•

284E

If you do not have the appropriate
privilege class to issue SA VESYS,
contact your system administrator.

The ncss is not completely inside
the virtual machine.
Explanation: The command cannot
build the DCSS if any of it is outside the
virtual machine. It will build the DeSS
if the DCSS is completely within the
user's virtual machine.
System Action: RC = 88.
Execution of the command terminates:
the DCSS is not saved.
For LANGGEN, the DCSS and the CP
repository are not saved.

User Response: Use the CP DEFINE
command to redefine the virtual
machine so the DCSS is completely
inside your virtual machine. Then
re-IPL CMS and reissue the command.

285E

CP repository not saved;
condition code code, return code rc
Explanation: The CP message
repository was not saved.
System Action: RC = 104.
The execution of the command
continues, but the CP repository is not
saved.

Conversational Monitor System (eMS) Messages

331

DMS
2851

CP repository saved

System Action: RC = 40.
Execution of the command terminates;
the DCSS is not saved.

Explanation: The CP message
repository was successfully loaded and
saved.

User Response: Obtain CP privilege
class E or higher to save the DCSS. (Or
have your system administrator save the
DCCS.)

System Action: RC = O.
None.
User Response: None.
I

286E

288E

The DCSS is too small for the
data being stored

Explanation: During the DCSSGEN
procedure, you requested that the
Installation DCSS be saved or the
attempt to save it was automatic and
the SAVESYS failed. The DCSS was
not saved. A previous message should
have given the reason for the
unsuccessful save.

Explanation: The length of the data
being stored in the DCSS is greater than
the size of the DCSS.
System Action: RC = 40.
Execution of the command terminates;
the DCSS is not built.

System Action: RC = 40.
The Installation DCSS is not saved.

User Response: Change the size of the
DCSS as defined by the NAMESYS
macro in CP's System Name Table or
reduce the amount of data in the DCSS.

286W

System Action: Message
DMSEXG298R is issued.
User Response: Respond to message
DMSEXG298R to save the DCSS or to
cancel the DCSSGEN procedure.

287E

You must have a special privilege
class to successfully issue the
LANGGEN command
Explanation: LANGGEN issues a
SAVESYS command, which requires a
CP privilege class of E or higher.

332

User Response: Ensure that you have
the privilege class to issue the
SAVESYS command and verify that the
entry in the System Name Table
(DMKSNT) is correct. Refer to previous
message(s) to determine why the DCSS
was not saved.

The DCSS is too small for the
data being stored.
Explanation: The storage allocated for
the DCSS is not large enough to contain
all the EXECs requested in the load list
file provided for the DCSSGEN
procedure.

VM/SP System Messages and Codes

dcssname DCSS not saved.

2881

dcssname DCSS not saved
Explanation: During the DCSSGEN
procedure, you requested that the
Installation DCSS not be saved because
of errors encountered while creating it.
Or, the specified segment could not be
saved as the previous message indicated.
System Action: RC = 0, or the RC from
the previous message.
The DCSS is not saved.
User Response: If a previous message
was issued, take action accordingly.
Otherwise, none.

(

DMS
289E

The default language, langid,
must be active

292W

Explanation: The default language was
not set; it must be set to issue the
LANGGEN command.

Explanation: When the CP
information is to be saved, LANGGEN
loads the information at hexadecimal
location X'20000'. This may write over
data loaded there by the user.

System Action: RC = 104.
None.
User Response: Issue SET
LANGUAGE to the default language
named in the error message and then
reissue the LANGGEN command.

290E

System Action: Execution of the
command continues.
User Response: If only the CP
information is to be saved, ensure that
no program is residing at X'20000' when
LANGGEN is issued.

Duplicate applications specified in
control file fn ft fm
Explanation: The control file for
LANGGEN has two files with the same
first three characters in each filename.
Since these three characters determine
the application id, this is an error and
should be corrected.

293R

User Response: Correct the control
file and then reissue the LANGGEN
command.

System Action: If a response other
than those shown above is supplied, the
prompt is repeated until a response is
entered correctly.

Error occurred while loading the
DCSS

User Response: Enter "1," "YES," "0,"
"NO," or a null line.

Explanation: LANGGEN issued a
LOAD command to build the DCSS. An
error occurred during the execution of
this command.
294E
System Action: RC = 32.
Execution of the command terminates.
The DCSS is not saved.
User Response: Refer to the message
issued from the LOAD command.

Is this a DBCS language? Enter 1
(YES) or 0 (NO)
Explanation: This prompt asks
whether or not input and output data
should be treated as possible
Double-Byte Character Set (DBCS) data.
The answer to this prompt should be 1,
YES, 0, NO, or a null line; if you just
press the enter key (a null response)
then the default answer of 0 (NO) is
taken.

System Action: RC = 32.
The DCSS is not built. None.

291E

Text data will be loaded at
X'20000' in user area; user data
may be overwritten

Invalid language level id {levelidl;
reenter}
Explanation: A language level id may
be only one character, and it must
either be in the range A-Z or 0-9. If it
did not meet both of these requirements,
then the error message is given;
System Action: RC = 24.
The system waits for a response.

Conversational Monitor System (eMS) Messages

333

DMS
User Response: Specify the language
level id correctly and reissue the
command.

295R

297W

Explanation: DCSSGEN could not find
the execid requested in the load list file.

Language level id =

System Action: DCSSGEN continues
processing with the next entry in the
load list file. When processing
completes, message DMS298R is issued
to allow you to save the DCSS or to
cancel the DCSSGEN.

Explanation: The answer to this
prompt should be a single character in
either the A-Z or 0-9 range. This
character designates which level of
DCSS to load. The levelid is the third
character in the language DCSS name.
If there is a null response, the default is
character'S'
System Action: If the response to this
prompt is not in the A-Z or 0-9 ranges,
then the following error message is
displayed:

User Response: Delete or correct the
erroneous entry in the load list file, or
verify that the file requested resides on
one of the accessed disks.

298R

DMSINQ294E Invalid language level
id levelid; reenter

User Response: Enter a valid level id.

System Action: The system waits for a
response.

Should the installation segment
be used? Enter 1 (YES) or 0 (NO)

User Response: Based on the specific
error condition encountered, enter '1' if
you want to disregard the error(s) and
save the DCSS or enter '0' to discard the
DCSS.

Explanation: During CMS nucleus
generation, you can decide if you will
want to build the Installation
Discontiguous Shared Segment or omit
it.
System Action: The system waits for a
response. For a positive response,
message DMSINI310R is issued.
User Response: Enter 1 to build the
Installation Discontiguous Shared
Segment or enter 0 to omit it. A null
response defaults to 1 (YES).

An· error has been detected while
building the DCSS. Do you still
want the DCSS saved? Enter 1
(YES) or 0 (NO)
Explanation: The DCSSGEN
procedure encountered an error while
building the Installation DCSS. A
previous error message indicated a
specific error condition encountered.

The prompt is repeated until answered
correctly.

296R

Execid execid was not loaded

299E

Insufficient storage to complete
update
Explanation: The update is being
performed in storage but there is
insufficient storage to insert the next
update line.
System Action: RC = 41.
Execution of the command is
terminated. The system status remains
the same.
User Response: Issue the command
again. specifying NOSTOR on the

334

VM/SP System Messages and Codes

DMS
command line. This causes updates to
be performed on disk.

300E

no SYSaaa was specified with the DLBL
command. This message appears only if
the user is in the CMS/DOS
en vironmen t.

Insufficient storage to begin
update

System Action: RC = 24.
Execution of the command is
terminated. The definition does not
take effect.

Explanation: An update is being
performed in storage, but there is
insufficient storage available to contain
the entire input source file.
System Action: RC =4l.
If the keyword STOR was specified on
the command line, execution of the
command terminates. The system status
remains the same. If the keyword STOR
was not specified, the update continues
and is performed on disk. No RC = 41
is issued in this case.

User Response: Reissue the DLBL
command specifying a DOS logical unit
for each disk specified. In the case of
DTFCP, specify a DEV ADDR operand
with the DTFCP macro and with the
associated DLBL command.

303E

Explanation: A request was made for
LISTIO A or LISTIO UA, but no logical
units satisfied the request.

User Response: If RC = 41, issue the
command again, specifying NOSTOR in
the command line. This causes updates
to be performed on disk. Otherwise, no
action is necessary.

30lE

System Action: RC = 28.
Execution of the command is
terminated. The system status remains
the same, except when the EXEC option
was specified and there was an existing
$LISTIO EXEC file. In this case, the
$LISTIO EXEC file is erased.

SYSaaa not assigned for disk fm
Explanation: No ASSGN command
was issued prior to the DLBL command
associating the named DOS logical unit
with a CMS disk.
System Action: RC = 36.
Execution of the command is
terminated. The definition does not
take effect.
User Response: Issue an ASSGN
command for each of the DOS logical
units specified in the DLBL, and then
reissue the DLBL command.

No SYSXXX satisfies request

User Response: Ensure that the
correct request has been made.

304E

Invalid operand value value
Explanation: The value specified is not
valid for one of the following reasons:
•

It is larger than ten digits.

•
•

It is a nonnumeric value.
The number is greater than 231_1
for track numbers.
The number is greater than
999999 for BUFSP size.

•
302E

No SYSXXX operand
{entered Ispecified}
Explanation: No SYSaaa operand was
entered to associate the specified disk
mode with a DOS logical unit, or in the
case of DTFCP, the DEV ADDR operand
was missing from the DTFCP macro and

This message is also displayed if a null
line is entered as the first specification
for the EXTENT option of the DLBL
command.
System Action: RC = 24.

Conversational Monitor System (CMS) Messages

335

DMS

3041

Execution of the command is
terminated. The definition does not
take effect.

No new definition for the data set is
created. If one already exists, it
remains unchanged.

User Response: Reissue the command,
specifying the appropriate values for all
entries.

User Response: Either reissue the
DLBL command using a valid disk
mode, or issue "ASSGN SYSaaa IGN"
followed by the original DLBL command
using the DUMMY operand.

Update processing will be done
using disk
307E
Explanation: An update is being
performed in storage, and there is
insufficient storage available to contain
the entire input source file. The
keyword STOR was not specified on the
command line. The update processing
continues with the update being
performed on disk.

Explanation: The user catalog
'ddname' referenced by the CAT option
has not been defined by a previous
DLBL command.
System Action: RC = 24.
Execution of the command is
terminated. The definition does not
take effect.

System Action: The updating process
continues.

User Response: Reissue the command,
specifying the CAT option with a
previously defined ddname, or issue a
DLBL command for the user catalog
ddname and then reissue the DLBL
command for the subject data set.

User Response: None.

305E

Incomplete extent range
Explanation: Only the starting relative
track number was specified for an
extent range. The number of tracks
must also be specified.
System Action: RC = 24.
Execution of the command is
terminated. The definition does not
take effect.
User Response: Reissue the command
with the proper extent specifications
including the number of tracks.

SYSaaa not assigned for IGNORE

306E

Explanation: When the DUMMY
operand is used for a data set, the
logical unit address must have been
assigned with the IGN operand before
the DLBL command was issued.
System Action: RC = 36.

336

VMjSP System Messages and Codes

Catalog DDNAME ddname not
found

308E

mode disk in [non-]CMS
format--invalid for [non-]CMS
dataset
Explanation: The user has specified a
CMS fileid ("CMS fn ft") but references
a disk that is in non-CMS (for example,
OS or DOS) format. Or the user has
specified a non-CMS fileid ("DSN
datasetname") but references a CMS
disk. The references to disk include not
only the disk mode in the command line
but also the mode in MUL T and
EXTENT specifications. This message
is also issued if the user specifies CMS
for file identification but uses one of the
VSAM options (for example, CAT or
BUFSP) with it.
System Action: RC = 24.
The command is terminated with no
change to the current definition of

(

DMS
DLBL since thE' new definition does not
take effect.

311W

User Response: Reissue the command
with a disk mode appropriate for the
data set.

309W

Explanation: The user specified the
SAVESYS parameter, but did not
specify a name to save the system as.
System Action: Initialization will
continue, but the system will not be
saved.

CMSBATCH command ignored--it
is only valid when the NOSPROF
parameter was specified on the
IPL command

User Response: If you really want to
save the system, reissue the IPL
command, and specify a system name
with the SAVESYS parameter.

Explanation: The CMSBATCH
command was entered at the initial VM
READ and the NOSPROF parameter
was not specified on the IPL command.
!

312W

System Action: The command is
ignored, and not stacked for execution.

Language not generated - no text
decks specified in control file In It

User Response: To initialize a batch
machine:

310R

No system name specified; system
not saved

Reissue the IPL command with the
BATCH parameter, or

Explanation: No DCSS is built since
the LANGGEN control file does not
contain any text decks. (A control file
can contain just comments, but that will
not help to generate a language.)

Reissue the IPL command with the
NOSPROF parameter, then repeat
the original command at the VM
READ.

System Action: RC = O.
Execution of LANGGEN completes, but
no DCSS is built or no CP repository is
saved.
User Response: Specify at least one
text deck in the LANGGEN control file.

Installation segment name =
Explanation: During CMS nucleus
generation, you can name the
Installation Discontiguous Shared
Segment or accept the default name.
System Action: The system waits for a
response.
User Response: Enter a valid
Installation Segment name using one to
eight alphanumeric characters or press
enter to accept the default name.

313W

SYSPROF EXEC not found; notify
system administrator
Explanation: The SYSPROF EXEC file
was not found. Initialization is
completed by DMSINS instead.
System Action: CMS is operational,
but the SYSPROF EXEC has not been
executed.
User Response: Notify the system
administrator to place SYSPROF EXEC
in a DCSS, or on the S-disk or its
extension.

Conversatjonal Monitor System (eMS) Messages

337

DMS
314W

Automatic re-IPL by CP message

Explanation: User has been
automatically re-IPLed by CP after
the virtual machine loaded a
disabled wait PSW, identified by
psw.

Explanation: message is one of the
following:

•

; no information available
•
Explanation: The virtual machine
entered CP and was automatically
re-IPLed. An error occurred while
retrieving restart information from
CP, so the exact cause of entry into
CP is not available.

•

Explanation: A program interrupt
occurred at the address specified in
the virtual program new PSW while
the virtual machine was in basic
control mode.

due to translation exception
while in non-EC mode

System Action: User is automatically
re-IPLed by CP.

Explanation: The user has entered
CP because of a translation
exception while in non-EC mode.
Probable CP error.

User Response: None.

315W

•

due to a paging error

338

Conflicting parameters specified;
all parameters have been ignored

Explanation: An I/O error occurred
during paging which caused the
virtual machine to enter CPo
Probable hardware error.

Explanation: The user has coded
another CMS parameter on the IPL
command along with the SAVESYS
parameter.

due to external interrupt loop;
PSW psw

System Action: All parameters are
ignored.

Explanation: The user's virtual
machine external new PSW is
enabled for an interrupt condition
that will not be cleared upon
acceptance. It is possible to receive
an interrupt condition from the CPU
Timer and the TOD Clock
Comparator that produces this loop.

User Response: If the user wants to
save the system, reissue the IPL
command with the SAVESYS parameter
only.

; name-shared page hexloc altered
Explanation: The named system
was altered by the virtual machine.
Hexloc is the first changed page
detected by the control program.
The changed page was returned to
free storage. An attempt to issue
BEGIN failed, so the CMS system
was automatically re-IPLed.

•

due to program interrupt loop;
PSW psw

due to disabled wait; PSW psw

VM/SP System Messages and Codes

3201

Maximum number of disk entries
recorded
Explanation: The maximum number of
disks have been specified for a
multivolume VSAM data set. The
system (S) disk cannot be a user disk.
System Action: Execution of the
command is terminated and the data set
definition is stored.
User Response: None.

DMS
3211

Maximum number of extents
recorded

3241

Explanation: Sixteen (16) extents have
been specified for a VSAM data set.
This is the maximum number of data set
extents allowed.

No user defined
{DLBLIMULTIEXTENTIFILEDEFI
LABELDEF}s in effect
Explanation: No definition is in effect
for the requested DLBLs, FILEDEFs, or
LABELDEFs.

System Action: Execution of the
command is terminated successfully and
the data set definition is stored,
including the I6-extent specification.

System Action: No further action
occurs. The system is terminated.
User Response: None.

User Response: None.
325W

, 3221

DDNAME ddname not found; no
CLEAR executed

Explanation: This message is issued as
a result of a non-zero return code from
the PRINTL macro. Preceding this
message, a system message was issued
describing the nature of the problem.

Explanation: No previous definition
for 'ddname' had been specified. This
includes the condition of a DLBL
IJSYSUC CLEAR with no previous job
catalog ddname (IJSYSUC) defined.

3231

IDUMP for jobname terminated
due to error on OOE

System Action: Execution of the
command is terminated. All definitions
remain unchanged.

System Action: IDUMP is terminated
at the time that the error is encountered
on OOE. Control is returned to caller's
next sequential instruction with a
return code of 4 in register 15.

User Response: l£the ddname was
entered incorrectly, reissue the
command with the correct ddname.

User Response: Refer to the previous
error message issued and take
appropriate action.

{Job IMaster ILABELDEF' s I
FILEDEF's} catalog DLBL cleared
Explanation: The DLBL for the
catalog referred to has been cleared and
is no longer active.
System Action: If the ~JOB catalog is
cleared, all other definitions formerly
flagged as using the JOB catalog are no
longer flagged as such. The message
can be the result of a DLBL * CLEAR
rather than a DLBL IJSYSUC CLEAR
or DLBL IJSYSCT CLEAR, when the
PERM option is not used when defining
the catalogs.

326E

Illegal SVC sue (HEX xx) called
from ustor
Explanation: STXIT AB macro was
issued while you were in abnormal task
termination routine. It can only be
issued from your main program.
System Action: Your program is
terminated.
User Response: Remove the STXIT AB
macro from your termination routine
and assemble your program again.

User Response: None.

Conversational Monitor System (eMS) Messages

339

DMS
3271

The installation DCSS could not
be loaded

329W

Explanation: The INSTSEG value
specified on the IPL command is invalid.

Explanation: APL or TEXT characters
were received from the terminal but
SET APL and SET TEXT were off.

System Action: The IPL command
executes, but the Installation DeSS is
not accessed for this CMS session.
User Response: Check the name and
location of the Installation DCSS. If it
is located lower than your virtual
machine size, redefine your virtual
storage to a value below or equal to the
Installation DCSS. Re-issue the IPL
command.

327W

System Action: Any compound
characters are replaced by blanks.
User Response: SET APL or TEXT
ON.

330R

INSTSEG value omitted; no
shared EXECs loaded

System Action: Execution of the
command waits until you respond to the
specification request. If a null line is
the first response, an error message
(DMSDLB048E) is displayed and the
DLBL command has no effect.
Otherwise, a null response after one or
more lines of data signifies the end of
the specifications.

System Action: The IPL command
executes, but the Installation DCSS is
not accessed for this CMS session.

User Response: Enter data set volume
specifications either on one line
separated by commas or on separate
lines. The final comma at the end of the
line is optional and may be omitted.
You must enter the filemode and, in the
DOS environment, the DOS logical unit
associated with that disk. Do not repeat
the filemode specified in the command
line.

User Response: Check the name of the
Installation DCSS and re-IPL.

Control file not specified
Explanation: A control file was not
specified on the VMFNLS command.
This control file must be specified, since
it is used to apply updates to the source
file before text is generated.
331R

System Action: RC = 24.
Processing of the VMFNLS command
stops.
User Response: Specify a control file
when you invoke the VMFNLS
command.
Refer to the VM/SP Installation Guide
for more information on VMFNLS.

340

VM/SP System Messages and Codes

Enter volume specifications:
Explanation: The system expects you
to enter the VSAM data set volume
specifications because you specified the
MULT option.

Explanation: The INSTSEG value on
the IPL command was missing. The
Installation DCSS (Discontiguous
Shared Segment) is not accessed for this
eMS session.

328E

Warning: APL/TEXT option not
in effect.

Enter extent specifications:
Explanation: The system expects you
to enter the. VSAM data set extents
because you specified the EXTENT
option with the DLBL command.
System Action: Execution of the
command waits until you respond to the
specification request. If a null line is
the first response, an error message

DMS
User Response: If user information
was supposed to t.e loaded, make sure
that the filenames and filetypes of the
user addition files are correct. The
filename should be applid concatenated
with UME, UPA or USY. The filetype
should be TXT concatenated with the
current langid.

(DM:SDLB304E) is displayed and the
DLBL command has no effect.
Otherwise, a null line means the end of
the specifications.
User Response: Enter dataset extent
specifications on the same line
separated by commas or on separate
lines with or without commas. You
must enter the starting relative track
number, number of tracks, filemode and,
if in DOS environment, the DOS logical
unit associated with that filemode. The
extents must be in ascending order for
each volume grouping in order for the
command to execute properly.

! I 332E

333E

Explanation: The specified number of
bytes exceeds the size of the largest
partition possible with this virtual
machine.

No user additions were loaded

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same. The old DOS partition size
remains unchanged.

Explanation: The SET LANGUAGE
command was issued with the "ADD
applid USER" option specified.
However, no user message text file, user
parser, or user synonym table was
found.

User Response: Specify a smaller
value. If the partition size is not an
important factor in this particular
session, issue SET DOSPART OFF and
allow the system to compute its own
partition size.

System Action: RC = 28.
No user information was loaded. The
system status remains the same.
User Response: Make sure that the
filenames and filetypes of your user
addition files are correct. The filename
should be applid concatenated with
UME, UPA or USY. The filetype
should be TXT concatenated with the
current langid.

3321

No user additions were loaded
Explanation: The SET LANGUAGE
command was issued with the"ADD
applid SYSTEM" option specified.
However, no user message text file, user
parser, or user synonym table was
found.
System Action: No user information
was loaded. However, system
information was found and loaded.

nnnnnK partition too large for
this virtual machine

334E

No system information or user
additions were found for
application applid
Explanation: The application specified
by applid on the SET LANGUAGE
command does not have a language
segment in the language DCSS, and
there are no user addition files with
applid as the first three characters of
the filename. The ADD and ALL
options must have been specified for
this error' to occur.
System Action: RC = 28.
The addition of the application
LANGBLK stops. No system
information or user additions for this
application are added.
User Response: If the applid was
entered incorrectly, then reissue the

Conversational Monitor System (eMS) Messages

341

DMS
command with the correct applid.
Otherwise. the application does not use
the NLS support provided by CMS.

Code Meaning
04
The 'libname' specified does
not exist. Reissue the the
command with a valid
'libname'.
08
The 'libname' is currently
active on a real 3800. DRAIN
the 3800 and reissue the
command.
12
The library containing the
volid is CP-owned. Consult
your system programmer for an
explanation.
16
The library containing the
volid is not currently mounted.
Have the operator mount the
volume. Then reissue the
command.
24
A paging error occurred.
Consult your system
programmer.

You can make user additions to the
parser, synonym, and message tables
without SYSTEM information. Rename
the text files containing the system
information and load them as user
additions.

346E

Error [nn] loading {{n {tluser In}
from disk
Explanation: The TEXT file specified
in a modname caused an error while
trying to LOAD it into user virtual
storage. For SET LANGUAGE, an
error occurred while attempting to load
a user addition to the parser or message
repository.
System Action: RC = 6.
None.
For SET LANGUAGE, RC=32.
The file is not loaded, but all other
program execution continues.

User Response: Fix the TEXT file so
that it does not cause a loading error
and reissue the command.
For SET LANGUAGE, depending on the
error code indicated, you can try to
correct the error encountered during
the LOAD.

347E

Error nn loading library libname
Explanation: A return code of 'nn' was
received from DIAGNOSE code X'74'
when trying to load the Named System
into user virtual storage.
System Action: RC = 100 + 'nn'
None.
User Response: The action taken
depends on 'nn' as follows:

342

VM/SP System Messages and Codes

348E

Error nn saving library libname
Explanation: A return code of 'nn' was
received from DIAGNOSE code X'74'
when trying to save the new version of
the named system from user virtual
storage.
System Action: RC = 200 + 'nn'
None.
User Response: The action taken
depends on 'nn' as follows:
Code Meaning
04
The 'libname' specified does
not exist. Reissue the
command with a valid
'libname'.
08
The 'libname' is currently
active on a real 3800. DRAIN
the 3800 and then reissue the
command.
12
The library containing the
volid is CP-owned. Consult
your system programmer- for an
explanation.

DMS
16

349E

The library containing the
volid is not currently mounted.
Have the operator mount the
volume. Then reissue the
command.
The space allocated by the
installation for 'libname' is not
large enough to accommodate
its new size after processing by
this command. Either use the
DEL function to delete some
modnames or have the
installation allocate a larger
area for 'libname'. Then
reissue the command.
A paging error occurred.
Consult the system
programmer.

351E

Module is marked Only Loadable
Explanation: The module was marked
only loadable by the linkage editor, but
an attempt was made to execute the
program.
System Action: RC = 12 or Abend
code = 15A.
Execution of the program terminates.
(Abend code = 15A for LINK, ATTACH,
or XCTL; RC = 12 for OSRUN.)
User Response: Make sure that the
name is correct. If so, determine why
the program was made only loadable by
the linkage editor. Link edit, an
executable version of the program and
re-execute the job stream or reissue the
OSRUN command.

Invalid library libname
Explanation: The first directory entry
in 'libname' was not the name of the
library itself. The named system was
improperly formatted on the DASD.

352E

Invalid SETPRT data in file

in it

Explanation: The SETPRT module
represented by 'fn ft' does not contain
valid SETPRT information.

System Action: None.
System Action: All output to the
virtual 8800 has been performed until
invalid SETPRT module was
encountered.

User Response: The named system had
either not been created before or was
destroyed since it was last modified.
Use the GEN function to create a new
library called 'libname' and then build it
using the ADD function.

350E

User Response: Find out why the
particular module caused the above
error. Most likely, the module in
question was not created with the CMS
GENIMAGE command. In any case,
close the virtual 3800 with the PURGE
option. Either use a different module or
fix the module that caused the error and
reissue the SETPRT command.

Module is marked Not Executable
Explanation: The module was marked
not executable by the linkage editor, but
an attempt was made to execute the
program.
System Action: RC _co, 4 or Abend
code = 15A.
Execution of the program is terminated.
(Abend code =--=-15A for LINK, ATTACH,
or XCTL; RC=4 for OSRUN.)
User Response: Link edit an
executable version of the program and
re-execute the job stream or reissue the
OSRUN command.

353E

No previous HELP command has
been entered. Please enter HELP
MOREHELP for information on
the MOREHELP command.
Explanation: The user entered the
MOREHELP command and a HELP
command had not been previously
entered.

ConvPl'sationaJ Monitor System (eMS) Messages

343

DMS
System Action: Re·= 4.
Processing is terminated.
User Response: The user should enter
the HELP command desired.

354E

RELATED information is not
available for the last HELP
command entered
Explanation: The user entered the
MOREHELP command with the
RELATED option specified, and there is
not a RELATED section in the HELP
file.
System Action: RC = 32.
Processing is terminated.
User Response: None.

3551

For related information on this
subject, enter MOREHELP
(RELATED.
Explanation: A section of a HELP file
other than RELATED was displayed and
a RELATED section exists within that
file.
System Action: RC = o.
None.
User Response: If the user wants to
display the related section of the file,
the specified command should be
entered.

360E

Invalid response response
Explanation: After prompting you for
information, VSAMGEN/SAMGEN
determined that your reply was invalid,
either because you did not enter one of
the choices given you in the prompting
message or because you entered a value
not valid for the entry being processed
(that is, the storage location of the
named system).
If the message is issued after the storage
location value is entered, the value
violates one of the following rules:

•
•
•

Must be a valid hexadecimal value.
Must be less than 16 megabytes.
Must be greater than X'20000'.

For DCSSGEN, the Installation segment
name you entered contains blanks.
For IT ASK, when asked if you wanted
the HELP files uppercased, your
response was not YES, NO, or a suitable
abbreviation.
System Action: RC = 24.
If this is the first time this message is
issued for this prompt, VSAMGEN reads
from the terminal after issuing the
message, thereby giving you another
chance to enter the correct information.
If it is issued·for the second time for the
same prompt, VSAMGEN terminates,
and the system returns to the CMS
command environment.
For DCSSGEN, the system reissues
DMSINI310R.

3561

For more detail on this subject,
enter MOREHELP.
Explanation: A BRIEF section of a
HELP file was displayed and there is
more detail available.
System Action: RC =
None.

User Response: If the user wants more
detail, the specified command should be
entered.

344

VM/SP System Messages and Codes

User Response: If it is the first time
the message is issued, reexamine the
prompting message and enter the
correct information. If it is the second
time the message is issued for this
prompt, VSAMGEN has terminated, so
you must restart the VSAMGEN EXEC.
If the message is from SAMGEN, the
EXEC must be restarted.
For ITASK, reply YES or NO to the
prompt when it is repeated.

DMS
361E

Disk mode[(vdev)] is not a
{CMSIDOS} disk

3621

Explanation: VSAMGEN is in the
process of link-editing the modules that
make up the named system in order to
create a CMS DOSLIB file with the
same name.

Explanation: VSAMGEN requires that
the A-disk be a read/write CMS disk,
and that the disk you specified as
containing the DOS SRL be a DOS disk.
For DMSUPD the OUTMODE option on
the UPDATE command specified a
filemode that was not a read/write CMS
disk.
System Action: RC = 36.
VSAMGEN has terminated. The system
returns to CMS command mode. For
DMSUPD the UPDATE command is
terminated.

LINK-EDITING sysname ...

System Action: None.
User Response: None.

363E

Invalid starting address vstor
Explanation: The start address
specified in the command line is not a
hexadecimal address within the load
range of the specified system.

User Response: If the message
concerns the CMS A-disk, access a CMS
disk in read/write mode as the A-disk
and reissue VSAMGEN. If the message
concerns the DOS disk, either access
the DOS disk and use that mode letter
to answer the prompt during the next
VSAMGEN attempt, or enter the
correct mode of the DOS disk
containing the DOS SRL during the
next VSAMGEN attempt.

System Action: RC = 24.
Execu tion of the command is
terminated. The system status remains
the same.
User Response: Reissue the command
with a valid starting address.

3631

For DMSUPD, reinvoke the UPDATE
command specifying a filemode of a
CMS disk in read/write mode.
Alternatively, the 'OUTMODE' option
can be eliminated allowing UPDATE to
choose the filemode of the output files.
Refer~nce the UPDATE command for
more details.

sysname DOSLIB created on
A-disk

Explanation: VSAMGEN creates a
CMS DOSLIB file from the object
modules that make up the named
system.
System Action: None.
User Response: None.

362E

Invalid storage protect key key
Explanation: The storage protect key
specified was not decimal, 0 to 15.
System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the command,
specifying a valid storage protect key.

363R

Enter location where sysname will
be loaded and saved:
Explanation: VSAMGEN/SAMGEN
requires a hexadecimal address for
fetching the VSAM and/or Access
Method Services systems into storage so
that the systems can be saved on a CP
volume.

Conversational Monitor System (CMS) Messages

345

DMS
System Action: VSAMGEN/SAMGEN
issues a read to the terminal and waits
for your response.

364R

Explanation: The message gives you
the choice of regenerating either one or
both of the named systems.

User Response: Enter the hexadecimal
address corresponding to the starting
relative page number in the
SYSPGNUM field of the NAMESYS
macro entered in the DMKSNT module
for the :named system.

364E

System Action: VSAMGEN issues a
read to the terminal and waits for your
response.
User Response: Enter a valid response.

VM storage not large enough to
contain system loading at vstor 1
to vstor2
365E
Explanation: The virtual machine's
storage must be large enough to allow
SSK instructions to be issued for the
complete load range of the saved system.

3641

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the command
with a valid system name.

3651

System Action: None.
User Response: None.

System sysname saved
Explanation: VSAMGENjSAMGEN
saves the named system on a CP volume
for subsequent use by user programs.

FETCHING sysname ...
Explanation: VSAMGEN is in the
process of fetching the phases that make
up the nameq system from the CMS
DOSLIB file of the same name. The
phases are fetched into storage in order
to be saved (written) on a CP volume.

System name not specified
Explanation: The system name was not
included in the command line.

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Use the CP command
DEFINE to redefine the virtual
machine's storage to a value large
enough to contain the saved system, and
IPL CMS again.

ENTER 'CMSVSAM', 'CMSAMS'
OR BOTH FOR GENERATION OF
NEW SYSTEM(S)

System Action: None.
User Response: None.

365R

One or more of the text files listed
in the in EXEC are missing. The
VSAM PP PID tape should be on
tape drive 181. Enter GO if tape
drive is ready to LOAD FILE or
QUIT.
Explanation: VSAMGEN has detected
one or more of the VSAM files
necessary to generate VSAM/ AMS is
missing. VSAMGEN expects the VSAM
PP tape to be mounted on drive 181.
System Action: None.

346

VM/SP System Messages and Codes

DMS
User Response: Enter the appropriate
response.

VSAM or Access Method Services
system.
System Action: None.

3661

Starting to read PTF decks from
reader ...
Explanation: VSAMGEN is starting
the 'UPDATE' procedure, during which
the user is prompted for the names of
the PTF decks to be applied to the new
system.

User Response: None.

367R

Explanation: You must supply the
ddname of the tape input or output data
sets to be used in the Access Method
Services jobstream. The ddname in
each case must match the "ddname"
operand in the Access Method Services
control statement being executed
(EXPORT, IMPORT, or REPRO).

System Action: None.
User Response: None.

366R

Enter name of system to be
saved:
Explanation: VSAMGEN has
link-edited the VSAM or Access lVlethod
Services system and fetched it into
virtual storage and is about to issue the
CP SA VESYS command for that system.
For SAMGEN, the simulated VSE/AF
SAM modules have been fetched into
storage and SAMGEN is about to issue
the CP SA VESYS command for the
CMSBAM DCSS.

Enter tape {inputloutput}
DDNAMEs:

System Action: The system waits for a
response.
User Response: Enter the ddname of
the tape input or output data sets to be
used.

3681

nn modules have been restored

Explanation: VMFDOS issues this
informational message to indicate to the
user the number of modules created on
disk from a VSE/AF distribution tape.

System Action: The system waits for a
response.

System Action: None.

User Response: Enter the name of the
system to be saved.

User Response: None.

3671

module TEXT written on A-disk
368R
Explanation: If the message was issued
by DMSVGN, VSAMGEN has read a
reader file and written it on the CMS
disk with the given name. The file is
used in creating a new named system.
If the message was issued by DMSVPD;
DMSVPD (called from VSAMGEN
EXEC) has read the named replacement
module from the DOS/VS PTF tape and
has written it on the user's A-disk for
subsequent application in the new

Erase sysname DOSLIB? (Enter
YES or NO)
Explanation: The CMS DOSLIB file
created during execution of the
VSAMGEN EXEC (see message
DMSVGN363I) can be erased at this
time. This message prompts you to
indicate whether or not you want the
file erased.
System Action: The system waits for a
response.

Conversational Monitor System (eMS) Messages

347

DMS
User Response: Enter either "yes" or
"no." Only the "yes" response will erase
the file.

370R

372E

Explanation: An EXPAND control
record was not in the correct format due
to one of the following:

ENTER 'GO' IF SAVED SYSTEM
IS TO BE CREATED,
OTHERWISE ENTER 'QUIT'
Explanation: The VSAMGEN EXEC
has created the specified DOSLIB as
stated in message DMSVGN363I and
now requires whether it is to continue
processing the DOSLIB or is to be
terminated.

371R

The first word on the record was not
'EXPAND'

•

The user did not format the CSECT
names and expansion sizes properly.

User Response: Fix the control record
and reissue the command.

373E

Control section csect does not exist
Explanation: The name that the
CSECT option specified for the
EXP AND command or the name on the
EXP AND control card is not the name
of a control section in the text file that
is being expanded.

sysname IS LOADED, IF ZAPS
ARE TO BE APPLIED GO 'CP'
MODE, APPLY THE ZAPS AND
THEN REPLY 'GO'.

System Action: RC = 32
The system stops executing the
command. System status stays the
same.

Explanation: It is possible at this point
to apply ZAPs to the loaded system by
entering CP mode. All text is now in
storage and the DISPLAY and STORE
commands may be used to make
changes.

User Response: Check the spelling of
the name that you specified. Make sure
it is the name of a label on a CSECT or
ST ART statement. Reissue the
command.

System Action: VSAMGEN issues a
read to the terminal and waits for a
response.
User Response: If ZAPs are desired,
enter CP mode. Make the desired
changes, return to CMS READ via
BEGIN command. Enter null line to
cause the VSAMGEN to continue.

•

System Action: RC = 32.
The system displays the invalid record
and stops the command immediately.
The system status stays the same.

System Action: The system waits for a
response.
User Response: If you desire to
temporarily halt the creation of the
saved system, enter 'QUIT'; if 'GO' is
entered, the saved system will be built.

Invalid EXPAND control card

374W

Zero-length CSECT csect
encountered
Explanation: The control section that
you specified has an ESD entry that
specifies zero for the length, and a
non-zero length is not specified on the
END record.
System Action: RC=4.
The system sets the length to zero and
processing continues.

348

VM/SP System Messages and Codes

(

DMS
User Response: Make sure that the
specified control section is actually zero
in length. If not, fix the problem and
reissue the command.

3751

383R

Apply in? (Enter NO or EOB)
Explanation: The user has requested
selection of PTF replacement modules
during VMFDOS execution.

nnnn (HEX xxxx) bytes at an offset
of +xxxxxxx into CSECT csect have
been added

System Action: The system waits for a
response.
User Response: If you do not want to
apply the PTF contained in the named
file, enter "no." If you do want the file,
indicate an EOB by pressing ENTER on
a 3277 display terminal or RETURN on
a 2741 terminal.

Explanation: The system successfully
expanded the specified control section.
The effective expansion length is in
decimal and hexadecimal. The offset is
in hexadecimal.
System Action: Processing continues.
384E

Missing modifier keyword(s)

User Response: None.

3761

Explanation: One or more keywords
were missing from the command
according to the syntax definition on
the invocation of this command.
Modifier keywords are defined with the
KW .n DLCS statement.

EXP AND processing complete
Explanation: All EXPAND control
records have been processed.
System Action: For the EXPAND
command, control returns to CMS. For
the ZAPTEXT command, the system
processes any remaining ZAP control
records.

System Action: RC = 24.
The command is not executed.
User Response: Add the missing
keywords and issue the command again.

User Response: None.
385E
382R

Enter number of tape files to be
processed:
Explanation: VSAMGEN must know
how many PTF tape files to scan for the
VSAM and Access Method Services
replacement modules.
System Action: The system waits for a
response.
User Response: Enter a decimal
number showing the number of tape
files to be processed starting with
current tape position.

Invalid modifier keyword:
keyword
Explanation: Keyword keyword is
invalid on the invocation of this
command. Modifier keywords are
defined with the KW .n DLCS
statement.
System Action: RC = 24.
The command is not executed.
User Response: Correct the invalid
keyword and issue the command again.

Conversational Monitor System (CMS) Messages

349

DMS
386E

Missing operand(s)

390E

Explanation: One or more operands
were missing on the invocation of this
command.

System Action: RC=24.
The command is not executed.

User Response: Add the proper
operands and issue the command again.

388E

Missing valuetype for operand
operand

User Response: Correct the invalid
value and issue the command again.

391E

Explanation: The operands operands
should not appear where they do on the
invocation of this command.

System Action: RC=24.
The command is not executed.

System Action: RC = 24.
The command is not executed.

User Response: Add the proper value
and issue the command again.

User Response: Remove the
unexpected operands and issue the
command again.

Invalid keyword: keyword
393E

Missing valuetype for option option
Explanation: The option's associated
value is missing on the invocation of
this command.

System Action: RC=24.
The command is not executed.

User Response: Correct the invalid
keyword and issue the command again.

User Response: Add the proper value
and issue the command again.

Invalid operandtype: operand
394E
Explanation: The operand is not valid
on the invocation of this command.
System Action: RC = 24.
The command is not executed.
User Response: Correct the operand
and issue the command again.

350

Unexpected operand(s): operands

Explanation: The operand's associated
value is missing on the invocation of
this command.

Explanation: The keyword keyword is
invalid on the invocation of this
command.

389E

VM/SP System Messages and Codes

Explanation: The operand's associated
value is invalid on the invocation of this
command.

System Action: RC = 24.
The command is not executed.

387E

Invalid valuetype value for operand
operand

Invalid option: option
Explanation: The option given on the
invocation of this command is not valid.
System Action: RC = 24.
The command is not executed.
User Response: Correct the option and
issue the command again.

DMS
395E

Invalid valuetype value for option
option

399E

Explanation: The option's associated
value is invalid on the invocation of this
command.

Too many tags or tag too long for
nickname in userid NAMES file.
Explanation: One of the following
conditions has occurred.
•

The information from the use rid
NAMES file that was stacked was
truncated. The stack has a limit of
255 characters.

•

While searching the NAMES file, an
entry was encountered that
contained more than 64 tags
(overflowing the internal tag tables
of the NAME FIND command). This
record was not processed correctly
by NAMEFIND.

System Action: RC = 24.
The command is not executed.
User Response: Correct the invalid
value and issue the command again.

396E

Maximum number of command
table entries exceeded
Explanation: The maximum number of
syntax entries in the command table is
268,345,455.

System Action: RC = 88.
Processing is terminated.

System Action: RC = 32.
Conversion stops.

User Response: Check the nickname
entry in ~he use rid NAMES file making
sure that each tag value is a maximum
of 255 characters long, and that the
:nick entry contains a maximum of 64
tags.

User Response: Decrease entries in the
table by splitting into user and system
tables or move them into additional
application tables.

397E

User validation function name not
found
Explanation: The user validation
function name is required to validate
the syntax of the command issued, and
it could not be found.
System Action: RC = 28.
The command is not executed.
User Response: Be sure that the
function is specified correctly in your
DLCS file. NUCXLOAD the function to
make it available, and then issue the
command again.

400S

System sysname does not exist
Explanation: The subject system has
not been defined in the Control Program
module DMKSNT.
System Action: For DMSVIB, CMS
abends with abend code X'044'. For all
other modules, RC = 44. Execution of
the user program is terminated. The
system returns to the state it was in
before the start of the user program.
User Response: Contact the system
programmer, who will generate the
saved system for the correct system
name.

Conversational Monitor System (CMS) Messages

351

DMS
401S

VM size [(size)] cannot exceed
{sysname Isegment} start address

402W

{(vstor)l(hex address)}

Explanation: The DMSLBR module,
that simulates the macros necessary to
run the ESERV program, could not be
found.

Explanation: The user's virtual
machine storage size as currently
defined is of such a size that the named
system (when loaded) would overlay
part of the user's virtual storage. This
could have occurred in one of the
following ways:
1.

System Action: System operation
continues but support for ESERV
command execution is not available.

The named system was saved below
the user's current virtual machine
size, or
The named system was saved at an
appropriate address, but the user's
current virtual machine storage size
is so large that it would be partially
over laid by the named system.

DMSLBR not in CMSBAM
segment; ESERV support not
available

User Response: If you require the use
of the ESERV command, contact your
system support personnel.

403S

CMSBAM shared segment not
available; reload CMSDOS
Explanation: An OPEN has been
issued for a file that resides on an
FB-512 DASD, but the CMSBAM shared
segment has not been generated.

The address for the saved segment
should be higher than the end of the
virtual machine address.

System Action: The OPEN is
canceled. System status remains the
same.

System Action: For DMSVIB, CMS
abends with an abend code of X'104'.
For DMSSET and DMSSFD, RC=40.
For all other modules, RC = 104.
Execution of the command is
terminated. The system status remains
the same.

User Response: The CMSBAM shared
segment must be generated and saved
with the VSAMPP EXEC and the SET
DOS ON command reissued.

User Response: Respond in one of the
following ways:
404S
1.

352

Contact the system programmer,
who must create a new copy of the
named VSAM or Access Method
Services system at an address that is
high enough not to conflict with any
virtual machine size permitted for
VSAM users, or
Enter CP mode and define a smaller
virtual machine storage size for this
VSAM user so his virtual storage is
not overlaid by the named system,
and then reload (via IPL) CMS/DOS.
Define storage for the virtual
machine less than the address of the
segment.

VM/SP System Messages and Codes

Logic module fn not found in
CMSBAM segment
Explanation: An OPEN has been
issued for a file residing on an FB-512
DASD but the appropriate logic could
not be located. This indicates that the
CMSBAM shared segment has been
generated incorrectly.
System Action: The OPEN is
canceled. System status remains the
same.
User Response: Have the system
programmer examine the CMSBAM

DMS
linkage editor map for unresolved
external references. The modules that
are unresolved must be obtained from
the DOS/VS PID tape and VSAMPP
EXEC must be rerun to generate the
CMSBAM shared segment.

User Response: Correct the XMITMSG
command and reissue it.

4091

Loading fn ft to userid vdev
Explanation: A named tape file is
being loaded to the specified minidisk.

405E

Invalid or missing message
number

System Action: The SPLOAD program
formats the minidisk if necessary,
positions the tape, and loads the
contents of the tape file to the indicated
minidisk. The tape file location and
destination are determined from the
SPLOAD PROFILE.

Explanation: The message number was
either not specified, was not numeric, or
was greater than 9999.
For DMSWMS, the VMFMSGS EXEC
was invoked incorrectly.

I
I

User Response: None.
System Action: RC = 24.

User Response: Correct the command
and retry.

410S

For DMSWMS, you should not invoke
the VMFMSGS EXEC, either as a
command or f.rom a user written
program.

407E

Explanation: An unexpected error
occurred while the Control Program was
processing a request from CMS to find
or load the specified saved system.
System Action: For DMSVIB, CMS
abends with abend code X'177'. For
other modules, RC = 177. In both
cases, 177 is the actual error code from
the Control Program, indicating that
paging I/O errors have occurred. The
QUERY SYSNAMES command displays
the names of the saved segments for the
CMS virtual machine. Any requested
segment must have been saved via
procedures documented in the VM/ SP
Installation Guide.

Invalid unique ID uniqueid
Explanation: The uniqueid provided to
P ARSECMD is invalid.
System Action: RC = 24.
The command is not executed.
User Response: The uniqueid is longer
than 16 characters. Make sure it is not
longer that 16 characters and issue the
command again.

408E

Control program error indication
xxx

User Response: Contact the
installation system programmer for
assistance.

Number of substitutions exceeds
20

Explanation: There were too many
substitutions specified; only 20
substitutions are permitted with
XMITMSG.
System Action: RC = 24.

411S

{lnputIOutput} error code nn on
SYSaaa
Explanation: An unrecoverable input
or output error occurred while reading
from or writing to SYSaaa. SYSaaa is
the card reader, the printer, a tape
drive, or the logical unit assigned to the

Conversational Monitor System (eMS) Messages

353

DMS
specified OS- or DOS-formatted disk.
The 'nn' code indicates the nature of the
error; it may be one of the following:

Execution of the command is
terminated. The system status remains
the same.

CARD READER

User Response: A message was
by DMSSSK before this message
issued. Use the explanation and
action for the DMSSSK message
correct the error.

Code

Meaning

An unknown error occurred.

issued
was
user
to

PRINTER
413S
Code

Meaning

1
5

A line was too long.
An unknown error occurred.

Explanation: The program has issued a
CDLOAD (SVC 65), but the DOS VSAM
environment under CMS is not active.
A CDLOAD requires VSAM storage
initialization to have taken place, but
this has not been done.

TAPE INPUT AND OUTPUT
Code

Meaning

A permanent I/O error
occurred.

Storage not initialized for VSAM
processing

System Action: RC = 104.
The job is terminated. The system
status remains the same.

DISK INPUT AND OUTPUT
Code

Meaning

2
3

A unit exception occurred.
A wrong-length record was
detected.
A permanent I/O error
occurred. (For disk output, this
error could be caused by full
disk space.)

System Action: RC = 100.
Execution of the command is
terminated.
U set Response: Use the error code to
determine and correct the possible cause
of error.

412S

DOSGEN FAILED DUE TO
SETKEY ERRORS
Explanation: Errors occurred while
trying to issue the SETKEY command
to set storage keys.
System Action: RC = 100.

354

VM/SP System Messages and Codes

User Response: Issue the CMS
command SET DOS ON with the VSAM
option in order to initialize storage
properly, and then reexecute the
program.

414E

Execid exec name exectype already in
storage
Explanation: The EXECLOAD
command cannot be executed because
an EXEC with the same execid is
already storage resident.
System Action: RC = 1.
Execution of the EXECLOAD command
is terminated. The system status
remains the same.
User Response: Either EXECDROP
the storage resident EXEC and reissue
the EXECLOAD command or reissue the
EXECLOAD command specifying the
PUSH option.

(
"-

DMS
415E

Invalid character char in execid
exec name exec type

417E

Explanation: The execname or
exectype of the execid contains an
invalid character. The following
characters are invalid: '=', '*', '(', ')',
and X'FF'.

Explanation: An EXECLOAD
command was issued for an EXEC file
that was not an EXEC 2 or System
Product Interpreter EXEC.

System Action: RC = 20.

System Action: RC = 4.

The execution of the command is
terminated. The system status remains
the same.

The EXEC file was not loaded and the
command execution was terminated.
User Response: If this EXEC is to be
storage resident, it must be converted to
an EXEC 2 or System Product
Interpreter EXEC.

User Response: Correct the execid
specified and reissue the command.

415W

Invalid character char in execid
exec name exec type

417W

Explanation: The execname or
exectype of the execid contains an
invalid character. The following
characters are invalid: '=', '*', ')', '("
and X'FF'.

System Action: The EXEC is not
loaded into the DCSS, the error is
recorded in the DCSS 'dcssname
DCSSMAP' file, and a prompt
(DMS298R) is issued asking if you want
to save the DCSS.

User Response: Correct the DCSSGEN
load list entry that caused the error.

There are no execname exec type
{SYSTEM I[or]USERI [or]SHARED}
EXECs storage resident.
Explanation: The EXECDROP or
EXECMAP command was issued and
there were no EXECs of the specified
category resident in storage.
System Action: RC = 28.

Only EXEC 2 and REXX EXECs
are supported as storage resident
EXECs
Explanation: Only EXEC 2 and REXX
EXECs can be loaded into the
Installation Discontiguous Shared
Segment (DCSS).

System Action: The EXEC is not
loaded into the DCSS, the error is
recorded in the DCSS 'dcssname
DCSSMAP' file, and a prompt
(DMS298R) is issued asking if you want
to save the DCSS.

416W

Only EXEC-2 and REXX EXECs
are supported as storage resident
EXECs

User Response: Correct the DCSSGEN
load list entry that caused the error.

418W

Drop pending for exec name exec type
Explanation: An EXECDROP
command was issued for an EXEC file
that is currently active.
Systenl Action: RC = 4.
The EXEC will be dropped when the
EXEC procedure completes.

User Response: None.
User Response: None.

Conversational Monitor System (CMS) Messages

355

DMS
419E

In It has an error with

that has HDR1 labels but is not
positioned correctly for input label
processing.

quote/comment nesting. {A quote
islA comment isln comments are}
open at the end of the program.

System Action: The tape is positioned
at the record that was read when the
HDR1-was executed.

Explanation: EXECUPDT was
specified with the NOCOMMENTS
option, and one or more unmatched
quotes or comments were found in the
EXEC. If the ETMODE option was
specified with NOCOMMENTS and
there is a quote error, there may be
unpaired shift-in and shift-out
characters.

For CMS/DOS, message DMSTLM435R
is issued.
For- OS simulation, an OPEN error
occurs.
The TAPEMAC and TAPPDS commands
are terminated without reading any tape
data.

System Action: RC = 100.
Error message DMS671E is issued with
RC=8 from XEDIT. The EXEC is
created, but the System Product
Interpreter cannot use it because of the
nesting error.

The T APESL macro returns an error
code of 32.
User Response: Verify that the proper
tape is mounted. Reply to message
DMSTLM435R if issued. If the wrong
tape is mounted, try again with the
correct tape. If labels are not expected
on the tape, respecify label type as BLP
or LABOFF and try again.

User Response: Correct the quotes
and/or comments in the source file and
reissue the command.

420E

NSL exit filename missing or
invalid
Explanation: The filename specified
for user-written, nonstandard label
processing routine must be the name of
a TEXT or MODULE file. No file could
be found that had a filetype of TEXT or
MODULE with the specified name.
System Action: RC = 24.
The command or program is not
executed.
User Response: Specify the name of a
valid NSL exit routine and reissue the
command.

421E

TAPn(vdev) HDRl1abel missing
for In
Explanation: A tape specified as
standard label does not have a HDR1
label. Filename is dtfname for
CMS/DOS or ddname for OS simulation.
The message will also occur for a tape

356 VM/SP System Messages and Codes

422E

TAPn(vdev) positioned wrong for

In
Explanation: A tape was not
positioned correctly for label processing
to occur. For output tapes, an attempt
was made to write a new label when the
tape was not positioned at an existing
HDR1 label or tapemark.
For CMS/DOS input tape, the message
is issued when the file sequence number
on the tape label is larger than the one
specified in the LABELDEF command.
The filename is the symbolic name in
the DTFMT for the file.
For CMS, the filename is LABDEFid.
For OS simulation, the filename is
ddname.
System Action: An OS file is not
opened. A CMS/DOS job is cancelled

DMS
and the TAPESL macro gives an error
return code of 32.

425R

TAPn(vdev) block count error for
fn;

enter 1 (IGNORE) or 2 (CANCEL)
User Response: Be sure the tape is
positioned properly and that the correct
tape is mounted. If necessary,
reposition the tape and then reissue the
job or command.

4231

Explanation: The block count in an
EOF1 record does not match the number
of blocks actually read. Filename is
dtfname for eMS/DOS or ddname for OS
simulation.

TAPn(vdev) position parameter
ignored; output file will be written
immediately after new VOLl label

For OS simulation, the message is only
issued when you do not have a block
count exit routine specified in the DeB
EXIT list.

Explanation: This message occurs
when you respond to message
DMSTLM433R by requesting that a new
volume label be written on a tape. An
OS simulation SL tape has been
requested with a specified positional
parameter indicating the file is not to be
the first on the tape.

For the TAPESL macro the message is
issued only when you have not specified
an error return (by the
ERROR = parameter) that is different
from the normal return.
System Action: The system waits for a
reply.

System Action: The positional
parameter is ignored and the new label
file is written immediately after the new
VOL1label.

User Response: Enter '1' to continue
processing normally or '2' to cancel the
job in eMS/DOS, or to cause an abend
with code 500 in either OS simulation or
when processing the eMS TAPESL
macro.

User Response: None.

424E

TAPn(vdev) not positioned at
EOF1 or EOVl label
Explanation: The eMS T APESL
macro was issued with the function EIN
but the tape was not positioned at an
EOF1 or EOV1 label.
System Action: No label is processed.
The macro returns a code of 32 and the
tape is left positioned to the same record
it was positioned at when the macro was
issued.
User Response: Space the tape so it is
positioned at the EOF1 trailer label and
reissue the macro or ignore the error if
you do not want the tape trailer label
processed.

426R

TAPn(vdev) unexpired file; enter 1
(IGNORE) or 2 (ERROR)
Explanation: The system is trying to
write over a HDR1 record on tape vdev
that has an expiration date that has not
yet expired.
System Action: The system waits for a
response.
User Response: Enter '2' to cancel the
job in eMS/DOS or to prevent the file
from being opened in OS simulation.
The reply '1' will cause eMS to
disregard the expiration date and write
over the existing record except when
DISP MOD was specified for OS
simulation. In this case, the tape will
be positioned at the end of the file,
ready to add new records.

Conversational Monitor System (CMS) Messages

357

DMS
4271

TAPn(vdev) EOVllabel read

4291

Explanation: While processing trailer
labels for an input tape file, an EOVI
label was read instead of an EOFI label.

Explanation: End-of-tape was
encountered while the system was
writing a tape file with CMS/DOS or OS
simulation I/O macros. The tape file
was not defined to have IBM standard
labels.

System Action: Multivolume
processing takes over.

If the type of label processing is BLP or
NL, a tape mark is written after the last
record. If the file has nonstandard
labels and a user exit has been specified,
control is transferred to this
nonstandard label routine.

User Response: No response is
necessary. However, if you want to
mount a new tape and continue reading
the file, you must send a message to the
operator requesting that a new tape be
mounted. The data on the new tape
must be processed as a new file by CMS.

4281

System Action: A tape mark is written
after the last data record. If the file has
nonstandard labels and a user exit has
b~en specified, control is transferred to
this nonstandard label routine. See
message DMSTLM428I for a description
of tape positioning and user program
action when this message is issued.

TAPn(vdev) EOVI label written on
volid
Explanation: End-of-tape was
encountered while writing an output file
on a tape with IBM standard labels
under CMS/DOS or OS simulation. This
message is also issued when T APESL is
used to write an EOVI label.

User Response: The operator must
mount a new tape to continue the file.
If possible, the operator should
reorganize the data so each file will fit
on an individual tape.

System Action: A tape mark and
EOVI label are written after detecting
the end-of-tape.

In a user routine, the output file should
be closed. This will cause a tape mark
to be written whether the label
processing is BLP, NL, or LABO FF.
The tape mark after the last record will
allow the file to be read without error.

For CMS/DOS, the job is then cancelled
and the tape is rewound and unloaded.
For OS simulation, the program
abnormally terminates with a code 001 if
you are using QSAM or if you use a
CHECK macro in BSAM. If you are
using BSAM with no CHECK macro,
your program continues to try to write
on the tape.
The tape is always rewound and
unloaded after this message is issued.
User Response: The operator must
mount a new tape to continue the file.
If possible, reorganize the output data to
fit on a single tape reel.

TAPn(vdev) EOT on output

430E

TAPn(vdev) LABELDEF
information missing for file fn
Explanati9n: Under CMS/DOS or CMS
you must specify a LABELDEF
statement for every labeled tape file.
One was not found for DTFMT or
labeldefid with the specified filename.
The message may occur for OS
simulation files if you have
inadvertently cleared the FILEDEF or
LABELDEF for the specified filename.
System Action: The job is canceled for
CMS/DOS, the file is not opened for OS

358

VM/SP System Messages and Codes

(
\

DMS

431E

simulation and the T APESL macro
returns an error code of 28.

message is the one found on the tape
label.

User Response: Specify a LABELDEF
statement for the file and execute the
job again.

System Action: The TAPE command is
terminated.
For CMS/DOS input files or CMS
TAPESL macro input, the command or
program is not executed; an error code
of 32 is returned.

TAPn(vdev) VOLI label missing
Explanation: This message occurs
when you request that a tape have its
VOL1 label checked or displayed. The
tape does not contain a VOL1 label as
its first record.

For CMS/DOS output files, message
DMSTLM435R is issued.
For CMS T APESL macro output files,
message DMSTLM433R is issued.

System Action: RC = 32.
The TAPE command is terminated.

For OS simulation input files, message
DMSTLM443R is issued.

For CMS/DOS input files or CMS
TAPESL macro input, the command or
program is not executed; an error code
of 32 is returned.

For OS simulation output files, message
DMSTLM446R is issued.
User Response: Be sure the correct
volume serial number is specified on the
command. If it is, the correct tape was
not mounted. Ask the operator to
mount the proper tape. Reissue the
command or program.

For CMS/DOS output files, message
DMSTLM435R is issued.
For eMS T APESL macro output files,
message bMSTLM433R is issued.
For OS simulation input files, message
DMSTLM443R is issued.
For OS simulation output files, message
DMSTLM446R is issued.
User Response: Be sure the operator
has mounted the correct tape. Respond
to any further messages that are issued.
If necessary, reissue the command or
program.

432E

TAPn(vdev) volid volid does not
match LABELDEF volid (volid) for

fn
Explanation: The volume serial
number (volid) on a tape VOLl label is
not the same as the volume serial
number specified on a LABELDEF or
FILEDEF command. Filename is
dtfname for CMS/DOS or ddname for OS
simulation. The volid displayed in the

433R

Enter l(volid) WRITE(volid) or 2
(REJECT)
Explanation: This message is issued
when an output OPEN routine finds a
tape that has a VOLl volid that does
not match the one specified or if an
output tape has been specified as SL and
no VOLl label is on it. The message is
issued only in situations where a
DOS/VS or OS/VS operating system
allows a VOLl label to be written. It is
never issued unless either message
DMSTLM431E or DMSTLM432E is also
issued.
System Action: The system waits for a
reply.
User Response: You may enter '2' to
reject the tape or rewrite the VOLl
label on the tape by entering '1'
followed by a left parenthesis and, with

Conversational Monitor System (eMS) Messages

359

DMS
no intervening blanks, a one- to
six-character volume serial number to
be written in the label. No owner field
may be specified. To write a VaLl label
with an owner field you must use the
WVOL1 function on the TAPE
command.

434E

4361

Explanation: This message is issued
when the as simulation user request
SUL tape label processing on a
FILEDEF command. The user also has
a user exit in the DCB exit list for the
file identified by ddname. However, the
tape did not contain a user UHL or UTL
label.

TAPn(vdev) input label error in
.field iieldname, file in

System Action: If a tape mark is read
instead of the expected user standard
label, the tape is positioned at the
record immediately after the tape mark.
Otherwise, the tape is backspaced so it
is positioned at the record that was read
when a user standard label was
expected.

Explanation: A field in a tape HDR1
label did not agree with the field
specified on a LABELDEF command for
the file. Filename is dtfname for
CMS/DOS or ddname for as simulation.
'fieldname' identifies the field causing
the error.
System Action: For CMS/DOS,
message DMSTLM435R is issued.

User Response: None, if the tape file
was not expected to contain a user
label. If one was expected, halt the
program execution and be sure the
correct tape is mounted.

CMS commands and T APESL macro
terminate without reading any tape
data.
For as simulation, the file is not
opened.
User Response: Be sure the
LABELDEF statement for the file is
correct. If it is, the wrong tape may be
mounted or it may be positioned at the
wrong file. Reply to message
DMSTLM435E if issued.

435R

Enter 1 (IGNORE) or 2 (CANCEL)
Explanation: This message is never
issued alone. It always follows another
CMS/DOS message that identifies a tape
label error.
This message gives the CMS/DOS user
the choice of ignoring a label processing
error and continuing the job or
cancelling it.
System Action: The system waits for a
reply.
User Response: Enter '1' or '2'.

360

VM/SP System Messages and Codes

TAPn(vdev) missing user standard
label for ddname

4371

TAPn(vdev) NSL routine returned
error code nnnnnn for in
Explanation: This message is issued
when you execute a nonstandard tape
label processing routine that returned a
nonzero return code of 'nnnnnn' in
register 15. 'fn' is the ddname for the
file that caused the code for as
simulation; for the T APE MAC and
TAPPDS commands, it is the id
parameter specified by the user.
System Action: The nonzero return
code prevents an as file from being
opened or causes the TAPEMAC or
T APPDS commands to be terminated
without processing any tape files.
User Response: Examine your NSL
routine to be sure you wanted to return
a nonzero code. If you did, then you
probably have the wrong tape mounted
or you anticipated this condition.

DMS
Volid volid is a duplicate entry

438E

System Action: RC = 4.
The text file is not produced.

Explanation: A duplicate VOLID was
entered in response to message
DMSLBD441R.

User Response: Change the control
file to include a language file identifier
record as described under the
LANGMERG command. (See the VM
System Facilities for Programming.)

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
441R
User Response: Reissue the command.
Then enter the correct VOLID(s) after
the system issues message
DMSLBD441R.

Explanation: A LABELDEF command
was entered with the VOLID ? operand.
The command expects at least one (1)
VOLID or a null line to be entered.
System Action: The system waits for a
response.

Volid volid is an invalid entry

439E

Explanation: This message is issued
for one of the following reasons:
•

Your response to message
DMSLBD441R contained an invalid
character in the volid

•

Your response to message
DMSTLM433R or DMSTLM446R
contained an invalid character in
the first volid you specified, or the
first volid is longer than six
characters.

System Action: If the response was to
DMSLBD441R, RC=24.
If the response was to DMSTLM433R or
DMSTLM446R, RC = 32. Execution of
the command is terminated. The system
status remains the same.
User Response: Reissue the command.
Then enter the correct volid(s) after the
system issues message DMSTLM433R,
DMSLBD441R or DMSTLM446R.

440W

Merged text deck not created - no
text decks were specified in
control file fn ft fm

Enter VOLID information:

User Response: Enter one (1) or more
VOLID(s) of the tape(s) to be processed
for the data set, or enter 'scratch' if
scratch tapes are to be used and no
VOLID checking is to be done at OPEN
time. If one or more VOLID(s) is
entered, the system continues to
reprompt for more VOLID information
until a null line is entered. If you
initially respond to message 441R with a
null line, it is treated as a VOLID of
'scratch'.

442E

SCRATCH may only be used as
the last volid for the file
Explanation: The 'scratch' VOLID was
not entered as the last VOLID for the
file.
System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the
LABELDEF command. Specify the
VOLID of 'scratch' as the last VOLID
entered for the file.

Explanation: The LANGMERG control
file did not contain any records that
identify language files.

Conversational Monitor System (CMS) Messages

361

DMS
443R

Enter 2 (REJECT) or 3
(NEWTAPE)

446R

Explanation: This message is issued
when an input OPEN finds a tape that
has a VaLl VaLID that does not match
the one specified. It is never issued
unless message DMSTLM 432E or
DMSTLM431E is also issued.

Enter l(volid) (WRITE(volid), 2
(REJECT), or 3 (NEWTAPE)
Explanation: This message is issued
when an output OPEN routine finds a
tape that has a VaLl VaLID that does
not match the one specified or if an
output tape has been specified as SL and
no VaLl label is on it. The message is
issued only in situations where an
OS/VS operating system allows a VaLl
label to be written or the correct tape
volume to be mounted. It is never
issued unless either message
DMSTLM431E or DMSTLM432E is also
issued.

System Action: The system waits for a
reply.
User Response: Enter 2 (or REJECT)
to reject the tape, or enter 3 (or
NEWTAPE) to allow the mounting of
the correct tape volume.

System Action: The system waits for a
reply.
444E

Volume volid is not a DOS
SYSRES

User Response: Enter 2 (or 'REJECT')
to reject the tape. Enter l(volid) (or
'WRITE (volid)') to rewrite the VaLl
label on the tape. The '1' or 'WRITE'
must be followed by a left parenthesis
and, with no intervening blanks, a one
to six character volume serial number to
be written in the label. No owner field
may be specified. To write a VaLl label
with an owner field, you must use the
WVOL1 function on the TAPE
command. Enter 3 (or 'NEWTAPE') to
allow the mounting of the correct tape
volume.

Explanation: The disk specified by the
mode operand of the SET DOS ON
command is not a VSE/AF system
residence volume.
System Action: RC = 32.
Execution of the command is
terminated. The system status remains ,
the same.
User Response: Reissue the command
with the correct mode.

445W

Invalid data in sequence field,
bypassing sequence check
Explanation: The sequence field on the
file being loaded is not numeric.
System Action: The file continues to
be loaded.
User Response: Check the file after it
has been loaded for possible
transmission errors.

447E

Invalid SYSPARM information.
Explanation: The information specified
with the SYSPARM option is invalid. It
may have been misspelled, or it may be
unacceptable or unrecognizable.
System Action: RC = 24.
Execution of the command is
terminated. System status remains the
same.
User Response: Correct and reenter
the command. Reviewing the relevant
SYSP ARM documentation may be
required. If the problem persists,
contact yOU!' system administrator.

362

VM/SP System Messages and Codes

(
~

DMS
448E
I

program that issued NUCXLOAD did
not terminate properly, but instead,
went into a loop.

Country code code not in list
Explanation: The source file name
specified on the VMFNLS command
contains a country code (code) that is
not in the VMFNLS LANGLIST file.

,
,
,

System Action: RC = 20005.
Execution stops.
User Response: Run the EXEC or
macro on its own, or check a program
issuing NUCXLOAD for a possible loop
that has not terminated properly. More
free storage may be obtained by
releasing a disk (to recover the space
used for the file directory) or deleting a
nucleus extension. Alternatively, re-IPL
CMS after defining a larger virtual
storage size for the virtual machine.

System Action: RC = 28.
Processing of the VMFNLS command
stops.

User Response: Check the file name of
the source file that you want to convert
to text. The 7th character (and 8th
character, if applicable) of this file
name, which is a country code, must
match an entry in the VMFNLS
LANGLIST file. If this country code
does not match, you must change the
file name of the source file so it does
match.

,
,

I',
,

449E

451E

Explanation: The REXX program
could not be read from the disk. This
problem almost always occurs only
when you are attempting to execute an
EXEC or program from someone else's
disk for which you have Read/Only
access, while someone with Read/Write
access to the disk has altered the
program so that it no longer exists in
the same place on the disk.

Error 22 running fn ft, line nn:
Invalid character string
Explanation: A character string
containing (1) unmatched shift-out (SO)
and shift-in (SI) control characters or (2)
an odd number of bytes between the
shift-out (SO) and shift-in (SI)
characters was scanned with OPTIONS
ETMODE in effect.

System Action: RC = 20003.
Execution stops.

System Action: RC = 20022.
Execution stops.

User Response: Reaccess the disk on
which the EXEC or program resides.

User Response: Correct the invalid
character string in the EXEC file.
452E
450E

Error 5 running fn ft, line nn:
Machine storage exhausted
Explanation: While attempting to
interpret a program, the System Product
Interpreter was unable to get the space
needed for its work areas and variables.
This may have occurred because the
program (such as the Editor) that
invoked the System Product Interpreter
has already used up most of the
available storage itself, or because a

Error 3 running fn ft, line nn:
Program is unreadable

Error 4 running fn ft, line nn:
Program interrupted
Explanation: The system interrupted
execution of your REXX program.
Usually this is due to your issuing the
'HI' (halt interpretation) immediate
command. Certain utility modules may
force this condition if they detect a
disastrous error condition.
System Action: RC = 20004.
Execution stops.

Conversational Monitor System (CMS) Messages

363

DMS
User Response: If you issued an 'HI'
command, continue as planned.
Otherwise, look for a problem with a
Utility Module called in your EXEC or
macro.

453E

455E

Explanation: The System Product
Interpreter has found a THEN or an
ELSE that does not match a
corresponding IF clause. This situation
is often caused by forgetting to put an
END or DO END in the THEN part of a
complex IF THEN ELSE construction.
For example,

Error 6 running In It, line nn:
Unmatched "/*" or quote
Explanation: The System Product
Interpreter reached the end of the file
(or the end of data in an INTERPRET
statement) without finding the ending
"* /" for a comment or quote for a literal
string.

If a=b then do;
Say EQUALS
exit
else
Say NOT EQUALS

System Action: RC = 20006.
Execution stops.

User Response: Make the necessary
corrections.

456E
Error 7 running In It, line nn:
WHEN or OTHERWISE expected
Explanation: The System Product
Interpreter expects a series of WHENs
and an OTHERWISE within a SELECT
statement. This message is issued when
any other instruction is found. This
situation is often caused by forgetting
the DO and END instructions around
the list of instructions following a
WHEN. For example,

Select
Select
When a=b then DO
When a=b then
Say 'A equals B'
Say 'A equals B'
exit
exit
end
Otherwise nop
Otherwise nop
end
end

System Action: RC = 20007.
Execution stops.
User Response: Make the necessary
corrections.

364

VM/SP System Messages and Codes

If a=b then do;
Say EQUALS
exit
end
else
(
Say NOT EQUALS~

System Action: RC = 20008.
Execution stops.

User Response: Edit the EXEC and
add the closing "* /" or quote. You can
also insert a TRACE SCAN statement at
the top of your program and rerun it.
The resulting output should show where
the error exists.

454E

Error 8 running In It, line nn:
Unexpected THEN or ELSE

Error 9 running In It, line nn:
Unexpected WHEN
or OTHERWISE
Explanation: The System Product
Interpreter has found a WHEN or
OTHERWISE instruction outside of a
SELECT construction. You may have
accidentally enclosed the instruction in
a DO END construction by leaving off
an END instruction, or you may have
tried to branch to it with a SIGNAL
statement (which cannot work because
the SELECT is then terminated).
System Action: RC = 20009.
Execution stops.
User Response: Make the necessary
correction.

DMS
457E

Error 10 running In It, line nn:
Unexpected or unmatched END

recursive subroutine that does not
terminate correctly could loop until it
causes this message.

Explanation: The System Product
Interpreter has found more ENDs in
your program than DOs or SELECTs, or
the ENDs were placed so that they did
not match the DOs or SELECTs.
This message can be caused if you try to
signal into the middle of a loop. In this
case, the END will be unexpected
because the previous DO will not have
been executed. Remember also, that
SIGNAL terminates any current loops,
so it can not be used to jump from one
place inside a loop to another.

System Action: RC = 2001l.
Execution stops.
User Response: Make the necessary
corrections.

459E

Explanation: You have exceeded the
limit of 500 characters for the length of
the internal representation of a clause.

This message can also be caused if you
place an END immediately after a
THEN OR ELSE construction.

If the cause of this message is not
obvious to you, it may be due to a
missing quote, that has caused a number
of lines to be included in one long
string. In this case, the error probably
occurred at the start of the data
included in the clause traceback
(flagged by '+ + +' on the console).

System Action: RC = 20010.
Execution stops.
User Response: Make the necessary
corrections. It may be helpful to use
'TRACE Scan' to show the structure of
the program and make it more obvious
where the error is. Putting the name of
the control variable on ENDs which
close repetitive loops can also help
locate this kind of error.

458E

The internal representation of a clause
does not include comments or multiple
blanks that are outside of strings. Note
also that any symbol ('name') gains two
characters in length in the internal
representation.

System Action: RC = 20012.
Execution stops.

Error 11 running In It, line nn:
Control stack full
Explanation: This message is issued if
you exceed the limit of 250 levels of
nesting of control structures (DO-END,
IF-THEN-ELSE, etc.)
This message could be caused by a
looping INTERPRET instruction, such
as:

line=IINTERPRET line.'
INTERPRET line
These lines would loop until they
exceeded the nesting level limit and this
message would be issued. Similarly, a

Error 12 running In It, line nn:
Clause> 500 characters

User Response: Make the necessary
corrections.

460E

Error 13 running In It, line nn:
Invalid character in data
Explanation: The System Product
Interpreter found an invalid character
outside of a literal (quoted) string.
Valid characters are:
A-Z a-z 0-9
(Alphamerics)
@} # $ ¢ . ? ! _ (Name Characters)
&*()-+ =-,"';:<,>/
(Special Characters)

Conversational Monitor System (CMS) Messages

365

DMS

461E

System Action: RC = 20013.
Execution stops.

concatenate the string to the value of
the symbol.

User Response: Make the necessary
corrections.

System Action: RC = 20015.
Execution stops.
User Response: Make the necessary
corrections.

Error 14 running In It, line nn:
Incomplete DO/SELECT/IF
Explanation: The System Product
Interpreter has reached the end of the
file (or end of data for an INTERPRET
instruction) and has found that there is
a DO or SELECT without a matching
END, or an IF that is not followed by a
THEN clause.

463E

Explanation: The System Product
Interpreter could not find the label
specified by a SIGNAL instruction (or
specified by a trap set to occur when a
certain event occurred). You may have
mistyped the label or forgotten to
include it.

System Action: RC = 20014.
Execution stops.

System Action: RC = 20016.
Execution stops. The name of the
missing label is included in the error
traceback.

User Response: Make the necessary
corrections. You can use 'TRACE Scan'
to show the structure of the program,
thereby making it easier to find where
the missing END should be. Putting the
name of the control variable on ENDs
that close repetitive loops can also help
locate this kind of error.

User Response: Make the necessary
corrections.

464E
462E

Error 15 running in It, line nn:
Invalid hex constant

System Action: RC = 20021.
Execution stops.
User Response: Make the necessary
corrections.

'13'X
'A3C2 lC34'X
'1DE8'X

366

VMjSP System Messages and Codes

Error 21 running In It, line nn:
Invalid data on end of clause
Explanation: You have followed a
clause, such as SELECT or NOP, by
some data other than a comment.

Explanation: For the System Product
Interpreter, hexadecimal constants may
not have reading or trailing blanks and
may have imbedded blanks at byte
, boundaries only. The following are all
valid hexadecimal constants:

You may have mistyped one of the
digits, for example typing a letter 0
instead of a o. This mess,age can also be
caused if you follow a string by the
I-character symbol "X" (the name of the
variable 'X'), when the string is not
intended to be taken as a hexadecimal
specification. In this case, use the
explicit concatenation operator ("II") to

Error 16 running In it, line nn:
Label not found

465E

Error 17 running In It, line nn:
Unexpected PROCEDURE
Explanation: The System Product
Interpreter encountered a PROCEDURE
instruction in an invalid position, either
because no internal routines are active,
or because a PROCEDURE instruction
has already been encountered in the
internal routine. This error can be

DMS
caused by "dropping through" to an
internal routine, rather than invoking it
with a CALL or a function call.

Execution stops.
User Response: Make the necessary
corrections.

System Action: RC = 20017.
Execution stops.
468E
User Response: Make the necessary
corrections.

466E

Explanation: The System Product
Interpreter found a variable or a literal
(quoted) string that is longer than the
limit.

Error 26 running fn ft, line nn:
Invalid whole number

The limit for names is 250 characters,
following any substitutions. A possible
cause of this error is the use of a period
(.) in a name, causing an unexpected
substitution.

Explanation: The System Product
Interpreter found an expression in the
NUMERIC instruction, a parsing
positional pattern, or the right hand
term of the exponentiation ('**')
operator that did not evaluate to a
whole number, or was greater than the
limit, for these uses, of 999999999.

The limit for a literal string is 250
characters. This error can be caused by
leaving off an ending quote (or putting a
single quote in a string) because several
clauses may be included in the string.
For example, the string 'don't' should be
written as 'don"t' or "don't".

This message can also be issued if the
return code passed back from an EXIT
or RETURN instruction (when a REXX
program is called as a command) is not
a whole number or will not fit in a
System/370 register. This error may be
due to mistyping the name of a symbol
so that is is not the name of a variable
in the expression on any of these
statements. This might be true, for
example, if you typed "EXIT CR"
instead of "EXIT RC."

System Action: RC = 20030.
Execution stops.
User Response: Make the necessary
corrections.

469E
System Action: RC = 20026.
Execution stops.
User Response: Make the necessary
corrections.

467E

Error 27 running fn ft, line nn:
Invalid DO syntax
Explanation: The System Product
Interpreter found a syntax error in the
DO instruction. You might have used
BY or TO twice, or used BY, TO, or
FOR when you didn't specify a control
variable.

Error 30 running fn ft, line nn:
Name or string > 250 characters

Error 31 running fn ft, line nn:
Name starts with numeric or "."
Explanation: The System Product
Interpreter found a variable whose name
begins with a numeric digit or a '.'. The
REXX language rules do not allow you
to assign a value to a variable whose
name begins with a numeric digit or a
period, because you could then redefine
numeric constants which would be
catastrophic.
System Action: RC = 2003l.
Execution stops.
User Response: Rename the variable
correctly. It is best to start a variable

System Action: RC = 20027.

Conversational Monitor System (eMS) Messages

367

DMS
name with an alphabetic character, but
some other characters are allowed.

470E

472E

Explanation: The System Product
Interpreter found an unmatched
parenthesis within an expression. You
will get this message if you include a
single parenthesis in a command
without enclosing it in quotes. For
example, COpy ABC A B D (REP
should be written as COpy ABC A B
D '(,REP.

Error 34 running in it, line nn:
Logical value not 0 or 1
Explanation: The System Product
Interpreter found an expression in an
IF, WHEN, DO WHILE, or DO UNTIL
phrase that did not result in a '0' or '1'.
Any value operated on by a logical
operator (--', I, &, or &&) must result in
a '0' or '1'. For example, the phrase "If
result then exit rc" will fail if Result
has a value other than 0 or 1. Thus, the
phrase would be better written as "If
result, = 0 I result, = 1 then exit rc."
System Action: RC = 20034.
Execution stops.

System Action: RC = 20036.
Execution stops.
User Response: Make the necessary
corrections.

473E

User Response: Make the necessary
corrections.

471E

Error 36 running in it, line nn:
Unmatched "(" in expression

Error 37 running in it, line nn:
Unexpected" ," or ")"
Explanation: The System Product
Interpreter found a comma (,) outside a
routine invocation or too many right
parentheses in an expression. You will
get this message if you include a comma
in a character expression without
enclosing it in quotes. For example, the
instruction:

Error 35 running in it, line nn:
Invalid expression
Explanation: The System Product
Interpreter found a grammatical error in
an expression. You might have ended
an expression with an operator, or had
two adjacent operators with no data in
between, or included special characters
(such as operators) in an intended
character expression without enclosing
them in quotes. For example LISTFILE
* * * should be written as LISTFILE ,* *
*' (if LISTFILE is not a variable), or
even as 'LISTFILE * * *'.

Say Enter A, B, or C
should be written as:
Say 'Enter A, B, or C'
System Action: RC = 20037.
Execution stops.
User Response: Make the necessary
corrections.

System Action: RC = 20035.
Execution stops.
474E
User Response: Make the necessary
corrections.

Error 39 running in it, line nn:
Evaluation stack overflow
Explanation: The System Product
Interpreter was not able to evaluate the
expression because it is too complex
(many nested parentheses, functions,
etc.).
System Action: RC = 20039.

368

VM/SP System Messages and Codes

DMS
Execution stops.

You may have mistyped a variable
name, or included an arithmetic
operator in a character expression
without putting it in quotes. For
example, the command MSG * Hi!
should be written as 'MSG * Hi!',
otherwise the System Product
Interpreter will try to multiply "MSG"
by 'Hi!'.

User Response: Break up the
expressions by assigning sub-expressions
to temporary variables.

475E

Error 40 running fn ft, line nn:
Incorrect call to routine

System Action: RC = 20041.
Execution stops.

Explanation: The System Product
Interpreter encountered an incorrectly
used call to a built-in or external
routine. Some possible causes are:
•

•

you passed invalid data (arguments)
to the routine. This is the most
common possible cause and is
dependent.on the actual routine. If
a routine returns a non-zero return
code, the System Product Interpreter
issues this message and passes back
its return code of 20040.

User Response: Make the necessary
corrections.

477E

Explanation: The System Product
Interpreter encountered the result of an
arithmetic operation that required an
exponent greater than the limit of 9
digits (more than 999999999 or less than

the module invoked was not
compatible with the System Product
In terpreter.

-999999999 ).

This error can occur during evaluation
of an expression (often as a result of
trying to divide a number by 0), or
during the stepping of a DO loop control
variable.

If you were not trying to invoke a
routine, then you may have a symbol or
a string adjacent to a '(' when you
meant it to be separated by a space or
an operator. This causes it to be seen
as a function call. For example,
TIME(4 + 5) should probably be written
as TIME*(4+5).

System Action: RC = 20042.
Execution stops.
User Response: Make the necessary
corrections.

System Action: RC = 20040.
Execution stops.
User Response: Make the necessary
corrections.

476E

Error 41 running fn ft, line nn:
Bad arithmetic conversion
Explanation: The System Product
Interpreter found a term in an
arithmetic expression that was not a
valid number or that had an exponent
outside the allowed range of -999999999
to + 999999999.

Error 42 running fn ft, line nn:
Arithmetic overflow/underflow

478E

Error 43 running fn ft, line nn:
Routine not found
Explanation: The System Product
Interpreter was unable to find a routine
called in your program. You invoked a
function within an expression, or in a
subroutine invoked by CALL, but the
specified label is not in the program, or
is not the name of a built-in function,
and CMS is unable to locate it
externally.

Conversational Monitor System (eMS) Messages

369

DMS
The simplest, and probably most
common, cause of this error is mistyping
the name. Another possibility may be
that one of the standard function
packages is not available.
If you were not trying to invoke a
routine, you may have put a symbol or
string adjacent to a "(" when you meant
it to be separated by a space or
operator. The System Product
Interpreter would see that as a function
invocation. For example, the string
3(4 + 5) should be written as 3*(4 + 5).

back any data. Similarly, an internal
routine, called as a function, must end
with a RETURN statement specifying
an expression.
System Action: RC = 20045.
Execution stops.
User Response: Make the necessary
corrections.

481E

System Action: RC = 20043.
Execution stops.

Explanation: The System Product
Interpreter carries out numerous
internal self-consistency checks. It
issues this message if it encounters a
severe error.

User Response: Make the necessary
corrections.

479E

This may be due to specifying the name
of a CMS module that is not intended
for use as a System Product Interpreter
function. It should be called as a
command or subroutine.

480E

User Response: Report any occurrence
of this message to your IBM
representative.

482E

Error 19 running in it, line nn:
String or symbol expected

System Action: RC = 20044.
Execution stops.

Explanation: The System Product
Interpreter expected a symbol following
the keywords CALL, SIGNAL, SIGNAL
ON, or SIGNAL OFF but none was
found. You may have omitted the string
or symbol, or you may have inserted a
special character (such as a parenthesis)
in it.

User Response: Make the necessary
corrections.

System Action: RC = 20019.
Execution stops.

Error 45 running In It, line nn: No
data specified on function
RETURN
Explanation: A REXX program has
been called as a function, but an
attempt is being made to return (by a
RETURN; instruction) without passing

370

System Action: RC = 20049.
Execution stops.

Error 44 running In It, line nn:
Function did not return data
Explanation: The System Product
Interpreter invoked an external routine
within an expression. The routine
seemed to end without error, but it did
not return data for use in the
expression.

Error 49 running In It, line nn:
Interpreter failure

VM/SP System Messages and Codes

User Response: Make the necessary
corrections.

DMS
Error 20 running in it, line nn:
Symbol expected

483E

Error 25 running In it, line nn:
Invalid sub-keyword found

485E

Explanation: The System Product
Interpreter may expect a symbol
following the END, ITERATE, LEAVE,
NUMERIC, PARSE, or PROCEDURE
keywords or expected a list of symbols
following the DROP, UPPER, or
PROCEDURE (with EXPOSE option)
keywords. Either there was no symbol
when one was required or some other
characters were found.

Explanation: The System Product
In terpreter expected a particular
sub-keyword at this position in an
instruction and something else was
found. For example, the NUMERIC
instruction must be followed by the
sub-keyword DIGITS, FUZZ, or FORM.
If NUMERIC is followed by anything
else, this message is issued.
System Action: RC = 20025.
Execution stops.

System Action: RC = 20020.
Execution stops.

User Response: Make the necessary
corrections.

Error 28 running in ft, line nn:
Invalid LEAVE or ITERATE

486E

Error 24 running In It, line nn:
Invalid TRACE request

484E

Explanation: The System Product
Interpreter issues this message when:
•

•

the action specified on a TRACE
instruction, or the argument to the
TRACE built-in function, starts with
a letter that does not match one of
the valid alphabetic character
options. The valid options are A, C,
E, I, L~ N, 0, R, or S.
an attempt is made to request
"TRACE Scan" when inside any
control construction or while in
interactive debug.

System Action: RC = 20024.
Execution stops.
User Response: Make the necessary
corrections.

Explanation: The System Product
Interpreter encountered an invalid
LEAVE or ITERATE instruction. The
instruction was invalid because:
•

no loop is active, or

•

the name specified on the
instruction does not match the
control variable of any active loop.

Note that internal routine calls and the
INTERPRET instruction protect DO
loops by making them inactive.
Therefore, for example, a LEAVE
instruction in a subroutine cannot
affect a DO loop in the calling routine.
You can cause this message to be issued
if you use the SIGNAL instruction to
transfer control within or into a loop.
A SIGNAL instruction terminates all
active loops, and any ITERATE or
LEAVE instruction issued then would
cause this message to be issued.
System Action: RC = 20028.
Execution stops.
User Response: Make the necessary
corrections.

Conversational Monitor System (CMS) Messages

371

DMS
487E

Error 29 running in it, line nn:
Environment name too long

490E

Explanation: The System Product
Interpreter encountered an environment
name specified on an ADDRESS
instruction that is longer than the limit
of 8 characters.

Explanation: The System Product
Interpreter halts execution of the
program because some system service,
such as user input or output or
manipulation of the console stack has
failed to work correctly.

System Action: RC = 20029.
Execution stops.

System Action: RC = 20048.
Execution stops.

User Response: Specify the
environment name correctly.

488E

489E

491E

Error 18 running fn ft, line nn:
THEN expected
Explanation: All REXX IF and WHEN
clauses must be followed by a THEN
clause. Another clause was found
before a THEN statement was found.

System Action: RC = 20033.
Execution stops.

System Action: RC = 20018.
Execution stops.

User Response: Make the necessary
corrections.

User Response: Insert a THEN clause
between the IF or WHEN clause and the
following clause.

Error 38 running fn ft, line nn:
Invalid template or pattern

492E

Error 32 running fn ft, line nn:
Invalid use of stem

Explanation: The System Product
Interpreter found an invalid special
character, for example 0/0, within a
parsing template, or the syntax of a
variable trigger was incorrect (no
symbol was found after a left
parenthesis). This message is also
issued if the WITH sub-keyword is
omitted in a PARSE VALUE
instruction.

Explanation: The REXX program
attempted to change the value of a
symbol that is a stem. (A stem is that
part of a symbol up to the first period.
You use a stem when you want to affect
all variables beginning with that stem.)
This may be in the UPPER instruction
where the action in this case is
unknown, and therefore in error.

System Action: RC = 20038.
Execution stops.

System Action: RC = 20032.
Execution stops.

User Response: Make the necessary
corrections.

372

User Response: Ensure that your
input is correct and that your program
is working correctly. If the problem
persists, notify your system support
personnel.

Error 33 running in it, line nn:
Invalid expression result
Explanation: The System Product
Interpreter encountered an expression
result that is invalid in its particular
context. The result may be invalid
because an illegal FUZZ or DIGITS
value was used in a NUMERIC
instruction (FUZZ may not become
larger that DIGITS).

Error 48 running fn ft, line nn:
Failure in system service

VM/SP System Messages and Codes

DMS
User Response: Change the program
so that it does not attempt to change the
value of a stem.

493E

SORT invalid in update mode
Explanation: The SORT subcommand
was issued in update mode.

Does not match the fileid in the first
input record for the DISK DUMPed
file.

Contains illegal characters, a blank
filename or filetype or an illegal
filemode.

System Action: RC = 100.
Execution of the command is
terminated. Message DMS1124W will
be issued informing you that the spool
file has been left in your reader.

System Action: RC = 3.
The data is not sorted.
User Response: None.

494W

User Response: A modified but
invalid spool file has been sent to you.
If you still want to load the file, use the
READ CARD command. Otherwise, use
the CP PURGE command to delete this
file from your reader.

FULLREAD set off.

\
) I
I

Explanation: Your terminal
configuration does not support the CMS
command "SET FULLREAD ON". So
that your session can continue,
FULLREAD has been set off.

497E

This terminal configuration, which
imposes several restrictions on your
session, occurs when going through a
VMjPassthru Facility (5749-RC1) (PVM)
327X Emulator link to another VM
system. These PVM links can be
indentified by an '8' to the immediate
left of the nodeid in the PVM selection
screen.

Minimum abbreviation is between
SO and SI
Explanation: A SET SYNONYM
subcommand was issued that contained
a DBCS string as the synonym name.
The minimum abbreviation length split
the nBCS string. The minimum
abbreviation length must not be
between a shift-out (SO) and a shift-in
(SI) control character.

The PVM emulator line driver does not
support the 3270 command "read-buffer"
which is used when FULLREAD is set
on and in processing P A keys.

System Action:

RC = 5.

User Response: Correct the minimum
abbreviation length and issue the
subcommand again.

System Action: FULLREAD setting is
turned off.
498E

User Response: None.

4968

Invalid fileid
input record

In It 1m found

Explanation: The fileid shown in the
message is found in the last input record
of the DISK DUMPed file. This DISK
DUMPed file is in a spool file being
processed by the disk command. This
field either:

Not executed--the two areas to
merge overlap each other
Explanation: The MERGE
subcommand was issued and the group
of lines that were to be merged
overlapped each other.
System Action: RC = 1.
No lines are merged.

Conversational Monitor System (CMS) Messages

373

DMS
User Response: Specify targets such
that the lines to be merged do not
overlap.

499E

5021

Explanation: The number of lines
recovered (or 'NO LINES' if 0 lines were
recovered), as a result of a RECOVER
subcommand, is displayed.

User not authorized to issue the
command command
Explanation: The TELL EXEC tried to
issue the specified 'command' found in
the GLOBALV file. Either the specified
'command' is invalid, or the user is not
authorized to issue the MSGNOH
command.

User Response: None.

503E

System Action: RC=3.
Lines are spilled or truncated depending
on SET SPILL ONIOFFIWORD.

Unable to unpack file In It 1m
User Response: To avoid truncation of
subsequent lines, change the truncation
setting by issuing a SET TRUNC
subcommand. SET SPILL also allows
you to avoid losing any characters by
truncation.

Explanation: An error condition was
detected during the process of
unpacking a file.
System Action: RC = 88.
Execution of the command is
terminated.
504E

5011

nn line(s) {truncatedlspilled}

Explanation: Lines were truncated or
spilled due to execution of the SHIFT or
EXPAND subcommand.

{Nolnn} line(s) deleted

Explanation: The number of lines
deleted as a result of a DELETE or
CDELETE subcommand is displayed.
System Action: None.
User Response: None.

374

{Trunca ted ISpilled}
Explanation: The current line has
exceeded the truncation column and the
extra characters have been truncated or
spilled.

User Response: Reissue the
DEFAULTS EXEC to set msgcmd to
either MSG or MSGNOH.

User Response: Contact your system
support personnel for assistance.

VM/SP System Messages and Codes

System Action: If NO lines were
recoverable, RC = 3 is returned.

System Action: RC = 40.
The command is rej ected.

500E

{Nolnn} line(s) recovered

System Action: RC = 3.
Lines are spilled or truncated depending
on SET SPILL ONIOFFIWORD.
User Response: To avoid truncation of
subsequent lines, change the truncation
setting by issuing a SET TRUNC
subcommand. SET SPILL also allows
you to avoid losing any characters by
truncation.

DMS
505E

Not executed--the target line (nn)
is within the lines to move

508E

Explanation: The destination line for a
move operation fell within the block of
lines to be moved.

Explanation: During the execution of
a XEDIT profile macro, a LOAD
subcommand was detected that was not
the first XEDIT subcommand in the
macro.

System Action: RC = 1.
User Response: Correct and reissue
the subcommand.

5061

System Action: RC = 3.
The XEDIT profile macro is partially
executed. The system executes all
REXX or EXEC 2 statements, CMS
commands, and XEDIT subcommands in
the macro until the LOAD subcommand
is reached. It then ignores the LOAD
subcommand and all subsequent
subcommands. Upon detection of the
first XEDIT subcommand, the editor
automatically executed a LOAD
subcommand that was used to invoke
the profile macro. No more than one
LOAD command, either implicit or
explicit, may be executed in one XEDIT
macro call.

{Nolnn} lines
{moved Icopied Imerged}

Explanation: The number of lines that
were moved, copied or merged is
displayed.
System Action: None.
User Response: None.

507E

LOAD must be the first
subcommand in the profile

No preserved data to restore
Explanation: A RESTORE
subcommand was issued to restore the
settings of XEDIT variables but the
PRESERVE subcommand had not
previously been issued to save the
settings of the variables.
System Action: RC = 3.
The RESTORE subcommand is not
executed.
User Response: If you wish to alter
XEDIT variables temporarily. enter the
PRESERVE subcommand, then change
the XEDIT variables using the SET
subcommand. Subsequently, enter the
RESTORE subcommand to restore the
variables to the values they had when
the PRESERVE subcommand was last
issued.

User Response: Correct your XEDIT
profile macro. Move the LOAD
subcommand up so that it is the first
XEDIT subcommand to be executed.

509E

subcommand subcommand not
valid from a prefix macro

Explanation: A subcommand is not
valid when issued from a prefix macro.
The following subcommands are invalid:
LPREFIX, QUIT, FILE, and READ.
System Action: RC = 4.
Execution of the macro continues.
User Response: Do not issue the
macro from the prefix area, or modify
the macro so this subcommand is not
issued.

Conversational Monitor System (CMS) Messages

375

DMS
5101

AUTOSAVED as fn ft fm

513E

Unknown CP/CMS command
Explanation: A command was
transmitted to CMS or to CP but was
not recognized.

Explanation: As a result of a SET
AUTOSAVE setting, the file was
written to disk with the fileid that is
displayed.

System Action: RC = -3.
System Action: The editing session
continues.

User Response: Correct and reissue
the command.

User Response: None.
514E
511E

String2 contains more arbitrary
characters than stringl

Explanation: A CMS or CP command
was executed, and an error occurred.

Explanation: In a CHANGE
subcommand, the operand 'string2'
contained more arbitrary characters
than the operand 'string1'.

System Action: The return code from
the CMS or CP command is displayed in
the message.

System Action: RC = 5.
User Response: Correct the operand
'string2' and reissue the CHANGE
subcommand.

512E

User Response: Correct and reissue
the command.

515E

Explanation: A eMS command that is
not one of the CMS subset commands
was issued and the user is in CMS
SUBSET mode.

RC = -2: The command was passed to
CMS. The VM/SP editor did not attempt
to decode the command.
User Response: None.

RECFM must be F, V, FP, or VP
Explanation: A SET RECFM
subcommand was issued and the
operand was not recognized.

Invalid subset command

System Action: RC = -1 or -2.
RC = -1: The command was passed to
CMS; the command was not a valid
system editor subcommand.

Return code nn from command

System Action: RC = 5.
The subcommand is not executed.
User Response: Correct and reissue
th~ subcommand.

516E

LRECL too large for V -format file
Explanation: A SET LRECL
subcommand was issued with a logical
record length that exceeds the maximum
for V-format files, which is 65,535 or a
SET RECFM VIVP subcommand was
issued for a file with a record length
greater than this maximum.
System Action: RC = 4.
The subcommand is not executed.
User Response: Correct and reissue
the subcommand.

376

VM/SP System Messages and Codes

DMS
5171

nn occurrence(s) changed on nn
line(s)

Explanation: An ALTER macro or a
CHANGE subcommand caused 'nn'
occurrences on 'nn' lines to be changed.

User Response: Correct and reissue
the subcommand.

521E

Explanation: The GET subcommand
was issued with a line number of zero;
or a CURSOR, SET CURLINE, SET
MSGLINE, SET RESERVED, SET
SCALE, or SET T ABLINE subcommand
was issued with an invalid line number.

System Action: None.
User Response: None.

518E

nn occurrence(s) changed on nn
line(s); nn line(s)
{truncated Ispilled}

Explanation: A CHANGE
subcommand caused 'nn' occurrences to
be changed; as a result, 'nn' lines were
truncated or spilled. If SET SPILL
OFF, they were truncated; otherwise,
they were spilled.

Invalid line number

System Action: For the CURSOR
subcommand, RC = 1; for the other
subcommands listed above, RC = 5.
User Response: Correct and reissue
the subcommand.

5221

System Action: RC = 3.

{N 0 Inn} occurrences
Explanation: The number of
occurrences of a string located by a
COUNT subcommand is displayed.

User Response: Issue SET SPILL
ONIWORD to avoid truncation.

System Action: None.
519E

LRECL must be lower than
WIDTH (nn)
Explanation: A SET LRECL
subcommand specified a logical record
length greater than the WIDTH option
in the XEDIT command.

User Response: None.

5231

Explanation: A SET TERMINAL
TYPEWRITER subcommand was issued
from a display terminal.

System Action: RC = 5.
The subcommand is not executed.

System Action: None.

User Response: Correct and reissue
the subcommand.

User Response: None.

524W
520E

Typewriter mode

NONDISP character reset to"

Invalid operand: operand
Explanation: A subcommand was
issued either with an invalid operand,
with too many operands, or with an
incorrect filemode.
System Action: RC = 5.
The subcommand is not executed.

Explanation: A SET APL ON or SET
TEXT ON subcommand was in effect,
and a SET NONDISP subcommand was
issued defining an APL or TEXT
character as the non-displayable
character. When a SET APL OFF or
SET TEXT OFF subcommand was
issued subsequently, eMS automatically

Conversational Monitor System (CMS) Messages

377

DMS
reset the non-displayable character to a
doublequote (").

User Response: Correct and reissue
the subcommand.

System Action: None.
528E
User Response: None.

525E

Explanation: The 'target' operands
specified in a SET RANGE subcommand
were reversed.

Invalid {PFkeyIPFkey/PAkey}
number

System Action: RC = 5.
The subcommand is not executed.

Explanation: A SET or QUERY PFn,
CMSPF nn, WMPF nn, or SCHANGE
subcommand was issued, and 'n' or 'nn'
was either zero or greater than 24; or, a
SET or QUERY PAn subcommand was
issued, and 'n' was either zero or greater
than 3.

User Response: Correct and reissue
the subcommand.

529E
System Action: RC = 5 or 24.
User Response: Correct and reissue
the subcommand.

526E

Invalid range: target2 (line nn)
precedes target! (line nn)

{[SET]subcommandISubcommandl
SIIRGTLEFTISPLTJOIN}
[subcommand] is only valid in
{display I editing} mode
Explanation: A subcommand was
issued that is valid only in display or
editing mode. The following
subcommands are valid only in display
or editing mode:

Option option valid in display
mode only
Explanation: The following SET
options are only valid in display mode:

ADD
BACKWARD
CURSOR
FORWARD
MODIFY

CMDLINE SCALE
CURLINE SCREEN
MSGLINE TABLINE
RESERVED TERMINAL

POWERINP
For the EXECUTE, JOIN, or SPLIT
subcommands, the CURSOR operand
was specified and the terminal is not in
display mode.
'

REFRESH
RGTLEFT

SCHANGE
SI
SOS
SPLTJOIN
Prefix subcommand
A
Prefix subcommand
I
Prefix macro 81

System Action: RC = 3.
System Action: RC = 3.
User Response: None.
User Response: None.
5301

527E

378

nn file(s) in storage

Invalid column number
Explanation: A QUERY RING
subcommand was executed.

Explanation: A CURSOR or MERGE
subcommand was issued with an invalid
column number.

System Action: None.

System Action: RC = 1.

User Response: None.

VM/SP System Messages and Codes

DMS
53lE

Disk is full; set new filemode or
clear some disk space

The subcommand is not executed.
User Response: Correct and reissue
the subcommand.

Explanation: The output disk became
full during execution of a FILE or
SAVE subcommand.

535E
System Action: RC = 13.
The editing session continues.

Explanation: A RENUM subcommand
was issued, and either the 'startno' or
'incr' operand was specified as zero.

User Response: Specify a new filemode
(SET FMODE) or make more room on
the disk.

532E

Invalid parameters for RENUM

System Action: RC = 5.
The subcommand is not executed.

Disk is full; AUTOSA VE failed

User Response: Correct and reissue
the subcommand.

Explanation: The output disk became
full during an automatic save operation.

536E
System Action: RC = 13.
The editing session continues.

Explanation: A 'SET SCREEN SIZE'
or 'SET SCREEN WIDTH' subcommand
was issued, and the number of lines or
columns specified exceed the limits of
the virtual screen.

User Response: Use the SET
AUTOSAVE subcommand to specify a
new filemode, or make more room on
the disk.

533E

System Action: RC = 1.
The subcommand is not executed.

Line nn is not reserved
Explanation: A SET RESERVED nn
OFF subcommand was issued, and 'nn'
indicates a line that is not currently
reserved.

User Response: Correct and reissue
the subcommand.

537E
System Action: RC = 4.
The subcommand is not executed.
User Response: Reissue the
subcommand.

534E

Too many logical screens defined
Explanation: A SET SCREEN
subcommand was issued, and 'n'
specified too many logical screens for
the physical screen size.

Logical screens exceed virtual
screen size

Each logical screen must contain
at least 5 lines and 20 columns
Explanation: A 'SET SCREEN'
subcommand was issued that specified a
logical screen size of less than 5 rows
and/or less than 20 columns.
System Action: RC = 4.
The subcommand is not executed.
User Response: Correct and reissue
the subcommand.

System Action: RC = 4.

Conversational Monitor System (CMS) Messages

379

DMS
538E

No name defined

542E

Explanation: A 'QUERY POINT *'
subcommand was issued, but no
symbolic names have been defined.

No such subcommand: name
Explanation: A subcommand not
recognized by the editor was issued.
System Action: RC =-1.

System Action: RC = 3.
User Response: If the name you
entered was a macro name, verify that
the macro resides on one of your
accessed disks.

User Response: None.

539E

Named line not found
Explanation: A 'SET POINT'
subcommand was issued to delete a
specified symbolic name, and the name
was not located.

543E

Explanation: A subcommand was
entered that required a numeric
operand, and an alphabetic operand was
specified instead, or the number was too
large. If the EXECUTE subcommand
was issued with a negative number, this
message is generated. The EXECUTE
subcommand only accepts numbers
greater than or equal to zero.

System Action: RC = 2.
User Response: None.

540E

Invalid number: number

Name already defined on line nn

System Action: RC = 5.

Explanation: A 'SET POINT'
subcommand was issued to define a
symbolic name, and the specified name
was already assigned to another line.

User Response: Correct and reissue
the subcommand.

System Action: RC = 1.
544E
User Response: Issue a 'SET POINT
.symbol OFF' subcommand to delete the
previous assignment, or select a unique
name and reissue the subcommand.

541E

Invalid hex data: xxxxxxxx
Explanation: The subcommand SET
HEX ON is in effect, and characters
that did not represent valid hexadecimal
notation (OO-FF) were entered in a
subcommand.

Invalid name
System Action: RC = 5.
Explanation: A 'SET POINT'
subcommand was issued, and the
specified name either exceeded eight
characters or was not preceded by a
period (.).

User Response: Correct and reissue
the subcommand.

545E

Missing operand(s)

System Action: RC = 5.
User Response: Correct and reissue
the subcommand.

Explanation: A subcommand was
entered without the required number of
operand(s), or the operand(s) misspelled.
System Action: RC = 5.
The subcommand is not executed.

380

VM/SP System Messages and Codes

DMS
The subcommand is not executed.

User Response: Correct and reissue
the subcommand.

User Response: Correct and reissue
the subcommand.
546E

Target not found
Explanation: A subcommand was
issued with a target operand specified as
a string expression or line name that
was not located.

547E

550E

Too many operands in synonym
definition

System Action: RC = 2.
The subcommand is not executed.

Explanation: A 'SET SYNONYM'
subcommand was issued with more than
64 operands or with an operand greater
than 160 characters.

User Response: Correct and reissue
the subcommand.

System Action: RC = 5.
The subcommand is not executed.
User Response: Correct and reissue
the subcommand.

Synonym definition incomplete
Explanation: A 'SET SYNONYM'
subcommand was issued without the
required number of operands.

550W

System Action: RC=5.
The subcommand is not executed.

Date/Time data not present for
file fn ft
Explanation: This message is issued
when using the OLDDATE option of
DISK LOAD and the time of the file
being loaded is blank.

User Response: Correct and reissue
the subcommand.

System Action: The file is loaded with
a new date and time.
548E

Invalid synonym operand: operand
User Response: None.
Explanation: A 'SET PREFIX
SYNONYM' subcommand was issued
with an invalid operand.
System Action: RC = 5.
The subcommand is not executed.
User Response: Correct the operand
and reissue the subcommand.

549E

Synonym abbreviation too large

5511

{Target IString} string found; [ --PFnn set for selective CHANGE]
Explanation: An SCHANGE macro
was executed. If a CLOCATE
subcommand was typed in the command
line or saved in the LASTLORC buffer,
the first part of the message is
displayed. If a CHANGE subcommand
was typed in the command line or saved
in the LASTLORC buffer, the message
also displays which PF key must be
pressed to perform the change.

Explanation: A 'SET SYNONYM'
subcommand was issued and 'n'
(minimum number of characters) was
larger than the word itself.

System Action: None.

System Action: RC = 5.

User Response: None.

Conversational Monitor System (CMS) Messages

381

DMS
552E

No synonym currently defined

A duplicate copy of the file that was
requested will not be loaded into
storage.

Explanation: A 'QUERY SYNONYM
*' subcommand was issued, and no

User Response: None.

synonyms are currently defined.

System Action: RC = 3.
557S

No more storage to insert lines

User Response: None.

5531

Editing file:

Explanation: Storage was exhausted
during the execution of one of the
following subcorn.mands: ADD, COPY,
DUPLICATE, GET INPUT,
POWERINP, REPLACE, SPLIT,
SPLTJOIN, and the following prefix
subcommands: A, C, M,".

In It 1m

Explanation: This message is displayed
on a typewriter terminal or a display
terminal used in typewriter mode, when
one of the following occurred:
1.

An XEDIT command was issued.

Multiple files are being edited, and a
QUIT or FILE subcommand was
issued. The fileid displayed is the
new current file.

System Action: RC = 4.
The subcommand stops executing when
no more storage is available.
User Response: Increase the storage
size of your virtual machine by issuing a
CP DEFINE STORAGE subcommand, or
release all unnecessary disks.

System Action: None.
User Response: None.

554E

558E

Explanation: A SET SERIAL
subcommand was issued, and the file
has a variable record format. Only files
with a fixed record format can be
serialized.

No storage available
Explanation: No more storage is
available and a subcommand that
requires free storage was issued.

System Action: RC = 5.

System Action: RC = 104.
The subcommand is not executed.

User Response: You can issue a SET
RECFM F subcommand to change the
record format of the file. (See also
message 560E.)

User Response: Increase the storage
size of your virtual machine by issuing a
CP DEFINE STORAGE subcommand.

555E

File

In It 1m already in storage

Explanation: A LOAD, SET FMODE,
SET FNAME, or SET FTYPE
subcommand was issued for a file that is
already in the ring of files in storage.

Wrong file format for
serialization

559W

Warning: file is empty
Explanation: A subcommand was
issued, but the file contains no lines.
For the SAVE/FILE subcommand, the
copy of the file on disk has not been
altered.

System Action: RC = 4.
System Action:

382

VM/SP System Messages and Codes

DMS
For DMSXSU, the subcommand is
executed until EOF is reached.

562E

For DMSXFD, the FILE or SAVE
subcommand is executed, except that
the permanent copy of the file on disk is
not changed.

No line(s) saved [by PUT(D)
subcommand]
Explanation: A GET subcommand was
issued, but no lines(s) had been stored
by a PUT or PUTD subcommand.
System Action: RC = 28.

User Response: None.
User Response: None.
560E

Not enough space for serialization
between TRUNC and LRECL

563W

Explanation: A SET SERIAL
subcommand was issued, and there is
not enough room to insert the serial
number.

Explanation: A GET subcommand was
executed, and one or more of the
inserted lines was truncated or spilled.
System Action: RC = 3.
Lines are spilled or truncated depending
on SET SPILL ONIOFFIWORD.

System Action: The subcommand is
not executed.
User Response: Issue a SET TRUNC
subcommand so that at least eight
characters separate the truncation
column and the logical record length.

User Response: None.

564W
561E

Records {truncated Ispilled}
Records {truncated Ispilled}

Cursor is not on a valid data field

EOF reached
Explanation: A GET subcommand was
executed, and lines were inserted up to
the end of the file. This message is also
issued for the JOIN subcommand.

Explanation: A command was issued
with the CURSOR or SCHANGE option,
and the cursor was not on a file line, or
the cursor or column specified was
outside the current zones.

System Action: RC = 1 (JOIN).
User Response: None.

System Action: RC = 1 or 3.
RC = 1 for JOIN CURSOR
RC = 3 for SI, SPLIT CURSOR, and SOS
System Action: The subcommand is
not executed.
User Response: Reposition the cursor
and reissue the subcommand.

565W

EOF reached; records
{truncated Ispilled}
Explanation: A GET subcommand was
executed, and lines were inserted up to
the end of the file. However, one or
more lines were truncated or spilled.
System Action: RC = 3.
Lines are spilled or truncated depending
on SET SPILL ONIOFFIWORD.
User Response: None.

Conversational Monitor System (CMS) Messages

383

DMS
566E

Logical screen (sll,swl,shl,svl) is
outside the virtual screen

System Action: RC = 5.
The macro is not executed.

Explanation: The screen defined by
(sll,swl,shl,svl) is outside the bounds of
the virtual screen.

User Response: Type a 'CHANGE' or
'CLOCATE' subcommand in the
command line and then press the PF /P A
key assigned to SCHANGE.

System Action: RC = 5.
The subcommand is not executed.
570W
User Response: Correct the values and
reissue the command.

567E

Update ft specified in the UNTIL
option field not found
Explanation: The 'UNTIL' option was
specified. However, the filetype
specified in this field was never found
while applying the updates.

Logical screens (sll,swl,shl,svl)
and (s12,sw2,sh2,sv2) overlap each
other

System Action: None.
Explanation: The screen defined by
(sll,swl,shl,svl) somehow overlaps the
screen defined by the parameters
(sl2,sw2,sh2,sv2).

User Response: None.

5711
System Action: RC = 5.
The subcommand is not executed.

Explanation: An XEDIT command or
one of the following XEDIT
subcommands was executed: XEDIT,
PUT, or PUTD. The fileid specified a
file that did not exist on one of your
accessed disks.

User Response: Correct the values and
reissue the command.

568E

Subcommand not valid with this
screen definition

System Action: None.

Explanation: The subcommand that
was issued is not valid in this screen
definition.

User Response: None.

572E
System Action: RC = 5.
The subcommand is not executed.
User Response: Do not use this
subcommand in this screen definition.

569E

NoCHANGEorCLOCATE
subcommand specified
Explanation: The PF /P A key assigned
to the SCHANGE macro was pressed,
but no 'CHANGE' or 'CLOCATE'
subcommand has been typed in the
command line and the LASTLORC
buffer does not contain a 'CHANGE' or
'CLOCATE' subcommand.

384

VM/SP System Messages and Codes

Creating new file:

Terminal error; data changed to
uppercase
Explanation: An error occurred when
the editor was reading from the CMS
console stack.
System Action: A 'SET CASE
UPPERCASE' subcommand is executed,
and the editor attempts to read the data
again.
User Response: If the read was
successful, you can reissue the SET
CASE subcommand if desired.
Otherwise, contact your system support
personnel for assistance.

DMS
5731

Input mode:

the following: non-numeric, zero, not in
ascending order.

Explanation: An INPUT or REPLACE
subcommand was executed.

System Action: RC = 5.
The subcommand is not executed.

System Action: The editor leaves edit
mode and enters input mode.
User Response: You can enter new
lines into the file, or enter a null line to
return to edit mode.

574E

User Response: Correct and reissue
the subcommand.

576E

CHANGE not valid {with
CLOCATE Iafter cursor
movement}

Explanation: A SET VERIFY
subcommand was issued, and the total
width of the 'startcoI' and 'endcoI'
operands is greater than the screen size
(on a typewriter terminal the maximum
screen size is 132); or a LEFT or
RGTLEFT subcommand was issued, and
the total value of 'n' (when added to the
value of 'n' specified in previous LEFT
or RIGHT subcommands, if any) exceeds
the logical record length of the file.

Explanation: One of the following
occurred:
1.

The SCHANGE macro was executed
with a CLOCATE subcommand
typed in the command line or saved
in the LASTLORC buffer. Then, the
PF key set for the selective change
was pressed.

The PF key assigned to the
SCHANGE macro was pressed, and
a CHANGE subcommand is typed in
the command line or saved in the
LASTLORC buffer. The cursor was
moved, and then the PF key set for
the selective change was pressed.

System Action: The change is not
made.
User Response: None.

575E

Invalid [argument or]
{JOINISPLITI
TABSIVERIFYIZONE} column(s)
defined
Explanation: The subcommand
displayed in the message was issued,
and the columns specified were one of

{Total verify width exceeds screen
size (nn) ITotal offset exceeds
LRECL (nn)}

System Action: RC=5.
The subcommand is not executed.
User Response: Correct and reissue
the subcommand.

577E

File has been changed; type
QQUIT to quit anyway
Explanation: A QUIT or CANCEL
subcommand has been issued, and a file
has been changed during the editing
session.
System Action: RC = 12.
The subcommand is not executed.
User Response: Issue a 'QQUIT'
subcommand if you do not wish to save
the changes made during the editing
session. Issue a 'FILE' subcommand if
you want the changed file to be written
to disk.

Conversational Monitor System (CMS) Messages

385

DMS'
578W

macro name macro is not currently
in storage

shift-in (SI) control character or a
shift-in (SI) control character and no
matching shift-out control
character. These control characters
must be paired properly or the
string is considered invalid.

Explanation: An XEDIT PURGE
subcommand was issued for 'macro' but
no macro with the given name was
currently in storage.
•
System Action: RC= 3.
No macro is purged from storage.
User Response: Correct the name and
reissue the subcommand.

579E

The characters between the SO
(shift-out control character) and the
SI (shift-in control character) must
be double-byte characters. If the
number of character positions is not
even between the SO and SI, then
the string does not contain
double-byte characters.

Records truncated to nn when
added to In It 1m
Explanation: A PUT(D) subcommand
was issued, and the lines added to the
existirig fixed format file were truncated
at the column indicated.

•

System Action: RC = 3.
The lines inserted into the file specified
were truncated at column 'nn'.

Invalid string: message
first byte:
second byte:

Explanation: A subcommand was
issued and the string specified was not
valid. In extended mode (SET ETMODE
ON), strings are validated regarding the
shift-out (SO) and shift-in (SI) control
characters. 'message' is one of the
following detected errors:
•

•

X '41' - X'FE'
X '41' - X'FE'

X '4040' (DBCS
blank)
X '0000' (DBCS null)
System Action: RC = 5.
User Response: Correct the string and
reissue the subcommand.

SHIFT-OUT (SO) IS NOT A
VALID DELIMITER.
The first character in certain
operands is a self-defining delimiter.
the shift-out (SO) control character
is not a valid delimiter for targets or
strings.

386

INVALID DOUBLE-BYTE
CHARACTER(S).
The characters between the shift-out
and shift-in control characters must
be valid double-byte characters. The
range of hex codes that may be used
to represent characters in the
Double-Byte Character Set are as
follows:

User Response: None.

580E

ODn NUMBER OF
CHARACTERS BETWEEN SO
AND SI.

581E

Subcommand is not valid in
extended mode

UNMATCHED SHIFT-OUT (SO)
AND SHIFT-IN (SI).

Explanation: A subcommand was
issued that is not valid in extended
mode (SET ETMODE ON). The
following subcommands are not valid in
extended mode.

A string was specified which
contained a shift-out (SO) without a

COMPress MErge
COVer lay Over lay

VM/SP System Messages and Codes

DMS
EXPand POWerinp
HEXType SORT

No line(s) changed

585E

Explanation: One of the following
occurred:

When ETMODE is ON, the SET
VERIFY option will only display the
first pair of verify columns.

•

A subcommand was issued to locate
and change a string of character(s),
but the string was not located.

•

A subcommand was issued that
attempted to modify the null TOP
OF FILE or END OF FILE line.

A subcommand was issued, but the
column pointer was at the the TOP
OF LINE (TaL) or END OF LINE
(EOL), (e.g. CINSERT,
COVERLAY).

System Action: RC = 3.
User Response: None.

582S

Editor abend
Explanation: The editor has failed
because: an error occurred while the
editor was reading from the CMS
console stack, or the editor was unable
to allocate a save area.
System Action: The system is
terminated abnormally.

System Action: RC = 1 or 4.
RC=l for JOIN, SPLIT, and SPLTJOIN
subcommands.
The change is not made.

User Response: Issue the XEDIT
command again. If the problem persists,
contact your system support personnel.

User Response: None.

586E
5831

EOF:
Explanation: On a typewriter terminal
or a display terminal used in typewriter'
mode, the line pointer has moved to the
null END OF FILE line.
System Action: None.
User Response: None.

5841

{String not foundlNot found [on
screen]}
Explanation: A FIND, FINDUP,
NFIND, NFINDUP, or HELP
CLOCATE subcommand was issued, and
the specified 'text' operand is not found.
The SCHANGE macro was invoked, the
CHANGE or CLOCATE subcommand
was issued, and the specified 'string'
(first operand for CHANGE and only
operand for CLOCATE) is not found
within the screen width.

TOF:
System Action: RC = 2.
Explanation: On a typewriter terminal
or a display terminal used in typewriter
mode, the line pointer has moved to the
null TOP OF FILE line.
System Action: None.
User Response: None.

User Response: For the SCHANGE
macro and the CHANGE or CLOCATE
subcommand, if the 'string' not found is
outside the screen width, the RIGHT or
LEFT subcommand can be issued to
change the screen so that the string will
be located.

Conversational Monitor System (eMS) Messages

387

DMS
5871

For NUCXLOAD a FILEDEF command
identifying the load library must be
issued prior to calling NUCXLOAD.

XEDIT:
Explanation: This message is displayed
as a result of one of the following:
•
•
•

System Action: RC = 32.
The subcommand is not executed.

you return to EDIT mode from
INPUT mode
you invoke XEDIT and you don't
have a PROFILE macro
you enter a null line from a
typewriter terminal

User Response: The System Product
Editor uses the data definition name
'SYSIN' to read the OS data set.
Therefore, you must issue a FILEDEF
command with 'SYSIN' specified as the
'ddname' before issuing the XEDIT
command or subcommand. Use CMS
subset to enter the FILEDEF command.

System Action: None.
User Response: None.

588E

For NUCXLOAD, if you are loading a
module from a CMS load library, issue a
FILEDEF command identifying the load
library.

Prefix subcommand waiting ...
Explanation: A SET RANGE or SORT
subcommand was issued and a prefix
subcommand or macro was still pending
in the file. (This is indicated by '''xxx'
pending ... " in the status area for the
file.) Alternatively, a SET RANGE or
SORT subcommand was issued from a
prefix macro.

590E

Explanation: An XEDIT command or
XEDIT or LOAD subcommand was
issued for an OS data set that is too
large for your virtual storage size.

System Action: RC = 8.
The subcommand is not executed.
User Response: You can issue a
RESET subcommand to remove the
pending prefix subcommands or macros,
or you can complete the execution of
the pending prefix subcommands or
macros and then reissue the
subcommand or macro from the
command line.

589E

Missing FILEDEF for DDNAME
ddname
Explanation: For XEDIT, a command
or subcommand was issued for a file
that resides on an OS disk, but no
FILEDEF command has been issued.

Dataset too large

System Action: RC = 88.
User Response: Use the CP command
DEFINE to increase the virtual storage
size, and reissue the XEDIT command or
XEDIT or LOAD subcommand.
Initialize CMS again.

591E

Open error on SYSIN
Explanation: An XEDIT command or
subcommand was issued for a data set
not supported by CMS. This message
usually follows message DMSSOP036E.
System Action: RC = 32.
The subcommand is not executed.
User Response: Refer to message
DMSSOP036E.

388

VM/SP System Messages and Codes

DMS
592W

Wrapped ....

596E

Explanation: While executing the
search for a target, or while executing a
subcommand, the search continued past
the end of file (or top of file) and
stopped when the line where it started
was reached again.

This module must be called within
the editor
Explanation: An attempt was made to
execute DMSXMS from CMS.
System Action: RC = 88.
User Response: Call this module from
within the editor.

System Action: None.
User Response: None.
597E
593E

{Nolnn} lines merged, nn line(s)
{truncated Ispilled}

Explanation: An XEDIT command or
XEDIT or LOAD subcommand has been
issued with a 'MERGE' and 'CTL'
option specified, and one of the updates
in the control file contains a './S'
card(s).

Explanation: In executing the
MERGEd subcommand, some lines were
truncated or spilled.
System Action: RC = 3.
Lines are spilled or truncated depending
on SET SPILL ONIOFFIWORD.
User Response: To avoid truncation of
subsequent lines, change the truncation
setting by issuing a SET TRUNC
subcommand. SET SPILL also allows
you to avoid losing any characters by
truncation.

594E

Unable to merge updates
containing ./S cards

System Action: RC = 32.
The command is not executed.
User Response: Remove the 'MERGE'
option and reissue the command.

598S

Unable to build update file:
internal list destroyed
Explanation: A FILE or SAVE
subcommand has been issued, and the
editor was unable to build the update
file.

File fn ft fm already exists; use
FFILE/SSA VE
Explanation: Attempted to FILE or
SAVE a file and found that a different
copy of the file was already on disk.

System Action: RC = 7.
The command is not executed.

System Action: RC = 3.
The subcommand is not executed.

User Response: Call your system
support personnel for assistance.

User Response: Use a different fileid,
or use FFILE or SSAVE to overlay the
other file on the disk.

599S

Unable to build update file:
serialization destroyed
Explanation: A FILE or SAVE
subcommand has been issued and the
editor was unable to build the update
file because the serialization field
contains a non-numeric character. This
situation may have been the result of a

Conversational Monitor System (CMS) Messages

389

DMS
previous update that did not include
serialization.

603R

System Action: RC = 7.
The command is not executed.

FO RMA T will erase all files on
disk mode(udeu). Do you wish to
continue? Enter 1 (YES) or 0 (NO)
Explanation: This message is a
reminder that the formatting process
erases existing files.

User Response: Verify that all the
applied updates include serialization.

System Action: The system waits for a
response.
First selection level (nn) cannot
be greater than second selection
level (nn)

600E

Explanation: The 'SET DISPLAY nl
n2' was issued and the n2 was less than

User Response: Enter 1 (or "YES") or

°(or "NO").
604R

Enter sort fields:

nl.

601R

System Action: RC = 5.
The subcommand is not executed.

Explanation: The command requires a
list of sort fields on which to perform a
sort.

User Response: Correct the operands
and reissue the subcommand.

System Action: The system waits for a
response.
User Response: Enter pairs of
numbers, separated by a blank, defining
the starting and ending character
positions of sort fields within the
records.

Enter specification list:
Explanation: The specification list
that is to be entered in conjunction with
the SPECS option is requested.
System Action: The system waits for a
response.
User Response: Enter the specification
list.

602R

Enter translation list:
Explanation: The translation list that
is to be entered in conjunction with the
TRANS option is requested.
System Action: The system waits for a
response.
User Response: Enter the translation
list.

390

VMjSP System Messages and Codes

605R

Enter disk label:
Explanation: You are requested to
enter a label for the disk being
formatted. The label will be written on
the disk at cylinder 0, track 0, record 3.
System Action: The system waits for a
response.
User Response: Enter a one- to
six-character label for the disk. If you
enter less than six characters, the label
is left-justified and padded with blanks.
If you enter a null line, the system
displays the message DISK REMAINS
UNCHANGED.

(

DMS
606R

System disk address = vdev

If you fail to enter either 1, YES, 0, or
NO, the message

Explanation: "vdev" designates the
device address of the system disk
(S-disk). On this disk CMS expects to
find all CMS system information and
programs not contained within the CMS
nucleus, such as the disk-resident
command modules. If the CMS nucleus
is written on this disk, then vdev is also
the IPL device address.

DMSINI081E Invalid reply;
enter 1 (YES) or 0 (NO)

is issued. Message DMSINI607R is
reissued and you may enter a valid
response.

608R

System Action: The system waits for a
response. If you enter an invalid device
address, the message
DMSINQ079E INVALID DEVICE ADDRESS REENTER

is issued. Message DMSINI606R is
reissued, and you may enter a valid
device address.
If you enter a null line, 190 is assumed
to be the system disk address.

Once the system disk address entered is
accepted, message DMSINI615R is
issued.
User Response: Enter a valid device
address or a null line.

607R

Rewrite the nucleus? Enter 1
(YES) or 0 (NO)

IPL device address

vdev

Explanation: "vdev" designates the
device address on which the CMS
nucleus is to be written. If the system
disk and the IPL device are to be the
same, you need only enter a null line.
System Action: The system waits for a
response.
If you enter an invalid device address,
message
DMSINI079E INVALID DEVICE ADDRESS REENTER

is issued. Message DMSINI608R is
reissued and you may enter a valid
device address.
If the IPL device designated is not
currently defined, is not in read/write
status, or is an unsupported device type,
message
DMSINI082E IPL DEVICE ERROR - REENTER

Explanation: Your response to this
message determines whether or not a
copy of the CMS nucleus is written onto
disk.
System Actiori: The system waits for a
response.

is issued. Message DMSINI608R is then
reissued. At this time, you may enter CP
mode by signaling attention, and
determine the status of the designated
device by entering the CP command
QUERY VIRTUAL vdev

User Response: Enter either "I" or
"0." If you enter 0, a copy of the CMS
nucleus is not written onto disk. The
remaining questions in generating a
new CMS nucleus are skipped and
control is passed to the CMS
initialization routine.

Then take the corrective action
necessary to define the device for your
virtual machine or to access it in
read/write status. Reenter CMS mode
by issuing the CP command
BEGIN

If you enter 1, message DMSINI608R is
issued.
Conversational Monitor System (eMS) Messages

391

DMS
cylinder or block number, or IPL the
CMS system and format the specified
IPL device with the RECOMP option.
Once the nucleus cylinder or block
address is accepted, message
DMSINI610R is issued.

You must then reenter the device
address.
Once the IPL device address is accepted,
message DMSINI609R is issued.
User Response: Enter a valid device
address or a null line.

609R

Nucleus (CYL or BLK) address
nnnn
Explanation: "nnnn" designates the
cylinder address or FB-512 block
number (on the device entered in
response to message DMSINI608R) on
which the CMS nucleus is to be written.
nnnn must be between 001 and m-1
where m equals the number of cylinders
or blocks on the disk, the cylinders or
blocks on a disk being numbered from 0
to m. nnnn must be entered in decimal.
For an FB-512 device, the block number
must be a multiple of 256 and 256 blocks
must be available at that location to
form an FB-512 extent.
System Action: The system waits for a
response.
If you do not enter a valid decimal

cylinder or block number, the message
DMSINI080E INVALID {CYLIBLK}
NUMBER - REENTER

is issued, message DMSINI609R is
reissued, and you may enter a valid
cylinder or FB-512 block number.
If the cylinder or FB-512 block(s)

specified is not greater than the number
already in use on the device (as
indicated in the file directory), the
message
DMSINI083E NUCLEUS {CYLIBLK}
SPECIFICATION
UNACCEPTABLE, ERROR IX'

is issued. Message DMSINI609R is
reissued. You may respond with a larger

392

VM/SP System Messages and Codes

lJser Response: Enter a valid cylinder
address.

610R

Also IPL (CYL or BLK) O? Enter 1
(YES) or 0 (NO)
Explanation: The initial IPL text is
always written on the same cylinder or
FB-512 block as the CMS nucleus, that
is, the cylinder or FB-512 extent
designated in response to message
DMSINI609R. (The initial IPL text is a
bootstrap program that reads in the
nucleus from the designated cylinder or
block.) If it is not also written on
cylinder or plock 0, you must enter the
cy linder or block number whenever an
IPL is issued for the system being
generated. For more information, see
the IPL command in the VMjSP CP
Command Reference.
System Action: If you do not enter 1,
YES, 0, or NO, the message
DMSINI081E Invalid reply;
enter 1 (YES) or 0 (NO)

is issued. Message DMSINI610R is
reissued and you may enter a valid
response.
If you enter 1, the initial IPL text is

written on cylinder or block 0 as well as
on the cylinder or block designated in
response to message DMSINI609R.
If you enter 0, the initial IPL text is

written only on the cylinder or block
designated in response to message
DMSINI609R.
If you enter either 1 or 0, message

DMSINI611R is issued.
User Response: Enter 1 or O.

(

DMS
611R

614E

Enter version identification:
Explanation: Thirty-two bytes of
information, including blanks, can be
entered to specifically identify the
version and level of CMS; this
information is displayed or printed out
when an IPL CMS is executed. The
default identification (specified by a
carriage return) is:

Explanation: A P A Key was pressed
and the screen was cleared to display a
pending message. If any changes were
made on the screen before the P A Key
was pressed, those changes were lost.

VM/SP REL3 mm/dd/yy hh:mm

System Action: RC = 8.
Any screen changes are lost.

where mm/dd/yy is the month, day, and
year and hh.mm is the hour and minute
the CMS nucleus was created.

User Response: See SET FULLREAD
documentation for information on how
to use P Akeys safely.

System Action: The system waits for a
response.

615R

User Response: Enter version
identification information or a null line.

612R

Enter installation heading:

VM/SP CONVERSATIONAL MONITOR SYSTEM

System Action: The system waits for a
response.
User Response: Enter up to 64
characters of identifying information, or
a null line.

TAPE must be invoked as a
nucleus extension
Explanation: The command was
invoked as a nucleus extension.
System Action: RC = 40.
System status remains the same.

Y -disk address = vdev

Explanation: "vdev" designates the
device address of the system disk
extension (Y -disk). On this disk, CMS
expects to find all CMS system
information and programs not contained
within the CMS nucleus and not on the
S-disk, such as disk-resident command
modules. If the CMS nucleus is written
on this disk, then vdev is also the IPL
device address. (It is not required that
you have a Y-disk.)

Explanation: Sixty-four bytes of
information, including blanks, can be
entered to serve as an installation
standard heading at the beginning of
each output file. The default heading
(specified by a null line) is:

613E

Screen modifications lost. See
'SET FULLREAD' to use P Akeys
safely.

System Action: The system waits for a
response.
If you enter an invalid device address,
the message
DMSINQ079E INVALID DEVICE ADDRESS REENTER

is issued. Message DMSINI615R is
reissued, and you may enter a valid
device address.
If you enter a null line, "19E" is
assumed to be the system disk extension
address.
If you do not want a Y-disk, then do not
have a disk 19E in your directory entry,
and enter a null line.

User Response: Notify the system
programmer that an error occurs when
you invoke this command.

Conversational Monitor System (CMS) Messages

393

DMS
Once the system disk extension address
is accepted, message DMSINI607R is
issued.

was in error. If they are correct, then
some program violated the SCBLOCK
defining the nucleus extension after
NUCXMAP displayed it. This program
should be identified and corrected.

User Response: Enter a valid disk
address or a null line.
618E
616W

Explanation: An attempt to establish a
function as a CMS nucleus extension
failed because of a system error, or
because the level of CMS does not
support extensions to its nucleus.

Explanation: The named nucleus
extension does not exist.
System Action: RC = 28.

System Action: RC = 13 or RC = 4n
where 'nn' is NUCEXT's return code to
the calling module. Execution of the
command that called NUCEXT
terminates.

User Response: Check the spelling of
'name'.

617E

NUCEXT failed

name does not exist

Error code nn from DMSFRET
while unloading module module
Explanation: An invalid DMSFRET
request was made while unloading the
specified module. An error was made in
calling a nucleus extension or the
created nucleus extension was damaged
in some way. NUCXDROP used the
BYTES associated with the module
name as the number of bytes to free,
starting at the ORIGIN address. One or
both of these fields have been destroyed.
The error code indicates the type of
error that occurred. The error code
meanings are:

User Response: Verify that the level of
CMS being used contains support for
nucleus extensions; take action
indicated by return code 'nn' as
appropriate.

619E

Module module not found
Explanation: The module requested
does not exist.
System Action: RC = 28.
User Response: Recheck the command.

Code Meaning
5
The number of doublewords
specified was 0 or negative.
6
The block of storage being released
was never allocated by DMSFREE.
7
The address given for the block
being released is not doubleword
aligned.
System Action: RC = 3.
The system makes no further attempt to
release the storage block.
User Response: NUCXMAP may be
used after defining a nucleus extension
to display the origin and length of the
loaded program. If these are incorrect,
the call defining the nucleus extension

394

VM/SP System Messages and Codes

620E

RTABLE error on line nnnn:
message
Explanation: The multiple variations
of 'message' are explained below.
System Action: In each case, the
system action is:
The programmable operator facility
terminates.

User Response: In each case, the user
response is:

DMS
-

Correct the routing table and reload
it or reinvoke the Programmable
Operator Facility.

•

The checking interval specified
has more than three numerals.

DUPLICATE NODEIDS
SPECIFIED

MESSAGES:
•

Explanation: An RT ABLE
parameter statement is incorrectly
specified, or if record found
preceding the first ROUTE
statement does not begin with
"TEXTSYM," "HOSTCHK,"
"PROPCHK," "LGLOPR," or
"LOGGING."
•

Explanation: A nodeid is specified
more than once on one PROPCHK
statement or on more than one
PROPCHK statement.

INVALID PARAMETER
STATEMENT

•

Explanation: Parameters other
than distinct single characters are
given in the TEXTSYM record. If
"more than 3 are given,
"INCORRECT NUMBER OF
PARAMETERS" is issued.

INVALID TEXT FIELD
Explanation: TESTSYM characters
are used incorrectly in the text field:

•

A not-symbol that directly
precedes a separator or does not
immediately follow a separator
character was found.

•

The response wait (second
interval) value exceeds the
checking interval (first interval)
value.
The checking interval or waiting
interval value is not greater
than zero.
-

The waiting interval specified
has more than two numerals.

PROPCHK BEFORE LGLOPR
STATEMENT
Explanation: A PROPCHK
statement appears in the routing
table before a LGLOPR statement.
The PROPCHK record requires the
nodeid of the logical operator given
in the LGLOPR record.

INVALID INTERVALS
SPECIFIED
Explanation: On a PROPCHKor
HOSTCHK statement:

HOSTCHK BEFORE LGLOPR
STATEMENT
Explanation: A HOSTCHK
statement appears in the routing
table before a LGLOPR statement.
The HOSTCHK record requires the
nodeid of the logical operator given
in the LGLOPR record.

The first non-blank character in
the text field is not a
blank-character separator or an
arbitrary-character separator.
Two separator characters are
found next to each other.

INVALID SEPARATOR
CHARACTERS

INV ALID OPERANDS
SPECIFIED
Explanation: The Programmable
Operator Facility does not recognize
the operands specified (on such
statements as LOGGING).

•

LOGICAL OPERATOR NAME
NOT FOUND
Explanation: The id specified for
the logical operator in the LGLOPR

Conversational Monitor System (CMS) Messages

395

DMS
statement cannot be found on the
system, or in the "userid NAMES"
file.

•

Explanation: One of the following
fields does not start in its proper
column: userid, nodeid, action
routine name, or action routine
parameter.

INVALID COLUMN FIELDS

•

Explanation: Any of the following
is true of the column fields in the
routing entry:
The starting or ending column
field is greater than 240 (the
maximum length of a CP
message).

•

The starting or ending column is
equal to zero.

System Action: In each case, the
system action is:

INCORRECT NUMBER OF
PARAMETERS

NON-NUMERIC VALUE
SPECIFIED
Explanation: A non-numeric
character was specified for a
numeric value in one of the
following fields of the routing table:
the starting column, the ending
col umn, the message type, or the
checking interval parameters on the
HOSTCHK or PROPCHK records.

396

Bad plist: message

621E

Explanation: The multiple variations
of 'message' are explained below.

The LGLOPR record has no
parameter.
The LGLOPR record has more
than 2 parameters.
The TEXTSYM record does not
have exactly 3 parameters.
The HOSTCHK record does not
have exactly 2 parameters.
The PROPCHK record has less
than 3 parameters.
The LOGGING record has more
than 1 parameter.

•

Explanation: The logical operator's
nodeid is included in a PROPCHK
record.

The ending column is less than
the starting column.

Explanation: This message is
issued if:

•

HOSTID IN PROPCHK RECORD

MISALIGNED FIELD

VM/SP System Messages and Codes

RC=24.
Execution is terminated.

MESSAGES:

•

{EXECIOIQUERY} MUST BE
INVOKED AS A NUCLEUS
EXTENSION
Explanation: {EXECIOIQUERY}
was invoked by an assembler
program and passed the incorrect
parameter list for a nucleus
extension call.
User Response: Make sure you are
passing a parameter list for a
nucleus extension.

•

DISK 'argument' ARGUMENT IS
MISSING
Explanation: The missing
'argument' is FILENAME or
FILETYPE. These are required
arguments when DISKR or DISKW
operations are specified.
User Response: Reissue the
command with the disk argument.

(

DMS
•

INPUT FILE 'fileid' DOES NOT
EXIST
Explanation: The indicated file
cannot be found.

User Response: Check the syntax
of the command.

•

User Response: Check to make
sure that the fileid has been entered
correctly.

•

Explanation: An invalid value was
specified for the indicated option.
For example, if 'Case3' is used in a
call to EXECIO, the message will
read ' ... VALUE 3 NOT VALID FOR
CASE OPTION.'

INVALID POSITIONAL
ARGUMENT 'argument'
Explanation: More than the
maximum number of positional
arguments (i.e., arguments before
the left parenthesis marking the
start of the options) were specified.
The number of positional arguments
allowed depends on the second
operand (DISKR, etc.) on the
command line.

User Response: Check the syntax
of the command.

•

User Response: Check the syntax
of the command.

•

UNKNOWN OPTION NAME
'name'

User Response: Check to make
sure that you have not misspelled an
option name.
V ALUE MISSING AFTER
'option' OPTION
Explanation: There is not value
specified after the indicated option,
yet one is required. For example,
the MARGINS option requires that
two values follow it. If one or both
of these is missing, the message is
produced.

'option' OPTION NOT VALID
WITH 'operation' OPERATION
Explanation: The indicated option
cannot be specified with the
indicated operation. For example,
the FINIS option is not valid if
PRINT is specified as the second
operand on the command line.

Explanation: The indicated option
name is not recognized by EXECIO.

•

'option' OPTION IS NOT VALID
WITH 'option' OPTION
Explanation: Two mutually
exclusive option values were
specified. For example, only one
input selection option is allowed;
therefore, if both a LOCATE and a
FIND option are specified, this
message will be issued.

This message is a likely result if the
left parenthesis option delimiter is
missing from the command line.
User Response: Check to make
sure that you have specified the
correct positional arguments, and
that you have not omitted the
parenthesis.

VALUE 'value' NOT VALID FOR
'option' OPTION

User Response: Check the
command syntax.

•

STRING OPTION WITH
LINES=* IS VALID ONLY FOR
CP OPERATION
Explanation: The STRING option
with LINES = * is valid only for a
CP operation.
User Response: Check the
command syntax.

Conversational Monitor System (eMS) Messages

397

DMS

•

DEVICE AND LINES
ARGUMENTS AnE REQUIRED

Explanation: The filemode operand
is required for a DISKW operation.
The DISKW operation may cause
writing to any disk to which the
user has write access.

Explanation: The first two EXECIO
command line operands are always
required.

User Response: Check the
command syntax.

Vser Response: Check the
command syntax.

•

INV ALID VALUE 'value' FOR
NUMBER OF LINES

•

E~planation: The number of lines
specified to be processed must be
either a non-negative integer or an
asterisk.

Explanation: For a DISKW
operation, if the record format
(recfm) is specified, it must be either
F or V. V is the default value.

User Response: Check the value
specified for the number of lines to
be processed.

User Response: Check the
command syntax.

MISSING 'DEVICE' ARGUMENT

•

User Response: Check the
command syntax.

User Response: Check the record
length argument.

INVALID 'DEVICE' ARGUMENT
'argument'
Explanation: The only valid values
for the 'DEVICE' argument are CP,
CARD, DISKR, DISKW, PUNCH,
PRINT, and EMSG.

•

lNV ALID VALUE 'value' FOR
DISK FILE LINE NUMBER
Explanation: The line number
specified is negative or a
non-numeric value.
User Response: Check the
comma:p.d syntax.

•
398

DISl{ l?ILEMODE REQUIRED
FOR DISKW

VM/SP System Messages and Codes

FILE FORMAT SPECIFIED
'recfm' DOES NOT AGREE
WITH EXISTING FILE FORMAT
'recfm'
Explanation: The record format of
a record to be written into an
existing disk file is inconsistent with
that file.

User Response: Check the
command syntax.

•

INV ALID RECORD LENGTH
ARGUMENT 'Irec1'
Explanation: For a DISKW
operation, if the logical record
length (Irecl) is specified, the value
must be less than 256 and greater
than O.

ExplanatiQn: The EXECIO
command requires a 'DEVICE'
argument.

•

INVALID RECORD FORMAT
'recfm' -- MUST BE EITHER F
ORV

User Response: Check the record
format specified against that of the
file.

•

FILE LRECL SPECIFIED 'lrecl'
DOES NOT AGREE WITH
EXISTING FILE LRECL 'lrecl'
Explanation: The logical record
length of a record to be written into

DMS
an existing disk file is inconsistent
with that file.

User Response: Check the
command syntax.

User Response: Check the logical
record length against that of the
file.
•

•

Explanation: Using the EXECIO
command, the maximum length of a
variable name for the VAR or STEM
option was exceeded. The maximum
for the VAR option is 250
characters. The maximum for the
STEM option is 240 bytes.

EXECIO OPTIONS ONLY
ALLOWED WITH EXTENDED
PLIST
Explanation: If any options are
used in the call to EXECIO, an
extended plist must be supplied.
The EXEC 2 interpreter always
supplies an extended plist, and CMS
supplies an extended plist for all
commands read from the console.
The most likely reason for this
message is an attempt to invoke
EXECIO (with options) from a CMS
EXEC file. Another reason may be
invocation of EXECIO from a user
program that doesn't supply an
extended plist.
User Response: You may provide
the extended plist by converting the
CMS EXEC file to an EXEC 2 file.
Or EXECIO may be invoked through
a separate EXEC 2 file called from
the CMS EXEC file. If called from a
program, the extended p1ist should
be set up according to the
documentation in the VM/ SP eMS
for System Programming.

•

INVALID CHARACTER IN FILE
IDENTIFIER

INVALID EXEC VARIABLE
NAME

User Response: Use a shorter
length variable name.
•

V AR OPTION WITH LINES > 1
IS INVALID
Explanation: The EXECIO
command was issued with the V AR
option and the number of lines
specified was greater than 1.
User Response: Either change the
lines operand to 1 or use the STEM
option.

Insufficient [free] storage
[message]

622E

Explanation: Insufficient storage was
available for task to execute a required
function. One possible cause of this
error message is that a program issuing
NUCXLOAD is in a loop. If present,
'message' is one of the following:

Explanation: The specified fileid
contains a character that is invalid
for the CMS file system.

•

for msgline
No Return Code
Execution continues.

User Response: Check the
description of the command format
and reissue the command uRing
valid characters.

•

for line spill
RC=l
Execution continues.

•

for PFKEYIP AKEY
No Return Code.
Execution continues.

INVALID MODE 'mode'
Explanation: More than two
characters were specified for the
mode.

Conversational Monitor System (CMS) Messages

399

DMS

•

400

System Action: Execution halts.

for synonyms
No Return Code.
Execution continues.

•

for I/O buffer
No Return Code.
Execution continues.

•

for extract
RC = 104
Execution of command
terminates.

•

for EXECCOMM
RC=104
Execution of command
terminates.

•

for EXECIO
RC=41
The request function
is not perform,ed.

•

for NAMEFIND
RC=41
Execution of the command
is terminated.

•

for reading map
RC = 104
Execution of the command
is terminated.

•

no table made
RC=41
DMSGLO created no global variable(s)
in storage for the GLOBALV
command.

•

(nn entries)

RC=41
DMSNXM (NUCXMAP) requires
one word of storage for each
nucleus extension.
The command is terminated, no
map is generated.

•

for processing screen changes
last screen modifications
are not processed.

•

for COPYKEY
image of vscreen is not placed
in printer spool.

VM/SP System Messages and Codes

User Response: Check a program
issuing NUCXLOAD for a possible loop
that is not terminating properly. More
free storage may be obtained by
releasing a disk (to recover the space
used for the file directory) or deleting a
nucleus extension. Alternatively, re-ipl
CMS after defining a larger virtual
storage size for the virtual machine.

622W

Insufficient free storage for
NAMEFIND buffer; processing
continues
Explanation: Insufficient storage was
available for NAMEFIND to create a
buffer containing information for the
NAMES file. The requested buffer size,
or the size of the file, was too large in
terms of the available free storage.
System Action: No buffer was created
and processing continues reading the
NAMES file from the disk. The buffer
size is set to 0, so that future
invocations of NAMEFIND will not
cause this warning to be displayed.
User Response: None.

623S

{ModuleIPhase} cannot be loaded
at location hexloc--this area is
available for system use only
Explanation: This error can occur
because:
1.

The module or phase is too large to
be loaded in the user area (it is
attempting to overlay the CMS
nucleus which resides at the end of
the user area).

The 'ORIGIN' option was specified
incorrectly on the LOAD command.
The origin specified is either
causing the module or phase to 1)
overlay the CMS nucleus, or 2)
overlay the Free Storage Pointers

(

DMS
(as the origin specified is the
beginning address of the segment
that follows the CMS nucleus).
System Action: RC = 88.
The command that was executed to
perform the load is terminated.

User Response: Reorganize the text
files so that fewer than 16,384 items
require relocation, then reissue the
command.

626E

User Response: If the 'ORIGIN' option
was incorrect, reissue the command
with the correct origin. If the module
or phase is too large, contact your
system support personnel, or use the
CMS nucleus 'CMSL' that is defined at
a higher location, if it is available on
your system.

6241

Invalid action routine parameter
parameter
Explanation: The parameter passed to
module DMSPOR in the routing table
contains an invalid routine name.
System Action: None.
User Response: Correct the routing
table entry. Make sure that the
parameters passed to module DMSPOR
contain a valid action routine name.
The valid action routine names that can
be specified with DMSPOR are:

No nucleus extensions are found
Explanation: No nucleus extensions
were located and therefore they cannot
be mapped for NUCXMAP.

GET
QUERY
SET

System Action: RC = o.

TOFB
TOVM
STOP

User Response: None.
627E
624W

Result is nnnn bytes too large for
CP command buffer

No nucleus extensions are loaded
Explanation: CP returned a response
to a command that is too large to fit
into the buffer provided by module
DMSPOR.

Explanation: No nucleus extensions
have been loaded and therefore cannot
be dropped.

System Action: None (no data
returned).

System Action: RC = 28.
User Response: None.

625S

User Response: If possible, request less
data (for example, as with the DISPLAY
command).

There are too many items that
require relocation to save all of
the RLD information
628E
Explanation: A LOAD or INCLUDE
command was issued with the
RLDSAVE option specified, and more
than 16,384 address constants in the text
file(s) require relocation.
System Action: RC = 104.
Execution of the command is
terminated. The system status remains
the same.

Invalid GLOBALV function
function
Explanation: The function specified on
the GLOBAL V command is invalid or
unknown.
System Action: RC = 4.

Conversational Monitor System (CMS) Messages

401

DMS
User Response: Reissue the command
specifying a valid GLOBAL V function.

629W

System Action: RC = 36.
Execution of the command is
terminated.
User Response: If the spool file is still
in your virtual reader, reissue the
command. If the error persists, contact
your installation support personnel.

Screen modifications may be lost.
Press ENTER key to process
screen changes.
Explanation: Your screen
modifications could not be processed
because your terminal configuration
does not support the CMS command
'SET FULLREAD ON'.

63lE

The PA key just depressed will be
executed. The next time the screen is
read, any screen modifications, which
are not overlayed by the function
executed, will be processed.

{functionlcommand} can only be
executed from an EXEC-2 or
REXX EXEC [or as a CMS
command]
Explanation: The command or
function was not invoked from an
EXEC-2 or REXX exec or from the CMS
command line.

This terminal configuration, which
imposes restrictions on your session,
occurs when going through a
VM/Passthru Facility (5749-RCl) (PVM)
327x Emulator link to another VM
system. These PVM links can be
identified by an'S' to the immediate left
of the nodeid in the PVM selection
screen.

This function or command noted in the
message either requires an extended
parameter list, which is not provided by
CMS EXEC, or a direct interface to the
variables in an EXEC (EXECOMM),
which is only available while an EXEC
2 or System Product Interpreter exec is
active.
System Action: For the XMITMSG
command, RC = 24.

The PVM emulator line driver does not
support the 3270 command 'read buffer'
which is used when FULLREAD is set
on and in processing P A keys.

For the P ARSECMD command, RC = 40.
For all other modules, RC = 4.

System Action: Key pressed is
executed. Screen changes are not
processed.

User Response: Invoke the command
again from and EXEC-2 or REXX exec
or from the CMS command line.

User Response: Press ENTER/PF key
to process screen changes.
632E
630S

Error accessing spool file
Explanation: An error occurred while
accessing the spool file, or the virtual
reader is busy. The reader file may
have been purged by the system, or the
file may have been transferred from
your virtual reader via a TRANSFER
command issued by the originator or the
system operator while the RDR
command was executing.

402

I/O error in EXECIO; rc = nnnn
from command command

VMjSP System Messages and Codes

Explanation: The specified error
return code was obtained by EXECIO
when the indicated command was
invoked. EXECIO will not continue,
but returns the error return code to its
caller. The EXECIO operation may
have partially completed before the
error occurred.

DMS
System Action: RC = Inn, where nn is
the return code from the command
specified in the message text.

634E

Explanation: The NAMEFIND
command was issued without a search
value (i.e., a tag with a value).

RC = 2008, signifying invalid variable
name from the EXECCOMM command.
User Response: Look at the
documentation for the indicated
command to interpret the return code.

633E

System Action: RC = 24.
Processing is terminated.
User Response: Reissue the command
with at least one tag with a value to
indicate what NAMEFIND should
search for.

Too many tags were
encountered--maximum is 64 per
line
Explanation: While searching the
names file, an entry was encountered
that contained more than 64 tags
(overflowing the internal tag tables of
the NAMEFIND command). This record
was not processed correctly by
NAMEFIND.

6351

No entries were found that
matched your search criteria
Explanation: NAMEFIND was unable
to locate an entry that matches the
search criteria specified on the
command line.

System Action: RC = 88.
Processing is terminated.

System Action: RC = 32.
Processing has completed.

User Response: Make sure the entries
in your names file do not have more
than 64 tags.

User Response: None.

636E
633W

No value to search for was
specified

Unsupported type of NET DATA
file

Returned values were truncated
Explanation: The information that was
stacked or displayed at the terminal was
truncated. The stack has a limit of 255
characters; CMS permits on 130
characters to be displayed.

Explanation: A file in the reader is not
able to be read in, because the
RECEIVE command cannot reformat it ..
For example, an OS PDS in NETDATA
format would not be able to be received
in CMS.

System Action: RC = 88.
Processing is completed.

System Action: RC = 88.
Processing is terminated.

User Response: Use the System
Product Editor to view the rest of the
entry.

User Response: None.

636W

Received null file; no file created
Explanation: A file that was read in
from the virtual reader contained no
data records (only NETDATA control
records were sent). No file was created
on the user's disk.

Conversational Monitor System (CMS) Messages

403

DMS
System Action: RC = 32.
Processing is terminated. No file is
created on the user's disk.

If the module code of the message was
DFT, the DMSDFT did not expect the
return code it received and cannot
interpret it.

User Response: None.

6a7E

Missing {valuelnodeid} for the
{option option loperand operand}

Explanation: An option or an operand
that requires a value following it was
specified, but no such value was given.
System Action: RC = 24.
Processing is terminated.
User Response: Check the format of
the command and reissue it, specifying
all the required values for the options
and operands.

6aSE

fn ft fm is too wide to append to fn
ftfm

System Action: RC = nnnn (whatever
the return code was in the message
above).
Processing is terminated.
The CONVERT command will issue
RC = 256 and the conversion will stop.
The P ARSECMD command will issue
RC=04.
The QUERY command will issue
RC=24.
NUCXLOAD issues a return code of 100
if message 639E is issued. DMSRLD
loads the module into storage for
NUCXLOAD. The following chart
shows the return codes from DMSRLD:
Code Meaning

Explanation: A note in the reader is
too wide to add to a fixed format
NOTEBOOK file on the user's disk, or a
record could not be added to the user's
fixed format NETLOG file because the
record was longer than the file.
System Action: RC = 32.
Processing is terminated. Either the
NOTE wasn't received or the log
message was not added to the user's
NETLOG file.
User Response: You can use either the
System Product Editor subcommand
SET RECFM or the COPYFILE
command to change the format of the
file from fixed to variable.

21
22
23
35
4nn
5nn

6nn
7nn

9nn
6a9E

Error in routine routine; return
code was nnnn
Explanation: An error occurred while
executing the routine specified in the
error message. The return code is given
to identify what the problem was.

404

VM/SP System Messages and Codes

Module length mismatch when
reading the module file.
Invalid format for the relocation
information record.
A Y-CON was found that could
not be relocated.
Invalid address range for
preallocated plist storage.
Error from FSST ATE (nn is the
FSST ATE return code).
Error reading the module header
records (nn is the FSREAD return
code).
Error reading the module code
(nn is the FSREAD return code).
Error reading the module
relocation information record (nn
is the FSREAD return code).
Error from FSCLOSE (nn is the
FSCLOSE return code).

User Response: Look up the routine
mentioned and determine from the
return code what the problem was.
Correct the problem and reissue the
command.

DMS
If the module code of the message was
DFT, then note the routine and the
return code nnnn and contact your
system administrator.

640R

HELP disk address

642E

Explanation: The DEFAULTS facility
is valid .only with certain commands and
only with certain options for a given
command.

= vdev

Explanation: "vdev" designates the
device address of the system HELP disk.
On this disk, CMS expects to find the
system HELP files.

System Action: RC = 24.
Execution of the command is
terminated.
User Response: Check the list of
commands and options that can be used
with the DEFAULTS command. (See
the VM/ SP CMS Command Reference,
or issue HELP).

System Action: The system waits for a
response.
If you enter an invalid device address,
the message DMSINQ079E INVALID
DEVICE ADDRESS - REENTER is
issued. DMSINQ640R is reissued, and
you may enter a valid device address.

643E

If you enter a null line, "19D" is
assumed to be the system HELP disk.

No class fileclass files in your
reader
Explanation: No files in your reader
have the same class as the virtual
reader. This may mean that your reader
is empty, or that the files in your reader
have a different class associated with
them.

If you do not want a HELP disk, enter
the system disk address as the HELP
disk address.

U s~r Response: Enter a valid disk
address or a null line.

641E

DEFAULTS does not accept
{command commandloption option
for command}

System Action: RC = 28.
Execution of the command is
terminated.

No {command Ioptions} specified
User Response: You can use the
RDRLIST command to see if there are
any files in your reader other than those
having the same class as your virtual
reader. You can use the CP CHANGE
command to make the class of the spool
files the same as your reader class.

Explanation: The DEFAULTS
command requires that you specify a
command and at least one option when
using the SET operand.
System Action: RC = 24.
Execution of the command is
terminated.
644E
User Response: Reissue the command
and specify a command and at least one
option.

All reader files are in HOLD
status or not class fileclass
Explanation: No files in your reader
have the same class as the virtual
reader, or if they have the same class,
they are in HOLD status (they have a
USER, SYS, or USYS value for the
HOLD field in RDRLIST).
System Action: RC = 28.

Conversational Monitor System (CMS) Messages

405

DMS
Execution of the command is
terminated.
User Response: To PEEK or
RECEIVE a file that is not held or is
not the same class as your virtual
reader, specify the spoolid in the
command, for example, "PEEK spoolid"
or "RECEIVE spoolid .... " Yau can also
use the CP CHANGE command to
change the spool file to NOHOLD or the
class of the file to be the same as the
reader class.

645W

System Action: RC = 32.
Execution of the command is
terminated.
User Response: Reissue the command
substituting the user's userid in place of
the nickname, or use the NAMES
command to insert the U serid in that
entry.

648E

The user tag name name is too
long to display in the panel

Explanation: The specified userid or
the value for the userid tag in the
specified 'NAMES' file was not a valid
userid for your computer system.

Explanation: Only the first 12
characters of a user-defined tag name
can be displayed in the NAMES panel.

System Action: RC = 32.
Execution of the command is
terminated.

System Action: None.
User Response: An entry is displayed
with tag names truncated to 12. If you
change this entry using the panel, the
tag names will also be truncated in the
file. Therefore, if you want to have tag
names greater than 12 characters, edit
the names file directly instead of using
the panel.

646E

macro name must be invoked from
the prefix area
Explanation: A prefix macro was
invoked from the command line and not
from the prefix area.

Userid userid not found; {no
message has been sent Ino files
ha ve been sent Icheck the userid
NAMES file}

User Response: Validate the value for
the userid and insert it correctly into
the NAMES file or reissue the command
with correct userid.

649E

Extraneous parameter[(s)]
parameter(s)
Explanation: There were more
operands specified than the command
issued will accept.
System Action: RC = 24.
Execution of the command is
terminated.

System Action: RC = 8.
User Response: None.

647E

Userid not specified for nickname
in userid NAMES file
Explanation: The entry for the
nickname specified does not contain a
value for the Userid tag; therefore,
communication with this user is
impossible.

406

VMjSP System Messages and Codes

User Response: Check the correct
format of the command and reissue the
command.

DMS
650E

Invalid spoolid nnnn

653E

Explanation: The value representing
the spoolid was not a valid spoolid
number.

Explanation: An error was
encountered while executing the
specified command.

System Action: RC = 20.

System Action: RC = 40.
Processing is terminated.

User Response: Reissue the command
with a valid spoolid.

651E

{option Icommand} must be issued
from
environment(s)

User Response: Check the return code
for the command shown in the message
to better identify the problem.

654E

Explanation: The command is valid
only in certain environments and is not
executed otherwise.

System Action: RC = 24.
The command is not executed.

User Response: To execute this
command or use this option you must
first issue the necessary command to
enter the required environment.

Missing operand(s); enter
EXECUTE < n > DISCARD

Invalid symbol string; {/O must be
specified alone Iin valid character
char following / symbol}
Explanation: The EXECUTE
subcommand was invoked with invalid
symbols specified in the command.

System Action: RC = 40.

652E

Error executing command, rc = nn

User Response: Reissue the
command(s) using valid symbols.

655E

Explanation: DISCARD was issued
without the correct operands. If you
use the EXECUTE subcommand to issue
DISCARD, the correct operands will be
appended automatically.

Spoolid nnnn does not exist
Explanation: There is no spool file
with this spoolid number in your virtual
reader.
System Action: RC = 28.
The command is not executed.

System Action: RC = 24.
User Response: None.
User Response: On a display terminal,
enter DISCARD in the command area
on the lines that contain the files to be
discarded and press PF10. Otherwise,
enter EXECUTE [n] DISCARD on the
command line to discard n files (the
default is one), starting with the fileid
displayed on the current line.

656E

{Error saving your NAMES file;
rc = nn from NAMEFIND
commandlError saving your
NAMES file; use FILE LIST to
clear some space on your disk}
Explanation: An error was
encountered while searching through
your 'Userid NAMES' file.
System Action: RC = 100.
The search was terminated
unsuccessfully.

Conven;ational Monitor System (CMS) Messages

407

DMS
User Response: Check the return
codes for the NAMEFIND command to
better identify the problem.

657E

660E

Explanation: All entries in the
NAMES file must have a NICKNAME
tag to indicate the beginning of the
entry. If this field is blank, the entry
will not be accepted from the panel.

Undefined PFkey IP Akey
Explanation: A PF or PA key that has
no function assigned to it was pressed.

System Action: The function is not
executed.

System Action: None.
User Response: None.

658W

The value for the tag tag is too
long to display in the panel

User Response: Fill in the value for
the Nickname.

660W

Explanation: The value for the
specified tag is too long to fit onto the
panel; therefore, only part of it is
displayed. If this value is changed it
will be truncated in the NAMES file.

User Response: If you. change this
entry using the panel, the tag values
will also be truncated in the file.
Therefore, if you want to have tag
values longer than the space allowed on
the panel, edit the names file directly
instead of using the panel.

System Action: None.
User Response: You may wish to
change the nickname value and press
PF6 to ensure that this entry can be
uniquely identified by the eMS
commands that reference the 'Userid
NAMES' file. Also, by pressing PF5
repeatedly you can locate all the entries
that have this nickname and then
decide which nicknames that you wish
to change.

Invalid prefix subcommand: prefix
Explanation: A prefix subcommand or
macro was issued with invalid or
extraneous operands.
System Action: The macro or
subcommand is redisplayed in the prefix
area prefixed by a"?"
661E
User Response: Correct and reissue
the macro or subcommand.

Warning: this entry duplicates an
existing nickname
Explanation: An entry has been added
or changed, and the nickname now
duplicates an entry (or entries) already
in the NAMES file. This entry can no
longer be identified uniquely by its
nickname tag. Since the CMS
commands (NOTE, SENDFILE, and
TELL) that search the 'Userid NAMES'
file often search based on the nickname
tag, only the first entry that begins with
this nickname will be used.

System Action: Only part of the value
is displayed in the panel.

659E

The nickname field must be filled
in

Prefix name is invalid for the line
on which it was entered
Explanation: A prefix subcommand or
macro was issued on a line in the file
that was invalid for the execution of
that subcommand or macro. For
example, most prefix subcommands and
macros are invalid on shadow lines

408

VM/SP System Messages and Codes

(

DMS
when SCOPE is DISPLAY. Also, if an F
or P was specified as the target for an
M prefix subcommand and they were
entered on a line within the lines being
moved, this message is issued. If an E
prefix subcommand was issued on a line
that cannot be extended, this message is
issued.

665E

Explanation: The NOTE command was
issued without any operands, which is
the correct procedure when you want to
continue an existing NOTE. However,
no NOTE was found.

System Action: The macro or
subcommand is redisplayed in the prefix
area, and it is prefixed by a",?"

System Action: RC = 28.
User Response: Specify a name (or
names) following the command name.

User Response: None.

662W

You are not on an entry; press PF
5, 7 or 8 to move to an entry

666E

Explanation: The command issued was
not executed because you were not
positioned on an entry in the file.

Note already exists; enter NOTE
to continue, or specify REPLACE
option
Explanation: The NOTE command was
issued with a name or names following
the command. However, a NOTE
already exists. You can process only
one NOTE at a time.

System Action: None.
User Response: Use a PF key to move
to an entry.

663W

File userid NOTE * not found; to
begin a new note, enter NOTE
name

System Action: RC = 28
User Response: You can either specify
NOTE with no operands to finish
processing the existing note, or you can
reissue the command and specify the
REPLACE option, which discards the
existing note and begins a new one.

There is/are nn undisplayed tag(s)
Explanation: This entry contains 'nn'
more tags than can be displayed in the
panel.
System Action: None.
667E
User Response: If the entry is deleted,
the undisplayed values are also deleted.
If the entry is changed, the undisplayed
tags are not changed. To change these
tags you must edit the 'Userid NAMES'
file.

664E

{Entry/Previous entry/Next entry}
not found
Explanation: PF 5, 7 or 8 was pressed
and the search failed to find an entry.
System Action: None.

NOTE header does not contain
the {keyword FROM/keyword TO/
OPTIONS line/DATE line}
Explanation: The NOTE header must
have a line that contains the options, a
line containing the date, a line
indicating the sender of the note, and a
line indicating the recipients. These
lines are denoted by the keywords
"OPTIONS:," "FROM:," "DATE:,"
"FROM:" and "TO:," respectively
beginning in column one of these lines.
If these lines are not present, the NOTE
has an invalid format and canhot be
sent using the NOTE option of
SENDFILE.

User Response: None.

Conversational Monitor System (CMS) Messages

409

DMS
System Action: RC = 32.
Processing terminates.

671E

User Response: Correct the format of
the header lines.

668E

Error {sending Ireceiving Icreating I
loadinglupdating} [file] fn ft fm;
rc = nn from command
Explanation: An error occurred while
attempting to send, receive, create, or
load a file.

The {ADDIAPPEND} option must
be specified alone

System Action: RC = 100.
Execution of the command is
terminated.

Explanation: No other options are
valid when either the ADD or APPEND
option is specified.

User Response: To further identify the
problem, check the return code specified
in the message for the command that
encountered the error, correct the
problem, and reissue the command.

System Action: RC = 40.
Processing terminates.
User Response: Reissue the command
using only the ADD or APPEND option.
672E
669E

List of addressees cannot begin
with CC:

Explanation: The specified device was
not defined at the correct virtual
address. The virtual reader must be
defined at the virtual address OOC and
the virtual punch must be defined at
OOD in order for the command issued to
function properly.

Explanation: 'CC:' is used to denote a
list of complimentary copy recipients
and cannot be the first addressee of a
NOTE.
System Action: RC = 24.
Processing terminates.

System Action: RC = 36.
User Response: Use the CP DEFINE
command to define the device at the
proper address. Then reissue the
command.

User Response: Reissue the command,
with the addressee preceding the 'CC:'
recipients.

670E

No names to be added were
specified
Explanation: The ADD option was
specified without any names to be
added.
System Action: RC = 24.
Processing terminates.
User Response: Reissue the command,
specifying the names to be added with
the ADD option.

Virtual {punchlreader} invalid or
not defined

673E

Addressees are in the note header
records; do not specify names
with the NOTE option
Explanation: The NOTE option of the
SENDFILE command was issued with a
name or names of people who were to
receive the file. However, the recipients
of the NOTE being sent should be
contained in the NOTE header records;
the names specified on the command
line are extraneous.
System Action: RC = 24.

410

VM/SP System Messages and Codes

DMS
User Response: Check that the proper
addressees are contained in the NOTE
header and reissue the command
without specifying any addressees.

674E

The command is not executed.
User Response: Do one of the
following:
•

There is evidently a problem with
the 'SYSTEM NETID * , file. This
file should contain information
about the Network ID. For more
information about this file, see the
description in the IDENTIFY
command. Contact your system
support personnel. The person
responsible for building your system
is responsible for maintaining this
file.

•

Reissue the DEFINE WINDOW or
DEFINE VSCREEN command with
a valid name.

{ReaderIPunch} is not ready
Explanation: The command issued
requires that the device specified have a
READY ~tatus associated with it.
System Action: RC = 36.
User Response: Use the CP READY
command to change the status of the
virtual device. Then reissue the
command.

675E

No names specified
Explanation: The SENDFILE
command requires that you specify the
name(s) of the recipient(s) of the files
(unless t"'1e file is a NOTE).

677E

Invalid option option in option line
Explanation: The OPTIONS line in the
NOTE header records contains an
option that is invalid or not in the
correct position. The five options on
the line following the keyword
'OPTIONS:' are expected to contain
specific values and be in the correct
order.

System Action: RC = 24.
User Response: Reissue the command,
specifying the name(s) of the
recipient(s).

System Action: RC = 32.
676E

Invalid character {*I =} for
{Network IDlwindow namelvirtual
screen name}

User Response: Check the format of
the options line as described in the
NOTE command description and correct
the invalid option and/or make sure that
the order in which the options appear
on the line agrees with the order in the
NOTE command description.

Explanation: This message was issued
for one of the following reasons:
•

•

SENDFILE is attempting to send a
file to another node, which should
be connected to your computer via
an RSCS machine. However, the
RSCS ID (or NETWORK ID) has the
value '*', which is not a valid ID.
An attempt was made to define a
window with a name of * or =, or to
define a virtual screen of * which is
not valid.

System Action: RC = 20.

678E

Invalid note header format; note
cannot be sent
Explanation: The SENDFILE
command was unable to send the NOTE
because the format of the addressees in
the NOTE was not what the SENDFILE
expected. Depending on the value of the
format option (LONG or SHORT) in the
'OPTIONS' line of the NOTE,

Conversational Monitor System (CMS) Messages

411

DMS
SENDFILE expects the addressees to
have certain formats. If the LONG
option was specified, each line must
contain one addressee, that can be
identified in the form "U serid AT
Node." If the SHORT format is specified,
everything following the 'TO: ' keyword
is an addressee in the form "U serid" or
"Userid AT Node."

680E

Invalid fileid specified with the
FILE LIST option
Explanation: The FILELIST option is
used to indicate that the file identified
as 'fn ft fm' actually contains a list of
files to be processed by the command. If
the FILE LIST option is specified, no
pattern matching characters (* or 0/0)
may appear in the fileid.

System Action: RC = 32.
System Action: RC = 20.
User Response: If the header format is
incorrect, try to correct the format of
the addressees. Check the description
of the NOTE header format (which
depends on the LONG and SHORT
options) in the description of the NOTE
command.

User Response: Do not use the
FILE LIST option, or specify the
complete fileid of the file that contains
the list of files to be processed.
(

681E
679E

Disk mode is {read/onlylfullinot
accessed}; note cannot be sent

Explanation: The spool file being
received has no fileid. It must have a
filename and filetype in order to be
identified.

Explanation: For the reason specified
in the message, the SENDFILE
command was unable to send the NOTE.
In order to send the NOTE, SENDFILE
must first save the NOTE on a disk. It
cannot do this if the disk is full or if the
disk has read/only access.

System Action: RC = 88.
User Response: Reissue the command,
specifying a filename and filetype. See
the RECEIVE command description for
more information on the command
format.

System Action: RC = 36.
The note is not sent.
User Response: If the' disk is full, try
to make some space available by erasing
any unwanted files. If the disk is
accessed read/only, use the CMS
ACCESS command to access the disk for
read/write capability; or change the
filemode to one that is a read/write disk
(you can use the System Product Editor
subcommand "SET FMODE mode" to do
this).

This is an unnamed file; specify
filename and filetype

682E

Error copying file fn ft A to {fn ft
fm Imode disk}; rc = nn from
COPYFILE
Explanation: The file was sent using
the DISK DUMP command and had to
be read onto the A-disk using the DISK
LOAD command. At that point the
RECEIVE command attempted use
COPYFILE to copy the file from the
A-disk to the disk specified in the error
message. However, the COPYFILE
command failed to execute and returned
the specified return code.
System Action: RC = 100.

412

VM/SP System Messages and Codes

DMS
User Response: See the description of
the COPYFILE command for more
information about the return code. The
file specified in the error message is still
on your A-disk and you can do with it
as you want. If there was a file with the
same fileid on your A-disk before
RECEIVE was issued, the original file is
renamed "$A$A$A$A $B$B$B$B A"
Take the proper actions to restore the
files to the fileid you want.

684E

File contains invalid records and
cannot be reformatted
Explanation: The spool file contains
records that PEEK does not recognize
as the correct format for DISK DUMP
or NETDAT A format files.
System Action: RC = 32.
The file is not formatted.
User Response: None.

683E

The entire file must be peeked at
to be reformatted

685E

Explanation: The PEEK command
reformats spool files that are in DISK
DUMP or NETDAT A transmission
formats to make them more readable.
To do this, the user must PEEK at the
entire spool file. The default for PEEK
is to peek at the first 200 records in a
spool file.

683W

System Action: RC = 5.
The subcommand is not executed.
User Response: Change the zone
setting and reissue the JOIN
subcommand.

686E

Synonym name not recognized by
prefix macro macroname
Explanation: A prefix macro was
issued using a synonym that cannot be
recognized by the prefix macro.
System Action: The prefix area is
redisplayed prefixed by a "?"
User Response: Use the system defined
synonyms for that macro.

The file has an LRECL greater
than 255 and cannot be
refornlatted
Explanation: The PEEK command
cannot reformat a file whose logical
record length is greater than 255.

lines(s) exceed zone
settings
Explanation: The first character of the
joined line did not fit within the zone.

System Action: RC = 32.
The file is not reformatted.
User Response: If you want to look at
the file reformatted, reissue the PEEK
command using the FOR and FROM
options. To PEEK at the entire file, use
"PEEK spoolid ( FROM 1 for * ). " You
can change the default options of PEEK
(originally FROM 1 FOR 200) by using
the DEFAULTS command.

Join~d

687E

This is a {SYSTEM
{HELDIDUMP}filelfile with a
SPECIAL CCW} This file cannot
be {peeked atlreceived}

System Action: RC = 32.
User Response: This file cannot be
peeked at in readable form. Use
RECEIVE to read the file in.

Explanation: A file in your reader has
a SYSTEM hold on it (status SYS or
USYS), is a system dump, or contains a
special CCW (usually generated by a
X'5A' carriage control character and as
such cannot be received or peeked at.

Conversational Monitor System (eMS) Messages

413

DMS
System Action: RC = 1, or RC = 10 (if
the file contains a special CCW).

690E

User Response: If the file is SYSTEM
HELD, request that the operator change
the spool file status to NOHOLD. If the
file is a SYSTEM dump file, refer to the
documentation for the VMDUMP and
VMFDUMP commands.

688E

Explanation: A request is received to
set node-checking ON or OFF for a
routing table that has no PROPCHK or
HOSTCHK statements. (Sent by the
programmable operator SET
node-checking command handler.)
System Action: The operation is not
performed.

XEDIT option only valid from
XEDIT environment
Explanation: The LISTFILE,
NAMEFIND, MACLIB, or DMSDDL
command was issued with the XEDIT
option, but the command was not issued
from the XEDIT environment.

User Response: Check the routing
table contents.

6911

System Action: RC = 24.
The command is not executed.

System Action: The programmable
operator facility closes all files, issues
the CP VMDUMP command, and IPLs
the last CMS system that was IPLed.

File must be F-format or
V-format

User Response: Note the error and
contact system support personnel.

Explanation: One of the following
conditions has occurred:
•

•

The LIST FILE command was issued
with the XEDIT option, but the file
where the information was to be
placed is not in the correct format.
The correct format is either fixed
format with LRECL of 108 or
variable format.
The MACLIB command was issued
with the XEDIT option, but the file
where the information was to be
placed is not in the correct format.
The correct format is either fixed
format with LRECL of 130 or
variable format.

System Action: RC = 24.
The command is not executed.
User Response: Correct the format of
the file.

414

VM/SP System Messages and Codes

VMDUMP taken, PROP will IPL
CMS
Explanation: An abend occurs in the
programmable operator facility
maninline. (Sent following
DMSPOE148T.)

User Response: Reissue the command
from the XEDIT environment.

689E

{PROPCHKIHOSTCHK} not
specified in RT ABLE

6921

Action routine routine abended,
PROP continuing
Explanation: An abend occurs in an
action routine. (Sent following
DMSPOE148T.)
System Action: The programmable
operator continues operation.
User Response: For a system action
routine, note the error and contact
system support personnel. For a user
action routine, correct the action
routine.

(

DMS
693E

Missing statement statement in
RTABLE

System Action: RC = 100.
An attempt is made to re-read the
screen. If errors persist, then screen
changes are not processed.

Explanation: One of the following
statements is missing from the RT ABLE:
LGLOPR, or ROUTE.

User Response: Check the terminal
and reissue the command. If the error
persists notify your system support
personnel.

System Action: The programmable
operator facility terminates.
User Response: Correct the RTABLE
and reload it or reinvoke the
programmable operator facility.

694E

Explanation: More than one of the
following statements is detected in the
RTABLE:LGLOPR,TEXTSYM,
LOGGING, or HOSTCHK.

System Action: RC = 5.
The subcommand is not executed.

System Action: The programmable
operator facility terminates.

User Response: Reissue the SET
SCREEN subcommand and be sure to
account for all the columns on the
screen.

Cannot define more than 63
CTLCHARs
Explanation: An attempt was made to
define new CTLCHARs when there were
already 63 CTLCHARs defined.
System Action: RC = 4.
The subcommand is not executed.
User Response: You can redefine the
existing CTLCHARs, but you cannot
add any more new on.es.

696W

The logical screens must cover
the full virtual screen width
Explanation: . A SCREEN WIDTH or
SCREEN DEFINE subcommand was
issued that did not account for the
entire virtual screen width.

More than one statement statement
in RTABLE

User Response: Correct the RTABLE,
and reload it or reinvoke the
programmable operator facility.

695E

697E

Invalid data received from the
display
Explanation: After a READ operation,
the data received from the display could
not be handled properly. This message
may occur when using a remote display
and transmission errors occur.

698W

New record length may result in
loss of double-byte characters
Explanation: A subcommand was
issued that changes the logical record
length (LRECL) of records that may
contain double-byte strings. As a result,
DBCS strings may have been truncated
and no longer contain matching
shift-out (SO) and shift-in (SI) control
characters. These truncated strings no
longer are recognized as double-byte
characters.
If SET LRECL was issued to decrease
the logical record length, then any
double-byte strings that have been
truncated will no longer be treated as
double-byte characters.
If PUT /PUTD was issued to append
records to a fixed-format file that has a
smaller LRECL, then any double-byte
strings that were truncated in the

Conversational Monitor System (CMS) Messages

415

DMS
appended records are no longer
recognized as double-byte characters.
System Action:

7011

Null file
Explanation: There were no records in
the file.

RC := 3.

User Response: To return to the
original LRECL of the file, issue "SET
LRECL *", thus avoiding any possible
truncation of DBCS strings. If you are
putting records to a fixed-format file,
change the record format (RECFM) or
the logical record length (LRECL) of the
file to which you are appending records.

For DMSRDC, two READ control cards
were encountered, but there were no
cards available to be placed in the first
file.
For DMSTPE, an end-of-CMS-file record
was found, but there were no other
records in the file.
System Action: Processing continues.

699E

No filetype specified or vdev is an
invalid disk address
Explanation: The command requires
that you specify a filetype or a valid
hexadecimal disk address.

User Response: If records were
expected, the file should be resubmitted.

702E

System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.

Explanation: This message appears
when you issue READCARD * and
prompting is not in effect. It indicates
that a record beginning with :READ has
been found in the spool file and the
following fileid is invalid.

User Response: Reenter the command,
specifying the filetype or the valid
hexadecimal disk address.

700E

Logical AND operator & not valid
for column targets

System Action: RC = 24.
Execution of the command is
terminated.

Explanation: The logical AND
operator, '&', is only valid for line
targets. It is not valid for column
targets.

User Response: Issue READCARD fn
ft, edit the received file, correct the
erroneous READ control card(s), punch
the file back to yourself, and then
reissue READCARD *

System Action: RC=5.
The subcommand is not executed.
User Response: Redefine the target
string and reissued the subcommand.

Missing, invalid, or incomplete
fileid in
following READ control card:
:READ ....
Command terminated

7021

{READ control card missing.
Following assumed: :READ
READCARD CMSUT1
A11:READ ... }
Explanation: One of the messages is
displayed when you issue READCARD
*, either:

416

VM/SP System Messages and Codes

DMS
1.

For FILE 'fn ft fm' CREATED: A file
containing the SET subcommand
options and their current settings is
created.

The first record in the spool file is
not a READ control card and when
a READ control card and when a
read control card in the spool file
has been identified and validated, it
is listed at the terminal.
A control card was encountered in
the input card stream and it
indicates the names assigned to each
file.

User Response: None.

7041

Explanation: A CLEAR request was
entered for a file definition that does
not exist. No action took place.

System Action: Processing continues.
User Response: If the file has been
read in as READCARD CMSUTI AI,
rename it to a desired fileid.

702W

Missing, invalid, or incomplete
fileid in
following READ control card:
:READ ....
Fileid changed to READCARD
CMSUTI

System Action: None.
User Response: Correct the file
definition specified in the CLEAR
request.

7051

User Response: A subsequent prompt
will allow you to specify the correct
fileid.

7031

File

Disk remains unchanged
Explanation: The reply to
DMSFOR605R was not "yes."

Explanation: This message appears
when you issue READCARD * and
prompting is in effect. It indicates that
a record beginning with :READ has
been found in the spool file and the
following fileid is invalid.
System Action: Processing continues.
The action specified is taken.

Invalid CLEAR request

System Action: None. The disk
remains unchanged.
User Response: Enter the next
command.

7061

Terminal input; type null line for
end of data
Explanation: The input ddname in the
MOVEFILE command refers to a
terminal. This message requests the
input data to be copied to the output
device or file.

In It 1m {copiedlcreated}

Explanation: The named file has been
copied from tape to disk, or a file was
created after issuing the STATUS
macro.

System Action: The system waits for a
response.
User Response: Enter data or a null
line.

System Action: For FILE 'fn ft fm'
COPIED: None.

Conversational Monitor System (CMS) Messages

417

DMS
7071

7081

Ten files copied

7101

Phase phase entry point at
location hexloc

Explanation: Ten members have been
copied from tape to disk as a result of
the MAXTEN option.

Explanation: The phase entry point is
located at 'hexloc'.

System Action: None.

User Response: None.

U set Response: Issue the START
command to begin execution.

Disk file FILE ddname Al assumed
for DDNAME ddname

7111

No system synonyms in effect
Explanation: No system synonyms are
in effect because you previously issued a
SYNONYM command with NOSTD
specified as an option.

Explanation: No FILEDEF commar.Ld
was issued for a ddname specified in the
MOVEFILE command. As a result, the
MOVEFILE command issues a
FILEDEF for that ddname.

System Action: None.
If this is the input ddname, the disk file
must exist on disk. The blocksize and
record format are taken from the
characteristics of the input disk file.
If this is the output ddname, the disk
file is created on the A-disk. Its
characteristics depend on the format of
the input file.

User Response: If you want to have
system synonyms in effect, issue the
SYNONYM command with the STD
option.

7121

System Action: Processing continues.

Explanation: The routine that handles
synonym processing is not in this
system; therefore, no synonyms are in
effect.

User Response: None.

709E

No synonyms (DMSINA not in
nucleus)

System Action: .None.

PROPCHK not specified in
RTABLE for nodeid nodeid

User Response: None.
Explanation: A request is received to
set node-checking ON or OFF for a node
that is not specified in the RT ABLE.
(Sent by the programmable operator
SET PROPCHK command handler.)
System Action: The operation is not
performed.
User Response: Enter the correct
nodeid or check the RT ABLE contents.

713E

Cannot connect to message
system service, CMSIUCV error
code = code
Explanation: Sent by the
programmable operator facility
initialization routine when a request to
CONNECT to Message Service results
in a non-zero return code from the
CMSIUCV function.
System Action: The programmable
operator facility terminates.

418

VM/SP System Messages and Codes

DMS
User Response: Refer to the IBM VM
System Facilities for Programming to
determine the meaning of the code. If
the problem cannot readily be corrected,
IPL the CMS system again. If the
problem persists, contact system support
personnel.

714E

716E

Explanation: The SRPI subcommand
environment wasn't found when either
you entered the CMSSERV command to
start communications between your
work station and CMS or when CMS
tried to process an SRPI subcommand.

Cannot connect to message
system service, service already in
use

System Action: Communications with
your work station ended. CMS
informed your work station program
that communications ended.

Explanation: IUCV has denied the
programmable operator facility's request·
to CONNECT to Message Service. For
example, the programmable operator
virtual machine already has a
connection to the message service.
(Sent by the programmable operator
initialization routine.)
System Action: The programmable
operator facility terminates.

User Response: IPL CMS and enter
the CMSSERV command to start
communications between your work
station and CMS. If you still have a
problem, contact your system
administrator.

717E

User Response: Terminate the
application that is using the Message
Service. If that cannot be done, IPL the
CMS system again. If the problem
persists, contact system support
personnel.

7151

System Action: None.
User Response: None.

Return code from command line
entry was nnn
Explanation: The command you
entered sent back a return code of nnn.
System Action: None
User Response: For information on the
return code and its meaning, see the
appropriate documentation for the
command you entered.

DOSGEN complete
Explanation: The CMS text decks have
been successfully loaded into the
discontiguous shared segment and the
CP SAVESYS command has been issued
to save the system.

SRPI subcommand environment
was not found.

718E

Unable to link to work station.
Explanation: Communications between
your work station and CMS couldn't be
initialized because the configuration of
your work station doesn't support the
required DFT mode.
System Action: Communications
between your work station and CMS
were not started.
User Response: Make sure you have
the correct work station configuration
to use the services of Enhanced
Connectivity Facilities. You can find
specific information about the supported

Conversational Monitor System (eMS) Messages

419

DMS
work station configurations in
Introduction to IBM System/370 to IBM
Personal Computer Enhanced
Connectivity Facilities, GC23-0957. Once
you've set up the correct configuration
for your work station, start the
communications program on your work
station and then IPL CMS and enter the
CMSSERV command. If you still have
problems, contact your system
administrator.

719E

008 Unexpected results were received
from the work station terminal
emulator.
012 There is an error in the Enhanced
Connectivity Facilities data sent
from your work station
communications program.
016 There is an error in the
communications data or flows sent
from your work station
communications program.

Work station communications
not active.

020 The data sent from your work
station communications program
contained an unexpected structured
field.

Explanation: The communications
program at your work station is not
running; therefore, CMS cannot
communicate with your work station.

024 When CMS tried to send data to
your work station, CP sent back a
reply stating that your work station
is disconnected.

System Action: CMS will periodically
attempt to start communications with
your work station until you either start
the communications program on your
work station or press PF3 to force CMS
to end its attempts to connect with your
work station.

028 The work station communications
program ended communications.
System Action: Communications with
your work station ended. If
communications with your work station
were active before this message was
displayed, CMS informed your work
station program that communications
ended.

User Response: Start the
communications program on your work
station or press PF3 to terminate
CMSSERV. If you cannot start your
work station communications program,
press PF3 and contact your system
administrator to find out what you need
to start Enhanced Connectivity
Facilities communications on your work
station.

720E

User Response: Check any
connections between your work station
and host system to which you have
access. Restart communications on
your work station, IPL CMS, and then
enter the CMSSERV command again to
start communications from the host. If
you still have problems, contact your
system administrator.

No longer linked to work station;
error code was nnn
Explanation: Unexpected results were
when your work station
program transmitted data to CMS.

l"L'~!eived

7211

Copy fn ft fm [{tolappendloverlay}
fn ft fm ({oldlnew} file)]

Code Meaning
004 The request from the work station
was out of sequence.

420

VM/SP System Messages and Codes

Explanation: This message appears in
conjunction with the TYPE option. It
indicates the name of the input file and
output file.

DMS
System Action: None.

7251

User Response: None.

7221

Explanation: The specified disk is also
accessed as the 'mode' disk. The -OS
indicates that the disk is an OS disk;
the -DOS indicates that the disk is a
DOS disk.

File fn LISTING Zl will hold
AMSERV output
Explanation: The Access Method
Services output will be placed on the
given disk (other than the user's
A-Disk). This information message is
omitted if the output file is placed on
the user's read/write A-disk.

System Action: Processing continues.
User Response: None.

7261

System Action: Processing continues.

mode( udev) [is accessed as]
{R/OIR/W} [-OS I-DOS]
Explanation: The specified
CMS-formatted disk is accessed in
read-only mode. -OS indicates the disk
is OS-formatted. -DOS indicates the
disk is DOS-formatted.

System Action: Processing continues.
User Response: None.

727E

7241

udeu mode released
Explanation: The specified device was
previously accessed as a read/write disk
with the mode letter indicated. This
device has now been released since the
user has accessed the same device as a
read/write disk with a different mode
letter.

User Response: None.

7231

udevalso = mode [-OSI-DOS] disk

Syntax definition for uniqueid
uniqueid not found

Note: A read/write OS or DOS disk can
be written on only by VSAM. If the
message occurs during IPL, then the
Y-STAT is too large to fit in the CMS
nucleus.

Explanation: The uniqueid uniqueid
was requested but not found in the
syntax definition table.

System Action: Processing continues.

System Action: RC = 28.

User Response: None, unless the
message occurred during IPL, in which
case refer to Appendix G of the VM/ SP
Installation Guide.

User Response: Issue SET LANG to
make sure correct parsing facility tables
are available or correct uniqueid on
P ARSECMD invocation, and issue the
command again.

udeu replaces mode( udeu)
[-OSI-DOS]
Explanation: The disk that was first
accessed replaces the disk specified by
the mode letter. The disk it replaces is
released, but is not detached.

7281

DEBUG entered
Explanation: The system has entered
the DEBUG environment. For a full
description of DEBUG, see the VM/SP
CMS User's Guide and the VM/ SP CMS
Command Reference.

System Action: Processing continues.
User Response: None.

System Action: The system waits for
the next command.

Conversational Monitor System (CMS) Messages

421

DMS
Reissue the IPL command and
provide an affirmative answer to
prompt DMSINI729R

User Response: Enter a DEBUG
subcommand.

729R

If prompt 729R does not appear,

Do you want to save the system?
Enter 1 (YES) or 0 (NO).

modify the SAVESYS parameter of
the DEFNUC macro in the
DMSNGP assemble file, and rebuild
the CMS nucleus and reissue the
IPL command.

Explanation: This prompt allows users
to save the CMS system during CMS
nucleus-generation.
User Response: Accepted responses
are 1, Y, YES (indicating YES), 0, N,
NO (indicating NO) or null (which takes
the default of YES).

730R

Saved systemname

7321

nnnn {cylindersIFB-512 blocks}
formatted on mode(vdev)
Explanation: This message tells you
how many cylinders or FB-512 blocks
have been formatted on the specified
disk.

Explanation: This prompt is displayed
when the user makes an affirmative
response to message 729R.

System Action: Processing continues.
User Response: None.

User Response: Enter the name the
system is to be saved as. If a null
response is made, the default name of
'CMS' is used.

7331

{FormattingIReserving} disk mode
Explanation: The FORMAT command
is formatting the specified disk.

731W

System will not be saved; reissue
the IPL command with the
SAVESYS parameter

System Action: Processing continues.
User Response: None.

Explanation: The SAVESYS command
was entered at the initial VM READ.
This is not a supported method of saving
the CMS system.
System Action: IPL completes, but the
system is not saved.
User Response: To save the CMS
system with an IPL of a dasd device,
reissue the IPL command with
SAVESYS parameter.
To save the system during nucleus
generation either:
Modify the DMSNGP ASSEMBLE
file to include a positive reponse to
the SAVESYS parameter, rebuild
the CMS nucleus, and reissue the
IPL command, or

422

VMjSP System Messages and Codes

735E

Primary and alternate drives are
identical.
Explanation: The tape drive specified
as a parameter of the ALT option in the
FILEDEF command is identical to the
specified primary drive. This is invalid.
System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the FILEDEF
command specifying a tape drive on the
ALT option that is different from the
primary tape drive.

(

DMS
737R

Enter the minidisk address for the
group element

indicates that the history information is
incomplete.

Explanation: The SPLOAD PROFILE
contains a '? in the address column for
this group element

User Response: You can do one of the
following:
Reissue the command without using
the HIST option
Reorganize the text files so that
fewer than 819 records exist and
reissue the command.

System Action: Execution of the
command waits until you respond to the
address request.
User Response: Enter the minidisk
address where you want the group
element tape file to be loaded.

7381

7501

ZAP processing complete
Explanation: An END control record
was encountered and processing is
terminated.

Record length is nnn bytes
Explanation: The message indicates
the length of records read in when it is
not 80 bytes.

System Action: All files are closed and
control returns to CMS.

System Action: Processing continues.

User Response: None.

User Response: None.
7511
7401

Member membername found in
library libname

Execution begins ...
Explanation: If more than one
LOAD LIB or TXTLIB was specified, this
message tells you which library the
member was found in.

Explanation: The user has requested
execution of a program under CMS.
System Action: The program has been
prepared for execution by the CMS
loader and control is now passed to the
program.

System Action: Processing continues.
User Response: None.

User Response: None.
752E
749W

There are too many comments in
text files to save all the history
information

Unable to delete member
membername from in it im

Explanation: You specified the HIST
option on the LOAD or INCLUDE
command and more than 819 comment
records were found in the TEXT files
you wanted to include in the module.

Explanation: DISCARD was issued for
a member, but the member could not be
deleted from 'fn ft fm'. If 'fn MACLIB'
is not the first MACLIB with the
filename 'fn' in the CMS search order,
DISCARD cannot call the CMS
MACLIB command to delete the
member.

System Action: RC = 4.
A warning is placed at the end of the
history information. This warning

System Action: RC = 88.
The member is not deleted from the
library.

Conversational Monitor System (eMS) Messages

423

DMS
the default logical operator). This
message is also issued if a LGLOPR
ASN or LGLOPR RPL is received from
the current logical operator.

User Response: Adjust the CMS disk
search order so that the proper
MACLIB will be the first in the CMS
search order.

754W

System Action: The operation is not
performed.

Label CMSGEXIT, the IUCV
Pending Connect exit, was given
control. This is an error.

User Response: If you must assign a
logical operator, issue an RPL (Replace)
request or contact the currently
assigned logical operator.

Explanation: The label specified as
CMS's general IUCV exit did not get
control.
User Response: If this message
persists, contact your system
programmer to determine why the CMS
general IUCV exit is getting control.

757E

function function not allowed for
default LGLOPR

Explanation: Sent by the
programmable operator LGLOPR
command handler when it receives an
RLS (Release) request from the default
logical operator.

System Action: The system returns to
the caller of label 'CMSGEXIT' with a
branch to the address contained in
general register 14.

System Action: The operation is not
performed.
755E

Cannot complete PROP /PMX
IUCV connection, CMSIUCV
error; code = code
Explanation: Sent when the PMX
cannot get an IUCV connection with
the programmable operator or the
programmable operator cannot get an
IUCV connection with PMX.
System Action: The program
continues.
User Response: Use specified 'code' to
determine the problem and retry.

756E

LGLOPR userid nodeid already
assigned
Explanation: Sent by the
programmable operator LGLOPR
command handler when it receives an
ASN (Assign) request and a logical
operator is already assigned (other than

424

VM/SP System Messages and Codes

User Response: Contact system
support personnel to determine if
another logical operator should be
assigned.

7581

{NCCFIVM} user use rid [nodeid] is
now LGLOPR for PROP on node
nodeid
Explanation: Sent by the
programmable operator LGLOPR
command handler to both the new and
old logical operators when a LGLOPR
command request is handled, or by the
LOADTBL command handler when the
current logical operator is replaced from
the loading of a new routing table.
System Action: The currently
assigned logical operator is replaced.
User Response: None.

(
\

DMS
7591

PMX terminated

7611

Explanation: Sent by the
programmable operator lUCY exit
routine to the current logical operator
when it receives an lUCY SEVER from
the PMX virtual machine. If the
current logical operator is an NCCF or
NetView operator, this message is sent
to the default logical operator.

Explanation: Sent by the
programmable operator to the default
logical operator when a network
management logical operator logs off
NetView or NCCF before issuing the
command "PROP LGLOPR RLS".
System Action: The network
management logical operator is released
and the default logical operator is
assigned.

System Action: If the logical operator
is an NCCF or NetView operator, the
default logical operator is assigned as
the logical operator and message 7581
will follow.
User Response: NCCF or NetView
must be CLOSEd and the PMX restarted
to restore the Programmable
Operator/PMX connection.

760E

User Response: None.

762E

Explanation: Sent by the
programmable operator mainline
sequence, the programmable operator
LGLOPR command handler, and the
LOADTBL command handler when the
programmable operator encounters a
GLOBAL V error.

User Response: Use the specified
'code' to determine the cause of the
problem and correct it or notify
appropriate personnel.

Host checking
suspended--LGLOPR not on a
checkable node
Explanation: Sent by the
programmable operator when the SET
HOSTCHK or QUERY HOSTCHK is
received and the current logical
operator is a NetView or NCCF
operator or a local VM user.

GLOBAL V subfunction error in
PROP, code = code

System Action: The programmable
operator continues operation and any
functions requested are still performed.
However, since the programmable
operator could not store or retrieve
some global variable, when restarted it
may not be able to retain the current
routing table or logical operator, or to
reconnect to the PMX.

NCCF LGLOPR session
terminated

System Action: The host-checking
status remains unchanged.
User Response: None.

763E

Not currently assigned as
LGLOPR, cannot be released
Explanation: Sent by the
programmable operator when the
LGLOPR RLS command is issued and
the issuer is not currently assigned as
the logical operator.
System Action: The logical operator
assignment remains unchanged.
User Response: None.

Conversational "Monitor System (CMS) Messages

425

DMS
764R

Languageid

769W

Explanation: This prompt asks for the
langid of the language-dependent text
decks that get loaded as part of the
CMS nucleus. This prompt is issued in
the default language.

Explanation: The first
non-commentary line of the repository
specifies the number of message number
characters to be placed in the message
header. You must specify 3 or 4 for this
value.

System Action: The system waits for a
response.

System Action: RC = 4.
A default value of 3 is used.

User Response: Enter a valid language
id (the default language id) as described
in the Explanation.

7661

Invalid number of message
characters value value

User Response: Correct the value and
retry.

Substitution character is char
770E
Explanation: The substitution
character is as stated in the message.

Invalid application id applid
Explanation: The applid that is
specified is invalid.

System Action: None.
System Action: RC = 24.
Execution stops. The language remains
unchanged.

User Response: None.

7671

Explanation: The number of message
number characters to display is as
stated in the message.

768W

771E

Invalid message number

System Action: None.

Explanation: The message number is
not numeric or is greater than 9999.

User Response: None.

System Action: RC = 8.
User Response: Correct the message
number and retry.

Invalid substitution character
value char
Explanation: The substitution
character is not a valid non-blank,
single-byte character.

426

User Response: Correct the specified
identifier and reissue the command.

Number of message number
characters to display is nn

772E

Invalid format number
Explanation: The format number is not
numeric or less than 01.

System Action: RC:= 4.
A default value of'&' is used.

System Action: RC = 8.

User Response: Correct the value and
retry.

User Response: Correct the format
number and retry.

VM/SP System Messages and Codes

(

DMS
773E

Duplicate message id id

777S

Explanation: The compiler has already
processed a message with a matching
message, format, and line number.

Explanation: The virtual DOS
partition is too small to accommodate
the FETCH request. If the module or
phase requested were fetched into user
storage, it would exceed PPEND.

System Action: RC = 4.
User Response: Correct the message id
and retry.

774E

DOS partition too small to
accommodate FETCH request

System Action: RC = 104.
Execution of the command is
terminated.

Line numbers for messages are
not consecutive

User Response: Redefine the size of
the virtual partition using the SET
DOSP ART command and reissue the
command. Note that redefining the
partition size causes storage to be
reinitialized, and therefore any previous
loads or fetches must be reissued.

Explanation: The line numbers for the
previous messages with matching
message and format numbers are not
consecutive.
System Action: RC = 8.
User Response: Correct the line
numbers and retry.

775W

778E

Text too long - 240 characters is
the maximum allowed
Explanation: The text for the current
message exceeds 240 characters.

Explanation: The call to VSEjVSAM
results in an error code indicating that
a problem could exist with the volume
on which the file resides.

System Action: RC = 4.
The text is truncated to 240 characters.

System Action: Your program is
terminated with an ABEND 35.

User Response: Correct the message
text and retry.

User Response: None.

779E
7761

Open error on DDNAME: possible
volume error. See VSE/VSAM
documentation for open error
code code.

Options used: list
Explanation: The options you used
when invoking the message compiler are
as listed in the message.
System Action: None.

Open error on DDNAME: possible
user programming error. See
VSE/VSAM documentation for
open error code code.
Explanation: The call to VSEjVSAM
results in an error code indicating that
an error in processing occurred due to
an error in your program.

User Response: None.
System Action: Your program is
terminated with an ABEND 35.
User Response: None.

Conversational Monitor System (CMS) Messages

427

DMS
780E

Open error on DDNAME: possible
DLBL/EXTENT error. Sef~
VSE/VSAM documentation for
open error code code.

783E

Explanation: The call to VSE/VSAM
results in an error code indicating that
an error in processing the
DLBL/EXTENT information you
supplied.

Close error on DDNAME: possible
user programming error. See
VSE/VSAM documentation for
close error code code.
Explanation: The call to VSE/VSAM
results in an error code indicating that
an error in processing occurred due to
an error in your program.
System Action: Your program is
terminated with an ABEND 35.

System Action: Your program is
terminated with an ABEND 35.

User Response: None.
User Response: None.
784E
781E

Open error on DDNAME: possible
catalog error. See VSE/VSAM
documentation for open error
code code.

Close error on DDNAME: possible
system error. See VSE/VSAM
documentation for close error
code code.
Explanation: The call to VSE/VSAM
results in an error code indicating that
there is a serious error in eMS or in
eMS/DOS making continued processing
of the application unwise.

Explanation: The call to VSE/VSAM
results in an error code indicating that
an error exists irl the specified catalog.
System Action: Your program is
terminated with an ABEND 35.

System Action: Your program is
terminated with an ABEND 35.

User Response: None.
User Response: None.
782E

Open error on DDNAME: possible
system error. See VSE/VSAM
documentation for open error
code code.
Explanation: The call to VSE/VSAM
results in an error code indicating that
there is a serious error in eMS or in
eMS/DOS, making continued processing
of the application unwise.
System Action: Your program is
terminated with an ABEND 35, except
for error code 34, in which case your
program is terminated but an ABEND is
not issued.
User Response: None.

428

VM/Sf' System Messages and Codes

785E

Error in request macro
processing: possible user
programming
error. See VSE/VSAM error code
code, return code = nnn.
Explanation: The call to VSE/VSAM
results in an error code indicating that
an error in processing occurred due to
an error in your program.
System Action: Your program is
terminated with an ABEND 35.
User Response: None.

(

DMS
786E

Error in request macro
processing: possible system error.
See VSE/VSAM error code code,
return code = nnn.

789W

Invalid response
Explanation: Your response to a query
is not one of those expected by the
VSEVSAM EXEC.

Explanation: The call to VSE/VSAM
results in an error code indicating that
there is a serious error in C MS or in
CMS/DOS making continued processing
of the application unwise.

System Action: The system waits for
you to enter another response. You
have two chances to enter a proper
response. If you are not successfui on
the second try, the VSEVSAM EXEC is
exited.

System Action: Your program is
terminated with an ABEND 35.

User Response: Enter a response.
User Response: None.
790R
787E

Error decompressing macroname
macro
Explanation: An error occurred in the
routine that decompresses macros read
in from tape. The reason may be that
the macro is not in standard VSE
compressed format.

Explanation: You must supply the
library name to be used.
System Action: The system waits for a
response.

System Action: VMDOS terminates
processing of the macro, then goes on to
process the next macro requested, or
exits, if no more macros were requested.
User Response: Be sure that the tape
is the compressed Source Statement
Library tape.

788R

Are the macros to be read from
tape or are they already on disk?
Reply TAPE or DISK. (Press the
ENTER key for a default of
TAPE.)
Explanation: The VSEVSAM EXEC
asks you if the macros are on tape or on
disk.
System Action: The system waits for a
response.
User Response: Enter "DISK" if the
macros are already on disk. If the
macros are to be read from tape, press
"ENTER."

If the default library name of
VSEVSAM is to be used, press the
ENTER key; else, enter the name
to be used for the library.

User Response: Enter the library name
to be used or just press "ENTER" to use
the default library name of
"VSEVSAM."

7911

The library name will be libname.
If the name is correct, press the
ENTER key; else, enter the name
to be used for the library, or enter
QUIT to exit.
Explanation: You can verify that the
correct library name will be used. You
have the opportunity to change the
library name or to stop execution.
System Action: The system waits for a
response.
User Response: If the library name is
correct and you want to continue, just
press "ENTER." If you want to use a
different library name, enter the name
you want to use and press "ENTER."
Otherwise, type "QUIT" and press
"ENTER" to exit.

Conversational Monitor System (eMS) Messages

429

DMS
792R

Are the macros to be erased from
disk? Reply YES or NO (press the
ENTER key for default of YES).

795E

Explanation: An error occurred while
using the VMFDOS module to read and
decompress macros from the VSE/VSAM
Optional Source Statement Library tape.

Explanation: Your response
determines whether or not the macros
will be erased.

System Action: The VSEVSAM EXEC
is exited with RC = 8.

System Action: The system waits for a
response.

User Response: Be sure that the
correct tape (VSE/VSAM Optional
Source Statement Library tape) is
attached to your virtual machine as
virtual 181. If the problem persists,
contact your system support personnel.

User Response: If you want to keep
the macros on disk, enter "NO,"
otherwise, the macros are erased.

7931

Error reading macros from tape

MACLIB generation completed
Explanation: VSEVSAM issues this
informational message to indicate to
you that the macro library has been
created.

796E

Error reading from VSEVSAM
SCAN file
Explanation: An unexpected error
code was returned by EXECIO while
reading from the 'VSEVSAM SCAN'
file.

System Action: None.
User Response: None.

System Action: The VSEVSAM EXEC
is exited with RC = 12.
794E

Error in MAC LIB generation
User Response: Issue the VSEVSAM
EXEC again. Respond 'disk' to message
DMSWVV788R. If the problem persists,
contact your system support personnel.

Explanation: An error occurred while
using the MACLIB command to
generate the VSEVSAM MACLIB.
System Action: The VSEVSAM EXEC
is exited with RC = 4.
User Response: Issue the VSEVSAM
exec again. Respond 'disk' to message
DMSWVV788R. In respoI?-se to message
DMSWVV808R, press the ENTER key.
If the problem persists, contact your
system support personnel. There may be
a problem with the MACLIB command
or with the macros that are used to
build the MACLIB.

430

VM/SP System Messages and Codes

7971

QUIT may be entered in response
to any query to end processing
Explanation: VSEVSAM issues this
informational message to indicate that
you can end processing by entering
"QUIT" to any query.
System Action: None.
User Response: None.

DMS
798R

The VSE/VSAM optional source
statement library tape must be
mounted as virtual 181. If it is
not, type QUIT here and have the
tape mounted; else press the
ENTER key to continue.

800E

Explanation: One of the files supplied
with the VM/SP system that is
necessary to generate the "VSEVSAM
MACLIB" is missing. It may be one of
the following files: "OPEN MACRO,"
"OPENR MACRO," "CLOSE MACRO,"
"CLOSER MACRO," "CDLOAD
MACRO," "GET MACRO," "PUT
MACRO," or the "VSEVSAM SCAN"
file.

Explanation: VSEVSAM issues this
message to remind you that you must
have the VSE/VSAM Optional Source
Statement Library tape mounted as
virtual 181.
System Action: The system waits for a
response.

System Action: The VSEVSAM EXEC
is exited with RC=2.

User Response: If you do not have the
VSE/VSAM Optional Source Statement
Library tape mounted as virtual 181,
then enter "QUIT" and have the tape
mounted. Otherwise, just press
"ENTER."

User Response: Be sure that the files
listed in the above explanation are
available on the system disk.

8011
799E

Error reading from VSEVSAM
SCAN file; all macros may not be
erased
Explanation: An unexpected error
code was returned by EXECIO while
reading from the "VSEVSAM SCAN"
file. Since this occurred while the
macros were being erased, and since the
EXEC is exited when the error is
encountered, all of the macros that were
read in from tape may not have been
erased before the EXEC was exited.

One of the files needed for
MACLIB generation is missing

Arguments entered are ignored
Explanation: A parameter was
specified on the 'VSEVSAM' command
line. The VSEVSAM EXEC does not
accept parameters.
System Action: Processing continues.
User Response: None.

8021

Macros erased; VSEVSAM
processing complete
Explanation: VSEVSAM issues this
informational message to indicate to
you that the macros have been erased.

System Action: The VSEVSAM EXEC
is exited with RC = 12.
User Response: The maclib has been
successfully generated. You can use the
CMS ERASE command to delete any
files that were not successfully erased
by the VSEVSAM EXEC.

System Action: None.
User Response: None.

803E

Invalid parameter specification
Explanation: The format of either the
catalog name or the password passed to
CATCHECK is invalid. This might
indicate that the catalog name or
password is too long.

Conversational Monitor System (CMS) Messages

431

DMS
on your system. If the problem persists,
call your system support personnel.

System Action: RC = 4.
User Response: Refer to the
CATCHECK documentation in the
VM/ SP CMS Command Reference for
the correct format of a catalog name or
password.

804S

807S

Explanation: An attempt to issue an
ASSGN for the non-CMS/DOS user for
an IJSYSCT or IJSYSUC DLBL results
in an error in the ASSGN routine.

Error establishing CMS/POS
environment

System Action: RC = 20.

Explanation: An error occurred during
storage initialization for the CMS/DOS
environment. If you are an OS/VSAM
user, this may also mean that an error
occurred while doing a "SET DOS ON
(VSAM."
System Action: RC = 8.

User Response: Run your job again. If
the problem persists, call your system
support personnel.

808R

User Response: Issue the command
again. If the problem persists, call your
system support personnel.

805S

Explanation: An error occurred while
processing the" ASSGN SYSLST
PRINTER" command issued to direct
output to the printer.

System Action: The system waits for a
response.
User Response: If you want the macro
to be erased press the enter key. Enter
"QUIT" to exit the VSEVSAM EXEC.

System Action: RC = 12.

806S

VSE/VSAM phase IKQVCHK not
found
Explanation: The CDLOAD SVC is not
able to locate the VSE/VSArvl Catalog
Check Service Aid phase "IKQVCHK"
in the CMS VSAM segments.
System Action: RC = 16.
User Response: Verify that
VSE/VSAM has been properly installed

432

VM/SP System Messages and Codes

Macro library libname will be
erased.
Press the ENTER key to continue
or type QUIT to exit.
Explanation: The VSEVSAM EXEC
allows you to verify that the correct
library is erased.

Error assigning output to printer

User Response: Verify that your
virtual printer is properly defined. Run
your job again. If the problem persists,
call your system support personnel.

Error encountered issuing ASSGN
for catalog

809E

Error copying VSEVSAM SCAN
file from {T-IS-}disk to A-disk
Explanation: If no "VSEVSAM SCAN"
file is found on the user~s A-disk, the
VSEVSAM EXEC tries to copy the file
from the T - or S-disk to the user's
A-disk. This is done because the
VMFDOS module used to read the
macros from tape expects the SCAN file
to be on the A-disk.
System Action: "VSEVSAM EXEC" is
exited with RC = 14.
User Response: Be sure that the
'VSEVSAM SCAN' file is on the T- or
S-disk.

DMS
812E

Input was ignored.

815E

Explanation: CMSSERV
communications read your input~ but
detected that the input was entered on a
screen other than the CMSSERV panel.
When the input was read, the
CONSOLE facility was not able to
inform CMSSERV that the input came
from another screen; therefore,
CMSSERV communications ignored the
input. See the description of the
CONSOLE facility in either the VM/SP
Release 5 Guide, SC24-5290 or the
VM/ SP System Reference for elvIS,
SC24-5286.
System Action: CMS ignored your
input and the CMSSERV panel was
displayed.

Explanation: The double-byte
character set (DBCS) string supplied as
a substitution was invalid.
System Action: RC = 8. After this
message is displayed, the message you
requested is either displayed or put into
a buffer; however, "**,, is put in the
message as a substitution rather than
the DBCS string you requested.
User Response: Correct the DBCS
string you coded and reissue the
message call.

823E

User Response: None, but you may
want to check whatever was running
before the CMSSERV panel was
displayed to be sure that it is correct.

813E

Invalid double-byte character
string text replaced by ,**,

PTF name1 is listed as a dependent
of PTF name2, but it is not
merged.
Explanation: The Reqby Log contains
an invalid entry. Change name2listed
change name1 as a prerequisite or
corequisite. However, VMFREMOV
discovered that change name2 was on
the system without change namel.
There is the possibility that the Reqby
Log does not accurately reflect applied
serVIce.

repos repository not found,
message nnnn cannot be retrieved
Explanation: The requested message
was not found in the specified
repository.

System Action: Processing ends.
System Action: RC = 16.
User Response: Erase the Req by Log
and reissue VMFREMOV with the
CONVERT option to rebuild the Reqby
Log correctly. For more information on
VMFREMOV, see the VM/SP
Installation Guide.

User Response: Verify the command,
verify that the repository exists, and
reissue the command.

814E

Message number nnnn, format nn,
line nn was not found; it was
called from routine in application
applid

824E

prodid VMFREQBY may be
incomplete due to a missing SCF

Explanation: The message requested
could not be found in the specified
repository.

Explanation: The Service Control File
(SCF) for a merged PTF was not
available on any Delta disk.

System Action: RC = 12.

System Action: The exec continues to
build the Reqby Log; however, the log
will be incomplete if the missing Service
Control File contained requisites.

User Response: Verify the command
and reissue it.

Conversational Monitor System (CMS) Messages

433

DMS
Processing ends after the build of the
Reqby Log completes. The Remove List
or Merge List is not processed.

User Response: You can correct the
error by making the Service Control
File available, erasing the Reqby Log,
and reissuing the command. If you
chose not to correct the Reqby Log, you
can still reissue the command; however,
you run the risk of removing a change
without removing changes which are
dependent upon it.
825E

order. If no local libraries exist, the
command should be:
GLOBAL TXTLIB ERPTFLIB EREPLIB

Reissue the CPEREP command. If the
problem persists, call your system
support personnel.

8281

Explanation: CLEAR/CLEARF or
ZERO was specified by the user, or
other parameters caused ZERO to be
requested by default. The VM
error-recording cylinders have been
erased. If CLEARF was specified, the
303X M CH and CCH frame records were
updated.

CLEAR IS VALID ONLY WHEN
SPECIFIED BY ITSELF
Explanation: CLEAR or CLEARF was
specified along with other parameters.
This is prohibited. The CLEAR
parameter must be specified by itself,
with no reports requested.
System Action: RC = 12.
Execution halts. The system status
remains the same. No clearing takes
place. No report is printed.
User Response: If you want the report,
reissue the CPEREP command
requesting the report without the
CLEAR parameter. Include the ZERO
parameter to clear the 3rror-recording
area after the report is completed. If you
want only to clear the ERDS, reissue
CPEREP specifying only the
CLEAR/CLEARF operand.

826E

EREP TXTLIBS NOT FOUND
Explanation: In attempting to search
the EREP TXTLIBs, DMSIFC found
that the pointer to the first rrXTLIB
contained zeros.
System Action: RC = 56.
Execution halts. System status remains
the same.
User Response: Issue a GLOBAL
TXTLIB command listing the applicable
EREP TXTLIBs in the proper search

434

VM/SP System Messages and Codes

CPEREP ZERO OR CLEAR HAS
BEEN COMPLETED

System Action: RC = O.
Control returns to CMS.
User Response: None required.
829W

ATTEMPTED ZERO WAS
SUPPRESSED. REQUIRES
PRIVILEGE CLASS F
Explanation: CLEAR or ZERO was
specified by the user, or other
parameters caused ZERO to be
requested by default. The VM/370
error-recording cylinders were not
erased because the user was not
authorized to do so. Only class F users
can erase the error-recording area.
System Action: RC=88 or O.
If the CLEAR function failed, the return
code will be 88. If the ZERO function
failed, the return code will be O.
Reports (if requested) have already been
generated. Control returns to CMS.
User Response: None required if
ZERO was requested by mistake or
default. If you need to erase the
error-recording cylinders, see your
system support personnel to get a class
F directory entry.

(

DMS
830E

I/O ERROR READING A BLOCK
OF RECORDS FROM THE ERROR
RECORDING CYLINDERS

Explanation: DMSREA, the CPEREP
read module, encountered a permanent
input/output error while attempting to
read a 4K block of records from the
error recording area. Probable
hardware error.
System Action: RC = 60.
Execution halts. System status remains
the same.
User Response: Execute the DDR
service program to obtain a dump of the
error- recording cylinder on which the
input error occurred. Reconstruct the
data on the error-recording cylinders. If
the reconstruction process is successful,
initiate the CPEREP operation again. If
the error recurs, call your system
support personnel.

831E

new release) that has made it
incompatible with the interface provided
by CPEREP. nnn is one of the
following reason codes:

Code Meaning
001

An EXCP was attempted with a
DCB other than that of the
SYS1.LOGREC data set.

002

OS/VS EREP is expected to use
only one lOB and one channel
program when it uses EXCP to
access the SYS1.LOGREC data set.
But it has attempted to use lOBs
or channel programs at more than
one location in storage.

003

The expected read/write command
in the channel program for
accessing SYS1.LOGREC contains
an unexpected op code.

004

While reading error records (with
EXCP) from (simulated)
SYSl.LOGREC, OS/VS EREP
made an attempt to read
non sequentially prior to
completion of the sequential
reading phase.

005

An attempt was made to read
record 2 of SYSl.LOGREC (the
time stamp record), which
CPEREP does not simulate.

006

The first EXCP to SYS1.LOGREC
was not the expected read of the
SYS1.LOGREC header record.

MORE THAN 100 CHARACTERS
OF OPTIONS SPECIFIED

Explanation: The maximum number of
characters that can be used to specify
CPEREP operands is 100. More than
100 characters were used.
System Action: RC = 62.
Execution halts. System status remains
the same.
User Response: Check the valid
command options. Reissue the
command using fewer than 100
characters to specify the options.

832S

SOFTWARE INCOMPATIBILITY
AT THE CPEREP-EREP
INTERFACE; CODE=NNN

Explanation: CPEREP is OS/VS EREP
running under CMS with CPEREP
providing interface code between OS/VS
EREP and CMS. Some change has been
made to OS/VS EREP (via PTF, or a

007 The channel program for accessing
SYS1.LOGREC does not have the
expected format.
008

An invalid disk address (CCHHR)
was used while attempting to
access SYS1.LOGREC.

009

There are no error records and yet
OS/VS EREP attempted to read
error records.

Conversational Monitor System (CMS) Messages

435

DMS
010

An invalid record length was
encountered while reading
SYSl.LOGREC. This may be due
to error records being overlaid on
the error cylinders.

844E

Explanation: Because of conditions
encountered during processing, no
modules were link edited. These
conditions will have caused messages to
be printed explaining specific problems.

System Action: RC = 104
CPEREP terminates with EREP
message(s) IFC1351 or IFC149I.

System Action: Processing ends.
User Response: Check the previous
messages and take appropriate action.

User Response: Reissue the command,
or have your system programmer try it.
If the problem persists, call your system
support personnel.
845W
842E

No {controillibrary} file name
found in In It lim]

•

A %CONTROL statement was found
in the LKEDCTRL file but there
was no control file name on the
%CONTROL~a~men~~

System Action: Processing ends.

A %LIBRARY statement was found
in the LKEDCTRL file but there
was no library file name on the
%LIBRARY statement.

User Response: Check the previous
messages and take appropriate action.

8461
System Action: Processing ends.

8431

LKED targeCmodule into library,
RC=nn

User Response: Correct the statement
and reissue the command.

Explanation: The link edit of
target_module gave the indicated return
code.

An invalid control record was
found and ignored

System Action: If the indicated return
code was less than the maximum
allowable, processing continues.
Otherwise, processing ends.

Explanation: An invalid control record
was found in the input control file. The
contents of that record are shown
following this message.
System Action: The record is ignored
and processing continues.
User Response: None

436

Errors were encountered during
the link edit processing that will
probably make the loadlib
unusable.
Explanation: During the Linkage
Editor's processing of one or more
modules a return code was greater than
the specified maximum allowable return
code. Previous messages will have been
issued which describe the errors.

Explanation: The name of the file you
specified could not be found in the
indicated file. Either:
•

No linked it performed

VM/SP System Messages and Codes

User Response: If errors occurred,
correct the errors and reissue the
command.

DMS
847R

System Action: The system waits for a
response.

Enter name of SNT definition file
or press ENTER key to quit
Explanation: SNTMAP processes
macro definitions that are in the SNT
definition file.
System Action: The system waits for a
response.

User Response: Enter a valid DASD
tpye.

850W

Explanation: The DASD type you
entered previously is not supported by
VM/SP.

User Response: Enter the file name. If
you don't enter the file type or file
mode, SNTMAP will assume the file
type is 'ASSEMBLE' and the file mode
is '*'

848E

System Action: SNTMAP will issue
message DMKWSM849R to prompt you
to enter the DASD type.
User Response: None.

Unable to proceed without
$DASD$ CONSTS file information
Explanation: This file contains
information about DASD that SNTMAP
needs for calculations and conversion.

851W

System Action: SNTMAP ends
processing.

System Action: SNTMAP continues
processing.
User Response: Correct the SYSSTRT
parameter in the SNT file or specify the
correct DASD type.

Enter volid DASD type or type
QUIT to end SNTMAP processing
Explanation: One of the following
happened:
SNTMAP wasn't able to find a CP
directory
SNTMAP found no USER
$SAVSYS$ entry in the CP directory
There were MDISK statements in
the directory that defined the DASD
type as FB-512
You previously entered an invalid
DASD type.

Page number exceeds device limit
of limit for sysname; SYSSTRT
parameter = parameter
Explanation: The page specification on
the SYSSTRT parameter is beyond the
limit for the DASD type.

User Response: Find the $DASD$
CONSTS file and make it accessible to
SNTMAP.

849R

devtype is not a valid DASD type

852E

SYSSTRT parameter for sysname
is not compatible with devtype
DASD type for volid; SYSSTRT
parameter = parameter
Explanation: The DASD type is a
count-key-data device, while the address
given on the SYSSTRT parameter is for
a fixed-block device, or vice-versa.
System Action: SNTMAP ends
processing.
User Response: Correct the SYSSTRT
parameter in the SNT file or specify the
correct DASD type.

Conversational Monitor System (CMS) Messages

437

DMS
853R

Enter the name of your current
CP directory file (the default is
VMUSERS DIRECT):

856E

Explanation: The directory contains a
USER $SA VSYS$ entry that describes
the DASD areas allocated for SNT data.
If SNTMAP can't find a directory,
SNTMAP will prompt you to enter the
DASD types.

Explanation: The specified disk
address was found more than once on
the specified entry records. A disk
address should only appear once in the
VMFP ARM file.

System Action: The system waits for a .
response.

System Action: For VMFZAP,
processing ends.

User Response: Enter the name of the
directory.

854W

Disk address vdev is listed more
than once on the {BASE, ZAP,I
DELTA} and/or MERGE entry
records in the prodid VMFPARM
file

For VMFMERGE, or VMFREMOV the
remaining disk addresses in the
VMFP ARM file are checked for
duplication first, then processing ends.

Unable to find CP directory file fn
no $SA VSYS$ boundary
checking will be done

it im;

Explanation: The directory contains a
USER $SAVSYS$ entry that describes
the DASD areas allocated for SNT data.
If SNTMAP can't find a directory,
SNTMAP can't check for $SA VSYS$
extent exceeded errors.

User Response: Check that the disk
addresses in the VMFP ARM file are
unique addresses, then reissue the
command.

857E

System Action: SNTMAP will issue
message DMSWSM849R to prompt you
to enter the DASD type.

Explanation: VMFMERGE or
VMFREMOV will only access the first
merge disk address and up to nine delta
disk addresses. They will not handle ten
or more de I ta disk addresses.

User Response: None.

855W

System Action: Processing ends.

No $SAVSYS$ areas defined in the
CP directory file; no $SA VSYS$
boundary checking will be done

User Response: Specify nine or less
unique disk addresses on the Delta
entry record in the VMFP ARM file,
then reissue the command.

Explanation: If SNTMAP can't find a
$SAVSYS$ entry in the directory,
SNTMAP can't check for $SAVSYS$
extent exceeded errors.
'858E
System Action: SNTMAP will issue
message DMSWSM849R to prompt you
to enter the DASD type.
User Response: None.

The number of disk addresses on
the DELTA entry record cannot
exceed nine.

Unable to find a tag(s) entry
record in the fn ft file.
Explanation: The specified entry
record could not be found in the given
file.
System Action: Processing ends.

438

VM/SP System Messages and Codes

DMS
User Response: For VMFZAP, if the
file is the prodid VMFP ARM file, check
the type of the missing record.
Determine which disks should be used,
and make the appropriate entry in the
prodid VMFP ARM file. If the file is a
ZAP control file, check which text file(s)
the zap is supposed to affect. Make the
appropriate NAME or DUMP entries in
the zap control file.

860E

Explanation: Within the prodid
VMFP ARM file, the specified record
appeared more than once. Only one
occurrence of each type of entry is
valid.

Reissue the command.

System Action: For VMFZAP,
processing ends.

For VMFMERGE or VMFREMOV,
insure that the required entry record is
in the given file, then reissue the
command.

859E

For VMFMERGE and VMFREMOV,
the remaining records in the
VMFP ARM file are checked and then
processing ends.

The prodid VMFPARM file has no
disk addresses on the
{BASEIMERGEIZAPIDELTA}
entry record.

User Response: For VMFZAP,
determine which disks (Base, Merge, or
ZAP) you need to use. Correct the
prodid VMFPARM file, and reissue the
command.

Explanation: The specified entry
record was found, but it did not have
any disk addresses on it.

For VMFMERGE and VMFREMOV,
insure that there is only one Merge and
Delta record entry in the VMFPARM
file, then reissue the command.

System Action: For VMFZAP,
processing ends.
For VMFMERGE or VMFREMOV, the
remaining records in the VMFP ARM
file are checked and then processing
ends.

8611

Accessing
{BASEIMERGEIZAPIDELTA} disk
vdev as mode
Explanation: Informational message
telling you what disk is temporarily
being accessed at what mode. This is
not an error.

User Response: For VMFZAP,
determine which disks (Base, Merge, or
ZAP) you need to use. Correct the
prodid VMFPARM file. Reissue the
command.
For VMFMERGE or VMFREMOV,
insure that there are disk addresses
listed on the appropriate record entries
in the VMFPARM file, then reissue the
command.

Only one
{BASEIMERGEIZAPIDELTA}
entry record may appear in the
prodid VMFPARM file.

System Action: Processing continues.
User Response: None

8621

{ ZAP I Change } name { has been
action I is no longer
SUPERSEDED by name}
Explanation: For VMFZAP, the
indicated zap has been successfully
applied.

Conversational Monitor System (CMS) Messages

439

DMS
For VMFMERGE, the indicated PTF or
ZAP has been successfully merged or
superseded. If the change was
SUPERSEDED, the name of the
superseding PTF is also given. For
VMFREMOV, the indic&ted PTF or ZAP
nas 1een successfully removed or is no
longer SUPERSEDED.

8641

PTF name will not be action
because it already is status.
Explanation: VMFMERGE will not
merge a PTF which is already
superseded or merged.
System Action: Processing continues.

System Action: Processing continues.

User Response: None

User Response: None.
864W
863E

The {MERGEIZAP} disk vdev must
be linked read-write.
Explanation: The specified address
from the VMFP ARM file is a disk which
is linked read-only. The disk must be
linked read-write.
System Action: Remainder of the disks
are checked and processing ends.
User Response: Check that the disk
address on the specified record of the
VlVlFP ARM file is correct. If so, link to
this disk in write mode. If the disk
address is not correct, change it.
Reissue the command.

864E

PTF name will not be action
because it already is status
Explanation: VMFMERGE will not
exclude a PTF which is already merged,
superseded or excluded. If you want an
excluded PTF to be merged, it must be
removed from the exclude list and added
to the apply list.
System Action: Processing ends.
User Response: None

440

VM/SP System Messages and Codes

{PTF IZAP} name will not be action
because it {already is I is not}
status
Explanation: For VMFZAP, the
change specified currently has the
designated status and cannot be
changed to the new status. This means
the zap has been superseded and will
not be reapplied.
For VMFl\IERGE, a requisite PTF
which is already excluded will not be
merged.
For VMFREMOV, a PTF which is not
merged or was merged and then
superseded, will not be removed.
System Action: For V:MFZAP,
processing continues with the next ZAP
name, if any.
For VMFMERGE or VMFREMOV,
processing for the current PTF ends, but
processing for remaining PTF(s)
continues.
User Response: To avoid this message
on future VMFZAP invocations, remove
the zap name from the ZAPLIST for this
product.
For VMFMERGE or VMFREMOV,
there is no response.

DMS
8651

Processing {PTF

I ZAP} name

System Action: Processing ends.

Explanation: Informational message
telling which change is currently being
processed. This is not an error.

User Response: Check that the PTF(s)
to be applied all belong to the same
product, then reissue the command.

System Action: Processing continues.
869E
User Response: None

866W

Explanation: VMFMERGE was
getting information about the changed
elements from the file specified when a
filename - filetype pair was not found on
an element tag or a single filetype was
not found on a replace tag.

No PTFs have been action
Explanation: VMFMERGE tried to
merge the PTF(s) you specified, but
none merged.
VMFREMOV tried to remove the PTF(s)
you specified, but none were removed.

System Action: Processing ends.
User Response: Look at the specified
tag in the specified Service Control File
(SCF). Insure that all element tags have
both a filename and filetype specified
and all replace tags have a single
filetype specified.

System Action: Processing finishes.
User Response: Correct the problems
indicated by the individual PTF error
messages issued by VMFMERGE or
VMFREMOV then reissue the
command.
870E
867E

Invalid status status in prodid
VMFMGLOG for entry ptl.

System Action: Processing ends.

System Action: The remaining records
are checked and then processing ends.

868E

PTF name is not a part of product
prodid.
Explanation: A PTF you specified
belongs to a different product. Only the
PTFs that are part of the product
specified on the command will be
processed.

Error in file fn ft fm. There are no
elements.
Explanation: A Service Control File
(SCF) was found with no elements in it.
There must be at least one ELEMENT
tag along with a corresponding
REPLACE tag in an SCF.

Explanation: VMFMERGE or
VMFREMOV found an invalid status
for the specified entry in the Merge Log.
Valid status values are MERGED and
SUPERSEDED.

User Response: Correct the specified
entry in the Merge log and reissue the
command.

Error in file In ft fm data is invalid
for tag tag.

User Response: Replace or fix the
specified SCF then reissue the
command.

871E

Error in file fn ft fm. The name tag
is missing.
Explanation: The specified tag was not
found in the given Service Control File
(SCF).
System Action: Processing ends.

Conversational Monitor System (CMS) Messages

441

DMS
User Response: Replace or fix the
specified SCF then reissue the
command.

872E

For VMFMERGE or VMFREMOV, the
remaining records are checked and then
processing ends.
User Response: For VMFZAP, make
the necessary corrections to the record.
In a ZAP control file, valid entries have
a text file name and csect name after a
NAME or DUMP tag. Reissue the
command.

Error in file fn {t {m. REPLACE
tag missing after element name
Explanation: A Service Control File
(SCF) was found with no REPLACE tag
after an element.

For VMFMERGE or VMFREMOV,
correct the invalid entry in the specified
file and· reissue the command.

System Action: Processing ends.
User Response: Replace or fix the
specified SCF then reissue the
command.

873E

Error in file {n ft (m. parm is an
invalid parameter. Expecting
parameter(s) PRODID, PREREQ,
COREQ, SUP, APARTEXT, or
CHANGES.
Explanation: An invalid parameter
was specified trying to retrieve data
from a Service Control File (SCF) using
the XEDIT macro named MRGSC
XEDIT.
System Action: Processing ends.
User Response: If you invoked
MRGSC XEDIT to get data from an
SCF, you did so incorrectly. If it was
VMFMERGE that invoked MRGSC
XEDIT, then an interface problem
exists.

874E

Invalid entry found at line line in
fn ft
Explanation: An invalid entry was
found at the specified line in the
specified file.
System Action: For VMFZAP,
processing ends.

442

VMjSP System Messages and Codes

875E

File {n {t {m not found on any
disks from the VMFPARM file.
Explanation: For VMFZAP, the
specified file could not be found on any
of the disks which were entered on the
BASE, MERGE, and ZAP entry records
of the VMFP ARM file for this product.
For VMFZAP, any file which is on a
disk not entered on the BASE, MERGE,
or ZAP records in the VMFP ARM file
will be ignored.
For VMFMERGE and VMFREMOV,
the specified file could not be found on
any of the disks which were entered on
the MERGE or DELTA entry records of
the VMFP ARM file for this product.
For VMFMERGE and VMFREMOV,
any file which is on a disk not entered
on the MERGE or DELTA records in
the VMFP ARM file will be ignored.
To find which disk a missing file should
reside on, refer to the description of the
appropriate file in the VM/ SP
Installation Guide.
System Action: Processing ends.
User Response: See if the proper disks
are specified in the VMFP ARM file.
Reissue the command.

DMS
876E

The total number of disk
addresses on the BASE and
MERGE entry records cannot
exceed nine.

878E

Explanation: The prodid ZAPLIST file
contains the names of ZAPs you want to
apply to a particular product. VMFZAP
will not apply any ZAPs which have
been superseded by other service. The
ZAPLIST for this product either
contains no non-comment ZAP names,
or any ZAP names in the ZAPLIST are
already superseded.

Explanation: The prodid VMFP ARM
file contains the disk addresses of disks
to be used when applying zaps to this
product. VMFZAP only allows 10 total
product disks to be accessed. Exactly
one' ZAP disk will be accessed. If more
than one disk address is listed on the
ZAP record, only the first one will be
used. The Merge and Base records of
the VMFP ARM file contained more
than the 9 remaining allowable disk
addresses.

System Action: Processing ends.
User Response: Check that there are
no other ZAPs you want to apply to this
product. If there are other ZAPs to be
applied, update your ZAPLIST by
removing the old ZAP names and
entering the new ones, and reissue the
command.

System Action: Processing ends.
User Response: Determine which disks
are really needed to apply ZAPs to this
product. Make the necessary
corrections to the Base, Merge, and ZAP
records of the prodid VMFPARM file.
Reissue the command.

877W

prodid ZAPLIST does not contain
any unsuperseded zap names. No
zaps will be applied.

879W

{ZAP I Change} name name
appears more than once in the fn
ft [It will only be applied once].

fn TEXT was previously zapped
but was not found on the ZAP
disk.

Explanation: A ZAP or change name
was found more than once in the
specified file.

Explanation: While erasing TEXT files
for the current product from the ZAP
disk, VMFZAP found the name of a
TEXT file in the VMFZPLOG but could
not find the TEXT file on the ZAP disk.
Some processing external to VMFZAP
either moved or erased the file. Since
VMFZAP would have erased the file
anyway as part of "cleaning up" the
ZAP disk before applying and
re-applying ZAPs, only a warning
message is issued.

System Action: For VMFZAP, the
specified ZAP will only be applied once.
Processing continues.
For VMFREMOV, the specified change
will only be processed once. Processing
continues.
User Response: Remove and duplicate
entries for this ZAP or change name
from the specified file.

System Action: None.
880E
User Response: You may wish to look
into why the file was moved or erased
from the zap disk.

Error in ZAPTEXT while
processing fnl TEXT, RC = nne
Text files affected by fn2 ZAP will
not be saved on the ZAP disk.
Explanation: The CMS ZAPTEXT
command returned a non-zero return
code. To protect your system from

Conversational Monitor System (CMS) Messages

443

DMS
incomplete or incorrectly applied ZAPs,
the temporary files which were ZAPped
will not be renamed to their permanent
names on your ZAP disk. These
temporary files will be erased.

883W

PTF name is not a part of product
prodid and must be action in
product prodid
Explanation: A PTF has a requisite or
dependent which belongs to a different
product. VMFMERGE and
VMFREMOV do not perform
cross-product checking.

System Action: Processing ends.
User Response: If possible, correct the
situation and reissue the comm~nd.

System Action: Processing continues.
881E

User Response: For VMFMERGE, if
the specified PTF is not already merged,
then merge it in the other product after
the processing for this product is
complete.

In TEXT was found on the ZAP
disk but was not zapped during
this VMFZAP run. This file
should not be on the ZAP disk.
Explanation: While searching for text
files to be ZAPped, VMFZAP found the
specified file on the ZAP disk. Unless
hi t by a previous ZAP during the
current run of VMFZAP, there should
not be a copy of the text file on the ZAP
disk.

For VMFREMOV, if the specified PTF
is not already removed, then remove it
from the other product after the
processing for this product is complete.

8841

System Action: Processing ends.
User Response: Check that the proper
zap disk has been specified for this
product in the VMFPARM file. If so,
move or erase the text file from that
disk. Reissue the command.

882E

System Action: Processing ends.
User Response: See if the proper disks
are specified in the VMFP ARM file.
Reissue the command.

444

Explanation: SNTMAP successfully
completed processing.
System Action: None.

File In ft 11m] [from name] not
found on any DELTA disks from
the VMFPARM file.
Explanation: The specified file could
not be found on any of the disks which
were entered on the DELTA entry
record of the VMFPARM file for this
product. Any file on a disk which is not
entered in the VMFPARM file will be
ignored.

VMjSP System Messages and Codes

Results of mapping are in two
eMS files: DASD SNTMAP
contains DASD related
information, and MEMORY
SNTMAP contains memory
related information.

User Response: None.

8851

File prodid VMFZPLOG not found
on the ZAP disk. No text files will
be removed from the ZAP disk.
Explanation: There was no
VMFZPLOG for the current product on
the ZAP disk, so VMFZAP assumes that
no ZAPs have been applied to this
product and that there are no text files
on the ZAP disk which need to be
erased before application of new ZAPs.
This is not necessarily an error. There
may in fact be no ZAPs applied to the
product.

DMS
System Action: None

888E

User Response: If VMFZAP continues
with no messages regarding files which
were on the ZAP disk but should not
have been, then no action is required. If
messages are issued regarding files
found on the ZAP disk which should not
have been there, then a VMFZPLOG
should have existed on the ZAP disk for
this product. Either find the
VMFZPLOG and move it to the ZAP
disk, or erase the text files which have
been zapped from the ZAP disk. Reissue
the command.

Explanation: The specified Service
Control file does not contain an element
that the Merge Log indicates it should
contain.
System Action: Processing ends.
User Response: Correct the specified
Service Control File or the Merge Log
and Reissue the command.

892E
886E

Filename name from the In It [1m]
file is longer than 8 characters.

System Action: The remaining
filenames are checked and then
processing ends.
User Response: Check that all the
filenames in the indicated file are eight
characters or less.

System Action: For VMFMERGE,
processing continues if the error was
due to an EXCLUDED requisite;
otherwise, processing ends.

Record number number from the
In ft 1m file is longer than 80 bytes.

For VMFREMOV, processing continues
with the next change to be removed.

Explanation: The ZAP control file
contains a record which is longer that
80 characters. The ZAP control file
must have a maximum width of 80
characters.
System Action: Processing ends.
User Response: Correct the ZAP
control file and reissue the VMFZAP
command.

PTF name has not been action
Explanation: For VMFMERGE, the
indicated PTF was not merged. There is
either a problem with this PTF, or with
one of its requisites. The specific
problem is indicated by a previous
message. For VMFREMOV, the
indicated PTF was not removed. There
is either a problem with this PTF, or
with one of its dependents. The specific
problem is indicated by a previous
message.

Explanation: A filename was found in
the specified file which is more than
eight characters long. CMS only allows
eight character filenames.

887E

Error in file name SCF. No entry
for element fn ft

User Response: Use the message(s)
provided to determine what the error is.
Once the error is fixed, reissue the
command.

893E

Incomplete processing, not all
[required] PTFs were action
Explanation: The PTF you specified
was not processed due to an error, but
at least one requisite PTF was
processed. The specific problem is
indicated by a previous message.
System Action: Processing ends.

Conversational Monitor System (eMS) Messages

445

DMS
User Response: Use the message(s)
provided to determine what the error is.
Once the error is fixed, reissue the
command. A build at this time is not
recommended because the merge was
incomplete.

893W

•

If the message text is 'File fn ft fm

not found', then a specific filetype
was specified in the member list
EXEC. Check that the object code
file for the indicated member exists.
If the file type is not TEXT, you may
rename it to a filetype of TEXT, or
you can update the member list and
specify the existing filetype.

Incomplete processing, not all
[required] PTFs were action

If you rename the object file to have

Explanation: The PTF you specified
was not processed due to an excluded'
requisite.

a filetype of TEXT, you may issue:
TXTLIB VMFTXT ADD
membername
RENAME VMFTXT TXT LIB A
libname = =

System Action: Processing continues.
User Response: Determine wpether the
requisite should be excluded or not. If
so, remove it from the Exclude List and
reissue the command. Otherwise,
remove the PTF from the Apply List and
use VMFREMOV to remove any other
requisites that may have been merged
for that PTF.

8951

Member In It added.
Explanation: VMFTXT added the
indicated member to the library you
specififd.
System Action: Processing continues.
User Response: None.

896E

File {In It 1m I In TEXT or In TXT*}
not found.

If the filetype specified in the
member list EXEC file is not TEXT,
erase VMFTXT TXT LIB A and
reissue the command.
•

If the message text is 'File fn TEXT

or fn TXT* not found', then a
specific filetype was not specified in
the member list EXEC. Check that
an object file for this indicated
member exists. Look at the CNTRL
file that you specified. Verify that
the object file has one of the listed
filetypes; and either rename the
object file to a listed filetype, or
update the member list and specify
the existing filetype. If you did not
specify a CNTRL filename, either
rename the object file to a filetype
of TEXT or update the member list
and specify the existing filetype.
If you renamed the object file to

Explanation: VMFTXT could not find
the object file for the indicated member
on any accessed disk.
System Action: Processing continues
for the remaining files in the member
list.
User Response:

446

VM/SP System Messages and Codes

have a filetype of TEXT, issue:
TXTLIB VMFTXT ADD
membername
RENAME VMFTXT TXTLIB A
libname = =
otherwise erase VMFTXT TXTLIB A
and reissue the command.

DMS
897E

Due to previous errors, the result
of this TXTLIB build is called
VMFTXT TXTLIB; your {n
TXTLIB has not been replaced.
Explanation: One or more errors has
occurred while building the TXTLIB.
System Action: Your original {n
TXTLIB (if it already exists) has been
unchanged. The new library is called
VMFTXT TXTLIB. The VMFTXT
TXTLIB file may be used for debugging
until you erase it or until you use the
VMFTXT EXEC again. RC = 40.
User Response: Correct the errors and
rerun VMFTXT.

I
I

Code Meaning
1
2

5
7

898E

VMFREMOV processing is
incomplete.
Explanation: VMFMERGE found the
temporary file prodid OVMFMGLG on
the Merge disk. This means that the
last time VMFREMOV was issued, the
exec was unable to finish processing.

System Action: Processing ends.
14

User Response: Reissue the
VMFREMOV command to complete the
remove process. Once the remove is
complete, reissue the VMFMERGE
command.

The file was not found.
The address of the buffer was
not within virtual storage
limits.
A permanent disk error
occurred. This may occur if
you link to and access another
user's disk, and try to read a
file that was refiled by its
owner after you issued the
ACCESS command. Reissue
the ACCESS command and try
to read the file again.
The number of records is less
than 0 or greater than 32768.
The fixed/variable flag is not F
orV.
The record read is longer than
the buffer.
The specified file is open for
writing; it must be closed and
opened for reading.
The number of records is
greater than 1 for a
variable-length file.
The end of the file was
reached.
An invalid displacement
appears in the AFT for a
variable-length file.
An invalid character appears
in the filename.
An invalid character appears
in the filetype.

'function' = WRBUF

Code Meaning
901T

Unexpected error at ustorl: plist
{unction {n {tIm at ustor2, base
ustor3, rc = nn
Explanation: An unexpected error
occurred in COPYFILE or LOADLIB
processing. The "function" indicates
one of the following CMS functions:
RDBUF, WRBUF, FINIS, ADTLKP,
FSTLKP, or RENAME. The return
code "nn" indicates one of the following
condi tions:
'function'

RDBUF

2
4

5
6
7

8
10

The virtual storage address
equals zero.
The first character of the
filemode is invalid.
The second character of the
filemode is invalid.
The r.ecord number or number
of records is too long.
An attempt was made to skip
over an unwritten
variable-length record.
The number of bytes was not
specified.
The maximum number of CMS
files (3400) was reached.

Conversational Monitor System (CMS) Messages

447

DMS
11
12
13
14

17
18

20
21

System Action: RC = 256.
Execution of the command is
terminated. The system status remains
the same, with the following exceptions:

The fixed/variable flag is not F
or V.
The disk is read-only.
The disk is full.
The number of bytes to be
written is not integrally
divisible by the number of
records to be written.
The length of this record is not
the same as that of the
previous record.
The characteristic (F or V) is
not the same as the previous
record.
A variable-length record is
greater than 65K bytes.
The number of records is
greater than 1 for a
variable-length file.
The maximum number of data
blocks (16060) had been
reached.
An invalid character appears
in the filename.
An invalid character appears
in the filetype.

•

If the APPEND option was specified
and the copying process began
before the error was discovered,
records have been appended to the
output file.

•

If the NEWFILE (the default),
REPLACE, or OVLY option was
specified, and the copying process
began before the error was
discovered, then COPYFILE
CMSUT1, on the output disk,
contains the records copied so far.

•

If multiple-output-file mode, several
output files may have been created
before the error was discovered.

User Response: Refer to the "function"
parameter and the RC "nn" parameter
to determine if an input/output error
occurred. If it did, try to reissue the
command. Otherwise, contact your
system support personnel for assistance.

'function' = FINIS

Code Meaning
6
The file is not open.
902T

IPL device read I/O error

'function' = ADTLKP

Explanation: An uncorrectable I/O
error occurred while reading a CMS
nucleus.

Code Meaning
1
The matching ADT block was
not found.

System Action: The system enters a
wait state.

'function' = FSTLKP

User Response: Call your installation
support personnel.

Code Meaning
1
The matching FST block was
not found.
'function' = RENAME

Code Meaning
24 The mode is invalid, or the
fileid is incomplete.
28 The file was not found, a new
file already exists, file ids are
identical, or the file is inactive.
36 The disk is not read/write.

448

VM/SP System Messages and Codes

903T

Impossible PHASE code xx
Explanation: A phase code larger than
the maximum was detected during the
file copying operation. This error
should never occur.
System Action: RC = 256.

(

DMS
Execution of the command is
terminated. The system status remains
the same, with the following exceptions:
•

905S

Explanation: CMS tried to write on a
virtual disk that resides on a disk whose
"write-inhibit" switch was set.

If the NEWFILE (the default),

REPLACE, or OVLY option was
specified, and the copying process
began before the error was
discovered, then COPYFILE
CMSUTl, on the output disk,
contains the records copied so far.
•

System Action: DMSDIO returns to
caller with a code 6, "FILE IS
READ-ONLY."
User Response: Notify the system
operator to reset the switch; then IPL
CMS again.

In multiple output file mode, several
output files may already have been
created before the error was
discovered.
907T

User Response: Contact your system
support personnel for assistance.

904T

Unexpected UNPACK error at
ustor1, base ustor2
Explanation: An error condition was
detected during the process of
unpacking a file. Probably, the file was
not in PACK format, or it was modified
after it was packed.
System Action: RC = 256.
Execution of the command is
terminated. The system status remains
the same, with the following exceptions
for DMSCPY:
•

I/O error on file

in it im

Explanation: The system tried to close
a file that had not been opened or could
not find a file that should exist.
For DMSHLP, an error occurred while
attempting to read from the requested
HELP text file.
For DMSUTL, an attempt to obtain
information about a member of the
library resulted in a return code that
indicated a permanent I/O error had
occurred.
System Action: RC = 256.
Execution of the command is
terminated. For DMSLBM, the
MACLIB condition is unpredictable.

If the NEWFILE (the default),

REPLACE, or OVL Y option was
specified, and the copying process
began before the error was
discovered, then COPYFILE
CMSUTl, on the output disk,
contains the records copied so far.
•

WRITE-INHIBIT switch set on
drive; notify operator

In multiple output file mode, several
output files may have been created
before the error was discovered.

User Response: Contact your
installation support personnel for
assistance.

User Response: For DMSLBM, issue
MAC LIB MAP to check the validity of
the library name.
For DMSLIO, if the error is in a
TXTLIB, check the integrity of the
dictionary.
For DMSUTL, if the error is in a
LOADLIB. check the integrity of the
directory.
Reissue the command and if the problem
persists, contact your installation
support personnel.

Conversational Monitor System (CMS) Messages

449

DMS
908E

File system error detected at
virtual address udeu; reason code
nn

Explanation: See the explanation of
message 908T.
System Action: RC = 100.
Execution of the command is
terminated. Some I/O may have
occurred on the disk. The status of the
disk is unpredictable.

A de allocation was attempted on a
hon-allocated disk block. The
error was detected in DMSTRK.
5

The cylinder number received by
the Control Program is not in the
user's range or an attempt was
made to access file record zero.
Error detected in module
DMSDIO.

An attempt was made to write on a
read-only disk. Error detected in
module DMSDIO.

A channel programming error
occurred. Allocation or
deallocation was attempted on a
block outside the range of the
DISK structure. The error was
detected in module DMSTRK. A
RDTRK/WRTRK operation was
attempted with a byte count of
zero. The error was detected in
module DMSDIO.

An I/O error occurred while
writing the volume label to commit
an ACCESS ERASE operation.
The error was detected in
DMSTRK.

An I/O error occurred during a
RDTRK/WRTRK operation to an
FB-512 device. The error was
detected by DMSDIO.

A plist error was encountered
during a truncate operation. The
error was detected by DMSERS.

A storage error occurred during a
truncate operation. The error was
detected by DMSERS.

User Response: If data on the pack is
still good, reissue the command. If the
problem persists, contact your system
support personnel.

908T

File system error detected at
virtual address udeu; reason code
nn
Explanation: An error has been
detected indicating that the CMS file
system may have become disoriented
with respect to the disk having virtual
address 'vdev'. 'nn' indicates the nature
of the error; it may be one of the
following:

Code Meaning
3

An error was detected in trying to
read from or write on a disk.
Probably the disk was detached
(via the DETACH command)
without having been released (via
the RELEASE command), or the
disk is an unsupported device.
Error detected in module
DMSDIO.
A deallocation was attempted on a
nonallocated DISK block, or a
MARK operation was attempted on
a block already allocated. The
error was detected in DMSTRK.
A RDTRK/WRTRK operation was
attempted to a DISK block number
zero. The error was detected in
module DMSDIO.

450

VM/SP System Messages and Codes

The cylinder number as calculated
in CMS is not within range of
user's disk, or an attempt was
made to write on system disk
(MODE = S). Error detected in
module DMSDIO.

DMS
lC

The file or ADT for a truncate
operation was not found. The
error was detected by DMSERS.

The file to undergo truncation was
located on a R/O disk. The error
was detected by DMSERS.

A storage error occurred during a
RDTR/WRTRK operation. The
error was detected in module
DMSDIO.

A FINIS error occurred during a
truncate operation. The error was
detected by DMSERS.

the command. If the problem persists,
contact your system support personnel.

909E

Explanation: An uncorrectable I/O
error has occurred on virtual device
address'vdev'. The CSW bytes at the
time of the error are displayed at the
"csw" position and sense data appears
at the "sense" position.
System Action: RC = 100.
Execution of the command is
terminated. Some I/O may have
occurred on the disk. The status of the
disk is unpredictable.

Inconsistent V-Format pointers
were detected during a truncate
operation. The error was detected
in module DMSERS.
No free block is available for
allocation. Error detected in
module DMSTRK. You may
recover files from this disk if you
access it as read-only and copy the
desired files to another disk.

A parameter list error occurred.
Error detected in module
DMSTRK.

The cylinder number received by
the Control Program is not in the
user's range, or an attempt was
made to access file record zero.
Error detected in module
DMSTRK.

Permanent I/O error on vdev;
CSW = csw, SENSE = sense

User Response: If data on the pack is
still good, reissue the command. If the
problem persists, contact your system
support personnel.

909T

Permanent I/O error on vdev;
CSW = csw, SENSE = sense
Explanation: An uncorrectable I/O
error has occurred on virtual device
address 'vdev'. The CSW bytes at the
time of the error are displayed at the
"csw" position and sense data appears
at the "sense" position.
If the FORMAT command was used, one
reason this error may have occured is
because a disk has been DETACHed
without being RELEASEd first. Then, a
FORMAT command was issued for a
. disk with the same virtual address as
the DETACHed disk.

No free block is available for
allocation. Error detected in
module DMSTQQ.

A parameter list error occurred.
Error detected in module
DMSTQQ.

System Action: The system enters a
disabled wait state. The user file
directory is not updated.

User Response: IPL CMS again.
Reissue the command. If the problem
persists, contact your system support
personnel.

User Response: IPL CMS again. If
data on the pack is still good, reissue

Conversational Monitor System (CMS) Messages

451

DMS
910T

An error occurred while the
external interrupt handler was
trying to sever IUCV path pathid;
re-IPL CMS

9121

Explanation: xxx x was in the list of
entry names built by ADDENTRY to be
notified when CMSSERV
communications ended; however, entry
xxxx was not found and therefore xxxx
was not notified.

Explanation: A CMS internal error
occurred in the External Interrupt
Handler. IUCV returned an error
whenever the CMS External Interrupt
Handler was trying to SEVER a path.

System Action: Processing continues,
but xxxx was not notified that
CMSSERV communications ended.

System Action: The CMS system halts
by loading a disabled wait state PSW.

User Response: Check the name to be
sure that it is an entry name that you
want notified and that it is spelled
correctly. To stop this message from
being issued when CMSSERV ends,
delete the entry name from the list
using DELENTRY. If you want to add
another entry point name to list, use
ADDENTRY. You can delete the entire
notification list by IPLing CMS unless
it is rebuilt by an EXEC or module
invoked during the IPL process.

User Response: If you wish to
continue, use the CP command STORE
PSW to turn off the wait state bit,
leaving the address field unmodified;
then, type BEGIN. Otherwise, IPL CMS
agaIn.

911E

An IUCV sever error occurred on
path pathid, iprcode = XX; severing
of other paths continues
Explanation: While CMS was trying
the sever all of the IUCV paths for the
program that issued the HNDIUCV CLR
or CMSIUCV SEVER with
CODE = ALL, a SEVER error occurred.
This SEVER error indicates that
although eMS recognized this path as
being owned by the program, lUCY does
not recognize this path as being a valid
path for this virtual machine.

913E

System Action: RC = 20.
Execution of the command is
terminated.
User Response: Fix the virtual screen
name and reissue the command.

915E

User Response: Determine where the
IUCV SEVER was issued directly and
change it to a CMSIUCV SEVER.

452

VM/SP System Messages and Codes

Invalid virtual screen name:
vname
Explanation: The DEFINE VSCREEN
command was issued and an invlaid
virtual screen name was specified.

The probable cause for this error is that
a program issued a CMSIUCV
CONNECT or ACCEPT to establish the
path and then issued an lUCY SEVER
directly instead of using the CMSIUCV
SEVER support.
System Action: RC = 1000 + lUCY
IPRCODE.
eMS continues to SEVER any other
paths that the issuing program owns
and returns to the program after all
paths have been severed.

ADD ENTRY name xxxx not found
for notification.

Maximum number of windows
already defined
Explanation: The DEFINE WINDOW
command was issued to create a window
but the maximum number of windows
was already defined. rrhe maximum
number of windows that can be defined
is 255.
System Action: RC = 13.

DMS
Execution of the command is
terminated. The window is not defined.

window showing the active virtual
screen.

User Response: Use QUERY
WINDOW * to display a list of all the
defined windows. Use DELETE
WINDOW to delete any windows not
needed and then re-issue the DEFINE
WINDOW command.

916E

•

System Action: RC = 4.
If the WAITREAD VSCREEN command
generated the message, the command is
terminated. For a System Product
Editor session, the terminal is set to
typewriter mode, and the editing session
continues.

Window wname is not
displayed Ihidden
Explanation: QUERY SHOW wname
was issued when the specified window
was not displayed via the SHOW
WINDOW command. Or, the QUERY
HIDE wname was issued when the
specified window was not hidden via the
HIDE WINDOW command.

User Response: Use the SHOW
WINDOW command so that windows
can be displayed the next time the
screen is refreshed.
For the W AITREAD VSCREEN
command, use the SHOW WINDOW
command to show a window on the
virtual screen specified in the
WAITREAD VSCREEN command.
Reissue the command.

System Action: RC = 28.
User Response: None.

917E

For the System Product Editor, issue
the SHOW WINDOW command for
whatever window XEDIT is using, and
then issue the subcommand SET
TERMINAL DISPLAY to return the
editor to display mode. If the problem
persists, contact your support personnel.

No windows are
{displayedlhiddenlshowing virtual
screen: vname}
Explanation: The message was
generated for one of the following
reasons:
•

•

A command was issued which
attempted to refresh the physical
screen, but no windows were
currently being displayed.
The QUERY SHOW * command was
issued and no windows have been
displayed via the SHOW WINDOW
command, or the QUERY HIDE *
command was issued and no
windows have been hidden via the
HIDE WINDOW command.

There is no window showing the
System Product Editor virtual
screen.

918E

No {windowslvirtual screens} are
defined
Explanation: A 'QUERY WINDOW'
command was issued and no windows
were defined. A 'QUERY VSCREEN'
command was issued and no virtual
screens were defined.
System Action: RC = 4.
User Response: None.

•

The WAITREAD VSCREEN
command was issued but there is no

Conversational Monitor System (CMS) Messages

453

DMS
919E

The eMS {window Ivirtual screen}
cannot be deleted

922E

Explanation: An attempt to delete the
CMS window or the CMS virtual screen
was made with the fullscreen CMS
setting ON or SUSPENDed.

Window does not fit entirely on
the screen
Explanation: The window is not
defined within the physical screen or an
attempt is being made to position/size
the window such that the window will
no longer fit within the physical screen.
The window would either be larger than
the physical screen or at a location such
that it does not fit entirely on the
physical screen.

System Action: RC = 24.
The command is not executed.
User Response: SET FULLSCREEN
OFF and re-issue the Delete command.

System Action: RC = 32.
The command is not executed.
920E

{Window IVirtual screen} name
already exists

User Response: Correct the operands
which caused the window not to fit and
re-issue the command.

Explanation: An attempt was made to
define a virtual screen or window when
one already exists with the same name.
923E

System Action: RC = 3.
The command is not executed.

Explanation: An attempt was made to
write to a position outside the area of
the virtual screen or to connect a
window to a virtual screen outside the
scroll able data area of the virtual
screen.

User Response: Delete the existing
window or vscreen, or rename the
window or virtual screen being defined.

921E

Specified location is outside the
virtual screen

{WindowlVirtual screen} name is
not defined

System Action: RC = 32.
The command is not executed.

Explanation: An attempt was made to
use a window or virtual screen with the
specified name but the window or
virtual screen does not exist.

User Response: Correct the line and
column coordinates so that they fall
within the boundaries of the virtual
screen.

System Action: RC = 28.
User Response: Use the DEFINE
WINDOW or DEFINE VSCREEN
command to create a virtual screen or
window with the specified name and
then re-issue the command.

, 924E

Data was truncated
Explanation: Data written to a virtual
screen was truncated to fit into a field
or to fit in the virtual screen area.
System Action: RC = 3.
The data is truncated, execution
continues.
User Response: None.

454

VM/SP System Messages and Codes

DMS
925E

I/O error on screen

System Action: RC = 24.

Explanation: An attempt to refresh the
physical screen terminated abnormally.

User Response: Define the virtual
screen with at least the minimum
number of lines and columns.

System Action: RC = 100.
The screen refresh operation is aborted.
User Response: Check the terminal,
and re-issue the command. If the
problem persists, check with your
programming center to report system
problems.

Or, logon or reconnect at a terminal
that has a larger screen.

928E

Command is not valid for virtuai
screen uname
Explanation: This message was issued
for one of the following reasons:

926E

Command is only valid {on a
display terminal Iin CMS
FULLSCREEN mode}

•

An attempt was made to queue
output (via the GET VSCREEN,
PUT VSCREEN, ROUTE, SET
LOGFILE, WAITREAD VSCREEN
or the WRITE VSCREEN
commands) to a virtual screen which
does not support such output (ie. a
virtual screen used by XEDIT).

•

An attempt was made to use the
CMS virtual screen to display
XEDIT.

•

A CLEAR VSCREEN, SET
VSCREEN, WAITT VSCREEN or
CURSOR command was issued for a
virtual screen that does not support
such commands (ie. a virtual screen
used by XEDIT).

Explanation: A full-screen command
has been issued from a terminal which
is not recognized as a display terminal.
Or, a command was issued which
requires the CMS full-screen setting to
be ON or SUSPENDed.
System Action: RC = 88.
The command is not executed.
User Response: Re-issue the command
from a valid display terminal
(3277/3278/3279/3290 type terminal). Or,
issue SET FULLSCREEN ON or
SUSPEND and re-issue the command.

927E

System Action: RC = 12.
The command is not executed.

{The virtual screen must contain
at least {I linel5 lines and 20
columns}IThe physical screen
must contain at least 20 lines and
80 columns}
Explanation: This message was issued
for one of the following reasons:
•

•

An attempt was made to define a
virtual screen with no data lines or
to use a virtual screen in XEDIT
which has too few lines or columns.
SET FULLSCREEN ON or
RESUME was issued and the
physical screen is not large enough.

User Response: Use another virtual
screen.

929E

Window wname is not connected
to a virtual screen
Explanation: A command was issued
to display a window or to update the
information displayed in a window (e.g.
SCROLL FORWARD) and the specified
window was not connected to a virtual
screen.
System Action: RC = 36.

Conversational Monitor System (eMS) Messages

455

DMS
did not include the password so CMS
prompts the user for it.

Execution of the command is
terminated. The system status remains
the same.

System Action: A password entered on
that line will not be seen. CMS will
wait until a response to the prompt is
entered and then will issue the proper
command to CPo

User Response: Use the SHOW
WINDOW or HIDE WINDOW command
to make a connection between the
window and a virtual screen.

930E

Explanation: A border command which
depends on the location of the cursor
was issued and the cursor was in an
invalid location.

93lE

User Response: Enter the proper
password in the field following the
prompt.

Cursor is not in a valid location

933W

System Action: Execution of the
border command is terminated.

Explanation: An I/O error occurred
trying to log data on disk.

User Response: Re-position the cursor
and re-issue the border command.

System Action: The log setting for the
virtual screen is set off. Execution
continues without logging.

Invalid {borderIWM} command:
{characterl command}

User Response: Check that the disk
specified is accessed in Read/Write mode
and is not full, and set logging on.

Explanation: A character was entered
in a border and was not recognized as a
valid border command. Or, an invalid
command was issued from a WM
window or with the #WM command.

934E

User Response: See the VM/SP CMS
Command Reference for a list of valid
border commands. If the command was
issued from a WM window or with the
#WM command, refer to POP WINDOW
or SET FULLSCREEN for a list of valid
commands.

{Enter the {readlwritelmultiple}
access passwordlEnter
password:IEnter password (It will
not appear when typed):}
Explanation: A CP LINK or
AUTOLOG command was issued with
full-screen setting ON. The command

456

VM/SP System Messages and Codes

Text was not written to virtual
screen. No field was defined.
Explanation: The text to write in a
virtual screen is not within the range of
a field in the scrollable area of a virtual
screen.

System Action: System execution
continues.

932R

Logging stopped for virtual
screen name

System Action: Text is not written in
the virtual screen.
User Response: Write a field in the
virtual screen, then write the text in
that field.

9351

FULLSCREEN CMS suspended
Explanation: There is not enough free
storage available for fullscreen CMS to
continue processing.
System Action: Fullscreen CMS is
suspended.

DMS
User Response: Free some virtual
storage and SET FULLSCREEN ON.
Or, increase the size of your virtual
machine and re-IPL CMS.

936W

•

Explanation: You have specified a
blank unique id (' ') on the :CMD for
this statement. Because this unique
id is used to indicate that only
translation table entries are to be
built, no other syntax definition
statements are allowed to be used.

Virtual screen vname is empty
Explanation: The virtual screen
specified is empty. There is no
information available to PUT in a file.
System Action: No action is
performed.

•

XEDIT is not active. Specify a
file name.
Explanation: You did not specify a file
name when you invoked Convert
Commands and there was no active
XEDIT session from which to get one.
System Action: RC = 40.
Conversion stops.

•

Line line: message
Explanation: The multiple variations
of 'message' are explained below.
System Action: In each case, the
system action is:

•
Conversion stops with a RC = 8.
User Response: In each case, the user
response is:
Correct the situation and issue the
command again.

MESSAGES:

function is not a system function.
Explanation: The function
specified, function, is not the name
of a system validation function and
the SYSTEM option was either
defaulted or specified on the
Convert Commands invocation.
Depending on what you are trying
to do, you should either correct the
name of the function, or else specify
the USER or ALL option when you
invoke Convert Commands.

User Response: Either specify a file
name to be converted or XEDIT a DLCS
file and issue the command again.

947E

routine is not a valid routine
name.
Explanation: The :RTN statement
is reserved for IBM use, and you
have specified a :RTN statement
with a name that is not on the list of
valid system command parsing
routines. If you have inadvertently
changed the name of a routine used
by a system command, change it
back. If you are trying to define a
routine of your own, you redefine
the syntax of your command so it
can be described with the :OPR and
:OPT statements.

User Response: Input something in the
virtual screen and reissue the command.

946E

Only :SYN statements may be
used with a blank unique ide

function is not an active user
function.
Explanation: You specified
validation of user functions (the
USER option) and you have
specified a user function in your
DLCS but you have not
NUCXLOADed the function to make
it usable by the parser. Either load
the user function to make it
available to Convert Commands, or

Conversational Monitor System (eMS) Messages

457

DMS

•

specify the ALL option to suppress
the check.

parser would not be able to find the
second syntax definition.

value is not a valid value for the
function function.

To determine if two names are
unique, you must compare the two
names using the longer of the two
minimum abbreviations (unless it is
longer than the shorter of two
names). For example, using KWL(
< HELP 1 > < HERO 2» you
would compare the first two
characters (HE) of each keyword
and find they were not unique. If
the name HERO had a minimum
abbreviation of 3, however, the
names would be unique because
HEL is not the same as HER. The
two keywords < HELP 1 > and
< HELPME 5> are unique because
the abbreviations of HELP (H, HE,
HEL, and HELP) are all different
from the abbreviation of HELPME
(HELPM and HELPME).

Explanation: A value specified in a
function list on an :OPR or :OPT
statement has been indicated to be
invalid by its function. If the value
is being specified for a system
function, you should make it valid.
If it is for a user function, you can
either correct it or, if you think
your function is incorrect, specify
the ALL option until a corrected
function is available.
•

TEXT may not be mixed with
other functions
Explanation: Because of the way
the TEXT function causes tokens to
be parsed, you cannot use it with
any other functions.

•

All keywords used in all :OPT
statements in a syntax definition for
a command or modifier level must be
unique, and all keywords in a single
:OPR statement must be unique. If
an :OPR statement is optional, the
keywords on succeeding :OPR
statements may not be duplicates
until after a required :OPR
statement is specified.

TEXT function may not have
values
Explanation: Because of the
definition of the TEXT function, you
cannot use a function list with it. If
your values do not have blanks, you
may be able to use a value with the
STRING function.
•

•

The unique id uniqueid has
already been used on line line.
Explanation: You have re-used a
unique id. This is not allowed,
because the parser would not be
able to find the second syntax
definition.

•

The keyword keyword conflicts
with one used on line line.
Explanation: The keyword name
(or translation of the name) has
already been used or has the same
abbreviation as a previous keyword.
This is not allowed, because the

458

VMjSP System Messages and Codes

The modifier modifier conflicts
with one used on line line.
Explanation: The modifier name
(or translation of the name) has
already been used or else it has the
same abbreviation as a previous
modifier. This is not allowed,
because the parser would not be
able to find the second subcommand
definition.
All of the modifiers on a single level
for one modifier level must be
unique. Modifiers may be reused on
different levels or on the same level
if they are in different modifier
levels. In the following example, the

DMS
modifiers 1M 0 K are correct, bu t the
modifiers IMBAD are not:

specified for this command is the
same as the name of a command
previously defined in the DLCS file.
This is not allowed because the
conflict may cause unexpected or
unpredictable results during
command resolution.

:CMD UID CMDNAME:;
:KW.l IMOK 4
:KW.2 IMBAD 4
:KW.2 IMOK 4
:KW.2 IMBAD 4
:KW.l XXXX 4
:KW.2 IMOK 5

•

The translation translation
conflicts with {onela synonym}
used on line line.

Explanation: You have defined an
arbitrary modifier (a :KW.n
statement with no keyword name)
without first defining a modifier
keyword at the same level. You
should reorder the keyword modifier
definitions (and their syntax
definitions) at this level so that at
least one keyword definition
precedes the arbitrary modifier
definition.

Explanation: The translation
specified for this command is the
same or has the same abbreviation
as a translation or synonym
previously used for another. This is
not allowed, because command
resolution would not be able to find
the second definition.
•

The synonym synonym conflicts
with {onela translation} used on
line line.

•

Explanation: The synonym
specified for this command is the
same or has the same abbreviation
as a translation or synonym
previously used for another. This is
not allowed, because command
resolution would not be able to find
the second definition.
•

•

The {translationlsynonym} name
conflicts with a command on line
line.
Explanation: The translation or
synonym (or the abbreviation)

A synta~ may not be defined
after an arbitrary modifier
statement.
Explanation: The previous
statement defined an arbitrary
modifier (a :KW.n statement with no
keyword name). Because there is no
real keyword associated with
arbitrary modifiers, you may not
define a syntax (:OPR. and :OPT.
statements) or a new level (:KW.n
where n is larger than the n used for
the arbitrary modifier) following
them. The only valid DLCS
statements following an arbitrary
modifier are more modifier keywords
or the start of a new command
definition.

The command command conflicts
with a {translationlsynonym} on
line line.
Explanation: The name of this
command is the same as the
translation or synonym of a
previous command. This is not
allowed because the conflict may
cause unexpected or unpredictable
results during command resolution.

An arbitrary modifier may not be
the first or only :KW.n at its
level.

948E

Line line: message
Explanation: The multiple variations
of message are explained below.
System Action: In each case, the
system action is:
Conversion stops with RC = 8.

Conversational Monitor System (CMS) Messages

459

DMS
User Response: In each case, the user
response is:

for the next statement is flagged
as unexpected. You will
probably want to insert the
missing :; on a previous line.

Correct the situation, and issue the
command again.

If the nl-name is omitted from a
keyword definition (for example
< name 2 3 > instead of < name
2 name 3 », the error flagged is
"Minimum abbreviation
expected, not: >" because the
number you wanted as an
abbreviation can be a keyword
name.

MESSAGES:
•

value is out of order or not a
DLCS statement name.
Explanation: Convert Commands is
looking for the beginning of a new
DLCS statement. The name that was
found is either not a DLCS
statement name (eg. aPR or :OPX)
or it is out of order (eg. a :OPR
statement following a. :OPT
statement). A :KW.n statement is
out of order if it follows an :OPR or
:OPT statement and is either the
first :KW.n statement in the
command or has a level that is
greater than the previous :KW.n
statement.

•

If you do not know exactly where
the error is occurring in a line,
XEDIT the DLCS file, and issue
Convert Commands with no file
identifier. The cursor is placed
under the specific. token in error.

data expected, not: value
Explanation: A syntax error has
been detected in a DLCS statement.
The message displays the value of
the token that is in error and a data
list of one or more items that are
valid. Valid items can be listed as
descriptive names, keyword values
or specific delimiter characters. If
the error involves an incomplete
DLCS statement at the end of the
DLCS file, the words "end of input
file" are used in place of value.
Convert Commands checks DLCS
statements for syntax errors in such
a way that the token shown to be in
error can follow the actual cause of
the error. You may have to correct
the error elsewhere.
Some examples are:
If the :; is omitted from the end
of a DLCS statement, the :cmd

460

Also, if you use a DLCS delimiter
character in a name· and do not
enclose it in quotes, Convert
Commands sees more tokens than
you wanted. Messages where value
is only part of the token you expect
to see can result. For example, the
name NOT> GOOD is seen as three
tokens (NOT, >, and GOOD), and
the name ALSO:BAD is seen as two
(ALSO and :BAD).

VM/SP System Messages and Codes

949E

Line line: message
Explanation: The multiple variations
of 'message' are explained below.
System Action: In each case, the
system action is:
Conversion stops with RC = 8.
User Response: In each case, the user
response is:
Correct this situation and issue the
command again.

MESSAGES:

(

DMS
•

Explanation: The modifier level
(the n in :KW.n) must be specified
with a minimum value of one and a
maximum value equal to the
previous modifier level plus one.
The first modifier statement after
the :CMD statement must be :KW.l.

The application id must be 3
characters long.
Explanation: The application
identifier you specified did not meet
the requirement that it must be
three characters long.

•

The application id applid does not
start with a capital letter.

•

Explanation: The minimum
abbreviation for a name must be
specified as an unsigned positive
integer.

Explanation: The application
identifier you specified did not meet
the requirement that the first
character must be a capital letter
(A-Z).
•
•

The application id applid does not
contain only letters and
numbers.

(0-9).

The System/User indicator
indicator does not start with S or

U.
Explanation: This token must start
with an S if Convert Commands is to
build a system syntax table, or a U
if you are building a user syntax
table.
•

•

The unique id uniqueid is longer
than 16 characters.

The modifier level must be a
positive number, not value
Explanation: The modifier level
(the n in :KW.n) must be specified as
an unsigned positive integer.

•

A closing quote was not found
for a string
Explanation: An opening quote for
a name was found but a matching
ending quote was not found before
the end of the input line. Make sure
your DLCS data does not extend
past column 72; quoted strings
cannot be continued from one line
to the next. If you are trying to
define a name with a keyword in it,
you must enclose it in quotes and
double the quote in the name. For
example, you define the name
CAN'T as 'CAN"T'.

Explanation: Unique ids cannot be
longer than 16 characters.
•

The minimum length must be
less than value, not value
Explanation: The minimum
abbreviation for a name must be
specified with a minimum value of
one and a maximum value equal to
the number of logical characters in
the name. Unless you are using a
DBCS language, this value is the
same as the number of letters in the
name. If the name does contain
DBCS characters, count each of
them as one logical character, and
do not count shift-in or shift-out
control characters.

Explanation: The application
identifier you specified did not meet
the requirement that the first
character must be a capital letter
(A-Z), and the last two characters
can be capital letters or numbers

•

The minimum length must be a
positive number, not value

•

There are no characters in a
quoted string.

The modifier level cannot be
more than number • You used
value
Conversational Monitor System (CMS) Messages

461

DMS
Explanation: A string consisting of
two consecutive quotes was found.
This is not allowed because it is
trying to define a name with a
length of zero. Because two quotes
are used to define a single quote
within a quoted string, this error
may be caused by omitting a
starting quote or having an extra
quote that prematurely ends a
quoted string. If you are trying to
define a blank unique id, you must
code a blank between the two
quotes. If you are trying to define a
name consisting of two quotes, you
must code six quotes.
•

•

Explanation You specified a
character between shift-out and
shift-in control characters that is
not a valid double-byte character.
The range of hex codes that may be
used to represent characters in the
Double-Byte Character Set is:
first byte:
second byte:

Explanation: Processing completed
with no errors. This is an informational
message.

Explanation: You have used a
blank or a parenthesis in a name.
This is not allowed because the
parser will recognize these
characters and use them to define
other tokens. They will never be
passed back as a name.

•

Unmatched shift-out (SO) and
shift-in (SI)
Explanation You have specified a
shift-out control character without a
shift-in or shift-in control character
with no preceding shift-out. These
control characters must be paired
correctly between columns 1 and 72
of the DLCS file to be considered
valid.

•

Odd number of characters
between SO and SI

System Action: None.
User Response: None.

Invalid SVC suc; GAM/SP not
installed

951E

Explanation: The SVC was issued as
the result of a program executing an I/O
macro for a graphics device, that is, a
device defined in a DCB with
DSORG=GS. The SVC requires the use
of the shared segment (CSMGAM)
containing GAM/SP, but this segment
could not be found.
System Action: Execution of the SVC
is terminated, and control is returned to
the program.
User Response:
1.

Explanation You have specified an
odd number of character positions
between shift-out and shift-in
control characters. To be valid, you
can have only double-byte
characters between them.

462

VMjSP System Messages and Codes

X'41' - X'FE'
X'41' - X'FE'
X'4040' (DBCS blank)
X'OOOO' (DBCS null)

{Conversion of fn ft fm [from
XEDIT] completelNo errors found
in fn ft fm [from XEDIT]}

9501

The character character may not
be used in a name.

This error is also caused by
consecutive shift-out and shift-in
control characters.

Invalid double-byte character(s)

If the attempted use of GAM/SP was

intentional, ask a system
programmer to ensure that GAM/SP
is installed correctly.
2.

If the program should not be

attempting to use GAM/SP, that is.
if it did not open a DCB with

DMS
DSORG = GS, check whether the
DCB has been unintentionally
overwritten.

952E

954E

Explanation: The SVC was issued as
the result of a program executing an I/O
macro for a graphics device, that is, a
device defined in a DCB with
DSORG = GS. The SVC requires the use
of a shared segment (CMSGAM)
containing GAM/SP. This segment
should contain a constant that identifies
it as being the GAM/SP shared segment,
but the constant could not be found.

Virtual storage size too large for
CMSGAM shared segment to load
at ustor
Explanation: An attempt was made to
load the shared segment (CMSGAM)
that contains GAM/SP for use by an
application program. The address at
which the shared segment must be
loaded is lower than the virtual
machine's highest address. A shared
segment can be loaded only at an
address above the highest address in
any virtual machine that uses it.

System Action: Execution of the SVC
is terminated, and control is returned to
the program.
User Response: Ask a system
programmer to check whether GAM/SP
is installed correctly, and if so, whether
the CMSGAM shared segment has been
loaded but then overwritten.

System Action: The shared segment is
not loaded, and control is returned to
the program.
User Response: Either ask the system
programmer to redefine the address at
which the shared segment is loaded, or
define a smaller virtual machine using a
CP DEFINE STORAGE command.

953E

955E

Explanation: The SVC was issued as
the result of a program executing an I/O
macro for a graphics device, that is, a
device defined in a DCB with
DSORG = GS. The SVC requires the use
of a shared segment (CMSGAM)
containing GAM/SP. This segment
includes a list of addresses of GAM/SP
modules, and one of these was found to
be zero.

User Response: Ask a system
programmer to ensure that GAM/SP is
installed correctly.

CMSGAM shared segment paging
I/O errors with eode
Explanation: An application program
was using the shared segment
(CMSGAM) containing GAM/SP when a
paging error occurred in the shared
segment. ccccccc identifies the type of
DIAGNOSE instruction that was being
executed by GAM/SP when the error
occurred: it is either FINDSYS or
LOADSYS.

CMSGAM shared segment error:
module address for SVC sue is zero

System Action: Execution of the SVC
is terminated, and control is returned to
the program.

CMSGAM shared segment error:
identifier invalid for SVC sue

System Action: Control is returned to
the program.
User Response: Ask a system
programmer to correct the paging
errors.

956E

Insufficient storage for GAM/SP
anchor block
Explanation: An application program
was using the shared segment
(CMSGAM) containing GAM/SP. After
being loaded, GAM/SP issued a
DMSFREE macro to obtain storage in

Conversational Monitor System (eMS) Messages

463

DMS
Processing ends.

the user's virtual machine for a control
block known as the anchor block.
Insufficient storage was available.

User Response: Edit the PROFILE file
for SPGEN to assign the desired value
to the keyword. Run the program
again.

System Action: Control is returned to
the program.
User Response: Define a larger virtual
machine using a CP DEFINE STORAGE
command.

957E

960E

Explanation: An error has been found
at the specified line number in the
PROFILE file for SPGEN. This message
is always preceded by another message
which explains the precise nature of the
problem.

Incompatible option options for
options
Explanation: System build options
were indicated in a PROFILE file for
SPGEN which are not compatible with
each other.

System Action: RC = 12.
Processing ends after the error checking
phase is done.

System Action: Parsing of the input
PROFILE for SPGEN continues to
complete the error checking phase;
processing then ends. RC = 12.
User Response: Adjust the PROFILE
options for SPGEN so that they are
compatible. Run the program again.

9581

User Response: Correct the error that
has been detected. Run the program
again.

961E

No keyword initialized in fn ft fm

System Action: RC = 36.
Processing ends.

System Action: RC = 12.
Processing ends.

User Response: Change the class of
the files in the device, move them, or
purge them. Run the program again.

User Response: Add the expected
keyword and its value to the PROFILE
for SPGEN and run the program again.
962E

Missing value for keyword
keyword.
Explanation: A keyword is present in
a PROFILE file for SPGEN, but has no
value assigned to it.
System Action: RC = 12.

464

VM/SP System Messages and Codes

There are class class files in the
device
Explanation: A virtual device (RDR,
PRT, or PUN) has been checked and
found to have files of the indicated class
when none were expected.

Explanation: An expected keyword is
not initialized in the PROFILE for
SPGEN.

959E

Error in line line of fn ft fm

Invalid character: character
Explanation: An invalid character has
been found in an input file.
System Action: RC = 20.
Processing ends.
User Response: Change the item found
to be in error. Run the program again.

DMS
963E

keyword value not found in fn ft fm

System Action: None.

Explanation: The PROFILE for
SPLOAD, of the given name, does not
contain the specified entry.

User Response: This message is
displayed only to indicate that the
system-dependent files may be modified
at this time; later steps use the modified
files during system build activities.

System Action: RC = 24. Processing
ends.
User Response: It is most likely that
the command was invoked with an
incorrect parameter. If not, check the
input file for accuracy. Correct the
problem and run the program again.

964R

9661

Explanation: You have the option of
converting all of the HELP files to
uppercase to enable printing or display
of the files on devices that do not
handle mixed case text.

Wrong tape mounted; mount
product tape VOLn.
Press ENTER when the correct
tape is mounted or type QUIT
Explanation: SPLOAD has examined
the PROFILE file and found that the
tape file you want to load from the
product tape is located on a tape other
than the one mounted. If the VOL
number is blank, it means that you do
not have a VM/SP product tape
mounted.

System Action: The program waits for
your response. If you reply YES, the
HELP files are converted to upper case.
Otherwise, they are not touched.
User Response: Reply "YES" or "NO"
to the prompt. The default is NO.

967R

System Action: The program waits for
your response.

User Response: Either type "QUIT" to
end processing, or mount the correct
product tape on the tape drive and then
press the ENTER key to continue.

You may wish to tailor the
following files at this time:
DMKSNT ASSEMBLE
DMKRIO ASSEMBLE
DMKSYS ASSEMBLE
DMKBOX ASSEMBLE
DMKFCB ASSEMBLE
DMSNGP ASSEMBLE
VMUSERS DIRECT
Explanation: The indicated files may
be modified to reflect
installation-specific parameters.

Type: (No) or Yes
Explanation: You are being asked to
type a response to a message.

System Action: SPLOAD waits for
your response.

9651

Do you wish to have the HELP
files converted to uppercase?

User Response: Type "NO" or "YES"
and press the ENTER key. The default
is "NO" (listed in parentheses).

9681

The following minidisks defined in
the base CP directory will be
formatted:
AUTOLOG1191
CMSBATCH 195
CMSUSER 191
EREP 191
OPERATNS 191, 193 MAINT 201, 319
MAINT 293, 294, 494, 496, 596
Explanation: The indicated minidisks
will be CMS FORMATted.
System Action: The indicated
minidisks will be CMS FORMATted.

Conversational Monitor System (eMS) Messages

465

DMS
User Response: Enter the minidisk
address as requested and press the
ENTER key.

User Response: None.

9701

Formatting user's udeu minidisk
Explanation: The specified minidisk is
being formatted using the CMS
FORMAT command.

9741

Unable to find IPL decks on the
minidisk you indicated
Explanation: The required files are not
located on the minidisk whose address
you supplied.

System Action: The FORMAT
command is used to format the indicated
minidisk.

System Action: Processing ends.
User Response: None.

971E

User Response: Determine the
minidisk address on which the IPL
decks reside and run the UTILITY
EXEC again.

Unable to locate fn ft
Explanation: The indicated file cannot
be found.
9751
System Action: RC = 24.
Processing ends.

Moving fn ft to tape
Explanation: The indicated file is
being written to tape.

User Response: Make sure the
indicated file has been loaded properly
and the minidisk on which it resides is
ACCESSed correctly. Run the UTILITY
EXEC again.

System Action: The indicated file is
written to tape using the MOVEFILE
command.
User Response: None.

9721

fn ft fm spooled to printer
9761
Explanation: This is an informational
message. The indicated file has been
spooled to the printer.

The fn ft program is on tape file
number number
Explanation: This is an informational
message.

System Action: None.
System Action: None.
User Response: None.
User Response: None.
973R

Enter the minidisk address where
the IPL decks were loaded
Explanation: The correct mini disk
must be accessed in order to proceed
with the processing.
System Action: The program waits for
your response and then continues
processing.

466

VMjSP System Messages and Codes

9771

Enter disk address where the
service programs are to be
written
Explanation: The program is prepared
to write the service programs to a
minidisk address which must be
obtained from you.

DMS
System Action: The program waits for
your response and then continues
processing.

981R

Explanation: The program is
requesting the real address of the
indicated DASD volume.

User Response: Enter the address of
the minidisk on which the service
programs are to be written, and then
press the ENTER key.

978R

What is the real address of your
volume volume?

System Action: The program issues
message DMS982R.

Type: (190) or cuu

User Response: Respond to message
DMS982R.

Explanation: The program is
requesting a minidisk address from you.
982R
System Action: The program waits for
your response.

Type: real address or SKIP
Explanation: The program is
requesting an address (cuu) from the
user.

User Response: Type a minidisk
address or just press the ENTER key to
accept the default address (190).

System Action: The program waits for
your response.

9791

User Response: Type the address
requested or type SKIP to cause the
program to bypass the processing of the
indicated DASD volume.

IPL vdev has been created
Explanation: This is an informational
message.
System Action: The program has just
completed building the indicated service
program.
User Response: None.

9801

An IPLabie CP nucleus now exists
on tape
Explanation: This is an informational
message.
System Action: None.
User Response: None.

983E

Violation of CMS naming
convention found in args
Explanation: The indicated item does
not conform to the CMS naming
conventions.
System Action: RC = 24.
Processing ends.
User Response: Examine the item and
correct it to insure that it does not
exceed eight characters in length and
contains only characters that may be
used in a CMS fileid. Run the IT ASK
EXEC again.

Conversational Monitor System (eMS) Messages

467

DMS
984E

User Response: If it is desirable,
restore the minidisk ACCESS manually
after completion of the program.

Too many class class files in device
Explanation: A virtual device (RDR,
PUN, PRT) has more files of the
specified class than expected.
995E
System Action: RC = 24.
Processing ends.
User Response: The program is
expecting that only one file of the
specified class exists in the virtual
device. Change the class of the files
that are not to be processed by this
command, move them, or purge them.
When only one file exists for the
indicated class, run the program again.

985E

Explanation: A program executing
under CMSDOS tries to open a DTF.
Not enough free storage was available
to satisfy requests issued by the
DMSBOP routine (OPEN). The DTF is
not opened.
System Action: RC = 104.
The program is cancelled.

Conflicting values for duplicate
keyword keyword
Explanation: A PROFILE file for
SPGEN has the same keyword listed
two or more times with different values
assigned.

Unable to obtain free storage for
DMSBOP processing; redefine
storage size

User Response: Redefine the storage
size of your virtual machine, or return
free storage that is not required.

996E

System Action: RC = 24.
Processing ends.

No logic module pointer in DTF
for dtfname
Explanation: A program executing
under CMSDOS issued an-OPEN for a
DTF called 'dtfname'. Since the DTF is
type SD, the program must pass the
pointer to the logic module. OPEN
checks the DTF for this pointer if the
DTF device is not FB-512, and if the
pointer is zero the DTF is not opened.

User Response: Correct the PROFILE
file so that only one instance of the
keyword appears in the PROFILE (or
that all instances have the same value
assigned to them). Run the program
again.

System Action: RC = 104.
The program is cancelled.
9861

Unable to restore ACCESS to
mdisk
Explanation: An attempt has been
made to restore ACCESS to a minidisk
and has failed. This can occur in the
instance where a minidisk is an
extension of another minidisk which has
been released prior to running the
program. The program cannot restore
ACCESS at the same mode as an
extension because it cannot determine
what minidisk the "parent" may have
been.
System Action: None.

468

VM/SP System Messages and Codes

User Response: Update the program to
initialize the logic module pointer.

999E

No ft module found
Explanation: The processor module
appropriate to the filetype was not
found.
System Action: RC = 28.
Execution of the command is
terminated.

DMS
name you want written on the disk label
record. Reissue the SA VEFD SAVE
command.

User Response: Correct the filetype
and reissue the command.

1074S

Disk not linked as R/W
Disk has not been initialized by
SAVEFD IN IT

1077E
Explanation: The disk that contains
the FSTs you want saved in the DCSS is
not linked read/write.

Explanation: The disk has either not
been used by SAVEFD before, or the
last SA VEFD operation performed on it
was a SA VEFD NOSA VE.

System Action: RC = 36.
Execution of the command is
terminated. The system status remains
the same.

System" Action: RC = 40.
Execution of the command is
terminated. The system status remains
the same.

User Response: Link the disk
read/write.

1075E

Explanation: The label name on the
disk was not the same as the label
specified on the SAVEFD SAVE
command.
System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Verify that you have
specified the correct disk on the
SAVEFD command.

1076E

User Response: Verify that you have
specified the correct disk on the
SAVEFD command. If so, issue the
SAVEFD INIT command first, then
reissue the SA VEFD SAVE command.

Label on disk label and label on
command label do not match

Segment name in disk label
segname and segment name on
command segname do not match
Explanation: The segment name on the
disk label record was not the same as
the segment name specified on the
SAVEFD SAVE command.
System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Issue the SAVEFD
INIT command and specify the segment

1078E

Cannot access saved file directory
for this disk
Explanation: The user issued ACCESS
with the SAVEONL Y option. The
access failed for one of the following
reasons:
•

No saved file directory exists for the
disk.

•

The disk has been changed since the
saved file directory was saved.

•

The DCSS containing the disk is at
an address that overlaps the user's
virtual machine.

•

The disk is already accessed using
the saved file directory.

•

The saved file directory overlaps
another accessed saved file
directory.

•

The disk being accessed is not in
EDF format.

System Action: RC = 44.

Conversational Monitor System (CMS) Messages

469

DMS
Execution of the command is
terminated. The system status remains
the same.

•

The fileid fnl ftl fml is the name
from the card stream of the spool
file.

User Response: Reissue the command
without the SAVEONL Y option, if
standard access is acceptable (the user
has his/her own copy of the file
directory). Otherwise, contact the
system administrator to save or resave
the file directory.

•

The phrase "and replace the existing
file of the same name?" appears
when the operation replaces an
existing file and the filemode of that
file is the same as fml.

•

The phrase "and replace fn2 ft2 fm2"
appears when the operation replaces
an existing file and the filemode of
that file is not fml.

•

The fileid fn3 ft3 fm3 is the name
from the card stream of the spool
file that you may specify when the
name differs from the name of the
incoming file.

Message

lO79R

Explanation: One of the following
messages may be issued:

•

Receive fnl ftl fml?
Reply 0 (NO), 1 (YES), 2 (QUIT),
or 3 (RENAME)

•

Receive fnl ftl fml and replace
the existing file of the same
name?
Reply 0 (NO), 1 (YES), 2 (QUIT),
or 3 (RENAME)

•

System Action: Your response is read
and analyzed.
User Response: The valid responses
include:
•

One of the digits specified in the
prompt.

•

One of the parenthetical words that
follow a digit or any initial
truncation of the word.

Receive fnl ftl fml and replace fn2
ft2 fm2?

Reply 0 (NO), 1 (YES), 2 (QUIT),
or 3 (RENAME)

•

Receive fnl ftl fml as fn3 ft3 fm3?
Reply 0 (NO), 1 (YES), 2 (QUIT),
or 3 (RENAME)

•

Receive fnl ftl fml as fn3 ft3 fm3
and replace the existing file of
the same name?
Reply 0 (NO), 1 (YES), 2 (QUIT),
or 3 (RENAME)

•

Receive fnl ftl fml as fn3 ft3 fm3
and replace fn2 ft2 fm2?
Reply 0 (NO), 1 (YES), 2 (QUIT),
or 3 (RENAME)

You supplied a response to determine
the handling of an incoming file.

The meanings of these responses are:
Response

Description

OorNO

If this file is one of a set
of files that constitutes
a single spool file, the
file is not received and
prompting continues for
the next file, if there is
one. If this is the last
file of a set of files or if
this is the only file in
the spool file, the
command is ended.

lor YES

Receives the file under
the name fnl ftl fml (or
fn3 ft3 fm3).

470

VMjSP System Messages and Codes

DMS
2 or QUIT

The meanings of these responses are:

Ends the command.

Response

Description

OorNO

Explanation: Message DMSI079R has
been issued and you responded with 3
(or RENAME).

Does not receive the file
under the name fn ft fm
and repeats the original
prompt message
DMSI080R which allows
you to specify a
different name for the
incoming file.

lor YES

Receives the file under
the name fn ft fm.

System Action: Your response is read
and analyzed.

2 or QUIT

Ends the command.

3 or RENAME Requests prompt
message DMSI080R, so
the incoming file can be
received using a
different name.

Enter the new name for fnl ftl fml

l080R

User Response: Enter a fileid of the
form:

l082E

fn [ft [fm]]

Note:

Explanation: This message is issued
when the QUERY WINDOW =
command is issued but no window
qalifies as the window on top.

Only fn is required; if ft and fm
are omitted, ft is set to ftl and fm
is set to Ai. Message DMSl08lR
is issued if the specified fileid
names an existing file.

System Action: The command
completes. System status remains the
same.

Replace fn ft fm?
Reply 0 (NO), 1 (YES), or 2 (QUIT)

l081R

Explanation: A message (DMSI080R)
was issued and you responded with a
fileid that names an existing file.
System Action: Processing continues.
The action specified is taken.
User Response: The valid responses
include:

No window qualifies as the
window on top

User Response: None.

1123E

Unknown response text ignored.
Explanation: You responded to prompt
message DMSI079R, DMSI080R, or
DMSI081R with a reply that does not
conform to the requirements for a valid
response.

•

One of the digits specified in the
prompt.

System Action: The original prompt
message DMSI079R, DMSI080R, or
DMSI081R (which repeats the list of
valid responses) is reissued.

•

One of the parenthetical words that
follow a digit or any initial
truncation of the word.

User Response: Respond with one of
the valid replies to the original message
when it is reissued.

Conversational Monitor System (eMS) Messages

471

DMS
User Response: If you do not need the
data in the spool file, purge it using the
CP PURGE READER spoolid command.

Spool file spoolid has been left in
your reader because one or more
files were not received.

1124W

If you wish to extract the data from the

Explanation: One or more files in your
reader were not received because you
either:
•

Responded with a 0 (or NO) or 2 (or
QUIT) to prompt message
DMSI079R or DMSI081R

•

An incoming file would have
replaced an existing file and the
NOREPLACE option was in effect
for the RECEIVE, DISK LOAD, or
READCARD commands.

spool file, reissue the RECEIVE
command with the FULLPROMPT
option. This will allow you to specify
the disposition for each incoming file.
Alternatively, you may specify the
REPLACE option on the RECEIVE
command, to allow the file(s) in the
spool file to replace existing files.

1125E

Command is not allowed as an
immediate command

If another message with a higher return

Explanation: You issued a command in
fullscreen CMS as an immediate
windowing command (prefixed by
#WM). The command is not allowed as
an immediate command.

code is issued with this message the
higher return code will be returned.

System Action: None.

System Action: RC = l.
The spool file processed by the
command is left in your reader.

User Response: Reissue the command
without specifying #WMcommand

472

VM/SP System Messages and Codes

(

DMM

Interactive Problem Control System Extension (IPCS)
Messages
I

100S

ERROR 'nnn' READING FILE 'fn
ft fm'

200S

Explanation: An error occurred during
the execution of an FSREAD macro
against file 'fn'. For a description of
error 'nnn', see the FSREAD macro in
the VM/SP eMS Macros and Functions
Reference.

Explanation: An error occurred during
the execution of an FSWRITE macro
against the file 'filename'. For a
description of error 'nnn', see the
FSWRITE macro in the VM/SP eMS
Macros and Functions Reference.
System Action: Processing stops and
returns to CMS.

System Action: RC = 8.
Processing stops and returns to CMS.

User Response: Check the macro
description to see what type of failure
'nnn' indicates. Correct the error and
retry.

User Response: Check the macro
description to see what type of failure
nnn indicates. Correct the error and
retry.

300S
109S

VIRTUAL STORAGE CAPACITY
EXCEEDED
Explanation: IPCS service routine
(SVC 199 services) could not obtain
needed storage.
System Action: Command execution
stops.
User Response: Define a larger virtual
machine and restart.

ERROR 'nnn' WRITING FILE 'fn
ft fm'

ERROR 'nnn' ON FSSTATE 'fn ft
fm'
Explanation: An error occurred during
the execution of the FSSTATE macro
against file 'fn ft fm.' For a description
of return code 'nnn', see the VM/SP
eMS Macros and Functions Reference.
System Action: RC = 8.
Processing stops and returns to CMS.
User Response: Check the macro
description to see what type of failure
'nnn' indicates. Correct the error and
retry.

Interactive Problem Control System Extension (IPCS) Messages

473

DMM
400S

ERROR 'nnn' CLOSING 'fn ft fm'

Processing stops. The system remains
in the same state as before the command
was issued.

Explanation: An error occurred during
the execution of an FSCLOSE macro
against 'fn ft fm.' For a description of
return code 'nnn', .see the FSCLOSE
macro in the VMj SP CMS lVIacros and
Functions Reference.

User Response: If PROB, PRB, or
IPCSDUMP was being executed, collect
the console log and call your IBM
programming support representative. If
a user program or EXEC was being
executed, correct the parameter being
passed to SUMMARY and retry.

System Action: Processing stops and
returns to CMS.
User Response: Check the macro
description to see what type of failure
'nnn'indicates. Correct the error and
retry.

500S

502S

Explanation: Problem nnnnn was not
found in the symptom summary file.

ERROR 'nnn' WRITING TO
VIRTUAL PRINTER

System Action: RC = 4.
Processing stops. The system remains
in the same state as before the command
was issued.

Explanation: An error occurred during
execution of a PRINTL macro against
the file 'filename'. For a description of
error 'nnn', see the PRINTL macro in
the VMj SP CMS Macros and Functions
Reference.
System Action: A number of lines of
printed output have not been sent to the
printer SPOOL files.

User Response: Retry the command
supplying the correct problem number.

560E

User Response: Check the macro
description to see what type of failure
'nnn' indicates. Correct the errOr and
retry.

50lS

System Action: RC = 8.

FILE 'PRBXXXXX DUMP AI'
ALREADY EXISTS - RENAME
OR ERASE
Explanation: IPCS uses PRBXXXXX
DUMP Al as its creation dumpname for
all dumps, and a file with that name
already exists.

INVALID P ARM 'parameter'
PASSED TO SYMPTOM
SUMMARY UPDATE PROGRAM
Explanation: The program or EXEC
that called SUMMARY passed an
invalid request or a problem number not
in the format PRBnnnnn, where nnnnn
must be numeric. If a user program or
EXEC was being executed, correct the
parameter being passed to SUMMARY
and retry.

PROBLEM'PRBnnnnn'NOT
FOUND IN SYMPTOM
SUMMARY

System Action: Processing stops.
User Response: Rename or erase this
file.

600S

ERROR 'nnn' RENAMING FILE
'fn ft fm'
Explanation: IPCSDUMP uses an
internal dump name of PRBXXXXX
DUMP Al during processing. An error
occurred renaming this file to
PRBnnnnn DUMP AI.
System Action: Processing stops.

474

VM/SP System Messages and Codes

DMM
User Response: Check the RENAME
command description in VM/SP eMS
Command Reference. to see what type of
failure nnn indicates. Correct the error
and retry.

6011

continue the search by pressing the
ENTER key (or its equivalent) without
entering any data. The last member
address shown will be used to restart
the CHAIN subcommand. The running
total of all members found will be
displayed.

OPERAND 'operand' NOT
RECOGNIZED
6111
Explanation: The system received a
search argument that was not
recognized by the STAT command.

Explanation: While searching the
chain specified, the address of the next
member in the chain has already been
found. This is caused by an unexpected
loop in the chain. The last address
displayed is the duplicate address.

System Action: RC = 4.
Processing stops. The system remains
in the same state as before the command
was issued.
User Response: Retry the command
specifying the correct operand(s).

6091

System Action: The CORTABLE
function is terminated. DUMPSCAN
processing continues.
User Response: Correct the input and
retry.

6101

System Action: The CHAIN function
is terminated. DUMPS CAN processing
continues.

REQUESTED ADDRESS NOT IN
REAL STORAGE
Explanation: The address field
contains an address which is higher
than the highest address in the dump.

LOOP DETECTED IN CHAIN COMMAND TERMINATED

User Response: None.

701R

A VALID DUMP HAS NOT BEEN
SPECIFIED. PLEASE ENTER
ONE OF THE FOLLOWING
OPERANDS:
NNNNN < MODE> - TO VIEW PRBNNNNN
FROM CMS DISK
'MODE'
HELP - TO REQUEST HELP
INFORMATION
END, QUIT, HX - TO EXIT

POSSIBLE INVALID CHAIN COMMAND TERMINATED

Explanation: You are required to
specify one of the operands listed above.

Explanation: While searching for the
chain specified by the user, the number
of entries exceeded 144. This may be
caused by an invalid chain.

System Action: The system waits for a
response. Subsequent action is
dependent on the user response.

System Action: The CHAIN function
is terminated. DUMPS CAN processing
continues.
User Response: If the chain is valid
and longer than 144 entries, you can

User Response: Enter the numeric
part of the dump file name, followed by
the disk name. Leading zeroes are not
required, so for PRB00056 on the A disk,
enter 56 a. If the mode is omitted, A is
assumed.

Interactive Problem Control System Extension (IPCS) Messages

475

DMM
7021

System Action: Subcommand
processing stops, DUMPSCAN
processing continues.

NON-HEX CHARACTER IN
COUNT - RETRY
Explanation: The count field in the
input line contains a non-hexadecimal
character.

User Response: Make sure that the
module name or entry point is correct
and retry the subcommand supplying
the correct module name.

System Action: Subcommand
processing stops, DUMPS CAN
processing continues.
7071
User Response: Make sure the count
field contains only hexadecimal
characters and reenter the command.

7031

Explanation: The page table entry for
the virtual address page containing
'module' was marked invalid. It was not
dumped when the dump was taken so it
cannot be displayed.

NON-HEX CHARACTER IN
ADDRESS - RETRY

System Action: Subcommand
processing stops, DUMPSCAN
processing continues.

Explanation: The address field
contains a non-hexadecimal character.

User Response: None.

System Action: Subcommand
processing stops, DUMPSCAN
processing continues.
7081
User Response: Correct the input and
retry.

705W

System Action: Processing continues
if possible.

Explanation: No entry was found in
DMMTAB for a subsystem dependent
routine for use by DUMPSCAN.
'dumptype' is the dump type field
supplied in the VMDUMP command.

User Response: None.

7061

'entry' NOT FOUND IN THE
LOAD MAP
Explanation: The name displayed was
entered to request a load map search
and display function. However, the
name was not found in the load map.

476

VM/SP System Messages and Codes

PAGE 'page' NOT FOUND IN
DUMP
Explanation: This virtual address was
not represented by an entry in the bit
map. This means it was not dumped at
the time the dump was taken.

'dumptype' DUMPSCAN
FUNCTIONS NOT A V AILABLE

System Action: Processing continues
with only 'common' functions available.

'module' 'page' NOT VALID

User Response: None.

7091

NO VALID SCROLL ADDRESS
Explanation: A SCROLL or SCROLL
U request must follow some other
request that generates a display address.
This has not happened yet in this
DUMPSCAN session. SCROLL will
scroll from the last address that was
displayed.
System Action: Subcommand
processing stops, DUMPSCAN
processing continues.

DMM
User Response: Enter an address in
the area you wish to examine by using
'DISPLAY hexloc'.

7101

7131

Explanation: The VMBLOK control
block for the specified 'userid' was not
found so the request could not be
honored.

NON-NUMERIC COUNT
CHARACTER - RETRY

System Action: Subcommand
processing terminates, DUMPSCAN
processing continues.

Explanation: The count field contains
a non-numeric character.
System Action: Subcommand
processing stops, DUMPSCAN
processing continues.
User Response: Correct the input and
retry.

7111

User Response: None.

7141

NON-HEX CHARACTER IN
INPUT - RETRY
Explanation: DTVHEX detected a
non-hexadecimal character.

LOOP IN VMBLOK CHAIN
Explanation: While searching through
the VMBLOK chains for entries, no end
was found to the chain.

System Action: Subcommand
processing stops, DUMPSCAN
processing continues.

Note: This message will occur if more
than 1024 users were logged on the
system at the time of dump.

User Response: Correct the input and
retry.

System Action: Subcommand
processing stops, DUMPSCAN
processing continues.

7151

System Action: Subcommand
processing stops, DUMPSCAN
processing continues.

DEVICE {'rdev' I'vdev'} NOT
FOUND
Explanation: On a real or virtual
device request, the specified device was
not found.
System Action: Subcommand
processing stops, DUMPSCAN
processing continues.
User Response: Make sure the
specified device is included in the
system that produces the dump. Retry
the subcommand.

NON-HEX CHARACTER IN
STRING
Explanation: The input string must
consist of valid hexadecimal characters.

User Response: May indicate an
overlay problem. Other DUMPSCAN
functions are still available. Continue.

7121

USER 'userid' VMBLOK NOT
FOUND

User Response: Correct the input and
retry.

7161

STRING 'string' (NOT
FOUNDINOT FOUND BEFORE
END)
Explanation: The requested string was
not found within the limits given, or, if
indicated, before the end of dump was
reached.

Interactive Problem Control System Extension (IPCS) Messages

477

DMM
System Action: Subcommand
processing stops, DUMPSCAN
processing continues.

7181

Explanation: The compressed load map
was not found at the end of the dump.
All DUMPSCAN functions except
MAPA, MAPN and USERMAP (for
CMS dumps) are still valid.

User Response: Check that the string
is correct, and retry the subcommand.

717E

INVALID FORM OF LOCATE
COMMAND

System Action: Processing continues.
User Response: You may continue to
use DUMPSCAN. If there is a valid
IPCS nucleus load map available and if
the dump is on the R/W A disk, you may
use the IPCSMAP subcommand to add
the load map to the dump.

Explanation: You issued the LOCATE
subcommand in an improper format or
with too few operands.
LOCATE (UP)

[stringlx'string'}
from to [inc]

Where:
string
x'string
from

Inc

7191
is up to 8 EBCDIC
characters.
is up to 16 hexadecimal
digits.
is an address (in
hexadecimal) up to six
significant digits in
length.
is an address (in
hexadecimal) up to six
significant digits in
length.
is an optional
increment (in
hexadecimal) from 1 to
1000.

For LOCATE, the 'to' address must be
greater than the 'from' address. For
LOCATE UP, the 'from' address must be
greater than the 'to' address.

System Action: The system stops
processing the subcommand.
User Response: Reissue the
subcommand in its valid form.

478

VM/SP System Messages and Codes

THIS DUMP HAS NO LOAD MAP

ERROR 'nnn' IN FSSTATE FILE
'fn ft fm'
Explanation: FSSTATE macro failed
to find the dump file specified by your
reply to DMMDSC701R.
System Action: Processing continues.
User Response: Consult the VM/SP
eMS Macros and Functions Reference,
for a description of error 'nnn' in the
FSST ATE macro. Correct the problem
and retry.

7201

LOAD MAP ALREADY PRESENT
Explanation: The IPCSMAP
subcommand was issued for a dump that
already has an IPCS map appended.
System Action: Issue message
DMMDSC725R.
User Response: Respond to message
DMMDSC725R which will follow.

DMM
7211

THE &NAME TABLE IS FULL

7241

Explanation: You have run out of
space in the &NAME table. The table
can hold up to 64 tokens, either
&NAMEs or subcommand operands.

Explanation: The subcommand AREGS
or MREGS was issued against a dump
taken on a machine running in
uniprocessor mode.

System Action: Subcommand
processing stops, DUMPSCAN
processing continues.

User Response: You may replace a
long &NAME entry with a shorter one
or you may terminate the session and
restart. This procedure clears out the
table.

7221

INVALID ENTRY INTO &NAME
TABLE

User Response: Verify that you are
examining the correct dump. To see the
registers, the PSW, etc., issue the REGS
subcommand.

725R

Explanation: The &NAME
subcommand has found an invalid
operand. PRINT and &name are not
allowed in the &name table as operands.

DO YOU WISH TO REPLACE IT?
RESPOND YESINO
Explanation: This message always
follows DMMDSC720I.
System Action: The system waits for a
response. Subsequent action is
dependent on the user response.

System Action: Subcommand
processing stops, DUMPS CAN
processing continues.

User Response: If the response is
"yes", a new load map is appended to
the dump in place of the present one.
For any other response, the
subcommand is terminated.

User Response: Reissue the
subcommand using a valid operand.

7231

(IPLINON-IPL) REGISTER
REQUESTED IN UNIPROCESSOR
DUMP

THE DUMP IS NOT ON THE
A-DISK
7261
Explanation: The IPCSMAP or
USERMAP subcommand requires the
dump to be on the A-disk.

(IPLINON-IPL) RIOBLOKS
REQUESTED IN
NON-MULTIPROCESSOR DUMP

System Action: Subcommand
processing stops, DUMPSCAN
processing continues.

Explanation: The subcommand
ARIOBLOK or MRIOBLOK was issued
against a dump taken on a
non-multiprocessor machine.

User Response: Copy the dump to the
A-disk of your virtual machine before
issuing the subcommand.

System Action: Subcommand
processing stops, DUMPSCAN
processing continues.
User Response: Verify that you are
examining the correct dump. Use the
RIOBLOK subcommand to see the
RCHBLOK, RCUBLOK, and

Interactive Problem Control System Extension (IPCS) Messages

479

DMM
RDEVBLOK of the specified device on
the failing processor.

731E

Explanation: A required operand is
either missing or invalid.

DOS SIMULATION NOT IN
EFFECT.

7281

OPERAND MISSING OR
INVALID

You may also get this message when
you specify the SCROLL operand before
a successful TRACE subcommand
established a "previous" trace location.

Explanation: You have requested a
display of DOS simulation pointers, but
DOS simulation is not in effect. In case
a problem has arisen with the DOS
error detection routine, the pointers are
displayed and may be valid.

System Action: Subcommand
terminates.

System Action: The pointers are
displayed anyway.

User Response: Reissue the command
with a valid operand.

User Response: None.
732E

NO DUMPID INFORMATION
FOUND.

7291

Explanation: IPCS did not recognize
this command.

Explanation: You have requested a
display of the DUMPID information
field in the DMPINREC but the field
contained only binary zeros.

Note: If the subcommand name is
longer than eight characters, only the
first eight characters are shown.

User Response: Check the spelling and
reissue the command.

System Action: Subcommand
processing stops, DUMPSCAN
processing continues.

System Action: Subcommand
terminates.

User Response: None.

CONFLICTING OPERAND operand

730E

Explanation: This message occurs
when:
1.

The same option is specified twice in
the same command, or
The function required by the given
option is incompatible with a
previously specified operand.

System Action: Subcommand
terminates.
User Response: Reissue the command
with the operands correctly specified.

480

VM/SP System Messages and Codes

UNRECOGNIZED SUBCOMMAND
- subcommand

733E

ERROR DETECTED WHILE
PROCESSING THE
SUBCOMMAND - subcommand
Explanation: IPCS detected an error
while it was processing subcommand.
Note: If the subcommand name is
longer than eight characters, only the
first eight characters are shown.

User Response: Fix the error and
reissue the subcommand.
System Action: Subcommand
terminates.

(

DMM
7401

TRACE TABLE POINTERS
INVALID:
START = start END = end
CURRENT = current
Explanation: While attempting to
display CP trace table entries, it was
determined that the CP trace table
pointers contained in the dump are
invalid. Possible causes of this error
are:
1.

The trace table start address
indicates the trace table begins at
zero.

The trace table start address is
greater than the trace table end
address.

The current trace table address is
outside of the trace table.

The current trace table address is
not on 16 byte boundaries, or the
trace start address or trace end
address is not on a page boundary.

The trace table is less than a page
In sIze.

•

If a "FROM" was not specified, then
determine the location of the trace
table and reissue the TRACE
subcommand with a "FROM"
location specified.

•

If a "FROM" location was specified,
then ignore the message.

741E

"FROM" LOCATION OUTSIDE
OF TRACE TABLE RANGE:
START = start END = end
CURRENT = current
Explanation: The "FROM" location
specified on the TRACE subcommand of
DUMPSCAN is a negative hexadecimal
number.
System Action: The TRACE
subcommand terminates. DUMPSCAN
processing continues.
User Response: Reissue the TRACE
subcommand with the correct "FROM"
location specified.

7411

"FROM" LOCATION OUTSIDE
OF TRACE TABLE RANGE:
START = start END = end
CURRENT = current

System Action:
1.

If a "FROM" location was specified,
then the processing of the
subcommand will continue at the
"FROM" location. The display will
not wrap at the trace table start
position and will stop when:

Explanation: The "FROM" location
specified on the TRACE subcommand of
DUMPSCAN points to a location
outside of the trace table while the trace
table pointers appear to be valid.

System Action: Processing continues.

The specified count (or default
count, if the count was not
specified) has been reached.

b. The address of the next trace
entry to display is less than or
equal to zero.

User Response: Verify the "FROM"
location specified on the TRACE
subcommand, and the trace table
pointers.
•

If a "FROM" location was not
specified, then the processing of the
subcommand will be terminated.

If the "FROM" location is incorrect,
then reissue the TRACE
subcommand with the correct
"FROM" location.

User Response:

Interactive Problem Control System Extension (lpeS) Messages

481

DMM
•

7421

means that the address of the next entry
to display would be negative. Since
negative addresses are impossible in a
dump, no trace table data can be
displayed.

If the trace table pointers are
incorrect and the "FROM" location
is correct, then ignore the message.

"FROM" LOCATION NOT ON A
16 BYTE BOUNDARY

User Response: Enter a TRACE
subcommand without the SCROLL or
SCROLLU operands.

Explanation: The "FROM" location
specified is not on a 16 byte boundary.

System Action: The system will stop
processing the command, and will not
display any trace entries.

System Action: The address specified
has been truncated to a 16 byte
boundary and processing continues.
User Response: Verify the "FROM"
location specified on the TRACE
subcommand. The "FROM" location
must be on a 16 byte boundary.

7431

Explanation: The specified load map is
not valid for the type of map being
processed. 'maptype' is one of the
following:

TRACE ENTRY IS TOO LARGE
TO BE COMPLETELY
DISPLAYED

•
•

Explanation: The formatted trace
entry could not completely fit on the
screen (24 line screen). Some lines of
output have been truncated.

744E

COMMAND TERMINATED, CAN
NOT PROCESS BEYOND
STORAGE BOUNDARY
Explanation: You issued one of these:
•
•

The TRACE subcommand with the
SCROLL or SCROLLU operand
The SCROLL or SCROLLU
subcommand,

NUCLEUS - The system nucleus
load map.
Name of the secondary map defined
in DMMTAB.

System Action: Processing continues.
User Response: Determine the fileid of
the correct load map for this map type
and respond to message DMMMAP806R.

System Action: Command completed.
User Response: To view the complete
formatted trace entry, the user should
reissue the TRACE subcommand
specifying a count of at least one (1).

maptype MAP 'In It 1m' IS NOT
VALID

8011

8021

FOR maptype, THE MAP NAMED
'In It 1m' WAS ADDED TO THE
IPCS MAP
Explanation: The specified map has
been added to the IPCS map which is
currently being built or, for the
USERMAP subcommand, to the IPCS
map which was previously appended to
the dump. 'maptype' is the name of the
secondary map type defined in
DMMTAB.
System Action: Processing continues.

following a previous trace table display
that stopped at the end of storage. This

482

VM/SP System Messages and Codes

User Response: None.

DMM
8031

'fn ft fm' CONVERSION
COMPLETE
Explanation: The dump or symptom
summary file named has been
successfully converted.

804E

System Action: None.

Explanation: The fileid of the specified
map is being requested for one of the
following reasons:

User Response: None.

Prompt was requested when the
command was entered.

The default name or the name
previously supplied could not be
found or was found to be in error.
'maptype' is one of the following:

ERROR IN DATA EXTRACTION
Explanation: The text portion of the
problem report may not be complete due
to the absence of supporting information
(for example, CPIPCS MAP Al does not
match the system). This message is also
issued if subroutines encounter an error
reading from the dumpfile, or DMMCPA
cannot recognize the abend code.
System Action: IPCS extraction
continues to extract as much data as
possible. This message occurs on the
terminal as well as in the text portion of
the problem report.
User Response: None.

8051

FOR 'type', ENTER 'FN FT FM'
OF THE map type MAP, OR ENTER
A NULL LINE, CMS, NONE, OR
QUIT

806R

xxxxxx ABEND CODE NOT
RECOGNIZED BY DATA
EXTRACTION

a.
b.
c.

System Action: The system waits for a
response. Subsequent action is
dependent on the user response.
User Response: Enter the fileid of the
requested map. If file type and/or file
mode are not entered they will default
to 'MAP' 'AI' respectively.
Alternatively you may enter one of the
following:
•

Explanation: This message is issued in
module DMMCPA if the abend code in
the dump does not compare with any
abend code in the lookup table.

•

•
System Action: Processing continues.
User Response: Either the abend code
in the dump is overlaid or an unknown
abend code has been presented. Call
your IBM program support
representative.

IPCS - When appending an IPCS
map to a dump.
NUCLEUS - The system nucleus
load map.
Name of the secondary map type
defined in DMMTAB.

•

a null line - To use the defined
default fileid.
CMS - To enter CMS subset.
On return this message will be
reissued.
NONE - To bypass processing
this particular map. The reply is
ignored and the message
reissued if the requested map is
the nucleus map.
QUIT - To terminate MAP
processing.

Interactive Problem Control System Extension (IPCS) Messages

483

DMM
UNABLE TO LOCATE maptype
MAP 'In It fm '

8071

8111

Explanation: The dump being
processed does not have an IPCS map.

Explanation: The specified input map
could not be found. 'maptype' is one of
the following:
1.

System Action: DMPINREC is
converted and RC =4.

NUCLEUS - The system nucleus
load map.
Name of the secondary map defined
in DMMTAB.

System Action: Processing continues.

User Response: None.

812E

User Response: Respond to message
806R which will follow.

8081

System Action: Processing stops.

Explanation: The IPCS map has been
created from the specified system's
nucleus load map.

User Response: None.

813E
System Action: Processing continues.
User Response: None.

System Action: Processing stops.
User Response: If the 'dumptype' field
is invalid, reissue the MAP command
with the correct 'dumptype'.

Explanation: The format of the
specified input map is not as expected
for the type of map being processed.
'maptype' is one of the following:

NUCLEUS - The system nucleus
load map.
Name of the secondary map defined
in DMMTAB.

System Action: Processing continues.
User Response: Respond to message
806R which will follow.

MAP FUNCTION NOT
SUPPORTED FOR 'dumptype'.
Explanation: The 'dumptype' field is
invalid, or MAP support has not been
defined for it in DMMTAB.

FORMAT OF maptype MAP 'fnft
fm' IS INVALID

'fn ft fm' ALREADY
CONVERTED
Explanation: The symptom summary
or dump file named has already been
processed by CONVERTS.

{CPICMS} IPCS MAP 'fn ft fm'
CREATED FROM MAP 'fn ft fm'.

8101

NO IPCS MAP APPENDED TO
DUMP

814E

{CPICMS} IPCS MAP NOT
CREATEDIAPPENDED
Explanation: The IPCS map was not
created or appended due to some
previous error or user action.
System Action: Processing stops.
User Response: Inspect the previous
messages to determine the reason the
map could not be created or appended.

484

VM/SP System Messages and Codes

DMM
815E

PROCESSING ERROR IN
{CPICMS} MAP ROUTINE 'name'

8I8E

Explanation: The named routine has
returned an invalid return code or
invalid data to the map routine, or the
map routine itself has failed.

Explanation: Space exists in the IPCS
map header for 20 header entries. All 20
header entries have been filled and
additional map processing has been
requested.

System Action: Processing stops.
User Response: Save the input and the
output and report the problem to your
IBM programming support
representative.

816E

INPUT MAP LIMIT REACHED
FOR {CPICMS} IPCS MAP 'fn ft
fm'

System Action: The requested map is
not added to the IPCS map, and
processing stops.
User Response: Check to determine if
one of the existing maps can be
eliminated. If this is possible, recreate
the IPCS map using the PROMPT
option of the MAP command, and enter
a null line in response to message 806R
for the map or maps not required.

{CPICMS} IPCS MAP 'fn ft fm'
ALREADY EXISTS
Explanation: The specified IPCS map
was previously created and still exists.
System Action: Processing stops.
819R
User Response: Determine if the
existing IPCS map is still valid or
required. If so, it may be renamed or
the MAP command reissued with the
'prompt' parameter to permit the
creation of a new IPCS map with a
different file name. Otherwise, erase it
and reissue the MAP command.

817E

map type MAP 'fn ft fm' OVERLAPS
A PREVIOUS MAP

Explanation: The address range of the
specified input map overlaps either
partially or completely the address
range of a map previously included in
the IPCS map. 'maptype' is the name of
the secondary map defined in
DMMTAB.

ENTER THE 'FN' OF THE
{CPICMS} IPCS MAP TO BE
CREATED, OR ENTER A NULL
LINE
Explanation: The file name of the new
IPCS map is being requested in response
to the 'prompt' parameter included on
the MAP command. 'FN' is the
filename to be assigned to map; the
default IPCS map file names are
'CPIPCS' or 'CMSIPCS'. The file type
and file mode will be 'MAP AI'.
System Action: Processing continues.
User Response: Enter the desired file
name of the IPCS map to be created or
press the ENTER key (or its equivalent)
to use the default. 'Quit' may also be
entered to terminate the MAP
command.

System Action: Processing stops.
User Response: Determine which input
map is in error and reissue the
command using the proper input maps.

Interactive Problem Control System Extension (IPCS) Messages

485

DMM
8201

map support is available. If it is, report
the problem to IBM.

INSUFFICIENT MAP
PROCESSING DISK SPACE FOR
'fn ft fm'
Explanation: The amount of disk space
required for map processing is not
available.

8241

Explanation: The specified IPCS map
has been appended to the dump.

System Action: CMS subset is
automatically entered to permit
obtaining additional disk space.
User Response: You can obtain
additional disk space on the 'A' disk and
enter 'return', but first try to delete any
files which you no longer need.

8211

System Action: Processing continues.
User Response: None.

830R

User Response: Enter the requested
data or a null line.

System Action: No map is appended
and processing continues.

System Action: Proc.essing continues
with no map appended.
User Response: Check the
documentation for the defined
subsystem or SCP to determine if IPCS

486

8401

VM/SP System Messages and Codes

ADDRESS 'rstor' NOT
AVAILABLE
Explanation: All of the required data
at the specified address was not
available in the dump.
System Action: Formatting of the
current unit is bypassed and processing
c.ontinues with the next logical unit, if
any, to be formatted.

IPCSMAP FUNCTION NOT
SUPPORTED FOR 'dumptype'
Explanation: The dump being
processed is not an IPCS supported type,
or if it is, no support has been defined
for appending an IPCS map.

System Action: IPCSDUMP will
prompt you for the missing keyword
data.

Explanation: The specified IPCS map
does not correspond to the dump.

822E

ENTER KEYWORD 'keyword =
Explanation: An extraction routine
returned with keyword data missing.

{CPICMS} IPCS MAP 'fn ft fm'
NOT VALID FOR DUMP
'PRBnnnnn'

User Response: Ensure that the
correct level of the system nucleus load
map was used in creating the IPCS map
and that this level matches the dump.
Also, ensure that the correct IPCS map
was processed. You are prompted via
message B06R to enter the correct name.
Respond with the correct map name or
respond QUIT to bypass appending a
map at this time.

{CPICMS} IPCS MAP 'fn ft fm'
APPENDED TO 'PRBnnnnn'

User Response: None.

8411

LOW CORE 'rstor' REFERENCED
Explanation: A dump address below
32K was unexpectedly referenced while
formatting some logical unit.
System Action: Formatting of the
current logical unit is bypassed, and
processing continues with the next
logical unit, if any, to be formatted.

DMM
User Response: None.

8421

853S

Explanation: IPCSDUMP was entered
but no class V or D dump files were
found in your spool reader.

ADDRESS'rstor'
RE-REFERENCED
Explanation: A dump address which
was previously referenced while
formatting some logical unit was
unexpectedly re-referenced.

System Action: None.
User Response: Check the reader
queue to determine if any files exist. If
there are reader files, check to make
sure they are of the proper class and not
in a hold status.

System Action: Formatting of the
current logical unit is bypassed and
processing continues with the next
logical unit, if any, to be formatted.
8551
User Response: If this message is
repeated multiple times with the same
address, it is probably indicative of a
large loop due to invalid control blocks.
Halt current execution and reissue the
PRTDUMP command with the
NO FORM option.

8431

FOR 'EXTRACTION': The
extraction routine specified in
DMMTAB was not found.
FOR 'FORMAT': DMMPRT could
not find the format routine specified
in DMMTAB for CP or CMS dumps.
System Action:

Explanation: An error occurred while
obtaining one of the following:

2.
3.

{CPICMS}
{'EXTRACTION' I'FORMAT'}
ROUTINE NOT FOUND
Explanation:

REQUIRED RESOURCES NOT
AVAILABLE - FORMATTING
BYPASSED

NO DUMP FILES EXIST

FOR 'EXTRACTION': Processing
continues with full user prompting.

Six work buffers.
The DMPINREC.
Dump page zero.

FOR 'FORMAT': Standard print
dump is taken (PSW, regs, O-end).

System Action: The NOFORM option
is forced on and the option verification
message is issued. If NOH EX was not
requested, the hex dump is printed,
otherwise processing stops.
User Response: If the error occurred
while obtaining six work buffers,
reconfigure your virtual machine with
more storage and reissue the command.

User Response: None.

856E

UNABLE TO LOCATE {CPICMS}
'routine' ROUTINE 'name'
Explanation: The command was
unable to find the specified processing
routine defined in the communications
table DMMTAB.
'routine' = MAP, FORMAT,
EXTRACT or DUMPSCAN;
'name' = module name.
System Action: MAP processing
terminates, other functions continue.

Interactive Problem Control System Extension (IPCS) Messages

487

DMM
User Response: Determine why the
named routine could not be found.
Make it available to the command and
reissue the command.

860E

863E

INVALID OPERAND - operand
Explanation: If issued by DMMDCM,
DMMDCP, or DMMDSC, CP detected
an invalid operand on the subcommand
line. If issued by DMMSCR, you
specified an operand on the SCROLL,
SCROLL U or SCROLLU subcommand;
operands are only allowed when
scrolling for a trace formatting display.
For PRTDUMP, the first operand
entered was not PRBnnnnn. For MAP,
the second operand was not PROMPT.

FATAL I/O ERROR READING
DUMP
Explanation: The DIAGNOSE code
X'34' or X'14' failed while reading the
dump from the spooled reader.
System Action: Processing stops.

System Action: The system stops
processing the command or
subcommand.

User Response: Reader may already be
opened(in use) with another file. Close
reader and retry IPCSDUMP command.
If IPCSDUMP still fails, then contact
the system programmer.

861E

User Response: Reissue the command
or subcommand without the operand or
with a valid operand.

FILE 'fn' NOT FOUND
864E
Explanation: File name entered could
not be found.

Explanation: CMS detected an error
when setting up SVC 199 addresses.

System Action: Processing stops.
User Response: Reissue the command
specifying the correct filename.

862E

488

System Action: Processing stops.
User Response: There may be an SVC
199 conflict. Re-IPL the system an
reissue the command. If it still fails,
then see your system programmer or
report the problem to your IBM
programming support representative.

NO PARAMETERS ENTERED
Explanation: At least one parameter is
required for this command to function
and none were entered. For
PRTDUMP, the first parameter must be
a filename (PRBnnnnn) of a dump file
previously created by IPCSDUMP. For
MAP, the first parameter must be the
SCP or subsystem type.

STORAGE INITIALIZATION
INCOMPLETE

865E

NO PARAMETERS ALLOWED
Explanation: Parameters are not
allowed with this command.

System Action: Processing stops.

User Response: Reissue the command
specifying the correct parameter.

User Response: Issue command
without parameters.

VM/SP System Messages and Codes

DMM
866E

FILE 'fn ft fm' NOT FOUND

System Action: Subcommand
processing stops, DUMPSCAN
processing continues.

Explanation: The file identified as 'fn
ft fm' could not be found.

User Response: Report the problem to
your IBM programming support
representative.

System Action: Processing stops.
User Response: Enter command with
the correct 'fn ft fm'.
8691
867E

'fn ft fm' IS NOT A SYMPTOM
SUMMARY FILE

Explanation: The user issued either
SYMP (a DUMPS CAN subcommand) to
display the symptom record or
PRTDUMP to print the dump. An error
has occurred during the execution of an
FSREAD macro against 'fn ft fm'. For a
description of error 'nnn', see the
FSREAD macro in the VM/ SP eMS
Macros and Functions Reference.

Explanation: The 'fn ft fm' named is
not a symptom summary file and cannot
be converted.
System Action: Processing stops.
User Response: None.

868E

REQUIRED RESOURCES NOT
AVAILABLE

System Action: For displaying the
symptom record, the SYMP function is
terminated, but DUMPS CAN processing
continues. For printing the dump, the
PRTDUMP function continues.

Explanation: IPCS was unable to get
the required resources. This usually
indicates that an error has occurred
within the IPCS system.

User Response: Check the macro
description to see what type of failure
'nnn' indicates. Correct the error when
possible and retry.

System Action: Subcommand
processing stops, DUMPS CAN
processing continues.
User Response: Report the problem to
your IBM programming support
representative.

8681

REQUIRED RESOURCES ARE
NOT AVAILABLE, SYMPTOM
RECORD FOR FILE 'PRBnnnnn'
CANNOT BE DISPLAYED.
Explanation: The user issued either
SYMP (a DUMPS CAN subcommand) to
display the symptom record or
PRTDUMP to print the dump. An error
occurred while obtaining the
DMPINREC needed for displaying the
symptom record.

ERROR 'nnn' OCCURRED WHILE
READING SYMPTOM RECORD
FOR FILE 'PRBnnnnn'.

8701

SYMPTOM RECORD FOR FILE
'PRBnnnnn' CANNOT BE
FOUND.
Explanation: The user issued either
SYMP (a DUMPS CAN subcommand) to
display the symptom record or
PRTDUMP to print the dump. A valid
symptom record could not be found for
display or for print.
System Action: For displaying the
symptom record, the SYMP function is
terminated, but DUMPSCAN processing
continues. For printing the dump, the
PRTDUMP function continues.
User Response: None.

Interactive Problem Control System Extension (IPCS) Messages

489

DMM
871E

USER NOT AUTHORIZED TO
PROCESS CP SYSTEM DUMPS;
NO OTHER DUMPS EXIST
Explanation: A user who is not
authorized to issue DIAGNOSE code
X'34' invoked IPCSDUMP to process a
dump, and a class V dump does not
exist.

490

VM/SP System Messages and Codes

System Action: Dump processing
terminates.
User Response: If you tried to look at
a system dump, get authorization to
issue DIAGNOSE code X'34'; else,
obtain a class V dump.

CSI

Group Control System (GCS) Messages
OOIE

Invalid option 'option'

004E

Explanation: An invalid option has
bee:h entered. The option may have
been misspelled, it may conflict with
another option on the command line, or
it may have been entered twice. The
option may also have been abbreviated
incorrectly.

'optionl' and 'option2' are
conflicting options
Explanation: The options named in the
message are mutually exclusive and
must not be coded in the same
command.
System Action: RC = 24.
The command terminates, and system
status is not changed.

System Action: The command
terminates, and system status is not
changed.

User Response: Correct and reissue
the command.

User Response: Correct and reissue
the command.
005S
002E

Invalid parameter 'parameter' in
the option 'option' field
Explanation: The parameter entered
after 'option' was invalid.
System Action: RC = 24.
The command terminates, and system
status is not changed.
User Response: Correct the option and
reissue the command.

003E

'option' option specified twice
Explanation: This option was specified
more than once in the command line.
System Action: RC = 24.
The command terminates, and system
status is not changed.

Virtual storage capacity exceeded
Explanation: There is not enough
storage available to complete the
requested operation.
System Action: No action is taken on
the command, and system status is not
changed. For query commands, the
return code is 8; otherwise, the return
code is 104.
User Response: You must either free
some virtual storage or increase the size
of your virtual machine. To free some
virtual storage, issue the RELEASE
command for any minidisks that you no
longer need; then reissue the original
command. To increase the size of your
virtual machine, use the DEFINE
command; then re-IPL GCS and reissue
the original command.

User Response: Correct and reissue
the command.

Group Control System (GCS) Messages

491

CSI
005T

Virtual storage capacity exceeded

009E

Explanation: There is not enough
virtual storage available for file
management control blocks.

Explanation: One of the following:
1.

System Action: The virtual machine is
placed in a disabled wait state and the
disk is not updated.

2.
3.

User Response: Use the CP command
DEFINE to increase the size of the
virtual machine, re-IPL GCS, and
reissue the command.

006E

Operand is missing or invalid

An operand was coded incorrectly in
a command; or
A required operand was not coded;
or
A duplicate operand was coded.

System Action: The command
terminates with no action taken.
User Response: Correct the operand
and reissue the command.

Invalid parameter 'parameter'
0101
Explanation: An invalid operand, an
extraneous operand, or too many
operands were coded in the command
line or EXEC statement.

Explanation: The GDUMP command
was completed successfully. All
requested areas were dumped.

System Action: RC = 24.
The command or EXEC statement
terminates, and system status is not
changed.
User Response: Correct and reissue
the command.

Command Complete

System Action: Processing continues.
User Response: None.

011E

Invalid character in fileid 'fn ft'.
Explanation: An invalid character was
specified in the file 'fn ft'.

007E

Extraneous parameter 'parameter'
System Action: RC = 20.
Execution of the command is
terminated. The system status remains
the same.

Explanation: Too many operands were
specified for the GROUP EXEC.
System Action: RC = 24.
The GROUP EXEC is not executed.

User Response: Check the description
of the command format and reissue the
command.

User Response: Check the GROUP
EXEC format and re-execute the
GROUP EXEC.
012E
0081

Invalid Reply
Explanation: An invalid reply has
been entered for a previous message.
System Action: The previous message
will be displayed.
User Response: None.

492

VM/SP System Messages and Codes

No options allowed
Explanation: An option was specified
as part of the ACCESS command.
System Action: RC = 24.
No action is taken on the command, and
system status is not· changed.
User Response: Correct and reissue
the command.

CSI
013E

014E

No function specified

016E

Disk vdev not attached

Explanation: No functions were
entered with a QUERY, GLOBAL, or
SET command.

Explanation: The disk identified in the
message is not attached to the virtual
machine.

System Action: RC = 24.
No action is taken on the command, and
system status is not changed.

System Action: The task which
attempted to use the disk ends
abnormally with an abend code of 037.

User Response: Include the desired
function and reissue the command.

User Response: Use the CP LINK
command to connect the proper disk to
the virtual machine, and re-execute the
program.

Invalid function 'function'
Explanation: The GLOBAL command
has been entered with a function other
than LOADLIB. GCS can support only
the LOADLIB function of the GLOBAL
command.

017E

Disk '{modelvdevlvolid}' not
accessed
Explanation: The disk identified in the
message has not been accessed.
System Action: Execution of the
command or task is terminated. System
status is not changed if a command was
issued, but if the error occurred in a
task, the task ends abnormally with an
abend code of 037. The return code
from a command is O.

System Action: RC = 24.
No action is taken on the command, and
system status is not changed.
User Response: Correct the command
to 'GLOBAL LOADLIB
[libnamel. ..libname8]' and reissue the
command.

User Response: Access the disk and
re-execute the command or program.
015E

'parameter' is invalid for the
'function' function
0171
Explanation: A QUERY DISK
command has been issued with an
invalid parameter.

Disk 'mode' not accessed
Explanation: The disk specified in the
FILEDEF command has not been
accessed.

System Action: RC = 24.
The command is not executed.

System Action: This message is for
information only. Execution continues.

User Response: Correct and reissue
the QUERY command.

User Response: None.

018E

Disk mode is Read/Only
Explanation: The filemode of the
output file specifies a read-only disk
which cannot be written on.
System Action: If the problem
occurred when you issued a GROUP or

Group Control System (GCS) Messages

493

CSI
GENERATE EXEC, these EXECs
terminate with no action taken and
RC = 36. If the prefix is 'CSIXCP' or
'CSIVIP,' then the problem occurred
when a task attempted to write to a R/O
disk. The task ends abnormally with an
abend code of 037.

020E

Explanation: All read/write disks
currently accessed are full.
System Action: No action is taken on
the command, and system status is not
changed. The QUERY command issues
RC=2.

User Response:
1.

N 0 Read/Write disk with space
available accessed

If you have read/write authority
over the disk on which the output
file reside, use the CMS ACCESS
. command to re-access the disk as a
read/write disk, and then re-execute
the command or program; or

User Response: Access additional
read/write disks, or remove unneeded
files .

Invalid mode 'mode'

021E
2.

Use the CP LINK command to reset
the disk to read/write mode
(entering a password if necessary),
re-access the disk, and then
re-execute the command or program.

Explanation: This message can occur
for anyone of the following reasons:
1.
2.

No Read/Write mode disk accessed

019E

"3.
Explanation: The user does not have
access to a read/write disk in filemode
'mode' on which the command can write
its output. The command, in order to be
executed, requires that the disk be
accessed in read/write mode.
System Action: Execution of the
command is terminated. The return
code is 36 from CSIGEN and CSIGRP;
return code is 1 from QUERY DISK
R/W.
User Response:
1.

494

Access a read/write disk in the mode
you require and reissue the
command, or
Use the CP LINK command to reset
the disk to read/write mode, access
the disk again, and then reissue the
command.

VMjSP System Messages and Codes

The file mode was not entered
correctly.
The file mode number, if entered, is
not between 0 and 6.
More than two characters were
specified for the file mode.

System Action: RC = 24.
No action is taken on the command, and
system status is not changed.
User Response: Reissue the command
with the filemode specified correctly.

022E

No filename specified
Explanation: The OSRUN command
has been entered without specifying the
name of the application program to be
run.
System Action: No action is taken on
the command, and system status is not
changed.
User Response: Correct and reissue
the OSR UN command.

CSI
023E

No filetype specified

028S

Explanation: The FILEDEF command
requires that you specify both filename
and filetype.

Explanation: An input or output
operation has been attempted against a
device which is not defined in your
virtual machine.

System Action: RC = 24.
No action is taken on the command and
system status is not changed.

System Action: If the user's SYNAD
exit was specified in the DCB, it will be
executed. Otherwise, message 306 or
307 is issued and the task is abnormally
terminated with system abend code 001.

User Response: Reissue the command,
specifying the filename and filetype.

024E

User Response: DEFINE or ATTACH
the desired device to your virtual
machine.

File 'fileid' not found
Explanation: The file named in the
message was not found on any accessed
disk(s).

029S

System Action: RC = 28.
The file in question is not put in the
GLOBAL LOADLIB list and the system
continues with the next file, if any.

System Action: The channel status
word (CSW) and any available sense
information is displayed. If the first two
bytes of sense information are X'1070',
no sense information was available. If
the user's SYNAD exit was specified in
the DCB, it will be executed.
Otherwise, message 306S or 307S is
issued and the task is abnormally
terminated with system abend code 001.

System 'sysname' does not exist
Explanation: The system named in the
message has not been defined in the
Control Program module DMKSNT.

User Response: Examine the
device-dependent sense information for
details concerning the error. The
meaning of the sense information can be
found in the documentation for that
device or its control unit. Information
about the CSW can be found in the IBM
System/370 Principles of Operations,
GA22-7000.

System Action: If the message prefix
is 'CSIGRP,' then the failure occurred
during system generation, and system
status is not changed. If the message
prefix is 'CSIVSI,' then the failure
occurred while starting VSAM. The
task which was in control at the time of
the error is ended abnormally with an
abend code of 036.
User Response: Contact the system
programmer, who will generate a saved
system using the correct system name.

Unit check on device udeu. CSW
= csw, SENSE = sense
Explanation: A unit check has
occurred on the specified device.

User Response: Make sure that the
'system name' file has been created and
that it is on a disk that is accessed.

025E

Device udeu not attached

030S

Unrecoverable I/O error on device
udeu. CSW = csw
Explanation: An unrecoverable error
has occurred on the specified device.
System Action: The channel status
word (CSW) is displayed. If the user's

Group Control System (GCS) Messages

495

CSI
SYNAD exit was specified in the DCB,
it will be executed. Otherwise, message
306S or 307S is issued and the task is
abnormally terminated with system
abend code 001.
User Response: Examine the CSW for
information concerning the error.
Information about the CSW can be
found in the IBM System/370 Principles
of Operations, GA22-7000.

030T

032T

Supervisor error {112131415}.
Re-IPL sysname
Explanation: This message will be
issued with an error number between 1
and 5.
Error

Explanation

A G ETMAIN error has been
detected during GCS supervisor
internal processing. The error
probably occurred because
there was insufficient free
storage to allocate system
control blocks.

A FREEMAIN error was
detected during GCS supervisor
processing. The error probably
occurred because an authorized
program has destroyed system
pointers or other vital
information needed for storage
management.

GCS was unable to get storage
to extend a save area for a
critical processor.

GCS was unable to release a
save area extension for a
critical processor.

A QUERY LOCK command has
been issued, and the machine
that holds the lock was invalid.
The invalid virtual machine ID
indicates that the lock is held
by a nonexistent virtual
machine.

Unrecoverable I/O error on device
vdev. CSW = csw
Explanation: An unrecoverable I/O
error has occurred on the virtual device
with address 'vdev'. The two CSW bytes
at the time of the error appear in the
'csw' position in the message.
System Action: GCS halts by loading
a disabled wait state PSW. Execution of
the command is terminated.
User Response: Re-IPL GCS and
reissue the command that failed. If the
problem persists, contact your system
support personnel.

031S

Insufficient free storage is
available
Explanation: There is not enough free
storage available to process the
TACTIVE, TSAB, TLOADL, or IUCV
DUMPSCAN command that was issued.
If the message prefix is 'CSIIAL,' then
the message was issued for a TACTIVE
command. If the prefix is 'CSIITL,' then
the command was TLOADL. If the
prefix is 'CSIIIU,' the message was
issued for the lUCY DUMPS CAN
command. Finally, a prefix of 'CSIITA'
indicates that the message was issued
for the TSAB command.
System Action: The subcommand will
not complete.
User Response: Define a larger virtual
machine.

496

VM/SP System Messages and Codes

System Action: All five errors cause
the the 'system name' supervisor to be
terminated. The virtual machine is
reset.
User Response: If error 1 or 3 has
occurred, define a larger virtual
machine and re-IPL GCS. If the
problem persists, notify your system
support personnel.

CSI
If error 2 has occurred, make sure the
problem program is not altering system
storage. If the problem persists, notify
your system support personnel.

106E

Explanation: The maximum number of
virtual machines that can join this
group must be specified. The number of
group members must be in the range 1
to 65,535. Only digits 0-9 are valid.

If error 4 has occurred, notify your
system support personnel.
If error 5 has occurred, re-IPL GCS and
retry the operations that preceded the
failure. Contact your system support
personnel.

100E

System Action: None.
User Response: Specify the maximum
number of virtual machines that can
join this group.

Missing the system name operand
Explanation: You must specify a saved
system name when you invoke the
GROUP exec from a line mode terminal.
This operand was missing from the exec
call as issued.

107E

System Action: RC = 12.
The QUIT subcommand is not executed.

User Response: Reissue 'GROUP'
followed by the system name.

User Response: Issue the 'QQUIT'
subcommand if you want to leave the
file without saving the changes made
during the editing session. Press the
PF6 key or ENTER if you do want to
save the changes made in the file.

Enter selection number 1, 2, or 3
Explanation: The selection number
identifies the screen to be displayed or
updated.
System Action: None.
User Response: Type one of these
numbers on the command line and press
the ENTER key.

105E

System name not specified

File has been changed. Use
QQUIT to quit anyway.
Explanation: A QUIT subcommand
was issued by pressing the PF3 key but
the file has been changed during the
editing session.

System Action: RC = 24.
The command terminates.

104R

Maximum number of Virtual
Machines missing or invalid

1081

Saved System information is
continued on the next page
Explanation: There are two pages for
entering saved system information
identified on the Primary Option Menu.
The input areas for defining the
maximum number of virtual machines
that can IPL this group and the system
identification are on page two.

Explanation: No system name was
entered on the Primary Option Menu
after invoking the GROUP exec.

System Action: None

System Action: None.

User Response: None

User Response: Enter the system name
on the Primary Option Menu.

Group Control System (GCS) Messages

497

CSI
109E

System 'sysname' defined in
DMKSNT with NAMESYS

1101

All saved segment names on this
page are valid

p~am~~VMGROUP=NO

Explanation: The saved segment.
name(s) indicated have been defined in
DMKSNT.

Explanation: The system named in the
message has not been defined as part of
a group using the NAMESYS macro
parameter'VMGROUP=YES'.

System Action: None.
User Response: None.

System Action: No action is taken on
the GROUP exec.
User Response: To use GCS, the
system name must be defined as part of
a group. To define the system name as
part of a group, use the NAMESYS
macro parameter 'VMGROUP = YES'.

1111

You are now editing your 'fileid'
file
Explanation: The 'GROUP' exec has
been invoked from a line mode terminal.
System Action: None.

1091

System sysname defined in
DMKSNT with NAMESYS
parameter VMGROUP=YES
Explanation: The system named in the
message has been defined as part of a
group using the NAMESYS macro
parameter'VMGROUP=YES'.

User Response: None.

112E

Undefined PFKEY/PAKEY
Explanation: You have pressed a
PFkey or PAkey that has no function
assigned to it.

System Action: None.
System Action: None.
User Response: None.
User Response: None.
109T

System sysname defined in
DMKSNT with NAMESYS
parameter VMGROUP=NO.
Explanation: The system named in the
message has not been defined as part of
a group using the NAMESYS macro
parameter 'VMGROUP = YES'.
System Action: The CP command
"SYSTEM RESET" is issued which
causes a disabled wait PSW to be
loaded.

1131

The number of Authorized VM
userids processed is nnnnn
Explanation: 'nnnnn' is the total
number of virtual machine userids in
the 'system name GROUP' file
authorized to (1) execute programs in
virtual supervisor state and (2) have
access to all GCS functions.
System Action: None.
User Response: None.

User Response: Contact the system
programmer. To use GCS the system
name must be defined as part of a group
by using the NAMESYS macro
parameter 'VMGROUP = YES'.

498

VM/SP System Messages and Codes

CSI
114E

No authorized VM userids have
been specified

118R

Explanation: No userids have been
designated as authorized VM userids.
Authorized VM userids have authority
to run programs in virtual supervisor
state and have access to all GCS
functions.

Select disk address in the range of
001 through FFF
Explanation: System disk address or
system disk extension address is not in
the valid range.
System Action: None.
User Response: Correct the disk
address in error.

System Action: None.
User Response: None.
119R
1151

This is the {firstllast} page for
this screen

Select trace table size in the
range of 4K through 16384K
Explanation: The entry for the trace
table size is invalid.

Explanation: This is an information
message sent if you are on the first or
the last page of a GROUP EXEC menu.

System Action: None.
User Response: Correct the trace table
size.

System Action: None.
User Response: None.

1201
116E

The number of invalid userids on
this page is nn

Explanation: The userid named in the
message is a valid userid and is also an
entry In the Authorized VM userids list.

Explanation: At least one userid
entered on this screen is not a valid
logon.

System Action: None.

User Response: None.

User Response: Correct the userid(s)
that are in error.

1171

'userid' is a valid Authorized VM
userid

All userids on this page have been
verified as valid
Explanation: All userids have been
verified as valid userids.

1211

'userid' is a valid userid
Explanation: The userid entered as the
recovery machine or the userid entered
to receive dumps is a valid userid.
System Action: None.
User Response: None.

System Action: None.
User Response: None.

Group Control System (GCS) Messages

499

CSI
122E

'userid' is not a valid userid

126E

Explanation: The userid must be valid
in order to receive dumps of common
storage or be designated as the recovery
machine.

Explanation: No saved segments have
been identified for automatic linkage
when this GCS group is IPLed.

System Action: None.

User Response: Correct the userid(s)
in error.

User Response: None.

127E
1231

No saved segment names have
been specified

No userid has been specified to
receive dumps

The number of invalid saved
segment names on this page is nn
Explanation: At least one saved
segment name entered on the screen is
not defined in the system.

Explanation: Since no dumpid has
been specified, the dumps of storage will
default to the virtual machine operator.

System Action: None.
System Action: None.
User Response: Correct the saved
segment name(s) that are in error.

User Response: None.

124E

No userid has been specified as
the recovery machine

129T

Explanation: You must identify a
userid as the recovery machine.

Explanation: You have DETACHed
your virtual console.

System Action: None.

System Action: The CP command
'SYSTEM RESET' is issued which
causes a disabled wait PSW to be
loaded.

User Response: Designate the recovery
machine userid.

1251

User Response: Define a virtual
console with the CP DEFINE command,
and re·IPL the named system.

The number of saved segment
names processed is nnnnn
Explanation: 'nnnnn' is the total
number of saved segment links that the
system will attempt to link when this
GCS group is IPLed. The saved segment
lines are defined in the group
configuration file.
System Action: None.
User Response: None.

500

No virtual console attached.
Re-IPL sysname.

VM/SP System Messages and Codes

130T

Virtual console not ready. Re-IPL
sysname.
Explanation: You have NOTREADYed
your virtual console.
System Action: The CP command
'SYSTEM RESET' is issued which
causes a disabled wait PSW to be
loaded.

CSI
User Response: Ready your virtual
console with the CP READY command,
and re-IPL the named system.

131T

1341

Explanation: This is a normal message
upon IPL of the GCS system load deck
from the reader. The message specifies
how much free common storage is
available for GETMAIN requests.

ECMODE must be set ON to IPL
sysname.
Explanation: You must have
ECMODE ON to IPL this system.

System Action: The system continues
processing. If there is not enough free
common storage available for
GETMAIN requests, problems may
occur after the system is saved and
subsequently IPLed.

System Action: The CP command
"SYSTEM RESET" is issued which
causes a disabled wait PSW to be
loaded.
User Response: Set ECMODE ON
using the CP SET command, and re-IPL
the named system.

132S

User Response: Check the system
build documentation to make sure that
you have the available free common
storage that you need for this system.

Segment 'segname' does not exist
135T
Explanation: The segment named in
the message has not been defined in the
CP module DMKSNT.

System Action: The CP command
"SYSTEM RESET" is issued which
causes a disabled wait PSW to be
loaded.

User Response: Contact the system
programmer, who will generate the
segment.

User Response: Contact the system
programmer. The maximum number of
virtual machines that can join the group
is specified when the named system is
built.

Paging 1/0 error for segment
'segname'
Explanation: CP has encountered a
PAGING I/O error while attempting to
read the segment name from a direct
access storage device containing the
segment.
System Action: The segment is not
linked to the virtual machine. The
system continues processing.
User Response: If the problem persists
after you re-IPL the virtual machine,
notify system support personnel.

Group allocation exceeded for
system'sysname'
Explanation: The maximum number of
virtual machines that can join the group
associated with the named system has
been exceeded.

System Action: The segment is not
linked to the virtual machine. The
system continues processing.

133S

sysname has nnnnnnnn bytes of
a vailable common free storage

136T

Recovery machine 'userid' is not
IPLed. System 'sysname' cannot
be initialized.
Explanation: The recovery virtual
machine for this group has not been
IPLed, or the GCS system has been
regenerated.
System Action: The CP command
"SYSTEM RESET" is issued, which

Group Control System (GCS) Messages

501

CSI

13ST

causes a disabled wait PSW to be
loaded.

User Response: Contact the system
programmer. The recovery machine for
the group must IPL the named system
before other members of the group can
IPL it. If the system has been
regenerated, an the machines in the
virtual machine group must re-IPL the
GCS saved system.

User Response: Make sure that you
specified the right trace table size. If
the trace table size is correct you must
increase the size of available free
common storage.

140T

nnnnnnnn bytes needed for
requested number of users
exceeds available common free
storage of mmmmmmmm bytes

Explanation: The supervisor has
encountered an error for which no errOr
recovery was possible.

Explanation: A control block in the
common storage is allocated for each
user that may join the group. This
message is displayed if the size
(displayed as 'nnnnnnnn' bytes) of the
control blocks allocated for all users
exceeds available free common storage
(displayed as 'mmmmmmmm' bytes).

System Action: The named system
uses CP messages to display this
message on both the user's and the
system operator's consoles. The virtual
machine is dumped. The CP command
'SYSTEM RESET' is issued for this
virtual machine, which causes a
disabled wait PSW to be loaded.

System Action: The CP command
"SYSTEM RESET" is issued which
causes a disabled wait PSW to be
loaded.
User Response: Make sure that you
specified the right number of users that
may join the group. If this number is
correct, you must increase the size of
available free common storage.

139T

nnnnnnnn bytes needed for
requested trace table size exceeds
available common free storage of
mmmmmmmm bytes
Explanation: The trace table is
allocated in free common storage. This
message is displayed if the size of the
trace table (displayed as 'nnnnnnnn'
bytes) exceeds available free common
storage (displayed as 'mmmmmmmm'
bytes).
System Action: The CP command
"SYSTEM RESET" is issued which

502

VM/SP System Messages and Codes

sysname supervisor has terminated
because of an unrecoverable
error. Virtual machine has been
reset.

User Response: Re-IPL the named
system. If the failure persists on
subsequent IPLs, notify the system
programmer.

1418

Recovery machine 'userid' for
sysname has abnormally
terminated
Explanation: The virtual machine that
was designated as the recovery machine
has somehow been reset.
System Action: The supervisor of the
named system uses CP messages to
display this message on both the user's
and the system operator's console. The
supervisor will terminate, issuing
message 140T, and the virtual machine
will be dumped.
User Response: Have system support
personnel re-IPL the.recovery machine,
then re-IPL your virtual machine.

CSI
142T

Storage needed for Storage
Management exceeds available
common free storage. Define
more common storage.

201S

Explanation: A permanent console
error occurred while attempting to do
I/O to the console.

Explanation: Storage management
could not find enough common storage
for its control blocks.

System Action: All virtual machines
that have IPLed the named system will
be reset.

System Action: The CP command
"SYSTEM RESET" is issued which
causes a disabled wait PSW to be
loaded.
User Response: Increase the size of
common storage.

143T

Permanent console error - re-IPL
sysname

User Response: Re-IPL the system.

2021

GCS
Explanation: GCS is the active
operating system in your virtual
machine.

Storage needed for Storage
Management exceeds available
private free storage. Define more
private storage.

System Action: None.
User Response: None is necessary.

Explanation: Storage management
could not find enough private storage
for its control blocks.
System Action: The CP command
"SYSTEM RESET" is issued which
causes a disabled wait PSW to be
loaded.
User Response: Increase the size of
private storage.

200S

Console cannot be initialized re-IPL sysname

2031

Ready (nnnnn);
Explanation: The system has
completed the command that was
entered, but the command may not have
been completed successfully. A return
code from the command appears in the
'nnnnn' portion of the message. Error
or information messages with additional
information about the problem may
have preceded this message. The system
is ready for further input.
System Action: None.

Explanation: The console cannot be
opened for the named system due to an
I/O error.
System Action: All virtual machines
that have IPLed the named system will
be reset.

User Response: Check the return code
for the command in the VM/ SP Group
Control System Command and Macro
Reference or in the VM/ SP CP
Command Reference. Reissue the
command if necessary.

User Response: Re-IPL the system.

Group Control System (GCS) Messages

503

CSI
204S

Recovery task abended

2081

Explanation: An unrecoverable error
occurred in the recovery task.

Explanation: A REPLY command was
entered, but there is no outstanding
reply request with the identification xx.
Either the message request has already
been answered, the message reply
identification xx is incorrect, or a reply
was not being requested.

System Action: All virtual machines
for the entire group are terminated.
User Response: Re-IPL the system.

205E

System Action: The REPLY xx
command is ignored.

Unknown CP/GCS command
Explanation: A command was
transmitted to GCS or to CP but was
not recognized.
System Action: No action is taken;
system status is not changed.

User Response: If the reply
identification was incorrect, correct and
reissue the command.

209E

User Response: Correct and reissue
the command.

206E

Reply xx not outstanding

Reply xx not accepted, reply too
long for requestor
Explanation: A REPLY command was
entered and the reply text was too long
for the user's buffer. A REPLY text can
not be more than 119 characters long.

Reply not accepted, ID not
specified

System Action: The REPLY command
is ignored.

Explanation: A REPLY command was
entered without an identification
number.

User Response: Correct and reissue
the REPLY command.

System Action: The REPLY command
is ignored.
210E
User Response: Reissue the REPLY
command with a correct ID number
specified.

207E

Reply not accepted, ID number
not 00 to 99
Explanation: A REPLY command was
entered specifying an id not in the
range of 00 - 99.
System Action: The REPLY command
is ignored.
User Response: Correct and reissue
the command.

504

VM/SP System Messages and Codes

Reply not accepted, invalid ECB
address
Explanation: The WTOR to which the
REPL Y command is responding
contains an invalid (inaccessible) ECB
address in the parameter list.
System Action: The WTOR issuer is
abended. The abend code is E23; the
reason code is 1300.
User Response: Make sure that
parameter list addresses are within the
range of your storage. (Please also see
the entry for abend E23 in Figure 11 on
page 71)

CSI
Reply not accepted, invalid reply
buffer address

211E

Explanation: The WTOR to which the
REPL Y command is responding
contains an invalid (inaccessible) reply
buffer address in the parameter list.

System Action: The WTOR issuer is
abended. The abend code is D23; the
reason code is 1300.
24
User Response: Make sure that
parameter list addresses are within the
range of your storage. (Please also see
the entry for abend D23 in Figure 11 on
page 71)

28
32
36

Member cannot be loaded,
command not defined, RC = nn

212E

40
Explanation: A LOADCMD command
was entered, but an error occurred and
one of the following return codes was
set:
Code
1
4

Meaning
A LOADCMD already exists
for the requested name.
Module is marked "not
executable." The module is
not loaded; the command is
not defined. To determine
why the "not executable" flag
was set, examine the
information provided by the
linkage editor at the time the
module was created. The
module is not suitable to be
used as a command module.
Module is an overlay
structure. The module is not
loaded; the command is not
defined. If this program is to
be used as a command
module, it must be
restructured so that it does
not require overlays.

Module is marked "only
loadable." The module is not
loaded; the command is not
defined. This module is not
suitable to be used as a
command module.
The command name specified
is a GCS immediate command
or an abbreviation for one. A
nucleus extension will not be
created.
Too many or extraneous
operands were specified.
The specified member cannot
be found.
No member name was
specified.
A permanent I/O error was
detected when the system
attempted to search the
directory.
Insufficient virtual storage
was available for reading
directory entry for this
module.
There was not enough free
storage to build nucleus
control blocks representing
the command.

System Action: Execution of the
command is terminated. The command
name is not defined to the system.
User Response: Check return code
reason. If user error, correct the
problem if possible and reissue the
LOADCMD command.

2131

Reply xx cancelled
Explanation: The program that issued
a WTOR request with the reply
identifier 'xx' has abnormally
terminated. The reply that the program
asked for is therefore no longer needed.
System Action: Processing continues.
User Response: None.

Group Control System (GCS) Messages

505

CSI
2141

2151

2161

217E

No replies outstanding

The common lock is free

Explanation: A QUERY REPLY
command was entered, and there are no
outstanding reply requests.

Explanation: The QUERY LOCK
command was entered, and the common
lock is not held by any machine.

System Action: Processing continues.

User Response: None.

2181

The following replies are
outstanding:

The common lock is held by userid

Explanation: A QUERY REPLY
command was entered causing REPLY
id numbers and texts to be listed.

Explanation: The QUERY LOCK
command was entered, and the common
lock is held by the userid named in the
message.

System Action: Processing continues.

User Response: The REPLY command
may be entered with a REPLY id and
text in response to one of the
outstanding replies.

User Response: None.

GROUP ID = sysname, Users:
Current = nnnnn, Maximum
mmmmm

219E

Explanation: The OSRUN command
was issued with a parameter field of
more than 100 characters. Parameters
passed with the OSRUN command may
not be more than 100 characters in
length.

Explanation: A QUERY GROUP
command was entered causing the
system to provide the following
information:

System Action: RC = 24.
No action is taken on the command, and
system status is not changed.

sysname - the supervisor name of the
group you are running under.
nnnnn - the current number of users
in the group.
mmmmm - the maximum number of
users allowed for that group.
System Action: Processing continues.
User Response: None.

Parm field contains more than 100
characters

User Response: Reduce the parameter
field to a maximum of 100 characters
and reissue the OSRUN command.

220E

Unable to open file

'tn'

Explanation: The system was unable
to OPEN the file identified in the
message.
System Action: If the message prefix
is 'CSIGLB,' the system could not find
the LOAD LIB specified in the GLOBAL
command. Previously specified
LOADLIBs are nullified. A return code
of 28 is issued.

506

VM/SP System Messages and Codes

CSI
If the prefix is 'CSILOS,' the task that
issued the OPEN ends abnormally with
an abend code of 806 and a reason code
of 8. The abnormal end occurs because
the BLDL macro issued by the CSILOS
module was unable to read the file
directory.

Explanation: An I/O error occurred
while READing from a disk.
System Action: If the message prefix
is 'CSIGLB,' then the failure occurred
while processing a GLOBAL command.
Previously specified load libraries are
nullified, and the command issues a
return code of 100.

User Response: Re-IPL GCS, make
sure the file 'filename LOADLIB' exists,
and try the operation again. If the
failure persists, contact your system
programmer.

221S

If the message prefix is 'CSILOS,' the
task currently in control ends
abnormally, with abend code 806 and
reason code 8.

More than nnn libraries specified.
Explanation: No more than 63 load
libraries may be specified with a
GLOBAL command.
System Action: RC = 88.
Execution of the command is
terminated, and any previous library list
is cleared.
User Response: Combine some
libraries to reduce the number of
libraries required for this terminal
seSSIon.

222E

Error 'nn' reading file 'fileid' from
disk

223S

User Response: Contact your system
programmer.

Member 'membername' not found
in library

224E

Explanation: The member name
specified in the OSRUN command just
issued could not be found due to one of
the following:
•

None of the load libraries identified
in the GLOBAL command contained
this member name; or,

•

No load libraries were specified in
the GLOBAL command; or,

•

No GLOBAL command was issued.

File 'fn ft fm' contains invalid
record formats
Explanation: The load library file
named in the message did not have
'LIBPDS' as the first six characters in
its header record. GCS can support
only LIBPDS-format load libraries.
System Action: RC = 32.
The load library named in the message
is not GLOBALed, and the system
continues on to process the next
LOAD LIB in the GLOBAL command, if
any more LOADLIBS have been
specified.

System Action: The OSRUN command
fails, and the task abends with abend
code 806 and reason code 4.
User Response: Check the GLOBAL
command to make sure that the needed
libraries have been GLOBALed.
Reissue the GLOBAL command if
necessary and then reissue the OSRUN
command.

User Response: Check the format of
the LOADLIB named in the message,
and convert it to LIBPDS format if
possible.

Group Control System (GCS) Messages

507

CSI
2251

HX Complete

228E

Explanation: The HX command has
completed processing.

Explanation: A subtask of the program
or command failed with the specified
abend code ('xxx') and reason code
('yyyy'). The reason code is significant
only for FCA and FCB abend codes; it
will appear as zeroes for all other abend
codes.

System Action: All active programs
and commands in the virtual machine
have been terminated. All commands
not yet executed have been purged.
User Response: Enter new commands
for execution.

226E

System Action: The subtask has been
terminated. A dump may have been
taken.

Application 'name' failed - System
abend xxx-yyyy
Explanation: The application program
named in the message, Of a subtask of
the program, failed with the specified
abend code ('xxx') and reason code
('yyyy'). The reason code is significant
only for FCA and FCB abend codes; it
will appear as zeroes for all other abend
codes.

User Response: Refer to Figure 11 on
page 71 for explanations of the abend
and reason codes.

229E

User Response: Refer to Figure 11 on
page 71 for explanations of the abend
and reason codes.

508

System Action: The subtask has been
terminated. A dump may have been
taken.
User Response: Refer to Figure 11 on
page 71 for explanations of the abend
and reason codes.

Application 'name' failed - User
abend xxx-yyyy
Explanation: The application program
named in the message, or a subtask of
the program or command, failed with
the specified abend code ('xxx') and
reason code ('yyyy'). The reason code is
significant only for FCA and FCB abend
codes; it will appear as zeroes for all
other abend codes.

Subtask of 'name' failed - User
abend xxx-yyyy
Explanation: A subtask of the program
or command failed with the specified
abend code ('xxx') and reason code
('yyyy'). The reason code is significant
only for FCA and FCB abend codes; it
will appear as zeroes for all other abend
codes.

System Action: The program or
subtask has been terminated. A dump
may have been taken.

227E

Subtask of 'name' failed - System
abend xxx-yyyy

230E

Command 'command' failedSystem abend xxx-yyyy

System Action: The program or
subtask has been terminated. A dump
may have been taken.

Explanation: The command named in
the message failed with the specified
abend code ('xxx') and reason code
('yyyy'). The reason code is significant
only for FCA and FeB abend codes; it
will appear as zeroes for all other abend
codes.

User Response: Refer to Figure 11 on
page 71 for explanations of the abend
and reason codes.

System Action: The command has
been terminated. A dump may have
been taken.

VM/SP System Messages and Codes

CSI
User Response: Refer to Figure 11 on
page 71 for explanations of the abend
and reason codes.

231E

Command 'command' failed - User
abend xxx-yyyy

User Response: The condition of your
virtual machine may cause further
failures; contact your system
programmer.

234E

Explanation: The command named in
the message failed with the specified
abend code ('xxx') and reason code
('yyyy'). The reason code is significant
only for FCA and FCB abend codes; it
will appear as zeroes for all other abend
codes.

Abend xxx-yyyy occurred during
abend Resource Manager
processing
Explanation: The failure occurred
while attempting to release a task
resource, such as GETMAINed storage
or an open data set.
System Action:

System Action: The command has
been terminated. A dump may have
been taken.

If the failure occurred during
Resource Manager processing for a
subtask of the failing task,
termination will continue for the
failing task.

If the failure occurred during
Resource Manager processing for
the failing task, or occurred during
ABEND processing itself, the task is
set as nondispatchable, and
termination of that task is halted.

User Response: Refer to Figure 11 on
page 71 for explanations of the abend
and reason codes.

232E

Abend xxx-yyyy occurred during
abend ESTAE processing
Explanation: An ESTAE exit routine
failed, causing an abend.

No dump is taken for either of these
failures.

System Action: The failing exit is
bypassed, and any other exits are given
control. No dump is taken.

User Response: The condition of your
virtual machine may cause further
failures; contact your system
programmer.

User Response: The condition of your
virtual machine may cause further
failures; contact your system
programmer.
235E
233E

Abend xxx-yyyy occurred during
abend TASKEXIT processing
Explanation: A TASKEXIT exit failed,
causing an abend.
System Action: The failing exit is
bypassed, and any other exits are given
control. No dump is taken for any of
these failures.

Abend xxx-yyyy occurred during
abend internal processing
Explanation: The ABEND itself failed.
System Action: No dump is taken.
User Response: The condition of your
virtual machine may cause further
failures: contact your system
programmer.

Group Control System (GCS) Messages

509

CSI
236E

Ending apostrophe is missing

2391

Explanation: You did not include a
closing apostrophe in the parameter you
passed in an OSRUN command.

No entry points are currently
loaded in this virtual machine
Explanation: The system has
attempted to find all entry points loaded
by the system and could not find any.

System Action: The OSRUN command
terminates; system status remains
unchanged.

System Action: None.
User Response: None is necessary.

User Response: You can (1) reissue the
command, adding a closing apostrophe
to the parameter field, or (2) reissue the
command, omitting the apostrophes,
provided that there are no spaces or
special characters in the parameter you
wish to pass.

237E

2401

Explanation: The system has
attempted to find all entry points loaded
by the LOADCMD command and could
not find any.

Command ended without
detaching subtasks
Explanation: A command or program
ended normally but without
DETACHing those subtasks it created
that were not ATTACHed with
JSTCB = YES specified.

System Action: None.
User Response: None is necessary.

243S

User Response: The program should be
modified to DETACH all subtasks before
ending.

System Action: No action is taken on
the command. The system status is not
changed.

Ready;
Explanation: The system has
performed the action requested by the
user, or by an error message or
information message appearing before
this ready message.

Parameter list delimiter missing
Explanation: Tokenized plist is either
missing delimiter double word "FF" at
the end or is too long (longer than 1K
bytes).

System Action: The remaining
subtasks are DETACHed.

2381

No entry points were loaded by
the LOADCMD command

User Response: The user program
needs to have the delimiter of double
word "FF" at the end of the plist passed
to the command processing module.

300S

Control Program error indication
,
,
nnn

System Action: None.
User Response: None is necessary.

Explanation: An unexpected error
occurred while the Control Program was
processing a request from GCS to find
or load a saved system. Return code 177
is returned by CPo
System Action: The task which was in
control at the time of the error ends
abnormally with an abend code of 036.

510

VM/SP System Messages and Codes

CSI
User Response: Contact the
installation system programmer for
assistance.

301E

3041

Invalid CLEAR request
Explanation: A CLEAR request was
entered for a file definition that does
not exist .. No action was taken on the
command.

Invalid device 'devname'
Explanation: The device specified is
invalid.

System Action: None.
User Response: Correct the file
definition specified in the CLEAR
request.

System Action: RC = 24.
No action is taken on the command, and
system status is not changed.
User Response: Reissue the command,
specifying a valid device name.

302E

. --&05L

Explanation: A DLBL CLEAR
command was entered but the ddname
specified in the message was not found.

Parameter missing after
DDNAME

System Action: No action is taken on
the command.

Explanation: A parameter that is
required by the command was not
specified. For the FILEDEF command,
a device name or DUMMY or CLEAR
must be specified after the ddname. For
the DLBL command, a disk mode or
CLEAR must be specified after the
ddname.

User Response: Reissue the command
with the correct 'ddname' if'ddname'
was entered incorrectly.

306S
System Action: RC = 24.
No action is taken on the command, and
system status is not changed.
User Response: Correct and reissue
the command.

3031

No user defined
{FILEDEFIDLBL}s in effect
Explanation: A list of all FILEDEFs or
DLBLs in effect was requested, and no
FILEDEFs or DLBLs have been defined.
System Action: No further action
occurs; the command is terminated.
User Response: None.

DDNAME 'ddname' not found.

~~,,~t executed.

Input error 'nnn' on 'ddname'
.Explanation: If the prefix on the
message is 'CSISCT,' GeS issued this
message because an input error was
encountered (1) by an as CLOSE macro,
or (2) by an as CHECK or GET macro
when a SYNADAF (error analysis)
routine had not been specified by the
user. The error code in the message
identifies the specific error. For further
information, look up the error code in
the table in the 'User Response' section
below.
If the message prefix is 'CSISER,' this
message was built by the simulation
routine for the SYNADAF (error
analysis) macro; it was issued by a
user SYNAD routine. The error code in
the message identifies the specific error.
For further information. look up the
errol' code in the table in the 'User
Response' section below.

Group Control System (GCS) Messages

511

CSI
If the prefix is 'CSIXCP,' then an
unrecoverable error occurred while
reading from the disk named in the
message. The error code may be one of
the following:

Code
2
3

Meaning
A unit exception
occurred.
A record with an
incorrect length was
detected.
A permanent I/O error
occurred; the disk is full.

The fixed/variable flag in
FST entry was not F or

The given storage area
was smaller than the
actual size of the item
read. (This is a
recoverable error: the
number of bytes read
corresponds to the size of
the buffer.)
The number of items is
greater than 1 for a
variable-length file.
An unexpected end of file
occurred (the item
number specified exceeds
the number of items in
the file).
A variable-length file has
an invalid displacement
in the active file table.
Insufficient virtual
storage is available.
Requested item number is
negative, or item number
plus number of items
exceeds file system
capacity.

12
System Action: If the message prefix
is 'CSISCT' or 'CSISER,' the current
task ends abnormally with an abend
code of 001. If the prefix is 'CSIXCP,'
the task ends abnormally with an abend
code of 038.
User Response: Look up the error code
in the table below (for 'CSISCT' and
'CSISER' messages only) to find the
correct message and possible cause of
the error.

25
26

ALL DEVICES

Code
254

Meaning
BSAM was called with an
unposted ECB specified.

DISK INPUT

Code
1
2

512

Meaning
The file was not found.
The virtual storage area
was not within the limits
of the virtual machine.
A permanent disk error
occurred. This may occur
if you link to and access
another user's disk and
try to read a file that was
altered by its owner after
you issued the ACCESS
command. Reissue the
ACCESS command and
try to read the file again.
The number of items was
zero.

VM/SP System Messages and Codes

Note: All errors except 8 (above)
cause execution of the command to
terminate. Error 8 is valid if
reading the first portion of a large
record into a small buffer.

CARD READER

Code
2

Meaning
Intervention required.
The virtual reader is in a
NOTREADY condition or
is SPOOLed with the
NOEOF option.
I/O operation was
unsuccessful.
Accompanied by message
029S or 030S.
The number of bytes read
was less than the number
of bytes requested.

CSI
8

12
100

The given storage area
was smaller than the
actual size of the item
read. (This is a
recoverable error; the
number of bytes
corresponding to the size
of the buffer have been
read.)
End of file.
No virtual reader defined
at address X'OOC'.
Accompanied by message
28.

108
112

Device is not open.
Device is busy.

Note: All errors except 8 (above)
cause execution of the command to
terminate. Error 8 is valid if
reading the first portion of a large
record into a small buffer.

Code
2
3
13

System Action: The current task is
terminated abnormally with an abend
code of 001 if the message is from
module CSISCT or CSISER. The
current task is terminated abnormally
with an abend code of 038 if the message
is from module CSIXCP.
User Response: Look up the error code
in the table below (for 'CSISCT' and
'CSISER' messages only) to find the
correct message and possible cause of
the error.

ALL DEVICES
Code

307S

Output error 'nnn' on 'ddname'
Explanation: If the prefix on the
message number is 'CSISCT,' GCS
issued this message because an
OUTPUT error was encountered (1) by
an as CLOSE macro, or (2) by an as
CHECK or PUT macro when a
SYNADAF (error analysis) routine had
not been specified by the user. The
error code in the message identifies the
specific error. For further information,
look up the error code in the table in
the 'User Response' section below.

Meaning
A unit exception occurred.
A record with an incorrect
length was detected.
A permanent I/O error
occurred.

254

Meaning
BSAM was called with an
unposted ECB specified.

DISK OUTPUT
Code
2
4

5
7

If the message prefix is 'CSISER,' this
message was built by the simulation
routine for the SYNADAF (error
analysis) macro; it was issued by a
user SYNAD routine. The error code in
the message identifies the specific error.
For further information, look up the
error code in the table in the 'User
Response' section below.

If the prefix is 'CSIXCP,' then an
unrecoverable error occurred while
writing to the disk named in the
message. The error code may be one of
the following:

13
14

Meaning
The virtual storage address is
zero.
The first character mode was
invalid.
The second character mode
was invalid.
An attempt was made to skip
over an un wri tten
variable-length item.
The number of bytes was not
specified.
The fixed/variable flag was
not F or V.
The disk is either not
accessed or it a read-only
disk.
The disk is full.
The number of bytes to be
written is not integrally
divisible by the number of
records to be written.
The length of this item is not
the same as the previous
item.

Group Control System (GCS) Messages

513

CSI
16

17
18
20

21
22

25
26

The fixed/variable flag is not
the same as that of the
previous record.
A variable-length item is
greater than 65,535 bytes.
The number of items is
greater than 1 for a
variable-length file.
An invalid character was
detected in the filename.
An in valid character was
detected in the filetype.
Virtual storage capacity has
been exceeded.
Insufficient virtual storage is
available.
Requested item number is
negative, or item number plus
number of items exceeds file
system capacity.

100
108
112

OPEN error 'nn' on 'ddname'

308E

Explanation: An error occurred during
an 08 OPEN.
System Action: The task ends
abnormally with an abend code of 013.
The DCBFLG8 OPEN bit is not turned
on and the DCB is not initialized.

PRINTER

User Response: Using the error code
table below and the ddname displayed in
the message, check the associated
FILEDEF command and DCB macro for
invalid or missing DCB options.

Code

3
4

100

Meaning
The buffer size is too large.
Channel 12 was sensed
(virtual 3211-type printers
only).
Channel 9 was sensed (virtual
3211-type printers only).
Intervention required. The
device is in a NOTREADY
condition. Accompanied by
message 3468.
I/O operation was
unsuccessful. Accompanied
by message 0298 or 0308.
No virtual printer defined at
address X'OOE'. Accompanied
by message 0288.

Code
2

Meaning
Intervention required. The
virtual punch is in a
NOTREADY condition.
Accompanied by message
3468.
I/O operation was
unsuccessful. Accompanied
by message 0298 or 0308.

VM/SP System Messages and Codes

Meaning

Invalid D80RG specified.
Only P8 is supported.

A default FILEDEF for the
'ddname' displayed in the
message was issued. The
default FILEDEF failed.

RECFM does not agree with
the format of the existing file.
One RECFM is F and the
other is V.

No LRECL OR BLK8IZE
value was specified in the
DCB or FCB, and the file
does not exist.

(1) The DCB BLK81ZE is not
a correct multiple of the DCB
LRECL, or
(2) the DCB specifies writing
blocked output, but only
unblocked records are
permitted on the I/O device
(i.e. reader).

CARD PUNCH

514

No virtual punch defined at
address X'OOD'. Accompanied
by message 0288.
. Device is not open.
Device is busy.

CSI
6

(1) RECFM is fixed and
LRECL does not agree with
the record length of the
existing file, or
(2) RECFM is variable length
and LRECL is not 4 bytes
greater than the record
length of the existing file, or
(3) BLKSIZE is not a multiple
ofLRECL.

There is insufficient storage
available to process the
OPEN macro instruction.

The OPEN macro instruction
was issued for a file allocated
to a virtual unit record
device that has not been
defined. Either define the
device, or allocate the file to
a different device.

The OPEN macro instruction
was issued for a file allocated
to a virtual unit record
device that already has an
open file on it. Make sure
that the first file is closed
before the second is opened,
or allocate the file to a
different device.
Invalid OPEN option
specified. Valid options:
INPUT, OUTPUT, and
UPDAT. DISP is ignored.

An invalid device was
specified. I/O is supported for
disk, dummy, printer, punch~
and reader.

INPUT or UPDAT option was
specified, but the DCB did
not specify a MACRF of GET
or READ.

OUTPUT option was
specified, but the DCB did
not specify a MACRF of PUT
or WRITE.

(1) The LRECL value was

greater than the maximum
allowed, which is 32,760 bytes
for fixed-length logical
records, or 32,752 bytes + 4
bytes for the record
descriptor word (RDW) for
variable-length records, or
(2) LRECL = X was specified.

I/O option 'UPDATE' is
invalid for a file found on a
read-only extension. Output
file with DISP = MOD means
update, so it may not exist on
a read-only extension.

(1) The BLKSIZE value was

greater than the maximum
allowed (32,760 bytes for
fixed-length logical records;
32,752 bytes + 4 bytes for the
block descriptor word (BDW)
for variable-length records),
or
(2) The BLKSIZE value was
less than the minimum value
for variable-length logical
records (8 bytes).
Only CMS formatted disk I/O
is supported. OS or DOS
formatted disk I/O is not
supported.

OPEN error 'nn' on 'ddname'

308W

Explanation: An error occurred during
an as OPEN.
I

System Action: The DCBFLGS OPEN
bit is not turned on and the DCB is not
initialized.
User Response: Using the error code
table below and the ddname displayed in
the message, check the associated
FILEDEF command and DCB macro for
invalid or missing DeB options.
Code

Meaning
The INPUT option was
specified, but the associated
file does not exist.

Group 9ontrol System (GCS) Messages

515

CSI
309E

CLOSE error 'nn' on 'ddname'

User Response: Reissue the DLBL
command with a valid data set name.

Explanation: An error occurred during
an OS CLOSE.
312R
System Action: The task ends
abnormally with an abend code of 014.

Explanation: The system expects you
to enter VSAM data set volume
specifications because you specified the
MULT option of the DLBL command.

User Response: Check the error code
and ddname displayed in the message
with the table below, and make the
appropriate changes.
Code
I

310R

The unit record device
that the file was allocated
to was not opened.
There is insufficient
storage available to
process the CLOSE macro
instruction.
An invalid device was
specified. I/O is
supported for disk,
dummy, printer, punch,
and reader.

User Response: Use the REPLY
command to supply the requested
information.

Invalid data set name
Explanation: An invalid VSAM data
set name was specified in the DLBL
command line.
System Action: RC = 24.
No action is taken on the command and
system status is not changed.

516

User Response: Enter data set volume
specifications using the REPLY
command. The data may be entered on
one line separated by commas, or may
be entered on separate lines. The final
comma at the end of the line is optional
and may be omitted. The data entered
is the filemode for each disk. Do not
repeat the filemode specified in the
command line.

Enter data set name:

System Action: The command waits
for a response.

31lE

System Action: Execution of the
command is delayed until you respond
to the specification request. If a null
line is the first response, an error
message (CSIDLB021E) is displayed and
the DLBL command has no effect.
Otherwise, a null response after one or
more lines of data signifies the end of
the specifications.

Meaning

Explanation: A DLBL command was
entered with the? or DSN? operand.
The command requires that a VSAM
data set name be entered.

VM/SP System Messages and Codes

Enter volume specifications:

313E

Invalid ddname

~ddname'

Explanation: The ddname specified in
the DLBL command is invalid.
System Action: RC = 24.
No action is taken on the command, and
system status is not changed.
User Response: Reissue the DLBL
command with a valid ddname. The
ddname may not be more than 7
characters long.

CSI
3141

Maximum number of disk entries
recorded

to the DLBL definitions in effect. If the
message prefix was 'CSIVIP', the task is
terminated with an abend code of 37.

Explanation: The DLBL command just
entered specified the maximum number
of disks allowed for a multivolume
VSAM data set.
System Action: Execution of the
command is terminated; the data set
definition is stored.

User Response: Reissue the ACCESS
and DLBL commands using a disk
formatted for use with VSAM data sets.

3171

Explanation: The DLBL for the job
catalog has been cleared and is no
longer active.

User Response: None.

System Action: If the job catalog is
cleared, all other definitions flagged as
using the job catalog are no longer
flagged as such. This message can be
the result of a DLBL * CLEAR or DLBL
IJSYSUC CLEAR.

Catalog DDNAME 'ddname' not
found

315E

Job catalog DLBL cleared

Explanation: The user catalog
'ddname' referenced by the CAT option
has not been defined by a previous
DLBL command.

User Response: None.
System Action: Execution of the
command is terminated. The definition
does not take effect.

3181

User Response: Either:
1.

Explanation: The DLBL for the master
catalog has been cleared and is no
longer active.

Reissue the command specifying the
CAT option with a previously
defined ddname; or

System Action: The message can be
the result of a DLBL * CLEAR or DLBL
IJSYSCT CLEAR.

Issue a DLBL command for the user
catalog ddname and then reissue the
DLBL command for the data set you
have defined.

User Response: None.

319S
316E

mode disk is in CMS format;
Invalid for VSAM dataset.
Explanation: The DLBL command that
was issued included the DSN operand,
indicating that the dataset is in VSAM
format. But the disk identified in the
DLBL command is in CMS format.
Note that references to the disk in the
DLBL command include not only the
disk mode in the command line but also
the mode in the MULT specifications.
System Action: The command or
program is terminated with no change

Master catalog DLBL cleared

Unexpected error code nn on vdev
Explanation: An error occurred during
EXCP processing for a VSAM data set.
The error code indicates the type of
error that occurred.
System Action: Execution of the
current task is terminated with an
abend code of 039.
User Response: Check the error code
displayed in the message with the table
below, and make the appropriate
changes.

Group Control System (GCS) Messages

517

CSI
Code
5

320E

Meaning

322E

No Active Disk Table
(ADT) was found.
The disk is in neither OS
nor DOS format.

Explanation: SET SYSNAME was
issued for GCSBAM or GCSVSAM but
no new system name was specified.
System Action: RC = 24.
No action is taken on the command, and
system status is not changed.

Error during FILEDEF CLEAR
processing, DCB(s) not closed.
Explanation: A "FILEDEF 'DD'
CLEAR" or "FILEDEF * CLEAR" was
issued before the corresponding DCB(s)
was closed.

User Response: Reissue the command
specifying a new system name.

323E
System Action: RC = 40.
For "FILEDEF 'DD' CLEAR" the
command terminates and the system
status is not changed. If the "FILEDEF
* CLEAR" was issued, then all
non-permanent FILEDEF entries with
closed DCB's will be cleared.

System Action: RC = 24.
No action is taken on the command, and
system status is not changed.
User Response: Reissue the command
specifying all required parameters.

324S
Saved system name 'sysname'
invalid. Only GCSVSAM or
GCSBAM allowed.

Parameter missing after
SYSNAME
Explanation: SET SYSNAME was
issued without any other parameters.

User Response: Issue a QUERY
FILEDEF command to display all
FILEDEFs in effect. Close the
associated DCB(s) and reissue the
command.

321E

New system name missing after
name

VM Size (size) cannot exceed
sysname start address (vstor)

System Action: RC = 24.
No action is taken on the command, and
system status is not changed.

Explanation: The user's virtual
machine storage size as currently
defined is such that the named system
(when loaded) would overlay part of the
user's virtual storage. This could have
occurred in either of the following ways:
(1) The named system was saved below
the user's current virtual machine size,
or
(2) The named system was saved at an
appropriate address, but the user's
current virtual machine storage size is
so large that it would be partially
overlaid by the named system.

User Response: Reissue the command
using GCSBAM or GCSVSAM as the
SYSNAME.

System Action: The task which was in
control at the time of the error ends
abnormally with abend code of 036.

Explanation: An attempt was made,
using the SET command, to change a
SYSNAME that is not supported by
GCS. The BAM (GCSBAM) and VSAM
(GCSVSAM) saved systems are the only
saved systems that can be manipulated
via the SET command.

User Response: Either:

518

VM/SP System Messages and Codes

CSI
1.

325E

Contact the system programmer,
who must create a new copy of the
named VSAM or BAM saved system
at an address that is high enough
not to conflict with any virtual
machine size being used with VSAM
processing; or

327E

Explanation: The call to VSE/VSAM
results in an error code indicating that
an error in your program may have
caused an error in processing.

Enter CP mode and define a smaller
virtual machine storage size for this
VSAM user so his virtual storage is
not overlaid by the named system,
and then re-IPL GCS and re-execute
the program.

System Action: The current task ends
abnormally with an abend code of 035.
User Response: You may have issued
an ACCESS command after a DLBL
command, in which case you must
reissue the DLBL command. Otherwise,
consult the VSE/VSAM documentation,
correct the error, and re-execute the
program.

Number of VSAM exit routines
has exceeded maximum of 128.
Unable to continue.
Explanation: The number of exit
routines for VSAM data sets (both
active and inactive) has exceeded the
maximum of 128 allowed for this virtual
machine.

329E

System Action: The active task is
terminated with an abend code of 03A.

System Action: The current task ends
abnormally with an abend code of 035.
User Response: Consult the
VSE/VSAM documentation, correct the
error, and re-execute the program.

OPEN error on 'ddname': Possible
volume error. See VSE/VSAl\1
documentation for OPEN error
code code.
Explanation: The call to VSE/VSAM
results in an error code indicating that
a problem could exist with the volume
on which the file resides.
System Action: The current task ends
abnormally with an abend code of 035.
User Response: Consult the
VSE/VSAM documentation, correct the
error, and re-execute the program.

OPEN error on 'ddname': Possible
catalog error. See VSE/VSAM
documentation for OPEN error
code code.
Explanation: The call to VSE/VSAM
results in an error code indicating that
an error exists in the specified catalog.

User Response: Reduce the number of
exit routines for VSAM data sets and
re-execute the program.

326E

OPEN error on 'ddname': Possible
user programming error. See
VSE/VSAM documentation for
OPEN error code code

330E

OPEN error on 'ddname': Possible
system error. See VSE/VSAM
documentation fdr OPEN error
code code.
Explanation: The call to VSE/VSAM
results in an error code indicating that
there is a serious error in GCS support
ofVSAM.
System Action: The current task ends
abnormally with an abend code of 035.

Group Control System (GCS) Messages

519

CSI
System Action: The current task ends
abnormally with an abend code of 035.

User Response: Consult the
VSE/VSAM documentation, correct the
error, and re-execute the program.

33lE

CLOSE error on 'ddname':
Possible user programming error.
See VSE/VSAM documentation
for CLOSE error code code.

User Response: Consult the
VSE/VSAM documentation, correct the
error, and re-execute the program.

334E

Explanation: The call to VSE/VSAM
results in an error code indicating that
an error in your program may have
caused an error in processing.

Explanation: The call to VSE/VSAM
results in an error code indicating that
there is a serious error in GCS VSAM
support.

System Action: The current task ends
abnormally with an abend code of 035.

User Response: Consult the
VSE/VSAM documentation, correct the
error, and re-execute the program.

332E

CLOSE error on 'ddname':
Possible system error. See
VSE/VSAM documentation for
CLOSE error code code.

User Response: Consult the
VSE/VSAM documentation, correct the
error, and re-execute the program.

335S

Explanation: The call to VSE/VSAM
results in an error code indicating that
there is a serious error in GCS support
ofVSAM.

System Action: The current task ends
abnormally with an abend code of 039.

User Response: Consult the
VSE/VSAM documentation, correct the
error, and re-execute the program.

Error in request macro
processing: Possible user
programming error. See
VSE/VSAM error code code.
Return code code.
Explanation: The call to VSE/VSAM
results in an error code indicating that
an error in your program may have
caused an error in processing.

Internal error during VSAM
processing: namel name2
function(s) not supported
Explanation: An internal error was
detected in the GCS code that supports
VSAM.

System Action: The current task ends
abnormally with an abend code of 035.

333E

Error in request macro
processing: Possible system error.
See VSE/VSAM error code code.
Return code code.

User Response: Contact IBM support
personnel.

336S

Internal error during VSAM
processing: Illegal use of SVC 11
Explanation: An internal error was
detected in the GCS code that supports
VSAM.
System Action: The current task ends
abnormally with an abend code of 039.
User Response: Contact IBM support
personnel.

520

VM/SP System Messages and CodeR

(

CSI
337S

338S

Internal error during VSAM
processing: Unsupported SVC sue
(Hex xx) called from ustor

340S

Explanation: An internal error was
detected in the GCS code that supports
VSAM.

Explanation: An internal error was
detected in the GCS code that supports
VSAl\1.

System Action: The current task ends
abnormally with an abend code of 039.

User Response: Contact IBlvI support
personnel.

User Response: Contact IBM support
personnel.

Internal error during VSAM
processing: Invalid form of sve
sue (Hex xx) called from ustor

341S

System Action: The current task ends
abnormally with an abend code of 039.

System Action: The current task ends
abnormally with a abend code of 039.

User Response: Contact IBM support
personnel.

User Response: Contact IBM support
personnel.
342S
Internal error during VSAM
processing: Unsupported function
function of SVC sue (Hex xx) called
from ustor
Explanation: An internal error was
detected in the GCS code that supports
VSAM.
System Action: The current task ends
abnormally with an abend code of 039.
User Response: Contact IBM support
personnel.

Internal error during VSAM
processing: Phase name not found
Explanation: An internal error was
detected in the GCS code that supports
VSAM.

Explanation: An internal error was
detected in the GCS code that supports
VSAM.

339S

Internal error during VSAM
processing: Unsupported form of
name macro

Internal error during VSAM
processing: Unexpected error code
'nn' on udeu
Explanation: An internal error was
detected in the GCS code that supports
VSAM.
System Action: The current task ends
abnormally with an abend code of 039.
User Response: Check the error code
with the table below to determine the
error, and contact IBM support
personnel.
Code
1

3
4
7

Meaning
No CCW address from
CCB
Unsupported device
Invalid CCW
No console CCW

Group Control System (GCS) Messages

521

CSI
343S

Internal error during VSAM
processing: Invalid device class
devclass for devtype

System Action: If the user's SYNAD
exit was specified in the DCB, it will be
executed. Otherwise, message 306S or
307S is issued and the task is
abnormally terminated with abend code
001.

Explanation: An internal error was
detected in the GCS code that supports
VSAM.

User Response: READY the specified
device.

System Action: The current task ends
abnormally with a abend code of 039.
User Response: Contact IBM support
personneL

3441

347R

Explanation: VSE/VSAM is waiting
for a response from the terminal
operator.

VSAM IDUMP taken date time
Explanation: VSE/VSAM has initiated
a dump for a potential problem
situation.

System Action: The requesting task
waits for a response.
User Response: VSE/VSAM indicated
the nature of the requested data in a
previous message. Use the REPLY
command to provide the requested data.

System Action: A dump is taken and
processing continues.
User Response: Consult VSE/VSAM
manuals for information relative to
IDUMPs.

3451

No option specified
Explanation: The indicated option was
entered in an incomplete form on the
DLBL command.
System Action: RC = 24.
Execution of the command is
terminated. The system status remains
the same.
User Response: Reissue the command
specifying the required data for the
option.

346S

Intervention required on device
vdev
Explanation: The specified device
cannot perform the requested I/O
operation because it is in a NOTREADY
condition.

522

VM/SP System Messages and Codes

Enter response:

348E

Open error nn
Explanation: An error occurred during
OS OPEN macro processing. A ddname
is not specified because of the nature of
the error.
System Action: The task is terminated
abnormally with an abend code of 013.
User Response: Check the error code
displayed in the message, and make the
appropriate changes.
Code
14

Meaning
An address that was
specified by the user was
invalid. Or, the DEB
address in the DCB was
invalid.

CSI
349E

Close error 'nn'

351E

Explanation: An error occurred during
an OS CLOSE. A ddname is not
specified because of the nature of the
error.

Explanation: The VSAM system names
cannot be changed because VSAM has
already been initialized. At least one
VSAM macro has been issued since the
last lPL, and VSAM may be in use.
VSAM system names can be changed
only before VSAM is initialized.

System Action: The task ends
abnormally with an abend code of 014.
User Response: Check the error code
displayed in the message in the table
below, and make the appropriate
changes.
Code
2

System Action: Execution of the SET
command is terminated. System status
is unchanged.
User Response: If you wish to change
the system names for VSAM, re-lPL
GCS and issue the SET command before
starting any VSAM programs.

Meaning
(1) A CLOSE macro
instruction was issued,
and an address that was
specified by the user was
invalid (possibly the
DCB address); or

400T

(2) the DEB address in
the DCB is invalid. This
can occur if the DCB
DEB address is
maliciously changed, or if
two tasks are sharing the
same DCB, and the task
that closes the DCB is
not the task that opened
the DCB.

350S

System Action: The GCS system halts
by loading a disabled wait state PSW.
Execution of the command is
terminated.
User Response: Contact your system
support personnel, or re-lPL the names
system and try the operation again.

4011

System Action: The current task is
ended abnormally with an abend code of
036.
User Response: VT AM is not installed
on your system, or it has not been
installed correctly. Contact your system
support personnel.

Program Exception code occurred
at vstor in system routine routine.
Re-IPL sysname.
Explanation: The specified hardware
exception occurred in a GCS system
routine.

Internal error during VT AM
processing: Module 'module' not
found.
Explanation: The module that handles
VTAM Control Block Manipulation
requests could not be found.

System name not changed.
VSAM already initialized.

Directory error encountered
during initialization of the IUCV
environment
Explanation: An lUCY error occurred
while the system was trying to initialize
the virtual machine's lUCY
environment. No lUCY functions can
be performed. The most likely cause for
this error message is that CP was
unable to read the virtual machine
directory.
System Action: The system
terminates.

Group Control System (GCS) Messages

523

CSI
User Response: Have the system
checked for hardware errors.

4021

indicates the type of IUCV error
encountered. The PMX performs this
RETRY operation up to 10 times, or
until the connection is successfully
established.

A GETMAIN error occurred while
trying to obtain storage for the
sysname IUCV Path Table.

System Action: The PMX waits 15
seconds and then tries to establish the
lUCY connection again. This RETRY
process is repeated up to 10 times, or
until an lUCY connection is
established. If all 10 attempts fail, the
PMX terminates.

Explanation: The virtual machine's
lUCY environment could not be
initialized because of a GETMAIN
failure. No lUCY functions can be
performed.

User Response: Wait for 15 seconds
and see if the next attempt fails, or
terminate the PMX and restart it
specifying the userid of the virtual
machine running the programmable
operator facility.

System Action: The system
terminates.
User Response: Determine the cause of
the GETMAIN failure and re-IPL the
named system.

4031

An IUCV CONNECT error
occurred while trying to connect
to CP Signal Services. IPRCODE
= xx.

405E

Explanation: Sent when the PMX
cannot get an lUCY connection with
the programmable operator.

Explanation: The system was unable
to set up a communications path to CP
Signal Services. A non-zero value was
returned in the IPRCODE field of the
lUCY CONNECT parameter list.

System Action: The program
terminates.

System Action: The system
terminates.
User Response: Look up the IPRCODE
specified in the message in the lUCY
return codes table in the VM System
Facilities for Programming, correct the
problem, and then re-IPL the system.

404E

Retry will be attempted in 15
seconds; PROP is not active in
virtual machine use rid
Explanation: The PMX encountered
an lUCY error when attempting to
connect to the virtual machine with the
specified userid. This message is always
preceded by message 405E, which

524

VM/SP System Messages and Codes

An IUCV error occurred while
trying to connect to PROP virtual
machine. IUCVCOM return code
= code

User Response: Use the specified code
to determine the problem and retry.

406E

PMX has abended and will now
take a dump and wait for NCCF
termination. Abend code = xxx
Explanation: Indicates that an abend
occurred in the PMX.
System Action: The PMX enters a
dormant state, waiting for NetView or
NCCF to terminate.
User Response: Use the specified code
along with the dump to determine the
problem.

CSI
407E

User Response: Try the operation
again and/or notify the appropriate
personnel of the condition.

PROP has terminated or abended.
The command is not accepted.
Explanation: Sent when the NetView
or NCCFoperator tries to issue a
programmable operator command after
the programmable operator has been
terminated due to "STOP" or abend; or,
the programmable operator has
QUlESCEd the path for termination
cleanup.

4101

Explanation: Sent to the NetView or
NCCF logical operator, if any, when it
is determined that the programmable
operator has been restarted after an
abend.

System Action: The operation is not
performed.

System Action: None.

User Response: Notify the appropriate
personnel.

User Response: None.

4111
408E

PROP has resumed activity.

PMX has not been started. The
command is not accepted.

PROP has abended.
Explanation: Sent to the NetView or
NCCF logical operator, if any, when it
is determined that the programmable
operator has abended and cannot accept
commands.

Explanation: Sent when the NetView
or NCCF operator tries to issue a
programmable operator command but
the PMX was never invoked.

System Action: None.
System Action: The operation is not
performed.
User Response: Notify the appropriate
personnel. NetView or NCCF must be
CLOSEd and the PMX invoked for a
network management operator to
communicate with the programmable
operator.

409E

User Response: None.

4121

Explanation: Sent to the NetView or
NCCF logical operator, if any, when it
is determined that the programmable
operator has been stopped and cannot
accept commands.

An error occurred while trying to
SEND to PROP virtual machine.
The command is not accepted.
IUCVCOM return code = nnnn
Explanation: Sent when a NetView or
NCCF operator has issued a
programmable operator command but it
cannot be sent to the programmable
operator via lUCY because the message
limit on the path has been exceeded.
System Action: The operation is not
performed.

PROP has stopped.

System Action: None.
User Response: None.

4131

PMX has terminated.
Explanation: Sent to the NetView or
NCCF logical operator, if any, and to
the GCS console when the PMX
terminates.
System Action: None.
User Response: None.

Group Control System (GCS) Messages

525

CSI
414E

Disk 'vdev' not properly formatted
for ACCESS

4181

Explanation: The disk being
ACCESSed has other than a 512, lK, 2K
or 4K block size.

Explanation: Sent to the GCS console
or to the requesting NetView or NCCF
operator when the PMX cannot obtain
the storage required for buffers and
control blocks.

System Action: RC = 16.
Execution of the command is
terminated.

System Action: The requested action
is not performed.

User Response: Reformat the disk
using the FORMAT command under
CMS, specifying a BLOCKSIZE of 512,
lK, 2K, or 4K. Then re-IPL GCS and
reissue the ACCESS command.

User Response: Notify the appropriate
personnel.

419E
415E

Explanation: Sent when a NetView or
NCCF operator tries to issue a
programmable operator command but
the PMX has abended.
System Action: The requested action
is not performed.

System Action: RC = 24.
No action is taken on the command, and
system status is not changed.

User Response: Notify the appropriate
personnel.

User Response: Check the device
address and reissue the command.
Note: A valid address is any address
within the range X'OOl' through X'FFF'.

No device specified
Explanation: The command requires
that you specify a device address or
mode letter.
System Action: RC = 24.
No action is taken on the command, and
system status is not changed.
User Response: Reissue the command,
specifying a valid device address or
mode letter.

526

PMX has abended. The command
is not accepted.

Invalid device address 'vdev'
Explanation: The device address was
not specified correctly, or the device
was not accessed.

416E

Insufficient free storage available.
The command is not accepted.

VM/SP System Messages and Codes

420T

File system error detected.
Virtual address 'vdev'. Reason
code 'nn'.
Explanation: An error has been
detected indicating that the GCS file
system may have become disoriented
with respect to the disk that has the
virtual address 'vdev'. 'nn' is a code
indicating the nature of the error; it
may be one of the following:
Code Meaning
Three problems could have
3
produced this error code: (1) An
error was detected in trying to
read from or write on a disk.
Probably the disk was detached
(via the DETACH command)
without having been released (via
the RELEASE command), or the
disk is an unsupported device.

CSI

The error was detected in module
CSIDIO.
(2) A de allocation was attempted
on a nonallocated disk block.
The error was detected in
CSITRK.
(3) A read/write operation was
attempted to a disk block number
zero. The error was detected in
module CSIDIO.
(1) The cylinder number is not
within the range of user's disk.
Error detected in module CSIDIO;
or
(2) A deallocation was attempted
on a non-allocated disk block.
The errol' was detected in
CSITRK.
The cylinder number received by
the Control Program is not in the
user's range or an attempt was
made to access file record zero.
Error detected in module CSIDIO.
An attempt was made to write on
a read-only disk. Error detected
in module CSIDIO.
Three explanations are possible:

(1) A channel programming error

occurred. The error was detected
in module CSIDIO.
(2) A deallocation was attempted
on a block outside the range of
the disk structure. The error was
detected in module CSITRK.
(3) A read/write operation was
attempted with a byte count of
zero. The error was detected in
module CSIDIO.
13

An I/O error occurred during a
read/write operation to an FB-512
device. The error was detected by
CSIDIO.
A plist error was encountered
during a truncate operation. The
error was detected by CSIERS.
A storage error occurred during a
truncate operation. The error
was detected by CSIERS.
The file or ADT for a truncate
operation was not found. The
error was detected by CSIERS.

The file that was to be truncated
was located on a RIO disk. The
error was detected by CSIERS.
A storage error occurred during a
read/write operation. The error
was detected in module CSIDIO.
An error occurred in module
CSIFNS during a truncate
operation. The error was
detected by CSIERS.
Inconsistent V-Format pointers
were detected during a truncate
operation. The error was
detected in module CSIERS.
No free block is available for
allocation. Error detected in
module CSITRK. You can
recover files from this disk if you
access it as read-only under CMS
and copy the desired files to
another disk.
A parameter list error occurred.
Error detected in module
CSITRK.
The cylinder number received by
the Control Program is not in the
user's range, or an attempt was
made to access file record zero.
Error detected in module
CSITRK.

System Action: The system enters a
disabled wait state. The user file
directory is not updated.
User Response: IPL GCS again and
then reissue the command if data on the
pack is still good. Contact your system
support personnel if the problem
persists.

421S

Disk 'mode (vdev)' is full
Explanation: No more disk space is
available on the minidisk identified in
the message.
System Action: RC = 13.
The last attempted write to the disk is
terminated, and the task that attempted
the write is terminated. The system will

Group Control System (GCS) Messages

527

CSI
attempt to CLOSE any OPEN files
belonging to that task.

4241

'vdev mode' released
Explanation: The specified device was
previously accessed as a read/write disk
with the mode letter indicated in the
message. This device has now been
released since the user has accessed the
same device as a read/write disk with a
different mode letter.

User Response: IPL CMS and try to
create more disk space by deleting
unneeded files. Then re-IPL GCS and
run the program again. See the VM/SP
eMS User's Guide for other ways to
resolve the 'Disk Full' problem.

System Action: Processing continues.
422E

'vdev' already accessed as
Read/Write 'mode' disk
Explanation: You are trying to access
the specified device in read-only mode,
but you have already accessed it in
read/write mode. You cannot have a
disk accessed as both read-only and
read/writ.e, because the read-only file
directory would not reflect any updates
you made until the next time you
accessed the disk.

User Response: None.

4251

Explanation: The disk being accessed
replaces a disk previously accessed as
the same mode letter. The disk being
replaced is released, but it is not
detached.
System Action: Processing continues.

System Action: RC = 36.
No action is taken on the command, and
system status is not changed.
User Response: If you wish to access
the specified device in read-only mode,
first release the disk by issuing the
RELEASE command and then reissue
the ACCESS command.

4231

User Response: None.

4261

Explanation: The disk identified in the
message has been accessed in read-only
mode or in read/write mode, as
indicated. An '-OS' or '-DOS' at the end
of the message means that the disk is
OS or DOS formatted. If the '-OS' or
'-DOS' do not appear, then the disk is in
CMS format.

User Response: None.

528

VM/SP System Messages and Codes

'mode' [-OSI-DOS]

System Action: Processing continues.
User Response: None.

427S

System Action: Processing continues.

'vdev' also
disk

Explanation: The disk identified in the
message is also accessed as the 'mode'
disk. If an '-OS' or '-DOS' appears at
the end of the message, the disk is
formatted as an OS or DOS disk. If
'-OS' or '-DOS' do not appear, then the
disk is formatted as a CMS disk.

mode (vdev) {R/OIR/W} [-OS I-DOS]

Note: A read/write OS or DOS disk can
be written on only by VSAM.

'vdev' replaces 'mode (vdev)'
[-OS I-DOS]

'mode (vdev)' device error
Explanation: An error was
encountered in trying to access the disk,
either because it is an unsupported
device, or because an I/O error occurred
while reading in the master file
directory from the device.

CSI
System Action: RC = 100.
Execution of the command is
terminated. The system status remains
the same unless another disk was
replaced by this access, as indicated by
message CSIACC425I.

429E

Explanation: (1) The files requested
were not on the specified disk. If
another disk was already accessed as
mode 'fm', it is released.
(2) if the disk you are trying to access
contains no files and you are trying to
access it as a read-only disk, then your
disk access has failed. If another disk
was already accessed as mode 'fm', it is
released.

User Response: If this is the first time
that you are using this disk, use the
FORMAT command under CMS to
format it, and then reissue the command
under GCS. If the problem persists,
contact your system support personnel.

428S

System Action: RC = 28.
Execution of the command is
terminated. System status is not
changed.

'mode (udeu), not attached
Explanation: The specified device is
not attached to the virtual machine.
System Action: If the message prefix
is 'CSIACC,' then execution of the
ACCESS command that was issued is
halted. The system status remains the
same unless another disk was replaced
by this access, as indicated by message
CSIACC425I. The return code is 100.

User Response: Check to see that the
fileid is specified correctly, and reissue
the command.

430W

To finish running the GROUP EXEC,
LINK your A-disk from the command
line. You can then finish running the
exec in the normal way.

OS disk - Fileid specified is
ignored
Explanation: The OS or DOS disk
identified in the ACCESS command just
issued has been accessed, but the fileid
provided in the command is not
applicable and has been ignored.

If the message prefix is 'CSIGRP,' your
A-disk is detached. This could have
happened while you were running the
GROUP EXEC, or even before you even
invoked the GROUP EXEC. As a result,
the exec cannot create the GROUP
EXEC file for your GCS system. 'rhe
exec will continue running to allow you
to LINK your A-disk from the command
line.

User Response: To complete an
ACCESS operation, use the CP LINK
command to attach the missing disk to
your virtual machine, or ask the system
operator to attach the disk to your
machine. Then reissue the ACCESS
command.

File 'In It 1m' not found. Disk 'mode
(udeu)' will not be accessed.

System Action: RC = 4.
Execution of the command continues.
User Response: None.

431T

SEVER external interrupt has
occurred on the Signal Services
Path, Re-IPL sysname.
Explanation: An IUCV External
Interrupt has occurred. This interrupt
was a SEVER on the Signal Services
Path.
System Action: The GCS system halts
by loading a disabled wait state PSW.
Execution of the command is
terminated.

Group Control System (GCS) Messages

529

CSI
User Response: Contact your system
programmer to determine why the
IUCVINI SET failed.

User Response: Re-IPL the named
system. Contact your system support
personnel if further failures occur.

432T

Program exception code occurred
at vstor while no task active,
Re-IPL sysname

449E

Explanation: A character string
containing (1) unmatched shift-out (SO)
and shift-in (SI) control characters or (2)
an odd n urn bel' of bytes between the
shift-out (SO) and shift-in (SI)
characters was scanned with OPTIONS
ECMODE in effect.

Explanation: The specified hardware
exception occurred in a GCS system
routine.
System Action: The GCS system halts
by loading a disabled wait state PSW.
Execution of the command is
terminated.

System Action: Execution stops.
User Response: Correct the invalid
character string in the EXEC file.

User Response: Contact your system
support personnel or re-IPL the named
system.
450E
433S

Label GCSGEXIT, the IUCV
Pending Connect exit, was given
control. This is an error.

System Action: The system returns to
the caller of label 'GCSGEXIT' with a
branch to the address contained in
general register 14.

System Action: Execution stops.

User Response: If this message
persists, contact your system
programmer to determine why the GCS
general IUCV exit is getting control.

User Response: Run the EXEC or
macro on its own. More free storage
may be obtained by releasing a disk (to
recover the space used for the file
directory). Alternatively, re-IPL GCS
after defining a larger virtual storage
size for the virtual machine.

IUCVINI SET for GCS failed with
return code nnn. Cannot continue
IPL.
451E
Explanation: A non-zero return code
was received during GCS IPIJ when
trying to establish GCS as an IUCV
user. nnn is the return code that GCS
returns.
System Action: The GCS IPL is
terminated.

530

VM/SP System Messages and Codes

Error 5 running in it, line nn:
Machine storage exhausted
Explanation: While attempting to
interpret a program, the System Product
Interpreter was unable to get the space
needed for its work areas and variables.
This may have occurred because a
program that invoked the System
Product Interpreter has already used up
most of the available storage itself.

Explanation: The label specified as
GCS's general IUCV exit did got
control.

434S

Error 22 running in it, line nn:
Invalid character string

Error 3 running in it, line nn:
Program is unreadable
Explanation: The REXX program
could not be read from the disk. This
problem almost always occurs only
when you are attempting to execute an
EXEC or program from someone else's

CSI
disk for which you have Read/Only
access, while someone with Read/Write
access to the disk has altered the
program so that it no longer exists in
the same place on the disk.

454E

Explanation: The System Product
Interpreter expects a series of WHENs
and an OTHERWISE within a SELECT
statement. This message is issued when
any other instruction is found. This
situ~tion is often caused by forgetting
the DO and END instructions around
the list of instructions following a
WHEN. For example,

System Action: Execution stops.
User Response: Re-access the disk on
which the EXEC or program resides.

452E

Error 4 running fn ft, line nn:
Program interrupted

WRONG

RIGHT

Explanation: The system interrupted
execu tion of your REXX program.
Certain utility modules may force this
interruption if they detect a disastrous
error condition.

Select
Select
When a=b then
When a=b then DO
Say 'A equals B'
Say 'A equals B'
exit
exit
Otherwise nap
end
Otherwise nap
end
end

System Action: Execution stops.

User Response: Look for a problem
with a utility module called in your
EXEC or macro.

User Response: Make the necessary
corrections.

455E
453E

Error 7 running fn ft, line nn:
WHEN or OTHERWISE expected

Error 6 running fn ft, line nn:
Unmatched "j*" or quote
Explanation: The System Product
Interpreter reached the end of the file
(or the end of data in an INTERPRET
statement) without finding the ending
,,* /" for a comment or quote for a literal
string.

Error 8 running fn ft, line nn:
Unexpected THEN or ELSE
Explanation: The System Product
Interpreter has found a THEN or an
ELSE that does not match a
corresponding IF clause. This situation
is often caused by forgetting to put an
END or DO END in the THEN part of a
complex IF THEN ELSE construction.
For example,

System Action: Execution stops.
User Response: Edit the EXEC and
add the closing ,,* /" or quote. You can
also insert a TRACE SCAN statement at
the top of your program and rerun it.
The resulting output should show where
the error exists.

If a=b then do;
Say EQUALS
exit
else
Say NOT EQUALS

If a=b then do;
Say EQUALS
exit
end
else
Say NOT EQUALS

System Action: Execution stops.
User Response: Make the necessary
corrections.

Group Control System (GCS) Messages

531

CSI
456E

Error 9 running In It, line nn:
Unexpected WHEN or
OTHERWISE

458E

Explanation: This message is issued if
vou exceed the limit of 250 levels of
~esting of control structures (DO-END,
IF-THEN-ELSE, etc.).

Explanation: The System Product
Interpreter has found a WHEN or
OTHERWISE instruction outside of a
SELECT construction. You may have
accidentally enclosed the instruction in
a DO END construction by leaving off
an END instruction, or you may have
tried to branch to it with a SIGNAL
statement (which cannot work because
the SELECT is then terminated).

This message could be caused by a
looping INTERPRET instruction, such
as:
line=/INTERPRET line'
INTERPRET line

These lines would loop until they
exceeded the nesting level limit and this
message would be issued. Similarly, a
recursive subroutine that does not
terminate correctly could loop until it
causeR this message.

System Action: Execution stops.
User Response: Make the necessary
corrections.

457E

Error 10 running In It, line nn:
Unexpected or unmatched END
Explanation: The System Product
Interpreter has found more ENDs in
your program than DOs or SELECTs, or
the ENDs were placed so that they did
not match the DOs or SELECTs.
This message can be caused if you try to
signal into the middle of a loop. In this
case, the END will be unexpected
because the previous DO will not have
been executed. Remember also, that
SIGNAL terminates any current loops,
so it can not be used to jump from one
place inside a loop to another.
This message can also be caused if you
place an END immediately after a
THEN OR ELSE construction.
System Action: Execution stops.
User Response: Make the necessary
corrections. You can use "TRACE
Scan" to show the structure of the
program, thereby making it easier to
find your error. Putting the name of the
control variable on ENDs that close
repetitive loops can also help locate this
kind of error.

532

VM/SP System Messages and Codes

Error 11 running In It, line nn:
Control stack full

System Action: Execution stops.
User Response: Make the necessary
corrections.

459E

Error 12 running In It, line nn:
Clause > 500 characters
Explanation: You have exceeded the
limit of 500 characters for the length of
the internal representation of a clause.
If the cause of this message is not
obvious to you, it may be due to a
missing quote, that has caused a number
of lines to be included in one long
string. In this case, the error probably
occurred at the start of the data
included in the clause traceback
(flagged by + + + on the console).

The internal representation of a clause
does not include comments or multiple
blanks that are outside of strings. Note
also that any symbol (name) gains two
characters in length in the internal
representation.
System Action: Execution stops.

CSI
User Response: Make the necessary
corrections.

460E

462E

Explanation: For the System Product
Interpreter, hexadecimal constants may
not have leading or trailing blanks and
may have imbedded blanks at byte
boundaries only. The following are all
valid hexadecimal constants:

Error 13 running fn ft, line nn:
Invalid character in data
Explanation: The System Product
Interpreter found an invalid character
outside of a literal (quoted) string.
Valid characters are:

'13'x
'A3C2 lC34'x
'lDES'x

A-Z a-z 0-9
(Alphamerics)
@ # $ ¢ . ? ! _ (Name Characters)
&*()-+ =-,''';:<,>/

You may have mistyped one of the
digits, for example typing a letter 0
instead of a O. This message can also be
caused if you follow a string by the
I-character symbol X (the name of the
variable X), when the string is not
in tended to be taken as a hexadecimal
specification. In this case, use the
explicit concatenation operator (II) to
concatenate the string to the value of
the symbol.

(Special Characters)
System Action: Execution stops.
User Response: Make the necessary
corrections.

461E

Error 14 running fn ft, line nn:
Incomplete DO/SELECT/IF
Explanation: The System Product
Interpreter has reached the end of the
file (or end of data for an INTERPRET
instruction) and has found that there is
a DO or SELECT without a matching
END, or an IF that is not followed by a
THEN clause.
System Action: Execution stops.
User Response: Make the necessary
corrections. You can use "TRACE
Scan" to show the structure of the
program, thereby making it easier to
find where the missing END should be.
Putting the name of the control variable
on ENDs that close repetitive loops can
also help locate this kind of error.

Error 15 running fn ft, line nn:
Invalid Hex constant

System Action: Execution stops.
User Response: Make the necessary
corrections.

463E

Error 16 running fn ft, line nn:
Label not found
Explanation: The System Product
Interpreter could not find the label
specified by a SIGNAL instruction or a
label matching an enabled condition
when the corresponding (trapped) event
occurred. You may have mistyped the
label or forgotten to include it.
System Action: Execution stops. The
name of the missing label is included in
the error traceback.
User Response: Make the necessary
corrections.

Group Control System (GCS) Messages

533

CSI
464E

Error 21 running In It, line nn:
Invalid data on end of clause

in the expression on any of these
statements. This might be true, for
example, if you entered "EXIT CR"
instead of "EXIT RC."

Explanation: You have followed a
clause, such as SELECT or NOP, by
some data other than a comment.

System Action: Execution stops.

User Response: Make the necessary
corrections.

User Response: Make the necessary
corrections.
467E
465E

Error 17 running In It, line nn:
Unexpected PROCEDURE

Explanation: The System Product
Interpreter found a syntax error in the
DO instruction. You might have used
BY or TO twice, or used BY, TO, or
FOR when you didn't specify a control
variable.

Explanation: The System Product
Interpreter encountered a PROCEDURE
instruction in an invalid position, either
because no internal routines are active,
or because a PROCEDURE instruction
has already been encountered in the
internal routine. This error can be
caused by "dropping through" to an
internal routine, rather than invoking it
with a CALL or a function call.
System Action: Execution stops.
User Response: Make the necessary
corrections.

466E

Error 26 running In It, line nn:
Invalid whole number
Explanation: The System Product
Interpreter found an expression in the
NUMERIC instruction, a parsing
positional pattern, or the right hand
term of the exponentiation (**) operator
that did not evaluate to a whole
number, or was greater than the limit,
for these uses, of 999999999.
This message can also be issued if the
return code passed back from an EXIT
or RETURN instruction (when a REXX
program is called as a command) is not
a whole number or will not fit in a
System/370 register. This error may be
due to mistyping the name of a symbol
so that is is not the name of a variable

534

VM/SP System Messages and Codes

Error 27 running In It, line nn:
Invalid DO syntax

System Action: Execution stops.
User Response: Make the necessary
corrections.

468E

Error 30 running In It, line nn:
Name or String> 250 characters
Explanation: The System Product
Interpreter found a variable or a literal
(quoted) string that is longer than the
limit.
The limit for names is 250 characters,
following any substitutions. A possible
cause of this error is the use of a period
(.) in a name, causing an unexpected
substitution.
The limit for a literal string is 250
characters. This error can be caused by
leaving off an ending quote (or putting a
single quote in a string) because several
clauses may be included in the string.
For example, the string 'don't' should be
written as 'don't' or "don't".
System Action: Execution stops.
User Response: Make the necessary
corrections.

CSI
469E

Error 31 running in it, line nn:
Name starts with number or "."
Explanation: The System Product
Interpreter found a variable whose name
begins with a numeric digit or a period
(.). The REXX language rules do not
allow you to assign a value to a variable
whose name begins with a numeric digit
or a period, because you could then
redefine numeric constantE' which would
be catastrophic.

System Action: Execution stops.
User Response: Make the necessary
corrections.

472E

System Action: Execution stops.
User Response: Rename the variable
correctly. It is best to start a variable
name with an alphabetic character, but
some other characters are allowed.

470E

Error 34 running in it, line nn:
Logical value not 0 or 1

System Action: Execution stops.
User Response: Make the necessary
corrections.

473E

Explanation: The System Product
Interpreter found an expression in an
IF, WHEN, DO WHILE, or DO UNTIL
phrase that did not result in a 0 or 1.
Any value operated on by a logical
operator (--', I, &, or &&) must result in
a 0 or 1. For example, the phrase "If
result then exit rc" will fail if result has
a value other than 0 or 1. Thus, the
phrase would be better written as If
result --, = 0 then exit rc .

Say Enter A, B, or C
should be written as:
Say 'Enter A, B, or C'

User Response: Make the necessary
corrections.

System Action: Execution stops.
User Response: Make the necessary
corrections.

Error 35 running in it, line nn:
Invalid expression
Explanation: The System Product
Interpreter found a grammatical error in
an expression. You might have ended
an expression withan operator, or had
two adjacent operators with no data in
between, or included special characters
(such as operators) in an intended
character expression without enclosing
them in quotes.

System Action: Execution stops.

471E

Error 36 running in it, line nn:
Unmatched "(" in expression

474E

Group Control System (GCS) Messages

535

CSI
System Action: Execution stops.

You may have mistyped a variable
name, or included an arithmetic
operator in a character expression
without putting it in quotes.

User Response: Break up the
expressions by assigning sub-expressions
to temporary variables.

System Action: Execution stops.
Error 40 running in it, line nn:
Incorrect call to routine

475E

Explanation: The System Product
Interpreter encountered an incorrectly
used call to a built-in or external
routine. Some possible causes are:
•

•

User Response: Make the necessary
corrections.

477E

Error 42 running in it, line nn:
Arithmetic overflow/underflow
Explanation: The System Product
Interpreter encountered the result of an
arithmetic operation that required an
exponent greater than the limit of 9
digits (more than 999999999 or less than

you passed invalid data (arguments)
to the routine. This is the most
common possible cause and is
dependent on the actual routine. If
a routine returns a non-zero return
code, the System Product Interpreter
issues this message and passes back
its return code of 20040.

-999999999 ).

This error can occur during evaluation
of an expression (often as a re~ult of
trying to divide a number by 0), or
during the stepping of a DO loop control
variable.

the module invoked was not
compatible with the System Product
Interpreter.

System Action: Execution stops.
If you were not trying to invoke a

routine, you may have a symbol or a
string adjacent to a "(" when you meant
it to be separated by a space or an
operator. This causes it to be seen as a
function call. For example, TIME(4 + 5)
should probably be written as
1'IME*(4 + 5).
System Action: Execution stops.
U s(Jr Response: Make the necessary
corrections.

476E

Error 41 running in it, line nn: Bad
arithmetic conversion
Explanation: The System Product
Interpreter found a term in an
arithmetic expression that was not a
valid number or that had an exponent
outside the allowed range of -999999999
to + 999999999.

536

VMjSP System Messages and Codes

User Response: Make the necessary
corrections.

478E

Error 43 running in it, line nn:
Routine not found
Explanation: The System Product
Interpreter was unable to find a routine
called in your program. You invoked a
function within an expression, or in a
subroutine invoked by CALL, but the
specified label is not in the program, or
is not the name of a built-in function,
and GCS is unable to locate it
externally.
The simplest, and probably most
common, cause of this error is mistyping
the name.
If you were not trying to invoke a

routine, you may have put a symbol or
string adjacent to a H(" when you meant
it to be separated by a space or

CSI
operator. The System Product
Interpreter would see that as a function
invocation. For example, the string
3(4 + 5) should be written as 3*(4 + 5).

System Action: Execution stops.
User Response: Report any occurrence
of this message to your IBM
representative.

System Action: Execution stops.
User Response: Make the necessary
corrections.

479E

482E

Error 19 running In It, line nn:
String or symbol expected
Explanation: The System Product
Interpreter expected a symbol following
the keywords CALL, SIGNAL, SIGNAL
ON, or SIGNAL OFF but none was
found. You may have omitted the string
or symbol, or you may have inserted a
special character (such as a parenthesis)
in it.

System Action: Execution stops.

User Response: Make the necessary
corrections.

User Response: Make the necessary
corrections.
Error 20 running In It, line nn:
Symbol expected

483E
480E

Error 45 running In It, line nn: No
data specified on function
RETURN

Explanation: A REXX program has
been called as a function, but an
attempt is being made to return (by a
RETURN; instruction) without passing
back any data. Similarly, an internal
routine, called as a function, must end
with a RETURN statement specifying
an expression.

System Action: Execution stops.
System Action: Execution stops.
User Response: Make the necessary
corrections.

User Response: Make the necessary
corrections.

Error 24 running In It, line nn:
Invalid TRACE request

484E
481E

Error 49 running In It, line n11,:
Interpreter failure
Explanation: The System Product
Interpreter carries out numerous
internal self-consistency checks. It
issues this message if it encounters a
severe error.

Explanation: The System Product
Interpreter issues this message when:
•

the action specified on a TRACE
instruction, or the argument to the

Group Control System (GCS) Messages

537

CSI
built-in function, starts with a letter
that does not match any valid
alphabetic character options. The
valid options are A, C, E, I, L, N, 0,
R, or S.
•

loops by making them inactive.
Therefore, for example, a LEAVE
instruction in a subroutine cannot
affect a DO loop in the calling routine.
You can cause this message to be issued
if you use the SIGNAL instruction to
transfer control within or into a loop.
A SIGNAL instruction terminates all
active loops, and any ITERATE or
LEAVE instruction issued then would
cause this message to be issued.

an attempt is made to request
"TRACE Scan" when inside any
control construction or while in
interactive debug.

System Action: Execution stops.
User Response: Make the necessary
corrections.

485E

Error 25 running fn ft, line nn:
Invalid sub-keyword found
487E
Explanation: The System Product
Interpreter expected a particular
sub-keyword at this position in an
instruction and something else was
found. For example, the NUMERIC
instruction must be followed by the
sub-keyword DIGITS, FUZZ, or FORM.
If NUMERIC is followed by anything
else, this message is issued.

Error 29 running fn ft, line nn:
Environment name too long
Explanation: The System Product
Interpreter encountered an environment
name specified on an ADDRESS
instruction that is longer than the limit
of 8 characters.
System Action: Execution stops.

System Action: Execution stops.

User Response: Specify the
environment name correctly.

User Response: Make the necessary
corrections.
488E
486E

Error 28 running fn ft, line nn:
Invalid LEAVE or ITERATE
Explanation: The System Product
Interpreter encountered an invalid
LEAVE or ITERATE instruction. The
instruction was invalid because:
•

no loop is active, or

•

the name specified on the
instruction does not match the
control variable of any active loop.

Note that internal routine calls and the
INTERPRET instruction protect DO

538

VM/SP System Messages and Codes

Error 33 running fn ft, line nn:
Invalid expression result
Explanation: The System Product
Interpreter encountered an expression
result that is invalid in its particular
context. The result may be invalid
because an illegal FUZZ or DIGITS
value was used in a NUMERIC
instruction (FUZZ may not become
larger that DIGITS).
System Action: Execution stops.
User Response: Make the necessary
corrections.

CSI
489E

Error 38 running fn ft, line nn:
Invalid template or pattern

492E

Error 32 running fn ft, line nn:
Invalid use of stem
Explanation: The REXX program
attempted to change the value of a
symbol that is a stem. (A stem is that
part of a symbol up to the first period.
You use a stem when you want to affect
all variables beginning with that stem.)
This may be in the UPPER instruction
where the action in this case is
unknown, and therefore in error.
System Action: Execution stops.

System Action: Execution stops.
User Response: Change the program
so that it does not attempt to change the
value of a stem.

User Response: Make the necessary
corrections.

490E

Error 48 running fn ft, line nn:
Failure in system service

493E

Explanation: The System Product
Interpreter halts execution of the
program because some system service
has failed to work correctly.

Error 1 running fn ft: No filename
specified
Explanation: The EXEC command
requires that you specify the name of
the EXEC that you wish to execute.
System Action: Execution stops.

System Action: Execution stops.
User Response: Ensure that your
input is correct and that your program
is working correctly. If the problem
persists, notify your system support
personnel.

491E

Error 18 running fn ft, line nn:
THEN expected
Explanation: All REXX IF and WHEN
clauses must be followed by a THEN
clause. Another clause was found
before a THEN statement was found.
System Action: Execution stops.
User Response: Insert a THEN clause
between the IF or WHEN clause and the
following clause.

User Response: Reissue the command
and specify the filename.

494E

Error 2 running fn ft: File not
found
Explanation: The specified file was not
found on the accessed disks. This
message can be issued when you try to
invoke an EXEC from within another
EXEC.
System Action: Execution stops.
User Response: Access the disk where
the file exists and reissue the command,
or enter the correct name of the EXEC
if you entered it incorrectly.

Group Control System (GCS) Messages

539

CSI
495R

Enter input for EXEC 'execname':

5001

Explanation: 'execname' is the EXEC
name. The System Product interpreter
recognized a request for terminal input.
In most cases, this message will have
been preceded by an informational
message from the EXEC.

Explanation: The GCS extraction
routine was unable to locate the
RSCSV2 extraction routine DMTYEX.
System Action: Processing continues,
and a problem report will be created by
the GCS extraction routine.

System Action: The task executing the
request is suspended until a REPL Y
command is issued.

User Response: Contact the system
programmer to determine why the
routine could not be found.

User Response: Use the REPLY
command to supply the required
information.

5011
496R

Enter DEBUG input for EXEC
'execname':

System Action: Return to IPCS
DUMPSCAN routine with a return code
of 8, which causes the '????????' message
to be displayed.

System Action: The task executing the
request is suspended until a REPL Y
command is issued.

User Response: Contact the system
programmer to determine why the
routine could not be found.

User Response: Use the REPLY
command to supply the required
information.

5021
Insufficient storage for EXEC
interpreter
Explanation: There is insufficient
storage for the System Product
Interpreter to initialize itself.
System Action: Execution is
terminated at the point of the error.
User Response: Redefine storage and
reissue the command.

540

VM/SP System Messages and Codes

Unable to locate type DUMPSCAN
routine 'routine'
Explanation: The GCS DUMPSCAN
routine was unable to locate the RSCS
DUMPSCAN routine DMTYDS.

Explanation: 'execname' is the EXEC
name. The EXEC is being executed in
DEBUG mode. The EXEC awaits the
next user input.

497E

Unable to locate type extraction
routine 'routine'

Task 'taskid' not found
Explanation: One of the DUMPS CAN
subcommands (TACTIVE, TLOADL,
TSAB) has been issued with a taskid
that was not in the task's active
program list or taskid table.
System Action: Return to IPCS/E
DUMPSCAN routine with a return code
of 0, which causes the ready message to
be displayed.
User Response: Reissue the command
with the correct taskid.

CSI
5031

5061

No IUCV path table
Explanation: The IUCV DUMPSCAN
subcommand was entered and the
number of entries in the IUCV path
table was zero.

Explanation: The GCS EXTRACTION
routine was unable to read the dump
information record.
System Action: IPCS will prompt the
user to enter all information for the
problem report.

System Action: Return to IPCS
DUMPSCAN routine with a return code
of 0, which causes the ready message to
be displayed.

User Response: Supply information in
answer to the prompts that appear on
the screen.

User Response: None.

5041

Page 'vstor' not found in dump
507E
Explanation: The virtual address
identified in the message was not found
in the dump. This means it was not
dumped at the time the dump was taken.

Trace formatting routine 'routine'
not found
Explanation: Trace formatting could
not locate the named routine.

System Action: Return to IPCS
DUMPSCAN routine with a return code
of 0, which causes the ready message to
be displayed.

System Action: The record is
displayed or printed in hexadecimal
notation with no formatting done.
User Response: Install the required
TEXT file on an accessed CMS disk and
then re-execute the program.

User Response: None.

5051

Unable to read dump information
record

Taskid 'xxxx' invalid
5081
Explanation: One of the DUMPSCAN
subcommands (TACTIVE, TLOADL,
TSAB) has been issued with a taskid
that is invalid. (Taskid must be from
to x'FFFF')

Explanation: CPTRAP lost the last
part of this record.

System Action: The first portion of
the record is displayed in hexadecimal
notation (unformatted).

System Action: Return to IPCS
DUMPSCAN routine with a return code
of 0, which causes the ready message to
be displayed.
User Response: Reissue the command
with a valid taskid.

The following record was partially
lost:

User Response: None.

5091

ETRACE set ON for event-type(s)
Explanation: This is the normal reply
when external tracing for the specified
event has been enabled for the virtual
machine.
System Action: Processing continues.
User Response: None.

Group Control System (GCS) Messages

541

CSI
5101

ETRACE set ON for event-type(s)
for GROUP

System Action: Command terminates
with no action taken.

Explanation: This is the normal reply
from an ETRACE command that was
issued to set external tracing on for an
event-type for the whole group.

User Response: Use the QUERY
ETRACE command to find the event
types which are in effect for the group.
Then reissue the command without the
event types which were in effect for the
group.

System Action: Exits are scheduled on
all virtual machines in the group to set
ETRACE on for the event-type named in
the message.

5141

All external trace events are
disabled

User Response: None.
Explanation: No external tracing is
being done in this virtual machine.
5111

ETRACE set OFF for event-type(s)
System Action: Processing continues.
Explanation: This is the normal reply
when external tracing for the specified
event has been disabled for the virtual
machine.

User Response: None.

5151
System Action: Processing continues.

Explanation: External tracing for the
specified event type has been enabled
for this virtual machine.

User Response: None.

5121

ETRACE set OFF for event-type(s)
for GROUP
Explanation: This is the normal reply
from an ETRACE command that was
issued to set external tracing off for an
event-type for the whole group.
System Action: Exits are scheduled on
all virtual machines in the group to set
ETRACE off for the event-type named in
the message.

External trace is enabled for
event-type(s)

System Action: Processing continues.
User Response: None.

5161

External trace is enabled for
event-type(s) for GROUP
Explanation: External tracing for the
specified event type was enabled for this
virtual machine by the GROUP operand
ofETRACE.

User Response: None.
System Action: Processing continues.
513E

ETRACE GROUP option is in
effect for event-type(s)
Explanation: An attempt was made by
an unauthorized user to disable external
tracing while the GROUP option was in
effect. The GROUP option overrides the
command.

542

VM/SP System Messages and Codes

User Response: None.

CSI
5171

ITRACE set ON for euent-types(s)

521E

Explanation: This is the normal reply
when the ITRACE command is issued to
enable ITRACE.

Explanation: An unauthorized user
attempted to disable ITRACE while the
ITRACE GROUP option was in effect.
The GROUP option overrides the
command.

System Action: ITRACE is enabled for
the issuing virtual machine.
User Response: None.

5181

System Action: Command terminates
with no action taken. ITRACE remains
in effect for the group.

ITRACE set ON for euent-type(s) for
GROUP

User Response: Use the QUERY
ITRACE command to find the event
types which are in effect for the group.
Then reissue the command without the
event types which were in effect for the
group.

Explanation: This is the normal reply
when an authorized user issues the
ITRACE GROUP command.
System Action: Exits are scheduled on
all virtual machines in the group to
enable ITRACE.

ITRACE GROUP option is in
effect for euent-type(s)

5221

Internal trace is enabled for
event-type(s)

User Response: None.
Explanation: ITRACE is enabled for
this virtual machine.
5191

ITRACE set OFF for euent-type(s)
System Action: Processing continues.
Explanation: This is the normal reply
when the ITRACE has been disabled for
the issuing virtual machine.
System Action: ITRACE is disabled
for the issuing virtual machine.

User Response: None.

5231

User Response: None.

5201

Explanation: ITRACE is enabled for
this virtual machine by the GROUP
operand.

ITRACE set OFF for euent-type(s)
for GROUP
Explanation: This is the normal reply
when an authorized user has issued the
ITRACE END GROUP command,
turning off ITRACE in all virtual
machines in the group.

Internal trace is enabled for
event-type(s) for GROUP

System Action: Processing continues.
User Response: None.

5241

All internal trace events are
disabled

System Action: ITRACE is disabled
for all virtual machines in the group.

Explanation: ITRACE is disabled for
this virtual machine.

User Response: None.

System Action: Processing continues.
User Response: None.

Group Control System (GCS) Messages

543

CSI
525E

Userid is missing or invalid

request involved only areas which
require authorization to dump and
DSS's but the receiver was not
authorized and no DSS's exist.

Explanation: The TO operand was
specified, but the userid was either left
out or is invalid. The userid cannot be
longer than eight characters.

System Action: Command terminates
with no dump taken.

User Response: Reissue the command
specifying a valid range.

User Response: Reissue the command
specifying a valid userid.
5281
Userid 'userid' is not in CP
directory

526E

Explanation: A dump was taken. If the
receiver is an authorized user, the dump
contains the whole virtual machine and
any discontiguous shared segments.
Otherwise the dump contains all key 14
storage (storage belonging to
non-privileged applications) and any
other storage that is not fetch-protected.

Explanation: The dump request was
passed to CP, but the receiving userid,
whether specified or defaulted, was not
found in the CP directory.
System Action: Command terminates
with no dump taken.

System Action: In the case of machine
termination, the termination continues.
In the case of SYSTEM RESTART,
control returns to the virtual machine
at the point where it was interrupted to
issue the CP SYSTEM REST ART
command.

User Response: Reissue the command
specifying a valid userid.

527E

Invalid range
Explanation: One of the following
conditions was encountered:
1.

Hexloc1 greater than hexloc2.

Invalid modifier - only '-', '.', and ':'
are valid.

Invalid byte count.

Address specified which is out of the
range of the virtual machine's
storage.

Dump complete

User Response: None.

529E

Partial dump taken
Explanation: The dump was only
partially completed for one of the
following reasons:
1.

544

Range specified is not a valid
hexadecimal number.

The dump request involved only
areas which require authorization to
dump, but the receiver was not on
the list of authorized users specified
at GCS build time. Or the dump

VM/SP System Messages and Codes

2.
3.

CP experienced an 1/0 error when
attempting to bring a page to be
dumped.
DSS specified, but no DSSs found.
The dump request involved some
protected storage, but the receiver
was not on the list of authorized
users specified at GCS build time.

System Action: Command terminates
with a partial dump taken.
User Response:

CSI
1. If the dump failed because of a CP
I/O error, reissue the command. If
the problem persists, contact the
system programmer.
2. If the dump failed because no DSS
was found, no user action is
required.
3. If the dump failed because the
receiving userid was unauthorized,
reissue the command specifying an
authorized receiver.

530E

Dump failed: I/O error
Explanation: CP encountered an I/O
error while attempting to bring in the
parameter list or the dump address list
passed by the GCS supervisor.
System Action: The command
terminates with no dump taken.
User Response: Reissue the command.
If the failure persists, contact the
system programmer.

Dump failed
Explanation: An error occurred while
attempting to dump the virtual machine.

5331

Virtual Machine load list is empty
Explanation: The GCS DUMPSCAN
subcommand VMLOADL was entered
and the pointer to NUCCBLKS is zero.

System Action: In the case of machine
termination, the termination continues
with no dump taken. In the case of
SYSTEM REST ART, control returns to
the virtual machine at the point it was
interrupted to enter the command, and
no dump is taken.

System Action: Return to the IPCS
DUMPS CAN routine with return code
zero, which causes a ready message to
be displayed.

User Response:

User Response: None.

53lE

532E

Find out from the installation
system programmer if the system is
currently experiencing any spool
problems. If it is, try the dump
again after the problem is fixed.
Also find out from the installation
system programmer if the userid
designated at GCS build time as the
dump receiver is in the CP
directory. If it is not, you cannot
dump via SYSTEM REST ART until
this is corrected.

5341

Explanation: The GCS DUMPSCAN
subcommand TSAB was entered and the
pointer to the task storage anchor block
IS zero.
System Action: Return to the IPCS
DUMPS CAN routine with return code
zero, which causes a ready message to
be displayed.

Dump failed: Spooling error
Explanation: CP ran out of spool
space.
System Action: Command terminates
with no dump taken.
User Response: Reissue the command
when spool space is available.

Task storage anchor block ptr is
zero

User Response: None.

5351

NUCON extension ptr is zero.
Can't find task load list.
Explanation: The GCS DUMPSCAN
subcommand TLOADL was entered and
the pointer to NUCON EXTENSION is
zero.

Group Control System (GCS) Messages

545

CSI
System Action: Return to the IPCS
DUMPSCAN routine with return code
zero, which causes a ready message to·
be displayed.

5391

Explanation: The GCS DUMPSCAN
subcommand TSAB was entered and the
pointer to NUCON EXTENSION is zero.

User Response: None.

5361

System Action: Return to the IPCS
DUMPSCAN routine with return code
zero, which causes a ready message to
be displayed.

Taskid table ptr is zero. Can't
find task load list.
Explanation: The GCS DUMPSCAN
subcommand TLOADL was entered and
the pointer to T ASKID TABLE is zero.
System Action: Return to the IPCS
DUMPSCAN routine with return code
zero, which causes a ready message to
be displayed.

User Response: None.

5401

System Action: Return to the IPCS
DUMPSCAN routine with return code
zero, which causes a ready message to
be displayed.

Task block ptr is zero. Can't find
task load list.
Explanation: The GCS DUMPSCAN
subcommand TLOADL was entered and
the pointer to TASK BLOCK is zero.
System Action: Return to the IPCS
DUMPSCAN routine with return code
zero, which causes a ready message to
be displayed.

User Response: None.

5411

System Action: Return to the IPCS
DUMPSCAN routine with return code
zero, which causes a ready message to
be displayed.

Task load list ptr is zero.
Explanation: The GCS DUMPSCAN
subcommand TLOADL was entered and
the pointer to the TASK load list is
zero.
System Action: Return to the IPCS
DUMPSCAN routine with return code
zero, which causes a ready message to
be displayed.
User Response: None.

Task block ptr is zero. Can't find
task storage anchor block.
Explanation: The GCS DUMPSCAN
subcommand TSAB was entered and the
pointer to TASK BLOCK is zero.

User Response: None.

5381

Taskid table ptr is zero. Can't
find task storage anchor block.
Explanation: The GCS DUMPSCAN
subcommand TSAB was entered and the
pointer to TASKID TABLE is zero.

User Response: None.

5371

NUCON extension ptr is zero.
Can't find task storage anchor
block.

User Response: None.

5421

NUCON extension ptr is zero.
Can't find IUCV path table.
Explanation: The GCS DUMPSCAN
subcommand IUCV was entered and the
pointer to NUCON EXTENSION is zero.
System Action: Return to the IPCS

546

VM/SP System Messages and Codes

CSI
DUMPSCAN routine with return code
zero, which causes a ready message to
be displayed.

5461

Explanation: The GCS DUMPS CAN
subcommand TACTIVE was entered and
the pointer to TASK BLOCK is zero.

User Response: None.

5431

IUCV storage anchor block ptr is
zero. Can't find IUCV path table.

System Action: Return to the IPCS
DUMPSCAN routine with return code
zero, which causes a ready message to
be displayed.

Explanation: The GCS DUMPSCAN
subcommand IUCV was entered and the
pointer to IUCV STORAGE ANCHOR
BLOCK is zero.
System Action: Return to the IPCS
DUMPS CAN routine with return code
zero, which causes a ready message to
be displayed.

Task block pointer is zero. Can't
find state block.

User Response: None.

5471

State block pointer is zero.
Explanation: The GCS DUMPSCAN
subcommand T ACTIVE was entered and
the pointer to STATE BLOCK is zero.

User Response: None.

5441

System Action: Return to the IPCS
DUMPSCAN routine with return code
zero, which causes a ready message to
be displayed.

IUCV path table ptr is zero
Explanation: The GCS DUMPSCAN
subcommand IUCV was entered and the
pointer to PATH TABLE is zero.
System Action: Return to the IPCS
DUMPSCAN routine with return code
zero, which causes a ready message to
be displayed.

User Response: None.

5481

Explanation: The GCS DUMPSCAN
subcommand T ACTIVE was entered and
the pointer to TASKID TABLE is zero.

User Response: None.

5451

System Action: Return to the IPCS
DUMPSCAN routine with return code
zero, which causes a ready message to
be displayed.

NUCON extension ptr is zero.
Can't find state block.
Explanation: The GCS DUMPS CAN
subcommand TACTIVE was entered and
the pointer to NUCON EXTENSION is
zero.

User Response: None.

549E
System Action: Return to the IPCS
DUMPS CAN routine with return code
zero, which causes a ready message to
be displayed.
User Response: None.

Task ID table pointer is zero.
Can't find state block.

productname control block
formatting routine routine not
found
Explanation: The control block
formatting routine for the indicated
product name is not on the user's
accessed disk.

Group Control System (GCS) Messages

547

CSI
System Action: Processing is
terminated.
User Response: Get the indicated
routine's text deck on an accessed disk
and reissue the PRTDUMP command.

550R

Do you wish to format
productname control blocks? Reply
YES or NO.
Explanation: Enter YES if you want to
format control blocks for the indicated
product name; enter NO if you want an
unformatted dump only.
System Action: Control will be passed
to the appropriate formatting routine.
User Response: Enter YES or NO at
your terminal.

548

VM/SP System Messages and Codes

ATS

Transparent Services Access Facility (TSAF) Messages
0011

0031

Initialization is complete. The
service level is 8888.

Termination is in progress
Explanation: TSAF has accepted a
STOP command.

Explanation: This message is issued
when all permanent TSAF tasks have
been started and TSAF is ready for
normal operation. The service level of
the code running is 888B.

System Action: TSAF will terminate
with return code O.
Operator Response: None.

System Action: TSAF is running
normally. It will perform its
communications functions, as well as
dynamic link and collection monitoring.
You can enter commands.

004E

Parameter parameter is not valid
Explanation: You entered a parameter
on a TSAF command that TSAF does
not recognize.

Operator Response: You can now
enter TSAF commands.

System Action: TSAF ignores the
command and is ready for another.
002T

Parameter parameter is a duplicate
or is not valid
Explanation: The argument, parameter,
was passed as a parameter on
invocation of RUNTSAF. The argument
is either invalid o;r it duplicates a
previous argument. TSAF takes any
numeric value to be the number of 1K
internal trace blocks. If you provide
two numeric values, TSAF considers the
second a duplicate, even if its value is
not the same as the first.
System Action: TSAF will terminate
with return code 12.

Operator Response: Correct the
command and re-enter it.

OOSE

A required parameter is missing
Explanation: A required parameter is
missing from the input command.
System Action: TSAF ignores the
command and is ready for another
command.
Operator Response: Enter the correct
command.

Operator Response: Check the TSAF
invocation, and restart TSAF with valid
parameters.

Transparent Services Access Facility (TSAF) Messages

549

ATS
0061

TSAF link statistics and session
accounting records will be
generated

0101

External trace started
Explanation: TSAF processed a SET
ETRACE ON command. Before
receiving this command, external
tracing was off.

Explanation: The TSAF virtual
machine directory contains the account
option.

System Action: CP will write external
trace records to CPTRAP until it
receives a SET ETRACE OFF command.

System Action: TSAF will pass
accounting records to CPo

Note: Nothing will be recorded by
CPTRAP until CPTRAP is also
appropriately enabled.

Operator Response: No action is
required. However, if you do not want
TSAF accounting records, notify the
system administrator so they can delete
the account option from the TSAF
directory en try.

Operator Response: None.

External trace ended

0111
0071

No TSAF link statistics or session
accounting records will be
generated

Explanation: TSAF processed a SET
ETRACE OFF command. Before
recei ving this command, external
tracing was on.

Explanation: The TSAF virtual
machine directory does not contain the
account option.

System Action: CP will not write
external trace records to CPTrap until
it receives a SET ETRACE ON
command.

System Action: None.
Operator Response: No action is
required. If, however, you want
accounting records, notify the system
administrator to add the account option
to the TSAF directory entry.

1,009E

cmd is not a valid TSAF command

Explanation: You entered a command
at the TSAF virtual console that TSAF
does not recognize.
System Action: TSAF ignores the
command and is ready for another.

Operator Response: None.

0131

Trace area size is nnnK
Explanation: TSAF has obtained an
internal trace block of the size specified
by nnn. This size may be either:
•
•

The default value (40K)
The value specified as an input
argument to TSAF, rounded up to a
4K multiple, if necessary.

System Action: None.
Operator Response: Correct the
command and re-enter it.

550

VM/SP System Messages and Codes

Operator Response: None.

ATS
0171

Abend code ccc at aaaaaa

abend modifier, together, identify the
failure point. This message normally
follows message ATSOI8I.

Explanation: TSAF terminated
abnormally, and CMS gave control to
the TSAF abend exit routine. TSAF
gets the abend code, ccc, and the failure
address, aaaaaa, from the PSW at the
time the abend in the ahend work area
(DMSABW) occurred.
System Action: ATSCAB will display
this and other problem determination
messages at the terminal. Then
ATSCAB will take a VMDUMP of the
entire TSAF virtual machine, and issue
a CP SYSTEM RESET command
(assuming that CONCEAL is ON) to
cause CP to re-IPL the CMS system that
the virtual machine is using.

System Action: See message ATSOI7I.
Operator Response: Save this
information and contact your service
representative.

0211

Failure at offset nnnn in module
mmmmmm dated yy.ddd
Explanation: TSAF did a program
check or issued an abend nnnn bytes
into module mmmmmm. yy.ddd is the
year and day the module was compiled.
ATSCAB determines the module name
and compilation date from the
eye-catcher by assuming register 11 or
12 is the base register.

Operator Response: Save this
information and contact your service
representative.

System Action: See message ATSOI7I.
0181

Program old PSW is psw
Explanation: TSAF terminated
abnormally, and CMS gave control to
the TSAF abend exit routine. psw is the
PSW at the time the abend in the abend
work area (DMSABW) occurred. This
message usually follows message
ATSOI7I.
System Action: See message ATSOI7I.
Operator Response: Save this
information and contact your service
representative.

0191

Abend modifier is aaaaaaaaaa
Explanation: TSAF terminated
abnormally, and CMS gave control to
the TSAF abend exit routine. The
module that invoked the abend set the
abend modifier field (CGM __REPORT) to
aaaaaaaaaa. This is alphanumeric
information. The abend code and the

Operator Response: Keep problem
information and contact your service
representative.

0221

Called from offset nnnn in module
mmmmmm dated yy.ddd
Explanation: An instruction nnnn
bytes into module mmmmmm called the
module in which the abend occurred.
yy.ddd is the year and day mmmmmm
was compiled.
If the save area contains a non-zero
backward pointer, TSAF issues this
message after message 0211. TSAF
extracts the name and compilation date
of the calling module from the
eye-catcher.

System Action: See message ATSOI7I.
Operator Response: Keep problem
information and contact your service
representative.

Transparent Services Access Facility (TSAF) Messages

551

ATS
0231

VMDUMP ATSCABn mm/dd/yy
hh:mm:ss taken
Explanation: A VMDUMP of the
entire TSAF virtual machine has been
taken. TSAF specified "ATSCAB
mm/dd/yy hh:mm:ss" as the *dumpid
operand on the VMDUMP command.
On the message identifier:

077E

Note the address of the entry
Issue a TRACE subcommand with
the FROM and FOR count options.

CONFLICTING OPERAND operand
Explanation: This message occurs
when:

n = 1

if the dump was invoked
during the first entry to the
abend exit
if the dump was invoked after
n = 2
ATSCAB2 was entered
mm/dd/yy is the current date
hh:mm:ss is the current time.

Operator Response: Keep problem
information and contact your service
representative.

NON-NUMERIC COUNT
CHARACTER - RETRY

The same option is specified twic"e in
the same command, or

•

The function required by the given
option is incompatible with a
previously specified operand.

System Action: Subcommand
terminates.

System Action: See message ATS0171.

075E

•

User Response: Reissue the command
with the operands correctly specified.

OPERAND MISSING OR
INVALID

078E

Explanation: The count field has
non-numeric characters.

Explanatioll: One of the following
commands caused an error:

System Action: Subcommand
terminates.

•

TRACE subcommand (from module
ATSZTR)

User Response: Correct and reissue
the command.

076E

You specified the SCROLL
operand before a TRACE
subcommand established a
"previous" location.
You specified the FOR operand
with no count value or an
invalid value.
You specified the FROM
operand with no fromloc value
or an invalid value.
You used an unknown operand
or invalid abbreviation.

FORMATTED DATA ENTRY
EXCEEDS MAXIMUM SIZE
Explanation: You used either a
SCROLL or TRACE subcommand with
the FORMAT option, but without the
FOR count option, to display a trace
entry that is too big to fit on the screen.
System Action: CP truncates the
displayed entry and terminates the
subcommand.

•

FDISPLAY subcommand (from
module ATSZTD)
-

User Response: View the entry, by
doing the following:

552

VM/SP System Messages and Codes

You did not specify parameters
on the subcommand.
The LINKCTL operand has no
parameters.

ATS
You specified an unknown
operand or invalid abbreviation.
System Action: Subcommand
terminates.
User Response: Reissue the command
with a valid operand.

0791

0801
•

The trace table start address is
greater than the trace table end
address.

•

The current trace table address is
outside of the trace table.

•

A "FROM" location was not
specified and the trace table
pointers are invalid.

•

The address of the next trace entry
to display is beyond the end of the
dump.

User Response: If you did not specify a
"FROM" location, determine the
location of the trace table, and reissue
the TRACE command with a "FROM"
location specified. If you did specify a
"FROM" location, ignore the message.

Explanation: While trying to display
TSAF trace table entries, IPCS found
that the TSAF trace table pointers in
the dump are invalid. Possible causes of
the error are:

The trace table is not an integer
number of pages.

The address of the next trace entry
to display is less than or equal to
zero.

If you did not specify a "FROM"
location then the subcommand
terminates.

TRACE TABLE POINTERS
INVALID:
START = start END = end
CURRENT = current

•

A page needed for trace table
wrapping is missing from the dump.

•

The data at the end of the table is
not a valid trace entry.

"FROM" LOCATION OUTSIDE
OF TRACE TABLE RANGE:
fromloc
START = start END = end
CURRENT = current
Explanation: The "FROM" location
that you specified on the TRACE
subcommand points to a location
outside of the trace table, while the
trace table pointers appear to be valid.
The CURRENT trace table pointer is
adjusted to point to the start of the last
entry entered in the trace table. The
END trace table pointer is adjusted to
the start of the entry nearest the bottom
of the trace table. You may use any of
the displayed pointer values to return to
the trace table.

System Action: If you specified a
"FROM" location, then the processing
of the subcommand will continue at the
"FROM" location. The display will not
wrap at the trace table start position,
and will stop when one of the following
occurs:

You can start outside of the trace table
and scroll into the trace table. In this
case, trace table wrapping will not
occur unless you restore wrapping by
issuing a TRACE without a FROM
operand, or specify a "FROM" location
within the trace table.

•

System Action: Processing continues.

The specified count (or default
count, if count was not specified)
has been reached.

User Response: Verify the "FROM"
location specified on the TRACE

Transparent Services Access Facility (TSAF) Messages

553

ATS
subcommand, and the trace table
pointers.
•

0841

If the "FROM" location is incorrect,

Explanation: IPCS determined that the
address was to be on a page that does
not exist in the dump. Either the
TRACE subcommand (module ATSZTS)
or the FDISPLA Y subcommand (module
ATSZTD) may issue this message.

reissue the TRACE subcommand
with the correct "FROM" location.
•

08lE

PAGE xxxxxxxx NOT FOUND IN
DUMP

If the trace table pointers are
incorrect and the "FROM" location
is correct, ignore the message.

System Action: The subcommand will
ignore this page and continue
processing if possible.

"FROM" LOCATION NOT A
VALID TRACE ENTRY: fromloc

User Response: None.
Explanation: The "FROM" location
that you specified on the TRACE
subcommand does not point to the
begining of a valid trace entry.

085E

System Action: Subcommand
terminates.

Explanation: The current CPTRAP
entry being formatted is not a valid
TSAF trace entry. This could be caused
if part of the entry was not collected by
CPTRAP.

User Response: Respond to the
message that follows (ATSZTS0921 or
ATSZTS093I).

082E

INVALID TRACE ENTRY FOUND
IN CPTRAP FILE

System Action: The system displays
the entry in dump format without any
formatting.

INVALID TRACE ENTRY FOUND
AT addr

User Response: None.
Explanation: The data at location
addr is not a valid TSAF trace entry.
086E

System Action: Subcommand
terminates.
User Response: Respond to the
message that follows (ATSZTS092I or
ATSZTS093I).

083E

REQUIRED RESOURCES NOT
AVAILABLE
Explanation: An error occurred while
IPCS was getting work buffers to
process the TRACE subcommand.
System Action: Subcommand
terminates.
User Response: None.

554

VM/SP System Messages and Codes

NO TRACE ENTRIES FOUND addr
Explanation: The TRACE subcommand
did not find any trace entries at the
specified address. This is caused by all
or a portion of a trace entry being on a
page that is not present in the dump.
System Action: Subcommand
terminates.
User Response: Enter a TRACE
subcommand with the "FROM" option
to return to the trace table.

ATS
ATTEMPT TO GO BEYOND
STORAGE BOUNDARY

087E

090E

Explanation: You tried to scroll
beyond the dump storage boundaries.
System Action: Subcommand
terminates without displaying any trace
entries.
User Response: Enter a TRACE
subcommand without a SCROLL option.

088E

UNABLE TO UPDATE THE
DUMP WITH THE ABEND PSW
AND REGISTER DATA
Explanation: While extracting
information from the dump, the TSAF
extraction routine detected an error.
This error prevented the routine from
updating the dump with the PSW and
the register information saved when
TSAF detected the abend. One of the
following caused the error:
•

A load map was not appended to the
dump (shown by an earlier message).

•

The IPCS SVC 199 subcodes did not
function properly.

UNABLE TO LOCATE TRACE
TABLE POINTERS
Explanation: One of the following
occurred:
•

IPCS could not find the pointers in
the load map, or the map may be
missing or invalid.

•

The pointers are on a page that is
not present in the dump.

System Action: Subcommand
terminates and trace table wrapping is
disabled.
User Response: Enter a TRACE
subcommand with the "FROM" option.

089E

System Action: The system stops
extracting data from the dump. The
system will prompt you for any
information that it could not extract
from the dump.
User Response: Do not rely on the
following:
•

The register information displayed
when you use the register-related
subcommands of DUMPS CAN

•

The abend PSW and register
information displayed when you
print the dump using the PRTDUMP
facility

•

The information in the symptom
record.

UNABLE TO LOCATE GLOBAL
CONTROL BLOCK (ATSCGM)
Explanation: IPCS did not find the
global control block, ATSCGM. The
map may be missing or invalid.

If possible, determine the location of the
following to debug the problem:

System Action: Subcommand
terminates.

•
•

User Response: Use IPCSMAP to
append a valid TSAF load map to the
dump, and reissue the FDISPLAY
subcommand.

The abend PSW in the dump
Register information in the dump (if
it exists).

You can find the abend PSW and
registers by invoking DUMPSCAN to
view the file.
If the TSAF and CMS load maps were
not appended to the dump then locate
the appropriate TSAF and CMS load
maps and invoke the IPCSMAP

Transparent Services Access Facility (TSAF) Messages

555

ATS
subcommand to append the load maps to .
the dump.

0921

TRACE ENTRY SEARCH
STOPPED AT addrl
TO SEARCH TO LOWER DUMP
ADDRESSES, TRY ADDRESS
addr2
TO SEARCH TO HIGHER DUMP
ADDRESSES, TRY {ADDRESS
addr3 I "SCROLL"}

Once valid load maps have been
appended to the dump, use the MAPN
subcommand to locate the pointer to the
abend PSW and register data. If the
comment on the dump (displayed via the
DUMPID subcommand) began with:

Explanation: This message or message
ATSZTS093I will follow message
ATSZTS081E and ATSZTS082E. IPCS
found an invalid entry, and there are no
valid entries between the invalid entry
address specified in message
ATSZTS081E or ATSZTS082E and the
search end address.

ATSCABI locate the P ABNWA field
ATSCAB2 locate the P ABNW A2 field.
The appropriate field contains the
full word address of the TSAF ABEND
work area. The first 16 fullwords of the
abend work area contain the general
purpose registers. Following the
registers is the abend PSW.

091E

System Action: Subcommand
terminates.
User Response: To continue looking
for a trace entry, do one of the
following:

DATA FIELD OVERLAPS
TRAILER RECORD
Explanation: While using the
FORMAT option, IPCS found that a
trace entry has a data field length
greater than the room for that data
field. For example, a data field may
contain a length value of five bytes, but
only four bytes are available before the
start of the trailer record. A storage
overlay of the trace table could cause
this.

•

Issue the TRACE subcommand with
FROM using addr2 or addr3.

•

Issue the TRACE subcommand with
the SCROLL operand, depending on
the information in the message and
the direction you wish to search.

Note: When searching toward the lower
dump addresses by specifying FROM,
the search proceeds from the FROM
location toward the higher dump
addresses. Therefore, the first entry
found may not be the entry with the
highest address. To view all of the valid
entries that may be present, display the
possible valid entry, and scroll
downward until an invalid trace entry is
reached.

System Action: The system displays
the data field up to the overlap and
displays this message. The system will
display the names of any defined data
fields that it did not process, along with
this message:
EXPECTED DATA NOT IN TRACE
ENTRY
Processing continues.
0931
User Response: Use the DISPLAY
subcommand to check the actual
contents of the trace entry.

POSSIBLE TRACE ENTRY AT
addr
USE THE "FROM" OPERAND TO
DISPLAY THE ENTRY
Explanation: This message or message
ATSZTS0921 will follow message
ATSZTS081E and ATSZTS082E. IPCS

556

VM/SP System Messages and Codes

ATS
found an invalid entry, but found a
possible valid entry at the address in the
message.
System Action: Subcommand
terminates.

display the data structure that the
FDISPLA Y subcommand could not
display.

0961

User Response: Issue a TRACE
subcommand with the address as the
FROM location and a FOR count of 1 to
display the entry.

0941

THE DATA STRUCTURE IS
EMPTY
Explanation: The FDISPLAY
subcommand detected that there are no
entries defined in the data structure
that FDISPLAY was to display.

THE POINTER TO THE
SPECIFIED STRUCTURE IS
ZERO

System Action: The subcommand
terminates.
User Response: None.

Explanation: While trying to locate
the requested data structure, the
FDISPLAY processing modules detected
a pointer that contained the value of
zero. A zeroed pointer value indicates
one of the following:
•
•

300T

Explanation: TSAF was unable to
issue an HNDIUCV SET CMS function
during initialization. nnnn is the
HNDIUCV return code.

The data structure has not been
defined.
The pointer was overlayed.

System Action: TSAF will terminate
with abend code ATS300.

System Action: The subcommand
terminates.

User Response: Restart TSAF. If this
message appears again, contact your
system programmer or service
representative.

User Response: Use the DISPLAY and
LOCATE subcommands to try to locate
and display the data structure.

0951

Error during HNDIUCV SET,
return code = nnnn

THE LINK WAS NOT FOUND IN
THE LINK-TYPE TABLE

302T

Cannot connect to *CRM, it is
already in use

Explanation: You requested a
link-type (e.g. BSC or CTCA) on the
FDIPSLAY LINKCTL subcommand.
However, TSAF could not find the entry
related to the link-type in the link-type
table. The link-type table definition is
necessary to process the FDISPLAY
LINKCTL subcommand.

Explanation: TSAF was unable to
connect to the Collection Resource
Management (*C~M)· system service
because it was already in use by another
virtual machine.

System Action: The subcommand
terminates.

Operator Response: Determine which
virtual machine should be connected to
the *CRM port, and take appropriate
action.

User Response: Use the DISPLAY and
LOCATE subcommands to locate and

System Action: TSAF will terminate
with abend code ATS302.

Transparent Services Access Facility (TSAF) Messages

557

ATS
303T

Cannot connect to *CRM, not
authorized

partition that the collection has not yet
detected.

Explanation: The TSAF virtual
machine was unable to connect to the
Collection Resource Management
(*CRM) system service because it was
not authorized in the VM/SP user
directory.

System Action: The TSAF virtual
machine will reset its collection
management structures and try again to
join an appropriate collection.
Operator Response: No action is
necessary. However, if this happens
repeatedly, it may be because there are
too many systems trying to join the
collection (more than eight systems).
Display the collection table at the agent
node (the node that this one is trying to
join) to determine the current collection
size. If the collection already has the
maximum number of nodes, then delete
the link from this node to the agent to
prevent unnecessary repetitions of the
attempt to join.

System Action: TSAF will terminate
with abend code ATS303.
Operator Response: Make sure you
are running TSAF under the correct
userid. If it is the correct userid, report
the problem to your system programmer.
You must check the TSAF virtual
machine directory for the correct lUCY
authorization (i.e. it must have an
"IUCV *CRM" entry).

304T

Error during CMSIUCV
CONNECT to *CRM, return code
= nnnn

5131

Explanation: This TSAF virtual
machine is trying to join a collection by
sending a request-to-join message to
node nodeid. If nodeid is not busy
(already engaged in a join) it will
become the agent for this TSAF virtual
machine in the join protocol.

Explanation: TSAF was unable to
issue a CMSIUCV CONNECT CMS
function during initialization. nnnn is
the CMSIUCV return code.
System Action: TSAF will terminate
with abend code ATS304.
Operator Response: Restart TSAF. If
this message appears again, contact
your system programmer or service
representative. Use the CMSIUCV
return code to determine what you
should do.

511W

Completion time expired while
attempting a JOIN
Explanation: This TSAF virtual
machine was unable to join a collection
within the expected time. This happens
when several TSAFs are trying to join
each other at the same time or when
there has been a sharp increase in load
coincident with the attempt to join. It
can also happen because of a collection

558

VM/SP System Messages and Codes

Attempting JOIN with node
nodeid as the agent

System Action: A request-to-join
message is sent to nodeid.
Operator Response: None.

514W

JOIN aborted because of
I-message from node nodeid
Explanation: Something changed at
another TSAF virtual machine in the
collection after the join protocol was
started here. This is a normal
occurence when several TSAF virtual
machines are involved.
System Action: The TSAF virtual
machine will reset its collection
management structures and try again to
join an appropriate collection.

ATS
Operator Response: None.

5151

System Action: The TSAF virtual
machine will now try to join an
appropriate collection by issuing
handshake messages on all available
links.

Join in progress for node nodeid
Explanation: This collection has
begun join processing for node nodeid.
This message will be sent to the TSAF
virtual console for each member of the
collection.

Operator Response: None.

5201

System Action: This TSAF virtual
machine adds nodeid to its collection
table and schedules the first join
synchronization. If it is the agent for
nodeid it also sends nodeid the current
collection management structures.

Synchronization is now NORMAL
Explanation: The logical clocks of the
collection are synchronized. This action
takes place periodically and at the
completion of the join protocol. These
messages will be sent to the operator
consoles of all members of the
collection, including the joiner.

Operator Response: None.

5161

Node nodeid cannot join,
maximum collection size has been
reached
Explanation: The collection that
nodeid is trying to join is at its
maximum allowable size.

Operator Response: None.

5211

System Action: Node nodeid is not
allowed to join. The join protocol is
aborted.
Operator Response: Delete the links
between node nodeid and the current
collection to prevent unnecessary
attempts to join.

5181

System Action: The system adjusts the
logical clocks to maintain
synchronization.

RESET: collection now has size 1
Explanation: The TSAF virtual
machine reset its collection
management structures to show it as the
only member of its collection. This is a
normal occurence following an
unsuccessful attempt to join a
collection. It is also one of the stages of
initialization. No sessions are
interrupted by the reset action.
However, new connections cannot be
made to remote resources until their
collection has been joined.

Collection is roughly
synchronized
Explanation: This is the first
synchronization event of the join
protocol. The joining node sets its
logical clock as close as possible to the
clocks of the collection it is joining.
The other nodes send the
synchronization messages that will
allow it to do this. These messages will
be sent to the operator consoles of all
members of the collection, including the
joiner.
System Action: If this TSAF virtual
machine is a current member of the
collection, it sends a synchronization
message to the joiner. If this TSAF
virtual machine is the joiner, it has
received synchronization messages from
a maj ori ty of the collection, and can
now set its logical clock.
Operator Response: None.

Transparent Services Access Facility (TSAF) Messages

559

ATS
530E

nodeid no longer agree with the rest of
the collection or are not available
because nodeid stopped communicating.
If nodeid is still communicating, no
sessions are broken. As long as all
components are still working correctly,
the system repairs the problem by the
join protocol.

Authentication check failed on
message from node nodeid
Explanation: An atomic broadcast
message from node nodeid did not pass
the authentication tests. This happens
after an unsuccessful attempt to join.
However, if this happens frequently,
node nodeid may be experiencing some
trouble.

System Action: Node nodeid is
removed from the collection table. The
system attempts to rejoin the node using
handshake messages.

System Action: The system ignores
.the message.
Operator Response: No action is
necessary. However, if many nodes
show this message referring to node
nodeid more than once, then unless the
problem corrects itself within a few
minutes, restart the TSAF virtual
machine on node nodeid.

I
I
I
I

I
I
53lE

System Action: The system ignores
the message.
Operator Response: No action is
necessary. However, if many nodes
show this message referring to node
nodeid more than once, then unless the
problem corrects itself within a few
minutes, restart the TSAF virtual
machine on node nodeid.

Node nodeid deleted from
collection
Explanation: The node nodeid has
been deleted from the collection table of
each node in the collection. This
happens after a detected partition; the
collection management structures of

560

600S

VM/SP System Messages and Codes

Message with invalid frame type
received: frame-type
Explanation: The routing group has
received a frame with a frame-type value
that it is not prepared to handle.

Timeliness check failed on
message from node nodeid
Explanation: An atomic broadcast
message from node nodeid did not pass
the timeliness tests. This happens after
an unsuccessful attempt to join.
However, if it happens frequently, node
nodeid may be experiencing some
trouble.

5401

Operator Response: None.

System Action: The system discards
the message and continues processing.
Operator Response: Contact your
system programmer or service
representative.

60lE

Frame discarded. Hop-Count limit
reached.
Explanation: Upon receiving a frame
to forward to another node, the routing
group found that the frame exceeds the
forwarding limit.
System Action: The system discards
the frame and continues processing.
Operator Response: Contact your
system programmer or service
representative.

ATS
602E

Incompatible release or service
level detected on link vdev

TSAF storage requirements before the
ADD command can be issued again.
Contact your system programmer to
correct this shortage.

Explanation: The TSAF virtual
machines attempting to communicate
through link vdev are incompatible.
70lE

603E

Explanation: The link driver could not
complete the addition of the new link.
See the message issued before this for
the reason.

Operator Response: Contact your
system programmer.

System Action: The system does not
add the specified link.
Operator Response: Take action
according to the preceding message.

Duplicate node nodeid detected on
link vdev
Explanation: A node with the nodeid
nodeid is already in the collection.

702E

Link unit address vdeu is not valid
Explanation: The specified virtual
device address is not defined for the
virtual machine or is not a valid device
address, that is, it is not a one, two, or
three digit hexadecimal number.

System Action: The link udev is
deleted from the ATSLINKS file, and
you will get message 7131. Further
communication on the link is prevented
until the problem is fixed.

System Action: The system does not
add the specified link.

Operator Response: Contact your
system administrator so that he can
assign a new and unique node id to the
node indicated in the message.

700E

Driver rejected the new link vdev

System Action: The link vdev is
deleted from the ATSLINKS file, and
you will get message 7131. Further
communication on the link is prevented
until the problem is fixed.

Operator Response: Correct the
command and resubmit it, or have the
virtual device attached to this virtual
machine as the specified unit address.

Link-Definition table overflow,
unable to add the new link vdev
703E
Explanation: To add the new link, the
system must expand the Link Definition
Table, but there is not enough storage
available to do so.
System Action: The system does not
accept the defined link.
Operator Response: Deleting one or
more unneeded links may allow a new
one to be added. This condition
indicates that the virtual machine is
severely short of virtual storage.
Whatever is freed by the DELETE
command(s) may be exhausted by other

. Link vdev is not a supported link
type
Explanation: The device at the
specified virtual unit address does not
have the required characteristics for a
CTCA or BSC link.
System Action: The system does not
add the specified link.
Operator Response: Check that the
correct device is attached to the virtual
machine, correct the command if
necessary, and re-enter the command.

Transparent Servjces Access Facility (TSAF) Messages

561

ATS
704E

Record number nnnnnnnn in
AT SLINKS FILE is not valid

7071

Explanation: The link group got a
response from the other end of this link.

Explanation: The record does not have
a correctly specified virtual unit
address.

System Action: The system will use
the new link.

System Action: The system does not
add the link corresponding to the
record.
Operator Response: Examine the
ATSLINKS FILE. Correct the record
that is in error.

7051

Operator Response: None.

7081

Explanation: The link group cannot
get a response from the other end of this
link. The link device may have a
malfunction (in this case, you may have
received other messages). Other reasons
that you may get this message are a
processor went down or the TSAF
virtual machine at the other end of the
link went down.

Operator Response: Examine the link
state and have it fixed if you discover
any malfunctions. If there is no
problem with the link itself, check on
the status of the neighboring system.

: 706W

Received an interrupt on unit
vdev, which is not in the link table
Explanation: An unexpected interrupt
was received from the specified virtual
device. The link device may have a
malfunction.
System Action: The system ignores
the interrupt.
Operator Response: You do not need
to take action unless the condition
persists. If the condition does persist.
notify your system programmer or
service representative.

562

VM/SP System Messages and Codes

An attempt to reset link vdev has
failed
Explanation: The driver tried to
execute a channel program to reset the
link device, but the channel program
did not complete in the expected way.

Link vdev went down

System Action: The system will try to
use the link later.

Link vdev came up

System Action: The system will try to
use the link later.
Operator Response: Check the
hardware units associated with the link.
If you do not find a problem, contact
your system programmer or service
representative.

710E

Unable to allocate control block
for link vdev
Explanation: To add the new link the
system must allocate a Link Control
Block, but there is not enough storage
available to do so.
System Action: The system does not
add the specified link.
Operator Response: Deleting one or
more unneeded links may allow a new
one to be added. This condition
indicates that the virtual machine is
severely short of virtual storage.
Whatever is freed by the DELETE
command(s) may be exhausted by other
TSAF storage requirements before the
ADD command can be issued again.
Contact your system programmer to
correct this shortage.

ATS
711E

Unable to allocate I/O buffer for
the link udeu

System Action: The system continues
operation, and will use the defined link,
despite the error. However, TSAF will
not automatically use the link the next
time TSAF starts.

Explanation: The attempt to add the
link failed.
System Action: The system does not
add the specified link.
Operator Response: Deleting an
unneeded link to allow a new one to be
added would not work in this case. This
condition indicates that the virtual
machine is severely short of virtual
storage. Contact your system
programmer to correct this shortage.

712E

Operator Response: Contact your
system programmer. You will have to
add the new link's definition manually
to ATSLINKS FILE AI.

716E

Explanation: An internal TSAF or
CMS error occurred, which prevented
TSAF from removing the unit as an
active link.

Link unit address vdev is a
duplicate

System Action: The system does not
accept the delete request.

Explanation: A link that uses this
virtual unit address has already been
added.

Operator Response: Retry the
command. If the retry does not work,
inform the system programmer. The
iink's definition can later be deleted
from the file ATSLINKS FILE
manually. If the link must be removed
immediately, detach it from the virtual
machine. Then, when you stop TSAF,
edit ATSLINKS FILE to remove the
link, and restart TSAF.

System Action: The system does not
add the link.
Operator Response: Delete the other
link, or correct the command and
re-en ter it.

7131

Link udeu deleted
Explanation: The link that you
specified has been deleted.

717E

System Action: The system deletes the
link.
Operator Response: None

715E

Driver rejected the request to
delete link udeu

Failed to add the definition of link
udeu to ATSLINKSFILE AI.
Return code from FSWRITE was
nnnn.
Explanation: The system could not
modify the definition file, ATSLINKS
FILE, as specified by the ADD LINK
command.

Unable to retrieve sense bits from
unit udev, CSW is csw
Explanation: Following an I/O error,
the link driver tried to issue a Sense I/O
channel command to the link device.
However, the link driver did not get the
expected sense bits.
System Action: The system continues
operation, but the TSAF virtual
machines may partition the collection
since the link may not be usable.
Operator Response: Contact your
system programmer or service
representative.

Transparent Services Access Facility (TSAF) Messages

563

ATS
7I8E

Severe 1/0 error on unit vdev,
CSW is csiV
Explanation: The link drive
encountered a severe I/O error on the
specified virtual device. The system
displays the Channel Status Word,
iridicating the error.

7I9W

some sort of file recovery (e.g. restore
from a backup).

721E

Failed to delete the definition of
link vdev from ATSLINKS FILE
AI. Return code from FSWRITE
was nnnn

System Action: The system continues
operation, but the TSAF virtual
machines may partition the collection
since the link may not be usable.

Explanation: While trying to do a
deletion, a write error occurred on the
file that TSAF uses to permanently
record link definitions.

Operator Response: Contact your
system programmer or service
representative.

System Action: The system continues
operation. The system will not use the
defined link, despite the error.
Operator Response: Contact your
system programmer. You must
eventually delete the file or perform
some sort of file recovery (e.g. restore
from a backup).

ATSLINKS FILE not found
Explanation: The file that TSAF uses
to permanently record link definitions
does not exist on the virtual machines's
A-disk.
7221

No links are defined

SystemActi~n:

The system continues
operation, but no link definitions exist.

Explanation: This is a response to the
TSAF QUERY LINK command.

Operator Response: If this is not an
expected condition, contact your system
programmer. The TSAF virtual
machine may be missing the appropriate
LINKS and ACCESSES.

System Action: None.
Operator Response: None.

723E
720E

Failed to delete the definition of
link vdev from ATSLINKS FILE
At. Return code from FSREAD
was nnnn.

Link vdev 110t found
Explanation: This is a response to a
TSAF QUERY or DELETE command.
System Action: None.

Explanation: While trying to do a
deletion, a read error occurred on the
file that TSAF uses to permanently
record link definitions.

Operator Response: None.

7241

Link vdev added
Explanation: This is a response to the
TSAF ADD LINK command.
System Action: The system will now
try to use this link.
Operator Response: None.

564

VM/SP System Messages and Codes

ATS
7941

Sense bits are 'xx'X

798W

Explanation: An I/O error on the link
caused the link driver to do a Sense I/O
to the device.

Explanation: The specified CSW was
not expected as a result of the last I/O
operation.

System Action: The system will try
the I/O again later.

System Action: The system will try
another I/O operation later.

Operator Response: Contact your
system programmer.

7951

Unexpected CSW (csw) for unit
vdeu

Operator Response: Contact your
system programmer.

Retry limit exceeded on unit udeu
7991
Explanation: An I/O error occurred on
the device and the I/O was retried
without success.

Explanation: You will get this message
in response to one of the following:

System Action: The system will try
the I/O again later.
Operator Response: Contact your
system programmer.

7961

Unit udeu is not operational

•

The TSAF ADD LINK command

•

Any time that TSAF receives a "not
operational" indication on an I/O
operation to the specified virtual
device.

System Action: The system will try
another I/O operation later.

Bad 1/0 completion on unit udeu,
CSW is csw
Explanation: The link driver did not
get the expected result.

Operator Response: Check to see that
the device is properly connected to the
system. If all connections are correct
and the system programmer verifies that
the CP system generation is correct,
then the device needs to be repaired.

System Action: The system will try
another I/O operation some time later.
Operator Response: Contact your
system programmer.
888T
7971

Unable to obtain storage for
structure

Unit-check indicated on unit udeu
Explanation: The CSW indicated a
unit check on the specified device.
System Action: The system will try
another I/O operation later.
Operator Response: Contact your
system programmer.

Explanation: The TSAF module that
issued the message has issued a request
to eMS to get storage for the specified
structure, structure. CMS diagnosed an
error on the request. The problem may
have occurred because the TSAF virtual
machine had insufficient virtual
storage.
System Action: TSAF will abend with
code ATS888.
Operator Response: Provide more
storage for the TSAF virtual machine,

Transparent Services Access Facility (TSAF) Messages

565

,,'

ATS
and restart TSAF. If it fails again,
contact your system programmer or
service representative.

890T

U nahle to release storage for
structure
Explanation: The TSAF module that
issued the message has issued a request
to return to CMS the storage for the
specified structure. CMS diagnosed an
error on that request.
System Action: TSAF will abend with
code ATS890.

566

VM/SP System Messages and Codes

Operator Response: Keep the problem
information and contact your system
programmer or service representative.

999T

TSAF system error.
Explanation: The TSAF module that
issued this message encountered a
condition that should not have
occurred.
System Action: TSAF will abend with
code ATS999.
Operator Response: Contact your
system programmer or service
representative.

Other Messages

eMS EDIT Messages
The following messages are issued by the CMS Editor in response to
the EDIT command and its subcommands:

nnn LINE(S) CHANGED fB, nnn LINE(S) TRUNCATED"
Explanation: A CHANGE subcommand caused nnn lines to be
changed and/or nnn lines to be truncated.

Explanation: An automatic save (AUTOSAVE) was just performed on
the file currently being edited.

AVAILABLE STORAGE IS NOW FULL
Explanation: The size of the file cannot be increased. Any attempt to
add lines produces the message NO ROOM. Other commands are
unaffected. Use the FILE subcommand to store what you have already
edited on disk. To continue editing, you may temporarily increase the
size of your virtual machine by issuing the CP command DEFINE, or
split the file into two smaller ones.

EDIT:
Explanation: This message indicates entry to edit mode. During
initialization, if the file identification specified in the EDIT command
is found on disk, this is the first response; otherwise, the file is new
and the message NEW FILE: precedes the message EDIT:. This
message is also displayed:
•
•
•
•

When you enter a null line in edit mode.
When you return from Cl\tlS subset to edit mode.
If verification is on when you enter a null line in input mode.
If verification is on when a SAVE subcommand completes
execution.
Other Messages

567

Other Messages
END ZONE SET TO 72
Explanation: The SERIAL subcommand was issued when the zone
setting was within the serialization field. The end zone is reset to
column 72.

EOF:
Explanation: The line pointer is positioned after the bottom line of
the file or, if the file is empty, after the null line at the top of the file
(subject to the setting of the VERIFY subcommand).

EOF REACHED
Explanation: The number of lines beyond the starting line specified
in a GETFILE subcommand exceeded the end of the indicated file.
The lines from the starting line to the end of the file were inserted in
the file. When verification is on, the last line inserted is displayed at
the terminal.

FILE IS EMPTY
Explanation: An attempt to SAVE or AUTOSAVE a null file was
detected. If the subcommand was FILE, the Editor exits and is erased;
if it was SAVE or AUTOSAVE, control returns to edit mode. In either
case, the file is not stored on your disk.

FILE NOT FOUND
Explanation: The file identification specified in a GETFILE
subcommand was not found on an auxiliary storage device.

GETFILE IS INCOMPLETE
Explanation: The available storage was exceeded while attempting to
execute a GETFILE subcommand. The last line inserted into the file
is displayed at the terminal.

GIVEN STARTING LINE IS BEYOND EOF
Explanation: The starting line specified in a GETFILE subcommand
points beyond the last line of the indicated file.

INPUT:
Explanation: Indicates entry to input mode; lines entered at the
terminal become part of the file.

568

VM/SP System Messages and Codes

Other Messages
INV ALID LINE NUMBER REFERENCE IN STMNT nnnnn
Explanation: This message occurs for VSBASIC files only. The line
number referenced in statement nnnnn is invalid (not numeric). The
old line number is nnnnn. The RENUM subcommand is terminated by
the Editor without renumbering the file. To continue, correct
statement nnnnn and reissue the subcommand.
INV ALID SYNTAX IN STMNT nnnnn
Explanation: This message occurs with VSBASIC files only.
RENUM cannot convert the line number operand in statement nnnnn
because of incorrect language usage. The old line number is nnnnn.
The RENUM subcommand is terminated by the Editor. To continue,
correct the statement in line nnnnn and reissue the command.
INVALID $name PARAMETER LIST
Explanation: The indicated edit macro was invoked with one or more
errors in the subcommand line.
LINE xxxxx REFERENCED IN STMNT nnnnn, NOT FOUND
Explanation: This message occurs for VSBASIC files only. The line
number specified as an operand in statement nnnnn was not found.
The old line number is nnnnn. The RENUM subcommand is
terminated by the Editor. To continue, correct the line number
operand xxxxx in statement nnnnn and reissue the command.
MAXIMUM LINE NUMBER EXCEEDED
Explanation: The RENUM subcommand specified values for "strtno"
and "incrno" that would result in a line number that exceeds 99999 for
VSBASIC files or 99999999 for FREEFORT files. The RENUM
subcommand is terminated by the Editor. To continue, reissue
RENUM with proper strtno and incrno values.
This message is also issued for other serialized files if the line number
exceeds 99999. The file must be reserialized.

NEW FILE:
Explanation: The message is issued during Editor initialization if the
file identified in the EDIT command is not found on· the specified disk.
If no filemode was specified with the EDIT command, CMS searches
only the A-disk and its extensions.

Other Messages

569

Other Messages
NO LINES MOVED
Explanation: The edit macro $MOVE was invoked with number of
lines to be moved equal to O.

NO ROOM
Explanation: An attempt to enter additional lines to a file was
detected after the message A VAILABLE STORAGE IS NOW FULL
was displayed. Any stacked lines are cleared to avoid multiple error
mess~ges or improper subcommand execution sequences. Use the
FILE subcommand to store what you have edited so far on disk. To
continue editing, you must either split the file into two smaller files or
temporarily increase the storage size of your virtual machine via the
CP DEFINE STORAGE command. The maximum virtual storage
permitted is determined by the MSTOR value in your directory entry.

NON-NUMERIC CHARACTER IN LINE NUMBER COLUMNS
Explanation: A nonnumeric character was found in the columns
reserved for line numbers. The line pointer identifies the line in error.
You should correct or delete the line in error.

NOT FOUND"
Explanation: The search operand specified in the ALTER, CHANGE,
FIND, or LOCATE subcommand was not encountered in the delimited
range (current ZONE setting), or before the end of the file was
reached.

OVERFLOW AT STATEMENT nnnnn
Explanation: This message occurs with VSBASIC files only. The
conversion of the line number operand in statement nnnnn would
produce a record exceeding the logical record length. The old line
number is nnnnn. The RENUM subcommand is terminated by the
Editor; to continue, correct the statement at old line number nnnnn
and reissue the subcommand.

READ ERROR - GETFILE IS INCOMPLETE
Explanation: An unrecoverable error was encountered during the
execution of a GET FILE subcommand. The last line inserted into the
file is doisplayed at the terminal.

570

VMjSP System Messages and Codes

Other Messages
RECORD LENGTH OF FILE TOO LARGE
Explanation: The file identification of a GETFILE subcommand
indicates a file with a record length greater than the file being edited.
The GETFILE subcommand is not executed.

RENUM MODULE NOT FOUND
Explanation: The RENUM subcommand requires that tl:ere be a
RENUMmodule on the system disk. The RENUM subcommand is
terminated by the Editor. Your installation system programmer must
place the RENUlVI module on the system disk.

RENUMBER LINES
Explanation:
1.

The line number prompter cannot proceed because there are no
more numbers between the current line number and the line
number of the next line already in the file (that is, they differ by
one). In LINEMODE RIGHT, the user can turn LINEMODE OFF,
issue a SERIAL subcommand, SAVE the file on disk (reserializing
it), and finally turn LINEMODE RIGHT on and continue with the
editing session.

The next line number, 100000000 or 100000, is too large.

If you are editing a VSBASIC or FREEFORT file, you can use the
RENUM subcommand to renumber your file.

RESERIALIZATION SUPPRESSED
Explanation: Reserialization on a SAVE, AUTOSAVE, or FILE
subcommand is suppressed when LINEMODE RIGHT is set so that the
numbers used during the editing session are retained. To reserialize,
repeat the SAVE, AUTOSAVE, or FILE with LINEMODE OFF set.

SAVED (See" _SAVED".)
SERIALIZATION IS INCOMPLETE
Explanation: During the execution of a SAVE, AUTOSAVE, or FILE
subcommand that is serializing a file, the disk becomes full before the
last line is written. The partial file is erased and the user is notified of
the condition.

Other Messages

571

Other Messages
SET NEW FILEMODE, OR ENTER CMS SUBSET AND CLEAR SOME
SPACE
Explanation: During the execution of a SAVE, RENUM,
AUTOSAVE, or FILE subcommand, the disk becomes full before
writing the last line of the file. The Editor erases the partial file. To
continue, either (1) alter the destination of the edit file with the
FMODE subcommand, or (2) enter CMS subset and erase unneeded
files to make more room available.

SET NEW FILEMODE AND RETRY
Explanation: An attempt was made to SAVE, AUTOSAVE, or FILE a
file on a disk that is read-only or not accessed. You may reissue the
subcommand specifying the filemode of a read/write disk; or, if you do
not have a read/write disk active, you may enter the CMS subset
environment by issuing the subcommand CMS, then issue the ACCESS
command to gain access to a disk in read/write status, and then return
to the edit environment by issuing the RETURN command.
If you are using a VSBASIC file and issued a RENUM subcommand,
you must access the disk you specified in read/write status for the
subcommand to operate. The RENUM subcommand is terminated by
the Editor without renumbering the file. To continue, use the FMODE
subcommand to direct the file to a read/write disk and reissue the
RENUM subcommand.

This message is also issued if you use FMODE subcommand specifying
an access-mode letter not in the range A-G, S, Y, or Z, or an
access-mode number that is greater than 5.

SET NEW FILENAME AND RETRY
Explanation: During the execution of a SAVE, AUTOSAVE, or FILE
subcommand, an error occurred while altering the name of the CMS
work file. You can now start recovery procedures, since the Editor
returns to edit mode. The work file remains. It should be erased, and
a different file identification for a subsequent SAVE, AUTOSAVE, or
FILE subcommand should be specified.

STACKED LINES CLEARED
Explanation: Multiple subcommands were detected after a failure to
increase the file size when the Editor had indicated NO ROOM. This
message is also displayed when an abnormal exit from edit mode
occurs (to preserve the eMS command environment from stacked
EDIT subcommands), or when an error is encountered in executing an
edit macro.

572

VM/SP System Messages and Codes

Other Messages
STACKED LINES CLEARED BY $name
Explanation: When the named edit macro (such as $MOVE) is
invoked, any stacked lines are cleared by the macro before its
execution. This message also occurs when an edit macro is issued
when the current line pointer is at the top of the file or the end of the
file. When an edit macro is issued with the current line pointer at any
other point in the file, the message does not occur unless lines are
stacked in the console stack.

STRING NOT FOUND, NO DELETIONS MADE
Explanation: The specified character string has not been found by
the end of the file. No deletions have been made, and the current line
poin ter remains unchanged.

TOF:
Explanation: The current line pointer is positioned at the null line at
the top of the file. This message appears either after the TOP
subcommand has been issued or after any other EDIT subcommand has
positioned the line pointer at the null line at the beginning of the file.

TOO MANY LINES TO MOVE
Explanation: The $MOVE edit macro was invoked with the number
of lines to be moved greater than 25.

TOO MANY LINES TO STACK
Explanation: During initialization, the parameter of the STACK
subcommand implies a storage requirement in excess of that reserved
for the execution of the subcommand. The limit is 25 lines.

TRUNC SET TO 72
Explanation: The SERIAL subcommand was issued and the
truncation column was set within the serialization field. The
truncation column is reset to column 72.

TRUNCATED
Explanation: The current line has exceeded the truncation column.
If verification is on, the truncated line is displayed, followed by the

message INPUT: (if in input mode).

Other Messages

573

Other Messages
WRONG FILE FORMAT FOR LINE MODE RIGHT

Explanation: The LINEMODE RIGHT option is not compatible with
variable-length files or files that have a fixed record length other than
80.

WRONG FILE FORMAT FOR RENUM

Explanation: The filetype of the file you are editing is not VSBASIC
or FREEFORT, or the Editor detected an invalid line number. For
VSBASIC files, the line number must be the first five characters of the
record. For FREEFORT files, the line number must be the first eight
characters of the record. The RENUM subcommand is terminated by
the Editor without renumbering the file. To continue, correct the line
number or filetype and reissue the RENUM subcommand.

WRQNG FILE FORMAT FOR SERIALIZATION

Explanation: The SERIAL subcommand was issued for a
variable-length file or for a file that does not have a fixed record
length of 80.

ZONE ERROR

Explanation: The string specified in a CHANGE subcommand is too
long for the current zone specification. The file is not changed.

Explanation: Same as ?EDIT:, but the input line is not displayed
because the SHORT subcommand is in effect.

Explanation: Same as ?EDIT:, but is displayed when an invalid edit
macro is issued and the SHORT subcommand is in effect.

?EDIT:

Explanation: An unrecognizable EDIT subcommand or invalid
subcommand operand was encountered. The input line is displayed for
inspection. This form is used if the LONG subcommand is in effect.

574

VM/SP System Messages and Codes

Other Messages
DMSBWR170S DISK 'mode (vaddr)' IS FULL
Explanation: eMS issues this message if the output disk becomes full
during execution of a FILE, SAVE, RENUM, or AUTOSAVE
subcommand becomes full. The subcommand is terminated by the
Editor, erases the work file (which is incomplete), and requests the
user to specify a new filemode or make more room on the disk.

DEBUG Messages
The following error messages are issued in the DEBUG environment
by DEBUG subcommands:

INCORRECT DEBUG EXIT
Explanation: For the GO subcommand, this message indicates that
the subcommand was issued without an operand, but an operand was
required because the debug environment was entered by issuing the
DEBUG command.
For the RETURN subcommand, this message indicates that RETURN
was not the proper subcommand to use, because the debug
environment was entered due to a breakpoint, a program or external
interrupt, or an unrecoverable error. To exit from the debug
environment under these circumstances, issue the GO subcommand (no
operand is necessary).

Issued by: GO, RETURN

INV ALID OPERAND
Explanation: For the BREAK subcommand, this message indicates
that the breakpoint identification number specified in the first operand
is not a decimal number between 0 and 15 inclusive, or the second
operand cannot be located in the debug symbol table and is not a valid
hexadecimal number. If the second operand is intended to be a
symbol, a DEFINE subcommand must have been previously issued for
that symbol; if not, the operand must be a valid hexadecimal storage
location.
For the DEFINE subcommand. this message indicates that tpe name
specified in the first operand contains all numeric characters, the
second operand is not a valid hexadecimal number, or the third
operand is not a decimal number between 1 and 56 inclusive.
For the DUMP subcommand, this message is issued if the address
specitJed by the second operand is less than that specified by the first
operand. or if the first or second operands cannot be located in the
debug symbol table and are not valid hexadecimal numbers. If either
operand is intended to be a symhol, a DEFINE subcommand must
Other Messages

575

Other Messages
previously have been issued for that symbol; if not, the operand must
specify a valid hexadecimal location.
For the GO or ORIGIN subcommand, a specified operand cannot be
located in the debug symbol table and is not a valid hexadecimal
number. If the operand is intended to be a symbol, a DEFINE
subcommand must have been previously issued for that symbol; if not,
the operand must specify a valid hexadecimal location.
For the GPR subcommand, the operand(s) specified are not decimal
numbers between 0 and 15 inclusive, or the second operand is less than
the first.
For the SET subcommand, the first operand is not CAW, CSW, PSW,
or GPR, or the first operand is GPR and the second operand is not a
decimal number between 0 and 15 inclusive, or one or more of the
hexinfo operands does not contain hexadecimal information.
For the STORE subcommand, the first operand cahnot be located in
the debug symbol table and is not a valid hexadecimal number, or the
information specified in the second, third, or fourth operands is not in
hexadecimal format. If the first operand is intended to be a symbol, a
DEFINE subcommand must have been previously issued for that
symbol; if not, the operand must specify a valid hexadecimal storage
location.
For the X subcommand, the first operand cannot be located in the
debug symbol table and is not a valid hexadecimal number, or the
second operand is not a decimal number between 1 and 56 inclusive. If
the first operand is intended to be a symbol, it must have been defined
in a previous DEFINE subcommand; otherwise, the operand must
specify a valid hexadecimal number.

Issued by: BREAK, DEFINE, DUMP, GO, GPR, ORIGIN, SET,
STORE,X

INVALID STORAGE ADDRESS
Explanation: For the DEFINE, DUMP, GO, STORE, or X
subcommand, the sum of the current origin and the hexadecimal
location specified in the subcommand is greater than the user's virtual
storage size. If the current origin size is unknown, reset it to the
desired value by issuing the ORIGIN subcommand, and then reissue
the subcommand.
For the GO subcommand, this message may also indicate that the
address at which execution is to begin is not on a halfword boundary
(indicating that an operation code is not located at that address).
For the ORIGIN subcommand, the address specified is greater than the
user's virtual storage size.

576

VM/SP System Messages and Codes

Other Messages
Issued by: DEFINE, DUMP, GO, ORIGIN

INVALID STORAGE REFERENCE
Explanation: The location indicated by the second operand is uneven
(not on a halfword boundary) or the sum of the second operand and
the current origin value is greater than the user's virtual storage size.
If the current origin value is unknown, it may be reset to the desired
value by issuing the ORIGIN subcommand.
Issued by: BREAK

MISSING OPERAND
Explanation: The user did not enter the minimum number of
operands required by the subcommand.
Issued by: BREAK, DEFINE, GPR, ORIGIN, SET, STORE, X

TOO MANY OPERANDS
Explanation: The user entered more operands than the subcommand
required.
Issued by: BREAK, CAW, CSW, DEFINE, GO, GPR, ORIGIN, HX,
PSW, RETURN, SET, STORE, X

16 SYMBOLS ALREADY DEFINED
Explanation: The debug symbol table is full and no new symbols can
be defined until the current definitions are cleared by obtaining a new
copy of CMS. However, an existing symbol can be assigned to a new
storage location by issuing another DEFINE subcommand for that
symbol.
Issued by: DEFINE

Other Messages

577

Other Messages

CMS EXEC Messages
The CMS EXEC interpreter generates two error messages, the descriptions
of which are found in the "Conversational Monitor System (CMS)
Messages" section.

DMSEXCOOIE NO FILENAME SPECIFIED
DMSEXT072E ERROR IN EXEC FILE 'fn', LINE nnn - message

EXEC 2 Messages
The EXEC 2 interpreter generates three error messages, the descriptions of
which are found in the "Conversational Monitor System (CMS) Messages"
section.

DMSEXE085E ERROR IN fn ft fm, LINE nnn -message
DMSEXE175E INVALID EXEC COMMAND
DMSEXE255T INSUFFICIENT STORAGE FOR EXEC INTERPRETER

System Product Interpreter Messages
The System Product Interpreter generates messages DMSREX449E through
DMSREX492E in the CMS environment, and CSIREX449E through
CSIREX492E in the GCS environment. Descriptions of these messages are
found in the "Conversational Monitor System (CMS) Messages" and "Group
Control System (GCS)" secti~ns, respectively.

578

VM/SP System Messages and Codes

Summary of Changes
To obtain editions of this publication that pertain to earlier releases of VM/SP,
you must order using the pseudo number assigned to the specific edition. For:
•
•
•
•

Release
Release
Release
Release

4,
3,
2,
1,

order
order
order
order

STOO-1579
STOO-1353
SQ19-6204
ST19-6204

Summary of Changes to SC19-6204-4 for VMjSP Release 5
Addition of messages from new VM/SP components
Transparent Services Access Facility (TSAF)
TSAF is a new component of VM/SP for Release 5. This is a facility that lets
users connect to and communicate with local or remote virtual machines within a
group of systems. With TSAF, a user can connect to a program by specifying a
name that the program has made known, instead of specifying a userid and nodeid.
All messages that TSAF generates are now contained in this publication. These
messages have an ATS prefix, and they are documented in mixed case wi th
variables in italics.
In addition, this manual contains all TSAF abnormal termination (abend) codes.

Other Additions and Enhancements
Parsing Facility
The eMS parsing facility is a new enhancement for Release 5. This facility parses
and translates command name arguments. It iH important to National Language
Support (NLS) because it lets users enter commands in their own national
language.
A u~er defines command syntax in a special language, the Definition Language for
Command Syntax (DLCS). The parsing facility parses a specified command by
checking whether command arguments arE' specified according to the DLCS
definition for that command.
Defining command syntax in a DLCS file and using the parsing facility has the
fo]]owing advantages:
•

Syntax checking if; unnecessary in programs.
Summary of Changes

579

•

Users can invoke programs in their own national language by modifying the
DLCS file.

All messages that the parsing facility generates are now contained in this
publication. These messages have a DMS prefix and are documented in mixed
case with variables in italics.

CMS Session Services
CMS Session Services is a new enhancement to VMjSP for Release 5. This
enhancement provides the end user with window and virtual screen functions.
When the command SET FULLSCREEN ON Is issued, CMS is in full-screen mode
and appears in a window. This allows a user to enter commands from anywhere
on the physical screen, scroll through data and log data into files. The user can
view messages and other information through windows on the physical screen.
All messages that CMS Session Services generates are now contained in this
publication. These messages have a DMS prefix and are documented in mixed
case with variables in italics.

Enhanced Connectivity Facilities on VM/SP
Enhanced Connectivity Facilities on VMjSP is a new component for VMjSP
Release 5. It is also part of a set of programs that make up IBM Systemj370 to
IBM Personal Computer Enhanced Connectivity Facilities.
This component provides a means for VMjSP to communicate with work stations
(for example, IBM Personal Computers) and a programming interface called the
Server-Requester Programming Interface.
All messages that IBM Systemj370 to IBM Personal Computer Enhanced
Connectivity Facilities generates are now contained in this publication. These
messages have a DMS prefix and are documented in mixed case with variables in
italics.

Installation Messages
The messages that were in the back of the Release 4 VMjSP Installation Guide,
SC24-5237 have been incorporated into this publication for this release.

National Language Support (NLS)
Most of the messages are now documented in mixed case. Variables in these
messages are denoted by italics.

Miscellaneous
Minor usability, editorial, and technical changes have been made throughout this
publication.

580

VMjSP System Messages and Codes

Summary of Changes to SC19-6204-3 for VM/SP Release 4
Split of this Publication
The four message cross-reference listings are now contained in a new VM/SP
Release 4 publication System Messages Cross-Reference, SC24-5264. These
cross-references are:
•
•

Command-to-Message Cross-Reference (formerly Appendix A)
Message Summary Alphamerically by Message Identifier (formerly Appendix
B)

•
•

Message-to-Module Cross-Reference (Appendix C)
Message text-to-Message Identifier Cross-Reference (formerly Appendix D).

Addition of messages from new VM/SP components
Interactive Problem Control System (IPCS)
IPCS is a new component of VM/SP for Release 4. This component provides
VM/SP users with an interactive, online facility for diagnosing and reporting
software failures and for managing problem information and status.
All messages that IPCS generates are now contained in this publication. These
messages have a DMM prefix, and they are documented in upper case (variables in
lower case).

Group Control System (GCS)
GCS is also a new component of VM/SP for Release 4. This component is a virtual
machine supervisor. Like CMS, GCS depends on CP for reliability and
availability. However, unlike CMS, GCS provides a multitasking environment,
whereas CMS supports an execution environment for only one task at a time.
All messages that GCS generates are now contained in this publication. These
messages have a CSI prefix, and they are documented in mixed case (variables in
italics).

Other Additions and Enhancements
Stand-Alone Dump Facility Wait State Codes
The stand-alone dump facility is an enhancement to VM/SP serviceability. This
facility is necessary to dump real storage when VM/SP cannot create a CP abend
dump. The wait state codes provide a communication path from the stand-alone
dump facility to the user.

Case of eMS Messages
Many CMS messages are now documented in mixed case. Variables in these
messages are denoted by italics.
Messages generated in the following command environments are mixed case:
XEDIT, FILELIST, RDRLIST, MACLIST, SENDFILE. and NOTE.

Summary of Changes

581

In addition, messages generated in the following commands are mixed case:
EXECDROP, EXECIO, EXECLOAD, EXECMAP, EXECSTAT j EXECUTE,
EXPAND, PEEK, RECEIVE, and TELL.

Message Variable Improvement
Several message variables have been changed, added, or deleted. The variables are
now more consistent, and they better describe the information that will replace
them.
M~iscellaneous

"VMjSP Restrictions," formerly Appendix E in VM/SP System Messages and
Codes, is contained in Appendix D of V,M/SP Planning Guide and Reference,
8C19-6201.

Minor usability, editorial, and technical changes have been made throughout this
publication.

Summary of Changes to SC19-6204-2 for VMjSP Release 3
PER Command
The PER command allows monitoring of certain events in the user's virtual
machine as they occur during program execution.

eMS Performance Enhancements
The CMS performance enhancements include: LISTFILE and RENAME migration,
reduction of the SCBLOCK look-aside buffer, removal of the CMSSEG segment,
and an enhancement to the GLOBALV command.

SQL/DS Support
CP and CMS changes and enhancements have been included in VM/SP Release 3
to allow SQL/DS to operate on VM/SP without either a guest VSE operating
system or VSE/VSAM. These enhancements are provided in a general manner so
that other applications may take advantage of them.

Nucleus Reduction
The CP resident nucleus has been modified by:
•
•
•
•

making all or part of selected resident modules pageable
constructing new modules from portions of selected resident modules so that
you can delete current modules from the loadlist
eliminating duplicate code in selected resident modules
conditionally assembling AP/MP-only code.

CATCHEK Support
CATCHECK is a new CMS command. The CATCHECK command allows the eMS
VSAM user (with or without DOS set ON) to invoke the VSEjVSAM Catalog
Check Service Aid to verify a complet<.> catalog structure. CATCHECK produces a
print file containing the catalog analysis.

DMSDOS Split

582

VM/SP System Messages and Codes

The DMSDOS module rflceives initial control on all VSE SVC invocations.
Several SVCs have been split from the DMSDOS module and eleven new modules
were created, all residing in the CMSDOS discontiguous shared segment (DCSS).
This was done to improve serviceability and maintainability. DMSDOS invokes
the appropl'iate proeessing routines, and control returns to DMSDOS upon
eompletion.
VM/SP Release 3 supports a new operand for SVCI07, PCEXIT, which returns the
pcexit routine address and save area in register 0 and register 1, respectively.
Also, CMS/DOS now simulates the VSE IDUMP macro. When a program product
issues the VSE IDUMP macro, a dump is generated and sent to a virtual printer.

Assembler Language VSAM Support
CMS supports VSAM macros for use in CMS programs. All of the VSE/VSAM
macros and their options and a subset of the OS/VSAM macros are supported by
CMS.

System Product Interpreter Support
The System Product Interpreter is an interpretive command and macro processor.
It may help you increase productivity with the creation and execution of
EXEC-type command procedures and programs. Its functions are easy to learn and
are written in a high-level language, known as the Restructured Extended
Executor (REXX) language.

Programmable Operator Facility Enhancements
Several enhancements have been added to the Programmable Operator Facility.
Among them are:
•
•
•
•
•

message routing with nicknames
availability enhancements
enhanced text comparison
EXEC action routines
enhancements to message recording and error handling (logging).

Enhancements to the System Product Editor
Enhancements to the System Product Editor provide new or improved support in
the following areas:
•
•
•
•
•
•
•

color and extended highlighting
prefix macros
selective line editing
screen layout control, including vertical screen split
PF key changes
several new functions
modifications t.o miscellaneous existing functions.

3088 Multisystem Communications Unit Support
The 3088 Multisystem Communications Unit interconnects multiple systems using
block multiplexer channels. The 3088 uses an unshared subchannel for each
unique address and is fully compatible with existing channel-to-channel adapter
protocol.

Printer and Tape Support
VM/SP Release ;, includes support for the following printer and tape devices:
Summary of Changes

583

•
•
•
•
•

3262
3800
4245
4250
3430

Printer, Model 5
Printing Subsystem Models 3 and 8
Line Printer
Printer
Magnetic Tape Subsystem.

Miscellaneous
Various minor technical and editorial changes have been made throughout this
publication.

584

VM/SP System Messages and Codes

Glossary of Terms and Abbreviations
This section explains or defines the terms,
acronyms, and abbreviations that appear in this
manual. For a complete list of terms used in VM/SP
refer to the VM/SP Library Guide, Glossary, and
Master Index, GCI9-6207. You may al$o want to
refer to the IBM Vocabulary for Data Processing,
Telecommunications, and Office Systems, GC20-1699.

ACF/VTAM Version 3. Refers to ACF/VTAM
Version 3 for VM/SP, Program No. 5664-280, unless
otherwise noted.

FB-512. The 3310 and the 3370 Direct Access
Storage Devices.

3088. The 3088 Multisystem Communications Unit
(MCU) Models 1 and 2.
3270. Refers to a series of display devices that are
supported as VM/SP terminal display stations. A
specific device type is used only when a distinction
is required between device types.

The use of display terminals applies only to VM/SP
system consoles used in display mode.
Information pertaining to the IBM 3284 or IBM 3286
printers includes any printers used for the display
terminal copy function unless otherwise noted.
3330. The IBM 3330 Disk Storage, Models 1,2, or
11; the IBM 3333 Disk Storage and Control, Models
1 or 11; and the IBM 3350 Direct Access Storage
operating in 3330/3333 Model 1 or 3330/3333 Model
11 compatibility mode.
3370. The IBM 3370 Direct Access Storage Models
AI, A2, Bl, and B2.
3375. The IBM 3375 Direct Access Storage Device.

GAM/SP. The IBM Graphic Access
Method/System Product, Program No. 5668-978.

3422. The IBM 3422 Magnetic Tape Subsystem.
3480. The IBM 3480 Magnetie Tape Subsystem.
370x. The IBM 3704 and IBM 3705
Communications Controllers.

270x. The IBM 2701, 2702, and 2703 Transmission
Control Units or the Integrated Communications
Adapter (ICA) on the Systemi370, Model 135.

3705. The 3705 I and the
noted.

~)705

II, unless otherwise

3800. The IBM Printing Subsystems, Models 1, :3,
and 8. A specific device type is used only when a
distinction is required between device types.
References to the ~1800 Model ~ apply to both
Models :~ and 8 unless otherwi::;e f'xplicitly stat(·d.
The IBM :~800 Model 8 is available onl~T in selected
world trade countries.

G lossar:v of Terms and Abbreviations

585

586

VM/SP System Messages and Codes

Bibliography
Virtual Machine/System Product:
•

CMS Command Reference, SC19-6209

•

CMS for System Programming, SC24-5286

•

CMS Macros and Functions Reference, SC24-5284

•

CP Command Reference, SC19-6211

•

CP for System Programming, SC24-5285

•

Data Areas and Control Block Logic Volume 2 (CMS), LY24-5221

•

Data Areas and Control Block Logic Volume 1 (CP), LY24-5220

•

Group Control System Command and Macro Reference, SC24-5250

•

Installation Guide, SC24-5237

•

Introduction, SC19-6200

•

Operator's Guide, SC19-6202

•

Planning Guide and Reference, SC19-6201

•

System Messages Cross-Reference, SC24-5264

•

System Product Editor Command and Macro Reference, SC24-5221

•

System Product Editor User's Guide, SC24-5220

•

System Product Interpreter Reference, SC24-52::19

•

Transparent Services Access Facility Reference, SC24-5287

Virtual Machine:
•

Diagnosis Guide, L Y24-5241

•

System Facilities for Programming, SC24-5288

•

Running Guest Operating Systems, SC19-6212

Bibliography

587

Others:

588

•

CMS GAM/SP User's Guide, LC33-0126.

•

DOS/ VS Sort/Merge Version 2 Programmer's Guide, SC33-4404.

•

Guide to the DOS/ VSE Assembler, GC33-4024

•

IBM Programmer's Guide to the Server--Requester Programming Interface for
VM/SP, SC24-5291.

•

IBM Virtual Machine/System Product and Stand-Alone Versions:
Input/Output Configuration Program User's Guide and Reference, GC20-1843

•

OS/VS and DOS/VS Analysis Program-I (AP-I) User's Guide, GC26-3855

•

OS/VS, DOS/VSE, VM/370 EREP Messages, GC38-1045

•

OS/ VS Message Library: Mass Storage System (MSS) Message, GC38-1000

•

OS/ VS Utilities Messages, GC38-1005

•

VSE/ Advanced Functions Messages, SC33-6098

•

VSE/ VSAM Messages and Codes, SC24-5146

VM/SP System Messages and Codes

Index

abend
See abnormal termination (abend)
ABENDs
CMS (Conversational Monitor System)
dumps 63
reporting problems 63
CP (Control Program)
cause of 34-62
codes 34-62
collecting information 32
dumps 32
recovery 33
system programmer action 34
GCS (Group Control System)
dumps 69
reporting problems 69
TSAF (Transparent Services Access Facility)
dumps 101
reporting problems 101
abnormal termination (abend)
CMS (Conversational Monitor System)
causes of 64
codes 64-68
dumps 63
module names 64
reporting problems 63
user action 64
CP (Control Program)
cause of 34-62
codes 34-62
collecting information 32
dumps 32
recovery 33
system programmer action 34-62
GCS (Group Control System)
causes of 71
codes 71
dumps 69
module names 71
reporting problems 69
user action 71
TSAF (Transparent Services Access Facility)
causes of 102
codes 102-103
dumps 101
module names 102
reporting problems 101
user action 102
action on CP errors
general user 7
system operator 7

cause of abnormal termination
CMS 64-68
CP 34-62
GCS 71-100
TSAF 102-103
CMS (Conversational Monitor System)
abnormal termination (abend)
causes of 64-68
codes 64
dumps 63
module names 64-68
reporting problems 63
user action 64-68
error messages 233-472
CMS EDIT subcommand messages 567-574
CMS Editor messages 567-574
CMS EXEC messages 578
codes
abend
CMS 64-68
CP 34-62
GCS 71-100
TSAF 1.02-103
wait state
CP 13-22
loader 23-25
stand-alone dump facility 26-31
component code in message identifier 1
Control Program (CP)
abnormal termination (abend)
cause of 34-62
codes 34-62
collecting information 32
dumps 32
recovery 33
system programmer action 34-62
error message numbers 6
error messages 105-231
problem determination 6
general user 7
system operator action 7
return codes 11
wait state codes 1.3-22
Conversational Monitor System (CMS)
abnormal termination (abend)
dumps 63
reporting problems 63
error messages 233-472
CP (Control Program)
See also Control Program (CP)
abnormal termination (abend)
collecting information 32
dumps 32

Index

589

recovery 33
error message numbers 6
error messages 105-231
problem determination 6
general user 7
system operator action
return codes 11
wait state COdElS 13

DDR command return codes 12
pEBUG command error messages 575
debugging abends
CMS 64-68
CP 34-62
GCS 71-100
TSAF 102-103
default setting for message display 5
DIRECT command return codes 10
displaying messages 5, 6
DMCP command 7
dumps
for CMS abend 63
for CP abends 32
for GCS abend 69
for TSAF abend 101

EDIT subcommand messages 567-574
Editor, CMS, messages 567-574
Editor, VMjSP, messages 2,374-390
error messages
CMS 233-472
CMS EXEC interpreter 578
CP 105-231
DEBUG command 575
EXEC 2 interpreter 578
GCS 491-548
IPCS 473-490
System Product Interpreter 363-372, 578
TSAF 549-566
errors, CP, action for
general user 7
system operator 7
EXEC 2 interpreter messages 578

format of messages

590

VMjSP System Messages and Codes

GCS (Group Control System)
abnormal termination (abend)
causes of 71-100
codes 71
dumps 69
module names 71-100
reporting problems 69
user action 71-100
error messages 491-548
Group Control System (GCS)
See also GCS (Group Control System)
abnormal termination (abend)
dumps 69
reporting problems 69
error messages 491-548

identifier, message 1
Interactive Problem Control System (IPCS)
error messages 473-490
return codes 12
IPCS (Interactive Problem Control System)
See also Interactive Problem Control System
(IPCS)
error messages 473-490
return codes 12

Languages, displaying messages in other
loader wait state codes 23-25

message format 1
message identifier
message number
in CP error messages 6
in message identifier
messages
CMS EDIT 374-390, 567-574

CMS EXEC interpreter 578
DEBUG command 575
displaying at terminal 5
displaying in other languages 6
error
CMS 2:33-472
CP ]05-23]
GCS 491-548
IPCS 473-490
TSAF 549-566
EXEC 2 interpreter 578
identifier
syntax conventions 3
System Product Editor 2
System Product Interpreter 363-372, 578
variables used in 3
MNOTES 3
module code in message identifier 1
module names of CMS abends 64-68
module names of GCS abends 71-100
module names of TSAF abends 102-103

normal waits for stand-alone dump facility

other languages

from CMS DDR eommand 12
from CP DIRECT command 10
from IPCS ]2
partial listing 9
sample 11

SET EMSG ON command 5, 7
severity codes in message identifier 1
stand-alone dump wait state codes 26-31
normal waits 30
program execution 28
program generation 26
subcommands
DEBUG messages 575
EDIT messages 567-574
syntax in messages 3
system operator action
CP abends 32
CP errors 7
System Product Editor
See Virtual Machine/System Product (VM/SP)
System Product Editor messages 2, 374-390
System Product Interpreter 363-372, 578
system programmer action on CP abends 34-62

prefix in message identifier 1
problem determination in CP
general user action 7
system operator action 7
punctuation in messages 3

RC
See return codes
recovery from abnormal termination (abend)
CP 33
responses, unnumbered 3
return codes

terminals, displaying messages at 5
termination, abnormal
CMS 64-68
CP 34-62
GCS 71-100
TSAF 102-103
Transparent Services Access Facility (TSAF)
abnormal termination (abend)
causes of 102-103
codes 102
dumps 101
module names 102-103
reporting problems 101
user action 102-103
error messages 549-566
TSAF (Transparent Services Access Facility)
See also Transparent Services Access Facilitv
(TSAF)
.
abnormal termination (abend)
dumps 101
reporting problems 101
error messages 549-566
type code in message identifier 1

Index

591

displaying 5
format 1
unnumbered responses 3
user action on CP errors 7

variables used in messages 3
Virtual Machine/System Product (VM/SP)
messages
displaying 5, 6
format 1
System Product Editor messages 2, 374-390
VMiSP
See Virtual Machine/System Product (VM/SP)
Vl\:l/SP (Virtual Machine/System Product)
messages

592

VM/SP System Messages and Codes

wait state codes
CP 13-22
loader 23-25
stand-alone dump facility 26-31
normal waits 30
program el(:ecution 28
program generation 26

INumerics I
4nxx identifier, messages with

International Business
Machines Corporation
P.O. Box 6
Endicott, New York 13760
File No. S370/4300-39
Printed in U.S.A.

SC 19-6204-4

---------,-

Virtual Machine/System Product
System Messages and Codes
Order No. SC19-6204-4

READER'S
COMMENT
FORM

Is there anything you especially like or dislike about this book? Feel free to
comment on specific errors or omissions, accuracy, organization, or
completeness of this book.
If you use this form to comment on the online HELP facility, please copy the
top line of the HELP screen.
____ Help Information

line

IBM may use or distribute whatever information you supply in any way it believes appropriate without
incurring any obligation to you, and all such information will be considered non confidential.
Note: Do not use this form to report system problems or to request copies of publications. Instead,
contact your IBM representative or the IBM branch office serving you.

Would you like a reply? _YES _NO
Please print your name, company name, and address:

IBM Branch Office serving you:
Thank you for your cooperation. You can either mail this form directly to us or give this
form to an IBM representative who will forward it to us.
\

5019-6204-4

Reader's Comment Form
CUT

OR
FOLD
ALONG

LINE

Please Do Not Staple

Fold and tape

III
BUSINESS REPLY MAIL
FIRST-CLASS MAIL

PERMIT NO. 40

NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES

ARMONK, NY

POSTAGE WILL BE PAID BY ADDRESSEE:

INTERNATIONAL BUSINESS MACHINES CORPORATION
DEPARTMENT GSO
PO BOX 6
ENDICOTT NY 13760-9987

1... 11 .. 11.1 ... 1.11'111 ••• 1.1111.1 •• 1111.1 ••• 111"11
Please Do Not Staple

Fold and tape

---- -',--........-'-- ....--- ---

----- ----.,.

Fold and tape

Virtual Machine/System Product
System Messages and Codes
Order No. SC19-6204-4

READER'S

COMMENT
FORM

line

IBM may use or distribute whatever information you supply in any way it believes appropriate without
incurring any obligation to you, and all such information will be considered nonconfidential.
Note: Do not use this form to report system problems or to request copies of publications. Instead,
contact your IBM representative or the IBM branch office serving you.

Would you like a reply? _YES _NO
Please print your name, company name, and address:

IBM Branch Office serving you:
Thank you for your cooperation. You can either mail this form directly to us or give this
form to an IBM representative who will forward it to us.

SC19-6204-4

Reader's Comment Form
CUT
OR

FOLD
ALONG

LINE

Please Do Not Staple

raid and tape

Fold and tape

II
BUSINESS REPLY MAIL
FIRST-CLASS MAIL

PERMIT NO. 40

NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES

ARMONK, NY

POSTAGE WILL BE PAID BY ADDRESSEE:

----- --- -- -------------_.INTERNATIONAL BUSINESS MACHINES CORPORATION
DEPARTMENT G60
PO BOX 6
ENDICOTT NY 13760-9987

1111111111111111,111,11'1,1,1"1,11,1,,1,1'11111,,,1
Please Do Not Staple

Fold and tape

----------,-

-- --

Fold and tape

Virtual Machine/System Product
System Messages and Codes
Order No. SC19-6204-4

REAUt:H'~

COMMENT
FORM

Is there anything you especially like or dislike about this book? Feel free to
comment on specific errors or omissions, accuracy, organization, or
completeness of' this book.
If you use this form to comment on the online HELP facility, please copy the
top line of the HELP screen.
_ _ _ Help Information

line

IBM may use or distribute whatever information you supply in any way it believes appropriate without
incurring any obligation to you, and all such information will be considered nonconfidential.
Note: Do not use this form to report system problems or to request copies of publications. Instead,
contact your IBM representative or the IBM branch office serving you.

Would you like a reply? _YES _NO
Please print your name, company name, and address:

IBM Branch Office serving you:
Thank you for your cooperation. You can either mail this form directly to us or give this
form to an IBM representative who will forward it to us.

SC19-6204-4

Reader's Comment Form
CUT
OR
FOLD
ALONG

LINE

Please Do Not Staple

Fold and tape

I II
BUSINESS REPLY MAIL
FIRST-CLASS MAIL

PERMIT NO. 40

NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES

ARMONK, NY

POSTAGE WILL BE PAID BY ADDRESSEE:

----- -- ----- ------_.----INTERNATIONAL BUSINESS MACHINES CORPORATION
DEPARTMENT G60
PO BOX 6
ENDICOTT NY 13760-9987

1111111111111111111111111111111111111111111111111111
Please Do Not Staple

Fold and tape

----....---------,-

Fold and tape

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                     : 2010:04:16 17:16:57-08:00
Modify Date                     : 2010:04:17 00:04:07-07:00
Metadata Date                   : 2010:04:17 00:04:07-07:00
Producer                        : Adobe Acrobat 9.31 Paper Capture Plug-in
Format                          : application/pdf
Document ID                     : uuid:54a0539b-02a0-4f9e-8a58-9e86770347ae
Instance ID                     : uuid:636d5601-69ff-45d9-bc74-43798cf9c970
Page Layout                     : SinglePage
Page Mode                       : UseNone
Page Count                      : 609

EXIF Metadata provided by EXIF.tools

SC19 6204 4_VM_SP_System_Messages_and_Codes_Release_5_Dec86 4 VM SP System Messages And Codes Release 5 Dec86

Navigation menu

Versions of this User Manual:

Views

Navigation