Transaction Configuration Center - Enhancement - Transactional Functions - Status Variation - Transaction status is DELETED with unchanged source code

This page explains the case when the transaction is flagged as deleted in the evolution node, while there is no change in the analyzed code source.

1. Run at least 2 snapshots
2. Connect to TCC
3. Observe the variation

1. Check if the DELETED Transaction is not an ADDED/DELETD Transaction, for this refer to Transaction Configuration Center - Enhancement - Transactional Functions - Status Variation - Transactions status are ADDED and DELETED If not go to the next step
2. Read the status in the TF of the entry point
3. If the status in the TF of the entry point is DELETED
   
   1. Read the object status itself of the entry point
   2. If the object status itself  is DELETED then refer to CAST Engineering Dashboard - Object - Missing objects
   3. If the object status itself  is UNCHANGED:
      1. Compare the entry points configuration between the 2 runs, Is the entry point was configured in the previous run but not in the current run? If yes then this explains the the reason for having a DELETED transaction, else go to the next step
4. If the status in the TF of the entry point is UNCHANGED
   
   1. Check if the Transaction was a valid Transaction in the previous run that becomes an empty Transaction in the current run, in order to check this refer to the following section How to determine if I have detected all the transactions? If yes then do the bellow steps else go to the next step:
      1. Open TCC of current run and previous run
      2. View the call graph of Transaction from previous run
      3. Open Enlighten with the knowledge base associated to the current run
      4. Try to trace the Call graph of Transaction from previous run:
         1. Place the object corresponding to the entry point in the Graphical View
         2. Add Linked Objects of the object corresponding to the entry point as seen in the full call graph of TCC
         3. Place the objects corresponding to the linked objects in the Graphical View
         4. Add Linked Objects of the linked objects as seen in the full call graph of TCC
         5. Do point 3 and 4 until:
            
            1. You are not able to trace the Transaction because of missing link then refer to CMS Snapshot Analysis - Run Analyzer - Missing or Wrong links between two objects
            2. Or you are not able to trace the Transaction because of missing objects then refer to  CMS Snapshot Analysis - Run Analyzer - Missing objects
            3. Or you are able to trace the missing path then refer to Transaction Configuration Center - AFP Calibration - Transactional Functions - Missing Links

   2. Check if the Transaction is not a detailed Transaction of merged transactions, for this run the following query on the current local base - SQL Queries - CAST Knowledge Base - Queries on Transactions - How to get the Merged object of a Main object in a Transaction Merge

      If the query returns rows then the Transaction is merged with another one and the query will provide you the name of the Transaction that becomes the root merge of the deleted Transaction.

5. If the status in the TF of the entry point is MODFIED, This sounds strange but possible. This can happen if the deleted Transaction on which we are investigating is a root Transaction of a Transactions merge, and the entry point of the detail Transaction is DELETED in the current run, in this case the root cause of deletion of Transaction that we are investigating on can be due to the deletion of the merged Transaction.
   Run the following query on the previous local base to get the name of the merged Transaction - SQL Queries - CAST Knowledge Base - Queries on Transactions - How to get the Merged object of a Main object in a Transaction Merge

   If the query returns rows then the Transaction was merged with another one and the query will provide you the name of the detail Transaction, now you need to investigate the root cause of the deleted merged Transaction, by following the current troubleshooting guide

If the above steps do not solve your issue contact CAST Technical Support. with the following Relevant input

• If your AIP version is 8.3.26 and all the transactions are deleted or empty for a mainframe application then, please note that this is a known issue with Mainframe TCC setup file in 8.3.26 AIP. So to resolve the issue you need to manually import the attached TCCSetup file MainframeTCCSetup in TCC and compute the FP. Also, note that this file is corrected in AIP version 8.3.27

Ticket # Number, Number