SC33 0035 2_DOS_PLI_Transient_Library_Messages_Aug77 2 DOS PLI Transient Library Messages Aug77

SC33-0035-2_DOS_PLI_Transient_Library_Messages_Aug77 SC33-0035-2_DOS_PLI_Transient_Library_Messages_Aug77

User Manual: SC33-0035-2_DOS_PLI_Transient_Library_Messages_Aug77

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

Download
Open PDF In Browser	View PDF

SC33·0035·2
File No. 5360/5370·29

Program Product

DOS
PL/I Transient Library:
Messages
Program Number 5736-LM5
(This program product is available as
part of composite package 5736-PL3)

--..- =:
.....
-- - - _.---------:--=-=~
~-.

-~---

Third Edition (August, 1977)
This edition is a reprint of SC33-0035-1 incorporating
changes released in Technical Newsletters SN33-6120 (dated
June, 1974), SN33-6126 (dated December, 1974), and
SN33-6171 (dated October, 1976).
This edition applies to Version 1, Release 5, Modification 0
of the DOS PL/I Transient Library, Program Product 5736-LM5,
and to any subsequent version, release, and modification.
Information in this pUblication is subject to significant
change. Any such changes will be published in new editions
or technical newsletters. Before using the publication,
consult the latest IBM System/370 Bibliography, GC20-0001,
and the technical newsletters that amend the bibliography,
to learn which edition and technical newsletters are
applicable and current.
Requests for copies of IBM publications should be made to
the IBM branch office that serves you.
Comments may be addressed to IBM Corporation, P.O. Box 50020,
Programming Publishing, San Jose, California 95150. All comments
and suggestions become the property of IBM.

Preface

This publication lists the execution-time messages that can be produced
by the DOS PL/I Transient Library when this library is used during the
execution of a PL/I program compiled by the DOS PL/I Optimizing
Compiler. Most of these messages are accompanied by additional
information intended to illustrate the detected condition and to point
to the appropriate corrective action.
The compile-time(IEL) messages produced by the DOS PL/I Optimizing
Compiler are listed in a separate publication: ~ R1L1 Optimizing
Compiler: nessages, Order No. SC33-002l.

Associated Publications
DOS PL/I Optimizing Compiler:
Specifications,

Order No. GC33-0016

General Information.
Programmer's Guide,
Execution Logic.
Installation,

Order

No~

GC33-0004

Order No. SC33-000a

Order No. 5C33-0019

Order No. SC33-0020

Reference Data...

Order No.. 5X33-600 1

Language Reference ManuaL

Order No. GC33-0005

Availability of Publications
The availability of a publication is indicated by
letter in the order number. The use keys are:
G - General:

5 - Sell:

it~

yse

ke~,

the first

available to users of IBM systems, products, and
services without charge, in quantities to meet their
normal requirements; can also be purchased by anyone
through IBM branch offices.

can be purchased by anyone through IBM branch offices.

iii

Contents

INTRODUCTION • • • • • • • • • •
Format of Execut:on-Time Messages..
Before Calling IBM... • • • •

1
1
2

EXECUTION-TIME

(IB~)

•

"ESSAGES • •

Introduction

Execution-time
file SYSPRINT.
the operator's
action for the
transmitted to
~essages

messages are printed on the device associated wi t.h the
If SYSPRINT is unusable the message will be printed on
console.
However, any message associated with the system
CHECK condition or the COpy or SNAP options will .not be
the operator's console.

are printed at execution time when:

An error occurs for which there is no specific on-condition in
PL/I.
(1 message is printed and the ERROR condition is raised).

An on-condition is raised for which there is no on-unit in the
program and for which the standard system action includes printing
an execution-time message.

Format of ExecutioI!.-time Messages
Execution-time messages have the following format:
message-number - ONCODE=nnnn 'condition-name' CONDITION RAI5ED - text location message
Each message number is of the form IBMnnn, where "IBM" indicates that
the message is a PL/I execution-time message, and "nnn" is the number of
the message.
The final character "I" or "A" indicates to the operator
whether the message is informatory or whether he should take some
action.
The on~code is that for the condition name that follows.
The text
"ONCODE:" and the actual on-code generated by the system only appear
when the message is printed; they are not listed in the message texts in
this publication.
The condition name is the PL/I 'on-condition raised in association
with the exceptional or error condition that caused the message to be
printed.
The condition name and the text "CONDITION RAISED" are not
normally listed in the message texts in this publication, although they
are always included when the message is printed.
The text of the
message may consist of one or two parts,'according to the requirements
of the individual message.
The parts are a fixed part and a variable
part. The fixed part only of each message is given in this publication.
The variable part of a message can be one of the following:
•

a condition name

•

an entry name

•

a file name

according to the requirements of the message.
The nature of the location message wili depend on whether the PL/I
program vas compiled with the GOSTMT option or the NOGOSTMT option.
If
GOSTMT vas specified, the location message vill be as follows:

Introduction

IN STATEMENT nnn AT OFFSET nnnnnn IN PROCEDURE WITH ENTRY entry-name
If NOGOSTMT was specified, the location message will be as follows:
AT OFFSET nnnnnn IN PROCEDURE WITH ENTRY eptry-name
The location messages generated by the system only appear when the
messages are printed; they are not listed in the messa.ge texts in t:his
publication.
An example of an execution-time message in the form in v.hich i.t will
be printed is given below:
IBM0371

ONCODE=0612 'CONVERSION' CONDITION RAISED CONVERSION FRO~
CHARACTER TO BIT ON INPUT AFTER 'TRANSMIT' DETECTED IN
STATEMENT 207 AT OFFSET 004A8C IN PROCEDURE WITH ENTRY PROG1

Before Calling IBM ...
Unless the programmer response for the message specifies otherwise,
before calling IBM for programming support with regard to an executiontime error:
1.

Ensure that the program includes an active ERROR on-unit that
includes the statement:
CALL PLIDUMP('HB');

Run the program again.
If the problem recurs, ensure that the following are available:

Listings of the source program, the object program, and the job
control statements for the execution of the program.

Relevant data sets.

Job stream (job control statements and data) in machine readable
form.

The requirements for problem determination and APAR submission are
given in the programmer's guide for this compiler.

Execution-time (IBM) Messages

IB!0021

INTERRUPT DURING PLII PROGRAM-MANAGEMENT LIBRARY ROUTINE.
PROGRAM TERMINATED
Explanation: An interrupt has occurred during the handling of
a PLII on-condition or error condition in the program
management routine or a routine invoked by it. It indicates
that a disastrous error has occurred during execution of the
program, such as the overwriting of control blocks or sections
of code~ The program is terminated, and if the DUMP option of
the OPTION job control statement is requested for the job, a
dump of the partition is produced by the DOS dump program. The
most common cause of this type of error is the overwriting of
control information by the PLII program. The program may
contain arrays which have exceeded their bounds.
Programmer Response: Refer to chapter on "Program Checkout"
in the programmer's guide for this compiler for advice on how
to tackle this type of error.
The program should be
recompiled with STRINGRANGE and SUBSCRIPTRANGE enabled, and
reexecuted before calling IBM.

IBM0061

NO MAIN PROCEDURE, PROGRAM NOT EXECUTED
Explanation: An attempt has been made to execute a program
containing one or more external PLII procedures, none of which
has the MAIN option in its PROCEDURE statement.
Programmer Response:
Ensure that the first external PLII
procedure to be invoked has the MAIN option in its PROCEDURE
statement.

IBM007A

WAITING FOR REPLY TO 'DISPLAY' MESSAGE
Explanation: The purpose of this message is to prompt the
operator to make an appropriate reply.
This message is always
issued when a DISPLAY statement with the REPLY option is
executed.

IBM0081

NO MAIN STORAGE AVAILABLE, N.EEDS xxxxxxxx MORE BYTES
Explanation:
1.

There is insufficient main storage to begin program execution.
The one line message which appears means that xxxxxxxx
more bytes of storage must be made available before
execution of the main procedure can begin.
This does !!Q!:
include the storage required once execution of the main
procedure begins.

The three line message which appears during program

Execution-Time (IBM) Messages
••• BEPORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2 •••

execut~on

means that a request for xxxxxxxx bytes of
storage has been made either by a PLII statement or by a
~ibrar,y ,module calle9. by a PLII statement.
To satisfy the
request,' xxxxxxxx more,bytes of contiguous free storage
must be made available.

grog£ammer Response:
1.

If the message appears during program iriitializatLQn, the
program is not executed.

If the message appears during program execution, the
program is terminated.

In both cases, control is returned to the caller with a return
code of 4012 in Register 15, or a CANCEL macro instruction is
issued.
The programmer should check the space requirements of
the job and either reduce those requirements by amending the
program or increase the size of the partition in which the job
is to run.
IBM0201

'CONVERSION' CONDITION RAISED BY 'SIGNAL' STATEMENT
~XElgnat!QB:

The program contains a SIGNAL statement to raise
the 'CONVERSION' condition for which there is no on-unit.

g~Qg~g~er

R~ponse:
Either remove the SIGNAL statement or
include an on-unit for the CONVERSION condition in the program.

IBM021I

UNKNOWN SOURCE ATTRIBUTES ON INPUT
~xplsnat!Qn:

The CONVERSION condition has been raised within a
GET LIST or GET DATA statement with the FILE option.
The
attributes of the source data cannot be determined.
For
example:
DCL (A,B) CHAR (14) ;
GET LIST (A, B)
Where the input stream contains 'PIG'C, 'DOG',--- the condition
will be raised when the first item is encountered. The value
for ONSOURCE will be:
"'PIG'C", and for ONCHAR will be:
"C".

IBM022I

UNKNOWN SOURCE ATTRIBUTES ON INPUT AFTER 'TRANSMIT' DETECTED
Explanation: The CONVERSION condition has been raised after an
error has caused the TRANSMIT condition to be raised.
For an
exrldnation of the conversion error, see the explanation given
for message IBM021I.

IBM023T

UNKNOWN SOURCE ATTRIBUTES
Explanation: The CONVERSION condition has been raised within a
GET LIST STRING or GET DATA STRING statement.
For an
explanation of the conversion error, see the explanation given
for message IBM021I.

4
***B~FORE

CALLING

IB~

FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

IBM024I

CONVERSION FROM F-FORMAT ON INPUT
Explanation:
An invalid character has been detected in an
F-format input field.
PrQgrammer ResQQ~:
Include a suitable on-unit in the program
to monitor errors ~n the input data that are revealed by the
CONVERSION condition.
Use the ONSOURCE and ONCHAR built-in
functions to identify the error and the ONSOURCE and ONCHAR
pseudovariables to assign a valid numeric value so that the
program can continue to be executed normally.
Otherwise check
that all input is in the correct format before executing the
program.

IBM0251

