DSXchange

Lol - I was thinking of complex solutions and locking that is done differently in SQL for hashed files... and the answer was so simple!

Let's see... you remove the SUMT() and it works, add the SUM() and you get a DS warning... so wouldn't it seem that this is what DS is doing?

I've seen that limit hit here with just over 3,000 jobs. This is because of all the other type 30 (Dynamic) files created. The temporary solution was to change all LOG and STATUS type hashed files to type 2 - then go about making the project smaller. Too many CopyOfCopyOfCopy... jobs out there.

Sure, you can sign up for premium content at any time you wish to see a lot of informational and (hopefully) helpful content. AMT(SUM) is a new column and not in your DDL, it can have different metadata. When you are sure that a warning message is handled appropriately, you can demote it to informat...

abhilashnair,

TheBird is using an aggregator stage, so the direct solution there does not apply, but it does illustrate what could be your problem. The metadata of "AMT" is not guaranteed to be the same as that for "SUM(AMT)" from the DB.

My first thought is that your job is waiting on locks that it will never get. I vaguely recall having had a similar problem in the past. It is easier in this case to use a hashed file stage and change the query syntax around a bit to read "WITH NAME UNLIKE \\... AND READONLY EQ 'NRO'" in the selecti...

does your windows box have an active FTP server?

In this case the switch stage is exactly tailored to what you want to do and will be more efficient. If you have a large percentage of records that are dropped then the filter stage will be more appropriate, but if each row that comes in to the stage is passed on depending upon the values in one col...

I tend to ignore the link colors in the Designer as I've had cases where the run information in the Designer and that in the Director log are different. The log file information is correct. The error message is pretty clear, the data set you are trying to read does not exist. What error message do y...

Das, the documentation is really helpful in cases like this, look at the Ascential DataStage BASIC Guide on pages 6-158 and 6-159

the dsjob program is called from your UNIX shell. You will need to have your environment set up correctly in order to do this; i.e. issuing the ". ./dsenv " command in your DataStage home directory and either ensuring that $DSHOME/bin is in your path or calling dsjob with an absolute path.

Could you explain "not working"? Your errors should be different with fixed width columns.

my thoughts are that mput is not in your path

I would just use simple math; you can write your own roundup routine:

Roundup(Value,Places)


Hmmm, this could actually be an inline transform as well.

The INT() function will return 1 for 1.499 and 2 for 1.50001. Is this what you are looking for?