Issue about DSEXPORT.exe
Moderators: chulett, rschirm, roy
Issue about DSEXPORT.exe
SET DSExportCmd="C:\Program Files\Ascential\DataStage7.5\DsExport.exe"
SET Host=aaa
SET User=bbb
SET Password=ccc
SET Job=ddd
SET Project=eee
Echo Exporting %Job%
%DSExportCmd% /H=%Host% /U=%User% /P=%Password% /JOB=%Job% %Project% %Job%.dsx
I have the above code in a bat file and when I run this, I get the dsx file for that job, but the problem what I have is that, it takes the shared container export as well used in this job.
So when I take individual jobs export from this project, I would have .dsx file for each job and each job has this shared container export as well. So when I try to import, it is trying to import the shared container as well.
So how to skip this shared container export while taking the job design export which acutally uses a shared container.
SET Host=aaa
SET User=bbb
SET Password=ccc
SET Job=ddd
SET Project=eee
Echo Exporting %Job%
%DSExportCmd% /H=%Host% /U=%User% /P=%Password% /JOB=%Job% %Project% %Job%.dsx
I have the above code in a bat file and when I run this, I get the dsx file for that job, but the problem what I have is that, it takes the shared container export as well used in this job.
So when I take individual jobs export from this project, I would have .dsx file for each job and each job has this shared container export as well. So when I try to import, it is trying to import the shared container as well.
So how to skip this shared container export while taking the job design export which acutally uses a shared container.
Thanks
-
- Participant
- Posts: 82
- Joined: Tue Jan 22, 2008 10:37 am
- Location: UK
Re: Issue about DSEXPORT.exe
I don't believe this is possible from the command line.Ramani wrote:So how to skip this shared container export while taking the job design export which acutally uses a shared container.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 82
- Joined: Tue Jan 22, 2008 10:37 am
- Location: UK
-
- Participant
- Posts: 82
- Joined: Tue Jan 22, 2008 10:37 am
- Location: UK
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Ascential Software\DataStage Client\Manager]
"Export Referenced Containers"="0"
---------
Probably best to use the Manager to set the option, export, unset the option, export, close Manager, then use regedit to export this value - as the .reg file is Unicode or at least double-byte.
[HKEY_CURRENT_USER\Software\Ascential Software\DataStage Client\Manager]
"Export Referenced Containers"="0"
---------
Probably best to use the Manager to set the option, export, unset the option, export, close Manager, then use regedit to export this value - as the .reg file is Unicode or at least double-byte.
-
- Participant
- Posts: 82
- Joined: Tue Jan 22, 2008 10:37 am
- Location: UK
A friend of mine Preston wrote a Perl script to strip out the shared containers and all the dependent objects. He based it on a script called dsx_split.pl or something close to that posted on this forum. We took the DataStageBackup.bat script on my tips page and turned it into DataStageMigrate.bat. The first script creates a file called JobList.txt from DIR *.dsx. The second we create this file manually in an editor. When we run this script it exports these jobs, next it imports them to the server and project on the command line. Next it compiles the job. Last it creates a audit trail in a table by creating a sql text file and running SQL Server's command line tool to run the insert statement. So know we know what migrated and when and by whom. Nice little tool.
We also copy the dsx files and check them into CVS.
We also copy the dsx files and check them into CVS.
Mamu Kim