This is a newbie question..
Is it possible to 'package' (like in a RPM or DPKG format) the deployment directory that is created after a job is compiled and move that compiled job to a different DataStage server that is running the same OS and DataStage version?
'packaging' jobs
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Yes and no.
The term DataStage uses is "export", which creates a pure text image (DSX or XML format). When imported on the other server, this resolves into the appropriate structures within the DataStage Repository there.
The point you've missed is that there is no single "deployment directory" created by DataStage. There are rows in repository tables, and some new repository tables. The export/import process manages this.
Another way to manage it is to use DataStage's Version Control, which "sees" both servers and can manage the migration without the need to export/import. This is free with DataStage, but must be separately installed.
The term DataStage uses is "export", which creates a pure text image (DSX or XML format). When imported on the other server, this resolves into the appropriate structures within the DataStage Repository there.
The point you've missed is that there is no single "deployment directory" created by DataStage. There are rows in repository tables, and some new repository tables. The export/import process manages this.
Another way to manage it is to use DataStage's Version Control, which "sees" both servers and can manage the migration without the need to export/import. This is free with DataStage, but must be separately installed.
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.