CONVERSION FROM F-FORMAT ON INPUT AFTER 'TRANSMIT' DETECTED
Explanation:
An invalid character has been detected in an
F-format input field.
A transmission error has also occurred;
the conversion error may be directly attributable to the
transmission error.
PrQgramme~ Respon~:
If the conversion error recurs after the
transmission error has been eliminated. take the steps given
for the preceding message.

IBM027I

CONVERSION FROM E-FORMAT ON INPUT
]~~~at~QQ:

An invalid character has been detected in an
E-format input field.

Progr~~]esPQll~:
Take the steps advised for conversion
errors in message IBM024I.

IBM028I

CONVERSION FROM E-FORMAT ON INPUT AFTER 'TRANSMIT' DETECTED
]~~natiQ~:

An invalid character has been detected in an
E-format input field.
A transmission error has also occurred;
the conversion error may be directly attributable to the
transmission error.

££Qgrammer Response:
If the conversion error recurs after the
transmission error has been eliminated, take the steps advised
for message IBM024I.
IBM029I

CONVERSION FROM B-FORMAT ON INPUT
~X£1~atiQQ:

An invalid character has been detected in a
B-format input field.

Programmer ResJLQ.!!..§.g:
Include a suitable on-unit in the program
to monitor errors in the input data that are revealed by the

Execution-Time (IBM)

Messages

***BEFORE CALLING IBM FOR PFOGRAMMING SUPPORT, REFER TO PAGE 2***

CONVERSION condition. Use the ONSOURCR and ONCHAR built-in
functions to identify the error and the ONSOURCE and ONCHAR
pseudovariables to assign a valid bit character so that the
program can continue to be executed normally. Otherwise check
that all input is in the correct format before executing the
program.
lBM031!

CONVERSION PROM B-PORMAT ITEM ON INPUT AFTER 'TRANSMIT'
DETECTED
~xplanation:

An invalid character has been detected in a
B-format input field.
A transmission error has also occurred;
the conversion error may be directly attributable to the
transmission error.

Programmer RespoD~:
If the conversion error recurs after the
transmission error has been eliminated, take the steps given
for message IBM029I.
IBM032I

CONVERSION FROM 'CHARACTER' TO ARITHMETIC
Explanation:
An invalid character has been detected in a
character string that is being converted to an arithmetic data
type.
Programmer Response:
If the error is in the conversion of a
PLII source program constant or in the conversion of a
character string created during the execution of the program~
correct the source program, recompile it and rerun it.

lBM033I

CONVERSION PROM CHARACTER TO ARITHMETIC ON INPUT OR OUTPUT
]xElgnatiQll: A character which is invalid for conversion to an
arithmetic form has been detected in one of the following:
1.

An arithmetic constant in a list-directed or datadirected item.

A character constant being converted to an arithmetic form
in a list-directed or ~ata-directed item.

An A-format input field being converted to an arithmetic
form.

Programmer Response:
IBM024I.
IBM034l

Take the steps advised fbr message

CONVERSION PROM CHARACTER ON INPUT AFTER TRANSMIT DETECTED
Explanation:
A character which is invalid for conversion to an
arithmetic form has been detected in one of the following:
1.

An arithmetic constant in a list-directed or data-directed
input item.

A character constant being converted to an arithmetic form

***BEFORl CALLING IBM FOR PROGRAMMING SUPPORT t

REFER TO PAGE 2***

in a list-directed or data-directed input item.
3.

An A-format input field being converted to an arithmetic
form.

A transmission error has also occurred; the conversion error
may be directly attributable to the transmission error.
Programmer Response:
If the conversion error recurs after the
transmission error has been eliminated, take the steps advised
for message IBM024I.
IBM035I

CONVERSION FROM 'CHARACTER' TO 'BIT'
Explanation:
An invalid character has occurred in a character
string that is being converted to a bit string.
Programmer Response: If the error is in the conversion of a
PL/I source program constant or in the conversion of a
character string created during the execution of the program,
correct the source program, recompile it, and rerun it.

IBM036I

CONVERSION FROM CHARACTER TO BIT ON INPUT OR OUTPUT
Explanation:
A character other than 0 or 1 appears in one of
the following:

IBM037I

A bit constant in a list-directed or data-directed item.

A character constant being converted to bit form in a
list-directed or data-directed item.

An A format input field being converted to bit form.

A B-format input field (excluding any leading or trailing
blanks).

CONVERSION FROM CHARACTER TO BIT ON INPUT AFTER 'TRANSMIT'
DETECTED
Explanation: A character other than 1 or 0 appears in one of
the following:
1.

A bit constant in a list-directed or data-directed input
item.

A character constant being converted to bit form in a
list-directed or data-directed input item.

An A-format input field being converted' t,o bit form.

A B-format input field
blanks).

(e~cluding

any leading or trailing

A transmission error has also occurred; the conversion error
may be directly attributable to the transmission error.

Execution-Time (IBM) Messages
***BEFORe CALLING IBM FOR PROGRAKKING SUPPORT, REFER TO PAGE 2***

Progguer RespoQg:
If the conversion error recurs after the
transmission error has been eliminated, take the steps advised
for message IBM024I.
IBM0381

CONVERSION TO PICTURE CHARACTER STRING
]Xp~g~ioQ:

A character that does not match the picture
specification has occurred in a conversion to a PICTURE
ch~racter string.

Prog~~B~~~:
Ensure that the character string that is
to Le converted to a PICTURE character string is suitable for
the conversion.
If necessary, use the ONSOURCE and ONCHAR
built-in functions to identify the error and the ONSOURCE and
ONCHAR pseudovariables to replace an erroneous character with a
character that is valid for conversion.

IBM039I . CONVERSION TO PICTURE CHARACTER STRING ON INPUT OR OUTPUT
~l~nation:

A character that does not match the picture
specification has occurred in a stream-oriented item that
requires conversion to a PICTURE character string.

_~£Qg~g~~£_~~§pon~:

Either ensure that all input data to the
program is in the correct format or take the steps given for
the preceding message to ensure that the program has adequate
erLor recovery facilities so that it can comment on any invalid
data found in its input, and continue processing.

IBM0401

CONVERSION TO PICTURE CHARACTER STRING ON INPUT AFTER
'TRANSMIT' DETECTED

A character that does not match the picture
specification has occurred in a stream-oriented input item that
requires conversion to a PICTURE character string.
A
transmission error has also occurred; the conversion error may
be directly attributable to the transmission error.

~~pld!!ati<21!:

PrQg£~~--...BesEQng:

If the conversion error recurs after the
transmission error has been eliminated, take the steps advised
for message IBM039I.

IBM0421

CO VERSION FROM P-FORMAT (ARITH) ON INPUT
~.!.E.l.E!!!at!on:

An edit-directed P-format input item contains a
character that does not match the picture specification.
r£Qg£g~~~£_B~~Qn~~:

Either ensure that all input data to the
program is in the correct format before executing the program
or use the program to check the data.
If necessary, use the
ONSOURCE and ONCHAR built-in functions to identify the error
and the ONSOURCE and ONCHAR pseudovariables to replace an
erroneous character with a character that is valid for
c on version.

BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

IBM043I

CONVERSION FROM P-FORMAT
DETECTED

(ARITH) ON INPUT AFTER 'TRANSMIT'

~'!.:Ql.2nati.Q.ll:

An invalid character has been detected in a
P-format (arithmetic) input field.
A transmission error has
also occurred; the conversion error may be directly
attributable to the transmission error.

g£Qg~mer ~~spon§~:

If the conversion error recurs after the
transmission error has been eliminated, take the steps advised
for message IBM042I.

IBM0451

CONVERSION FROM P-FORMAT

(CHAR)

ON INPUT

Explanation:
An invalid character has been detected in a
P-format input item.
Programmer Response:
Either ensure that all input data to the
program is in the correct format before executing the program
or use the program to check the data.
If necessary, use the
ONSOURCE and ONCHAR built-in functions to identify the error
and the ON SOURCE and ONCHAR pseudovariables to replace an
erroneous character with a character that is valid for
conversion.
IBM0461

CONVERSION FROM P-FORMAT (CHAR)
DETECTED

ON INPUT AFTER 'TRANSMIT'

Explanation:
An invalid character has been detected in a
P-format (character) input item.
A transmission error has also
occurred; the conversion error may be directly attributable to
the transmission error.
Programmer Response:
If the conversion error recurs after the
transmission error has been eliminated, take the steps advised
for message IBM045I.
IBM050I

RESTRICTED STREAM CONVERSION
~xplanatiQn:

The combination of attributes of the character
string source and the target variable require a conversion that
is not supported in a program compiled with the LIMSCONV
option.

IBMOS1I

RESTRICTED STREAM CONVERSION ON INPUT
EX,Elanati.Q.ll:
The combination of attributes of the stream
source and the target variable require a conversion that is not
supported in a program compiled with the LIMSCONV option.

Execution-Time
***BEFORE CALLING

IB~

(IBM)

Messages

FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

IBM052I

RESTRICTED STREAM CONVERSION ON INPUT APTER 'TRANSMIT' DETECTED
Explanation: The combination of attributes of the stream
source and the target variable require a conversion that is not
supported in a program compiled with the LIMSCONV option.
A
transmission error has also occurred and the attributes of the
stream source may have been determined erroneously as a result.

IBM100I

'NAME' CONDITION RAISED BY 'SIGNAL' STATEMENT
~xplanation:

The program contains a signal statement to raise
the NAME condition for which there is no on-unit.
Programmer Response:
Either remove the SIGNAL statement or
include an on-unit for the NAME condition in the program.

IBM101I

INVALID ELEMENT-VARIABLE IN STREAM FOR 'GET FILE DATA'
~lanation:

The NAME condition is raised immediately any of
the following errors is detected:
1.

When an identifier in the input stream has no counterpart
in the data list of the GET statement, or when the GET
statement has no data list and an identifier that is not
known in the block is encountered in the stream.
When invalid blank characters are found within an
in the input stream.

~dentifier

When the name field, or part of a qualified name, is
omitted.

When there are more than 256 characters in a
fully-qualified name.

When blanks are found within an array subscript other than
between the optional sign and the decimal digits.

When an array subscript is missing or indicates too many
dimensions ..

When a value in a subscript is not a decimal digit.

When the subscript is beyond the declared range of
~ubscripts for a particular array.

If the left-parenthesis is missing after the name of an
array.

10.

If a character other than "=" or a blank is found after a
right-parenthesis that delimits an array subscript in the
input stream.

11.

If the end-of-file or a non-blank delimiter is found
before "=" in an item in the input stream.

f£.Qg~.~§£ __B~.§E.Q1!.§§:

Use the DATAPIELD condition built-in
function in a NAME on-unit to obtain the invalid data ite~.

***BEPORE CALLiNG IBM POR PROGRArtMING SUPPORT, REFER TO PAGE 2***

IBM1201

