CMS Snapshot Analysis on Documentation - V2

CMS Snapshot Analysis - Information - How to change label of an existing snapshot

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

How to change label of a existing snapshot ?

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Details

Steps

In CMS edit the central service containing the snapshot
Click on ‘Manage Snapshot’ action
Snapshot Definition window appears. Change the label of the snapshot in the editor. Click on OK to quit
In the central service, click on ‘Synchronize‘ action to commit the actions. The name of the snapshot will change in this editor

Notes / Comments

CMS Snapshot Analysis - Run Analyzer - SQL PLSQL - Information - Mandatory step to see Public Synonyms and Public DB links

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page provide information about the mandatory steps required to create and see Public Synonyms and Public DB links

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

To create Public Synonyms and Public DB links, it is mandatory to analyze Public schema in addition to your participating schema.

Please make sure:
PUBLIC schema is selected in DMT along with participating schema. (7.2.X onwards)
PUBLIC schema is analysed by looking in the log and Analysis Unit description containing Name : PUBLIC

CMS Snapshot Analysis - Run Analyzer - SQL PLSQL - Information - How to exclude objects from analysis in New PL -SQL Analyzer

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

In the New PL/SQL analyzer, How to exclude objects from analysis?

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Details

New PL/SQL Analyzer requires extracted database source to perform analysis.
Hence as a workaround, modify the .UAXDirectory file to remove the tags corresponding to the objects to filter out from the analysis

Note: However, if those objects are referenced in stored procedures, then analyzer will raise some resolution errors / warnings.

CMS Snapshot Analysis - Run Analyzer - CPP - Information - Locating the pre-processing file

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The purpose of the file is to Locate the pre-processing file.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Details

The pre-processing file used by the C++ Analyzer can be found here:

%TEMP%\CAST\CAST\<version_number>\CAnalyzer2\PreprocessedFile.cpp

Notes / Comments

Related Pages

CMS Snapshot Analysis - Run Analyzer - DOTNet - Information - Designer.vb is not analyzed

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page provides information about the Designer.vb files which is not analyzed by CAST.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

Designer.vb is an auto generated file, it is analyzed by .NET analyzer.

These files are analyzed to resolve objects of other functional classes.

Since these files are auto-generated files, they do not contribute to LOC.

Notes/comments

CMS Snapshot Analysis - Run Analyzer - JSP - Information - Links from the text embedded inside the custom JSP tags are not interpreted by java analyzer

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page is to explain that the links from custom JSP tags are not expected as they are not analyzed by the Java analyzer.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

If there are some Custom JSP tags in your code with some text embedded in that and you are expecting a link from this text to some other part of your code then the text embedded inside the custom tag will not be interpreted. You need to find those links using the Reference Finder.

CMS Snapshot Analysis - Run Analyzer - PHP - Information - Warning - Duplicate object of type xxxx has been detected

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page gives us information on the warning message Duplicate object of type xxxx has been detected : yyyy occurred during PHP analysis

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

The warnings about duplicate objects occurs when two objects with same name and same type have been detected in the same file.
Example -
“Duplicate object of type ‘phpSection’ has been detected : ‘php’”
“Duplicate object of type ‘phpArray’ has been detected : ‘$position’”

CMS Snapshot Analysis - Information - Overview of the Dichotomy process

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The main purpose of this page is to give an overview of investigation by dichotomy.

When the log files are not enough to identify the file that is the root cause of a blocking error, or a crash, or a process that never ends, during the analysis or during the Run Metrics Calculation step, one could investigate by dichotomy to find out this file.

Please refer to official documentation about the logic of execution units : CMS+-+Working+with+Execution+Units

CMS Snapshot Analysis - Run Analyzer - JEE - Information - Common Syntax error

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page would confirm the behavior of analyzer when a syntax error occurs..

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

When a syntax error occurs in the analyzer, the analyzer would skip the file rather than parsing the rest of the code. This is the current behavior of the analyzer and doesn’t have any workaround. We need to solve the syntax considering the analyzer chosen and then re analyse the source code.

CMS Snapshot Analysis - Run Analyzer - SQL PLSQL - Information - How to modify server name in PLSQL extraction before analysis

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

With the PL/SQL offline analyzer (new), changing the server from where the extraction is done leads to the change of all DB objects fullname. As consequence, all DB objects will be seen as added/removed. To avoid this problem, please follow above stepsbefore generating a new snapshot. If the new snapshot has been generated before doing these steps, you will need first to restore the KB, CB dumps corresponding to the first extraction.

CMS Snapshot Analysis - Run Analyzer - DOTNet - Information - Metrics will not be computed on XSD files

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page would confirm the behavior of the Dot Net analyzer about computing the metrics on XSD files.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

What are XSD files : XSD files in a dot net project would store the information to validate the XML files which extends to XML Schema Definition. These files might have queries some times.

What does cast do on these XSD files : Cast only analyzes the XSD files in order to get the complete context of the code and analyze the project correctly but, there will be no metrics computed on these files.

CMS Snapshot Analysis - Run Analyzer - How to activate SHOW SQL mode in order to get the SQL traces during the Analysis

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page provide information about how to activate SHOW SQL mode in order to get the SQL traces during the Analysis.i.e. Analysis log in SHOW SQL mode

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

Step to activate SHOW SQL mode:

Open CMS
Run Analysis
Expand the debug option
Select the option “Activate debug options” as shown in the screenshot below.
Select the option “Show SQL”
Click on Finish
Analysis log with Show SQL trace is created under %temp%\CAST\CAST\7.X folder

