Be careful. Unless you know you have a problem don't make any changes.
The purpose of the change is to allow the XM writes to be executed at the I/O
priority set by XM instead of the priority of the XM process.

We have seen in a few case where the large number of writes issued by a
checkpoint could cause disc contention, so lowering the I/Os priority can
lesson the impact of a checkpoint.

Of course if you have such a high I/O rate that the checkpoint never
completes XM logging will hang and then the system will lock up...



--
         ___
        /  /            Stephen F. Macsisak :Performance Consultant
HEWLETT/hp/PACKARD      Commercial Systems Division
      /__/              [log in to unmask] :(408)447-5851 (or MOONEY N201PC)