DSXchange

I think I might have found a work around for the problem after spending so much time for it. I compared the cooked data and live data. In the cooked data, amount fields were without any quote around them. But the file from live is generated thro PX jobs and so while creating file makes all the numer...

Hi I am just wondering if buffer env params are causing this to fail, then it should appy to all files. But it works fine for cooked data and fails for live file. Some info abt job: rowsize 700 bytes, 35 columns. The buffer changed from 128K to 500K is the link row buffer in job properties. This is ...

Hi, Still not able get the solution for this and I have tried various things on this. Instead of running the job on thousands of rows, I ran it on 100 rows it failed. I tried following combinations on it with array size as 200: 10 rows - ran fine. 11 to 14 - ran fine 15 rows - ran fine 16 rows or ab...

But my job started on 14 Oct 07 at 16:20:36 and finished on the same day at 18:54:15 as per the logs.

So is this warning generated only in case a job runs thro' midnight or are there some other cases as well?

Sorry it is parallel job.

Hi, I was running a job and it generated following warning: buffer(6),1: APT_BufferOperator warning: newTime < startTime I searched the forum and there are just two posts and no enough info in them. Once of the job in my env was running for 150 mins yesterday and after that it finished with this war...

When we tested the same job with the same setting for the prepared data, it runs fine.

But when we run it for the file extracted from some interface, it aborts.

Just to improve performance we are using 200. If we do not, it takes around 80 mins and it we set it to 200, then runs in 50 mins or so.

Hi, I have a job which read a file and load it in SQL server table. ODBC stage is used to do this. Whenever I trying to load a big file it is giving me following error. djsLoadGECStagingExp.3611_200709.tfbExp.lnkExpWrite: DSD.BCIPut call to SQLExecute failed. SQL statement:INSERT INTO tblExposure(Si...

Thanks Craig!

There can be many ways to utilize it. Few which I can think of:

If you are creating temp files, you can create them in this space.

If the AIX is SMP machine, then just changing the dataset file path for one of the nodes and the new space would be used.

Never used the loops n all.

But may be a work around I would have gone for - Use the routine to perform looping as per the no. of values in input. Call the job or sequence in the loop in routine.

Other option could be a job param, but I think there is a limitation to its length.

The field should be nullable on output link after the lookup and am assuming when you mentioned nullable, you meant on the output link. Are you sure there is no matching rows from the lookup. It might be that matched record has Cont_Id as 0. Try updating all 0 fpor Cont_Id in lookup to other value t...

After creating C program for function, you need to create the object file from it.

The program that you compile to create the object file should be without main() function.

Then create the routine in PX and link that routine to this object file and it should work.

Sort your input on the input cols. Define stage vars and derivations as follows: PrevRecType_SVAR => CurrRecType_SVAR CurrRecType_SVAR => Incoming link column RecType SeqNo_SVAR => If PrevRecType_SVAR = CurrRecType_SVAR Then If SeqNo_SVAR = 2 Then 1 Else 2 Else SeqNo_SVAR Assign the SeqNo_SVAR to ou...