'RECORD' CONDITION RAISED BY 'SIGNAL' STATEMENT
Explanation:
A SIGNAL statement to raise the RECORD condition
has been executed. There was no on-unit for this condition.
Programmer Response:
Supply an on-unit for the RECORD
condition or remove the SIGNAL statement.

IBM1211

LENGTH OF RECORD VARIABLE LESS THAN RECORD LENGTH
Explanation:
A record in a record-oriented input/output
statement is longer than the record variable.
This message is produced for records that are longer than the
associated PL/I variable.
For a READ statement, the record is
truncated to the length of the variable in the INTO option.
For a LOCATE statement (F-format records only), a buffer is not
allocated.
For a WRITE statement (F-format records only), the
record is transmitted with additional padding bytes to make up
the length.
The contents of the padding bytes are undefined.
For a REWRITE statement, the record is replaced by the shorter
record made up to the correct length with the appropriate
number of padding bytes, the contents of which are undefined.
R~Qg£~er

Respo~:
Either supply an on-unit for the RECORD
condition so that the program can continue to be executed, or
modify the program to make the length of the record variable
the same as the length of the records on the data set.
The
language reference manual for this compiler gives details of
how such records are handled when the RECORD condition is
raised.

IBM1221

LENGTH OF RECORD VARIABLE GREATER THAN RECORD LENGTH
Explanation:
A record in a record-oriented input/output
statement is shorter than the record variable.
This message is produced for records that are shorter than the
associated PL/I variable.
For a READ statement using F-format
records and a fixed-length variable in the INTO option, the
excess bytes in the variable are undefined.
For a LOCATE
statement, where the maximum length of the records is less than
the length of the PL/I variable, the buffer is not allocated.
For a iRITE statement, the variable in the FROM option is
longer than the maximum length of the records and is truncated
to the maximum record length.
For a REWRITE statement, the
variable in the FROM option is longer than the record it is to
replace, and is truncated to the length of this record.
Programmer Res£QQ~:
Either supply an on-unit for the RECORD
condition so that the program can continue to be executed, or
modify the program to make the length of the record variable
the same as the length of the records on the data set.
The
language reference manual for this compiler gives details of
how such records are handled when the RECORD condition is
raised.

Execution-Time (IBM)

Messages

***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

IBM123I

'WRITE' OR 'LOCATE'

VARIABLE HAS ZERO LENGTH

Expla~11QQ:
A WRITE or REWRITE statement has attempted to
transmit a record variable of zero length, or a LOCATE
statement has attempted to obtain buffer space for a zero
length record variable.

PrQg£~~~£-Bgspon§g:
Modify the program to ensure that the
varying-length string used as a record variable is not a null
string when the WRITE, REWRITE or LOCATE statement is executed.

IBM124I

ZERO LENGTH RECORD READ FROM REGIONAL DATA SET
]x£l~nation:

A record of zero length has been read from a
REGIONAL data set associated with a DIRECT file.
A zero-length
record on a direct-access device indicates the end of the data
set.
However, the message above will only be produced if the
data set has been created incorrectly.

f~ogrammer

Response:
Check that the data set was created
correctly as a regional data set.
Recreate the data set if
necessary and possible.
Check also that the record has been
accessed with a key that is valid for the data set.

IBM125I

'WRITE' or 'LOCATE' VARIABL
KEY ..

TOG SHORT TO CONTAIN EMBEDDED

.E;x£1~nation:

A WRITE or REWRITE statement has attempted to
transmit, or a LOCATE statement has attempted to allocate
buffer space for, a record variable too short to contain the
data set embedded key.
For a WRITE or REWRITE statement, no
transmission takes place; for a LOCATE statement, a buffer
is not allocated.

IB~1401

'TRANSMIT' CONDITION RAISED BY 'SIGNAL' STATEMENT
~lLe.1~!@1ion:

The program contains a SIG NAL sta tement to raise
the TRANSMIT condition for which there is no on-unit ..

g~Qg~~mm~~_B~~QQ~~:

Either remove the SIGNAL statement or
include an on-unit for the TRANSMIT condition in the program.

IBM141I

UNCORRECTABLE ERROR IN OUTPUT
.E;XElanation:
Data management has detected an uncorrectable
error while transmitting output data between main storage and
an external storage device.
The condition is raised on the
completion of a WRITE, REWRITE, or LOCATE statement.
For
BUFFERED files, this condition may be raised only after the
execution of several I/O statements. after the I/O statement
which transmitted the record.
No further processing of an
OUTPUT file other than a file associated with a unit record
device can occur..
Processing of an UPDATE file may continue.
For INDEXED data sets, the condition can also occur while
searching throuqh the indexes or tracing an overflow record.

***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO

P~GE

2***

~~Qg~~er

Respo~:
If the error recurs, obtain a dump of the
input/output buffer areas by using PLIDUMP in a TRANSMIT
on-unit.
See the programmer's guide for details of PLIDUMP.
The resultant output, together with all relevant listings and
data sets should be preserved for examination by IBM.

IBM142I

UNCORRECTABLE ERROR IN INPUT
Explanation:
Data management has detected an uncorrectable
error while transmitting input data between main storage and an
external storage device.
The condition is raised on the
completion of a READ or REWRITE statement for each record in
the block that contains the error and for every item
transmitted by GET statements from a block that contains the
error.
The contents of the record or data item are undefined.
However, processing of subsequent records in the input file can
be continued.
For INDEXED data sets, the condition can be
raised while searching the indexes or tracing an overflow
record.
R~Qg~g~~g~BgspoQ§~:

If the error recurs, obtain a dump of the
input/output buffers by using PLIDUMP in a TRANSMIT on-unit.
See the programmer's guide for details of PLIDUMP.
The
resultant output, together with all relevant listings and data
sets should be preserved for examination by IBM.

IBM143I

UNREADABLE OMR DATA
~X£lanation:

One of more OMR columns contain a marginal mark,
weak mark, or poor erasure that cannot be read.
The condition
is raised on completion of the RiAD operation for the card.
A
X'3F' character 1S substituted for unreadable characters, and
also put in the last byte of the record.
The card is stacker
selected to the alternate stacker.

IBM144I

WRITE ERROR IN INDEX SET.
ExQ!anatiQn:
Data management has detected a physical error
whilst attempting to write on the index set of a VSAM KSDS.
The condition is raised on the completion of a WRITE, REWRITE,
LOCATE, or DELETE statement.
No further processing of an
OUTPUT file can occur~
Processing of an UPDATE file may
continue.

IBM145I

READ ERROR IN INDEX SET.
Explanation:
Data management has detected a physical error
whilst attempting to read from the index set of a VSAM KSDS.
The condition is raised on the completion of a READ, WRITE,
REWRITE, LOCATE, or DELETE statement.
No further processing
of an OUTPUT file can occur.
Processing of an UPDATE file
may continue.
If the error occurs on a READ statement, no
data is transferred to the record variable.
For sequential
access, data set positioning may be lost, causing a subsequent
READ without KEY to raise ERROR (see message IBMS31I)

Execution-Time (IBM)

Messages

***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

IBM1461

WRITE ERROR IN SEQUENCE SET.
Exp!anat!Qll: Data management has detected a physical error
whilst attempting to write on the sequence set of a VSAM
KSDS.
The condition is raised on the completion of a WRITE,
No further processing
REWRITE, LOCATE, or DELETE statement.
of an OUTPUT file can occur.
Processing of an UPDATE file may
continue.

IBM1471

READ ERROR IN SEQUENCE SET.
ExE1anation: Data management has detected a physical error
whilst attempting to read from the sequence set of a VSAM KSDS.
The condition is raised on the completion of a READ, WRITE,
REWRITE, LOCATE, or DELETE statement.
No further processing
of an OUTPUT file can occur.
Processing of an UPDATE file
may continue.
If the error occurs on a READ statement, no
data is transferred to the record variable.
For sequential
access, data set positioning may be lost, causing a subsequent
READ without KEY to raise ERROR (see message IBM831I)

IBM1601

'KEY' CONDITION RAISED BY 'SIGNAL' STATEMENT
Explanation: The program contains a SIGNAL statement to raise
the KEY condition for which there is no on-unit.
Erogrgmmer Response:
Either remove the SIGNAL statement or
include an on-unit for the KEY condition in the program.

IBM1611

KEY SPECIFIED CANNOT BE FOUND
~XElanation:

A READ or REWRITE statement specified a recorded
key which could not be found on the data set.
In the case of
an INDEXED data set, the key in error is either higher than the
highest level index or the record is not in the prime area or
the overflow areas of the data set.
In the case of a DIRECT
file associated with a data set with REGIONAL organization, the
key in error is not in the specified region.

Prmrralllmer Respo~:
Determine why the key was incorrect and
modify the program or the data set as necessary.
Use of the
ONKEY built-in function in a KEY on-unit will aid in
determining the value of the erroneous key.
IBM1621

KEY SPECIFIED ALREADY IN USE ON DATA SET
Explanation:
In the case of data set with INDEXED
organization, an attempt has been made to transmit a keyed
record to a data set which already holds a record with the~ame
key.
In the case of a data set with REGIONAL(1) organization
that is being created seque~tially, an attempt has been made to
transmit a record to a region that already contains a record.
Programmer Response:
Either check the validity of the data
that is being processed before executing the program or use the

***BEFORE CALLING IBM FOR PROGRAKMING SUPPORT, REFER TO PAGE 2***

program to check the data.
Use of the ONKEY built-in function
in a KEY on-unit will aid in identifying an erroneous key, in
correcting it, and in permitting processing to continue
normally.
IBM163I

KEY SPECIFIED IS LESS THAN VALUE OF PREVIOUS KEY
~~ P 1 an at.!2.!!

:
A key w.i t h a val u e t hat i s Ie s s t han the val u e
the preceding key has been detected during the creation or
extension of an INDEXED or REGIONAL SEQUENTIAL data set.

Progr~~RespoB§g:
Ensure that the records that are to be
written onto an INDEXED or REGIONAL data set that is being
created or extended are in the correct ascending key sequence
order.
Otherwise use a KEY on-unit to comment on the error
and, where possible, to permit processing to continue normally.

IBM164I

KEY SPECIFIED CANNOT BE CONVERTED TO VALID DATA
Explanation:
A WRITE, READ, REWRITE, LOCATE statement for a
REGIONAL data set specified a key with a character-string value
consisting entirely of blanks or containing characters other
than 0-9 or blank as part of the region number.
Programmer Response:
Ensure that the key is in the correct
format.
If necessary, use th~ ONKEY built-in function in a KEY
on-unit to identify the erroneous key.
The on-unit can be used
to report any such errors and allow processing to continue.
Records associated with the erroneous keys can be transmitted
in a subsequent run for which the keys have been corrected.

IBM165I

KEY SPECIFIED IS INVALID
Explanation:
For an INDEXED data set, either the KEY or
KEYFROM expression is a null string or an attempt has been made
to rewrite a record where the embedded key of the replacement
recQro is not equal to that of the record that is to be
overwritten. For a REGIONAL data set, the key specified is a
null string.
Progr~-Bg§EQB§g:

