Universe Table

Kniranjani · Post by **Kniranjani** » Tue Sep 28, 2004 2:24 am

Hi
Can any one tell me what are the importtant tables present in UV.How many difault tables created in UV and what is their functionalities

ray.wurlod · Post by **ray.wurlod** » Tue Sep 28, 2004 3:58 pm

Welcome aboard! :D

Do you want to know about UniVerse or DataStage? They're no longer the same thing.

UniVerse (the database) is owned, developed and sold by IBM.

kduke · Post by **kduke** » Tue Sep 28, 2004 5:50 pm

The hash files used by DataStage mostly start with "DS" like DS_JOBS, DS_JOBOBJECTS and DS_METADATA. The files which start with "RT" like RT_CONFIG109 and RT_STATUS1078 are associated with jobs. Each job is assigned a surrogate key called a job number. This job number is concatenated to the RT file names to make them unique to a job. Multiple instance jobs share these RT files and the instance id is in a field or part of the key depending on the RT file. To extract information out of these files is very difficult and you need to be a Universe expert. There is an API to extract most anything you would need included with DataStage and is cover in detail in the manuals and on this web site. Very little is published on the internal structure of any DataStage hash file and is up to the user to figure out. A few of us through experience and hacking know how these files work. Where they store things can and does change from release to release.

ray.wurlod · Post by **ray.wurlod** » Tue Sep 28, 2004 9:29 pm

Yes, but then there's all the other ones, like VOC, VOCLIB, &*& in the project, lots more in the UV account, more again in the SQL Catalog, and so on. And there are some (like UV.LOGINS) that only occur on Windows. That's why I sought to clarify what information is actually sought.

kduke · Post by **kduke** » Tue Sep 28, 2004 10:02 pm

Ray

I am just guessing because the question was too vague.

Kniranjani · Post by **Kniranjani** » Tue Sep 28, 2004 10:38 pm

HI Ray
I want to know about Universe.So could u please put some light in this area.
Thanks
Niranjani

ray.wurlod · Post by **ray.wurlod** » Wed Sep 29, 2004 1:35 am

UniVerse is a trademark of International Business Machines Corporation.
Note that not all "tables" in the following list are full SQL tables with security and integrity constraints. Most are hashed files of some kind.

Code: Select all

UniVerse SQL System Tables
UV_SCHEMA      schemas
UV_TABLES      tables
UV_VIEWS       views
UV_ASSOC       associated multi-valued columns
UV_COLUMNS     columns
UV_USERS       users with CONNECT privilege

UniVerse Admin Account Tables (synonyms exist)
&DEVICE&        logical to physical device mapping
&MAP&           output from MAKE.MAP.FILE command
&PARTFILES&     Distributed files
ADMIN_BP        BASIC programs for admin utilities
APP.PROGS       BASIC progams for applications
BLTRS           data file for BLOCK.TERM command
BP              BASIC programs for UniVerse
DATA.TYPES      data type validation for GCI
DICT.DICT       PI-style dictionary metadata
DICT.PICK       Pick-style dictionary metadata
ERRMSG          data for Pick-style STOP, ABORT
GCI             GCI subroutine definitions
GLOBAL.CATDIR   global BASIC Catalog Space
GTARS           technical requests (empty)
INCLUDE         header files for BASIC programmers
MENU.FILE       UniVerse menu definitions
NEWACC          data for VOC file in new accounts
PTERM.FILE      data for PTERM command
REVISE.DISCUSSIONS    extended help for REVISE
REVISE.PROCESSES      templates for REVISE
STAT.FILE       output from LIST.FILE.STATS command
SYS.HELP        help topics
SYS.MESSAGE     tokenized output strings (error codes, etc.)
UDRSYS          systems participating in database replication
UDRPUB          tables published for replication
UDRSUB          subscriptions to published tables
UV.ACCESS       control of access to certain admin functions
UV.ACCOUNT      UniVerse accounts
UV.FLAVOR       control of account creation
UV.LOGIN        maps Windows loginID styles
UV.TRANS        transaction logging recoverable files
UV_LOGS         transaction logging log activities
VCOMM            obsolete
VCOMM.PORTS      obsolete

Tables in every UniVerse Account
&SAVEDLISTS&    saved Select Lists
VOC             UniVerse vocabulary file
VOCLIB          UniVerse vocabulary extensions

Optional tables in every UniVerse account
&COMO&          command output interactive processes
&HOLD&          alternate "printer" destination
&PH&            output from phantom processes
&TEMP&          VOC records changed by upgrade

File Dictionaries (metadata)
D_filename

Why did you want to know?

Remember that UniVerse is NOT the same as DataStage.
DataStage has other default tables, and lacks some of the ones mentioned above.