DSXchange

You will need to explicitly define the format for the date field. Default is YYYY-MM-DD, with the hyphens.

You can use Basic Transformer to handle this.

For AIX, I'm struggling to get a straight answer on the cost of the compiler. I've seen per user and per processor options. Per user is pricey, but not that pricey compared with DataStage. Per (named) user, on the other hand, wouldn't sit well with the DS Designer concurrent user licensing model. I...

Dang. Foiled again!

That is not a fair attitude to have when we are dealing with an operating system. It is like saying that Windows 2000 and Windows XP are not much different. Ascential made a point on specifically saying what is supported and what is not. If you are able to get something to work on something that is ...

The surrogate key generator always starts at 1, unless you provide it with an alternative value (using a parameter, perhaps), pull the latest value from somewhere (the database, perhaps), and doing the calculation in a transformer. There are several solutions. The problem you had was that you think ...

Solution: Include the job design next time.

There is really no good reason. Having the job design would allow you to visually verify and diagnosis problems with your programs if it fail. Like for this situation.

You can use a BigInt if you want. My talk of the decimal field is specifically for those 'fixed length' fields that some clients (especially those with mainframe-produced data) like to see and use.

Use the Change Capture Stage. Chapter 30 on your Parallel Job Developer Guide (parjdev.pdf). Handle the results on the following filter stage/transform stage. For fields that are not used, you can use a merge stage to combine those into the main stream after the Change Capture stage. Correction: Now...

This will work for "Time" field. Have fun with the "Timestamp" version.

Yes.

Make sure your metadata for input and output are correctly defined. That's all. Edit: RCP would not trigger this bug unless there was a pre-existing name being propagated. Considering that it's an string, not a number field (which Surrogate Key Generator stage only generates), this is an unlikely ca...

Harithay -- You have the following options: 1. Read. Parallel Job Developer's Guide (parjdev.pdf) provide an excellent resource. Check out Chapter 15 - Transformer. 2. Search. This forum have a long history of information that is very useful for you. Do a search for "stage variables". 3. T...

When you are dealing with integers, you can give it any precision numbers you want, but... Datastage will ignore the precision number when it handles Integers. If you MUST have a specific length for numbers, either use Varchar, or Decimal. Integers are exactly the same as C's Integers. P.S. Integers...

DataStage is dumb. Dumb. Dumb dumb dumb. It does not read minds. It does not know what the intent of something is. It does not know what is right, what is wrong, where things are, and where things should be. Keep that in mind, and whenever you tell DataStage to do something, you have to tell it ever...