IBM1661

As for the previous message.

KEY SPECIFIES POSITION OUTSIDE REGIONAL DATA SET
~z£lanat'!Qn:

A WRITE, READ, or REWRITE statement specifies a
key whose relative record or track value exceeds the number of
records or tracks respectively for the REGION~L data set.
Programmer

Respo~:

As for message IBM164I.

Execution-Time (IBM)

Messages

***BEFORE CALLING IBM FOR PROGRAMM!NG SUPPORT, REFER TO PAGE 2***

IBM167I

NO SPACE AVAILABLE TO ADD KEYED RECORD
Explanation:
For a SEQUENTIAL file associated with an INDEXED
data set, an attempt has been made to write or locate a record
during the creation or extension of such a data set when the
space allocated to the data set is full.
For a DIRECT file
associated with an INDEXED data set, there is no space in the
available overflow areas to accept the ~verflow record caused
by the insertion of a new record by a WRITE statement.
For a DIRECT file associated with a REGIONAL data set, there is
no space to add the record in the specified region.
Note that
the data set is not necessarily full.
£IQg~~£-E~spon~:

Use the ONKEY built-in function to
identify the key value that caused the error.
If the key is in
error, correct it and recommence the job from the point reached
when the error occurred. If the key is correct, organize the
data set so that the rejected record can be accommodated.

IBM168I

'KEYFROM' VALUE LIES OUTSIDE KEY RANGE(S)
SET.

DEFINED FOR DATA

Explanation:
A WRITE or LOCATE statement specified a key
with a value outside the key ranges specified for the data
set when it was defined.
(VSAM KSDS).
IBM180I

'ENDFILE' CONDITION RAISED BY 'SIGNAL' STATEMENT
E~E!~natiQ~:

The program contains a SIGNAL statement to raise
the ENDFILE condition for which there is no on-unit.

£rog£~~§r

R~§~A§~:
Either remove the SIGNAL statement or
include an on-unit for the ENDFILE condition in the program.

IBM181I

'ENDFILE' CONDITION RAISED
]~E!snation:

The end of an input file has been detected.

Prog£ammer Response: Include an on-unit for the ENDFILE
condition for each input file in the program to handle the
end-of-file processing.
JIBM182I

END OF PILE PREVIOUSLY ENCOUNTERED ON STREAM INPUT
ExE!~natiQll:

The ENDFILE condition was raised when the file
mark was encountered but an attempt is being made to read ~
beyond the end of the file.
Either an ENDFILE on-unit has been
executed and a further attempt to read the file is being made
or the end-ot-file mark was encountered between items in the
d~ta list of the current GET statement.

ErQq£s~~§£-B~sPO]~§:

If the program contains an ENDFILE

16
"' BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

on-unit, make sure that it does not attempt to read the file
after the ENDFlLE condition has been raised for it.
If the
error occurred during execution of a GET statement with two or
more items in the data list, make sure that the GET statement
can be completed by providing sufficient data items before the
e~d-of-file mark is encountered.
IBM2001

'UNDEFINEDFlLE' CONDITION RAISED BY 'SIGNAL' STATEMENT
Explanation: The program contains a SIGNAL statement to raise
the UNDEFINEDFlLE condition for which there is no on-unit.
Programmer Response: Either remove the SIGNAL statement orinclude an on-unit for the UNDEFlNEDFILE condition in the
program.

IBM2051

I/O ERROR -

'REGIONAL' DATA SET CANNOT BE FORMATTED

Explanation: When a REGIONAL data set was being opened for
output the open process could not format it with dummy records
for a REGIONAL(l) SEQUENTIAL OUTPUT file or with capacity
records for a REGIONAL(3) SEQUENTIAL OUTPUT file or a
REGIONAL(l) or REGIONAL(3) DIRECT OUTPUT file.
This is due to
an incorrectable input/output error that is similar to the type
of input/output error that raises the TRANSMIT condition.
Programmer Response:
If the error recurs after reSUbmitting
the job, use PLIDUMP to obtain a storage dump and retain all
the relevant documentation for study by IBM.
IBM2061

'LlNESIZE' OR • PAGESI ZE' OUTSIDE IMPLEMENTATION-DEFINED LIMI TS
Explanation: The impl~mentation-defined maximum or minimum for
the LINESIZE option of the ENVIRONMENT attribute has been
exceeded. For F and U-format records, the maximum is 32,759;
for V-formatreoords, the maximum is 32,751. The minimum in
all cases is 1.
Progran~r Response:
Check that the argument to the LINESIZE
option is within the prescribed lirnit9. If the argument is a
variable, check that it is a FIXED BINARY (31,0) STATIC
variable that was correctly initialized before the file was
opened.

IBM2081

WRONG BLOCKSIZE OR RECORD LENGTH SPECIFIED
Explanation:

One of the following errors may have occurred:

1-.

The block size is less than the record length.

For FB-format records, the blocksize is not a multiple of
the record length.

For an indexed sequential,...lNPUT or UPDATE file, the
Execution-Time (IBM) Messages

••• BEFORE ~ALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2··.

blocksize specified on the file declaration is less than
the actual blocksize of the data set.
4.

Record length is greater than 80 bytes for SYSIPT or
SYSPCH.

For a diskette file the record length is greater than 128.

Programmer Response: Check the blocksize and record length
specified in the BLKSIZE and RECSIZE option of the ENVIRONMENT
attribute for the file.
If the argument of either option is a
variable, check that it is FIXED BINARY(31,0) S~TIC and that
it has been initialized.
IBM212I

KEYLENGTH NEGATIVE OR GREATER THAN 255
Explanation: The KEYLENGTH option of the ENVIRONMENT attribute
for this file has an invalid keylength that is greater than 255
or i s negat~i vee
Programmer Response: The argument of the KEYLENGTH option
should be checked to ensure that it is either a constant or a
variable with the attributes FIXED BINARY (31,0) STATIC whose
value neither exceeds 255 nor is negative when the file is
opened.
If the argument is a variable, check that it has been
~orrectly initialized.

IBM213I

INVALID KEYLOC VALUE
Explanation:
1.

The offset of the key within a record is invalid.
The sum
of the KEYLOC value and the key length is greater than the
record length.

For blocked ISAM files, either KEYLOC has not been
specified or KEYLOC(O) was specified. Both are invalid.

Programmer Response:

IBM214I

Check the value of the argument to the KEYLOC option. If
the argument is a variable, check that it is FIXED BINARY
(31,0) STATIC and that it has been correctly initialized.

Specify a KEY.LOC value that is greater than zero.

CONFLICTING OR INVALID ENVIRONMENT OPTIONS
Explanation: This message will be produced when a program is
executed for which the compilation produced a message
indicating precisely the conflicting or invalid environment
options.
Programmer Response:

IBM215I

Correct the source program.

INVALID BUFOFF VALUE
Explanation:

The values that can be specified in the BUFOFF

••• S!:FO~E

CALLII«; IBM FOR PROGRAMMING SUPPORT, REFER TO PA.GE 2 •••

option for an ASCII input data set are in the range 0 thru 99.
£~Qgrammer

Response:
Ensure that the value specified in the
BOFOFF option is within the range of values given above.
If
the argument is a variable, ensure that it is correctly
initialized.

IB"216I

INVALID OFLTRACKS VALUE
!xplanation: The maximum number of overflow tracks per
cylinder is 9 for a model 2311, 19 for models 2314 and 2321,
18 for model 3330, and 11 for moqel 3340.
Programmer Response:
Ensure that the number specified for the
OFLTRACKS option is neither negative nor too large.

IBM217I

SYMBOLIC DEVICE NAME FOR THIS FILE ASSIGNED WITH IGN OPTION
Explanation: The DOS LIOCS open routines have ignored a
request by the PL/I program to open a file associated with a
symbolic device name that was assigned with the IGN option.

IBM2181

INVALID STACKER OPTION
Explanation:
1 or 2.

IBM225I

The value of the stacker option specified was not

VALOE OF ENVIRONMENT OPTION DOES NOT MATCH ACTUAL DATA SET
VALUE.
Explanation: For VSAM data sets the values of KEYLOC,
KEYLENGTH, and RECSIZE are specified when the data set is
defined.
If values are specified on any file declarations
they must match the defined values.

IBM228I

PASSWORD INVALID OR NOT SPECIFIED.
Explanation: For VSAM data sets defined with a password, ENV
(PASSWORD) must be specified.
If this password is invalid or
is not specified the system operator is allowed a number of
attempts to specify the correct password (the number of
retries is specified when the data set is defined).
If these
attempts fail ONDEFINEDFILE is raised.

IBM229I

NO ENTRY IN VSAM CATALOG.
Explanation:
Before using a VSAM data set a catalog entry
must be made and space allocated for the data set, using the
Access Method Services DEFINE utility.
This message may mean
that ENV(VSAM) has been specified for a file, but the data
set has not been convetted from I5AM to VSAM.

Execution-Time (IBM)

Messages

***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

~IBM2301

1/0 ERROR READING CATALOG OR VOLUME LABEL.

Explanation:
An 1/0 error prevented the reading of a VSAM
catalog or a volume label.
IBM231I

TIMESTAMP MISMATCH.
Explanation:
For VSAM data sets the index and data can
be updated separately and the time of the latest update of
each is recorded.
If these times do not match, the integrity
of the data is uncertain.
Similarly the timestamp in the data
set catalog record may not match the timestamp on the volume
containing the data set; this indicates the extent information
in the catalog record may not agree with the extents indicated
in the VTOC for the volume.

IBM232I

DATA SET NOT AVAILABLE.
]~pla~ion:

The data set to be accessed is already being
used by another program and is not shareable.
Refer to the
Programmer's Guide for further information.

IBM233I

DATA SET NOT PROPERLY CLOSED.
Explanation:
The last time the data set was opened the close
operation failed, leaving the data set in an unusable state.
Use of the access method services VERIFY utility program
may restore the data set to a usable state.

IBM234I

DATA SET NEVER LOADED.
Explanation:
A file cannot be opened for INPUT or UPDATE to
access a VSAM data set until one or more records have been
loaded into the data set using a SEQUENTIAL OUTPUT file.
Having once loaded records into the data set records can be
added using a DIRECT UPDATE file even after all records have
been deleted from the data set.

IBM235I

UNIDENTIFIED ERROR DURING VSAM OPEN.
Explanation: The VSAM routines have detected an error during
the open process, the cause of which cannot be determined
explicitly.
g~Q~~mme~ Respon~:

If the error recurs after resubmitting
the job, use PLIDUMP to obtain a storage dump and retain
all the relevant documentation for study by IBM.

IBM236I

OPERATING SYSTEM UNABLE TO OPEN FILE ccc.
Explanation: When a VSAM data set is opened through the ISAM
compatibility interface, this condition will
occur if VSAM detects errors during the open process.

