8464ch09_Oper.fm Draft Document for Review February 7, 2020 3:15 pm – The local cluster is not in a degraded state. The following examples are degraded  states: Out of cache resources Out of physical scratch Note : This override can be enabled independently of the status of the copies in the  cluster. This override causes the local cluster to satisfy the mount request if both of the following  conditions are true: If the local cluster does not have a valid copy of the data, the default cluster selection  criteria applies.  GLYPH<SM590000> Prefer local cache for private mount requests – The cluster is available. – The local cluster includes a valid copy of the data, even if that data is only on physical  tape. GLYPH<SM590000> Force volumes that are mounted on this cluster to be copied to the local cache  GLYPH<SM590000> Enable fewer RUN consistent copies before reporting RUN command complete  GLYPH<SM590000> Ignore cache preference groups for copy priority  When this setting is selected for a private (non-scratch) mount, a copy operation is  performed on the local cluster as part of the mount processing. When this setting is  selected for a scratch mount, the Copy Consistency Point on the specified MC is  overridden for the cluster with a value of Rewind Unload. This override does not change  the definition of the MC, but it does influence the replication policy.  When this setting is selected, the maximum number of RUN copies, including the source,  is determined by the value that is entered at Number of required RUN consistent copies,  including the source copy. This value must be consistent before the RUN operation  completes. If this option is not selected, the MC definitions are used explicitly. Therefore,  the number of RUN copies can be from one to the number of clusters in the grid  configuration or the total number of clusters that are configured with a RUN Copy  Consistency Point. If this option is selected, copy operations ignore the cache preference group when  determining the priority of volumes that are copied to other clusters. Note:  These settings override the default TS7700 behavior and can be different for  every cluster in a grid. Use this window to add, modify, or delete Inhibit Reclaim Schedules that are used to  postpone tape reclamation in a TS7700Tcluster. To change any setting in this window, complete the following steps: a. Select or clear the box next to the setting that must be changed. If the user enables the  Enable fewer RUN consistent copies before reporting RUN command complete option,  the user can alter the value for the Number of required RUN consistent copies  including the source copy. b. Click  Submit Changes Inhibit Reclaim Schedules window  Chapter 9. Configuring and operating the IBM TS7700  489