DSXchange

Hi Kim,
I import the dsx and i also exported and created all the files & folders that are necessary ap per u r Copy2project and install.txt instructions.
I try to run DSJobReportDb by passing a jobname and i get this error:
Job stopped - before-job routine returned error: DSU.ExecDOS is not cataloged
I dont have exedos functinality in before or after job routine .
How can i modify this job.

Thanks,
Har

Search
I know for a fact that "DSU.ExecDOS not cataloged" has been answered in the past.

ray,
I check the VOC File for ExecDOS and its not their.
I planning to add the following record to VOC file,can you correct the following record if their any mistakes in it
DSU.ExecDOS
001 V
002 DSU_BP.O/DSU.ExecDOS
003 B
004 BN
009 DSU_BP.O

Thanks,

Seems like you need to replace all occurances of ExecDOS with ExecSH and convert the DOS commands to UNIX ones as well.

Craig is correct. There is a before job routine which runs the dsjob command. You need to fix the path to make this work in your project. If you are on UNIX then you need ExecSH instead of ExecDOS. You also need to change / to \. This outputs to a XML file below the project in the KimD folder. You can change all this here.

../../DSEngine/bin/dsjob -report #Project# #JobName# XML >./KimD/#JobName#.xml

is the command that it wants to execute. This xml file becomes the source file for all 3 tables.

ETL_JOB_HIST
ETL_ROW_HIST
ETL_PARAM_HIST

For the PX users I have a much improved version of this job and these tables. The ETL_ROW_HIST was aggregated to remove the partitions. We found that row counts at the partition level is valuable to see if a hash partition is unbalanced.

We also found that we are RAM bound. The xml contains the process id of each stage. If you get a ps -elm then you can look up the size and add up the process sizes for a job. This takes some work if you are on a grid or in our case a cluster because this requires figuring out which server the PID is on. This required Kevin to parse the config file.

If we can add up all the processes running by job then we can figure out when we start paging and do better load balancing. We are real close to getting all this in tables. I will see if they will let me post it.

I have a script now which will do the same. It adds up all the process sizes for one job and displays the process names and sizes. Way cool.

I am trying to run the command (changed #Project# and #JobName# to actual values and tried it in the unix prompt)

../../DSEngine/bin/dsjob -report #Project# #JobName# XML >./KimD/#JobName#.xml

I am sure that i am typing the correct names and using the correct caps, but i recieve the following message....
Whats wrong, and yes I am running as dsadm

The #'s surround parameter names and their values get substituted at run time. Just like $Project would in a shell script. All jobs run in the project directory. The path to dsjob is because the Projects directory is relative to the DSEngine directory on most DataStage servers.

I think you need to go to class and learn the basics. These jobs require basic knowledge of parameters and DataStage in general.