I guess that one place to put the wrapper script is in the BatchServer, which I believe is the the location of the SAS startup script that is called from LSF. The object spawner is usually not involved in batch execution. But in my world, if the company policy is not to allow XCMD, what you are looking for is a way to fool them. A work around would have the same impact (and security issues) as the XCMD approach. Wouldn't be more straight forward to open a discussion in this policy instead? What will happen if they discover your neat work around...? ... View more

Make sure that you understand the requirement correctly! SAS DI studio let's you create a job flow as SAS Metadata. Based on this metadata SAS code gets generated. What will be executed is SAS code. If SAS code throws an error (eg. there is a syntax error in a expression defined in a transformation) then it's kind-of too late to try and capture this error and write it to an error table (as this capturing code would come after the error occured). A syntax error is a syntax error - how code behaves after that is unpredictable. What you can do is define conditions (eg: lookup table does not exist) and actions (eg. logging the condition in an error table). Thanks for the question! I didn't realize what the Return Code Check transformation is used for. Was good to have a read in the docu. http://support.sas.com/documentation/cdl/en/etlug/60948/HTML/default/viewer.htm#p0ygtz7di8z8kpn1ufncd1ajt1pj.htm http://support.sas.com/documentation/cdl/en/etlug/60948/HTML/default/viewer.htm#n13t3zm3lp6u7dn15a8k13mak3gh.htm The paper Art posted: That could be a way to capture rejected rows when loading into a SAS dataset with integrity constraints turned on (using audit trails: http://support.sas.com/documentation/cdl/en/lrcon/62955/HTML/default/viewer.htm#a001224397.htm) I personally feel that when this level of control is needed then it's possibly time to think about loading data into a data base like Teradata or Oracle. ... View more

Hi Kandasamy, 1. You can pass parameters from the scheduler to the DI job using the SYSPARM command line option. You get the value of the SYSPARM into a SAS macro variable called also SYSPARM. You can then use it as you want. 2. Not sure if this is relevant or not but you can use the Data Integration loop transformation to read the values of a table (audit table) and run another DI job each time passing it the current row value from the table as a parameter. Eyal ... View more