Yes I have tried it, but unfortunately, I don’t have the not working codes anymore. Actually, it is not easy to replicate it because you would require that the different processes access the library at the same time. In my case, I have a macro which starts a number of processes and executes some IML code with lots of modules (at least 20). The error was something like “Cannot load library, there is a lock on mylib.mystore from task X” As far as I understand it, IML loads the modules when they occur the first time. Since they are all in the same library, I do not exactly know when each task is accessing the library. Furthermore when one task has finished, I start an new one, so it is also not known when the new process has to access the module library. But I think, it should work if I load all modules (LOAD module=_all_) only once after starting a new process and then I wait bit before I start any other process. Maybe, I’ll implement this when I update myparallel-processing-macro (as I have written, the current version just defines again all modules from the “original” code of the modules in a local storage). I guess, I still could get in trouble if there are a lot other (non-IML) steps before IML needs the modules then I am not sure when I need the access. In this case, I still would need to make a copy of the original lib in the work-library, for example. Maybe something like a read-only storage which is accessible by multiple processes at the same time could be an improvement for IMl (in case it doesn’t already exist 😉 ) Thanks for your help 🙂
... View more