DataStage code audits to verify compliance with standards

lmoose1 · Post by **lmoose1** » Tue Jan 13, 2009 10:13 am

We have our DataStage development standards documented, but audits by the admins are needed to ensure compliance. Audits can be quite time consuming for larger applications. We have a few short cuts, but are looking for something faster and more easily repeatable -- both for ourselves as admins and for the developers to first do their own self-audit. How do other customers do DataStage code audits?

ray.wurlod · Post by **ray.wurlod** » Tue Jan 13, 2009 2:42 pm

Done properly an audit IS time consuming. There's no way around that. You just have to make the investment.

vmcburney · Post by **vmcburney** » Tue Jan 13, 2009 5:17 pm

You can audit naming standards using some logic statements in the stylesheet that gets applied to DataStage job reports and export XML files. Generate a job report and have a look at the XSL stylesheet that gets applied to it. You can add statements that change the colour of stage and link names that do not use the right naming standards. You can colour stage types that are not recommended. You can look for hard coded file paths or login details. As for the job design itself it is always good to do peer review at some point.