The two parts to this example show how DBDOC helps with graphic history maintenance.
Message 1.
History tag CBTE01 references CBTE01.C_APV (not found in any database).
The Historical Tag can have any legitimate name, including CBTE01. However, the "Tag Atom" entry must refer to a legitimate database value. In this case, the problem is that there is no database tag "CBTE01", which means that Tag Atom "CBTE01.C_APV" is erroneous. If the entry in Tag Atom were changed to have the "-" in the name, there would be no error.
Usually, this message comes because no such tag is in the database at all, often because it did exist but was deleted. DBDOC checks that the tag name and tag atom make sense.
Message 2.
Trendcfg tag CBTE-01 refers to missing or invalid entry in history database.
The Trend error is caused by the fact that there is no Historical tag CBTE-01, which is what the Historical Tag should have been called. The trend group is thus flawed because it is calling up an entry that does not exist.
In the case of the messages in the example, it is pretty clear that the Historical Tag named "CBTE01" should be modified to be "CBTE-01" and the Tag Atom entry corrected. Then both messages would go away.
In the example, the Trend error refers, in fact, to an invalid tag, not a missing one. The other form of the error is, of course, to name a trend tag that does not exist at all. To resolve that error, you either eliminate the trend tag entry in the Trend Configuration section, or you correct the spelling of the Trend Tag entry in the Trend group.
This error can be built directly into Hyperview. For more information, see the article Building error reports into the M14.