"is non-zero, an error will be reported if any child component within the supplied object is not locked by the current thread. See datLock.
The object must be locked again, using datLock, before it can be used by any other HDS function. All objects are initially locked by the current thread when they are created.
"is non-zero, then an attempt is made to unlock any component objects contained within the supplied object.
The majority of HDS functions will report an error if the object supplied to the function has not been locked for use by the calling thread. The exceptions are the functions datLock and datLocked.