TM1 Forum

Hi There

Scenario is as follows for using RunProcess with master wrapper:
RunProcess => pass parameters such that months 1 to 6 are deleted in destination cube, and months 1 to 6 are copied from source cube
RunProcess => pass parameters such that months 6 to 12 are deleted in same destination cube, and months 6 to 12 are copied from same source cube

This immediately goes into serial mode, with a status of wait on the second line.

Any ideas?

Many thx!
Chris

TM1 is pretty good and reliable at parallelizing pure data transactions, and even metadata these days as long as there is absolutely no overlap in objects (and dependencies) between threads. If your threads are locking then the most likely explanation is that there's a conflict in the subset names you are using for the zero out and/or data copy and both threads are trying to update the same metadata object which will of course cause a lock.

If each sub-process called by RunProcess does it's own view and subset creation make sure that:
- all subsets and views used are temp objects
- all subsets and views ARE UNIQUELY NAMED

If you went old skool and are doing the subset and view creation in the wrapper before calling the sub-processes (not really recommended), then you need to make sure that the sub-processes perform no manipulation of these objects at all.

chewza wrote: ↑Thu Jun 27, 2024 3:56 pm RunProcess => pass parameters such that months 1 to 6 are deleted in destination cube, and months 1 to 6 are copied from source cube
RunProcess => pass parameters such that months 6 to 12 are deleted in same destination cube, and months 6 to 12 are copied from same source cube

Should the second part read months 7 to 12 and not 6 to 12? If not, would deleting identical periods in both process calls cause this?

Maren

Many thanks all - got it working now!
Example was just hypothetical - did some additional work to ensure views/subsets unique