DSXchange

sean ...

Yes ... it will take a bit of experimenting, but spend some time in the MetaStage manuals reading up on the Scripting facilities ... it is possible to script the collection of objects and the depositing of them into a new User category.

... tom

dfong ... An interesting question is that if latest version could not be identified, what is the point of keeping multiple versions? I think I need to clarify something here ... Publish To Browser does not create identical multiple versions. If you Publish ERwin info via the CDSA MetaBroker, MetaSta...

dfong ...

There may be a simpler way, but what I do is use TOAD to view my tables and get the most recent export date.

... tom

Neil ...

No. You can manually export your Queries via Tools => Directory Exchange => Export, but I suspect you already know that.

... tom

gmaradana ...

You are experiencing a corruption problem with the repository which is not of your doing ... and you are not the only one. Apparently there is a bug in release 7.5.1r2. Contact Ascential (aka IBM).

... tom

akrzy ...

Yes, you can import a BO universe. Read up on the BO MetaBroker using the pdf on the MetaStage CD.

... tom

dfong ... we could locate the physical colume name of the PDM in the CommonDSA repository. There are hundreds of tables in the metadata model and we have no luck to locate the table. Ok ... couple of thoughts: 1) There is no such animal as a "CommonDSA repository". What you first have is a...

Giri ... Sorry ... no magic here. ConnectTo is the only solution and there is no way (presently) to automate this process. To make matters worse, you need to keep a manual list of what you connect so that when you create your PROD repository, you can duplicate your connections (they can't be migrate...

Shekhar ...

Why do you need information on the DTD? And you will find the process metabroker on your MetaStage CD.

... tom

Yes, this would be easier, but impractical. Consider that when jobs and table definitions move to PRD, and PRD and DEV live in the same repository. What will you do when the ERwin model evolves from release 1.5 to release 2.0 ... ??? And when some of your jobs, which are not in PRD are rotated back ...

Sathish ...

MetaStage is a highly complex environment and instructions on how to best implement this software is not something which can be done via e-mail. Contact IBM and get some MetaStage training. And read the Friendly manuals.

... tom

GreatPlay2 ...

Ok ... Ok ... I stand corrected. There is some interaction between Version Control and DataStage, but not between VC and MetaStage. If you were hoping that VC would provide meta data which MetaStage could collect and make available for reporting ... you are out of luck.

... tom

Parag ... We have three servers for DataStage. Using DataStage Version control changes will be moved from Development  Acceptance (System testing)  Production. You should plan on a DEV and a PRD environment. 1. First changes are made into ERWin Model 2. Import Erwin model into MetaStage. 3. Publis...

Tim ...

No - Version Control in no way contributes to meta data. Your DataStage jobs do not know whether or not they are being facilitated by Version Control, so all they emit is their standard process meta data ... and Version Control does not create any meta data.

... tom

Bill ... Ok ... let's try a few things: 1) Go to File => New => Templates and choose either Data Lineage or Process Analysis. Now work with the Wizard and try several different settings. 2) Within your DataStage Import Category, right-click a JobDesign and choose Data Lineage Where Used or Depends O...