CMS Snapshot Analysis - Run Analyzer - DOTNet - Information - Analyzer does not exclude generated code

Mon, 01 Jan 0001 00:00:00 +0000

Description

C# generated code can be recognized by the fact that the classes are using the System.CodeDOM.Compiler.GeneratedCode attribute. The generated code should be automatically be excluded from all metric results.

In the below screenshots from Enlighten, visualizing for example class RemoteConnectivityFeature which is using the GeneratedCodeAttribute and the screenshot from the Dashboard which shows the same object as violation for several rules.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

CMS Snapshot Analysis - Information - Generate snapshot after some jobs failed in the analysis unit and see the results for successful jobs

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page is to explain how to generate snapshot after some jobs failed in the analysis unit and see the results for sucessfull jobs.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

If there are some jobs failed in the analysis unit and if you want see the results for only successful jobs except failed ones. It is not possible to generate the snapshot if one analysis unit has failed. Because it might have impact on the data in the dashboard, it might lead to partial result on the dashboard.
The only workaround is to rework the analysis unit definition manually to remove the failing part of the code (maybe the whole analysis unit) and re-analyze only the analysis unit part which is successful.

CMS Snapshot Analysis - Run Analyzer - Mainframe - Information - Mainframe File descriptor Block must be defined with zero record

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains why Mainframe File Descriptor block must be defined with zero record.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Details

Quality/rules: File descriptor block must be defined with zero record

Block contains 0 records

It was a clause used on IBM Mainframe COBOL because in the old days of COBOL you had to specified a buffer size. By putting 0 records in the BLOCK CONTAINS, it will leave up to System to get the optimal block size for buffer on the machine being processed (i.e., IBM-360, IBM-370, etc).
This rule is for IBM zOS environments and should be deactivated for other platforms.

CMS Snapshot Analysis - Run Analyzer - DOTNet - Information - How to split the DOTNet class file

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page provides you with information on how to split the dotnet class file, if the size of the file is more than 2 MB and leads to memory issue during the analysis process. This is rarely required anymore with improvements to the .NET analyzer.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

To split the class file whose size is more than 2 MB and causes the memory issue while running the analysis, you need to edit the class file to partial class files.

CMS Snpahsot Analysis - Run Analyzer - J2EE - Information - How to check if Hibernate is not used in the J2EE source code

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains How to check if Hibernate is not used in the J2EE source code?

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Details

With following steps one can check if hibernate is used or not:-

Search hibernate.properties in the source code. If not found then hibernate is not used.
Check if hibernate is there in hibernate.cfg.xml file. If not found then probability is that Hibernate is not used
Check if there is hbm.xml file (mapping file) in the source code. If not found then probability is that Hibernate is not used

Notes / Comments

CMS Snpashot Analysis - Run Analyzer - ABAP - Information - Analyse customization of SAP systems with CAST

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains the Analysis of SAP systems with CAST

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Details

The ABAP Analyzer analyzes ABAP code (in programs, includes, function pools, classes…) for custom components and system components.

Moreover, it can analyze ABAP code in customer exits and BAdIs.

However, it does not support enhancements nor system parameters for the moment.

Notes / Comments

Related Pages

CMS Snapshot Analysis - Run Analyzer - SAP - Information - How the SAP SYSTEM table is specified in CAST

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains How the SAP SYSTEM table is specified in CAST

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Details

How to check if the table is the SAP SYSTEM table or a user table

This information can be found in the .list file (i.e. SAP_Tables_nnnn.list). For each table, this file contains certain pieces of information such as or etc. If a table class begins with USER or APPL, the ABAP Analyzer considers the table as a USER table. The analyzer will consider a table with any other class, as a SYSTEM table.

CMS Snapshot Analysis - Run Analyzer - Information - MaxMem value

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes how to change the MaxMem value

Applicable CAST Version

Release	Yes/No
8.3.x	✅

Details

There is no impact on analysis resolution when changing the MaxMem value.

MaxMem can be changed in the section [ AMT ] of the %ALLUSERSPROFILE%\Application Data\CAST\CAST<version_number>\GloballySharedSettings.ini file:

[ AMT ]
MaxMem=

Notes / Comments

Related Pages

CMS Snapshot Analysis - Run Analyzer - Information - Understand AMT traces

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Follow the below steps which will describe different aspects of AMT memory log. It will help you identify possible out-of-memory issues.

How to understand the information in AMT log

List of Analyzers for which we need AMT traces : CMS Snapshot Analysis - Run Analyzer - Information - How to enable memory traces

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

How to understand the information in AMT log

CAST alloc Bytes : Represents memory used by the analyzer.

CMS Snapshot Analysis - Run Analyzer - Information - AMT Saving debug mode - How to get the IN Tables from the End User

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

AMT saving debug mode will allow to keep IN_OBJECTS table content into the KB after analysis

Keeping these information will speedup DATABASE team diagnostic on saving analysis phase in the following cases:

Duplicated object GUID
Performance issue during object comparison phase
Crash during the Save step (comparing object on server, Merging object on server)
Missing links between objects

Note: After completing the investigation, please ensure that saving debug mode is turned off by running the same script but replace the query’s OPTION_VALUE as ‘0’ and store procedure’s 2nd parameter as ‘OFF’.

CMS Snapshot Analysis - Run Analyzer - Information - Reducing memory consumption of the Inference Engine

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains provides the method to reduce the memory consumption of the Inference Engine

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Details

