Page 1 of 1

MKS toolkit issues

Posted: Tue Oct 21, 2014 1:27 pm
by taylor.hermann
I'm going to revive this old topic, since we may be having issues with MKS toolkit. We are running Version 9.1 on Windows. Is installing MKS toolkit a requirement to install datastage? Because our admin told me that he didn't see an option to not install it. And that it was done behind the scenes. He only sees "MKS Platform Components 9.x" as installed components on the server.

Is it possible to uninstall this without issues? Or will it break everything?

Posted: Tue Oct 21, 2014 2:16 pm
by PaulVL
I think you should break your topic into it's own thread and describe the issue you may be having.

Posted: Tue Oct 21, 2014 3:05 pm
by chulett
I agree... and done.

Posted: Wed Oct 22, 2014 3:33 pm
by ray.wurlod
Allegedly MKS Toolkit is no longer used by DataStage itself, but is retained for backwards compatibility.

If you have any job, routine or command that relies on "UNIX", then you'll have to keep it.

Otherwise, theoretically, you ought to be able to uninstall it.

To be cautious, get confirmation from IBM Support first.

Posted: Wed Oct 22, 2014 3:48 pm
by chulett
Still curious what the issues are that you may be having...

Posted: Thu Oct 23, 2014 8:03 am
by taylor.hermann
Ok so our issues were on two separate posts.

One being a fifo pipe error randomly while jobs are running:

viewtopic.php?t=153463

Second being that we found whenever the issues occured, sh.exe popped up on our process explorer on the server:

viewtopic.php?t=153484

Now, we finally may have figured our what has caused the problem, after dealing with random, unexplained errors for 5+ months. This included multiple compile crashing and locking jobs, random fifo pipe errors, and a timeout issue.

Apparently a MKS Toolkit file (mkstk.dll) in system32 was showing up as unregistered by windows. And now that we have registered this .dll, everything seems to be running smoothly....

Its funny how the smallest little thing can cause delays from going to production and produce these crazy errors.

Posted: Thu Oct 23, 2014 8:15 am
by chulett
Ah.... THOSE errors. :wink:

So seems like we can mark this particular topic as resolved?