Exporting - Importing DS components
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 132
- Joined: Wed Mar 01, 2006 11:12 pm
- Location: Pune
Exporting - Importing DS components
While migration from developement to UAT or SIT when we Export the datastage jobs do we need to manually compile the jobs after Importing.
My problem is that suppose I export job1 to a .dsx file. The status of the job in developemnt is compiled. now when I import it to UAT environment the status is 'Not Compiled' I need to manually compile the job.
Is there any way to skip the step of compiling and get the compiled job itself after migration.
My problem is that suppose I export job1 to a .dsx file. The status of the job in developemnt is compiled. now when I import it to UAT environment the status is 'Not Compiled' I need to manually compile the job.
Is there any way to skip the step of compiling and get the compiled job itself after migration.
SMB
-
- Participant
- Posts: 104
- Joined: Sat Dec 24, 2005 1:26 am
- Location: Bengaluru
Re: Exporting - Importing DS components
Compile is done to snanity check and to generate runtime code on server.
may be job in new environment has to compile to skanity check and to generate run time code on server.
so that reason job has to compile (recommend even its in compiled state).
I think its a matter of one click of mouse on compile button.
I hope it will not affect the job design or logic.
Is it right?.
Thanks,
Satish - Bangalore - India
may be job in new environment has to compile to skanity check and to generate run time code on server.
so that reason job has to compile (recommend even its in compiled state).
I think its a matter of one click of mouse on compile button.
I hope it will not affect the job design or logic.
Is it right?.
Thanks,
Satish - Bangalore - India
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
If the export includes executables, then it is not necessary to compile in the project into which the components were imported. Equally, it is not wrong to do so. Validating jobs is the preferred way to verify connectivity; parameter defaults may be changed in Director if desired without the need to re-design or re-compile jobs.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 132
- Joined: Wed Mar 01, 2006 11:12 pm
- Location: Pune
Re: Exporting - Importing DS components
HI Satish,getsatish_gk wrote:Compile is done to snanity check and to generate runtime code on server.
may be job in new environment has to compile to skanity check and to generate run time code on server.
so that reason job has to compile (recommend even its in compiled state).
I think its a matter of one click of mouse on compile button.
I hope it will not affect the job design or logic.
Is it right?.
Thanks,
Satish - Bangalore - India
Thanks for the information. but in my current project we have operator who will run the jobs in production using a menu designed in Unix and the Import will be done by the operator himself (though by DS Manager) and since I am having more than 400 + jobs so I need to click the button that many times or use the mass compile. But the problem here is that the operator doesnot knows anything about datastage and again its a matter of time as it takes more than an hour to compile all the jobs.
SMB
-
- Participant
- Posts: 132
- Joined: Wed Mar 01, 2006 11:12 pm
- Location: Pune
we have a client-side commandline-tool called "dsmove", which can be controlled by any script like batch or else.
It can:
- import any ds-element
- export jobs, routines and transforms (as single *.dsx-file for each element, if needed)
- delete elements
- compile jobs
all via command line.
If you need more details about "dsmove" let me know.
It can:
- import any ds-element
- export jobs, routines and transforms (as single *.dsx-file for each element, if needed)
- delete elements
- compile jobs
all via command line.
If you need more details about "dsmove" let me know.
Wolfgang Hürter
Amsterdam
Amsterdam
-
- Participant
- Posts: 132
- Joined: Wed Mar 01, 2006 11:12 pm
- Location: Pune
sure WoMaWil..WoMaWil wrote:we have a client-side commandline-tool called "dsmove", which can be controlled by any script like batch or else.
It can:
- import any ds-element
- export jobs, routines and transforms (as single *.dsx-file for each element, if needed)
- delete elements
- compile jobs
all via command line.
If you need more details about "dsmove" let me know.
it would be helpful if you can give me more details about the tool, and if possible the source code for it.
Thanks in advance...
SMB
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: