DSXchange

one thing that I am wondering of is these job sequencers were scheduled via DataStage Director before I installed the MetaStage ProcessBroker; could this cause the problem?

Yes.

OK ... couple of quick thoughts:

1) Is your DEV server the same as your PROD server? You must have the Process MetaBroker located on the same server as the executing DataStage jobs.
2) You must have the DataStage Emit Process meta data check box checked at the Project level.

... tom

On further thought, let me modify my last comment: since you really want to schedule as much of this as possible, you COULD export all the tables to the DataStage development environment, every time the ERwin model changes, via scheduled scripting. You would, however, need to advise the developers w...

If you are pushing ERwin table definitions to the DataStage developers (highly recommended as Best Practice) then you don't want to send all the tables from each model release. You would ideally create a User-defined Category, drag in just the delta tables and Publish (also scriptable) to the develo...

There are two methods of connecting or associating objects - but really only practical at the table level. Search this forum for "ConnectedTo". These features allow you to connect tables which have different origins.

... tom

Many MetaStage functions can be scripted, and therefore scheduled. Included in this group is your ERwin to MetaStage - check your MS User's Guide on Scripting. ERwin model change detection is another matter. The only way you're going to know which tables have changed is to get friendly with your mod...

Sasi ...

You must re-import from Oracle if your definition has changed. This sounds a little to obvious, so I may be misunderstanding your problem.

... tom

Hi Gaby ... I don't understand what you mean by "different identity strings". When you import your DataStage project into MS, the tables which originated in ERwin will have a different Identity String than the tables which originated in DataStage. Search the MS User's Guide For "Ident...

Gaby ... Is this how it's suppose to work? Do I have to connect the tables definitions manually? The two tables now have different identity strings - read up on the Connected to function. If the tables are modified in Erwin (for example, a column is added), and the steps within MetaStage are repeate...

Giri ... Ok ... a couple of things first: for Data Lineage you must have imported the DataStage project before importing any related process meta data. This is important for the process meta data to successfully connect with the JobDesign. Then decide on a JobDesign to report on. Get the run name of...

Giri ... Take a look at the packaged Queries - you will see Data Lineage Sources(7) and Data Lineage Targets(7). The "(7)" indicates DataStage7. If you right click and run these, you will be reporting on the entire project - probably not what you want. You need to build a Template. Go to F...

I don't mean to be tedious here, but sometimes little things matter (usually always). I will assume your Process MetaBroker is landing the XML files in the Listener\Runs folder and you are using a manual launch of the RunImporter bat file to bring this data into your repository. All that being true,...

Giri ...

Not sure of your exact requirements, but have you considered copying the XML files before importing them, and then change the RunImporter.cfg file to delete them after use ... ???

... tom

Nkali ...

Probably need a little more information. Are you importing your DataStage project into MetaStage, or are you working entirely with DataStage?

... tom

denzil ...

Yes ... all table and file types will be imported into MetaStage.

... tom