In the Cognos 8.4 distribution some diagnostic tools are default installed in the directory \bin\utilities\diagnostictools\win32. One of them is "C8FrameMgr". Most of these tools were earlier available on the support site of Cognos.

Just execute the file "execute_ C8FrameMgr.bat" or java -jar C8FrameMgr.jar from the DOS prompt. Or execute the file "execute_IBMCognos8.bat" from windows explorer window.

Summary of Information Collected

· Content Store Information
· Ambiguous Join Info
· List of Facts
· Multiple Valid Join Info
· Recursive Join Info

Sample output of a GO SALES framework model

=============================================================================
*** IBM Cognos 8 Framework Manager Result file generated 19:51:44
=============================================================================



=============================================================================
*** Content Store Information
=============================================================================

Database Type: Microsoft SQL Server

Database Version:
9.0.3077

Driver Type: JNetDirect JSQLConnect - JDBC 2.0

Driver Version: 5.55


=============================================================================
*** Ambiguous Join Information
=============================================================================


Model File: D:\Data\fm\Security row based\model.xml

** VIEW THE LOG FILE FOR A LIST OF ALL RELATIONSHIPS **

Potential Ambiguous Join #1
Namespace: Product query subjects
Query Subject: PRODUCT
Type: Fact (previously defined as a Dimension)
Relationship: PRODUCT_COLOR_LOOKUP <--> PRODUCT
Expression:
[gosales].[PRODUCT_COLOR_LOOKUP].[PRODUCT_COLOR_CODE] =
[gosales].[PRODUCT].[PRODUCT_COLOR_CODE]


Potential Ambiguous Join #2
Namespace: Product query subjects
Query Subject: PRODUCT
Type: Fact (previously defined as a Dimension)
Relationship: PRODUCT_SIZE_LOOKUP <--> PRODUCT
Expression:
[gosales].[PRODUCT_SIZE_LOOKUP].[PRODUCT_SIZE_CODE] =
[gosales].[PRODUCT].[PRODUCT_SIZE_CODE]


Potential Ambiguous Join #3
Namespace: Product query subjects
Query Subject: PRODUCT
Type: Fact (previously defined as a Dimension)
Relationship: PRODUCT_STYLE <--> PRODUCT
Expression:
[gosales].[PRODUCT_BRAND].[PRODUCT_BRAND_CODE] =
[gosales].[PRODUCT].[PRODUCT_BRAND_CODE]


Potential Ambiguous Join #4
Namespace: Product query subjects
Query Subject: PRODUCT
Type: Fact (previously defined as a Dimension)
Relationship: PRODUCT_TYPE <--> PRODUCT
Expression:
[gosales].[PRODUCT_TYPE].[PRODUCT_TYPE_CODE] =
[gosales].[PRODUCT].[PRODUCT_TYPE_CODE]


Potential Ambiguous Join #5
Namespace: Product query subjects
Query Subject: PRODUCT_TYPE
Type: Fact (previously defined as a Dimension)
Relationship: PRODUCT_LINE <--> PRODUCT_TYPE
Expression:
[gosales].[PRODUCT_LINE].[PRODUCT_LINE_CODE] =
[gosales].[PRODUCT_TYPE].[PRODUCT_LINE_CODE]


Potential Ambiguous Join #6
Namespace: gosales
Query Subject: TIME_DIMENSION
Type: Dimension (previously defined as a Fact)
Relationship: INVENTORY_LEVELS <--> TIME_DIMENSION
Expression:
[gosales].[INVENTORY_LEVELS].[INVENTORY_YEAR] =
[gosales].[TIME_DIMENSION].[CURRENT_YEAR] AND
[gosales].[INVENTORY_LEVELS].[INVENTORY_MONTH] =
[gosales].[TIME_DIMENSION].[CURRENT_MONTH]


Potential Ambiguous Join #7
Namespace: gosales
Query Subject: TIME_DIMENSION
Type: Dimension (previously defined as a Fact)
Relationship: PRODUCT_FORECAST <--> TIME_DIMENSION
Expression:
[gosales].[PRODUCT_FORECAST].[SALES_YEAR] =
[gosales].[TIME_DIMENSION].[CURRENT_YEAR] AND
[gosales].[PRODUCT_FORECAST].[SALES_MONTH] =
[gosales].[TIME_DIMENSION].[CURRENT_MONTH]


Potential Ambiguous Join #8
Namespace: gosales
Query Subject: COUNTRY
Type: Dimension (previously defined as a Fact)
Relationship: SALES_TARGET <--> COUNTRY
Expression:
[gosales].[SALES_TARGET].[COUNTRY_CODE_RETAILER] =
[gosales].[COUNTRY].[COUNTRY_CODE]


Potential Ambiguous Join #9
Namespace: gosales
Query Subject: TIME_DIMENSION
Type: Dimension (previously defined as a Fact)
Relationship: Orders <--> TIME_DIMENSION
Expression:
[gosales].[Sales].[Day key (order date)] =
[gosales].[TIME_DIMENSION].[DAY_KEY]


Potential Ambiguous Join #10
Namespace: gosales
Query Subject: TIME_DIMENSION
Type: Dimension (previously defined as a Fact)
Relationship: Returned item <--> TIME_DIMENSION
Expression:
[gosales].[Returned items].[Day key (return date)] =
[gosales].[TIME_DIMENSION].[DAY_KEY]


Potential Ambiguous Join #11
Namespace: gosales
Query Subject: Sales
Type: Fact (previously defined as a Dimension)
Relationship: Sales <--> PRODUCT
Expression:
[gosales].[Sales].[Product number] =
[gosales].[PRODUCT].[PRODUCT_NUMBER]


Potential Ambiguous Join #12
Namespace: gosales
Query Subject: Sales
Type: Fact (previously defined as a Dimension)
Relationship: Sales <--> BRANCH
Expression:
[gosales].[Sales].[Sales branch code] =
[gosales].[BRANCH].[BRANCH_CODE]


Potential Ambiguous Join #13
Namespace: gosales
Query Subject: Sales
Type: Fact (previously defined as a Dimension)
Relationship: Sales <--> ORDER_METHOD
Expression:
[gosales].[Sales].[Order method code] =
[gosales].[ORDER_METHOD].[ORDER_METHOD_CODE]


Potential Ambiguous Join #14
Namespace: gosales
Query Subject: TIME_DIMENSION
Type: Dimension (previously defined as a Fact)
Relationship: Sales target <--> TIME_DIMENSION
Expression:
[gosales].[Sales target].[Month key] =
[gosales].[TIME_DIMENSION].[MONTH_KEY]


Potential Ambiguous Join #15
Namespace: gosales
Query Subject: Product
Type: Fact (previously defined as a Dimension)
Relationship: PRODUCT_COLOR_LOOKUP <--> Product
Expression:
[gosales].[PRODUCT_COLOR_LOOKUP].[PRODUCT_COLOR_CODE] =
[gosales].[Product].[Product color code]


Potential Ambiguous Join #16
Namespace: gosales
Query Subject: Product
Type: Fact (previously defined as a Dimension)
Relationship: PRODUCT_SIZE_LOOKUP <--> Product
Expression:
[gosales].[PRODUCT_SIZE_LOOKUP].[PRODUCT_SIZE_CODE] =
[gosales].[Product].[Product size code]


Potential Ambiguous Join #17
Namespace: gosales
Query Subject: Product
Type: Fact (previously defined as a Dimension)
Relationship: PRODUCT_BRAND <--> Product
Expression:
[gosales].[PRODUCT_BRAND].[PRODUCT_BRAND_CODE] =
[gosales].[Product].[Product brand code]


Potential Ambiguous Join #18
Namespace: goretailers
Query Subject: RETAILER
Type: Fact (previously defined as a Dimension)
Relationship: RETAILER_TYPE <--> RETAILER
Expression:
[goretailers].[RETAILER_TYPE].[RETAILER_TYPE_CODE] =
[goretailers].[RETAILER].[RETAILER_TYPE_CODE]


Potential Ambiguous Join #19
Namespace: goretailers
Query Subject: RETAILER_SITE
Type: Fact (previously defined as a Dimension)
Relationship: RETAILER_SITE <--> ACTIVITY_STATUS_LOOKUP
Expression:
[goretailers].[RETAILER_SITE].[RTL_ACTIVITY_STATUS_CODE] =
[goretailers].[ACTIVITY_STATUS_LOOKUP].[ACTIVITY_STATUS_CODE]


Potential Ambiguous Join #20
Namespace: goretailers
Query Subject: RETAILER_SITE
Type: Fact (previously defined as a Dimension)
Relationship: RETAILER_SITE <--> RETAILER
Expression:
[goretailers].[RETAILER_SITE].[RETAILER_CODE] =
[goretailers].[RETAILER].[RETAILER_CODE]


Potential Ambiguous Join #21
Namespace: goretailers
Query Subject: Retailer
Type: Fact (previously defined as a Dimension)
Relationship: RETAILER_TYPE <--> Retailer
Expression:
[goretailers].[RETAILER_TYPE].[RETAILER_TYPE_CODE] =
[goretailers].[Retailer].[Retailer type code]


Potential Ambiguous Join #22
Namespace: gohr
Query Subject: EMPLOYEE
Type: Fact (previously defined as a Dimension)
Relationship: GENDER_LOOKUP <--> EMPLOYEE
Expression:
[gohr].[GENDER_LOOKUP].[GENDER_CODE] =
[gohr].[EMPLOYEE].[GENDER_CODE]