1BM237I

SYMBOLIC UNIT NOT ASSIGNED OR INVALID.
~XE1~natiQn:

The address in the ASSGN statement for the
loqical unit was UA or IGN or the logical unit was invalid.

***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

IBM2381

ERROR IN EXTENT STATEMENT.
Explanation:
1. The symbolic unit specified in the EXTENT statement was
invalid.
2. The volume serial numbers in the EXTENT statement do not
match those in the catalog entry.
3. More than 16 extents were specified.

IBM2391

INSUFFICIENT SPACE FOR MASTER INDEX OR CYLINDER INDEX.
Explanation:
1. The master index is not large enough to reference the prime
data area.
2. The cylinder index area is not large enough to reference
the prime data area.

IBM2401

UNABLE TO MOUNT REQUIRED VOLUME.
Explanation: Either an attempt was made to mount two volumes on
the same unit or the operator was unable to mount the required
volume.

IBM2411

'REUSE' OPTION SPECIFIED FOR A NON-REUSEABLE DATA SET.
Explanation: The ENVIRONMENT option REUSE can only be
specified with VSAM data sets which have been defined, during
their creation by Access Method Services, as reuseable.

IBM2421

ALTERNATE INDEX PATH IS EMPTY.
Explanation: A path can become empty by having all of its
pOinters deleted. Such a path cannot be opened.

IBM2431

ATTEMPT TO POSITION AT LAST RECORD FAILED.
Explanation: When the ENVIRONMENT option BKWD ·is used, on
opening, the file must be positioned at the last record.
If
the attempt to position at the last record fails, the file is
closed and the UNDEFINEDFILE condition is raised with this
message. This message may also be given when BKWD is specified
for an empty data set.

IBM3001

'ZERODIVIDE' CONDITION RAISED BY 'SIGNAL' STATEMENT
Explanation: The program contains a SIGNAL statement to raise
the ZERODIVIDE condition for which there is no on-unit.
programmer Response:

Either remove the SIGNAL statement or

Execution-Time (IBM) Messages
***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

include an on-unit tor the ZERODIVIDE condition in the program.
IBM301I

'ZERODIVIDE' CONDITION RAISED
Explanation: The program has attempted to execute a statement
in which a value of zero has been used as the divisor in a
division operation.
Programmer Response: Either check the data that could produce
a zero divisor before running the program or insert a
ZERODIVIDE on-unit to handle the condition whenever it arises.

IBM320I

'UNDERFLOW' CONDITION RAISED BY • SIGNAL' STATEMENT
Explanation: The program contains a SIGNAL statement to raise
the UNDERFLOW condition for which there is no on-unit.
Programmer Response: Either remove the SIGNAL statement or
include an on-unit for the UNDERFLOW condition in the program.

IBM321I

• UNDERFLOW' CONDITION RAISED
Explanation: The magnitude of a floating-point number is
smaller than the permitted minimum.

IBM340I

'SIZE' CONDITION RAISED BY 'SIGNAL' STATEMENT
Explanation: The program contains a SIGNAL statement to raise
the SIZE condition for which there is no on-unit.
Programmer Response: Either remOve the SIGNAL statement or
include an on-unit for the SIZE condition in the program.

IBM341I

'SIZE' CONDITION RAISED IN I/O STATEMENT
Explanation: The high-order (i.e. leftmost) significant
binary or decimal digits are lost in an input/output operation
where the size of the value being transmitted exceeds the
declared (or default) size of the data item.

IBM342I

'SIZE' CONDITION RAISED
Explanation: The high-order (i.e., leftmost) significant
binary or decimal digits are lost in an aSSignment to a
variable or temporary variable where the size of the value
being assigned exceeds the declared (or default) size of the
data item.
Programmer Response: Either modify the program so that the
data item is large enough for the value being assigned to it or

22
***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

use a SIZE on-unit to permit processing to continue when the
SIZE condition is raised.
3601

'STRINGRANGE' CONDITION RAISED BY 'SIGNAL', STATEMENT
Explanation: The program contains a SIGNAL statement to raise
the STRINGRANGE condition for which there is no on-unit.
Programmer Response: Either remove the SIGNAL statement or
include on on-unit for the STRINGRANGE condition in the
program.

3611

'STRINGRANGE' CONDITION RAISED
Explanation: In the expression SUBSTR(S,I,J), I and J are such
that the substring does not lie wholly within the string S.
Programmer Response:
It should be possible to modify the
source program so that this condition cannot occur.

Execution-Time (IBM) Messages
*BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

22.1

IB~380I

'AREA' CONDITION RAISED BY THE 'SIGNAL' STATEMENT
~xpla~~!ion:

The program contains a SIGNAL statement to raise
the AREA condition for which there is no on-unit.

grogrammer ResBQn§~:
Either remove the SIGNAL statement or
include an on-unit for the AREA condition in the program.
IBM381I

'AREA' ASSIGNMENT NOT EXECUTED, TARGET AREA TOO SMALL
ExplanatiQn:
In an assignment of an area variable, the current
extent of the area on the right-hand side of the assignment
statement is greater than the size of the area to which it is
to be assigned.
Response:
Correct the program or insert an area onunit to permit the target area to be allocated with fresh
extents.

R~grammer

IBM382I

NOT ENOUGH CONTIGUOUS SPACE IN THE AREA FOR ALLOCATION
~xpl~g!ion:

In the execution of an ALLOCATE statement,
insufficient space is available in the specified area for the
allocation.

g~gra~~~~spo~§g:

Provide an on-unit to permit the
allocation to be reattempted.
If necessary, change the value
of the pointer qualifying the reference to the inadequate area
so that it points to another area in which the allocation can
be reattempted.

IBM400I

'CONDITION' CONDITION RAISED BY 'SIGNAL' STATEMENT
Expla~ion:

The program contains a SIGNAL statement to raise
the CONDITION condition for which there is no on-unit.

Programmer Respo~:
Either remove the SIGNAL statement or
include an on-unit for the CONDITION condition in the program.
IBM420I

'SUBSCRIPTRANGE' CONDITION RAISED BY 'SIGNAL'

STATEMENT

~X£l~natiQQ:

The program contains a SIGNAL statement to raise
the SUBSCRIPTRANGE condition for which there is no on-unit.
Either remove the SIGNAL statement or
include an on-unit for the SUBSCRIPTRANGE condition in the
program.

PrQg£~~RespoQ~:

Execution-Time

(IBM)

Messages

***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

IBM421I

'SUBSCRIPTRANGE' CONDITION RAISED
EXQ!anation: An array subscript has been found to have a value
exceeding the declared bound for the array.
RIogrammer ResQonse: In order to ensure that the program can
continue to execute after encountering a subscript range error,
include an on-unit for this condition with the source program,
and recompile it.
Note that array handling operations are
slower when SUBSCRIPTRANGE is enabled than when the condition
is disabled.

IBM440I

'STRINGSIZE' CONDITION RAISED BY 'SIGNAL' STATEMENT
~xQl~atiQll:

The program contains a SIGNAL statement to raise
the STRINGSIZE condition for which there is no on-unit.

Programmer Res£Q~~:
Either remove the SIGNAL statement or
include an on-unit for the STRINGSIZE condition in the program.
IBM441I

'STRINGSIZE' CONDITION RAISED
~XElanation:

The 'STRINGSIZE' condition is raised when a
string is assigned to a shorter string, causing right-hand
characters or bits in the source string to be truncated.

Programmer ResQonse:
Determine whether or not truncation of
the right-hand characters or bits in the source string is
correct.
Use an on-unit to record the relevant data or modify
the program as is necessary.
Note that when STRING SIZE is
enabled, string-handling operations are slower than when the
condition is disabled.
IBM460I

'OVERFLOW' CONDITION RAISED BY 'SIGNAL' STATEMENT
Explanation: The program contains Q SIGNAL statement to raise
the OVERFLOW condition for which there is no on-unit.
Programmer Response:
Either remove the SIGNAL statement or
include an on-unit for the OVERFLOW condition in the program.

IBM461I

'OVERFLOW' CONDITION RAISED
EXQlanation: The OVERFLOW condition occurs when the magnitUde
of a floating-point number exceeds the permitted maximum.
Programmer RespoQ§g:
Modify the program to ensure that the
condition does not recur, or provide an on-unit to handle the
condition if it is liable to recur.

24
***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

IBK480I

'PIXEDOVERFLOW' CONDITION RAISED BY SIGNAL

STATE~ENT

Explanation: The FIXEDOVERFLOW condition, for which no on-unit
has been provided, has been raised by the execution of a SIGNAL
statement.
Programmer Respon~:
Modify the program so that it can
continue to execute e~ther by providing an on-unit for the
FIXEDOVERFLOW condition, or by removing the SI'GNAL statement
that raises this condition.
IBM482I

'FIXEDOVERFLOW' CONDITION RAISED
Explanation: The FIXEDOVERLOW condition occurs when the length
of the result of a fixed-point arithmetic operation exceeds the
permitted maximum (15 for decimal values, and 31 for binary
values) •
PrQgramm~~~espon§g:
Modify the program to ensure that the
condition does not recur, or provide an on-unit to handle the
condition if it is liable to recur.

IBK531I

OPERATION EXCEPTION
Expla~ion:
An attempt has been made to execute an
instruction with an invalid System/360 or 370 operation code.

Programmer Response: It is possible that an error in the
program has caused part of the executable instructions to be
overwritten by data.
Refer to the section on program checkout
in the programmer's guide for suggestions for deleting and
correcting such errors.
Other possible causes of an operation
exception might be an attempt to invoke an external procedure
or other routine that was not incorporated into the executable
program by the linkage editor or the execution of a branch
instruction that has been made incorrect because a control
block had previously been overwritten.
Consequently, it is
advisable to check the linkage editor diagnostics to ensure
that all requested external procedures and subroutines have in
fact been incorporated into the executable program, and any
overlay phases are loaded into the correct storage locations
and do not overwrite any phases that are still active.
IBK532I

PRIVILEGED OPERATION EXCEPTION
Explanation:
An attempt has been made to execute certain
System/360 or 370 instructions which can only be executed by
the supervisor program.
This condition can only be raised for
a PL/I program which includes a non-PL/I routiri~ that contains
such an instruction or in which an error has occurred causing
an executable instruction in the program to be overwritten with
data that is identical to one of the privileged instructions.
Programmer Response:

If the error is not in a non-PL/I routine

Execution-Time (IBM)

Messages

***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

included in the executable program, the PL/I program should be
checked for an error that could cause the executable
instructions to be overwritten by data that matches a
privileged operation.
The section on program checkout in the
programmer's guide contains suggestions for detecting and
correcting such errors.
IBM5331

EXECUTE EXCEPTION
~XI!lanation:

An attempt has been made to use an IBM System/360
or 370 EXECUTE instruction to execute another EXECUTE
instruction.
This can occur if a routine that contains this
error has been included in the PL/I program, or if an
executable instruction that is the subject of a
compiler-generated EXECUTE instruction has been overwritten by
data that matches the operation code for the EXECUTE
instruction.

g~Qg£~~-B§spo~:

If the error is not in a non-PL/I routine
included in the executable program, the PL/I program should be
checked for an error that could cause the executable
instruction to be overwritten by data that matches the
operation code for the EXECUTE instruction on.
The section on
program checkout in the programmer's guide contains suggestions
for detecting and correcting such errors.

IBM5341

PROTECTION EXCEPTION
~xplanat1Qn:

An attempt has been made to store data in main
storage that is outside the partition allocated to the program.

PrQg£ammer Response:
If the error is not in a non-PL/I routine
included in the executable program, the PL/I program should be
checked for an error that could cause the address used by the
store instruction to be corrupted.
The section on program
checkout in the programmer's guide contains suggestions for
detecting and correcting such errors.
IBM5351

ADDRESSING EXCEPTION
Explanation:
An invalid address has been supplied as an
operand to an IBM System/360 or 370 instruction.
g£Qg~~er

R~spon~:
If the error is not in a non-PL/I routine
included in the executable program, the PL/I program should be
checked for an error that could cause the address to be
corrupted.
The section on program checkout in the programmer's
guide contains suggestions for detecting and correcting such
errors.

IBM536I

SPECIFICATION EXCEPTION
~~E!~ation:

An alignment error in the operands of an IBM
System/360 or 370 instruction, or an error in the specification
of the operands, has occurred.

***BEFORE CALLING IBM FOR

PROGRA~MING

SUPPORT, REFER TO PAGE 2***

Pro!l.I:ammer Response:
If the error is not in a non-PL/I rout.ine
included in the executable program, the PL/I program should be
checked for an error that could cause the operand to be
corrupted by overwriting control blocks or sections of
executable code.
The section on program checkout in the
programmer's guide contains suggestions for detecting and
correcting such errors.
IBM537I

DATA EXCEPTION
Explanation:
An attempt has been ~ade to process FIXED DECLMAL
data that is not in the correct form·a t.
Programmer Respgll.§.§:
The PLII program shou.ld be check·ed for a·n
error such as an operation on a FIXED DECIMAL data item before
it has been initialized, or an error which could cause the data
item to be overwritten.
Refer to the chapter on program
checkout in the programmer's guide for hints on how to trace
such errors.

IBM538I

OPERATION EXCEPTION.

FLOATING POINT INSTRU"CT.ION S NOT SUPPORTED

Explantion:
An attempt has been made to execute a
floating-point instruction on a machine that does not have
hardware facilities for floating-point arithmetic.
The
floating-point instruction is contained either in instructions
generated by the compiler, or in a non-PL/I routine in this
program .•
IBM560I

EVENT VARIABLE AS ARG TO CPLN P-V ALREADY IN USE WITH tILE XXX
Explanation: The event variable used in this statement is
already active and is associated with an input/output operation
on the named file.
Progr~~~~~~£~~:

Modify the program so that the COMPLETION
pseudovariable refers to the event variable when it is inactive
when the statement is executed.
IBM562I

EVENT VARIABLE AS ARG TO CPLN P-V ALREADY IN USE WITH 'DISPLAY'
STMT
~xplanati.Q.!!:

The event variable used in this statement is
already active and is associa~ed with a DISPLAY statement.

g£Qgrammer Response:
Modify the program so that the COMPLETION
pseudovariable refers to the event variable when it is inactive
when the statement is executed.

Execution-Time (IBM)

Messages

***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

IBM563I

EVENT VARIABLE ALREADY IN USE WITH 'FILE' XXX
EX.121~!ion:
The event variabl.e use·d in this statement i.s
already active and is associated with anot~her input/output
operation on the named file.

Programmer Resp0l!g:
Modify the program so that the
input/ouf'put operation refers to ano·ther e.vent variabl.e. or.
include a WAIT statement to prevent execution of the sta.temellt
until the active event is complete.
IBM564I

EVENT VARIABLE ASSIGNED TO, ALREADY IN USE WITH 'FILEt XXX
Explanation:
An attempt has been made to assign a value to an
event variable while it is still associated with an
input/output operation.
R~Qg£s~~~~

Re~~~§g:
Modify the program so that the event
variable used as the target in the assignment, or as the
argument of the COMPLETION pseudovariable is not the same event
variable associated with an input/output operation.
Alternatively, include a WAIT statement to prevent execution of
this statement until the active event is complete.

IBM567I

WAIT IN ON-UNIT FOR I/O EVENT BEING WAITED FOR
Expill.g.t!.Q1!:
This error is caused when a WAIT st'a tement
specifies an event variable and the completion of the event
causes entry to an on-unit for an I/O condition which contains
another WAIT statement for the same event variable.
For example:
ON RECORD(F)

BEGIN;

WAIT (E) ;

END;
WRITE FILE (F) ••• EVENT (E) ;
WAIT(E);
/* THIS STATEMENT RAISES
THE RECORD CONDITION */
R~ogrg~~~]~spon§~:

Remove the WAIT statement from the
on-unit for the input/output condition.

IBM568I

EVENT VARIABLE ASSIGNED TO, ALREADY IN USE WITH 'DISPLAY'
STATEMENT
]X.l2lanat~:

The event variable specified as the argument of
the COMPLETION built-in function or used as the target in an
assignment is still associated with a DISPLAY statement.

28
***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

~rogrammer

Response:
Modify the program so that
variable used as the target in the assignment or
argument of the COMPLETION pseudovariable is not
variable associated with the DISPLAY statement.
include a WAIT statement to prevent execution of
until the active event is complete.

IBM571I

the event
as the
the same event
Alternatively,
this statement

EVENT VARIABLE ALREADY IN USE WITH 'DISPLAY' STATEMENT
Explanation: The event variable specified in the statement is
already associated with a DISPLAY statement.
Programmer Response:
Either use a different event variable or
insert a WAIT statement so that the DISPLAY statement is
complete before th.is sta temen t is executed.

IBM6001

INCORRECT VALUES FOR W,P,S FIELDS IN E-FORMAT SPECIFICATION
EXElanatig~:

An edit-directed input/output operation for an
E-format item has been specified incorrectly.

Programmer Response:
the language rules.
IBM601I

Correct the E-format item according to

VALUE OF W FIELD TOO SMALL IN F-FORMAT SPECIFICATION
~~~lgnation:

An edit-directed input/output operation for an
F-format item has been specified incorrectly with a
W-specification that is too small to allow room for the
decimal-point when the number of fractional digits is specified
as zero.
Programmer Respo~:
the language rules~

IBM6041

Correct the F-format item according to

INVALID ASSIGNMENT TO PICTURED CHARACTER STRING
Explanation: A data item which is not a character string
cannot be assigned to a pictured character string because it
does not match the declared characteristics of the pictured
target variable.
Programmer Response:
Modify the program so that the assignment
can be possible by altering the characteristics either of the
source variable or of the target variable.

IBM605I

ITERATION FACTOR IN FORMAT LIST OR DEPTH OF R-FORMAT NESTING
TOO LARGE

IBM6061

INVALID REMOTE FORMAT ITEM IN 'ORMAT LIST

Execution-Time (IBM) Messages
***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

IBM607I

REMOTE FORMAT STATEMENT IS OUTSIDE THE CURRENT BLOCK

IBM608I

LABEL VARIABLE IN R-FORMAT ITEM DOES NOT REFER TO R-FORMAT
STATEMENT LABEL

IBM6501

SOURCE NOT MODIFIED IN CONVERSION ON-UNIT, RETRY NOT ATTEMPTED
Explanation:
The CONVERSION condition has been raised by the
presence of an invalid character in the string to be converted.
The character has not been corrected in an on-unit, either by
the ONCHAR or by the ONSOURCE pseudovariable,.
Programmer Response:
Modify the CONVERSION on-unit to use
either the ONCHAR or ONSOURCE pseudovariable to assign a valid
character to replace the invalid character in the source
string.

IBM651I

'ONSOURCE' OR 'ONCHAR' PSEUDOVARIABLE USED OUT OF CONTEXT
Explanati~:
Either ONSOURCE or ONCHAR has been used as a
pseudovariable in a statement not contained in a CONVERSION
on-unit or in a block that is dynamically-descendent from such
an on-uni t.

Programmer Response:
Modify the source program so that ONCHAB
and ONSOURCE are used as pseudo variables in the correct
context.
IBM670I

X LT 0 IN SQRT(X),
]X'planati2.!!: The built-in function SQR"; has been invoked with
an argument that is less than zero.
on-codes associated with this message are:
1500 Short floating-pointSQRT error
1501 Long floating-point SQRT error
Programmer Respon§g:
Modify the program so that the argument
of the SQRT built-in function can never be less than zero.

IBM6711

X LE 0 IN LOG (X), LOG2 (X), OR LOG10 (X)
Explanati~:
One of the built-in functions, LOG, LOG2, or
LOG10, has been invoked with an argument that is less than or
equal to zero.
The invocation may have been direct or as part
of the evaluation of an exponentiation calculation.

On-codes associated with this message are:
1504 Short floating-point Log, Log 2 or Log 10 error

***BEFORE CALLING rBM FOR

PROGRA~MING

SUPPORT, REFER TO PAGE 2***

1505 Long floating-point Log, Log 2 or Log 10 error.
Programmer Response:
If a direct invocation, then modify the
program so that the argument of the LOG, LOG2, or LOG10
built-in function is greater than zero.
If part of an
exponentiation, then ensure that the argument is greater than
zero.
IBM672I

ABS(X) TOO LARGE IN SIN (X) , COS (X) , SIND(X) , COSD(X) , TAN (X) ,
OR TAND (X)
Explanation: The argument passed to TAN, TAND, SIN, SIND, COS,
or COSD exceeds the limit specified below:
Floating-Point
Precision

Limit

Binary p :$; 21
Decimal p :$; 6

X < (2**18) * K

where K = pi for X in
radians (SIN,
COS, or TAN)

X < (2**50) * K

Binary 21 < P
Decimal 6 < P

:$;
:$;

53
16

K = 180 for X in
degrees (SIND,
COSD, TAND)

The error has arisen during one of the following:
1.

The evaluation of SIN, SIND, COS, COSD, TAN, or TAND when
invoked implicitly.

The evaluation of TAN, when invoked during the evaluation
of TAN or TANH with a complex argument.

The evaluation of SIN or COS, when invoked during the
evaluation of EXP, SIN, SINH, COS, COSH, TAN or TANH with
a complex argument.

The evaluation of a general exponentiation function with
complex arguments.

On-codes associated with this message are:
1506
1507
1508
1509
IBM674I

Short floating-point SIN, SIND, COS or COSD error
Long floating-point SIN, SIND, COS or COSD error
Short floating-point TAN or TAND error
Long floating-point TAN or T~ND error

