Page tree
Skip to end of metadata
Go to start of metadata
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.2.x(tick) 
8.1.x(tick) 
8.0.x(tick) 
Observed on RDBMS
RDBMS
Yes/No
Oracle Server(tick)
Microsoft SQL Server(tick)
CSS2(tick)

Action Plan

Perform the following steps to reproduce issue for CPP technology:

  1. 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 to find out what are the pertinent files.
  2. 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.
  3. Import the databases mngt and local if reproducing the analysis issue else import all the three bases for snapshot issue.
  4. Synchronise the databases from CAST-MS
  5. Configure the analysis

    1. Open CAST-MS

    2. Get the deployment folder path.

    3. Map the source code path in order to respect the deployment defined in configuration.
    4. Go to the current Version tab and check the path of AU whether it is mapped to the same path of the deployment folder.
    5. If customer provides the complete source code then the complete source code in the mapped deploy folder and run the analysis.
    6. If customer provides only couple of files as requested by support, then proceed as explained in Reproduce with the Preprocessed File :
    7. Configure DLM only if the issue is related to DLM. If not required delete it from CAST-MS because while configuring the analysis you might not have the dlm.xml file, for more info please refer this page
    1. Only if the issue is related to missing links and reference pattern, configure reference pattern otherwise remove it from CAST-MS, for more info please refer this page
    2. If you don't require the settings in"Tools before analysis" and "Tools after analysis" for your reproduction then remove these configurations from Content enrichment tab in CAST-MS, for more info, please refer this page
    3. Uncheck the analysis units of other technologies if you have other technologies apart from the technology that is being analyzed but in case of missing links between inter technologies (for ex: missing links between java method and oracle table) you have to be careful while un-checking the analysis units of other technologies. This will shorten down the analysis run time, for more info, please refer this page
    4. If Architecture model is configured, the same configuration should be made, for more info, please refer this page
    5. Check all the tabs in the CAST-MS for different configuration done by customer, make sure you have the same configuration otherwise your analysis will fail at some other step and you will end up with different issue.

  6. Run the analysis

Reproduce with preprocessed file

Reproduce with the Preprocessed File

  1. Create new test project, using as source the PreprocessedFile.cpp. Accept version and set as current 
  2. Create new C/C++ Analysis unit 
  3. Add as source  PreprocessedFile.cpp file 
  4. First Test Analysis on the AU (can provide useful message for further investigation, such like quoting missing header files)
  5. Then Run Analysis and see if issue is reproduced

 

 

  • No labels