#1. In case of COBOL Application
When an analysis+snapshot is performed on a COBOL/Mainframe application and results are observed on the dashboard, it is expected to get multiple object paths for a single object violation.
Reason - COBOL/Mainframe source code files also use copybooks (.cpy files) and the analyzer analyzes all the .COB and .CPY files. A COBOL program can be implemented in several source files: one for the program itself and various others for the copybooks it references (for instance, for data description). So, if there is a violation flagged for a COBOL object then the copybooks that are associated with this object's source file also come up in the object path on the dashboard.
If the above queries are ran on the KB, they will return the results with multiple source paths including the copybook file path as well.
So this is an expected behaviour of the product for COBOL/Mainframe application.