HP 3000 Manuals HP 3000 Manuals
List of Messages (074 - 171)
074 No current record in indexed file (Fatal)
* This is the result of an internal system error.
* Contact Technical Support who will help you discover
the cause of the error and how it can be rectified.
075 Indexed data file name too long (Fatal)
* When creating indexed files, the extension .idx is
added to the user-defined file-name, and so your
file-name must not exceed x-4 characters in length,
where x is the maximum length of file-name. See your
COBOL System Reference for details.
* 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 should 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 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 help you discover
the cause of your error and how it can be rectified.
079 COBCONFIG syntax error (Fatal)
* An error exists in the run-time configuration sidefile
accessed via the environment variable COBCONFIG.
* Check your syntax against your COBOL System Reference.
You might have used incorrect syntax, or syntax that
is not compatible with the type of RTS tuneable you
are configuring (this could include assigning an
illegal value to the RTS tuneable).
081 Key already exists in indexed file (Fatal)
* This is the result of an internal system error.
* Contact Technical Support who will help you discover
the cause of your error and how it can be rectified.
082 CALL convention not supported (Fatal)
* The CALL convention you have specified is not
supported.
* See your COBOL User Guide for a list of supported CALL
conventions.
086 Remote file system failure (Fatal)
100 Invalid file operation (Fatal)
* You have tried a file operation which violates a
general rule of COBOL in some way. The most likely
cause of this error is that you have tried a rewrite
on a sequential file opened I-O, or on a relative file
with access mode sequential also opened I-O, without
preceding it with a successful read NEXT.
* Recode your program to ensure that the REWRITE
statement in error is preceded by a read NEXT.
101 Illegal operation on an indexed file (Fatal)
* This is the result of an internal system error.
* Contact Technical Support who will help you discover
the cause of your error and how it can be rectified.
102 Sequential file with non-integral number of records (Fatal)
* You have either specified an incorrect record length
for a sequential file, or the sequential file you are
trying to access is corrupt in some way, or the file
which you have specified is not a sequential file.
* Recode your program so that it specifies the correct
type of file, or if the error is the result of a
corrupt file, try to run the program again using a
backup copy of that file.
103 Parameter cannot be passed BY VALUE (Fatal)
104 Null file name used in a file operation (Fatal)
* You specified a data-name for a file-name instead of a
literal, and the data item contained only spaces when
you tried to open the file.
* Recode your program specifying the correct file-name.
105 Memory allocation error (Fatal)
* The run-time system is unable to allocate sufficient
memory space to successfully carry out the tried
operation, probably because of insufficient memory
space on your system.
* You should obtain more memory in which to run your
program. Refer to your operating system documentation
for details of how you can obtain more memory, if this
is possible.
106 Dictionary error (Fatal)
* This could be the result of a read or write error to
file or disk, but it is more likely to be the result
of an internal system error.
Alternatively, your application might have called many
programs without canceling them afterward, so that
memory becomes exhausted during Animation.
* Contact Technical Support who will help you to
discover the cause of your error and how it can be
rectified.
Ensure that as much memory as possible is available
during Animation by CANCELing any program you do not
currently need to access.
107 Operation not implemented in this Run-Time System (Fatal)
* You are trying to perform a file operation which your
run-time system does not support.
* You should recode your program so that it does not try
such operations, or you should acquire a version of
your system that does support this facility.
108 Failure to initialize data division (Fatal)
* The run-time system cannot load your program properly
because the data needed to correctly initialize the
Data Division has become corrupted.
* You should compile your program again to try to obtain
good intermediate code.
109 Invalid checksum in Run-Time System (Recoverable)
* The internal information in the run-time system has
been altered. The run-time system might have become
corrupted, or you might have illegally tried to change
the internal run-time system information.
110 Generated code not supported by this RTS (Fatal)
* Contact Technical Support who will help you to
discover the cause of the error and how it can be
rectified.
114 Attempt to access item beyond bounds of memory (Fatal)
* Memory access violation has been detected by your
operating system.
115 Unexpected signal (Fatal)
* A signal the run-time system was not expecting has
been caught.
116 Cannot allocate memory (Fatal)
* For some reason a part of your run-time system is
unable to allocate you sufficient memory to enable you
to execute your code.
* You should try to reduce memory usage by canceling
programs that are not in use, then try the operation
that caused this message again.
117 Bad collating sequence (Fatal)
* This is an internal system error.
* Please contact Technical Support who will help you to
discover the cause of the error and how it can be
rectified.
118 Symbol not found (Fatal)
* You are unable to load your object file. You have
tried to call a program that has not been specified in
the COBPATH environment variable.
* Check that your COBPATH has been set up correctly. If
not, revise your COBPATH to include the program being
called.
119 Symbol redefined (Fatal)
* You are unable to load your object file because it has
an entry point with the same name as a module already
loaded.
* Once your program has terminated recode it to remove
the naming duplication. Resubmit your program to your
COBOL system.
120 Symbol string table of zero size (Fatal)
* You probably have a malformed object file.
* Once the program has terminated you must correct your
object file. If this does not work, contact Technical
Support who will help you to discover the specific
cause of the error.
121 Symbol is not in TEXT section (Fatal)
* You have tried to call a subprogram that is not an
executable program.
Alternatively, you have used the same name for a
called program as for a previously defined data item.
* Check that the subprogram being called is an
executable one. If required, correct the subprogram's
name in the calling program and resubmit it to your
COBOL system.
Once your program has terminated, recode it to remove
the naming duplication. Resubmit your program to your
COBOL system.
122 Coblongjmp() called below level of cobsavenv() (Fatal)
* You might have returned control to a higher level in
the CALL/PERFORM hierarchy than the level at which
cobsetjmp was called. Coblongjmp must be called only
from the same or from a lower level in the
CALL/PERFORM hierarchy as cobsavenv was. See your
COBOL System Reference for details of cobsavenv and
coblongjmp.
* Check and correct the logic of your program, and then
resubmit your program to your COBOL system.
123 Unknown relocation type (Fatal)
* You are using incompatible versions of the object file
and the COBOL run-time library.
* Once the program has terminated, resubmit your object
file to your COBOL system with the current version of
your COBOL run-time library. If this does not work,
contact Technical Support who will help you to
discover the specific cause of the error.
124 Communication failure during I/O request to the central file
handler
125 All locks/ current transactions canceled due to exceeding
time limit
126 Record size exceeds system limit (Fatal)
129 Attempt to access record zero of relative file (Recoverable)
* The value specified in the RELATIVE KEY data item
contains the value zero.
* You should ensure that the value in the RELATIVE KEY
data item is greater than zero, then continue to run
your program.
135 File must not exist (Recoverable)
* The operating system has been unable to find a file
which you have tried 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 try
the file operation again. If the error is the result
of a spelling mistake then ask for the correct file
and try the file operation again.
137 Illegal device specification--not mass storage
138 File closed with lock--cannot be opened (Recoverable)
* You are trying to open a file which you previously
closed with lock, which violates one of the general
rules of COBOL programming.
* You cannot open the relevant file. As this error
implies that your program logic contains a mistake,
you might want to close any remaining open files,
execute a STOP RUN statement and recode.
139 Record length or key data inconsistency (Recoverable)
* A discrepancy exists between the length of a record,
or the keys which you have specified, in your current
program and its definition in the program in which it
was first opened.
* Your program has a fault, so you probably should edit
your code, then resubmit it to your COBOL system
before running it again.
141 File already open--cannot be opened (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 and
continue to run your program if the fact that the file
is already open is acceptable to you. However as this
error implies that your program logic contains a
mistake, you might want to close any open files,
execute a STOP RUN statement and then recode.
142 File not open--cannot be closed (Recoverable)
* You have tried to close a file which is not open which
is impossible to achieve.
* You can abandon your attempt to close the relevant
file and continue to run your program. However, as
this error implies that your program logic contains a
mistake, you might want to close any open files,
execute a STOP RUN statement and then recode.
143 Rewrite/delete in sequential mode not preceded by successful
read (Recoverable)
* You have failed to do a successful read on a
sequentially accessed file trying a REWRITE or DELETE
on some of the information contained in that file.
* If the previous read was successful then perform a
read on the relevant file before you retry the
unsuccessful REWRITE or DELETE operation. If the
previous read was also unsuccessful close the file,
execute a STOP RUN statement and then recode your
program before you next run it.
144 Boundary violation (Recoverable)
* You have tried to write a record to a variable length
record file, the length of which is not within the
defined range for that file.
* Recode your program.
146 No current record defined for sequential read (Recoverable)
* The file position indicator in your file is undefined
owing to a failed read/START or INVALID KEY condition.
You have tried to read another record in the file but
as the current record is undefined the system cannot
find the start of the record for which you have asked.
* You should try a START operation, and continue to do
so until the file position indicator is updated
successfully.
147 Wrong open mode or access mode for read/start (Recoverable)
* You have tried to carry out a read or START operation
on a file which has not been opened for INPUT or I-O,
or which is not open at all.
* Open the file for I-O or for INPUT and you should then
be able to continue to run your program. However, as
this error implies that your program logic contains a
mistake, you might want to close any files which are
open, execute a STOP RUN statement and then recode.
148 Wrong open mode or access mode for write (Recoverable)
* You have tried to write to a file in sequential access
mode that you have not opened for OUTPUT or EXTEND, or
you have tried to write to a file in random or dynamic
access mode that has not been opened INPUT or I-O, or
which is not open at all.
* Close the file and reopen it with the correct open
mode for the file type. However, as this error
implies that your program logic contains a mistake,
you might want to close any files that are open,
execute a STOP RUN statement and then recode.
149 Wrong open mode or access mode for rewrite/delete
(Recoverable)
* You are trying to do a REWRITE or a DELETE on a file
that you have not opened for I-O, or which is not open
at all.
* Close the file and reopen for I-O. However, as this
error implies that your program logic contains a
mistake, you might want to close any open files,
execute a STOP RUN statement and then recode.
151 Random read on sequential file (Recoverable)
* You are trying to do a random read on a file which has
sequential organization.
* Read the file with the correct access mode. As this
error implies that your program logic contains a
mistake, you might like to close any files which are
open, execute a STOP RUN statement and recode.
152 REWRITE on file not opened I-O (Recoverable)
* You have tried a REWRITE on a file that is not open
I-O.
* Close the relevant file and open it for I-O
operations. You should then be able to carry out the
REWRITE operation successfully. However, as this
error implies that your program logic contains a
mistake, you might want to close any open files,
execute a STOP RUN statement and then recode.
153 Subscript out of range (Fatal)
* A subscript which you have used in your program is out
of the defined range, that is, it is either less than
one or it is greater than the number of occurrences of
the item.
* You should recode your program.
154 PERFORM nested too deeply (Fatal)
* This error usually results if you have used GO TO to
jump out of the range of a PERFORM rather than to jump
to an EXIT statement at the end of its range.
* When your program has terminated you should to recode
your program to ensure that the GO TO in question
jumps to an EXIT statement at the end of the PERFORM's
range.
155 Illegal command line (Fatal)
* The run-time system does not recognize as valid the
command line format you have specified.
Alternatively, the generic command-line interpreter,
which must be present if your program is to be run
successfully, is not found on your system.
Alternatively, you have set an invalid COBSW value.
* Rerun your application with a valid command line.
Make sure that the interpreter is present to enable
your system to pick up the commands correctly and then
rerun your program.
Reset COBSW to a valid value.
156 Too many parentheses in compute statement (Fatal)
* You have coded a COMPUTE statement which is too
complex for your system to handle successfully.
* You should recode your program. We strongly advise
you to break the relevant COMPUTE statement into a
number of simpler statements.
157 Not enough program memory: object file too large to load
(Recoverable)
* Either your program is too large for the available
memory space, or the stack is full.
* If you have specified the ON OVERFLOW/EXCEPTION clause
in the relevant CALL statement, the error is
recoverable. Any associated imperative statement is
executed before the next instruction.
158 Attempt to REWRITE to a line-sequential file (Recoverable)
* You have used the REwrite statement in conjunction
with a file whose organization is line sequential.
The REWRITE statement cannot be used with line
sequential files.
* Close the file in error before executing a STOP RUN
statement to ensure that you do not lose any data from
it. Recode your program to make the organization of
the file to which you want to do a REWRITE either
sequential, indexed sequential, or relative.
159 Malformed line-sequential file (Recoverable)
* A line-sequential file which you are trying to access
is corrupt in some way.
* Rerun your program using the backup copy of that file.
160 Overlay loading error (Recoverable)
* An error has occurred while trying to load the
intermediate code for an independent segment. The
segment is either missing or corrupted in some way.
* If the segment is missing, locate it. If you cannot
find it, or if it is present and corrupt, resubmit
your program to your COBOL system.
161 Illegal intermediate code (Fatal)
* The intermediate code which is currently being
processed is not valid code. You are probably trying
to execute a corrupted file or one which has not been
submitted to your COBOL system successfully.
* You should resubmit your source program to your COBOL
system, to try to obtain uncorrupted intermediate
code.
162 Arithmetic overflow or underflow (Fatal)
* You are executing a program that is trying to perform
a floating-point divide by zero.
* You should recode your program to avoid this illegal
operation.
163 Illegal character in numeric field (Fatal)
* By default the value which you enter into a numeric or
numeric edited field is checked to ensure that it is
numeric. You have entered either nonnumeric
characters or uninitialized numerics into numeric or
numeric edited fields: these are automatically space
filled and are thus classified as nonnumeric items.
* You must adjust your code so that no invalid data is
used. You can locate the invalid numeric data in your
code by setting the +F switch on, and animating your
program until you receive this error. You might need
to use one of the Compiler directives, BADSIGNS,
HOST-NUMCOMPARE, SIGNCOMPARE or SPZERO, to resolve
invalid data in numeric fields. See your COBOL System
Reference for details of these directives.
164 Run-Time subprogram not found (Fatal)
* You have tried to call a subroutine whose entry
address has not been set up in your run-time system.
* Check to see that you used a valid call number in the
unsuccessful subroutine call. If not, revise your
code to contain a call number which your system
recognizes. If you did use a valid call number but
still received this error you should contact Technical
Support.
165 Version number incompatibility (Fatal)
* One or more of the run-time support modules is
incompatible with the run-time system you are using.
The name of the incompatible support module is
displayed.
Alternatively, the run-time system you are using is
incompatible with the version of your COBOL system.
Either "RTS" or the name of the run-time system file
is displayed: coblib.dll (OS/2), coblib.dle (DOS) or
coblib.dlw (Windows).
* Reinstall the support module, using your installation
disks.
Reinstall the run-time system file, using your
installation disks.
If no support module name is displayed, you have done
one of the following:
* Used intermediate code which has been produced on a
version of your COBOL system that is incompatible with
the run-time system you are using. Your RTS,
therefore, cannot execute correctly any generated code
you are producing or have already produced from this
intermediate code.
* Tried to execute a file which is not your COBOL
system's intermediate or generated code.
166 Recursive COBOL CALL is illegal (Fatal)
* You have tried to call a COBOL module that is already
active.
* You should recode your program.
167 Too many USING items (Fatal)
* The list of items which you have supplied in a
CALL....USING statement is longer than the run-time
system can handle.
* Once your program has terminated recode it with group
items rather than elementary items before rerunning
it.
168 Stack overflow (Fatal)
* You have nested a PERFORM statement or a series of
CALL statements too deeply.
* Edit your program to reduce the number of levels in a
nested PERFORM or CALL statement, then resubmit your
source code to your COBOL system.
169 Illegal configuration information (Fatal)
* You have tried an operation for which your machine is
not configured; the most likely cause of this is that
Adis is not configured correctly.
* Check that Adis is configured correctly. See your
COBOL System Reference for details of how you can
reconfigure Adis.
170 System program not found (Fatal)
* A system program, for example Adis or ExtFH, is not
present on the current logged-in drive.
* Ensure that all the system programs are available on
the logged-in drive and copy those which are not
currently present using your backup system disk. Once
all the necessary system programs are available you
can run your program.
171 Japanese operations illegal with this RTS (Fatal)
* You are trying to perform Japanese operations with a
non-Japanese run-time system, or you have used a
Japanese version of your COBOL system to produce code
which you are now trying to run using a non-Japanese
run-time system.
* You should resubmit your program using a non-Japanese
run-time system, or if you still want your program to
perform Japanese operations, you should acquire a
Japanese run-time system.