Search found 81 matches

by blewip
Mon Feb 19, 2007 3:15 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: DataSets can't handle float properly
Replies: 10
Views: 3390

That's what I'm doing in the extraction job.

It shows up as 2.55487e+07
by blewip
Fri Feb 16, 2007 8:18 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: DataSets can't handle float properly
Replies: 10
Views: 3390

That's what I'm doing in the transformation job.

That where I get the value 25548700.
by blewip
Fri Feb 16, 2007 5:21 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: DataSets can't handle float properly
Replies: 10
Views: 3390

DataSets can't handle float properly

I have been struggling to get my floats (doubles actually) to work correctly. I think I have found out why, the DataSet can't handle floats correctly. We have a common framework where an extraction jobs is used to determine which rows are extracted, this is stored in a DataSet then a transformation ...
by blewip
Fri Feb 24, 2006 9:57 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Error When Comiling the Job Sequencer
Replies: 6
Views: 2460

My problem was actually caused by the p.c's network card set to Half Duplex.

My more complex jobs didn't compile either.
by blewip
Wed Feb 22, 2006 4:34 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Error When Comiling the Job Sequencer
Replies: 6
Views: 2460

I am also getting this error, compiling sequences, but jobs are okay. My p.c is new, but I am an administrator, and I have refeshed the security to the DataStage client folders just in case. I am wondering if this is a bug, I am running 7.5.1. If I don't hear anything, I will raise this with Ascenti...
by blewip
Tue May 24, 2005 5:51 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: PX Functions
Replies: 2
Views: 1343

Well this should work

Code: Select all

StringToDecimal(DSLink2.VarCharField)/1000
by blewip
Tue May 24, 2005 3:34 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: More problems with Pesky Floats
Replies: 15
Views: 7643

If I change the precision (the length) it does not seem to have any effect. However I have been playing around with something that does appear to have an effect. I did say that we have tried Double and this has no effect, however it turns out that this is not entirely true. If I change the type from...
by blewip
Mon May 23, 2005 9:38 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: More problems with Pesky Floats
Replies: 15
Views: 7643

It seems that the problem may be with the conversion from Float to display, internally the data may be okay. However as I actually want the Float to be output to a file it's not very helpful for me. I understand that the conversion process can be the source of problems, but I think this should be co...
by blewip
Mon May 23, 2005 7:21 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: More problems with Pesky Floats
Replies: 15
Views: 7643

ArndW I tried some other numbers, all pretty bad, the worst I found in my short testing was this one 10234.5683 I am sure there are worse ones, however if you assign a float to this value and then display the result, it is 10234.6. This is an error of 0.0317 I also tried to do some Math with FLOAT2D...
by blewip
Mon May 23, 2005 5:33 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: More problems with Pesky Floats
Replies: 15
Views: 7643

I shall make no comments about the application (I didn't write it). You say the best solution if you have a float input is to leave it as a floating point number However this is what I am doing when I get the 0.0022 error. It is actually better when I take the Float and convert it to Numeric; error ...
by blewip
Mon May 23, 2005 4:50 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: More problems with Pesky Floats
Replies: 15
Views: 7643

Well the first thing is we are a Bank and therefore we are looking to get a good representation of the number. I guess we do accept that with a Float we are not going to get and exact number all the time, but I just think the difference is too great. The difference between the entered value and the ...
by blewip
Mon May 23, 2005 3:39 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: More problems with Pesky Floats
Replies: 15
Views: 7643

More problems with Pesky Floats

Is anybody else getting unexplained results from Floats? We have a database with Floats in it and we are finding difficult to get any consistent results. We have generated a test case and I will explain the results we are getting. Basically we are generating 1 row of data then hard coding a Float an...
by blewip
Fri May 20, 2005 5:03 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: DSEE and SunOS
Replies: 1
Views: 1075

I think the 1st part has been answered before, only Solaris on Sun platforms are supported.
by blewip
Fri May 20, 2005 2:16 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Formatting Decimal to String conversion
Replies: 3
Views: 10909

I had a few problems with the old solution, and I found a better way. There appears to be a new function DFloatToStringNoExp, this converts to string. doesn't give you an exponential and allow you you have control over the number of decimal places. DFloatToStringNoExp(DSLink2.FLOAT2DECI,6) I sure pe...
by blewip
Wed May 18, 2005 8:19 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Stored Procedure Stage with Sybase on unix
Replies: 8
Views: 4665

Thanks guys this work a treat.

I set the return code = no.
Also my Stored Procedure just returns a result set, so the Stored Procedure Parameters were left blank.