SQL Queries - CAST Knowledge Base - Queries on metrics and diagnostics on Documentation - V2

SQL Queries - CAST Knowledge Base - Queries on metrics and diagnostics - How to check which Metrics computation option has been calculated

Mon, 01 Jan 0001 00:00:00 +0000

Purpose of Query

Thus query will help you to check which Metrics computation option has been calculated.

Applicable CAST Version

Release	Yes/No
8.3.x	✅
8.2.x	✅

Applicable RDBMS

RDBMS	Yes/No
Oracle Server	❓
Microsoft SQL Server	❓
CSS	✅

Query for CSS

SELECT CASE 
 WHEN infval = 0 THEN 'SPA Metrics computation: no metrics computation' 
 WHEN infval = 1 THEN 'SPA Metrics computation: all metrics' 
 WHEN infval = 2 THEN 
'SPA Metrics computation: all metrics except copy/paste and commented code' 
ELSE 'N/A' 
END 
FROM anainf ai 
 JOIN anajob aj 
 ON aj.idjob = ai.idjob 
 AND aj.jobtyp = 3001 
WHERE ai.inftyp = 1 
 AND ai.infsubtyp = 31;

Query result example

SQL Queries - CAST Knowledge Base - Queries on metrics and diagnostics - How to detect a metric with its total procedure missing

Mon, 01 Jan 0001 00:00:00 +0000

Purpose of Query

The query detects the missing total/detailed procedure in a metric.

Applicable CAST Version

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅
7.2.x	✅
7.0.x	✅

Applicable RDBMS

RDBMS	Yes/No
Oracle Server	❌
Microsoft SQL Server	❌
CSS2	✅
CSS1	✅

Query for CSS

Run the below query for total procedure :

SELECT vt.metric_value_procedure_name, 
 t.metric_id AS "METRIC ID", 
 t.metric_name AS "METRIC NAME", 
 CASE t.metric_type 
 WHEN 0 THEN 'deactivated' 
 ELSE 'activated' 
 END 
FROM <knowledge_base>.dss_metric_value_types vt 
JOIN <knowledge_base>.dss_metric_types t 
ON vt.metric_id = t.metric_id 
WHERE upper(vt.metric_value_procedure_name) NOT IN 
 ( 
 SELECT upper(sp.routine_name) 
 FROM information_schema.routines sp 
 WHERE sp.routine_schema = '<Knowledge_base>') 
AND vt.metric_value_index = 2 
AND t.metric_name NOT LIKE 'DELETED%'

Query result example

SQL Queries - CAST Knowledge Base - Queries on metrics and diagnostics - How to get DETAIL and TOTAL procedures

Mon, 01 Jan 0001 00:00:00 +0000

Purpose of Query

The below SQL queries provides the DETAIL and TOTAL procedures of Quality rules.

Applicable CAST Version

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
Oracle Server	❓
Microsoft SQL Server	❓
CSS3	✅
CSS2	✅

Query for CSS

Run the following queries on the CB:

SELECT TT.METRIC_SCOPE_PROCEDURE_NAME AS DetailProc , T.METRIC_ID , T.METRIC_NAME , COALESCE(P.OBJECT_TYPE_ID,0) AS OBJECT_TYPE_ID, VT.METRIC_VALUE_PROCEDURE_NAME AS TotalProc FROM DSS_METRIC_TYPE_TREES TT , DSS_METRIC_VALUE_TYPES VT , DSS_METRIC_TYPES T LEFT OUTER JOIN DSS_METRIC_PARAM_TYPES P ON ( P.METRIC_ID = T.METRIC_ID AND P.PARAM_INDEX = 1 ) WHERE T.METRIC_GROUP = 1 AND TT.METRIC_ID = T.METRIC_ID + 1 AND VT.METRIC_ID = T.METRIC_ID AND VT.METRIC_VALUE_INDEX = 2 AND metric_name LIKE ‘%<METRIC_NAME>%’ ORDER BY METRIC_NAME

SQL Queries - CAST Knowledge Base - Queries on metrics and diagnostics - How to get the Number of code lines at application or system level in the Knowledge Base

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains how to get the number of code lines at application/system level in the knowledge Base. The page is relevant for the following cases:

One application with more than one module.
One system with more than one application.
One system with one application containing more than one module.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS	✅

Details

SQL Queries - CAST Knowledge Base - Queries on metrics and diagnostics - How to list all Quality Rules and their definition from the Metric Tree

Mon, 01 Jan 0001 00:00:00 +0000

Purpose of Query

This query returns the list of all Quality Rules and their definition from the Metric Tree.

Applicable CAST Version

Release	Yes/No
8.3.x	✅
8.2.x	✅

Applicable RDBMS

RDBMS	Yes/No
Oracle Server	❓
Microsoft SQL Server	❓
CSS	✅

Query for CSS

 SELECT COALESCE(tech.techno_type_name, 'AllTechno') AS technology_name, 
 COALESCE(PT.object_type_id, 0) AS technology_id, 
 T.metric_id, 
 T.metric_name, 
 COALESCE(p.idprop, 0) AS Property_ID, 
 COALESCE(p.dsc, ' ') AS Property_Name, 
 COALESCE(T.scope_id, 0), 
 COALESCE(S.setname, 'NONE'), 
 TT.metric_scope_procedure_name AS detailed_proc_name, 
 VT.metric_value_procedure_name AS total_proc_name 
FROM dss_metric_type_trees TT, 
 dss_metric_value_types VT, 
 dss_metric_types T 
 LEFT OUTER JOIN dss_metric_param_types PT 
 ON PT.metric_id = T.metric_id 
 AND PT.param_index = 1 
 LEFT OUTER JOIN dss_techno_display_vw tech 
 ON tech.techno_type_id = PT.object_type_id 
 LEFT OUTER JOIN (SELECT DISTINCT d.dsc, 
 p1.idprop 
 FROM propattr p1, 
 propattr p2, 
 objdscref d 
 WHERE p1.idprop = p2.idprop 
 AND p1.attrnam = 'INF_TYPE' 
 AND p1.intval = d.inftyp 
 AND p2.attrnam = 'INF_SUB_TYPE' 
 AND p2.intval = d.infsubtyp) p 
 ON p.idprop = T.property_id 
 LEFT OUTER JOIN (SELECT setid, 
 setname 
 FROM set_definitions) S 
 ON S.setid = T.scope_id 
WHERE T.metric_group = 1 
 AND T.metric_type != 0 -- Not Deleted 
 AND TT.metric_id = T.metric_id + 1 
 AND VT.metric_id = T.metric_id 
 AND VT.metric_value_index = 2 
 AND EXISTS (SELECT 1 
 FROM dss_metric_type_trees x 
 WHERE x.metric_id = T.metric_id)

Query result example

SQL Queries - CAST Knowledge Base - Queries on metrics and diagnostics - How to run DETAIL and TOTAL procedures manually

Mon, 01 Jan 0001 00:00:00 +0000

Purpose of Query

This page explains how to execute the DETAIL and TOTAL procedures manually against the KB (i.e. execute them out of snapshot’s generation process) to identify the objects that are involved in a Quality Rule computation.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅
8.2.x	✅

Query for CSS

Get the DETAIL and TOTAL procedure

Follow SQL Queries - CAST Knowledge Base - Queries on metrics and diagnostics - How to get DETAIL and TOTAL procedures

SQL Queries - CAST Knowledge Base - Queries on metrics and diagnostics - How to run DETAIL and TOTAL procedures manually with working tables

Mon, 01 Jan 0001 00:00:00 +0000

Purpose of Query

This page will explain how to customize the detail procedure of the Quality rule Persistent class methods equals and hashCode must access its fields through getter methods diag to execute it manually.

