Hello everyone
Thanks for your time.
Behind the scenes is the Datastage repository a file structure or is it DB2 tables? I'm not talking about the client side. I need to know the behind the scenes technical stuff.
Datastage repository behind the scenes.
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You may "need to know" (why?), but Ascential elects not to publish this information and reserves the right to change it at any time.
In quick summary it's not file-based, it's database-based. It's definitely NOT DB2; Ascential explicitly markets itself as "database agnostic". To that end, currently, it uses a proprietary database called DataStage Engine that is based on IBM's UniVerse RDBMS.
Originally, and through to version 5.2, DataStage used UniVerse as its actual engine.
You can research this history on this forum. Search for VMARK, Ardent and UniVerse.
Currently there are two main sets of tables. Tables with names beginning "DS_" contain design-time information, while tables with names beginning "RT_" contain run-time information.
Expect major changes to the Repository structure in the next release, and further changes beyond that.
In quick summary it's not file-based, it's database-based. It's definitely NOT DB2; Ascential explicitly markets itself as "database agnostic". To that end, currently, it uses a proprietary database called DataStage Engine that is based on IBM's UniVerse RDBMS.
Originally, and through to version 5.2, DataStage used UniVerse as its actual engine.
You can research this history on this forum. Search for VMARK, Ardent and UniVerse.
Currently there are two main sets of tables. Tables with names beginning "DS_" contain design-time information, while tables with names beginning "RT_" contain run-time information.
Expect major changes to the Repository structure in the next release, and further changes beyond that.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.