TM1 Forum

Hi,

TM1 development is moving more and more to PAW, well in theory anyway!

One of the key tools when developing or sorting out issues is to asciioutput the results. As far as I know you can only output to a drive that the TM1 server has access to.

Given that PAW is a web based tool, and more than likely to be accessed from a users local machine, I think it would be useful to ascii to the local machine, rather than the TM1 server.

Anyone have any thoughts on this, or are their existing ways to make it possible?

Maren

Yup...

#Get the logging directory (Delivered with a trailing slash)
sLogDirPath = GetProcessErrorFileDirectory;

#write the file
asciioutput(sLogDirPath | 'tm1myerror.log', etc....)

Any file that starts tm1 and ends .log will show up in the download logs dialogue on the PAW admin page of the TM1 DB.

Simple when you know how, but some experimentation was required!

I use two different approaches:
1 - Drill to the text file
2 - Email the resulting file based on the logged in user. ExecuteCommand in epilog to run the necessary ps script

Where files are big, FTP or RDP to the rich client are options for admins with relevant access.

Hi,

thanks for the feedback, very interesting solutions that I will test at some point!

Still like logging onto the server and just opening from the directory, but good to see the available options and they do have other uses.

Maren

If it’s an IBM cloud environment, the SFTP access with e.g. FileZilla is very easy.

Similar solutions can probably be set up for other systems.
Why not just READ access to the TM1 logging directory through a mapped network drive ?

For smaller logs, I would just use LogOutput()
Then you can search the logs using TM1 REST API (or check TeamOne in the commercial subforum: https://www.tm1forum.com/viewforum.php?f=20)

Another option is to write logs to a custom cube

I also like the drill to file solution proposed by George and mapped network drive proposed by Wim