This is a particular J2EE diag. The DETAIL procedure uses work tables that are populated by other stored procedure and are truncated at the end of the Snapshot computation. If we run the detail query unchanged, no rows will be raised.

SQL Queries - CAST Knowledge Base - Queries on metrics and diagnostics - How to populate the working tables present in DETAIL and TOTAL procedure

Mon, 01 Jan 0001 00:00:00 +0000

Purpose of Query

This page explains how to manually populate the working tables present in the total and detail procedure. Working tables begin with WK . They are populated by other stored procedures and are truncated at the end of the Snapshot computation. If we run the detail query unchanged, no rows will be raised.

Applicable in CAST Version

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅

Applicable RDBMS

SQL Queries - CAST Knowledge Base - Queries on metrics and diagnostics - How to determine the remote calls for an object

Mon, 01 Jan 0001 00:00:00 +0000

Purpose of Query

This page provides a query to run on the CAST knowledge base which provides the remote calls for an object.

An example is for violated object for the metric **’**Avoid direct or indirect remote calls inside a loop’

Applicable CAST Version

Release	Yes/No
8.3.x	✅
8.2.x	✅

Applicable RDBMS

RDBMS	Yes/No
Oracle Server	❓
Microsoft SQL Server	❓
CSS3	✅
CSS2	✅

Query for CSS

Run the following query on the Knowledge Base

SQL Queries - CAST Knowledge Base - Queries on metrics and diagnostics - How to get LOC by module

Mon, 01 Jan 0001 00:00:00 +0000

Purpose of Query

This query lists LOC by module

Applicable CAST Version

Release	Yes/No
8.3.x	✅

Applicable RDBMS

RDBMS	Yes/No
CSS	✅

Query for CSS

For 8.3.36 and below:

SELECT k.keynam AS MODULE,
 SUM(oi.infval) AS LOC
FROM Keys k
JOIN SETROOT sr ON sr.IDSET = k.IdKey
JOIN CTT_OBJECT_APPLICATIONS coa ON coa.APPLICATION_ID = sr.IDROOT
JOIN objinf oi ON coa.object_id = oi.idobj
JOIN keys k2 ON k2.idkey = coa.object_id
WHERE k.ObjTyp = 20000
 AND coa.properties = 0
 AND inftyp = 1
 AND infsubtyp = 0
 AND k.KeyNam not like '%union content%'
 AND k.KeyNam NOT LIKE '% IFPUG objects'
 AND k2.objtyp IN
 (SELECT DISTINCT t.idtyp
 FROM typ t,
 typcat tc
 WHERE t.idtyp = tc.idtyp
 AND tc.idcatparent IN
 (SELECT cat.idcat
 FROM cat
 WHERE catnam LIKE '%APM Sources%'))
GROUP BY k.keynam

For 8.3.37 and above:

SELECT k.keynam AS MODULE,
 SUM(oi.infval) AS LOC
FROM Keys k
JOIN SETROOT sr ON sr.IDSET = k.IdKey
JOIN CTT_OBJECT_APPLICATIONS coa ON coa.APPLICATION_ID = sr.IDROOT
JOIN objinf oi ON coa.object_id = oi.idobj
JOIN keys k2 ON k2.idkey = coa.object_id
WHERE k.ObjTyp = 20000
 AND coa.properties & 255 = 0
 AND inftyp = 1
 AND infsubtyp = 0
 AND k.KeyNam not like '%union content%'
 AND k.KeyNam NOT LIKE '% IFPUG objects'
 AND k2.objtyp IN
 (SELECT DISTINCT t.idtyp
 FROM typ t,
 typcat tc
 WHERE t.idtyp = tc.idtyp
 AND tc.idcatparent IN
 (SELECT cat.idcat
 FROM cat
 WHERE catnam LIKE '%APM Sources%'))
GROUP BY k.keynam

Query result example