Multiple Job Compile Utility

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Munish
Participant
Posts: 89
Joined: Sun Nov 19, 2006 10:34 pm

Multiple Job Compile Utility

Post by Munish »

Hi All,
I have to deploy the project with 60 separate jobs into Test env.

Is there any way to use
'Multiple Job Compile' Datastage utility
through unix.

Thanks and regards,
Munish
MK
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

Not from unix. Deploy your jobs with the executables and you will not need to re-compile them.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Unless your test environment consists of protected projects there's nothing to stop you connecting to them with a client tool and effecting a multi-job compile that way. Of course, as others noted, you can obviate the requirement completely by exporting and importing the job and routine executables.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

I guess you intention to automate the process of compiling the code as soon as it is promoted from Dev to Test. The other option available is, pass on the list of jobs that are promoted to 'dscc', a client executable, to compile the jobs.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Munish
Participant
Posts: 89
Joined: Sun Nov 19, 2006 10:34 pm

Post by Munish »

Thanks Gentlemen,
I deployed them as Executable.

However, if someone could throw some more light on

1.
I deployed the jobs as Executable with Design Information,
When I open that DSX,

Some of the DSX have design information with binary information (0,1)
WHERE
as in others it is Design information with some OSH information.

What exactly happens when we create Executable with Design Information.

2.
All the Executables (With Design) have
ToolVersion "4"
ServerName "olbdev-o.in.telstra.com.au"
ToolInstanceID "TEG_R1-CBA-TRIAL3"
in the heading.
Will that make any difference when we export them to another environment.
I tried exporting them to New Project but on the same server.
and it worked fine.

Any comments!!!!

Thanks and regards,
Munish
MK
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

1. 'Binary' executable for the Transformer stages, OSH scripts for the rest.

2. Internal product gobbledygook. Don't lose any sleep over it. As long as the 'another environment' is properly setup and at least the same version, you'll be fine.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Munish
Participant
Posts: 89
Joined: Sun Nov 19, 2006 10:34 pm

Post by Munish »

Thanks Everyone,
I got the answers.
Closing the thread.
Regards,
Munish
MK
Post Reply