Setting MTQ value using a TI Process

[M1ndbender]

Hi there,
Does anyone know if it is possible to set the MTQ parameter to 1 at the beginning of a process and then to 45 at the end.

We running normally at 45 bit there are a few processes who cause issues if other processes run at the same time.

Just trying to avoid having to set MTQ manually each time they run.

Thanks

[burnstripe]

Hi, the parameter MTQ can only be controlled with tm1s.cfg or REST API, it is a dynamic parameter so technically you could update the parameter before execution but I'd be more curious why you'd need/want to set it to 1?

Assuming you have MTQQuery set to T, you could use DisableMTQViewConstruct in your TI process to disable the use of MTQ when calculating a view to be used as the datasource in the process and use EnableMTQViewConstruct to turn it back on

If your problem is that when the process runs, other processes are forced to queue due to no threads being available, then you may also consider lowering the MTQ down from 45 so that there is spare threads available for other processes to run.

There can be other reasons for processes to have issues if other processes are running at the same time if they share the same objects, it's not clear to me if thread capacity is your only issue here.

[M1ndbender]

Thank you for the reply. It is definately not the number of threads but the interactions between processes that share some dimensions.

I am looking into the Synchronization of processes functionality now.

[qml]

MTQ is a dynamic parameter, so in theory you can change it via the REST API and use it in the same server session, but the change isn't immediate - it takes up to a minute for the change to be reflected by the server. While I'm a fan of creative solutions, I doubt this is the best one for your problem - whatever the problem might be.

Can you tell us a bit more about the processes that "cause issues"? What are the issues?

[M1ndbender]

They are processes that touch all dimensions. When we run then as part of our normal loads they do not cause issues because we can run then serial but if someone runs them adhoc or now they need to run them manually more often we are seeing the instance hang and have to be restarted which causes data loss and is a pain. I am trying to find a way to allow the users to run these processes when they require without causing system issues, or having to try and remember to let me know so I can manually turn off MTQ until they are done