Command Line Compile

ccormack · Posted: Wed Feb 16, 2005 11:04 am

The most useful functionality I can think of would be dsjob -compile ... an addition to the dsjob unix utility. I have wanted this since day one. That way one can use a build tool like make or ant to compile jobs in specific orders saving many, many, many man days of time.

ray.wurlod · Posted: Wed Feb 16, 2005 8:10 pm

How? You have to be in Designer to create/modify the job designs and you can compile from any client (multiple compile tool). How does being able to do so from a command line add anything?

kcbland · Posted: Wed Feb 16, 2005 8:14 pm

ray.wurlod wrote:

How does being able to do so from a command line add anything?

You can command line import, so if you're doing code migrations from a tool such as PVCS, you can easily integrate pulling the source code and importing into a scripted operation. You can't do the last step - compile. For these purposes, I developed the batch job compiler, so that you steer from your migration/librarian tool, and then kick off the utility to find uncompiled objects and compile them.

ray.wurlod · Posted: Wed Feb 16, 2005 10:19 pm

But if you've exported the job executable, you don't need to recompile. Smile

kcbland · Posted: Wed Feb 16, 2005 10:27 pm

ray.wurlod wrote:

But if you've exported the job executable, you don't need to recompile. Smile

Yep, and you double the number of objects you have to store in your library. Deploying source code plus compiled code is a religious discussion, there's philosophical and practical components. I encourage my customers to adopt an approach to always deploy source code and then compile -> doesn't matter, DataStage, C++, whatever. You never have to deal with the issue of reconciling executables against source.

Just this week one of my customers is releasing the next iteration of their data warehouse (we do 4-6 majors a year). One of the enhanced DS jobs was dropped during migration because of an incorrect version label. We could at least open the job and visually inspect to make sure our developer notes kept in the long description had our revision commentary and the logic looked correct. Just migrating the executable denies us some of this capability. Migrating both source and executable leaves a tiny bit of doubt that both are a matched set, as in if the wrong executable version got migrated with the right source. I prefer to remove all doubt.

PhilHibbs · Posted: Tue Mar 22, 2005 12:03 pm

ray.wurlod wrote:

But if you've exported the job executable, you don't need to recompile. Smile

You do if the target environment has different transforms to the source environment, or different project parameters.

I'd like to be able to compile transforms from the command line as well. Also I'd like to be able to compile them in an interface like the Multiple Job Compile.