DSXchange

I have been asked to convert CoSort programs to PX as it was felt that PX sort is faster than CoSort. But I would like to know if there are any benchmarks to prove that PX is indeed faster than CoSort. I do not have the facility to test huge chunks of data (like over 150 GB). If any one has some sol...

Thanks, but the difference arises only while I am sorting the records
...how can I ensure that the sorting of the duplicate records in datastage is similar to what I described for Cosort?

By the way, can Cosort be plugged into PX? I thought it was a functionality only in the Server edition...

Sorry Arndw, I wasn't able to read the complete message... can u let me know what approach I need to take?

Thanks

Sorry Arndw, I wasn't able to read the complete message... can u let me know what approach I need to take?

Thanks

I have been trying to re-create a cosort program in Datastage PX. I have managed to replicate everything except the sorting order. Cosort uses a /SORT statement to sort incoming data. But when there are equal keyed records, it still sorts the data based on some unknown internal algorithm. Datastage ...

Thanks for the explanation, ArndW But if I were to use Minhajuddin's suggestions, then I will have to set the Nullable property to 'Yes', right? This again is not my requirement (sorry!) I want records having null values to be REJECTED by Datastage... these records should NOT come into the main proc...

Ok, my favourite editor is Edit Plus
The sample record I am giving is

12345||||ABCDE

The three fields in the middle have no values... how do I check what kind of null is used there?

Thanks.

sorry for getting the names wrong

Sorry if I have been confusing, let me clarify... I want PX to tell me when a null value is coming in the input field 'Field1'. But Field1 is a key column and hence cannot be nullable. In the event of a null coming in, the record should be rejected... I thought this was the purpose of setting Nullab...

Yes, the sequential file is actually read from unix environment... so what should I do to handle this kind of null?

THanks..

i haven't tried writing it to a dataset, but when I wrote it out to a sequential file, the null values are written to the output..

actually, I havent set the default value...

I am quite confused as to what is the real purpose of setting the Nullable property as 'No'. In a job, I had to read a field with a BigInt datatype from a sequential file. It was a key field, so I set the Nullable to 'No'. While testing it (reading the sequential file input), I gave a Null value for...

It works the same wrong way from the command line too...the 'winkie' was because I will have to raise this issue to my client and that would have to be done only in the rarest of rare cases... I will try to find out if there's any alternative support available within my current framewrok (without go...