DSXchange

we migrate the DS from 8 to 11, and AIX to Linux. I need to compile the c++ program in the Linux server. I used this command to get the .o file, and it's no problem. g++ -c HexToChar.cpp -o HexToChar.o however, I failed to compile the parallel job which use the .o file. And this is the error log. I ...

Since 2011, I joined the team and started to develop using Java and DataStage. I am familiar with JavaSE and the Datastage jobs buildup. I know how to tune the Java program or DS job to get the better performace. But it seems that only DS ETL knowledge is not good enough, what kind of job(position) ...

Use DS in the BI team.

I do the DataStage projects, 5 years, I like this tool and this kind of job. Everday I thinking about the process of data and how I could tune the job to have better performance. I got the interview opportunity about BI last week but I failed. The interviewer didn't ask my anything about the 'tech',...

btw, i set many parms to the parallel job. others are all okay, the system parm fail

yes.
define the system parm in the parallel job property;
DSAttachJob to get the parallel job handler;
DSSetParm to set parm to this system parm.

when run job, 'no this parm' error.

i called DSAttachJob. And also add system variable in the parallel job.
But failed on set parm , saying no this parm.

i found this in the forum Before join stage use sort stage and try this.. I think it may hapen because of memory issue.. Inline sort handle less volume of data. So is that possible because of too big volumn of data? in the sort stage i need to sort 9 million data. and i set 1000 M in the sort stage.

my colleague told me i should not use Hash to partition in the Sort stage. i am going to try another partition type

Aggregator_49: When checking operator: User inserted sort "Sort_300" does not fulfill the sort requirements of the downstream operator "APT_SortedGroup2Operator in Aggregator_49" I encounter this warning.. in the job, i use a sort before Aggregator. in the sort, i partition with ...

it's not correct to set environment variable user ds set parm
I found this in the forum.
but I want the job to run for different apt. e.g. the routine starts job1 using apt1, starts job2 using apt2. what should i do ?

code=-3 [ParamName does not reference a known parameter of the job]
hi chulett,
this is the error it shows, could u please advise how to fix ?

get it.. i will check the paramerr

so sad I search in the forum so long time but cannot find any post. I use a routine to run the DS job, now I want to specify the different APT fot different job, eg. file1.apt for job1, file2.apt for job2. I hope I can set this by DSSETPARM like the user defined params but failed. paramerr = DSSetPa...

so, how to fix this problem ?