Creation of a unique namespace associated with the simulation run that is read/write. This will avoid the potential of variable collision that may occur from using global variables or namespaces.
@DonMcCormack can you explain a bit more what the issue is that you are wanting to address? I am not sure I understand.
@SamGardner it's beneficial to be able to store and access system information to be used for specific Actions. Some of this information is stored in the Simulation Context associative array. There is other infomation that is not. For example, there is no way to both associate a distribution with a block and count the number of times it has failed. One solution is to create a global variable to store that information. This is bad practice in that it runs the risk of variable collusion with other globals. Defining a new namespace is a better solution, but carries the overhead of needing to find a unique namespace name. A better solution, I feel, is to make available a namespace associated with the simulation run that is read/write.
Thanks for the additional info @DonMcCormack . I have updated the Jira issue for this. I you want to follow this request, since you have a deeper understanding of the problem, you can go to https://rndjira.sas.com/browse/JMP-13854 and add yourself as a watcher.
