Page tree
Skip to end of metadata
Go to start of metadata
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(tick) 
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 for the reproduction of Mainframe Issues:

  1. In order to proceed with the below steps, get the Relevant input based on the type of issue.
  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 central base as well 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 should be in the mapped deploy folder.
    6. If customer provides only couple of files as requested by support, then recreate the user defined analysis unit and add the files in the specific configuration tabs to analyze those files. Refer page
    7. Running the analysis depends on the type of issues as below:
      Crash/Fatal error: Map the deploy folder and run the analysis to reproduce the crash. If there is a fatal error check the analysis log file the last file parsed and then create a user defined AU by configuring the file found as last file in the analysis log and run the analysis. Check if the fatal error is reproducible, if not then run the full analysis.
      Syntax error warnings: It is not advisable to run the complete analysis while reproducing the syntax error only running couple of files giving syntax error or particular analysis unit is enough.
      Other warnings: If the warning is related to unresolved copybook, you should check if the copybooks are physically present in the deploy folder if not then it is an expected behavior.
      Performance issue: Check in the analysis log and see which analysis unit is taking more than expected time and try to run only that analysis unit and see if the issue is getting reproduced. If the analysis log does not gives clarity on analysis unit (performance issue while loading the configuration, saving phase) then run the analysis on whole source code
    8. 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
    9. Configure SQLtablesize only if the issue is related to SQLtablesize else we can remove it from configuration that is from CAST-MS.
    10.  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
    11.  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
    12. 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
    13. If Architecture model is configured, the same configuration should be made, for more info, please refer this page
    14. 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

 

 

 

 

 

 

  • No labels