> I am getting ready to implement some client option sets to try and
> standardize options and include/exclude lists. After reading the material
on
> client option sets I have a couple questions:
>
> 1. When I make changes to the client options that a node is set up for, do
I
> need to restart the scheduler service on that node for the changes to take
> effect? Basically, when does the client scheduler service refresh his
> options from the cloptsets?

No restart needed.  CLOPT sets take effect during the next transaction.



> 2. Is there a way through a trace flag or whatever, to get a list of the
> options the client isusing after merging together the cloptsets and
DSM.OPT
> file? I'm especially interested in seeing the include/excludes.

Q INCLEXCL (undocumented but effective)

> 3. If I update a node to use a cloptset, do I need to restart the
scheduler
> service on the client?

No, CLOPTs kick into effect with the next transaction that occurs.