Catastrophic Error Messages - HP Guardian Errors Manual

Recovery The file is bad but possibly most of the file's contents could be recovered by copying the
entire file and ignoring only the records having this error.
-10
Cause NUMBEREDIT returns this error when the parameters represent disallowed renumbering: the
first new record number is not greater than that of the record preceding the first record to be
renumbered, the new record number increment is zero or negative, or no records are affected.
Effect The procedure stops.
Recovery Recovery is not possible.
13
-14
-15
-16
-17
Cause These errors can occur only when IOEdit is accessing a file other than an EDIT file. For
example, they can occur when a local version control system database is accessed.
Effect The procedure stops.
Recovery This error should not occur; recovery is not possible. Determine the type of access desired
and correct the request.

Catastrophic Error Messages

Errors for which no recovery is possible result in the immediate abnormal termination of the calling
process. For these conditions, IOEdit does not return to the caller but instead writes a message to
the home terminal and calls ABEND. The catastrophic error messages are the following.
**** IOEdit internal error, process aborted ****
Cause A data structure maintained by IOEdit has an inconsistent condition. The problem is in IOEdit
itself, not in the calling program.
Effect The calling process is terminated abnormally.
Recovery Recovery is not possible.
**** IOEdit unable to allocate Edit File Segment, process
aborted ****
Cause If the caller does not explicitly call the INITIALIZEEDIT procedure, the first IOEdit procedure
called does so automatically. In any case, INITIALIZEEDIT first tries to create the Edit File Segment
on the swapping disk volume for the calling process, and if that fails, it then tries every disk volume
in the system. If all attempts fail, IOEdit issues this message and calls ABEND. If the system is that
short of disk space, many other processes will probably fail in a similar manner.
Effect The calling process is terminated abnormally.
Recovery Recovery is not possible.
**** IOEdit stack overflow, process aborted ****
Cause In the course of accessing caller-provided information that is in user extended data segments,
IOEdit makes local copies on the stack. This can make the program's stack space requirements
226 IOEdit Errors
(cannot do renumbering)
(error accessing non-EDIT file line numbers)
(error accessing non-EDIT file change tags)
(change tag should be appended to record)
(both tag and record number error)
(change tag overlays text)