HP 3000 Manuals HP 3000 Manuals
List of Messages 156 - 254
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 will have to 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 will be 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 wish 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 will have to resubmit your source program to your
COBOL system, to try to obtain uncorrupted intermediate
code.
162 Arithmetic overflow or underflow (fatal)
* You have attempted to divide a data item by zero.
* You will need to 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.
* If you unset the numeric field check switch on the run
command line then the run-time system will not check that
all values in a numeric or numeric-edited field are
numeric and you should be able to run your program
successfully. Alternatively, you can make sure that you
initialize numeric and numeric-edited items with numeric
values, which should enable your program to run
successfully regardless of the setting of the numeric
field check switch.
164 Run-Time subprogram not found (fatal)
* You have attempted 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)
* You are using intermediate code which has been produced
on a version of your COBOL system that is incompatible
with the run-time system you are currently using. Your
RTS, therefore, will not be able to execute correctly any
generated code you are producing or have already produced
from this intermediate code.
Alternatively, you may have attempted to execute a file
which is not your COBOL system's intermediate or
generated code.
* Resubmit your source programs to your COBOL system using
the new version of your software.
166 Recursive COBOL CALL is illegal (fatal)
* You have tried to call a COBOL module that is already
active.
* You will need to 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 within a
nested PERFORM or CALL statement, then resubmit your
source code to your COBOL system.
169 Illegal configuration information (fatal)
* You have attempted 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 will be able
to run your program.
171 Japanese operations illegal with this RTS (fatal)
* You are attempting 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 will have to resubmit your program using a
non-japanese run-time system, or if you still want your
program to perform Japanese operations then you will have
to acquire a Japanese run-time system.
172 Recursive non MF PERFORM is illegal (fatal)
* You have tried full recursion of a PERFORM statement in a
program that was submitted to your COBOL system with the
OSVS parameter of the PERFORM-TYPE directive specified.
That is, you have attempted to end two PERFORMs with the
same return address.
* You should either resubmit your program to your COBOL
system with a parameter other than OSVS specified for the
PERFORM-TYPE directive, or recode your program so that
each PERFORM has its own unique return address before you
resubmit it to your COBOL system with the MF parameter of
the PERFORM-TYPE directive specified.
173 Called program file not found in drive/directory (fatal)
* You have attempted to call a program which is not present
on your current logged-in drive or directory, or in a
directory pointed to by the COBDIR environment variable.
* Once your program has terminated you will need to copy
the relevant file into your logged-in drive or directory.
If there is not sufficient space available to allow you
to do this, then you will have to set the COBDIR
environment variable to search the directory or drive on
which the file is present when your program calls it.
Refer to your COBOL System Reference for details of the
COBDIR environment variable. Once you have taken these
steps, run your program again.
175 Attempt to run intermediate code program which had severe errors
in it (fatal)
* You are attempting to run a program that produced severe
faults when you submitted it to your COBOL system with
the run-time switch E turned off.
Alternatively, you could attempt to run the program with
the E Run-Time switch set, though this may not give the
desired results.
* You should edit your source code to correct all the
severe faults, resubmit it to your COBOL system, then run
the intermediate code that is produced.
Refer to your COBOL System Reference for details of this
switch. Note that when your program is being animated,
Animator will report this error and will allow you to
continue to run the program.
176 Illegal inter segment reference (fatal)
* You may have a corrupted file. Alternatively, your code
contains a segment reference for the Forward Reference
Table which is illegal.
* Resubmit your source code to your COBOL system. If you
receive this error again, contact Technical Support who
will try to help you to discover the specific cause of
the error.
177 Attempt to cancel active program (fatal)
* You have tried to remove a currently executing program or
its parents or grandparents, from memory.
* Once your program has terminated you will need to recode
your program to ensure that you do not attempt to cancel
a program (or its parents or grandparents) while it is
still being executed.
178 Error during save (fatal)
* You cannot save the information which your program has
generated. This can be caused by several different
reasons but one of the most common causes is that you
have attempted to Build a module that is too large for
the available memory space.
* If the error is caused by a lack of space you can either
delete some of the files which you no longer need on your
current disk, or insert a new floppy disk to take the
output from your program. You should then be able to
rerun your program and save the information given by it.
179 Error during chain (program not found) ( severity:)
* You have tried to chain to another program which your
system is unable to find.
* Once your program has terminated you will need to copy
the relevant file into your logged-in drive or directory.
If there is not sufficient space available to allow you
to do this, then you will have to set the COBDIR
environment variable to search the directory or drive on
which the file is present when your program calls it.
Refer to your COBOL System Reference for details of the
COBDIR environment variable. Once you have taken these
steps, run your program again.
180 End-of-file marker error (fatal)
* A file-marker used to indicate that the end-of-file has
been reached is missing from one of your files.
* You will need to resubmit your code to your COBOL system,
or use a debugger to place the end-of-file marker at the
end of the file. You can then rerun your program.
181 Invalid parameter error (fatal)
* A parameter which you have used is not one which is
recognized by your system. You have probably used a
parameter for a run-time system subprogram which is not
in the first 64K of the Data Division.
* Revise your code to contain a parameter which is known by
your system. That is, ensure that the parameter is in
the first 64K of the Data Division.
182 Console input or console output open in wrong direction (fatal)
* You are either trying to read input from the screen or
write to the keyboard.
* You will have to recode your program.
183 Attempt to open line sequential file for I-O (fatal)
* You have tried to open a line-sequential file in the
input-output open mode, but this mode is not supported
for files with this organization.
* When your program has terminated you will have to recode
your program to ensure that the file with organization
line sequential is opened for input, output, or extend.
You will then be able to rerun your code.
184 ACCEPT/DISPLAY I-O error (fatal)
* You have either tried to read input from the screen or
write to the keyboard, or the ADIS module has not been
able to open your terminal's channels for I-O.
* Your program contains a mistake in its logic so you will
need to recode.
185 File malformed
186 Attempt to open stdin, stdout or stderr with incorrect code
187 Run-Time System not found on $COBDIR path (fatal)
* The run-time system cannot be found on the path you have
set up in the COBDIR environment variable.
Alternatively, you may not have installed your COBOL
system correctly.
* Ensure that the run-time system is on the path you have
set up in the COBDIR environment variable.
Alternatively, ensure that your COBOL system has been
installed correctly. If it has not, you must reinstall
your COBOL system.
188 File name too large (fatal)
* A file name which you have used has more characters than
the maximum number allowed by your operating system.
* You will need to recode your program to check the length
of the file in error, and rename it with a shorter file
name. You will then be able to run your program again.
189 Intermediate code load error (fatal)
* You are unable to load your intermediate code. You may
have attempted to load intermediate code that either has
not been successfully produced, or has been corrupted in
some way.
* Try to obtain good intermediate code, for example, by
resubmitting (or submitting) your source code to your
COBOL system. You should then be able to load your code
and run the program successfully.
190 Too many arguments to CALL (fatal)
* A CALL within your program cannot be successfully
executed because of the number of arguments which you
have used with it.
* When your program has terminated you can recode it using
group items rather than elementary ones. You should then
be able to run your program successfully.
191 Terminal type not defined (fatal)
* Your terminal is not defined in:
- the termcap file in COBDIR, or
- the terminfo database, or
- the cobcap file
- (depending on your environment). Your operating
system is therefore unable to drive your terminal as
it has no environment specification for it.
* Set up the necessary environment for your terminal.
192 Required terminal capability description missing (fatal)
* A compulsory entry, for example cursor movement or clear
screen, is missing from your terminal configuration
database ("termdesc" or "termcap").
* Add the missing entry to your terminal configuration
database ("termdesc" or "termcap").
193 Error in variable length count (fatal)
* The intermediate code which is currently being processed
is not a valid operation. You are probably trying to
execute a corrupt file or one which has not been
produced.
* You will have to resubmit your source code to your COBOL
system.
194 File size too large (fatal)
* A file which your program is accessing is too large for
successful execution to continue.
* When your program has terminated you should recode your
program spreading the data over more than one file to
ensure that no file becomes too large for your operating
system to handle. Having recoded your program you can
then rerun it.
195 DELETE/REWRITE not preceded by a read (fatal)
* Before a DELETE or a REWRITE statement can be
successfully executed in sequential access mode the last
input-output statement executed for the associated file
must have been a successful read. In your code no read
statement precedes your attempted DELETE or REWRITE.
* When your program has terminated, recode your program,
making sure that the last input-output statement to be
executed before the DELETE or REWRITE is a read
statement.
196 Record number too large in relative or indexed file (fatal)
* The relative record key has exceeded the system limit,
that is, the file is too large for the system to handle.
* Alternatively, the record key which you have specified is
too large for the system to deal with successfully, or
the pointer to the record has been corrupted in some way
so that it is either too large or it is not a multiple of
the record length.
197 Screen handling system initialization error (fatal)
* This error may be caused by one of the following:
- your display adapter is in the wrong mode
- your screen handling interface has not been correctly
initialized because your terminal does not have the
required capabilities
- your terminfo file is corrupted
- memory has been incorrectly allocated.
* If you are using a DOS or OS/2 system, the monitor must
be in alphanumeric display mode rather than graphics
display mode. You can set the display mode to a valid
alphanumeric mode by using the DOS MODE utility and then
rerunning your program.
If you are using a UNIX-type system, you must check that
your terminfo file contains the correct entry for your
terminal. Refer to your COBOL System Reference for
details. If your terminfo file is corrupt, or your
screen handling interface has not been correctly
initialized, you must advise your system administrator of
the problem, and he will take steps to attempt to correct
it. If your memory has been incorrectly allocated, you
must rerun your program.
198 Load failure (fatal)
* The system cannot load a program, usually because there
is insufficient memory.
Alternatively your program has run out of memory during
the loading or reloading of a file. This will occur more
frequently during Animation because of the extra memory
required during Animation.
* Make more memory available and then rerun your program.
Ensure that as much memory as possible is available
during Animation by canceling any program you do not
currently need to access.
199 Operating system corrupted (fatal)
* A system call has returned an unexpected error number
which is not documented.
* Contact Technical Support who will try to help you to
discover the specific cause of this error.
200 Run-Time System internal logic error (fatal)
* The amount of memory available on your machine is so low
that not even the run-time system can be fully loaded.
Alternatively, your run-time system has halted as a
result of an internal logic error from which you cannot
recover.
* Free some memory and then you should be able to run your
program successfully.
Contact Technical Support who will try to help you to
discover the cause of the error.
201 I-O error in paging system (fatal)
* There is no room available in your current directory or
on the floppy disk which you are using, for the paging
file.
* When your program has terminated, delete any files which
you no longer need from your directory to make room for
the paging file, or insert a new floppy disk.
202 Exported functionality error (fatal)
* You have either caused an internal run-time system error
by invalid use of an exported function, or the code
produced by a preprocessor within your COBOL system
contains errors.
* Ensure that all of your external assembler applications
call and use run-rime system functions correctly before
you attempt to run your program again. If you are using
a preprocessor as part of your COBOL system, you should
use the software as a standalone preprocessor to isolate
the problem areas.
203 CALL parameter not supplied (fatal)
* The item you are trying to access in the Linkage Section
of the currently executing program has not been
initialized.
* Recode your program to ensure that it contains all of the
necessary parameters, or check that it is a valid caller.
206 Reading unwritten data from memory (fatal)
* You are attempting to read data which has not been
written, from the core file.
207 Machine does not exist (recoverable)
* You have tried to access a machine that is not connected
to your network, or which is not on line.
* Make sure the machine is connected to the network and is
on-line, then attempt to access it again.
208 Error in multi-user system (fatal)
* This is normally caused by an unexpected error occurring
within the network or file-sharing facilities. A
corrupted network message will also return this error.
* Retry the unsuccessful operation. If the error persists,
contact Technical Support who will try to help you to
discover the specific cause of this error.
209 Network communication error (recoverable)
* This is normally given if an incorrect checksum has been
received in a communications packet.
* Your program should continue to execute after you have
received this error but results may be undefined.
210 File is closed with lock (fatal)
* You have tried to open a file which you have previously
closed with lock.
* Recode your program to avoid opening a file which has
previously been closed with lock.
211 Program not executable by Run-Time System (fatal)
* You have tried to run a program that is incompatible with
the current version of either your run-time system, your
object file or your COBOL run-time library. For example,
your run-time system will not run a program linked using
a different object file format or COBOL run-time library.
* If your object file is incompatible with the current
version of either your COBOL run-time library or your
run-time system, you will need to relink with the current
version of your COBOL run-time library.
212 Malformed Assembler subroutine file (fatal)
* You are attempting to access an assembler routine that is
not in the specific format for such a file.
* Examine the example assembler routine which was supplied
to you with your system and alter the structure of your
routine to be the same as this. Ensure that it is linked
properly, it has the correct structure, and you used the
right assembler. You should then be able to run your
code successfully.
213 Too many locks (recoverable)
* You have either tried to exceed the maximum number of
simultaneous record locks per file you can have, or you
have exhausted an operating system or network resource,
for example dynamic memory.
* Execute a COMMIT or an UNLOCK operation on the relevant
file and you should then be able to continue to run your
program. You should try not to retain a record lock for
longer than is necessary.
214 GO TO has not been ALTERed (fatal)
* You have violated one of the general rules of COBOL
programming.
* Close any files which may be open, execute a STOP RUN
statement and then edit your program to avoid such
illegal operations.
215 Cannot ANIMATE a program running COMMUNICATIONS (fatal)
* You have tried to animate a program which makes use of
the communications module. This cannot be done as both
Animator and the communications module need full use of
the CRT.
* You will have to run your program without the aid of
Animator.
216 Cannot initialize the named communications device (fatal)
* A device driver is probably missing.
* Ensure that all communications drivers are loaded before
you attempt to run Communications.
217 Incompatible host for compiled code file (fatal)
* The .GNT file is not valid for the host processor.
* You must resubmit your program to your COBOL system.
218 Malformed MULTIPLE REEL/UNIT file (fatal)
* Either your file header is not correctly formatted, or
you are not using a MULTIPLE REEL/UNIT file.
* You will have to attempt to run your program again using
a backup copy of the relevant file.
219 Operating system shared file limit exceeded (recoverable)
* You have tried to exceed your operating system's limit on
the number of shared files that you can have open
simultaneously. As this figure is operating system
dependent, you will need to consult your Release Notes
for details of how many shared files your system permits
to be open at any one time.
* Close some of the open shared files you are no longer
accessing and retry the file operation.
220 Attempt to execute more than one SORT or MERGE simultaneously
(fatal)
* You have coded your program in such a way that it is
attempting to execute more than one SORT or MERGE
operation at the same time. For example, you may have
coded a SORT statement in the input or output procedure
of another SORT statement, an operation that is
specifically prohibited under the rules of ANSI COBOL.
* You will have to recode your program to ensure that it
does not execute more than one SORT or MERGE at any one
time.
221 SORT/MERGE error: see status key (fatal)
* You have attempted a SORT/MERGE operation which has been
unsuccessful for some reason. You may have had too many
files open when you attempted a SORT/MERGE operation, or
the file which you are trying to access may be locked.
* The action you should take depends on the situation in
which it occurs.
222 SORT/MERGE error: see status key (fatal)
* You have attempted a SORT/MERGE operation which has been
unsuccessful for some reason. You may have had too many
files open when you attempted a SORT/MERGE operation, or
the file which you are trying to access may be locked.
* The action you should take depends on the situation in
which it occurs.
223 SORT/MERGE error: see status key (fatal)
* You have attempted a SORT/MERGE operation which has been
unsuccessful for some reason. You may have had too many
files open when you attempted a SORT/MERGE operation, or
the file which you are trying to access may be locked.
Alternatively, you have set the TMP environment variable
to point to a directory that does not exist.
* The action you should take depends on the situation in
which it occurs.
Either set TMP to point to a directory that does exist,
or unset TMP.
224 External Language Initialization failure
225 Dynamic load error - program component missing (fatal)
* The run-time system cannot locate the root or overlay of
a program that is currently loaded in memory.
* Either the library that contained the program has been
cancelled, or the program is no longer available on the
program search path. Ensure that the program is
available either on disk or on an open library.
226 EXTERNAL file definition inconsistent
227 EXTERNAL data definition inconsistent
228 Could not allocate memory for EXTERNAL item
230 Floating Point Support Module not found
254 Keyboard interrupt to ANIMATOR during ACCEPT (fatal)
* While using Animator you have terminated your program
with a keyboard interrupt.