Product Documentation
Abstract
This technote explains the behavior of temporary views and subsets in TM1 Server.
Content
TM1 10.2.2 Fix Pack 5 introduced temporary views and subsets (commonly referenced as temporary objects) for use in TurboIntergrator (TI) processes. Temporary objects are useful to avoid metadata lock contention in the }Views_ and }Subsets_ dimensions that were introduced in Planning Analytics 2.0.
Temporary objects can be explicitly deleted using the ViewDestroy and SubsetDestroy TI functions. If a temporary object is not explicitly deleted it will be automatically deleted at the end of the current transaction. A transaction may be a single TI process or a series of TI processes in which the ExecuteProcess TI function is used to call a TI process from within a TI process.
When an object is created, it must have a name. After creating a temporary view or subset, it is not possible to create another temporary object with the same name within the same TI process or series of TI processes (on the same thread).
The following TI functions can be used to create temporary objects:
If multiple temporary objects are required in the same TI transaction, each temporary object must be provided with a unique name. The following techniques can be used to generate a unique name:
- Append the parameter or variable value as a string to the temporary object name where the value is unique to the instance of the TI process. This is useful when many TI processes need to be started using ExecuteProcess, and each TI process has a unique parameter value.
- Append a timestamp generated with the NOW TI function. The NOW TI function returns a numeric value that can be converted to a string using the TIMST TI function.
For version 2.0.4 and earlier, temporary objects were visible and usable only by the TI process that created it and any of its child TI processes. Temporary objects were not visible to the ancestor and any sibling TI processes. You could create same-named objects in sibling child TI processes with the same parent TI process.
For version 2.0.5 and later, these temporary objects are visible to the ancestor and sibling TI processes. If a parent TI process P1 invokes two child TI processes, CP1 and CP2, and the child TI process CP1 creates a temporary view TV1, this temporary view exists for the duration of the parent TI process P1. You cannot create a temporary view with the same name V1 in the sibling TI process CP2 since the view is visible and usable in P1 and its children CP1 and CP2.
This change in behavior between 2.0.4 and 2.0.5 was an intentional enhancement.
Document Location
Worldwide
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD29G","label":"IBM Planning Analytics"},"Component":"TM1 Server","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
02 July 2020
UID
ibm11099989