Potential Ambiguous Join #23
Namespace: Database view
Query Subject: RETAILER_SITE
Type: Dimension (previously defined as a Fact)
Relationship: Returned items <--> RETAILER_SITE
Expression:
[gosales].[Returned items].[Retailer site code] =
[goretailers].[RETAILER_SITE].[RETAILER_SITE_CODE]


Potential Ambiguous Join #24
Namespace: Database view
Query Subject: RETAILER_SITE
Type: Dimension (previously defined as a Fact)
Relationship: Sales <--> RETAILER_SITE
Expression:
[gosales].[Sales].[Retailer site code] =
[goretailers].[RETAILER_SITE].[RETAILER_SITE_CODE]


Potential Ambiguous Join #25
Namespace: Database view
Query Subject: Sales target
Type: Dimension (previously defined as a Fact)
Relationship: Sales target <--> RETAILER
Expression:
[gosales].[Sales target].[Retailer code] =
[goretailers].[RETAILER].[RETAILER_CODE]


Potential Ambiguous Join #26
Namespace: Database view
Query Subject: Sales target
Type: Dimension (previously defined as a Fact)
Relationship: Sales target <--> Retailer
Expression:
[gosales].[Sales target].[Retailer code] =
[goretailers].[Retailer].[Retailer code]




=============================================================================
*** List of Query Subjects Which Are Facts (1..n) Only
=============================================================================


Model File: D:\Data\fm\Security row based\model.xml

Query subjects that only have the many (n) cardinality:

CONVERSION_RATE
CURRENCY_LOOKUP
EMPLOYEE_HISTORY
EURO_CONVERSION
INVENTORY_LEVELS
ORDER_DETAILS
Orders
PRODUCT_FORECAST
RETAILER_SITE_MB
Returned item
Returned items
RETURNED_ITEM
SALES_TARGET


=============================================================================
*** Multiple Valid Join Information
=============================================================================


Model File: D:\Data\fm\Security row based\model.xml

** VIEW THE LOG FILE FOR A LIST OF ALL RELATIONSHIPS **

Potential Multiple Valid Join #1
Namespace: gosales
Relationship: INVENTORY_LEVELS <--> TIME_DIMENSION
Expression:
[gosales].[INVENTORY_LEVELS].[INVENTORY_YEAR] =
[gosales].[TIME_DIMENSION].[CURRENT_YEAR] AND
[gosales].[INVENTORY_LEVELS].[INVENTORY_MONTH] =
[gosales].[TIME_DIMENSION].[CURRENT_MONTH]

Potential Multiple Valid Join #2
Namespace: gosales
Relationship: PRODUCT_FORECAST <--> TIME_DIMENSION
Expression:
[gosales].[PRODUCT_FORECAST].[SALES_YEAR] =
[gosales].[TIME_DIMENSION].[CURRENT_YEAR] AND
[gosales].[PRODUCT_FORECAST].[SALES_MONTH] =
[gosales].[TIME_DIMENSION].[CURRENT_MONTH]

Potential Multiple Valid Join #3
Namespace: Database view
Relationship: Sales Staff <--> Sales target
Expression:
[gohr].[Sales Staff].[Sales staff code] =
[gosales].[Sales target].[Sales staff code] and (
[gosales].[Sales target].[Day key (sales target)] between
[gohr].[Sales Staff].[Day key (record start date)] and
[gohr].[Sales Staff].[Day key (period record end date)] )

Potential Multiple Valid Join #4
Namespace: Database view
Relationship: Sales Staff <--> Orders
Expression:
[gohr].[Sales Staff].[Sales staff code] =
[gosales].[Sales].[Sales staff code] and (
[gosales].[Sales].[Day key (order date)] between
[gohr].[Sales Staff].[Day key (record start date)] and
[gohr].[Sales Staff].[Day key (period record end date)] )

Potential Multiple Valid Join #5
Namespace: Database view
Relationship: Returned items <--> Sales Staff
Expression:
[gosales].[Returned items].[Sales staff code] =
[gohr].[Sales Staff].[Sales staff code] and (
[gosales].[Returned items].[Day key (return date)] between
[gohr].[Sales Staff].[Day key (record start date)] and
[gohr].[Sales Staff].[Day key (period record end date)] )

Potential Multiple Valid Join #6
Namespace: Database view
Relationship: Sales target <--> Retailer site
Expression:
[gosales].[Sales target].[Country code retailer] =
[goretailers].[Retailer site].[Retailer country code] AND
[gosales].[Sales target].[Retailer code] =
[goretailers].[Retailer site].[Retailer code]



=============================================================================
*** Recursive Join Information
=============================================================================

Model File: D:\Data\fm\Security row based\model.xml

No potential Recursive Joins found

www.cogknowhow.com