# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | screen name(+) | 0;1 | FREE TEXT | B | This is the name to identify the screen. It should be namespaced and descriptive. | |
1 | description | 2;0 | WORD-PROCESSING | This should contain a full description of how this screen should be used, i.e., its purpose. | ||
2 | creator(+) | 0;3 | POINTER | 200 | This is the person who created the screen. | |
3 | date/time created(+) | 0;4 | DATE-TIME | This field contains the date/time the screen was created. | ||
4 | type of screen(+) | 0;5 | SET OF CODES | 0:EXCLUDE 1:INCLUDE | This field is used to determine the type of error screen to be applied to the error list. There are two types: EXCLUDE (0) - excludes the error messages from being displayed INCLUDE (1) - includes the error messages on the display. | |
5 | errors | 1;0 | MULTIPLE | 779.115 | This is a list of strings used to determine what errors should display. Each string is compared to each error that would otherwise be included in the display. If the string matches a string that occurs within the error, the error is either: INCLUDE type screens - the error will be included in the display. EXCLUDE type screens - the error will be excluded from the display. This is the verbatim text of the error to be screened. A list of possible errors is in the HLO Technical Manual. Alternately, you may cut and paste text from the error display into this field. You might screen errors for the following purposes: 1) To exclude certain errors from the display. Some of the errors don't require any action on your part. 2) To display only certain errors. These are critical errors which you want to act on quickly. You KNOW from experience what those errors are. |
Not Referenced