Could you check your readme file for the DataStage installation and make sure that it is supported for the 64 bit version; I seem to recall that it is not.
Can't find any information about MKS Toolkit in install guide. Besides that I have look into DataStage distr directory and have found next thing. There are 4 install files for MKS Toolkit in \2335-ds-75x2-win\DataStage Server\oe directory. Among them there are Toolkit64i.msi and Toolkit64x.msi. I think that this is install files for 64bit versions of Windows.
Can you tell me what is the purpose of this toolkit in DataStage? How important is this component for DataStage to work correctly and can I somehow exclude installing this toolkit with installing DataStage.
have you looked at the READMEs on your CD to see whether DataStage is supported on the 64bit Windows - I still think that it is not going to work.
The MKS Toolkit allows migration across platforms, especially allowing UNIX commands to be executing under Windows. If the install process complains about it then it is required and you have no workaround.
I have x86 family process and Windows64 that can handle 32bit applications! So if we follow the terms of formal logic DataStage can be installed on Win64.
unfortunately it doesn't work that way; unless Ascential specifically states that it supports Win64 then it won't be supported and might not work; which is why you might be having the problems you are.
I did a quick check at Supported Versions and didn't find Windows Server 64 bit; but your installation CD should have that information in the readme.
So please look at your DataStage files, if Win64 isn't in there then you are SOL.
Semkaa wrote:I have x86 family process and Windows64 that can handle 32bit applications! So if we follow the terms of formal logic DataStage can be installed on Win64.
Where "formal logic" breaks down here is that DataStage engines make calls to system functions that may not exist in Win64. That's why we have to wait until DatStage is certified on a particular operating system before we can guarantee that things will work. If they do happen to work (for example on WinXP) where not certified, that's just a fortunate happenstance.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Don't be sorry - don't hijack. Start your own thread and if you feel it helps, post a link back to this one. And when you do, post the error(s) you received, even if they are 'the same'.
-craig
"You can never have too many knives" -- Logan Nine Fingers