DSXchange

Can you please post the record schemas for the input and output so that we can see more precisely what you are attempting to do ?

If you require a Very Urgent response sign up with your support provider for premium service and find out the true cost of urgent. DSXchange is an all-volunteer site whose participants post as and when they can. And remember the old adage: lack of planning (or training) on your part does not consti...

I too am unfamiliar with Netezza so someone else will need to provide the details. In an ODBC environment there exists a setting called Transaction Isolation Level that you can set. I don't know, and can't find out right now, whether this is supported in the Netezza-specific stage.

Your requirement is faulty. You can not force every year to have 52 weeks because every year has more than 52 weeks.

At some point (around about year 7) you will have a year that either has 53 or more weeks, or that ends before Christmas.

Take a look at the server Transform WEEK.TAG and its associated function.

That will give you the kind of logic you will need to implement in a function that YOU write - there is none "out of the box" for parallel jobs unless you resort to using a BASIC Transformer stage.

Decimal[0,0] is illegal - you must have precision (the first of the numbers) greater than or equal to 1.

First, an alternative to the original question. What gets displayed by a query is governed by an entry called @SELECT or @ in the file dictionary. INSERT INTO DICT Time_D_Keys(@ID, F1, F2) VALUES ('@', 'PH', 'TimeKey ID.SUP'); Now to your more recent questions. When you create a tabl...

You simply can not sum dates or timestamps. You need to derive another field, such as length of service, and sum that.

Open the Designer and click the Job Report tool (the one that looks like an Internet Explorer icon). Does this report contain sufficient detail?

Modify stage with output link having a scale of 4 for this particular Decimal data type. Use decimal_from_decimal() function with [round_inf] as the rtype argument.

OK, I stand corrected (though wondering about why I thought it was microseconds). Have to wait till next time I'm on a Solaris system to investigate.

Just out of curiosity (again!) is the default on your system 4,000,000 ?

Partitioning of a Lookup File Set is "locked in" when the Lookup File Set is created - the index is based upon the indexed data. So whatever you add to the design is ignored. If this is something other than Auto, DataStage issues the alert to tell you that your instruction will not be heeded.

Posting the same question in multiple forums only wastes everyone's time. Please do not do so.

Reduce your transaction isolation level from Serializable to something of lesser intensity.

My point is that, if Column 4 is null, you actually base your decision on Column 2 from the left input.