Hi All,
I have a dsx file which I am trying to import into DataStage 7.1 version.
The import does not work and my guess is that it could be because the dsx file could be from a different version of DataStage. Is there any way to find out from which version of DataStage the dsx file was created?
Regards,
Sumit
Version of jobs in dsx file
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 197
- Joined: Mon Feb 17, 2003 11:20 pm
- Location: India
-
- Participant
- Posts: 197
- Joined: Mon Feb 17, 2003 11:20 pm
- Location: India
Imports from other versions of DataStage work just fine - as long as the version being imported is < the version being imported into, i.e. is older. The import process will automatically upgrade your jobs to the current version. What version are you importing from?
Other things off the top of my head - are you running out of space? Is your export corrupted?
Other things off the top of my head - are you running out of space? Is your export corrupted?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 197
- Joined: Mon Feb 17, 2003 11:20 pm
- Location: India
Thats what my question is. Does a dsx file store any information about the version of the tool using which the dsx file was created?The import process will automatically upgrade your jobs to the current version. What version are you importing from?
I checked the space and we have close to 6gig of space available.Other things off the top of my head - are you running out of space? Is your export corrupted?
Thanks and Regards,
Sumit
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Error on CREATE.FILE command suggests a space or permissions problem. Does the executing user have write permission to the VOC file or to the project directory? Execute (use) permission is also needed to the directory.
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.