Hi All,
I am trying to inspect the Job score from DS director, Can anyone please let me know how we can view the Job score and where can I find it .
Thanks,
Kaps
Job Score in Ds
Moderators: chulett, rschirm, roy
Post that question in the Enterprise Edition forum and mark the job type as 'Parallel'. Better yet, try searching that forum as you aren't the first person to ask questions about how to dump and read a score, so what you seek is out there already.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Thanks, I will surely visit the EE forum,chulett wrote:Post that question in the Enterprise Edition forum and mark the job type as 'Parallel'. Better yet, try searching that forum as you aren't the first person to ask questions about how to dump and read a score, so what you seek is out there already.
Thanks again
Kaps
Hi ,
To understand the dump score, you should have the undestanding of the operators,processes ..you can say the advanced datastage concepts..!
Generally it shows what are
1. What are the operateors datastage is using..and are there any additional operators are included ..
2.it shows keys used and the sorting..here you can avoid the sorting which is superfluous components..
Here job design can be improved..
3.It shows how data is partioned and sorted.
4.It shows what are the datasets created.
5.How data is buffered.
6.What degree is parellelism is achieved by the job and how many operators are running on each nodes..
Most important thing .. you can achieve is the superflous operatores like sorting ..which can cause performance issues and solution to this is to re-design the job..
----------------------------
Hope this helps..
------------
MK
To understand the dump score, you should have the undestanding of the operators,processes ..you can say the advanced datastage concepts..!
Generally it shows what are
1. What are the operateors datastage is using..and are there any additional operators are included ..
2.it shows keys used and the sorting..here you can avoid the sorting which is superfluous components..
Here job design can be improved..
3.It shows how data is partioned and sorted.
4.It shows what are the datasets created.
5.How data is buffered.
6.What degree is parellelism is achieved by the job and how many operators are running on each nodes..
Most important thing .. you can achieve is the superflous operatores like sorting ..which can cause performance issues and solution to this is to re-design the job..
----------------------------
Hope this helps..
------------
MK