Hi
I'm trying to export certain jobs from datastage using istool command.I'd like to know if .isx must be used in the file extension while using istool command?
Even it is not so can anyone share light on how to import from a .isx format to the datastage
@chulett Thank you.
Just want to add a few things as the topic you have pointed is resolved. someone pointed out earlier that if the password contains '$' a backslash needs to be infront of it.
I don't think it is needed.I'm using a password that contains a '$' and without the '/' it is working fine for me.
and I guess if I am using istool utility to export assets I must use the istool utility to import those.
OK... forgot the older conversation we had on this topic. So, is the consensus that after you uncompress the .isx file you can rename it to a have a .dsx extension and then use the Designer to import the file?
-craig
"You can never have too many knives" -- Logan Nine Fingers
@ chulett @arndW I have successfully created the exported.isx file in the server and place yhe file in my local folder usinfg ftp.
Then when i'm trying to extract that using 7zip it gives me error saying that "can't open file <filename> as archive.
I think I've used WinZip to uncompress the file, and just tested with my local compression tool at work, WinRAR. The single element files in the .isx file are in XML format and I haven't tried to import them but if you decide to give it a go please post your results to this thread so that others might benefit. My point was merely that the .isx file is actually an archive and it contains its own control structure information.
OK, but the conversation is specifically around the compatability of that XML format with the other import methods to see if using istool to get it back in is one's only option.
Hopefully someone can test and verify this.
-craig
"You can never have too many knives" -- Logan Nine Fingers
</a>