HP 3000 Manuals HP 3000 Manuals
List of Messages (172 - 254)
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 tried 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 tried 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 should copy the
relevant file into your logged-in drive or directory.
If insufficient space is available, you should 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.
174 Imported file not found (Fatal)
* You have tried to load a .dll file which contains
references to another .dll file which cannot be found
by the operating system.
* Locate the missing file and ensure it is located on
the default search path for your operating system.
175 Attempt to run intermediate code program which has severe
errors in it (Fatal)
* You are trying 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 try to run the program with
the E run-time switch set, though this might 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.
When your program is being animated, Animator reports
this error and enables you to continue to run the
program.
@L2NC1 = See also:
@L2NC2 = E RTS switch
176 Illegal intersegment reference (Fatal)
* You might 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 help you to discover the specific
cause of the error.
177 Attempt to cancel program failed (Fatal)
* You have tried to remove a currently executing program
or its parents or grandparents, from memory.
Alternatively, you have tried to cancel a DLL, either
directly or indirectly as an imported DLL, that
contains an entry point which has been registered as
an EXIT LIST function via the OS/2 API call
DosExitList.
* Once your program has terminated you need to recode
your program to ensure that you do not try to cancel a
program (or its parents or grandparents) while it is
still being executed.
Locate the erroneous DLL and ensure that the EXIT LIST
function is removed before you cancel the DLL. If you
cannot recode the DLL, you can set the O RTS switch to
force a logical cancel on the DLL.
@L2NC1 = See also:
@LP2 = O RTS switch
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 tried 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) (Fatal)
* You have tried to chain to another program which your
system is unable to find.
* Once your program has terminated you should copy the
relevant file into your logged-in drive or directory.
If insufficient space is available, you should 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 should 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 should 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 should recode
your program to ensure that the file with organization
line sequential is opened for input, output, or
extend. You can then 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 logic contains a mistake, so you must
recode.
185 File malformed (Recoverable)
186 Attempt to open stdin, stdout or stderr with incorrect mode
(Recoverable)
* You have tried to open either a standard input file
with output mode, or some other file in an incorrect
mode.
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 might 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 Filename too large (Fatal)
* A file-name which you have used has more characters
than the maximum number allowed by your operating
system.
* You should recode your program to check the length of
the file in error, and rename it with a shorter
file-name. You can then run your program again.
189 Intermediate code load error (Fatal)
* You are unable to load your intermediate code. You
might have tried 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 statement in 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.
* Your terminal type is undefined, so your operating
system is unable to drive your terminal. 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.
* Add the missing entry to your terminal configuration
database.
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 should 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 tried 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 can be caused by one of the following:
@LB2 = Your display adapter is in the wrong mode.
@LB2 = Your screen handling interface has not been
correctly initialized because your terminal does not
have the required capabilities.
@LB2 = Your terminfo file is corrupted.
@LB2 = 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 try 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 of
insufficient memory.
Alternatively your program has run out of memory
during the loading or reloading of a file. This
occurs 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 error code lies outside expected range
(Fatal)
* A system call has returned an unexpected error number
which is not documented.
* Contact Technical Support who will 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 stopped 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 help you to
discover the cause of the error.
201 I-O error in paging system (Fatal)
* No room is 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 in your COBOL system
contains errors.
* Ensure that all of your external assembler
applications call and use run-time system functions
correctly before you try 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 trying 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 try to access it again.
208 Error in multi-user system (Fatal)
* This is normally caused by an unexpected error
occurring in the network or file-sharing facilities.
A corrupted network message also causes this error to
be returned.
* Retry the unsuccessful operation. If the error
persists, contact Technical Support who will 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 might 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 does 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 should relink with the current
version of your COBOL run-time library.
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 might 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 should 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 try to run Communications.
217 Incompatible host for native 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 should try 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 should 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
trying to execute more than one SORT or MERGE
operation at the same time. For example, you might
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 should 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 keys (Fatal)
* You have tried a SORT/MERGE operation which has been
unsuccessful for some reason. You might have had too
many files open when you tried a SORT/MERGE operation,
or the file which you are trying to access might be
locked.
* The action you should take depends on the situation in
which it occurs. Check the status of each file
(USING/ GIVING) defined in the SORT statement.
222 SORT/MERGE error: see status keys (Fatal)
* You have tried a SORT/MERGE operation which has been
unsuccessful for some reason. You might have had too
many files open when you tried a SORT/MERGE operation,
or the file which you are trying to access might be
locked.
* The action you should take depends on the situation in
which it occurs. Check the status of each file
(USING/ GIVING) defined in the SORT statement.
223 SORT/MERGE error: see status keys (Fatal)
* You have tried a SORT/MERGE operation which has been
unsuccessful for some reason. You might have had too
many files open when you tried a SORT/MERGE operation,
or the file which you are trying to access might 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.
Alternatively, you have insufficient memory to load
your program.
Alternatively, the run-time system could not find
enough file handles to open and, therefore, load the
code.
* Either the library that contained the program has been
canceled, 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.
Either free some memory, use XM or restructure your
application so that it uses less memory.
Increase your operating system file handles limit.
226 EXTERNAL file definition inconsistent
* Two or more programs define the same external file but
with different formats. For example, maximum and
minimum record lengths might be different.
* Make sure that all of your programs define the
external file with the same format so that they are
consistent. It is useful to have the file definition
in a COPY file.
227 EXTERNAL data definition inconsistent (Fatal)
* Two or more programs are defining the same external
data item, but the first loaded program has defined
the size smaller than has the second or subsequent
loaded program.
* Make sure that both or all of your programs define the
size of the external data item as being the same.
228 Could not allocate memory for EXTERNAL item (Fatal)
229 SORT/MERGE module does not support EXTERNAL using/giving
files (Recoverable)
* You have tried a SORT or MERGE operation which has
USING/ GIVING files which are defined as EXTERNAL. The
SORT/ MERGE module does not support USING/ GIVING
files defined as EXTERNAL.
* Recompile your program to use the callable SORT module
(EXTSM).
230 Floating Point Support Module not found (Fatal)
235 Error in animator communications channel (Fatal)
* Animator has encountered system limits or conflicts
resulting in communications errors. Perhaps two
logins on the same UNIX system are trying to
cross-session animate the same program file.
* Copy the animated program file to a different
directory and try animation.
236 Animated program has terminated unexpectedly (Fatal)
* A program you are animating has terminated without
following the standard run-time system shut-down
process. The termination was probably either
initiated by the user or caused by a severe run-time
error.
* Run your program without animation to determine if it
runs successfully; if so, animate the program without
cross-session or intrasession animation.
237 Unable to initialize animated process (Fatal)
* Animator has encountered system limits in starting
your program. The animated program cannot start
because of either insufficient memory or too many
processes running on the UNIX system.
* Animate your program when the load on the system has
reduced. Run the program without animation to
determine if it runs successfully; if so, animate the
program without cross-session or intrasession
animation. Ask your system administrator to expand
the number of process slots and virtual memory page
maps.
254 Keyboard interrupt to ANIMATOR during ACCEPT (Fatal)
* While using Animator you have terminated your program
with a keyboard interrupt.