DSXchange

First off, do you understand what a "Type 2 Slowly Changing Dimension" is and just need help implementing it in DataStage or you're not even sure what one is? For the latter, there are plenty of sites out there you should be able to find to explain all of the SCD types. The tutorial that s...

A better solution would be to provide the full path to the file and that path should be parameterized. The project directory really is the last place you want to be putting files, you should have a dedicated separate location for landing files - ideally on a different partition.

You just need to have valid 'XPath Expressions' in the XML Input stage so it can parse them out properly and it's perfectly OK to only define a small number of columns and ignore the rest. Do you have an xsd for this? That would be the best metadata import source (which is what builds the XPath Expr...

Welcome aboard.

An exact search for "VSAM" found 70 other posts that mention that, in your shoes I would start there and see if any of them help.

Have you confirmed what in fact is taking the majority of space in the database? Is it still the log tables? Also sounds like you may want to involve your official support provider if your DBA needs some help identifying tables and recovering space in the database.

Have your DBA track down the large objects in the database, I would suspect they'll be job log related. Are they being purged on a regular basis?

Edited to add: Found you posted here as well so it seems that may indeed be the case.

Not sure how many different ways people can say this. There is a single value that can apply to all columns or you can setup unique values at the individual column level. Had you read the documentation? From Chapter 5 of the Parallel Job Developer Guide: Field defaults Defines default properties for...

Yah, that's been an interesting point now that I am working with Informatica - it seems to treat nulls as empty strings or at least in a fashion that I'm not used to. For example, it allows you to concatenate null fields into strings without any adverse affects, something I had to see first hand to ...

You add the appropriate "null field value" property to each column, individually.

Welcome aboard. I corrected your subject as "ERROR" didn't really help anyone know much about what your actual problem or question. In order to proceed, we're really going to need more information. Where do you get this error? When exactly does it happen? Did anything happen that you feel ...

^
+---- In a PX job, of course.

Wow... Michael Hester... long time no see.

Sounds like you still have CHAR data types in there. Once you trim your CHAR you need to ensure you have VARCHARs everywhere after that.

Phil posted that answer when the question was still over in the PX forum.