HP 3000 Manuals HP 3000 Manuals
List of Messages 079 - 155
079 COBCONFIG syntax error (fatal)
* There is an error in the run-time configuration sidefile
accessed via the environment variable COBCONFIG.
* Check your syntax against your COBOL System Reference.
You may 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).
080 ISAM file blocksize larger than run-time configuration can deal
with (fatal)
081 Key already exists 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.
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 attempted a file operation which violates a
general rule of COBOL in some way. The most likely cause
of this error is that you have attempted 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 try to 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
attempting 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,
attempt to run the program again using a backup copy of
that file.
103 Parameter type cannot be passed by value
104 Null file name used in a file operation (fatal)
* You specified a data-name for a filename instead of a
literal, and the data-item contained only spaces when you
tried to open the file.
* Recode your program specifying the correct filename.
105 Memory allocation error (fatal)
* The run-time system is unable to allocate sufficient
memory space to successfully carry out the attempted
operation, probably because there is no memory space left
on your system.
* You will have to 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 may have used many CALLed
programs without CANCELing them afterwards, so that
memory becomes exhausted during Animation.
* Contact Technical Support who will try to help you to
discover the cause of your error and how it may 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 attempting to perform a file operation which your
run-time system does not support.
* You will have to recode your program so that it does not
attempt such operations, or you will have to 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
Divison 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 within the run-time system has
been altered. The run-time system may have become
corrupted, or you may have illegally attempted to change
the internal run-time system information.
110 Generated code not supported by this RTS
* Contact Technical Support who will try to help you to
discover the cause of the error and how it may 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 cancelling
programs that are not in use, then attempt the operation
that caused this message again.
117 Bad collating sequence (fatal)
* This is an internal system error.
* Please contact Technical Support who will try to help you
to discover the cause of the error and how it may be
rectified.
118 Symbol not found (fatal)
* You are unable to load your object file. You have
attempted 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 will need to correct
your object file. If this does not work, contact
Technical Support who will try to help you to discover
the specific cause of the error.
121 Symbol is not in TEXT section (fatal)
* You have attempted 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 cobsetjmp() (fatal)
* You may 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
cobsetjmp was. See you COBOL System Reference for
details of cobsetjmp 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 try to 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 cancelled due to exceeding time
limit
126 Record size exceeds system limit
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 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.
137 Illegal device specification - not mass storage
138 File closed with lock- cannot be opened (recoverable)
* You are attempting to open a file which you previously
closed with lock, which violates one of the general rules
of COBOL programming.
* You will not be able to open the relevant file. As this
error implies that your program has a mistake in its
logic, you may want to close any remaining open files,
execute a STOP RUN statement and recode.
139 Record length or key data inconsistency (recoverable)
* There is a discrepancy 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.
* There is a fault in your program so you will probably
need to 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 contains a mistake in its logic, you
may wish 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 contains a mistake in its
logic, you may wish 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 attempting a REWRITE or DELETE on some of
the information contained within 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 attempted to write or rewrite 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 attempt 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 contains a mistake in its
logic, you may 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.
* Close the file and re-open it with the correct open mode
for the file type. However, as this error implies that
your program contains a mistake in its logic, you may
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.
* Close the file and reopen for I-O. However, as this error
implies that your program contains a mistake in its
logic, you may wish to close any open files, execute a
STOP RUN statement and then recode.
150 Program abandoned at user request (fatal)
* You have interrupted the program by means of a keyboard
interrupt. The program is closed down, and any open
files closed automatically by the run-time system.
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 contains a mistake in its
logic, you may 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 attempted 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 contains a mistake in its logic, you
may wish 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 will need to 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 will need 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.
* 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.