DSXchange

Suresh - without providing a lot more information nobody is going to be able to help you. How do you know that the load is the slow part, it could be the read from SQL Server or the transformation. Instead of writing to Sybase in your job, output to a sequential file stage and a file in C:\nul and s...

Sachin1 - thanks for testing that, I was pretty certain that would happen. So the rounding into a single-wide floating point is probably happening at the database level, not at the time the calculation is performed.

If you have a 64bit hashed file then it will be able to store 18Gb of data. If your OS does not allow files larger than 2Gb then using a 64bit hashed file won't help; and this is what I think has happened on your system. If you have PX installed and implemented it might make more sense to use datase...

What error is Left(TempVal, index(TempVal,'.',1)-1) returning? The inital error you posted makes sense, since you might be getting a conversion error on the implicit string-to-number conversion that is occurring when you try to multiply the string by 100. The derivation copied above ...

I had forgotten that. I'll give that a try and see if that works... Yes, it did!

IBM Support has come back on this issue, After investigating, we concur that the the failure is because the framework has combined the operators. To successfully run the job, please add the following variable to the job, as a parameter and set it's value to True while running the job. APT_DISABLE_CO...

Odd, this approach works for me. Please post what the incorrect result is.

Where are you seeing your answer? If you do the computation in a transform stage into a Decimal(38,15) column and write that to a sequential file what value do you see?

djoni - That is the way it is supposed to work, once you have a "protected" status any copies of that job should also be unchangeable. I think it makes sense to do it in this fashion.

ssunda6 - and what length is it when you read it again?

Please note the difference between VARCHAR and VARCHAR2.

The "smat" command can be found in your DataStage $DSHOME/bin directory and has a number of options, the "-t" shows the configuration file values and any lines that are changed from their defaults are prefaced with a "*", thus the grep to show only non-default values. Have you checked your dsenv fil...

I would check the values from within a running job to be certain. Those are some odd ulimit upper bounds (I wonder why they aren't just set to `unlimited'? What OS are you on? Perhaps they are auto-calculated). Although I cannot think of any uvconfig setting that would directly limit memory size in ...

ssunda - please note that VarChar2() cannot be used to store strings with trailing blanks or containing all blanks. I can't remember if leading blanks are trimmed out as well but I think they are.

DataStage server jobs can handle this length of string without a problem (internally strings are stored in a neat little form of linked lists, so inserting the letter "a" at the beginning of your long string wouldn't mean doing hundreds of thousand shift-rights to the rest of the contents - neat, eh...