UV Tables

dr.murthy · Post by **dr.murthy** » Mon Sep 13, 2010 1:00 am

Hi ,

could you please any one clarify me where i need to find out UV Tables information( means table information)

kondeti · Post by **kondeti** » Mon Sep 13, 2010 1:42 am

Murthy,
You will find in the project installation directory. But, you can't read directly those UV tables directly. You have to fire proper SQL queries in the command prompt (Administrator) for a respective project. Thank you.

dr.murthy · Post by **dr.murthy** » Mon Sep 13, 2010 3:36 am

Thanks for your reply,

am aware of datastage having two UV tables like
DS_JOBS and DS_OBJECTES but am not sure what information contains both tables.if posssible can you just guide me any info on this

ray.wurlod · Post by **ray.wurlod** » Mon Sep 13, 2010 3:50 am

Moderator: please move to Server forum

Moved. I'm thinking it should really go in General since this topic applies to both products but since I've added notes about Server job access, we'll go where you bid.

kondeti · Post by **kondeti** » Mon Sep 13, 2010 3:59 am

Both the tables DS_JOBS and DS_OBJECTES contain underlying metadata information about all the DataStage Jobs in a project. Like. JobId, Name, Created By, Modified By...etc. Thank You.

priyadarshikunal · Post by **priyadarshikunal** » Mon Sep 13, 2010 4:00 am

I don't think UV tables in datastage repository are documented. However the basic details can be found from the VOC and tables's data dictionary.

chulett · Post by **chulett** » Mon Sep 13, 2010 6:13 am

The second table would actually be DS_JOBOBJECTS and in addition to simply querying them, you could also use LIST.DICT to see their structure. But, as noted, they are not officially documented.

You could also use those tables in a Server job via the UV stage set either to localuv or by specifying a project / account name at runtime, typically via a job parameter.

kduke · Post by **kduke** » Mon Sep 13, 2010 3:28 pm

You have to trick DataStage into giving you the metadata for these tables. You need to create q-pointers. The VOC entry looks like this for DsJobs.

Q
<blank>
DS_JOBS

Where <blank> is an empty string. If you create with the ED command then put ; in there and replace ; with null. like c/;//.

There are lots of posts on q-pointers. RT_LOGnnn is another useful hashed file. EtlStats has lots of jobs which extract information from these tables. All of this is unsupported and may not work in the next release of DataStage. So be careful. API calls are a lot safer.