RE: Restricting a process

Patrick, 

Make sure the full text indexes are set to hourly instead of immediate. 
Very few users
ever need an immediate full text index update on their email database.

That will keep very active databases from consuming all of your CPU. Watch 
the console during
heavy usage to determine which databases are using up all of the CPU. Some 
may have allot of folders
and a Full Text index with attachment indexing. Attachment indexing is 
bad, disable it where possible. 

UPDATE_SUPRESSION_TIME= is the ini variable to Queue the index jobs to 
make it 
more efficient. Indexer is the most CPU intensive job, and is rarely idle. 


Try UPDATE_SUPRESSION_TIME=10

You can also use multiple Update tasks, via the ini variable UPDATERS=X

We run 3 on servers with allot of email databases.

If you want to restrict update or updall at the OS level then you can 
easily create a user class (CRTCLS)
to do so on iSeries for Job Run Priority. We do it here and have set 
Update to a priority of 30, to insure it does
not pin the CPUs. 

You will find a number of posts on CRTCLS it if you search the forum.

Regards, 

Sean