DSXchange

I have a fix for the bug. It turns out that I improperly used the mkdir function in the script. I was passing 777 for the MODE where I needed to be passing 0777. The bug seemed to only cause issues in the CYGWin environment. The script was working fine under RH Linux, Solaris, HPUX and DOS (ActiveSt...

Wow. I have duplicated the issue.
I ended up with a directory with a permission of "dr----x--T" and none of the files are visible or exist. No error messages are generated by the script. Working on it...., I'll post resolution once I know more.

Hi guys. It's been a while. I have since moved on and have not used DataSatage for a few years. I have moved over to the dark side and have been using Informatica Power Center for the last three years. As I recall, I had both ActivePerl (http://www.activestate.com) and CYGWIN (http://www.cygwin.com)...

Text files on unix by definition must have a trailing Linefeed (CHR10). All UNIX utilities will make sure that any non-zero byte file will have a trailing LineFeed. Vi for example will always put a LineFeed as the very last character in the file, even if it did not have one to begin with. Nice progr...

Well obviously, the DSX file does contain alot of "gobbly gook", but usually, the differences show up as recognizable snippets of code that make sense to the developer. Most of the time the only difference is some mapping code or job control code. Try it, you would be surprised how readabl...

This is exactly the question one should be able to answer very quickly when managing code in terms of change control. This question is another reason I wrote ParseDSX.pl which is posted elsewhere in this forum. Look for "DSX Cutter" as the main thread title. Basically, ParseDSX will extrac...

Another alternative is to use the $HOME environment variable which is standard variable created at login time under most UNIX environments.

I always say, "When in doubt, Perl can do it!" This is quite a common requirement. Albiet, one I would like to say no to since it is quite easy to get bad data in a spreadsheet. However, we typically don't have the power to say no. Assuming you have controls on data content quality, wouldn...

I created two perl scripts a while ago to do just this. It's great for source code control since you typically want to do change control at the job/routine level. ParseDSX.pl will split a DSX file into separate DSX files, one per job/routine in the same folder structure that they appear in DataStage...