HP 3000 Manuals HP 3000 Manuals
List of Messages 001 - 078
001 Insufficient buffer space (recoverable)
* You have tried to open a file directly or indirectly and,
although you have not exceeded your system's file limit,
something in your system is unable to allocate enough
memory space for this operation.
* Although you can trap this error you must do STOP RUN as
soon as it is reported.
002 File not open when access attempted (recoverable)
* You have tried to access a file without opening it first.
* Open the file with the open mode that you need and try
the operation again. As this error implies there your
program contains a mistake in its logic, you may want to
terminate the run and recode your program.
003 Serial mode error (recoverable)
* You have tried to open a device as a relative or indexed
file.
You are trying to execute a device, not a program.
* Open the device in the correct mode or close any open
files, do STOP RUN and recode your program.
The name of your program is recognized by the Operating
System as a valid device. Rename your program.
004 Illegal file name (recoverable)
* A file-name contains an illegal character. This could be
any character that is not part of the permitted character
set or it could be the system-dependent delimiter, which
on most systems is the space.
* Try the file operation again using the correct file-name.
005 Illegal device specification (recoverable)
* Devices to which your COBOL program can write are defined
by the operating system. You have tried to write to a
device that is not defined by your system.
* Try the operation again using a device name that your
system recognizes.
006 Attempt to write to a file opened for INPUT (recoverable)
* You have tried to WRITE to a file that is open only for
input.
* Close the file and open it with a mode such as I-O, which
allows you to write to the file. As this error implies
there is a mistake in your program's logic you may want
to terminate the run and recode your program.
007 Disk space exhausted (fatal)
* The disk is full.
* This error can be trapped, but once it has been reported
you must do a STOP RUN immediately to terminate your
program's run. When your program has terminated, delete
any files that you no longer need. Alternatively, if
your operating system supports this, put a new disk in a
floppy disk drive and redirect your program's file
operations to this.
008 Attempt to input from a file opened for OUTPUT (recoverable)
* You have tried to read from a file that is open only for
output.
* Close the file and open it with a mode such as I-O, which
allows you to read from the file. As this error implies
there is a mistake in your program's logic you may want
to terminate the run and recode your program.
009 No room in directory (recoverable)
* Either the directory is full, or your program cannot find
it.
* Either delete any files that you no longer need, or if
your operating system supports this, put a new disk in a
floppy disk drive and redirect your program's file
operations to this. Alternatively, specify a different
drive or directory for your file operations.
010 File name not supplied (recoverable)
* You have attempted to open a file that you have declared
as an external file, but have not named.
* Specify the external filename.
012 Attempt to open a file which is already open (recoverable)
* You have tried to open a file which is already open and
so cannot be opened again.
* Cancel your second attempt to open the file. If the fact
that the file is already open is acceptable to you,
continue to run your program.
013 File not found (recoverable)
* The operating system has been unable to find a file which
you have attempted to access in your program.
* Ensure that you are in the correct directory or that a
path to the file concerned exists. You can then attempt
the file operation again. If the error is the result of
a spelling mistake then ask for the correct file and
attempt the file operation again.
014 Too many files open simultaneously (recoverable)
* You have tried to exceed the maximum number of files
which you can have open at any one time. This may be a
software or an operating system constraint, but you must
not violate it.
* Close some of the open files which you are not currently
accessing, and then try to open the relevant file again.
You should then be able to continue to run your program.
Depending on your operating system, you may be able to
increase the maximum number of files you are allowed to
have open.
015 Too many indexed files open (recoverable)
* You have tried to exceed the maximum number of indexed
files which you can have open at any one time. This may
be a software or an operating-system restraint, but you
must not violate it.
* Close some of the open indexed files which you are not
currently accessing, and then try to open the relevant
file again. You should then be able to continue to run
your program. Note that indexed files count as two
files, one for data and one for the index.
016 Too many device files open (recoverable)
* You have tried to exceed the maximum number of device
files which you can have open at any one time. This may
be a software or an operating system constraint, but you
must not violate it.
* Close some of the open device files which you are not
currently accessing, and then try to open the relevant
file again. You should then be able to continue to run
your program.
017 Record error: probably zero length (recoverable)
* You have probably tried to access a record that has had
no value moved into it.
* Although this error is recoverable in the sense that it
can be trapped, once it has been reported you must
execute a STOP RUN statement immediately and then recode
your program to ensure that the COBOL record length is
not zero.
018 Read part record error: EOF before EOR or file open in wrong
mode (recoverable)
* A part record has been found at the end of a file.
Consequently your run-time system will treat the data
file as a record and not finding a full record will
report this error.
* Ensure that the record size you give when you read from
or WRITE to a file is consistent.
019 Rewrite error: open mode or access mode wrong (recoverable)
* You are attempting to do a REWRITE to a file that has not
been opened with the correct access mode for this
operation.
* Close the file and reopen it in a mode such as I-O, which
allows you to do REWRITE operations on that file. As
this error implies that your program contains a mistake
in its logic, you may want to close any open files and
then execute a STOP RUN. You can then recode your program
to eliminate the logic error.
020 Device or resource busy (recoverable)
* You have attempted to open a file that is assigned to a
device or resource (for example, a line printer) that is
not available at this time.
* You can trap the error status returned by open and retry
the open at regular intervals until it succeeds.
021 File is a directory (fatal)
* You have tried to WRITE to a directory instead of to a
file.
* You will have to recode your program so that it WRITEs to
a file and not to a directory.
022 Illegal or impossible access mode for OPEN (recoverable)
* The mode in which you are attempting to open a file
violates the General Rule of COBOL for that type of file;
for example you may have opened a line-sequential file in
the I-O mode.
* Open the file with a mode that is compatible with that
type of file.
023 Illegal or impossible access mode for CLOSE (recoverable)
* The mode in which you are attempting to close a file is
not possible for that type of file.
* Close the file with a new access mode which is compatible
with that type of file, or execute a STOP RUN statement
and recode your program.
024 Disk input-output error (recoverable)
* You may have performed a read after a WRITE, or there may
be either a verification failure or a parity error.
* In some circumstances this error will be fatal, but if it
occurs during a read you can trap it and then do a close
on the file before executing a STOP RUN statement.
025 Operating system data error (fatal)
* You are trying to set up terminal characteristics for a
device which is not a terminal.
* Recode your program.
026 Block I-O error (fatal)
* An error has occurred while you are attempting to access
a disk. This could be the result of a corrupt disk.
* If you have a corrupt disk try to run your program again
using your backup copy.
027 Device not available (recoverable)
* You are attempting to access a device which either is not
attached to your machine or if attached is not on-line.
* Attach the device to your machine and ensure that it is
on-line. Repeat the file operation.
028 No space on device (fatal)
* You have attempted a file operation such as WRITE for
which there is not sufficient space available on your
disk.
* When your program has terminated you will have to delete
some of the files or directories on your current logged
in disk. Ensure that you delete sufficient files on your
disk so that you have enough room to carry out successful
file operations.
029 Attempt to delete open file (recoverable)
* You have attempted to perform a DELETE FD operation on an
open file.
* Close the file before performing the DELETE FD operation.
030 File system is read-only (recoverable)
* The file system which you are using is read only, which
effectively means that it is write-protected. You have
tried to change a file in some way, for example you may
have tried to WRITE to a file or to DELETE information in
it.
* You will have to abandon your attempt to alter the file
unless you can make your own personal copy of it. You
should then be able to alter the contents of your copy,
but not of the original source.
031 Not owner of file (recoverable)
* You are attempting an operation on a file but the file's
owner has not given you the necessary permission for that
operation. You could for example be attempting to alter
the access modes for a file, which only the file's owner
can do.
* You will have to abandon your attempted file operation
unless the file's owner gives you the permission
necessary to do the operation you wish to carry out.
032 Too many indexed files, or no such process (recoverable)
* You have tried to open an indexed file but the number of
files that you currently have open is the system limit.
Alternatively, you could be trying to use a process id
which does not exist, or which your operating system no
longer recognizes.
* You will have to close some of the indexed files which
you are no longer accessing, and you should then be able
to open the file you require.
In this case you must rewrite your code so that it uses a
process id which your system recognizes.
033 Physical I-O error (fatal)
* You have a hardware error of some type, perhaps you have
not put a disk in the relevant drive or you may have
tried to WRITE to a disk but the processor detected
hardware interface has failed.
* You will have to try to correct the fault in your
hardware; for example put a disk in the necessary drive.
034 Incorrect mode or file descriptor (recoverable)
* You are either trying to write to a file which is open
for read purposes only, or read a file which is open for
write purposes only.
* You will need to close the file and reopen using the
correct access mode. As this error implies that there is
a mistake in the logic of your program you may want to
close any open files, execute a STOP RUN statement and
then recode your program to eliminate the logic error.
Note that shareable files opened INPUT (read-only) by the
COBOL system will still require write-permission (from
the operating system) to enable temporary locking to take
place.
035 Attempt to access a file with incorrect permission (recoverable)
* You are attempting a file operation which you do not have
sufficient permission to achieve. For example you could
be trying to write data to a file which has been set up
with the read attribute only.
* If you are the owner of the file you will be able to
alter the attributes of the file so that you have the
permission needed to effect the particular file operation
you were attempting. If you are not the owner of the
file you will not be able to carry out that operation
successfully unless you copy the file and make the
changes to the copy only. You will not be able to alter
the source file.
036 File already exists (recoverable)
* You are attempting an inappropriate operation on an
already existing file.
* As this error implies a fault in your program's logic you
may like to recode your program to eliminate this
mistake.
037 File access denied (fatal)
* Your attempt to access a file has been denied by the
operating system. You may have tried to write to a
write-protected file or you could have attempted to read
from an output device.
* Alter the access permission on the relevant file. Access
can be read-only, if you just want to read the contents
of the file without making any changes, or it can be read
and write in which case you will be able to alter its
contents.
038 Disk not compatible (fatal)
* You have tried to load a disk that is incompatible with
the current version of your operating system. This could
be because it was created under a previous version of the
system or it could have been created under a completely
different operating system. You would also receive this
error if you tried to load a disk with a name that
clashed with a disk that was already loaded.
* If the error is a result of a clash of names you can
rename one of the disks and then you will be able to load
both disks together if this is what you require.
039 File not compatible (fatal)
* You are trying to load a file that is not compatible with
the structure of files under the current release of your
software. This could be because the file was created
either under a different operating system or under a
previous version of your current system.
* You will need to create a new copy of the file which has
the correct structure.
040 National Language Variants not set up correctly (fatal)
* You have attempted to use the additional language
variants, but the environment or side file that is
required to set up the language either has not been set
up correctly, or does not exist, or is invalid.
Alternatively, your system cannot find COBNLS.DLL or
COBNLS.DLE.
* Set up the required environment or side file before you
attempt to run the program again.
Ensure that COBNLS.DLL is present in UTILS.LBR, or that
COBNLS.DLE is present in COBDIR.
041 Corrupt indexed file (recoverable)
* Your run-time system does not recognize the control
information for an indexed file and as the index has been
corrupted in some way the data within the file is no
longer accessible by your system. This error is
recoverable in the sense that it can be trapped but
should you receive it there is little you can do except
to close any open files and stop your program's run.
* You will have to rerun your program using the backup copy
of that file. If you have added a great deal of
information to the file since you last took a backup you
may like to rebuild the file using the Rebuild utility,
which will read the data (if this has not been corrupted)
and build a new index for it. See also
042 Attempt to write on broken pipe (recoverable)
* Your program has created a process as a result of a DD_
logical filename mapping assignment (for example, the
process may be a line printer spooler). The process was
not created properly, or has died prematurely. This
error occurs when your program attempts to write to the
process.
* You can trap the error status returned by the write
operation, then open the file again.
043 File information missing for indexed file (fatal)
* The system has crashed on your program's previous run,
while the file was open. Information was probably added
to the end of the file, but the directory information was
not updated and so that data cannot be accessed by your
system. Alternatively, you have copied the indexed file
from one disk to another but have copied either only the
data part of the file or only the index.
* If the error is the result of a crash then whether you
can access the necessary data or not is entirely system
dependent. If, however, it is the result of a faulty
copy you should be able to restore the missing part of
the file from the .dat or .idx file.
045 Attempt to open an NLS file using an incompatible program
(fatal)
* The NLS control information for a file within your
program does not match the same NLS control information
in the header of your index file. Alternatively, your
index file has become corrupted.
* Rebuild your index file, or rerun your program using the
backup copy of that file. If you have added a great deal
of information since you last took a backup, you may wish
to rebuild the file using a utility that is able to read
the data, if it is not corrupt, and build a new index for
it.
046 NLS support module not found (fatal)
* You have compiled your program with the NLS directive,
but the National Language Support module (COBNLSMG) has
not been found.
* If you encounter this message from a linked executable,
you must relink your program with COBNLSMG.
047 Indexed structure overflow (fatal)
* There is some fault in the structure of your indexed
file. You have probably tried to put another entry in
the index when there is no room for it.
Alternatively, you have tried to access an old format
indexed file, created perhaps using CIS COBOL.
You may have more than 64K duplicates for a key.
* If there is no room in your index for further entries you
will have to reorganize your file.
Run the Rebuild utility to check the consistency of this
indexed file, and to construct a new indexed file if the
old one was found to be corrupt. See your COBOL System
Reference for details of the Rebuild utility.
Recompile your program with IDXFORMAT"4"
048 Attempt to divide by zero (fatal)
* You are executing a program that is attempting to divide
by zero.
* Either recode your program so that you can trap the error
with an ON SIZE ERROR clause, or run your program without
the RTS O switch set, or recompile your program without
the CHECKDIV(OSVS) directive set.
065 File locked (recoverable)
* You have tried to open a file which has already been
locked, or opened for output by another user.
Alternatively, you have tried to lock or open for output
a file which another user already has open.
* Your program can inform the system operator (if there is
one) that it is unable to access this file and should
wait until the other user has finished using the file and
closes it. You should then be able to continue to run
your program.
066 Attempt to add duplicate record key to indexed file (fatal)
* You have tried to add a duplicate key for a key which you
have not defined as being able to have duplicates.
* As this error implies that there is a fault in the logic
of your program you will probably need to recode.
067 Indexed file not open (recoverable)
* You are attempting to access an indexed file which you
have not opened.
* Open the file in the relevant access mode and then retry
the unsuccessful file operation.
068 Record locked (recoverable)
* You have tried to access a record which is currently
locked by another user.
* Your program can inform the system operator (if there is
one) that the record is currently locked, and you should
then wait until the other user has released the lock on
that record. You should then be able to access the
relevant record. You should not continually retry to
gain access to the record without operator intervention,
as this could result in your application hanging.
069 Illegal argument to ISAM module (fatal)
* This is the result of an internal system error.
* Contact Technical Support who will try to help you
discover the cause of your error and how it can be
rectified.
070 Too many indexed files open (recoverable)
* You are attempting to open an indexed file but you have
already exhausted the system limit which specifies how
many of these files can be opened at any one time.
* Close some of the open indexed files which you are not
currently accessing. You should then be able to open the
indexed file which you require and to continue the
program run.
071 Bad indexed file format (fatal)
* You are either using a file which has been corrupted, or
there is an internal system error.
* If the disk you are using is corrupt, rerun your program
using your backup copy of the disk. If this is not the
cause of the error then you should contact Technical
Support who will try to discover the cause of your error
and how it can be rectified.
072 End of indexed file (fatal)
* This is the result of an internal system error.
* Contact Technical Support who will try to help you
discover the cause of your error and how it can be
rectified.
073 No record found in indexed file (fatal)
* This is the result of an internal system error.
* Contact Technical Support who will try to help you
discover the cause of the error and how it may be
rectified.
074 No current record in indexed file (fatal)
* This is the result of an internal system error.
* Contact Technical Support who will try to help you
discover the cause of the error and how it may be
rectified.
075 Indexed data file name too long (fatal)
* The maximum number of characters that the UNIX system
allows a file name to have is 14. However, when creating
indexed files, the extension .IDX is added to the end of
the user-defined file name, and so your file name must
not exceed 10 characters in length.
* Rename the file with a shorter file name, that is, one
that is less than 10 characters in length.
076 Can't create lock file in /ISAM directory (fatal)
* For some reason your system is unable to create a lock
file in the /ISAM directory. One reason for this could
be that in its previous run your program terminated
abnormally (perhaps due to a power failure) leaving some
files locked.
* You will have to manually remove all of the files that
are still locked from the /ISAM directory before you can
successfully run your program.
077 Internal ISAM module error (fatal)
* This is the result of an internal system error.
* Contact Technical Support who will try to help you
discover the cause of your error and how it can be
rectified.
078 Illegal key description in indexed file (fatal)
* This is the result of an internal system error.
* Contact Technical Support who will try to help you
discover the cause of your error and how it can be
rectified.