Customer has created a PS VB dataset on the volume which is part of a fip /flop Sysres, if this dataset is defined to SSM with a VOL, then SSM takes hold of this volume when it get updated. If this occurs then they delete the object and redefine it again to SSM.
If SSM has fingerprinted a datset on the volume which is part of a fip /flop Sysres then occasionally SSM takes hold of this volume. If this occurs then SSM need to be re-cycled so that the lock can be released.