Trends for deployment of your production DataStage Jobs?

eostic · Post by **eostic** » Tue Apr 21, 2009 10:49 am

Hi all...

Wondering specifically if many/any of you deploy "only" executable Job details to your production servers, or if you also include the Design metadata?

(specifically, the export option of "Executables without Designs").

If so, why or why not? Do you use the read-only feature along with migrating design info? ...or other alternatives.

Thanks in advance!

Ernie

kduke · Post by **kduke** » Tue Apr 21, 2009 12:56 pm

Production is always read only to developers but we always do designs. It is easier to debug. It is also impossible to tell if production has the correct version unless you can see the design.

ray.wurlod · Post by **ray.wurlod** » Tue Apr 21, 2009 1:17 pm

... or use the Version number field.

kduke · Post by **kduke** » Tue Apr 21, 2009 10:11 pm

We are using the comment field in job properties but they don't always update it.

sima79 · Post by **sima79** » Wed Apr 22, 2009 4:21 am

We use the option "Export job designs without executables". All code goes through our source code control procedure. Code is promoted through each environment dev->test->prod. The source code is imported into each environment then compiled. Good source code control should minimize the chance of deploying the wrong code.