CMS Snapshot Analysis - Compute Dependency Dataset - Error - Failed to generate the list of set

This page provides the solution to the error message Failed to generate the list of set, which occurs during the Compute dependency dataset phase as shown below :

Figure 1

1. Add an Application with two J2EE AUs ''Monster_Events_JSP" and "DATAFLOW_JSP1"
   
2. In dependency tab add two dependencies
     Dependency1 : Source - Monster_Events_JSP; Target -  DATAFLOW_JSP1
     Dependency2 : Source -  DATAFLOW_JSP1 ; Target - Monster_Events_JSP
   
3. Run snapshot

If your analysis fails with the error Failed to generate the list of set  when you try to run analysis at application level then Check in CAST-MS log for 'A cycle was detected' then fix the cycle using 'Details of the cycle' information.
This may mean you have cyclical dependency between Analysis Units. Cyclic dependencies is not introduced by DMT and is introduced due to manual addition of dependencies by the user. Cyclical dependency was supported in 7.0 but is not supported in 7.3. Hence you might face this error after carrying out migration from 7.0 to 7.3 also.

In 7.3.x, x<5 there was no detailed message in CAST-MS which could be used to detect the dependency cycle. But in 7.3 5 this can be resolved as there is a detailed message in the CAST-MS log. Steps to detect and resolve cyclic dependency are given below -

1. Open the CAST-MS log file and search for "A cycle was detected". The detail of the cyclical dependency is displayed in the log as follows:

   ERR: 2015-05-05 06:37:42: A cycle was detected in the dependencies between execution units
   INF: 2015-05-05 06:37:42: Details of the cycle
   INF: 2015-05-05 06:37:42: Analysis Units of this group :
   INF: 2015-05-05 06:37:42: AnalysisUnit : DATAFLOW_JSP1
   INF: 2015-05-05 06:37:42: Analysis Units of this group :
   INF: 2015-05-05 06:37:42: AnalysisUnit : Monster_Events_JSP
   INF: 2015-05-05 06:37:42: Analysis Units of this group :
   INF: 2015-05-05 06:37:42: AnalysisUnit : DATAFLOW_JSP1

2. To resolve the error, select the Dependencies tab (in the Application editor in the CAST Management Studio)
3. Remove the dependency that is causing the cycle

4. Run your analysis again until you no longer encounter the error.

   Note - The message 'A cycle was detected' can be displayed even if the analysis does not fail.

   If you receive this error and your analysis fails when you try to run individual analysis units then you may run the analysis at application level, which would make the analysis proceed further but the error A cycle was detected will still exist in the CAST-MS Log.

Ref call # 29307