Files > ERROR MESSAGES

name
ERROR MESSAGES
number
3.076
location
^%ZTER(2,
description
This file contains a number of the abbreviations used to indicate the type of error encountered. The most important ones are those which are indicated as fatal errors warranting termination of the job after logging of the error.
Fields
#NameLocationTypeDetailsIndexDescription
.01name(+)0;1FREE TEXTBThis field contains the brief name for an error used by one or more operating systems (e.g., UNDEF for an undefined error)
.02error type(+)0;2SET OF CODESF:FATAL
H:HARDWARE
I:IO/DEVICE
P:PROGRAM
D:DATA
L:LOCAL
This field attempts to indicate the primary responsibility for an error, such as hardware, or software, since this affects the extent of recoverability from an error.
.03screen in xter0;3SET OF CODES1:Don't show
2:Don't record
ACThis field is used to mark errors that should be screened in one way or another. If blank show and record error, 1 record but don't show in XTER in default mode, 2 don't record.
.04count screened errors0;4BOOLEAN0:No
1:Yes
This field turns one the counting of the screening of this error.
.05national0;5BOOLEAN1:Yes
This field should only be used by the National developers. This is to GUARANTEE that certain ones are in the file. These entries can't be deleted.
1operating system number1;0MULTIPLE3.0761This is a multiple field which is used to indicate which operating system(s) use a given brief name for an error.
2alternative screening text2;E1,50FREE TEXTIf you need to screen errors on text that can not be placed in the .01 field than use a local name for the .01 and enter the real screening text in this field. This field will allow ^ and other characters that cannot be placed in the .01 field.
3count of screened errors3;1NUMERICThis field holds a count of the number of times this error was screen from being recorded in the error trap.

Not Referenced