X=Y=O IN ATAN(Y,X) OR ATAND(Y,X)
Explanation: Two arguments, both zero, have been given for the
ATAN or ATAND built-in function.
ATAN or ATAND has been
invoked either directly'with a real argument or indirectly in
the evaluation of the LOG built-in function with a complex
argument.

Execution~Time

(IBM) Messages

***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2* ••

On-codes associated with this message are:
1510 Short floating-point ATAN or ATAND error
1511 Long floating-point ATAN or ATAND error
Programmer Response: Modify the program so that the arguments
of ATAN or ATAND are not both zero.
IBM6751

ABS(X) GE 1 IN ATANH(X)
Explanation:
The ATANH built-in function has been used wit-h a
floating-point argument with an'absolute value that equals or
exceeds 1.
-On-codes associated with this message are:
1514 Short floating-point ATANH error
1515 Long floating-point ATANH error
Programmer Response: Modify the program so that the absolute
value of a floating-point assignment to the ATANH built-in
function does not equal or exceed 1.

IBM6761

ABS(X) GT 1 IN ASIN(X) OR ACOS(X)
Explanation: The absolute value of the floating-point argument
of the ASIN or ACOS built-in function exceeds 1 .
On-codes associated with this message are:
1518 Short floating-point ASIN or ACOS error
1519 ,Long floating-point ASIN or ACOS error
Programmer Response: Modify the program so that the ASIN or
ACOS built-in function is never invoked with a floating-point
argument whose absolute value exceeds 1 •

IBM7001

ATTEMPT TO ASSIGN TO UNALLOCATED CONTROLLED VARIABLE IN GET
DATA FOR FILE FILENAME
Example:
DCL X CONTROLLED FIXED BIN;
GET DATA (X) ;
Input stream contains:

'x=5; •.•.• '

Explanation: A variable occurring in the stream for a GET FILE
DATA is CONTROLLED, but has no current allocation.

32
***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

IBM701I

ATTEMPT TO ASSIGN TO UNALLOCATED CONTROLLED VARIABLE IN GET
DATA
Example:
DCL STR CHAR(4)INIT('X=5:')
X CONTROLLED FIXED BIN;
GET STRING(STR) DATA(X);
Explanation: A variable occurring in the string for a GET
STRING DATA is CONTROLLED, but has no current allocation.

IBM722I

X=O AND Y NOT REAL AND POSITIVE IN X

Explanation: In an exponentiation operation the ~loating-point
base is zero and the exponent is not positive and real.
On-codes associated with this message are:
1550 Short floating-point real base with integer exponent.
1551 Long floating-point real base with integer exponent.
1552 Short floating-point real base with floating-point
exponent.
1553 Long floating-point real base with floating-point
exponent.
1554 Short floating-paint complex base with integer exponent.
1555 Long floating-point complex base with integer ~xponent.
1556 Short floating-point complex base with complex exponent.
1557 Long floating-point complex base with complex exponent.
Programmer Response: Modify the program sa that the
exponentiation operation involves a non-zero floating-point
base or a positive real exponent.
IBM724I

Z = +11 OR -11 IN ATAN(Z) OR Z=+l OR -1 IN ATANH(Z)
Explanation: The complex floating-point argument of the ATAN
built-in function has the value of +11 or -11. Alternatively,
the complex floating-point argument of the ATANH built-in
function has the value +1 or -1.
On-codes associated with this message are:
1558 Short floating-point complex ATAN or ATANH error 1559 Long
floating-point complex ATAN or ATANH error
Programmer Response: Modify the program so that the complex
floating-point argument of ATAN can never be +11 or -11,. or the
complex floating-point argument of the ATANH built-in function
never has the value +1 or -1.

Execution-Time (IBM) Messages
***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

IBM7501

'GOTO' TO AN INVALID BLOCK ATTEMPTED
Example:
DCL L LABEL;
BEGIN:
A: L

= Ai

END;
GOTO L;
Explanation: 1. A GOTO statement that transfers control to a
label variable is invalid because the generation of the block
that was active when the label variable was assigned was no
longer active when the GOTO statement was executed.
2. A GOTO label variable statement was executed, but the label
variable was uninitialised or contained an invalid address.
programmer ResPonse: 1. Modify the program so that the GOTO
statement transfers control to a label variable that was
assigned in a block that is still active.
2.
IBM7721

Initialise the call variable correctly.

'WAIT' WITH MULTIPLE ',EVENTS' NOT IN THIS SYSTEM
Explanation: A WAIT statement with more than one event
variable has been encountered. The DOS PL/I Transient Library
for this system was generated to handle WAIT statements for
single events only.
programmer Response: Modify the program so that the WAIT
statement specifies one event only.

IBM7801

NO 'OTHERWISE' CLAUSE AND NO 'WHEN' CLAUSES SATISFIED.
Explanation: It is an error if no WHEN clauses of a SELECT
statement are selected and no OTHERWISE clause exits.

IBM8021

GET/PUT STRING EXCEEDS STRING SIZE
Explanation: For input, a GET statement has attempted to
access data that exceeds the length of the source string. For
output, a PUT statement has attempted to assign data that is
longer than' the target string.

IBM8031

FURTHER OUTPUT PREVENTED BY PRIOR CONDITION FOR FILE FILENAME
Explanation: A PL/I WRITE, LOCATE, or PUT statement has been
issued for either a buffered output file on magnetic tape or an
indexed data set, when a previous attempt to transmit a record
raised the TRANSMIT condition.

***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

IBM804I

'PRINT' OPTION/FORMAT ITEM USED WITH NON-'PRINT' FILE FILENAME

Explanation: An attempt has been made to use one of the option
PAGE or LINE.

Execution-Time (IBM) Messages
***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

34.1

IBM80S1

'DISPLAY' WITH 'REPLY' OPTION HAS ZERO LENGTH STRING
Explanat!Qn: The current length of the character string to be
displayed or the maximum length of the character string to
which the reply is to be assigned is zero.

IBM8061

LAST 'READ' BEFORE THIS 'REWRITE' IS INCOMPLETE FOR FILE
FILENAME
Explanation:
An attempt has been made to execute a REWRIT!
statement before a preceding READ statement with the EVENT
option for the same file has been completed.
Programmer Response:
Modify the program so that the REWRITE
statement is executed after completion of the READ statement ay
inserting a WAIT statement for the given event variable into
the flow of control between the two statements.

IBM8071

NO PRECEDING 'READ SET' OR 'READ INTO' FOR 'REWRITE' ON FILE
FILENAME
Explanation: A REWRITE statement without t.e KEY option has
been executed when the last input/output operation on the file
was not a READ statement with the INTO or SET option or was a
READ statement with the IGNORE option.

IBM808I

INVALID ELEMENT VARIABLE IN STRING FOR 'GET STRING DATA'
Explanat!Qn: The identifier in the string named in the STRING
option of a GET STRING DATA statement does not match the
identifier in the data specification.
Note that the DAT1FIELD
built-in function will not return a value in this case.
Programmer Response:
Modify the program so that the string
contains the identifier in the data specification.

IBM8091

INVALID FILE OPERATION FOR FILE FILENAME
Explanation: An attempt has been made to ca.rry out an
operation on a file that is impossible from the file
declaration.
For example, it is not possible to execute a
REWRITE statement on a STREAM file, read an output file, or
write an input file.
A list of other possible conflicts
follows:

Execution-Time (IBM)

Messages

***BEFORE CALLING IBHPOR PROGRA'MMING SUPPORT, REFER TO PAGE 2***

Statement and Option

Conflicting File Attribute or
Qrganizatio!!

Any record I/O statement
Any stream I/O statement
READ SET
READ EVENT
READ KEY
READ IGNORE
WRITE

STREAM
RECORD
UNBUFFERED
BUFFERED
REGIONAL SEQUENTIAL or CONSECUTIVE
DIRECT
INDEXED or VSAM SEQUENTIAL UPDATE
INDEXED DIRECT NOiRITE
REGIONAL (not KEYED)
BUFFERED
INPUT or OUTPUT
UNBUFFERED or DIRECT
SEQUENTIAL
BUFFERED
INPUT or OUTPUT
VSAM (ESDS)
INPUT or UPDATE
UNBUFFERED
DIRECT
INDEXED or REGIONAL (without KEYED)
or VSAM (ESDS)
OUTPU'l'
INPUT

WRITE EVENT
REWRITE
REWRITE (without FROM)
REWRITE KEY
REWRITE EVENT
DELETE
LOCATE
LOCATE KEYFROM
GET
PUT
PrQg~gr

ResEo~:
Ensure that the file declaration and the
input/output statements for that file are compatible.

IBM8111

I/O ERROR.

CAUSE NOT KNOWN FOR FILE FILENAME

ExBlanation:
The data management routines have detected an
error during an input/output operation, the cause of which
could not be determined explicitly.
~~~ammer ~esponse:

If the error recurs after resubmitting
the job, use PLIDUMP to obtain a storage dump and retain all
the relevant documentation for study by IBM.

IBM8121

NO PRECEDING 'READ SET' OR 'READ INTO' FOR 'REWRITE' ON FILE
FILENAME
Explanati2n:
A REWRITE statement has been executed for which
no preceding READ statement, either with the INTO option or
with the SET option, has been executed.
Programmer Response:
Modify the program so that either the
RgWRITE statement is preceded by a READ statement or the
REWRITE statement is replaced by a WRITE statement; according
to the requirements of the program.

18M8131

LAST 'READ' BEFORE THIS 'REWRITE' IS INCOMPLETE FOR FILE
FILENAME

***8EFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

Explanation:
A REWRITE statement has been attempted before the
preceding READ statement with the EVENT option has been
completed.
Progra~Respo~:
Include a WAIT statement so that the READ
statement is complete before the REWRITE statement is executed.

IBM8141

TOO MANY INCOMPLETE I/O OPERATIONS
Explanation:
An attempt has been made to initiate an
input/output operation beyond the limit imposed by the
operating system.
Programmer Response:
Modify the p£ogram so that the
input/output operation is not initiated until an incomplete
input/output operation has been completed.

IBM8161

IMPLICIT 'OPEN' UNSUCCESSFUL FOR FILE FILENAME
ExElgnation:
An error has occurred during the implicit opening
of a file.
The UNDEFINEDFILE condition was raised and a normal
return was made from the associated on-unit, but the file was
still unopened.
R£Qg£~~~~ponse:

Ensure that the file has been completely
and correctly declared, and that the input/output statement
that implcitly opens the file is not in conflict with the file
declaration.

IBM818I

UNEXPECTED END OF FILE STRING DETECTED IN STREAM INPUT
]~Bl~~atiQn:

The end of the file has been detected before the
completion of a GET FiLE statement.

