Currently here at St Paul Travelers we are using the DataStage Version Control tool as our mechanism for DataStage code asset management. We are now beginning to use the DataStage PX, and have now attempted to migrate our code from development to the production environment. As a result, we encountered the following (see below) error while migrating the code. One note about our environment is that we do not have the C++ compiler in our production environment; all code should be pre-compiled and migrated to production without having to recompile, enterprise mandated. As a result the DataStage Version Control tool is attempting to recompile the code when it is moved to production. Is this standard practice with this tool? If so, what is the recommended approach to handling the movement of code without having to recompile the code, or is the correct approach?
Currently we are unable to migrate our PX jobs to production you input would greatly be appreciated.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2006-06-07T23:25:11Z by SystemAdmin
Pinned topic DataStage Version Control - Code Asset Migration
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2006-06-07T23:25:11Z at 2006-06-07T23:25:11Z by SystemAdmin
SystemAdmin 110000D4XK332 PostsACCEPTED ANSWER
Re: DataStage Version Control - Code Asset Migration2006-06-07T23:25:11Z in response to SystemAdminThat's an b:c3c6c386b5option[/b:c3c6c386b5] in the tool - simply uncheck the 'Recompile' option when you promote to production. You can also set that to be the default - meaning it can default to being unchecked.
See if that helps.