Some analyzers may be affected such as Java, PB, Mainframe, VB, and T-SQL analyzers:

In %ALLUSERSPROFILE%****\CAST\CAST<version_number>\GloballySharedSettings.ini search for the section**[Inference Engine].** If this section does not exist, create it and add the following parameters:

[Inference Engine]
LimitString=2000
LimitSubTarget=5000

Notes / Comments

CMS Snapshot Analysis - Run Analyzer - Information - Interrupting the analysis before the save phase

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes how to make sure analyzer will ask whether you need to save analysis result.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Details

When adding the following option to the %ALLUSERSPROFILE%\Application Data\CAST\CAST<version_number>\GloballySharedSettings.ini file, the analyzer (when the AMT saving system is in use) will ask whether you need to save analysis result (before starting the save phase):

[UniversalAnalyzer]
SavingPauses=1

Info

If you 0 instead of 1, the analyzer performs the save phase without asking.
Replace [UniversalAnalyzer] as appropriate

Notes / Comments

CMS Snapshot Analysis - Run Analyzer - Information - How to identify duplicate object GUIDs

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes about the method to find duplicate object GUIDs

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Details

(1) Activate AMT saving debug mode

(2) Run the following query on the KB:

select o1.OBJECT_ID as "ID of object 1"
 , o2.OBJECT_ID as "ID of object 2"
 , o1.NAME_ID as "GUID of object 1"
 , o2.NAME_ID as "GUID of object 2"
from IN_OBJECTS o1
 join IN_OBJECTS o2 on (o2.NAME_ID = o1.NAME_ID
 and o2.OBJECT_ID > o1.OBJECT_ID)

The rows returned by the query contain the objects having duplicated GUIDs.

CMS Snapshot Analysis - Run Analyzer - Information - What can lead an object to be marked as external

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This document explains what can make objects as external according to the analyzer in used. Note that in general when a project, or class is not analyzed in the KB - that means not selected in the analyzed files or folder, it is considered as external if used elsewhere.

NET Analyzer

J2EE Analyzer

C-CPP analyzer

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Details

.NET Analyzer

In .NET analyzer, a C# class library is consisdered as external object when the C# project of this libraru has not been analyzed in the same KB as the C# project which is refering to it.

CMS Snapshot Analysis - Run Analyzer - Information - Extracting JAR files

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains how to set a very short temporary extraction directory

Applicable CAST Version

Release	Yes/No
8.3.x	✅

Details

To set a very short temporary extraction directory in the folder c:\temp for example, in GloballySharedSettings.ini add these lines:
[ JavaAnalyzer ]
DeployDir=c:\temp

Notes / Comments

Related Pages

CMS Snapshot Analysis - FAQ

Mon, 01 Jan 0001 00:00:00 +0000

FAQ’s for Run Analyzer

How to analyze .js and .html files alone

In CAST AIP 8.2 or less, .js & .html files cannot be analysed, using .net analyzer only. It can only be analysed along with its associated project. (Hint: This is possible by creating a fake/dummy .net project associating the .js and .html files.)

Using J2EE analyser, it is possible to analyze .js and .html files alone.

From CAST AIP 8.3 onward please use the correct extension HTML5 and JavaScript

CMS Snapshot Analysis - Run Analyzer - CPP - Information - Conditions under which header file is set as internal or external

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The page explains the conditions under which the header file is set as internal/external.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

Conditions under which header file is set as internal/external

There are 3 kinds of files (and also of objects):

Internal files: First class objects, they are saved, links are traced from them, and diags are computed on them, they are visible in the dashboard.

CMS Snapshot Analysis - Run Analyzer - Information - How to enable memory traces

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains how to enable memory traces

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

There are two ways, depending on the technologies, to log the memory consumption when running an analysis : AMT traces or Perfmon Manager Traces.

Select the technology to know which memory traces to select

Technology

AMT Traces

Perfmon Traces

SAP ABAP

✅

Business Objects

CMS Snapshot Analysis - Run Analyzer - SQL PLSQL - Information - How to modify schema name in PLSQL extraction before analysis

Mon, 01 Jan 0001 00:00:00 +0000

Description

With the PL/SQL offline analyzer (new), changing the schema name from where the extraction is done leads to the change of all DB objects full name. As consequence, all DB objects will be seen as added/removed. To avoid this problem, please follow above stepsbefore generating a new snapshot. If the new snapshot has been generated before doing these steps, you will need first to restore the KB, CB dumps corresponding to the first extraction.

CMS Snapshot Analysis - Run Analyzer - Information - Power Builder - Pre-requisites for a Power Builder analysis

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page provides information about the specific mandatory steps required to run a Power Builder analysis.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Table of Contents

For Power Builder >= 11.5 only: install Power Builder

For Power Builder 11.5 and more recent : Install Power Builder

If you are analyzing an older version of Power Builder, then you do not need to install the product. A folder containing the Shared DLLs on the analysis machine is enough.

CMS Snapshot Analysis - Run Analyzer - JEE - Information - Cannot find file path of jar file

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page would confirm the behavior of analyzer when you encounters the below INF lines in the CAST-MS log file:

INF: 2017-01-23 20:22:33: cannot find : [T:\Test\JAR-Test\Single-Test\SourceAnalysis\FP\lib\Test-article-jartest-1.2.4.jar]\testat\met\businessobject\reference\article\Testfull.class
INF: 2017-01-23 20:22:33: cannot find : [T:\Test\JAR-Test\Single-Test\SourceAnalysis\FP\lib\Test-article-jartest-1.2.4.jar]\testat\met\businessobject\reference\article\Testfull_latest.class
INF: 2017-01-23 20:22:33: cannot find : [T:\Test\JAR-Test\Single-Test\SourceAnalysis\FP\lib\Test-article-jartest-1.2.4.jar]\testat\met\businessobject\reference\article\Testfull_new.class

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

The below lines from CAST-MS log are just information but not errors.

INF: 2017-01-23 20:22:15: cannot find : [C:\Program Files (x86)\Common Files\CAST\CAST\EnvProf\J2EE\EJB3\ejb3-persistence.jar]\javax\persistence\Column.class
INF: 2017-01-23 20:22:15: cannot find : [C:\Program Files (x86)\Common Files\CAST\CAST\EnvProf\J2EE\EJB3\ejb3-persistence.jar]\javax\persistence\DiscriminatorColumn.class
INF: 2017-01-23 20:22:15: cannot find : [C:\Program Files (x86)\Common Files\CAST\CAST\EnvProf\J2EE\EJB3\ejb3-persistence.jar]\javax\persistence\DiscriminatorValue.class
INF: 2017-01-23 20:22:15: cannot find : [C:\Program Files (x86)\Common Files\CAST\CAST\EnvProf\J2EE\EJB3\ejb3-persistence.jar]\javax\persistence\Embeddable.class
INF: 2017-01-23 20:22:15: cannot find : [C:\Program Files (x86)\Common Files\CAST\CAST\EnvProf\J2EE\EJB3\ejb3-persistence.jar]\javax\persistence\Entity.class

CMS Snapshot Analysis - Run Analyzer - Information - How to reproduce user issues for Extension

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains how to reproduce Fatal Error , Non-Fatal Error, Performance issue and warnings that occur during analysis or snapshot of a Universal Analyzer technology.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Action plan

Perform the following steps to reproduce Fatal Error, Non-Fatal Error, Performance issue and Warnings that may occur during analysis or snapshot of a Universal Analyzer technology.

In order to proceed with the below steps, get the Relevant input based on the following categories.
Non-Fatal Error / Warning / Fatal Error - Relevant Input
Performance Issue - Relevant Input

CMS Snapshot Analysis - Run Analyzer - J2EE - Information - How to find out the list of ancestors of a class

Mon, 01 Jan 0001 00:00:00 +0000

Description

Ancestors can be interfaces implemented by the class, or parent classes extended by the class. This page explains how to list the ancestors of a class.

Applicable in CAST Version

Release	Yes/No
8.3.x	N/A

Applicable RDBMS

RDBMS	Yes/No
CSS	N/A

How to find out the list of ancestors of a class

HOW To****find out the list of ancestors of a class

Open the source file and look if the class implements some interface. It is the case if the class declaration contains the implements keyword

CMS Snapshot Analysis - Run Analyzer - DOTNet - Information - How to find out the list of ancestors of a class

Mon, 01 Jan 0001 00:00:00 +0000

Description

Ancestors can be interfaces implemented by the class, or parent classes extended by the class. This page explains how to list the ancestors of a class.

Applicable in CAST Version

Release	Yes/No
8.3.x	N/A

Applicable RDBMS

RDBMS	Yes/No
CSS	N/A

How to find out the list of ancestors of a class

HOW To****find out the list of ancestors of a class

Open the source file and look if the class implements some interface. It is the case if the class declaration contains the : (colon) symbol.

CMS Snapshot Analysis - Run Analyzer - Information - How to find out if a framework is used in an application

Mon, 01 Jan 0001 00:00:00 +0000

Applicable in CAST Version

Release	Yes/No
8.3.x	N/A

Applicable RDBMS

RDBMS	Yes/No
CSS	N/A

How to check whether a framework is used by an application

The general approach to find out if a given framework is used by an application is :

Ask customer or refer to the documentation provided to the Cast AIP Administrator.
Scan the source code (with Notepad++ for instance) for imports of classes from the framework at the beginning of the source files.

CMS Snapshot Analysis - Run Analyzer - DOTNet - Information - How to reproduce user issues

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page will help you to reproduce user issues when the Technology of the application is .Net

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
CSS2	✅

Action Plan

Perform the following steps to reproduce issue for .Net technology:

In order to proceed with the below steps, get the Relevant input
Always use a CAST AIP setup installation. For reproducing issues, flat installation is not recommended because the analysis/snapshot may fail. This can be due to files that are missing in the flat installation.

CMS Snapshot Analysis - Run Analyzer - J2EE - Information - How to reproduce user issues

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page will help you to reproduce the user’s issue when the Technology of the application is Java.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Action Plan

Perform the following steps for the reproduction of J2EE Issues:

In order to proceed with the below steps, get the Relevant input. If Sherlock cannot be run, get only the files which are the pertinent ones. Navigate to CMS Snapshot Analysis - Run Analyzer - Information - Source code for reproduction to find out what are the pertinent files.

CMS Snapshot Analysis - Run Analyzer - CPP - Information - How to reproduce user issues

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page will help you to reproduce the issue when the Technology of the application is CPP.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Info

Perform the following steps to reproduce issue for CPP technology:

In order to proceed with the below steps, get the Relevant input. If Sherlock cannot be run, get only the files which are the pertinent ones. Navigate to CMS Snapshot Analysis - Run Analyzer - Information - List of inputs required to reproduce issue related to one particular object - Archived to find out what are the pertinent files.

