Page tree
Skip to end of metadata
Go to start of metadata
Purpose

This page lists the prerequisites, entities involved and steps to reproduce customer issues involved with Transaction Configuration Center.

Observed in CAST AIP

 

Release
Yes/No
8.3.x(tick)
8.2.x(tick)
8.1.x(tick)
8.0.x(tick)
7.3.x(tick)
Observed on RDBMS

 

RDBMS
Yes/No
Oracle Server(tick)
Microsoft SQL Server(tick)
CSS2(tick)
CSS1(tick)
Action plan

Perform the following steps to reproduce issues related to TCC

  1. In order to proceed with the below steps, get the Relevant input
  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. For performance issues on compute function points and/or load results, Synchronize the databases, Update the statistics on the local and central bases, then compute function points and/or load results (An additional, important input for investigation is to activate SQL Traces with the help of Transaction Configuration Center - Information - How to launch TCC in SHOW SQL mode in order to get the SQL traces while computing function points and/or loading results)
  4. For Crashes, reproduce the issue on the support environment using the customer schemas with the provided step by step scenario. If the issue is not reproduced on the support environment then reproduce the issue on user environment and create a dump file using Task Manager, for more information refer to What is a dump, and how do I create one?
  5. If your issue is related to missing, unexpected, inconsistent Data Functions or Transactions then:
    1. If the issue is under AFP Calibration node, then do the following:
      1. Check the exact step by step scenario, you have to check if the scenario is run analysis (with or without taking snapshot), open TCC then observe the issue or run analysis (with or without taking snapshot), open TCC, compute application function points then observe the issue. You can check this by comparing the analysis log file date (execution date) with the TCC log file date (execution date).
      2. Follow the same steps
        Internal to the support: If the step by step scenario include to take a full snapshot, then you can run analysis then run only a prepare Snapshot:
    2. Else if your issue is under Enhancement node, then:
      • Get the exact step by step scenario:
        • Scenario 1: Compute a snapshot by skipping analysis
        • Scenario 2: Run analysis and take a snapshot
      • Apply the exact step by step scenario
      • Open TCC and observe the result

Important note

Note that an application can contain several technologies, and it's not always necessary to run the analysis for the whole application, so you need to identify the technologies that are involved in the issue. For example, if your application contain J2EE, CPP and Oracle Forms, and you are facing an issue of incomplete transaction where the call hierarchy include only J2EE and Oracle Forms then there is no need to run analysis for the CPP part, you can deactivate all AU of CPP before running the analysis. If you will run analysis in your reproduction attempt then check what are the technologies that are involved in you issue and follow the page(s) bellow:

  1. CMS Snapshot Analysis - Run Analyzer - Information - How to reproduce user issues for Extension
  2. CMS Snapshot Analysis - Run Analyzer - DOTNet - Information - How to reproduce user issues
  3. CMS Snapshot Analysis - Run Analyzer - J2EE - Information - How to reproduce user issues
  4. CMS Snapshot Analysis - Run Analyzer - CPP - Information - How to reproduce user issues
  5. CMS Snapshot Analysis - Run Analyzer - Mainframe - Information - How to reproduce user issues
  6. CMS Snapshot Analysis - Run Analyzer - SQL - Information - How to reproduce user issues
  7. CMS Snapshot Analysis - Run Analyzer - Oracle Forms - Information - How to reproduce user issues
  • No labels