Programmer Response:
For edit-directed input, ensure that the
last item of data in the stream has the same number of
characters as specified in the associated format item.
If the
error occurs during execution of an X-format item, ensure that
the same number of characters to be skipped are present before
the last data item in the stream.
For list-directed and data-di~ected input, ensure that the last
item of data in the data set, if a string, is terminated by a
quote character and a 'B', if a bit string, that precedes the
end-of-file marker.
IBM821I

I/O STATEMENT OCCURRED BEFORE PREVIOUS 'READ' COMPLETED BY
'WAIT' FOR FILE FILENAME
]XE1anation:
While an indexed sequential file was open for
direct updating, an input/output statement was attempted before'
the completion of a previous READ statement with the EVENT
option.

Execution-Time

(IBM)

Messages

***bEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

Programme~espon~:
Include a WAIT statement so that the
erroneous input/output statement cannot be executed until the
completion of the previous READ statement with the EVENT
option.

IB"5221

NO SPACE FOR RECORD IN SEQUENTIAL OUTPUT DATA SET.
WITH THE fILENAME

ASSOCIATED

Explanation:
There is insufficient space on the data set in
which to add the record transmitted by this statement.
For
regional data sets, this can be caused by a WRITE or LOCATE
statement that specifies a region that is beyond the limit
established for the data set.
Programmer Response:
Enlarge the extent made available to the
data set.
For regional data sets, check that the region used
in a WRITE or LOCATE statement can be contained in the enlarged
data set.
IBMe231

INVALID CONTROL

FOR~AT

ITEM FOR GET/PUT STRING.

~planati~:

An invalid control format item (PAGE, LINE, SKIP,
or COL) has been detected in a remote format list for a GET or
PUT STRING statement.
For example:
DCL(A,B) CHAR(10),
C CHAR (80) ;
F:
FORMAT(A(10), SKIP,A(10»;
A='FRED'; B = 'HARRY';
PUT STRING (C) EDIT (A, B) (R (F»

;

Programmer Respon~:
Modify the source program so that GET or
PUT STRING statements do not attempt to use invalid control
format items in remote format lists.
IBM8251

EVENT VARIABLE ALREADY IN USE WITH FILE
~~lanati~:

An input/output statement with an EVENT option
has been attempted while a previous input/output statement with
an EVENT option that uses the same event variable is still
incomplete.

grogramm~~esponse:

Either change the event variable used in
the second EVENT option or insert a WAIT statement for the
event variable between the two input/output statements.

11"8261

EVENT VARIABLE ALREADY IN USE WITH DISPLAY STATEMENT
Explanation:
An input/output statement with an EVENT option
has been attempted while a previous DISPLAY statement with an
EVENT option that uses the same event variable is still
incomplete.

36
***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

Programmer Response: Either change the event variable used in
the second EVENT option or insert a WAIT statement for the
event variable between the DISPLAY statement and the
input/output statement.
IBM8281

INCORRECT SEQUENCE OF I/O OPERATIONS ON AN ASSOCIATED FILE
Explanation: Operations on a set of associated files were not
carried out in the correct sequence, as follows:
1. Appropriate I/O operations were not carried out in the
sequence Read-Punch-Print. Only the Print operation may be
omitted.
2. An attempt was made to print more than the maximum number
of lines on a card, using a print file that was associated
with a read or a punch file.

IBM8291

INSUFFICIENT VIRTUAL STORAGE AVAILABLE TO VSAM.
Explanation: During an OPEN/CLOSE or any other operation on a
VSAM data set insufficient virtual storage was available for
workspace and control blocks or for VSAM routines.
Insufficient virtual storage may occur in the partition, or in
the shared virtual area (SVA).

IBM8301

I/O ERROR DURING 'CLOSE'.
Explanation: An I/O error occurred while a VSAM close routine
was either reading or writing a catalog record, or completing
an outstanding I/O request.

IBM8311

NO POSITIONING ESTABLISHED FOR SEQUENTIAL READ.
Explanation: A READ statement without the KEY option has been
attempted on a VSAM data set, after sequential positioning has
been lost as the result of a previous error during sequential
processing (for example, read error on index set).

IBM8321

INSUFFICIENT SPACE FOR VSAM DATA SET.
Explanation: VSAM has been unable to allocate additional DASD
space for the data set (ESDS or KSDS). The condition is raised
on attempting to write or locate a record during the sequential
creation or extension of such a data set when the space
allocated to the data set is full. For a KSDS, the condition
may also occur when the associated PL/I file is opened for
update and attempts are made to write new records or to
increase the size of existing records by the WRITE and REWRITE
statements respectively.

IBM834I

REQUESTED RECORD LIES ON NON-MOUNTED VOLUME.
Explanation: The requested record lies on a non-mounted volume
of a VSAM data set spanning several volumes.

Execution-Time (IBM) Messages
***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

IBM835I

ATTEMPT TO REPOSITION FOR SEQUENTIAL READ FAILED.
Explanation: The attempt to reposition to the next highest key
for subsequent sequential retrieval on a VSAM KSDS, after the
'key not found' condition, has failed. If processing of the
file is continued, the next I/O statement should have a
positioning KEY option.

IBM836I

TOO MANY CONCURRENT OPERATIONS ON DATA SET.
Explanation: Several files may be accessing a VSAM data set by
means of the same DLBL statement (that is, using the same
title), but only one I/O operation may be active on the data
set at any given time. In addition, a READ-REWRITE pair on a
SEQUENTIAL UPDATE file counts as one operation, and also leaves
a position established.

IBM837I

ERROR IN INDEX UPGRADE.
Explanation: A change to a base cluster cannot be reflected in
one of the indexes of the cluster's upgrade set.

IBM838I

MAXIMUM NUMBER OF ALTERNATE INDEX POINTERS EXCEEDED.
Explanation: The maximum number of pointers allowed in an
alternate index depends on the record length specified for the
alternate index, but cannot exceed 2.::'i overall maximum of 32767.

IBM839I

INVALID ALTERNATE INDEX POINTER.
Explanation: A pointer in the alternate index is invalid.
This can be caused by incorrect use of the alternate index as a
Key Sequenced Data set (KSDS).

IBM840I

INVALID SEQUENTIAL WRITE.
Explanation: A WRITE statement on a file associated with a
Relative Record Data Set (RRDS) did not specify a relative
record number. This resulted in an attempt to write in a slot
already containing a record.

IBM850I

AGGREGATE LENGTH EXCEEDS 2**24 BYTES
Explanation: The length of the structure or array to be mapped
is greater than 2 2 - thereby exceeding the limits of
addressability.
Programmer Response: Reduce the s~ze of the array or structure
to a size that can be accommodated within the main storage
available. If a variable is used to specify the dimension or
length, check that it has been correctly initialized before the
storage is allocated to the aggregate.

IBM851I

UNABLE TO MAP ARRAY STRUCTURE ELEMENT

40
***BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

Explanation: The program contains a structure with an
adjustable element and an array element with extents that cause
the relative virtual origin to exceed (2 32 )-1. For example:
DCL 1 A,
2 B CHAR(N),
2 C (32766:32767,32766:32767,32766:32767)
CHAR(32767);
Programmer Response: Ensure that aggregates ~ith array
elements remain within the limit of addressability (2 32 ) .
IBM852I

AGGREGATE CANNOT BE MAPPED IN COBOL OR FORTRAN
Explanation: An attempt has been made to either pass to or
obtain from a FORTRAN routine an array of more than 7
dimenSions, or to pass to or obtain from a COBOL routine a
structure with more than three levels.
Programmer Response: Ensure that PL/I aggregates, passed to or
from COBOL or FORTRAN routines are within the limits described
above.

Execution-Time (IBM) Messages
••• BEFORE CALLING IBM FOR PROGRAMMING SUPPORT, REFER TO PAGE 2***

40.1

18"8801

PROGRA~

CHECK HAS OCCURRED IN THE

SORT/~ERGE

PROGRA~

Expl~nati2n:
An error has occurred during execution of the
sort/merge program when invoked from a PL/I program by .~~ns of
the PL/I sort interface facilities.
The sort program W4S
unable to continue and control has been passed to the PL/I
error-handler.

Prog~ammeK-Response:
Since the problem has occurred during
execution of the sort/merge program, refer to the appropriate
sort/merge program manual for an explanation of any diagnostic
messages produced by the sort program and for any other
information that may be necessary to correct the fault.

IB~9001

'WAIT' STATEMENT WOULD CAUSE
TERMINATED

(E1)
WAIT (E1) ;

CO~PLETION

PER~ANENT

WAIT.

PROGRA~

'O'B;

Expl~nation:

A WAIT statement that can never be coapleted hag
been encountered.
In the example, the event E1 is inactive
and incomplete.
PrQgra..!!!..!!!~Eespo.!!.§~:
~odify the program so that the WAIT
statement can never wait for an event that is inactive and
incomplete.

IB~9211

GOTO OUT OF ON-UNIT
SUBROUTINE TO FAIL

~AY

CAUSE FURTHER USE OF THIS COBOL

ExEl~na!ion:
If a COBOL subroutine is reinvoked after an
interrupt in the previous invocation was handled by a PL/T
on-unit that was terminated by a GOTO statement, the COBOL
subroutine will fail.

IB~9251

PLIRETC VALUE REDUCED TO 999.
Expl~nation:

The value passed to the PLIRETC built-in
procedure is greater than 999.
The value has been reduced
to 999 which is the maximum permitted user value.

Execution-Time
***BEPORi'CALLING IB~ fOR PROGRA~~ING

(IB~)

Messages

suppbst, REFER TO PAGE 2***

SC33-0035-2

c:
C'"
~

"T1

c;;-

z
!=>
(/')

W
0'>

(»
W

'-I

o
N
c.o
iJ
~.

:::l

r-+

c..
:::l

en
~

(/')

(')

w
w

6o
w

CJ1

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.3
Linearized                      : No
XMP Toolkit                     : Adobe XMP Core 4.2.1-c043 52.372728, 2009/01/18-15:56:37
Create Date                     : 2012:06:12 15:02:22-08:00
Modify Date                     : 2012:06:12 16:46:23-07:00
Metadata Date                   : 2012:06:12 16:46:23-07:00
Producer                        : Adobe Acrobat 9.51 Paper Capture Plug-in
Format                          : application/pdf
Document ID                     : uuid:6e8d7fdd-ccd2-4eb0-b670-eb37b59f9884
Instance ID                     : uuid:6619c798-7aea-413b-b2a1-bdf9d3b8a458
Page Layout                     : SinglePage
Page Mode                       : UseNone
Page Count                      : 52

EXIF Metadata provided by EXIF.tools

SC33 0035 2_DOS_PLI_Transient_Library_Messages_Aug77 2 DOS PLI Transient Library Messages Aug77

SC33-0035-2_DOS_PLI_Transient_Library_Messages_Aug77 SC33-0035-2_DOS_PLI_Transient_Library_Messages_Aug77

Navigation menu

Versions of this User Manual:

Views

Navigation