provide an option to keep a hash object after the data step finishes
on 04-04-201312:43 AM - last edited on 10-10-201509:57 PM by LainieH
I've encountered already several cases where it would have been very efficient to keep a hash object over the data step boundery so that it can be re-used in a later data step.
What I currently need to do is to either try and pack everything into a single data step or to write the hash table to a data set using the output() method and then re-load the data again in the downstream step where I need it once more.
What I would like to have is kind of a "persist" option as part of the declare() statement and then when I really don't need the hash table anymore I delete it using "delete()".