MKS Toolkit
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
MKS Toolkit
Please note that DataStage for Windows version 9.1 is not built on MKS Toolkit but, rather, uses direct Windows system calls.
If you've started relying on UNIX commands and you're on Windows, please consider this point as part of your upgrade strategy.
If you've started relying on UNIX commands and you're on Windows, please consider this point as part of your upgrade strategy.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Hello Ray,
I wasn't aware of that; does that mean that jobs don't use a UNIX type fork mechanism anymore?
I wasn't aware of that; does that mean that jobs don't use a UNIX type fork mechanism anymore?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Haven't researched it that deeply yet, but obviously they will have to use some mechanism for spawning processes. Parallel jobs still use processes (rather than threads) when running on Windows. As, indeed, do server jobs.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
The commands stay there....all the convenient stuff is still usable as always.....but the run-time underpinnings have been removed.....except for maybe needing to recompile something, it is a transparent change that is also hoped will increase stability.
Ernie
Ernie
Ernie Ostic
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
Hello all,
I have installed 9.1 client and server on windows 7 64. The InfoSphere Engine Resource Service will not start.
The following is displaced by the service:
"Windows could not start the InfoSphere Engine Resource Service on Local Computer. Error 1075: The dependance services does not exist or has been marked for deletion"
The following is in the windows event log:
"The InfoSphere Engine Resource Service service depends the following service: NuTCRACKERService. This service might not be installed."
It has been written above "Please note that DataStage for Windows version 9.1 is not built on MKS Toolkit but,.."
Is the above true? Do I need to install MKS Toolkit?
Thanks in advance for any help.
I have installed 9.1 client and server on windows 7 64. The InfoSphere Engine Resource Service will not start.
The following is displaced by the service:
"Windows could not start the InfoSphere Engine Resource Service on Local Computer. Error 1075: The dependance services does not exist or has been marked for deletion"
The following is in the windows event log:
"The InfoSphere Engine Resource Service service depends the following service: NuTCRACKERService. This service might not be installed."
It has been written above "Please note that DataStage for Windows version 9.1 is not built on MKS Toolkit but,.."
Is the above true? Do I need to install MKS Toolkit?
Thanks in advance for any help.
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
Information Server 8.5 was compatible with Windows 2003 and 2008, Information Server 8.7 and 9.1 are only compatible with Windows 2008. When IBM was announcing what was new in version 9.1 they believed the removal of MKS emulation would make the product run more efficiently on Windows.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn