DSXchange

A stage name to me is an object type not a COBOL section/mainline/subroutine. Of course you are not going to get COBOL sections in your metadata. It is a single code stream instead of a "stage". For mainframe jobs you can get information like predicate and SQL from "stages" (i.e....

Ray, I guess your reply is related to "process" metadata because static job type metadata certainly carries stage names in the metadata. Static Mainframe job metadata is very much like static server-side job metadata.

Kevin Janes

MetaStage can extract "mainframe" based job metadata and store it in the MetaStage Repository. Mainframe jobs are still stored on the DataStage "Server". So, static information about a job can be derived using MetaStage. Mainframe jobs are just ftp'd to the mainframe to be linked...

Do you know the size of your project's .dsx? If case you are unaware a .dsx is a DataStage export file. If you do a full project export in DataStage you should be able to get the .dsx file size. The last I knew, MetaStage did have some limitations on the size of a single DataStage project's .dsx it ...

MetaStage has the ability to collect "process" metadata from DataStage jobs while they are executing. The process metadata is then fed into the MetaStage repository. Process metadata gives you details about the job execution like Start Time, End Time, Rows proessed per stage, data lineage,...

The admin and listener pieces can be installed on a workstation or server. The choice is yours. Here is something to consider. When the listener is active, it acts as an interface between the DataStage server and your metadata respoitory. If the listener is installed on a workstation, then that work...

If you are an existing DataStage user and you already have a job base built, then you may have some work to do to get it up to speed in order to take full advantage of MetaStage. Once again, if you make the investment, it will pay off. Meta data is a discipline of Data Warehousing just like ETL/Data...

Whether you start using MetaStage up front or 1 year later, it is extremely important to have a meta data plan in place up front. Notice I said "meta data" and not "MetaStage". The bigger issue here is whether or not you can afford to skip meta data up front. The answer to that i...

I think vmcburney makes a good point in this: "A combination of new and experienced is probably the easiest to assemble." I think a mentoring type arrangement can work well. One observation... the new people should have some sort of client/server, distributed environment aptitude or the pr...

Ken's number 6 is a huge issue. Without a structured approach, the project will be much more challenging. I will add three more reasons: 1) Lack of meta data. This is very significant. 2) Lack of business analysis experience. This is essential to define the transformation of data from source to ware...

Ken, your information is accurate. Those are the exact same issues we have had to deal with. It can be lengthy to achieve some of these objectives. I will share a portion of our strategy to overcome the issues you mention. There are pros and cons to it and there is no perfect answer. I am, however, ...

Agreed... :D . I try to avoid "reverse engineering" from DataStage because there are too many relationships to understand and maintain for it to be effective. Plus maintenance may be a headache with each new release of DataStage. There is too much to keep up with. If there are issues with ...

Just a note of caution. If you use DS server and connect to mainframe data, you may run into logic/processing that cannot effectively be done on the server side. As noted by viswanath, it is a good idea to code mainframe type jobs using the 390 component. Remember, the DS server pallete was designed...

In order to improve your percentages in MetaStage, you could take the time to "save back" your table definitions to DataStage Manager and then re-import to MetaStage. If you build this process into your ETL development cycle, then the overhead is minimal. You could even include descriptive...

Geppo, the one thing you lose when you extract from the .dsx is relationships. Thus, impact analysis is somewhat limited. At one time, I wrote a VB script to do what you are describing but decided our impact analysis questions were too complicated for "raw" metadata. Just curious, what ben...