Currently the WF 7.6.11 server has a CPU_LIMIT set at 180 seconds. This is in the ibi\srv76\wfs\bin\edaserve.cfg file. This limit is to stop any run away jobs and does work very well. However, a few jobs do need more CPU time. One option is to run them as ‘deferred’. The deferred jobs have a higher CPU_LIMIT of 300 seconds. This also does work very well.

Here is a portion of the edaserve.cfg file;
SERVICE = DEFAULT
BEGIN
maximum = 40
number_ready = 10
profile = PSLOGIN
agent_refresh = 1
cpu_limit = 180
idle_session_limit = 3600
connection_limit = 7200
END

Now the long running job needs to be run in Report Caster and is subject to the 180 seconds limit. So this limit has been increased, but this effects all programs.

Is there a way to increase the CPU_LIMIT for only special execution userids?

Do I need to create a new special ‘service’ with higher limits, but then how do I control who is using or not using that service?

Looking for options, thanks in advance.

This message has been edited. Last edited by: Kerry,

We have created several Report Caster services. Most have the default user id. We have one that requires userid to be input. Perhaps you can use something like that to control who uses it.

How about having a second configuration with a longer CPU limit, that Report caster uses.