Page 1 of 1
Create temp view and open them by returnviewhandle
Posted: Wed Jul 17, 2019 8:01 am
by Drg
At someone it turned out to create a temporary view and subsets and return them in }dril process by returnviewhandlel?
Or is it impossible?
My research resulted in the fact that if you use temporary subsets or views, the view is deleted before the is actually returned. But In fact, the returnviewhandle function is executed before the process ends.
Re: Create temp view and open them by returnviewhandle
Posted: Wed Jul 17, 2019 12:19 pm
by tomok
I'm pretty sure you can't define a view as temporary when using the drill-thru to a view functionality. The whole point of this functionality is so a user can see the data in the cube at the drill-thru. If you define it as temporary to the process then it wouldn't be available for the user to view.
Re: Create temp view and open them by returnviewhandle
Posted: Wed Jul 17, 2019 5:18 pm
by ardi
Unfortunately you cannot open a temporary view with returnviewhandle
This is one of first things I tried when IBM introduced the Temp Views and Subsets.
There are many other limitations of Temporary Views and subset, the biggest limitation i find is that their scope is only within the process where they get created, it would be nice if they extend the scope to the thread that created them (if you have a batch TI and you execute multiple TIs, then it would be nice if the Temporary Objects can be used/referenced in other TIs that are triggered after such objects have been created)
Also you cannot use them as Custom Consolidation, A permanent Subset can be used in a CELLGETN function, but temporary subsets cannot
Re: Create temp view and open them by returnviewhandle
Posted: Thu Jul 18, 2019 6:22 am
by lotsaram
ardi wrote: ↑Wed Jul 17, 2019 5:18 pm
There are many other limitations of Temporary Views and subset, the biggest limitation i find is that their scope is only within the process where they get created, it would be nice if they extend the scope to the thread that created them (if you have a batch TI and you execute multiple TIs, then it would be nice if the Temporary Objects can be used/referenced in other TIs that are triggered after such objects have been created)
Yes this was also my #1 criticism of temp objects, note
was. Possibly you have been living under a rock but to IBM's credit this is something they fixed in 11.3. From that version on the scope of temp objects is now the execution chain not only the originating process. (Yes this wasn't exactly shouted from the rafters. Without this change
bedrock 4 would not be possible.)