datastage conversion unix to windows

[rzandieh]

if anyone converted datastage7.x from Unix server to windows?
did you encounter many issues going from Unix to windows?
and what kind if any?


Thanks in advance

[kduke]

The biggest problem I have seen is the "/" to "\". This can be fixed pretty easy if you know some tricks. Most of my routines plan for this so they can fix themselves. The rest are usually in parameters so they are easily fixed. Otherwise just export and import. If you hardcoded path names then you will have problems.

[kduke]

I forgot ExecSH. Shell scripts are another big problem.

[chulett]

I think both of those issues can be resolved by installing something like the MKS Toolkit. It won't help with the performance hit you are probably going to take, however.

[kcbland]

Sequential stages with Unix file specified now needs to be DOS as well.

[chanduch9]

Can someone suggest -> how to convert the sequential file Line termination from Unix Style to Windows Style. (Note:we are not allowed to use unauthorised packages or softwares)

And while moving the project from Unix to Windows, are there any other issues other than
1.Unix scripts
2. '/' to '\'
3.Seq files line termination from unix style to windows style.

Your suggestions are really helpfull.

Thanks
CC

[chulett]

Hmmm... is a text editor considered "unauthorised packages or softwares"?

[asorrell]

What Craig is trying to say is that unless you dump the jobs to a dsx file and edit the dsx file there is no other "automated" way to change from UNIX to DOS line terminators.

Please note: unless you really know what you are doing, editing a dsx file is dangerous - you can corrupt a job by changing something you shouldn't have. It is, of course, not recommended or supported by IBM.

Also - is your site really sure they want to go to Windows? Most of my customers are trying to get OFF Windows for server platforms. One of the major reasons for leaving the platform is the virus scans and their interference with jobs. There is also a fair amount of the DataStage developer population that feels it is a less stable platform in general.

[ray.wurlod]

DataStage on Windows actually runs on MKS Toolkit, a UNIX emulator, so it can cope with UNIX pathnames provided that the corresponding Windows folders exist.

For example, if your DataStage job refers to /tmp and your logged drive (where DataStage is installed) is D:, then /tmp will automatically refer to D:\tmp. If D:\tmp exists, it will work.

If your DataStage job refers to /usr/data/controls, then you need to create D:\usr\data\controls.

To make life even easier, Windows can cope with forward slashes, so it would be happy with D:/usr/data/controls.

[chulett]

What Craig is trying to say is that unless you dump the jobs to a dsx file and edit the dsx file there is no other "automated" way to change from UNIX to DOS line terminators.

Hadn't even gotten to the "trying to say" part yet, Andy. But as you surmised was laying the groundwork for it as long as editors were not verboten. And Ray, of course, makes a good point about the slashes and what does or doesn't still work path-wise.

As to the actual record terminators one chooses to use, it is not driven strictly by the platform your server is installed on - if that was all there was to the story it wouldn't even be an option. It can read and write either on either, so it's really about whom - other than DataStage internal to your jobs - will be either supplying or consuming your files and what they 'need'. Bottom line, there may not be a burning need to change this setting.