Moving a Datastage Project

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
Hemant_Kulkarni
Premium Member
Premium Member
Posts: 50
Joined: Tue Jan 02, 2007 1:40 am

Moving a Datastage Project

Post by Hemant_Kulkarni »

Due to diskspace constraints on our UNIX box, we are needed to move the Datastage projects from the path

/ascential/datastage/Projects/ProjectName
to
/san/datastage/Projects/ProjectName

One way of doing this is to create a New Project, Export the Old Project and Import into the New Project.

Considering that there are many datastage projects hosted currently, this exercise of moving the projects is a time consuming and I believe that this is the hard way of doing things.

Is there any smarter way of moving the projects around ? Like changing the VOC ?

Any thoughts on this would be helpful.
WoMaWil
Participant
Posts: 482
Joined: Thu Mar 13, 2003 7:17 am
Location: Amsterdam

Post by WoMaWil »

Dear Hermant,

Do it as you described. The VOC has many undocumented secrets and and everybody will blame you when there is a mistake.

Tell everybody to leave the project, check if there is no broken link to the project, then make one full export with for example dscmdexport as commandline-tool.

Then reimport. And you can go to town shopping during the export and later on during the import.

K
Wolfgang Hürter
Amsterdam
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Export/import is the only way. Any other "easy" way will involve you having to make repairs which will take even longer.

You can use the format.conv command to export and import, but this is messier and slower than the DataStage command.

Have you looked at other ways of recovering disk space, such as deleting files and hashed files that are no longer required?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply