Page 1 of 1
Problem jobs status queued on DataStage 11,5
Posted: Mon Sep 17, 2018 4:06 am
by lthomasjet
Hi
I have a problem on DataStage 11,5
The jobs are a status in queued
The parameter WLMON=1 in a file DSODBConfig.cfg
Thanks
Posted: Mon Sep 17, 2018 4:18 am
by qt_ky
Is this a first-time issue on a newly installed server, perhaps one with very little memory?
Have you looked under the Launchpad in your web browser, Operations Console, under the Workload Management tab where the settings are?
Posted: Mon Sep 17, 2018 4:31 am
by lthomasjet
This server runs well with 2 versions DataStage 8,7 et 11,5
Operations Console, sous l'onglet Workload Management On Director, Designer or Administrator ?
Posted: Mon Sep 17, 2018 5:37 am
by qt_ky
The Launch Pad is a web page.
The URL is usually something like this:
https://hostname:9443/ibm/iis/launchpad/
From there you can launch the Operations Console and find the WLM activity and policy settings.
Your server may be under-powered or overloaded and the default WLM policy thresholds may be too restrictive for your environment.
When jobs get added to the queue, then one or more WLM policies will light up in red as you monitor WLM activity from the Ops Console.
Posted: Mon Sep 17, 2018 6:41 am
by lthomasjet
thanks
My server has already started jobs
where is the default WLM policy thresholds ?
Posted: Mon Sep 17, 2018 4:22 pm
by ray.wurlod
You will find these thresholds in the Workload Management tab of the Operations Console.
Posted: Tue Sep 18, 2018 2:22 am
by lthomasjet
the links are grayed out. I can not see the parameters
Parameter in DSODBConfig.cfg
DSODBON=0
IgnoreLog=IIS-DSTAGE-RUN-I-0180/Attempting to Cleanup after ABORT
IgnoreLog=IIS-DSEE-TFSR-00019/Could not check all operators because of previous error(s)
IgnoreLog=IIS-DSEE-TCOS-00029/Creation of a step finished with status = FAILED.
[OPTIONS FOR RESOURCE MONITORING FOLLOW - DO NOT REMOVE THIS LINE]
WLMON=1
WLM_CONTINUE_ON_COMMS_ERROR=0
WLM_CONTINUE_ON_QUEUE_ERROR=0
WLM_QUEUE_WAIT_TIMEOUT=0
Posted: Tue Sep 18, 2018 5:15 am
by lthomasjet
I created a new queue but without success
Posted: Tue Sep 18, 2018 11:27 pm
by ray.wurlod
I'm pretty sure that DSODBON also needs to be set to 1.
Posted: Wed Sep 19, 2018 12:55 am
by lthomasjet
I have modify a parameter
[xxxxx@xxxxx] # grep DSODB DSODBConfig.cfg
DSODBON=1
How to fix this problem ?
Posted: Wed Sep 19, 2018 3:44 pm
by ray.wurlod
Having changed the parameter, did you stop and re-start the DSAppWatcher services?
Posted: Thu Sep 20, 2018 3:31 am
by lthomasjet
DSAppWatcher services was restarted
I resolve a problem by rebooting the servers