Page 1 of 1
startwlm.cmd (windows)
Posted: Mon Sep 10, 2018 3:08 am
by thurmy34
Hi
This morning all the five jobs launched on the PPD server were stuck in QUEUED status.
I stopped the wml using stopwlm.cmd and restarted it using startwlm.cmd.
The probleme is solved but startwlm.cmd open a window that i can't close wihtout stopping the wlmserver.
So i have to stay connected on the server which is bad.
Any idea to solve this ?
Thank you.
Posted: Mon Sep 10, 2018 6:25 am
by chulett
Sounds like you need the Windows equivalent of the Unix nohup command, something like
this. That or just manage it from the Services control panel object... you can get directly there by running
services.msc from the Start menu.
Posted: Mon Sep 10, 2018 6:35 am
by thurmy34
Hi
What is the name of the service for the wlmserver?
Thank you
Posted: Mon Sep 10, 2018 6:55 am
by chulett
No clue but I can't imagine it would be all that hard to find.
Posted: Mon Sep 10, 2018 7:48 am
by thurmy34
I found this
The workload management process, WLMServer, is automatically started and stopped as part of the DataStage Engine startup.
Maybe there is no service but a process who start with the engine.
Posted: Mon Sep 10, 2018 7:51 am
by chulett
Maybe. I'll have to leave that to others as I've never had the "pleasure" of working with DataStage on a Windows server.
Posted: Mon Sep 10, 2018 8:01 am
by thurmy34
lucky you
Thank you anyway
Posted: Wed Sep 19, 2018 12:27 am
by thurmy34
Hi
The Ibm support tells me that startwlm.cmd is not the best way to start the WLMServer.
It's better to stop the engine and to restart it.
Thank you