DBDOC-CHECK MISSING DISPLAYS.ERR

Some of the error types in this file have been converted to be displayed in the Error Browser, and are documented at the links below:

• Display not found [CHECK 197]
• Display with GUID not found [CHECK 198]
• EbVector references unknown graphic [CHECK 216]
• M1 display file not found (not configured) [CHECK 195]
• Missing M1 not defined [CHECK 267]
• Referenced M1 display file not found [CHECK 194]

The error types in this file that have not yet been converted are documented here:

This message means that the graphic indicated calls for another graphic, which was not found. This is not really an error, but is a weakness for the operators using the graphic system.

The usual sources of this error are:

1. Failure to build all graphics in the DBDOC document. If the graphic is not built, the DBDOC process will not find it. This is normally the case when there are a lot of messages in this file.
2. Graphics becoming obsolete and being eliminated, without correction of other graphics that call for the obsolete graphic.
3. Graphics being planned and anticipated that have not yet been built or installed.
4. Errors in pop-ups.

When there are a lot of these errors showing up, it normally means that you did not get all your graphics built or you are dealing with graphics that are not used. It suggests that operator graphic keys and touchpoints may be "dead" because those graphics are not in the system.

You can find where the graphic is linked using either the Audit Window or the Index of Unconfigured Graphics in the System Information chapter.