DFSMSrmm checks that volumes are labeled correctly and that the volume status and intended usage is acceptable to DFSMSrmm. If you are running DFSMSrmm in protect mode the volume is rejected under these conditions:

• An attempt is made to read a scratch volume.
• An attempt is made to read a volume obtained using the RMM GETVOLUME subcommand and the volume has not yet been written to. You use the RMM GETVOLUME subcommand to request a scratch volume and assign it to an owner defined to DFSMSrmm.
• Bypass label processing (BLP) is being used to write to a scratch or master volume unless you requested BLP processing through EDGRMMxx in the parmlib.
• An attempt is made to read or write to a volume using nonstandard labels, and the volume is defined to DFSMSrmm.
• An attempt is made to overwrite standard labels on a master volume, and the user is not authorized to do so.
• An attempt is made to write standard labels on a master volume that has no labels, and the user is not authorized to do so.
• An attempt is made to overwrite standard labels on a scratch volume by a user that is not authorized to do so.
• A scratch volume is requested for a nonstandard label request. In DFSMSrmm, scratch volumes must have standard labels.
• A volume is in an automated tape library and is defined to DFSMSrmm, but it is defined as not having a standard label or has different internal and external volume labels.
• An attempt is made to read or write to a volume that is waiting to be initialized.
• An attempt is made to read or write to a volume that is pending release.
• An attempt is made to write to a data set on the scratch volume other than the first one.
• An attempt is made to write to a data set that was specified with a sequence number that is not the next in the sequence from the last file DFSMSrmm has recorded. This applies only if DFSMSrmm is recording information about all the data sets on the subject volume.