I'm sorry, but that wouldn't work in this case. The whole idea is to give ONE SAS session access to ANOTHER concurrent session's work library, so the libname must be hardcoded,
The problem in this post is not a DI Studio priobem. DI Studio is a code generator that sends code to execution, and each open window in DI Studio will have it's own workspace server session. So it is just the same as having two Display Manager sessions open at the same time and finding a way to get access from one session to the other session's work library.
... View more