SM*ers,

Has anyone ran into the Incrthreshold option problem when a Windows client
deletes a file or directory with a long name, it sometimes reports this
using a compressed name. After the object is deleted, the compressed name
may be reused and the deletion notice may no longer identify a unique
object. During a journaled incremental backup of a file space, this may
result in the no active version response from the server resulting in an
unsuccessful expire for an object.

The default for incrthreshold=0.

Wouldn't it be wise to set it greater than 1 just in case this happens???

Thanks,

Demetrius Malbrough
UNIX/TSM Administrator