CMS Snapshot Analysis - Run Analyzer - Warnings - PL1 with extension - Unable to find the object end for type

This page is a troubleshooting guide for the warning Unable to find the object end for type XXXX which occurs during PL1 analysis.

This warning occurs if the analyzed source file does not contain END for the object type being reported.
For example "Unable to find the object end for type 'PL1 Function'" means that the analyzed source file does not contain END for the function.

Error Free Logs - CMS Snapshot Analysis - Run Analyzer - PL1 - Error Free Logs - CAST AIP 83

1. Configure a UA PL1 analysis.
2. Run analysis.
3. Open Log and see warning messages - Unable to find the object end for type.

1. Check for the existence of END in the source file.
   
   1. Open the file and check in the source code and see whether the reported object contains END or not. If it does not contain, then this explains the reason for warning.
2. If END is missing this means that the files are not preprocessed properly so you can follow the workaround as below:
   1. As a workaround, for the pre-processed file (present in the LISA folder), package these using standard "Files and Folders" discovery option in DMT (Pre-processed file can be identified by the first line of the file which will always be BEGIN_xxx.)
   2. For files which are not pre-processed, package it using "PL1" extractor in DMT, check for the pre processor log file for any warning/error in the log.
   3. Deliver the source code and run the analysis, you would not get any warnings.
3. If END is present still the analyzer is unable to recognize it then contact  CAST Technical Support with the following Relevant input

Relevant Input

1. Sherlock (CAST Support Tool (CST) - alias Sherlock) : Export Cast Database, Export logs, Export Configuration Files, Export source code. 
2. Explanation about the problem and supporting screenshots