CMS Snapshot Analysis - Run Analyzer - Performance issue - Mainframe - Analysis getting stuck at the beginning of the analysis

The analysis of the maniframe application remains at the same tracing log for more than 15 hours.

The analysis is stuck just after the below step in the analysis log:

About to run JOB_MAINFRAME_ANALYZER job '<Analysis log file name>'

Below is the step-by-step scenario leading to the problem: 

1. Create a new application
2. Create a version using the sources provided
3. Launch analysis

The impact of the problem on the analysis or the dashboard is: The analysis will not start and remain stuck at the beginning of the analysis.

To fix the problem, proceed as follows:

1. Apply the process of Dichotomy to find the culprit file, refer the page CMS Snapshot Analysis - Information - Overview of the Dichotomy process which provides the information on how to proceed

2. Once you find the file then check in the culprit file if you have 

   DISPLAY '-------------------------------------------------'
   
   For a workaround to this problem, replace the above line with the following
   
   DISPLAY '------------------------------------------------'
   
   The second statement has one character less (minus one '-'). 

   We can also take the help of notepad++ to find the files in the folder with the above bunch of minus (-) sign.

   This will unblock the analysis  and it will complete normally. 

 The analysis will complete successfully but there wont be any impact on the dashboard.