CMS Snapshot Analysis - Run Analyzer - Mainframe - Information - How to reproduce user issues

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page will help you to reproduce user issues when the Technology of the application is Mainframe.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Action Plan

Perform the following steps for the reproduction of Mainframe Issues:

In order to proceed with the below steps, get the Relevant input based on the type of issue.
Always use a CAST AIP setup installation. For reproducing issues, flat installation is not recommended because the analysis/snapshot may fail. This can be due to files that are missing in the flat installation.

CMS Snapshot Analysis - Compute Snapshot - Information - How to compute snapshot by skipping analysis

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Choose the reproduction scenario:

Compute a full snapshot by skipping Analysis
Compute DssRun command line
1. Compute DssRun command line with the argument LOCAL_IFPUG_GRAPH
2. Compute DssRun command line with the argument SMART_RANKING

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Action plan

Compute a full snapshot by skipping Analysis

Perform the following steps to generate snapshot by skipping analysis.

In order to proceed with the below steps, get the Relevant input

CMS Snapshot Analysis - Run Analyzer - SQL - Information - How to reproduce user issues

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page will help you to reproduce user issues when the Technology of the application is PL/SQL

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Info

Perform the following steps to reproduce <way what (in a brief way, since it is already explained in the Purpose paragraph>

In order to proceed with the below steps, get the Relevant input
Always use a CAST AIP setup installation. For reproducing issues, flat installation is not recommended because the analysis/snapshot may fail. This can be due to files that are missing in the flat installation.

CMS Snapshot Analysis - Run Analyzer - Oracle Forms - Information - How to reproduce user issues

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page will help you to reproduce user issues whether it is Fatal error, non fatal error, crash and warnings when the Technology of the application is Oracle Forms.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Action Plan

Perform the following steps to reproduce issue for Oracle Forms:

In order to proceed with the below steps, get the Relevant input
Always use a CAST AIP setup installation. For reproducing issues, flat installation is not recommended because the analysis/snapshot may fail. This can be due to files that are missing in the flat installation.

CMS Snapshot Analysis - Run Analyzer - Squirrel Analyzer - Update SQL XXL Table Size - Information - Check if the SQL XXL Tables were loaded

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page can be used to check if the SQL XXL Tables were properly loaded

Applicable in CAST Version

Release	Yes/No
8.3 x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

Checking SQLTABLESIZE information upload

To know which table has been tagged with the SQLTABLESIZE information, you can run on local site the following query:

SELECT OBJECT_NAME ,
 OBJECT_FULLNAME,
 OI.InfVal
FROM CDT_OBJECTS CO,
 ObjInf OI
WHERE OI.IdObj = CO.OBJECT_ID
AND OI.InfTyp = 115
AND OI.InfSubTyp = 1

Finding XXL tables

To know which are the XXL tables, you can run on local site the following query:

CMS Snapshot Analysis - Run Analyzer - Information - How to validate expected objects and links in CAST AIP documentation

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains how to validate in CAST AIP documentation the expected objects and links

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

Objects and links that are created by CAST product are the result of a modelling of the technology that is being analysed. As such while some modelling decisions for objects ’naturally’ derive from computer language concepts(classes, objects, functions etc) some others are more technical and are modelling of functionality (for instance web services) which are useful for connectivity between components. In order to find out if an object or link is EXPECTED or **NOT EXPECTED ,**the official CAST AIP documentation defines the modelling and product expectation. More specifically:

CMS Snapshot Analysis - Run Analyzer - Python - Information - How to check the syntax validity of a python file

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page provides the information about how to use the Python interpreter to check for the syntax validity of a Python file.

For more information, refer to:

Official Documentation : For Python

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

In order to identify whether a Python file is valid or not proceed as follows:

Open a command line from the path where your Python file exist.

CMS Snapshot Analysis - Run Analyzer - ABAP - Information - How to reproduce user issues

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page will help you to reproduce the user’s issue when the Technology of the application is ABAP.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Action Plan

Perform the following steps for the reproduction of ABAP Issues:

In order to proceed with the below steps, get the Relevant input. If Sherlock cannot be run, get only the files which are the pertinent ones. Navigate to CMS Snapshot Analysis - Run Analyzer - Information - List of inputs required to reproduce issue related to one particular object - Archived to find out what are the pertinent files.

CMS Snapshot Analysis - Run Analyzer - SQL Analyzer - Update SQL XXL Table Size - Information - Check if the SQL XXL Tables were loaded

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page can be used to check if the SQL XXL Tables were properly loaded.

Applicable in CAST Version

Release	Yes/No
8.3 x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

Checking SQLTABLESIZE information upload

To know which table has been tagged with the SQLTABLESIZE information, you can run on local site the following query:

SELECT OBJECT_NAME ,
 OBJECT_FULLNAME,
 OI.InfVal
FROM CDT_OBJECTS CO,
 ObjInf OI
WHERE OI.IdObj = CO.OBJECT_ID
AND OI.InfTyp = 1101000
AND OI.InfSubTyp = 2

Finding XXL tables

To know which are the XXL tables, you can run on local site, run the following query:

CMS Snapshot Analysis - Information - How to exclude objects from the dashboard using a SQL tool after module generation

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page provides information on how to exclude objects from the dashboard using a sql tool after module generation.

Excluding objects from the dashboard is excluding objects from the module, so will have an impact on Transactions and values for transactions in TCC if these objects are required for transactions.

For more information on this action, please refer to:

For 8.3: CMS - Modules tab

Applicable CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

CMS Snapshot Analysis - Information - How to check on and create links between application module and technology

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page provides assistance on checking links between application, module and technology and then creating the links if they do not exist.

Please see the image below which shows an example of links which should be in place:

Basically there should be a link between the application and the functional module, the application and the technology, the functional module and the technology, and between the technologies themselves.

The numbers in the image show the value of the link_type_id field that should be in place for each of these links in the dss_link and dss_link_info tables.

CMS Snapshot Analysis - Run Analyzer - DOTNet - Information - DOTNet core analysis

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains the behavior of Dot Net analyzer when analyzing Dot Net core projects and the method to identify whether a user has .NET core files.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Details

.NET Core is an open-source, general-purpose development platform maintained by Microsoft.

The project file of .NET Core does not contain any source file reference unlike we have for .NET framework project file.

CMS Snapshot Analysis - Run Analyzer - DOTNet - Information - DOTNet analysis PackageReference not found by analyzer

Mon, 01 Jan 0001 00:00:00 +0000

Description

When your package .NET code with PackageReference tag in the project file you will not encounter any alert as DMT does not support PackageReference referred to in the project file.

But while running an analysis you may see missing assembly warnings in the analysis log:

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Step by Step Scenario

Packaged and delivered the source code.
Ran the analysis and snapshot.
Validated analysis log

Solution

CMS Snapshot Analysis - Run Analyzer - Information - How front end and back end of an application are linked

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page gives information on the linkage between the front end and back end of an application.

See the image below. We have Front End of the application which is a Razor view (Razor HttpRequest) and Back end of the application is a .NET controller

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Details

In an application, there are two major parts. Front end code and back end code.

CMS Snapshot Analysis - Information - Which SQL rules are used when using code with the SQL analyzer extension

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page provides information on assisting with understanding which sql rules are being used with analyzing SQL code.

For more information, refer to:

Official documentation for the SQL analyzer: SQL

Applicable Platform or

Platform	Yes/No
8.3.x	✅

Details

This page provides information on assisting with understanding which metrics are being used when analyzing SQL code.

For example, if you are using the 3.4.4 version of the sql analyzer extension, then the following list of metrics is only used for items which have a CREATE statement (often found in the *.sql data definition language (DDL) files), so that they are part of the generation of the database (for 3.4.4 analyzer)

CMS Snapshot Analysis - Run Analyzer - T-SQL - Information - How to modify schema name in T-SQL extraction before analysis

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

With the T-SQL offline analyzer, changing the server and/or instance from where the extraction is done leads to the change of all DB objects fullname. As consequence, all DB objects will be seen as added/removed. To avoid this problem, please follow below stepsbefore generating a new snapshot. If the new snapshot has been generated before doing these steps, you will need to delete the last snapshot and apply the steps mentioned below.

Excerpt - The type or namespace name could not be found - Description

Mon, 01 Jan 0001 00:00:00 +0000

Description

After the analysis of a DOTNet application, open the analysis log and verify the existence of the following warning(s)

2018-08-13 22:23:00.115 Warning MODULMSG ; Job execution C:\CASTMS\Deploy\website_with_dot\WEBSITE_CODE\Website.UI\Home.aspx.vb(56,92): error CS0246: The type or namespace name ‘XXXX’ could not be found (are you missing a using directive or an assembly reference?)

2018-08-13 22:13:55.445151 Warning MODULMSG ; Job execution C:\CASTMS\Deploy\website_with_dot\WEBSITE_CODE\Website.UI\PoleAvailabilityManager.cs(25,17): error CS0234: The type or namespace name ‘VisualStudio’ does not exist in the namespace ‘Microsoft’ (are you missing an assembly reference?)

Excerpt - The type or namespace name could not be found - All

Mon, 01 Jan 0001 00:00:00 +0000

Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Step by Step Scenario

Package the source code
Run the analysis
Verify the analysis log

Action Plan

Check if the warnings are due to missing libraries or source code. The .NET compiler used by the analyzer is resolving the references either from the external assemblies or from other projects that have been added in the source code. Unresolved references are creating alerts during source code delivery in DMT.
1. Open Delivery manager tool and check if there are any alerts for missing source code, that were raised during packaging of .NET source code.
  1. For any alerts refer Delivery Manager Tool - Package - Validation - Alerts in order to resolve them.
  2. Check if the alert is coming for the project file which is physically not present in the source code.
    1. Lets see an example: Below is the code snippet of Sherlock.application.module.csproj

Excerpt - CMS Snapshot Analysis - Run Analyzer - Non Fatal Error - JEE with Core CAST AIP - Cannot find CAST Script file for the module named XXX - Purpose

Mon, 01 Jan 0001 00:00:00 +0000

This page explains how to solve the below error message :

Cannot find CAST Script file for the module named ‘xxxx’
The preprocessing of the CAST Script file
’<Name CastScript File>.castscript’ has failed.
Verify that use statements reference a correct module name.

This error message occurs when the analyzer is not able to find a castscript file that has been defined in the application.

Excerpt - CMS Snapshot Analysis - Run Analyzer - Non Fatal Error - JEE with Core CAST AIP - Can not resolve java file name - Purpose

Mon, 01 Jan 0001 00:00:00 +0000

This page gives the approach to solve the following error message “can not resolve java file name” as type or variable in block from block “.These types of error are usually linked to missing or unresolved inputs.

Excerpt - CMS Snapshot Analysis - Run Analyzer - Non Fatal Error - JEE with Core CAST AIP - Can not resolve java file name - Action Plan

Mon, 01 Jan 0001 00:00:00 +0000

Perform the following steps:

Check in the source code that the class reported in error log exists. If file does not exist in the source code then it is an expected behavior.
Check if the CMS - J2EE Environment Profiles are set in order for external modules to get resolved.
Check that no missing or unresolved libraries impact the resolution of ‘java file’
If you have not resolved issue, contact CAST Technical Support with below relevant input.

Excerpt - CMS Snapshot Analysis - Run Analyzer - Non Fatal Error - JEE with Core CAST AIP - Cannot find CAST Script file for the module named XXX - Action Plan

Mon, 01 Jan 0001 00:00:00 +0000

Check if the castscript file exists.
1. Copy the path defined in the log file and paste it in the explorer and check if the corresponding castscript file exists.
  1. If the file does not exist this may be due to the fact that the file was added as part of a custom environment profile and a custom castscript file is referenced. This file must be available in the machine where the analysis has been performed.
  2. If the file exists then you need to do the following:
    1. Replace the existing x query file present in \EnvProf\J2EE\Spring framework\cast-spring-config-3-x.xq. with cast-spring-config-3-x.xq file and run the analysis.
      This issue has been fixed in 8.2.7
2. If the above does not solve issue proceed to next step
Check if Custom CAST Script Library Directory path is set
To set the CAST Script Library, in the Left panel, go to Technologies tab, open the J2EE technology, select the Platform Setting tab. CAST Script Library Directory should have a value is correctly set as shown below.

Figure 1

Excerpt - CMS Snapshot Analysis - Run Analyzer - Non Fatal Error - JEE with Core CAST AIP - - EJB - Failed to Parse XML file comment or processing instruction expected - Purpose

Mon, 01 Jan 0001 00:00:00 +0000

This page gives the approach to solve the following error message**" Failed to parse xml file: (comment or processing instruction expected (pos l: 2 col: 1))".**

Excerpt - CMS Snapshot Analysis - Run Analyzer - Non Fatal Error - JEE with Core CAST AIP - EJB - Failed to Parse XML file comment or processing instruction expected - Action

Mon, 01 Jan 0001 00:00:00 +0000

These errors messages are caused by incomplete tags in the XML files. The log file message does not have details on the malformed EJB xml so for all the existing XML files:

Open the XML file in a web browser
1. If all tags are parsed without errors proceed to next xml file
2. If tags are not correct you will have a similar message to the below screenshot:
  
  In this case manually add the missing tag

Excerpt - CMS Snapshot Analysis - Run Analyzer - Non Fatal Error - JEE with Core CAST AIP - - EJB - Failed to Parse XML file comment or processing instruction expected - StepByStep

Mon, 01 Jan 0001 00:00:00 +0000

Discover the source
Accept and run the analysis
Check the log for the errors as shown in below screenshot.
Figure 1

Excerpt - CMS Snapshot Analysis - Run Analyzer - Non Fatal Error - JEE with Core CAST AIP - Failed to parse xml file unterminated end tag name - Action Plan

Mon, 01 Jan 0001 00:00:00 +0000

The error message indicates that the analyzer has failed to parse xml file because the end tag of an element is missing. This is an expected behavior as the xml tag is not complete.

Perform the following steps:

Using a text editor like Notepad++ , search in all the XML files present in the source code for the mentioned tag. For instance in the following example:

the ‘Setting’ tag is opened with no termination tag in those files, so you should search for ‘Setting’ string
Open the detected XML file, add the termination tag and save the file
Run analysis

Excerpt - CMS Snapshot Analysis - Run Analyzer - Non Fatal Error - JEE with Core CAST AIP - Syntax error Can not resolve type while analyzing code that uses IBM WAS libraries - Purpose

Mon, 01 Jan 0001 00:00:00 +0000

This page gives information on how to resolve issue when the following error message is present in analysis log, while analyzing a J2EE application that uses IBM WebSphere libraries:

Syntax Error : Can not resolve type com.ibm.ws.webservices.engine.enum.Style

Excerpt - CMS Snapshot Analysis - Run Analyzer - Non Fatal Error - JEE with Core CAST AIP - Syntax error Can not resolve type while analyzing code that uses IBM WAS libraries - Action Plan

Mon, 01 Jan 0001 00:00:00 +0000

Action Plan

The syntax error message appears because in JDK 5.0 (1.5), word “enum” is reserved as a keyword. The word “enum” should not be used in custom types which is the case for “com.ibm.ws.webservices.engine.enum.Style”.

As a solution:

Change the JDK version used to compile this application to JDK 1.4
Run analysis

Excerpt - CMS Snapshot Analysis - Run Analyzer - Non Fatal Error - JEE with Core CAST AIP - Failed to parse xml file unterminated end tag name - Purpose

Mon, 01 Jan 0001 00:00:00 +0000

This page gives information on how to resolve issue when the following error message is present in analysis log:

Failed to parse xml file: (unterminated end tag ‘’)

Excerpt - CMS Snapshot Analysis - Run Analyzer - Non Fatal Error - CPP - Remedy the errors read in the analysis log file - ActionCommon

Mon, 01 Jan 0001 00:00:00 +0000

Action Plan

Perform the following steps:

If the source code is built in VC6 then the project files created would be with the extensions .dsp and .dsw which are not managed by any discoverers which is already documented. This approach will decrease the effort we need to put in the manual configurations.
1. Open the project file .dsw and / or all required .dsp in a recent Microsotf Visual Studio IDE.
2. Visual studio will automatically propose to upgrade project files and create .vcxproj files
3. Use DMT and package the new source code with .vcxproj files which would discover the AUs automatically with correct configuration and then deliver
4. Accept the delivery and set it as current version.
5. In CMS select the Visual studio version used to convert the .dsp files as IDE
For all the projects built on Microsoft IDEs. Having Visual Studio installed is mandatory (Third-party Software Required by CAST)To check if the VS is installed correctly or not we need to follow below steps.
1. In CMS, Open ‘Manage Environment Profiles’ Dialog box
2. Select the IDE which you choose in CMS.
  Figure 1
3. the $(WINREGISTRY…..) values are existing in the registry
4. that the value of these registry keys are valid folders on the analysis machine, and that required subfolders are existing
When we cannot install a VS on the analysis machine do the following.
1. Get the list of necessary folders by looking at the corresponding Environment Profile as explained in Step 2.
2. Copy necessary folders from another computer where the VS is installed
3. Create the clone for for the environment profile “VC++ XXXXX - Mandatory part” and replace the values
  $(WINREGISTRY,“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\CurrentInstallFolder”)\include
  with the path of the folders, for exemple
  C:\MYVCXXXHEADERS\include
Compilation Error messages
1. When you get many compilation error messages (‘parser’ xxx expected, parser variable has already a name, parser xxxx)(one or two message per line of an analyzed file), first try to correct erroneous include paths, and then work on macro definition. The main exception to this rule is when you see that a wrong header file is included (for instance, trying to include <windows.h> on linux), and the selection of file to include depends on a configuration macro. As a tip, you should not usually have to define more than a dozen macros. As long as there is not a reasonable number of parser messages, it helps nothing to let the analysis go further. Therefore, the macro definitions must be fixed first in the job configuration. Always run a test analysis to check if you have errors in the test analysis log and then try to improve it one by one.
2. In case the source code contain C & C++ files or some files are written in C++, even if their name ends with “C”, then it is important to separate your C and C++ files into 2 separate jobs, linked together.
3. If the log contains some of the below error messages, it means that there is a compilation problem. Configure the job so that the first file gets analyzed without errors:
  1. [Configuration] error: Encountered #error directive: <For instance : MFC requires use of Winsock2 .h>
    1. This is the message issued by the pre-processed file and comes when you have directly or indirectly included < Winsock2.h> before which conflicts with for instance< Winsock2.h> that has to be used for MFC. The compilation stops after this message and analysis ends with a fatal error
    2. Check for the configuration errors before this fatal error and fix those configuration errors first.If it doesn’t solve the issue,proceed by the process of Dichotomy to identify which file causes the issue.
  2. [ Configuration ] FAR: Unknown identifier ‘XXX’ is probably an unknown compilation directive, the following results could be inconsistent. (file ‘S:\WORLDWIDE...\SSDLL.H’, line 154)__ [ Configuration ] FAR: Please consider reviewing your settings. (file ‘S:\WORLDWIDE...\SSDLL.H’, line 154)
  3. [Configuration] error: Encountered #error* directive: ERROR : Use of C run time library internal header file .. (file ‘C:\PROGRAM FILES (X86){}MICROSOFT VISUAL STUDIO 10.0\VC\CRT\SRC\CRTDEFS.H’, line 36). This usually comes from include paths, defined by the user, that refer to Microsoft header files. The include paths encompass too many directories, and should be more restrictive. See section about Microsoft include paths.
Parser Error messages. The below warnings concern internal functions of gcc __builtin_va_xxx (referenced in stdargs.h). The warning is specifically a system warning with no impact on the analysis:
1. [ parser ] xxx : Single operand or parenthesized expression expected. (file ‘U:\company\appname\SRC\xyz.C’, line 163)
  When such messages appear, they may not denote a serious problem. If they appear inside the body of a function, you will lose some links starting from the function, and no more. If they appear in the function header, you will maybe lose the whole function. When the code around the error refers templates (code with lots of “<>” : std::map<std::vector >), this is often an effect of missing header files (see section about pre-processor messages), which can be identified by running test analysis and checking the test analysis log. After running test analysis user will see the entries of missing headers in the test analysis log.
2. [ parser ] [: Unmatched parenthesis, brace or bracket, last valid position at …
  and there is only a “<:” at the mentioned position:
  ‘<:’ is a CPP convention for denoting ‘[’. In this specific case, you need to deactivate the option Accept trigraphs
3. Unresolved name ‘xxx’(file ‘Z:\SOURCE...\ASN1KEYS.C’, line 79)
4. Preprocessor cannot find file ‘xx\xxx.hpp’. (file ‘Z:\SOURCE...\ABOUT.H’, line 5)
5. Function xxxx() is called without having been declared. (file ‘Z:\SOURCE...\ASN1KEYS.C’, line 80)
6. [Parser] –: Unexpected token: –. [ Unexpected token is raised in cases when the trigraphs is used in the source. So to get rid of such warning, Just check the option “accept” trigraphs in the analysis option ]
7. If you encounter warnings like Warning: [Parser] __attribute__: ‘;’, ‘,’, or ‘=’ expected, refer CMS Snapshot analysis - Run Analyzer - Warnings - CPP with Core CAST AIP - Parser_attribute