IBM Support

TM1 10.2.2 Fix Pack 4 - New Tm1s.cfg parameter, MDXSelectCalculatedMemberInputs

Product Documentation


IBM Cognos TM1 10.2.2 Fix Pack 4 introduces a new parameter, MDXSelectCalculatedMemberInputs, for the TM1 server configuration file.


MDXSelectCalculatedMemberInputs changes the way in which calculated members in MDX expressions are handled when zero suppression is enabled.

Parameter type: optional, dynamic

MDXSelectCalculatedMemberInputs addresses an issue with calculated members in an MDX expression when zero suppression is enabled. When zero suppression is enabled on a query axis, calculated members might be dropped from the query or might cause zero suppression to be turned off.

The issue arises because zero suppression is based on the actual data in a cube. Calculated members do not have an actual member in the cube -- calculated members are derived from other members.

For example, suppose a cube has a calculated member, C, that is a sum of the members A and B.

The members A and B are actual members in the cube, while C is derived. When you run a query with A, B, and C in the columns, {A,B,C}, you see A, B, and C in the columns and you see that C is the sum of A and B. When you turn on zero suppression, only non-null rows of data are displayed for A, B, and C, as expected.

Now, suppose you restrict the columns to C only, {C}. When zero suppression is turned off, C is displayed in the columns. But if you turn on zero suppression, C might be dropped from the columns because C does not reference any actual member in the cube.

MDXSelectCalculatedMemberInputs addresses this issue. When MDXSelectCalculatedMemberInputs is enabled, TM1 assumes that if the inputs to the calculated member have data (the A and B in the example), then the calculated member (C) also has data and must be retained when zero suppression is turned on.

The processing occurs as follows:

1. Do a fast check of the calculated member to detect what specific actual members it references.

2. Consider these actual members as inputs to the calculated member.

3. Make sure that these inputs are included in the Stargate data underlying the view.

With the inputs included in the Stargate data, the suppression algorithm sees Stargate data at A and B, notices that A and B are inputs to C, and keeps C when zero suppression is enabled.

MDXSelectCalculatedMemberInputs works well for simple formulas, like C=A+B. If you use complex formulas, such as data-dependent formulas that contain conditional expression like IIF, enabling MDXSelectCalculatedMemberInputs might not resolve issues with zero suppression.

Note: Enabling MDXSelectCalculatedMemberInputs can increase the size of Stargate views. This can provide faster access times for cube data but can consume more system resources.

To enable MDXSelectCalculatedMemberInputs, add the following to the tm1s.cfg file.


Default value: F

[{"Product":{"code":"SS9RXT","label":"Cognos TM1"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"TM1","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF010","label":"HP-UX"}],"Version":"10.2.2","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
17 June 2018