The only thing that you should be aware of is that it'll only provide the Admin host if the Admin Server is running on the same box as the TM1 server. (Which I grant will usually, but not always, be the case.)
I suppose that another option would be to have the TI read the tm1s.cfg file to find the name of the admin host, though I must confess to being perplexed as to why you want this...
I find it quite useful to have start-up process/chore copy the contents of the config file into a simple cube. That way the values are available for use in websheets, rules, Ti's...
I apologize for raising the old topic but no where there is no explanatory description let it be here
Test this script only on Windows server.
p/s/
sctript created dimension
DimName='sys_ServerParameters';
you can append parameters
pParamsList=UPPER(':adminhost:ServerName:');
or append all parameters
pParamsList='';
macsir wrote: ↑Mon Feb 12, 2018 11:40 pm
I just put the admin host manually into a central control cube where all processes can refer to as it really doesn't change.
I also did this until I transferred a model that starts several hours and left home as a result of which users started the processes on the productive model and the child processes were run on the test.
so I came to the conclusion that it's better to make a process that will do this even when I'm not around.