Using Reference Reports

When you verify a legacy application, the parser generates a model of the application that describes the objects in the application and how they interact. If a Cobol source file contains a COPY statement, for example, the system creates a relationship between the file and the Cobol copybook referenced by the statement. If the copybook doesn’t exist in the repository, the system flags it as missing by listing it with a symbol in the tree view of the Repository Browser.

Reference Reports let you track these kinds of referential dependencies in verified source:

Tip: The Missing Files report in the Verification Report tool is a convenient alternative to an Unresolved Report when you are interested only in missing source files, and not in unresolved objects like system programs.