Problem jobs status queued on DataStage 11,5

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
lthomasjet
Participant
Posts: 7
Joined: Mon Sep 17, 2018 4:02 am

Problem jobs status queued on DataStage 11,5

Post 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
LT
qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post 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?
Choose a job you love, and you will never have to work a day in your life. - Confucius
lthomasjet
Participant
Posts: 7
Joined: Mon Sep 17, 2018 4:02 am

Post 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 ?
LT
qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post 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.
Choose a job you love, and you will never have to work a day in your life. - Confucius
lthomasjet
Participant
Posts: 7
Joined: Mon Sep 17, 2018 4:02 am

Post by lthomasjet »

thanks :)

My server has already started jobs
where is the default WLM policy thresholds ?
LT
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You will find these thresholds in the Workload Management tab of the Operations Console.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
lthomasjet
Participant
Posts: 7
Joined: Mon Sep 17, 2018 4:02 am

Post 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
LT
lthomasjet
Participant
Posts: 7
Joined: Mon Sep 17, 2018 4:02 am

Post by lthomasjet »

I created a new queue but without success
LT
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

I'm pretty sure that DSODBON also needs to be set to 1.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
lthomasjet
Participant
Posts: 7
Joined: Mon Sep 17, 2018 4:02 am

Post by lthomasjet »

I have modify a parameter

[xxxxx@xxxxx] # grep DSODB DSODBConfig.cfg
DSODBON=1

How to fix this problem ?
LT
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Having changed the parameter, did you stop and re-start the DSAppWatcher services?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
lthomasjet
Participant
Posts: 7
Joined: Mon Sep 17, 2018 4:02 am

Post by lthomasjet »

DSAppWatcher services was restarted
I resolve a problem by rebooting the servers
LT
Post Reply