Page 1 of 1

TM1 Turbo Debugger

Posted: Thu Aug 10, 2017 8:26 pm
by jjramirez

After install the Fix pack 7 (FP7) i also installed the Tm1 Turbo Debugger Tool as said it in ... -debugger/

Now I can add break points when executing TI Processes and it works ok, but the problem is I can not visualize all the code lines in the prolog, Data or Epilog. it is always incomplete. For example:
Debbuger.PNG (196.7 KiB) Viewed 908 times
It only shows me until line 238 but the prolog has 22 lines more. (it happens with every process with different number of lines)
maybe something is missing in configuration file? or did i make a mistake in installation process?

I am pretty new using TI Process and TurboDebugger so many thanks in advanced.

Re: TM1 Turbo Debugger

Posted: Fri Aug 11, 2017 12:02 am
by Wim Gielis
I face the same problem but did not spend time on it because that debugger is still new. It would be good if we could reach a solution, maybe with IBM involvement.

Re: TM1 Turbo Debugger

Posted: Fri Aug 11, 2017 1:18 pm
by jjramirez
Thank you so much for your answer Mr. Gielis.

Re: TM1 Turbo Debugger

Posted: Fri Oct 20, 2017 1:43 am
by PeteB

The debugger is fantastic, however I am have the same problem with the missing lines of code. It does not consistently occur, ie it does not depend on the number of lines as it impacts both small and large TIs. The same TI will sometimes show all lines and sometimes not.

I have raised this as issue with IBM unfortunately here is the answer.
ECuRep Mail Gateway - mail from support
File: mail.html 8459 bytes
File: mail.wri 4856 bytes
---------------------------- EMAIL TEXT START --------------------------
Hi Peter,

Just a quick note to let you know that IBM Cognos Support Management
have confirmed my suspicions; As this code is community sourced, it is
not supported by IBM, and any requestes for support for the
TurboIntegrator Debugger utility will therefore need to be directed to
the person(s) who developed it - You may be able to reach this person
via the Comments secttion on the DeveloperWorks Recipes page at: https:/
/ < ... rator-debu
gger/> .

Kind regards,
I have raised the question on the IBM developer Website.

Re: TM1 Turbo Debugger

Posted: Fri Oct 20, 2017 3:32 am
by Wim Gielis
PeteB wrote:
Fri Oct 20, 2017 1:43 am
I have raised the question on the IBM developer Website.
Thank you for the update Peter

Re: TM1 Turbo Debugger

Posted: Fri Oct 20, 2017 11:08 am
by Steve Rowe
Hmmm, I suspect that the support person is speaking out of turn here.

The TI Debugger was developed by an individual in IBM, not by an external person with a desire to improve our lot.

It is also mentioned as a feature in many IBM presentations that I have attended.

It's pretty rich to then claim that as the tool was developed in some kind of off-line skunk works manner that they are not going to support it. Seems there is a bit of a grey area here...

Re: TM1 Turbo Debugger

Posted: Tue Oct 31, 2017 2:28 am
by PeteB
Here is the latest update form IBM
Product Offering have said that the TI debugger will become officially part of Planning Analytics Workspace and therefore officially supported, but they can't give me a timeframe of when that will happen.

With that said, Product Offering would like to look into this issue, could you please send me the TI process in question, just the .pro file will be fine. However, they aren't making any promises on resolving the issue.
I will provide an update when I hear back.

I am not 100% sure but I believe the issue is possibly related to the length of the TI line of code. I have attached a very simple TI where the 10th line (very long line of code) is not showing and then the 3000 (short) lines TI are showing OK.

Re: TM1 Turbo Debugger

Posted: Sun Nov 05, 2017 9:48 pm
by PeteB
The latest update from IBM

Good news, Offering Management are going to fix the issue. It's a Word wrap issue.

Re: TM1 Turbo Debugger

Posted: Thu Dec 07, 2017 6:30 am
by PeteB
Very Good News. IBM have delivered the new version of TurboDebugger to address the wrapping error. From my testing this error has been fixed.