Return codes and error messages

Post Reply
Moder
Posts: 2
Joined: Fri Apr 20, 2018 8:18 am
OLAP Product: Planning Analytics
Version: 2.0.4
Excel Version: 2010

Return codes and error messages

Post by Moder » Fri Apr 20, 2018 9:11 am

I use TM1 IBM Planning Analytics 2.0.4

Is the Return codes and error messages from this link correct ?

https://www.ibm.com/support/knowledgece ... sages.html

I try to test it by made error in processes.

For Example

1. I use ProcessQuit() command to force process to quit.
I suppose to get return code as 9 according to the above link but I got 8 instead.

2. I use ProcessBreak() command to make process finished by break
I got code 7 by doing this while the above link tell me code 7 is something else that's not relevant.

So the question is

Where I can get the correct error message that match the error code ?

I appreciate any help and thanks in advance.

lotsaram
MVP
Posts: 3094
Joined: Fri Mar 13, 2009 11:14 am
OLAP Product: TM1, CX
Version: TM1 10.2.2 PA 2.0x
Excel Version: 2010 2013 365
Location: Switzerland

Re: Return codes and error messages

Post by lotsaram » Fri Apr 20, 2018 2:57 pm

The error codes which that documentation is referring to are the error codes for tm1runti.exe which should not be confused with the exit code for the TurboIntegrator process itself ("process return codes").

If you want to validate the internal integer value of the process return codes this is quite easy to do by just wrapping each return code in NumberToString and outputting it.
e.g.
2018-04-20_16-45-00.png
2018-04-20_16-45-00.png (29.92 KiB) Viewed 299 times
Then just look in the tm1server.log file
2018-04-20_16-49-47.png
2018-04-20_16-49-47.png (7.67 KiB) Viewed 299 times
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.

User avatar
PavoGa
Community Contributor
Posts: 203
Joined: Thu Apr 18, 2013 6:59 pm
OLAP Product: TM1
Version: 10.2.2 FP7, PA2.0
Excel Version: 2013
Location: Cleveland, Tennessee

Re: Return codes and error messages

Post by PavoGa » Mon Apr 23, 2018 11:38 am

Perhaps a useful tip, use a counter dimension (1...n) and add attributes for it to describe the error codes so they can be written to control cubes, output in messages, emails, etc.
Ty
Cleveland, TN

Post Reply