Automation of Development Datastage Code to production
Posted: Mon Dec 13, 2010 11:08 am
To All Datastage Experts,
I have been tagged with the all mightly task of automating the deployment of Datstage Code from development to production. Currently i development my own code on a development server, export the code when ready, then import code to production server and compile jobs. I know 8.5 will have some type of code control, but i have to come up with a code control method using version 8.
Here is what i have so far:
1. Continue to export Dsx from develolment when ready for production release, but code is moved to a freeware called subversion. From this area an operations team can access the code, but that is as far as i have gotten.
2. without allowing access to the gui what is the best command to issue in import code into production?
3. is there a command that can be entered to compile a list of jobs or is it better to just export and import jobs "with executables", or do the jobs still need to be compiled with this option?
Any advise will be appreciated...
I have been tagged with the all mightly task of automating the deployment of Datstage Code from development to production. Currently i development my own code on a development server, export the code when ready, then import code to production server and compile jobs. I know 8.5 will have some type of code control, but i have to come up with a code control method using version 8.
Here is what i have so far:
1. Continue to export Dsx from develolment when ready for production release, but code is moved to a freeware called subversion. From this area an operations team can access the code, but that is as far as i have gotten.
2. without allowing access to the gui what is the best command to issue in import code into production?
3. is there a command that can be entered to compile a list of jobs or is it better to just export and import jobs "with executables", or do the jobs still need to be compiled with this option?
Any advise will be appreciated...