TM1 Forum

Hi All,

What is the use and significance of using DebugUtility in TI process?
Where can I find more information on it?

Regards,
Deepak Jain

The only TurboIntegrator editor with any debugging utility is Vizier. And even then this is not debugging as you would normally think of it as what Vizier does is to surreptitiously insert ASCIIOutput into the TI process in the background for selected variables and return the result in a grid on execution of the process. It is not step-through debugging with variables watch window. But as far as TI goes it is as good as it gets.

However this now changes from 10.2.2 if using java functions, either rather than TI or called from TI. If you turn on debugging in java and insert a breakpoint then you can in fact step through the java code.

DebugUtility is an unsupported TI function that TM1 developers use to add new functionality, usually diagnostic in nature, while keeping intent obfuscated through the use of nondescript command codes/lack of documentation. The only way to get more info would be to ask a developer/support contact. They're usually pretty open about these sorts of things (hint: they like beer.)

DebugUtility(125,0,0,'','','');

The above code is written in TI process.
We are running TI Process to clear the cache information. So that we can get an appropriate time taken by cube to open in either Cube Viewer or Executive Viewer.

If anybody have some more info, please share.

Other commands:

• DebugUtilityEx ('SetMTQ','24') – change MTQ parameter tm1s.cfg

• DebugUtility( 114, 0, 0, vCubeName, pDestinationFolder, '') - Obfuscate data (found here: http://feederwhisperer.blogspot.ru/2015 ... -your.html)

Hi, does this really Obfuscate data?

Because I just tested it and it didn't seem to do anything like that, it just seemed to take a copy of the cub file

Maren