DSXchange

DataStage 6 upgrade has been worth it for us. There are some immediate benefits we were able to take advantage of. We have been using in-process and inter-process row buffering out of the box to improve job performance. You can turn this feature on at the job level (recommended) or the project level...

I also agree that new releases of the client should be able to talk to older server versions. We have develoment and production boxes and if the two do not get upgraded at the same time (which is not easy to do sometimes) then there can be development/testing issues because of the different versions...

We just upgraded from 5.1 to 6. The upgrade was painless for us because we are used to the process. We are running on AIX. I am very happy with DataStage v6 and feel it was worth the upgrade. I have a few open cases with Ascential pertaining to the Row Buffering feature that is new to v6. Row Buffer...

Just as a follow up, yes, I agree it is ideal to create and maintain table definitions in your modeling tool (such as ERWin) which would feed the rest of your development cycle. Also, it is also a good idea to include business metadata at the column level within the data models themselves to make it...

Some other factors drive the decision to do things a little bit differently such as number of Jobs in your project (over 500), number of table definitions (over 1500) and potentially this situation: We create sequential files out of DataStage that are then FTP'd to the mainframe (where the Data Ware...

As a best practice, DataStage developers should save Table Defintions back to DataStage Manager in order for MetaStage to build the Job/Table relationship (for lack of a better term). Hash tables, flat files database table defs, etc... They are all applicable. If table defintions are not saved back ...

I believe the preload option uses the Hash File Stage Read/Write Cache sizes to determine whether or no it will preload the hash table. Using DataStage Admin, check the project properties under Tunables for the Hash File Read/Write Cache size. By default, it is 128MB. If the server has enough cache,...

I have reported the Row Buffering / Sort bug to Ascential. My work around is to use "In Process" row buffering on the job that has a SORT Stage. In Process row buffering does work with the SORT Stage but "Inter Process" does not yet on AIX. I am not sure about NT, Solaris, etc......

I wanted to pass this on to DataStage v6 users. We have just upgraded from v5 to v6 and the most beneficial feature so far has been Row Buffering. Row Buffering can be set at the project level (on the server) or at the job level (job properties). We are choosing to do it at the job level for tuning ...

So far, we have not used "Data Elements" in DataStage. It sounds like they can add value in certain environments but I am not so sure we have enough standard format to justify using them. Most transformations for us have to deal with calculations and not really a standard format for someth...

They added a "Parallel Design" canvas to the Designer. There is now server, job sequence, mainframe, shared container, and parallel. The parallel design pallette has different objects than the server pallette because coding parallel jobs is different. All of the normal components of DataSt...

I consider MetaStage to be seperate from DataStage and prefer not to add MetaStage discussion under the DataStage topics. I thought it would be a good idea to add a MetaStage Enhancement Wish List.

Thanks,
Kevin

We have been applying transforms (XSLT) to MetaStage output and came across the same message. To correct it, we changed the style sheet to the following: OLD <!-- xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl" --> NEW - <xsl:stylesheet version="1.0" xmlns:xsl="http:/...

In DataStage Manager, under the menu item Import and then Table Definitions, there is a selection for XML Table Definitions that brings up a dialog that allows you to select schema types biz, xdr, and xsd for import.

-Kevin

What type of Schemas are you trying to bring in? Database schemas/Table Definitions? For certain data modeling tools like PowerDesigner, you need to save the model as a PowerDesigner/XML format (which is an option when you save). Then, whe you import the schema to DataStage, DataStage uses the Power...