Note: TS7760-VEC tape attach configurations must use CISCO switches (16 Gbps)

Remember: The LI REQ option shows only in the bottom of the MI windows for users with the Administrator role, and is not displayed on the host console.

Important: LI REQ commands that are issued from this window are not presented in the host console logs.

Tip: The Systems icon is only visible when the accessed TS7700 Cluster is part of a grid.

Note: If the accessing cluster is a stand-alone cluster, the Cluster Summary window is shown upon login instead.

Note: The number that is shown in parentheses in breadcrumb navigation and cluster labels is always the cluster ID.

Note: Remote cluster fence is enabled only when all clusters in a grid are at R4.1.2 (or later) code level.

Consideration: An existing cluster family cannot be moved within the Cluster Families window.

Remember: Each cluster family must contain at least one cluster. An attempt to save a cluster family that does not contain any clusters results in an error message. No changes are made, and the Cluster Families window remains in edit mode.

If the current state is	Selection	Restrictions and notes
Online	Service Prep	All following conditions must be met first: •The cluster is online. •No other clusters in the grid are in service prep mode. •At least one other cluster must remain online. Caution: If only one other cluster remains online, a single point of failure exists when this cluster state becomes service prep mode. Select Service Prep to confirm this change.
	Force Shutdown	Select Force Shutdown to confirm this change. Important: After a shutdown operation is initiated, it cannot be canceled.
Service Pending	Force Service	Use this option when an operation stalls and is preventing the cluster from entering Service Prep. Select Force Service to confirm this change. All but one cluster in a grid can be placed into service mode, but it is advised that only one cluster be in service mode at a time. If more than one cluster is in service mode, and service mode is canceled on one of them, that cluster does not return to normal operation until service mode is canceled on all clusters in the grid.
	Return to Normal	Select this option to cancel a previous service prep change and return the cluster to the normal online state. Select Return to Normal to confirm this change.
	Force Shutdown	Select Force Shutdown to confirm this change. Important: After a shutdown operation is initiated, it cannot be canceled.
Shutdown (offline)	User interface not available	After an offline cluster is powered on, it attempts to return to normal. If no other clusters in the grid are available, skip hot token reconciliation can be tried.
Online-Pending or Shutdown Pending	Menu disabled	No options to change state are available when a cluster is in a pending state.

Note: After a shutdown or force shutdown action, the targeted cluster (and associated cache) are powered off. A manual intervention is required on site where the cluster is physically located to power it up again.

Remember: Service mode is only possible for clusters that are members of a grid.

Note: On the host side, vary logical drives online on the remaining clusters of the grid to ensure mount points enough for the system to continue operation before setting a cluster in Service mode.

Important: Forcing Service Mode causes jobs that are currently mounted or that use resources that are provided by targeted cluster to fail.

Remember: If more than one cluster is in Service mode, and service is canceled on one of them, that cluster does not return to an online state until Service mode is canceled on all other clusters in this grid.

Note: After a shutdown or force shutdown action, the targeted cluster (and associated cache) are powered off. A manual intervention is required on the site where the cluster is physically located to power it up again.

Attention: A forced shutdown can result in lost access to data and job failure.

Note: For normal situations, set the cluster into service mode before shutdown is always recommendable.

Important: After a shutdown operation is initiated, it cannot be canceled.

Note: Copy and paste might bring in invalid characters. Manual input is preferred.

Tip: The expansion frame icon is displayed only if the accessed cluster includes an expansion frame.

Consideration: If the cluster is not a tape-attached model, the tape library icon does not display on the TS7700 MI.

Detail	Definition
Physical library type - virtual library name	The type of physical library (type is always TS3500) accompanied by the name of the virtual library established on the physical library.
Tape Library Health Fibre Switch Health Tape Drive Health	The health states of the library and its main components. The following values are possible: •Normal •Degraded •Failed •Unknown
State	Whether the library is online or offline to the TS7700.
Operational Mode	The library operational mode. The following values are possible: •Auto •Paused
Frame Door	Whether a frame door is open or closed.
Virtual I/O Slots	Status of the I/O station that is used to move cartridges into and out of the library. The following values are possible: •Occupied •Full •Empty
Physical Cartridges	The number of physical cartridges assigned to the identified virtual library.
Tape Drives	The number of physical tape drives available, as a fraction of the total. Click this detail to open the Physical Tape Drives window.

Note: The Date & Time column refers the time of the events to the local time on the computer where the MI was initiated. If the DATA/TIME is modified in the TS7700 from Coordinated Universal Time during installation, the event times are offset by the same difference in the Events display on the MI. Coordinated Universal Time in all TS7700 clusters should be used whenever possible.

Column name	Description
Date & Time	Date and time the event occurred.
Source	Cluster where the event occurred.
Location	Specific location on the cluster where the event occurred.
Description	Description of the event.
ID	The unique number that identifies the instance of the event. This number consists of the following values: •A locally generated ID, for example: 923 •The type of event: E (event) or T (task) An event ID based on these examples appears as 923E.
Status	The status of an alert or task. If the event is an alert, this value is a fix procedure to be performed or the status of a call home operation. If the event is a task, this value is its progress or one of these final status categories: •Canceled •Canceling •Completed •Completed, with information •Completed, with warning •Failed
System Clearable	Whether the event can be cleared automatically by the system. The following values are possible: •Yes. The event is cleared automatically by the system when the condition that is causing the event is resolved. •No. The event requires user intervention to clear. The event needs to be cleared or deactivated manually after resolving the condition that is causing the event.

To run this task	Action
Deactivate or clear one or more alerts	1. Select at least one but no more than 10 events. 2. Click Mark Inactive. If a selected event is normally cleared by the system, confirm the selection. Other selected events are cleared immediately. A running task can be cleared but if the task later fails, it is displayed again as an active event.
Enable or disable host notification for alerts	Select Actions → [Enable/Disable] Host Notification. This change affects only the accessing cluster. Tasks are not sent to the host.
View a fix procedure for an alert	Select Actions → View Fix Procedure. A fix procedure can be shown for only one alert at a time. No fix procedures are shown for tasks.
Download a comma-separated value (CSV) file of the events list	Select Actions → Download all Events.
View more details for a selected event	1. Select an event. 2. Select Actions → Properties.
Hide or show columns on the table	1. Right-click the table header. 2. Click the check box next to a column heading to hide or show that column in the table. Column headings that are checked display on the table.
Filter the table data	Follow these steps to filter by using a string of text: 1. Click in the Filter field. 2. Enter a search string. 3. Press Enter. To filter by column heading: 1. Click the down arrow next to the Filter field. 2. Select the column heading to filter by. 3. Refine the selection.
Reset the table to its default view	1. Right-click the table header. 2. Click Reset Table Preferences.

Element	Description
Y axes	The left vertical axis measures either throughput (MiBps) or copies (MiB), depending on the selected data sets. The right vertical axis measures the number of mounted virtual drives, reclaimed physical volumes, and data set size to copy. Possible measurements include MiB, GiBs, milliseconds, seconds, hours, and percentage.
X axis	The horizontal axis measures in hours the time period for the data sets shown. Measurements are shown in 15-minute increments by default. Click the time span (located at the top-center of the chart) to change the display increments. The following are the possible values: •1 day •12 hours •1 hour •30 minutes •15 minutes •custom
Last 24 hours	Click the icon in the top right corner of the page to reset the time span that is shown on the chart to the past 24-hour period. A change to the time span does not alter the configuration of data sets displayed in the main area of the chart.
Data sets	Data sets displayed in the main area of the chart are shown as lines or stacked columns.   Data sets related to throughput and copy queues can be grouped to better show relationships between these sets. See Table 9-6 on page 385 for descriptions of all data sets.
Legend	The area below the X axis lists all data sets selected to display on the chart, along with their identifying colors or patterns. The legend displays a maximum of 10 data sets. Click any data set shown in this area to toggle its appearance on the chart.   Note: To remove a data set from the legend, you must clear it using the Select metrics option.
Time span	The time period from which displayed data is drawn. This range is shown at the top of the page.   Note: Dates and times that are displayed reflect the time zone in which your browser is located. If your local time is not available, these values are shown in Coordinated Universal Time (UTC).   Click the displayed time span to modify its start or end values. Time can be selected in 15-minute increments. •Start date and time: The default start value is 24 hours before the present date and time. You can select any start date and time within the 90 days that precede the present date and time. •End date and time: The default end value is 24 hours after the start date or the last valid date and time within a 24-hour period. The end date and time cannot be later than the current date and time. You can select any end date and time that is between 15 minutes and 24 hours later than the start value.
Presets	Click one of the Preset buttons at the top of the vertical toolbar to populate the chart using one of three common configurations:   Throughput: Data sets in this configuration include the following: •Remote Read •Remote Write •Recall from Tape •Write to Tape •Link Copy Out •Link Copy In •Primary Cache Device Read   Throttling: Data sets in this configuration include the following: •Average Host Write Throttle •Average Copy Throttle •Average Deferred Copy Throttle   Copy queue: Data sets in this configuration include the following: •Copy Queue Size   The established time span is not changed when a preset configuration is applied.   Note: The preset options that are available depend on the configuration of the accessing cluster. See Table 9-6 on page 385 for existing restrictions.
Select metrics	Click the Select metrics button on the vertical toolbar to add or remove data sets displayed on the Historical Summary chart. See Table 9-6 on page 385 for descriptions of all data sets.
Download spreadsheet	Click the Download spreadsheet button on the vertical toolbar to download a comma-separated (.csv) file to your web browser for the period shown on the graph. In the .csv file, time is shown in 15-minute intervals.   Note: The time reported in the CSV file is shown in UTC. You might find time differences if the system that you are using to access the Management Interface is configured for a different time zone.
Chart settings	Click the Chart settings button on the vertical toolbar to enable the low graphics mode for improved performance when many data points are displayed. Low graphics mode disables hover-over tool tips and improves chart performance in older browsers. If cookies are enabled on your browser, this setting is retained when you exit the browser.   Note: Low graphics mode is enabled by default when the browser is Internet Explorer, version 8 or earlier.

Metrics section	Metrics category	Data set	Description
Throughput	I/O	Channel R/W MiB/s	Transfer rate (MiBps) of host data on the FICON channel, which includes this information: •Host raw read: Rate that is read between the HBA and host. •Host raw write: Rate that is written to the virtual drive from the host.
Throughput	I/O	Primary Cache Read	Data transfer rate (MiBps) read between the virtual drive and HBA for the primary cache repository.
Throughput	I/O	Primary Cache Write	Data transfer rate (MiBps) written to the primary cache repository from the host through the HBA.
Throughput	I/O	Remote Read	Data transfer rate (MiBps) to the cache of the accessing cluster from the cache of a remote cluster as part of a remote write operation.   This data set is only visible when the accessing cluster is part of a grid.
Throughput	I/O	Remote Write	Data transfer rate (MiBps) to the cache of a remote cluster from the cache of the accessing cluster as part of a remote read operation.   This data set is only visible if the access cluster is part of a grid.
Throughput	Copies	Link Copy Out	Data transfer rate (MiBps) for operations that copy data from the accessing cluster to one or more remote clusters. This is data transferred between legacy TS7700 Grid links.   This data set is only visible if the access cluster is part of a grid.
Throughput	Copies	Link Copy In	Data transfer rate (MiBps) for operations that copy data from one or more remote clusters to the accessing cluster. This is data transferred between legacy TS7700 Grid links. This data set is only visible if the access cluster is part of a grid.
Throughput	Copies	Copy Queue Size	The maximum size of the incoming copy queue for the accessing cluster, which is shown in MiBs, GiBs, or TiBs. Incoming copy queue options include the following: •Immediate •Synchronous-deferred •Immediate-deferred •Deferred •Family deferred •Copy refresh •Time delayed •Total This data set is only visible if the accessing cluster is part of a grid.
Throughput	Copies	Average Copy Life Span	The average age of virtual volumes to be copied to the distributed library for the accessing cluster. The following are the available options: •Immediate Mode Copy •Time Delayed Copy •All other deferred type copies   This data set is only visible if the accessing cluster is part of a grid.
Storage	Cache	Cache to Copy	The number of GiBs that reside in the incoming copy queue of a remote cluster, but are destined for the accessing cluster. This value is the amount of data that is being held in cache until a copy can be made.   This data set is only visible if the accessing cluster is part of a grid.
Storage	Cache	Cache Hit	The number of completed mount requests where data is resident in the TVC.   If two distributed library access points are used to satisfy a mount with synchronous mode copy enabled, this count is advanced only when the data is resident in the TVC for both access points. For this reason, this data set is visible only if the accessing cluster is a TS7700 Tape Attach, or is part of a grid that contains a TS7700 Tape Attach.
Storage	Cache	Cache Miss	The number of completed mount requests where data is recalled from a physical stacked volume.   If two distributed library access points are used to satisfy a mount with synchronous mode copy enabled, this count is advanced when the data is not resident in the TVC for at least one of the two access points. For this reason, this data set is visible only if the accessing cluster is a TS7700 Tape Attach, or is part of a grid that contains a TS7700 Tape Attach.
Storage	Cache	Cache Hit Mount Time	The average time (ms) to complete Cache Hit mounts. This data set is visible only if the accessing cluster is attached to a tape library. If the cache is partitioned, this value is displayed according to partition.
Storage	Cache	Cache Miss Mount Time	The average time (ms) to complete Cache Miss mounts.   This data set is visible only if the accessing cluster is attached to a tape library. If the cache is partitioned, this value is displayed according to partition.
Storage	Cache	Partitions                 Primary Used	If the accessing cluster is a TS7720 or TS7760 attached to a tape library, a numbered tab exists for each active partition. Each tab displays check boxes for these categories: •Cache Hit •Cache Miss, •Mount Time Hit •Mount Time Miss •Data in Cache   The amount of used cache in a partitioned, primary cache, according to partition.   This data set is only visible if the selected cluster is a TS7700T
Storage	Cache	Data Waiting for Premigration	The amount of data in cache assigned to volumes waiting for premigration.   This data set is only visible if the selected cluster is a TS7700T.
Storage	Cache	Data Migrated	The amount of data in cache that has been migrated.   This data set is only visible if the selected cluster is a TS7700T.
Storage	Cache	Data Waiting for Delayed Premigration	The amount of data in cache assigned to volumes waiting for delayed premigration.   This data set is only visible if the selected cluster is a TS7700T.
Storage	Virtual Tape	Maximum Virtual Drives Mounted	The greatest number of mounted virtual drives. This value is a mount count.
Storage	Physical Tape	Write to Tape	Data transfer rate (MiBps) written to physical media from cache. This value typically represents premigration to tape.   This data set is not visible when the selected cluster is not attached to a library.
Storage	Physical Tape	Recall from Tape	Data transfer rate (MiBps) read from physical media to cache. This value is recalled data.   This data set is not visible when the selected cluster is not attached to a library.
Storage	Physical Tape	Reclaim Mounts	Number of physical mounts that are completed by the library for the physical volume reclaim cache operation. This value is a mount count.   This data set is not visible when the selected cluster is not attached to a library.
Storage	Physical Tape	Recall Mounts	Number of physical mounts that are completed by the library for the physical volume reclaim operation.   This data set is not visible when the selected cluster is not attached to a library.
Storage	Physical Tape	Premigration Mounts	Number of physical mount requests completed by the library required to satisfy pre-migrate mounts.   This data set is not visible when the selected cluster is not attached to a library.
Storage	Physical Tape	Physical Drives Mounted	The maximum, minimum, or average number of physical devices of all device types concurrently mounted. The average number displays only when you hover over a data point.   This data set is only visible when the selected cluster attaches to a library.
Storage	Physical Tape	Physical Mount Times	The maximum, minimum, or average number of seconds required to complete the execution of a mount request for a physical device. The average number displays only when you hover over a data point.   This data set is only visible when the selected cluster attaches to a library.
System	Throttling	Average Copy Throttle	The average time delay as a result of copy throttling, which is measured in milliseconds. This data set contains the averages of nonzero throttling values where copying is the predominant reason for throttling.   This data set is only visible if the selected cluster is part of a grid.
System	Throttling	Average Deferred Copy Throttle	The average time delay as a result of deferred copy throttling, which is measured in milliseconds. This data set contains the averages of 30-second intervals of the deferred copy throttle value.   This data set is only visible if the selected cluster is part of a grid.
System	Throttling	Average Host Write Throttle for Tape Attached Partitions	The average write overrun throttle delay for the tape attached partitions. This data set is the average of the non-zero throttling values where write overrun was the predominant reason for throttling.   This data set is only visible if the selected cluster is a TS7720 or TS7760 attached to a tape library.
System	Throttling	Average Copy Throttle for Tape Attached Partitions	The average copy throttle delay for the tape attached partitions. The value presented is the average of the non-zero throttling values where copy was the predominant reason for throttling.   This data set is only visible if the selected cluster is a TS7720 or TS7760 attached to a tape library.
System	Throttling	Average Deferred Copy Throttle for Tape Attached Partitions	The average deferred copy throttle delay for the tape attached partitions. This value is the average of 30-second intervals of the deferred copy throttle value during the historical record.   This data set is only visible if the selected cluster is part of a grid and is a TS7720 or TS7760 attached to a tape library.
System	Utilization	Maximum CPU Primary Server	The maximum percentage of processor use for the primary TS7700 server.
System	Utilization	Maximum Disk I/O Usage Primary Server	The maximum percentage of disk cache I/O uses as reported by the primary server in a TS7700.

Note: This field is visible only if the selected cluster possesses a physical library.

Note: This field is visible only if the selected cluster possesses a physical library.

Note: See 1.6, “Data storage values” on page 12 for information related to the use of binary prefixes.

Tip: Consider limiting the MI user roles who are allowed to change the partition configurations through this window.

Note: The Start Time column refers to the time of starting a task to the local time on the computer where the MI was started. If the DATE/TIME is modified in the TS7700 from the Coordinated Universal Time during installation, the time that is shown in the Start Times field is offset by the same difference from the local time of the MI. Use Coordinated Universal Time in all TS7700 clusters whenever possible.

Considerations: No partition can be created if Resident-Only (CP0) has 2 TB or less of free space. Creating partitions is blocked by a FlashCopy for DR in progress, or by one of the existing partitions being in an overcommitted state.

Note: Currently in R4.2, tape (FC 5273, Tape Attach enablement) and cloud (FC 5278, Enable Cloud Storage Tier) attachment functions are mutually exclusive within a cluster. Nonetheless, a tape attach and a cloud attach cluster can be part of the same grid.

Tip: Consider limiting the MI user roles that are allowed to change the partition configurations through this window.

Column type	Description
Copy Type	The type of copy that is in the queue. The following values are possible: •Immediate: Volumes can be in this queue if they are assigned to a Management Class (MC) that uses the Rewind Unload (RUN) copy mode. •Synchronous-deferred: Volumes can be in this queue if they are assigned to an MC that uses the Synchronous mode copy and some event (such as the secondary cluster going offline) prevented the secondary copy from occurring. •Immediate-deferred: Volumes can be in this queue if they are assigned to an MC that uses the RUN copy mode and some event (such as the secondary cluster going offline) prevented the immediate copy from occurring. •Deferred: Volumes can be in this queue if they are assigned to an MC that uses the Deferred copy mode. •Time Delayed: Volumes can be in this queue if they are eligible to be copied based on either their creation time or last access time. •Copy-refresh: Volumes can be in this queue if the MC assigned to the volumes changed and a LI REQ command was sent from the host to initiate a copy. •Family-deferred: Volumes can be in this queue if they are assigned to an MC that uses RUN or Deferred copy mode and cluster families are being used.
Last TVC Cluster	The name of the cluster where the copy last was in the TVC. Although this might not be the cluster from which the copy is received, most copies are typically obtained from the TVC cluster. This column is only shown when View by Last TVC is selected.
Size	Total size of the queue, which is displayed in GiB. See 1.6, “Data storage values” on page 12 for additional information about the use of binary prefixes. When Copy Type is selected, this value is per copy type. When View by Last TVC is selected, this value is per cluster.
Quantity	The total number of copies in queue for each type.

Tip: This item is not visible on the TS7700 MI if there is no TS7700 tape-attached cluster in grid.

Note: The physical resources are shown in the virtual volume summary, virtual volume details table, or the cluster-specific virtual volume properties table for the TS7720T and TS7740 cluster models.

Volume detail	Description
Volser	The VOLSER of the virtual volume. This value is a six-character number that uniquely represents the virtual volume in the virtual library.
Media Type	The media type of the virtual volume. The following are the possible values: •Cartridge System Tape •Enhanced Capacity Cartridge System Tape
Maximum Volume Capacity	The maximum size (MiB) of the virtual volume. This capacity is set upon insert by the Data Class of the volume.   Note: If an override is configured for the Data Class 's maximum size, it is only applied when a volume is mounted and a load-point write (scratch or fast ready mount) occurs. During the volume close operation, the new override value is bound to the volume and cannot change until the volume is reused. Any further changes to a Data Class override are not inherited by a volume until it is written again during a fast ready mount and then closed.   Note: When the host mounts a scratch volume and unmounts it without completing any writes, the system might report that the virtual volume's current size is larger than its maximum size. This result can be disregarded.
Current Volume Size	Size of the data (MiB) for this unit type (channel or device).   Note: See 1.6, “Data storage values” on page 12 for additional information about the use of binary prefixes.
Current Owner	The name of the cluster that currently owns the latest version of the virtual volume.
Currently Mounted	Whether the virtual volume is currently mounted in a virtual drive. If this value is Yes, these qualifiers are also shown: •vNode: The name of the vNode that the virtual volume is mounted on. •Virtual Drive: The ID of the virtual drive that the virtual volume is mounted on.
Cache Copy Used for Mount	The name of the cluster associated to the TVC selected for mount and I/O operations to the virtual volume. This selection is based on consistency policy, volume validity, residency, performance, and cluster mode.
Mount State	The mount state of the logical volume. The following are the possible values: •Mounted: The volume is mounted. •Mount Pending: A mount request was received and is in progress. •Recall Queued/Requested: A mount request was received and a recall request was queued. •Recalling: A mount request was received and the virtual volume is being staged into tape volume cache from physical tape.
Cache Management Preference Group	The preference level for the Storage Group. This setting determines how soon volumes are removed from cache following their copy to tape. This information is only displayed if the owner cluster is a TS7740 or if the owner cluster is a TS7700T and the volume is assigned to a cache partition that is greater than 0. The following are the possible values: •0: Volumes in this group have preference to be removed from cache over other volumes. •1: Volumes in this group have preference to be retained in cache over other volumes. A “least recently used” algorithm is used to select volumes for removal from cache if there are no volumes to remove in preference group 0. •Unknown: The preference group cannot be determined.
Last Accessed by a Host	The most recent date and time a host accessed a live copy of the virtual volume. The recorded time reflects the time zone in which the user's browser is located.
Last Modified	The date and time the virtual volume was last modified by a host mount or demount. The recorded time reflects the time zone in which the user's browser is located.
Category	The number of the scratch category to which the virtual volume belongs. A scratch category groups virtual volumes for quick, non-specific use.
Storage Group	The name of the Storage Group that defines the primary pool for the premigration of the virtual volume.
Management Class	The name of the Management Class applied to the volume. This policy defines the copy process for volume redundancy.
Storage Class	The name of the Storage Class applied to the volume. This policy classifies virtual volumes to automate storage management.
Data Class	The name of the Data Class applied to the volume. This policy classifies virtual volumes to automate storage management.
Volume Data State	The state of the data on the virtual volume. The following are the possible values: •New: The virtual volume is in the insert category or a non-scratch category and data has never been written to it. •Active: The virtual volume is currently located within a private category and contains data. •Scratched: The virtual volume is currently located within a scratch category and its data is not scheduled to be automatically deleted. •Pending Deletion: The volume is currently located within a scratch category and its contents are a candidate for automatic deletion when the earliest deletion time has passed. Automatic deletion then occurs sometime thereafter.   Note: The volume can be accessed for mount or category change before the automatic deletion and therefore the deletion might be incomplete.   •Pending Deletion with Hold: The volume is currently located within a scratch category configured with hold and the earliest deletion time has not yet passed. The volume is not accessible by any host operation until the volume has left the hold state. After the earliest deletion time has passed, the volume then becomes a candidate for deletion and moves to the Pending Deletion state. While in this state, the volume is accessible by all legal host operations. •Deleted: The volume is either currently within a scratch category or has previously been in a scratch category where it became a candidate for automatic deletion and was deleted. Any mount operation to this volume is treated as a scratch mount because no data is present.
FlashCopy	Details of any existing flash copies. The following are the possible values, among others: •Not Active: No FlashCopy is active. No FlashCopy was enabled at the host by an LI REQ operation. •Active: A FlashCopy that affects this volume was enabled at the host by an LI REQ operation. Volume properties have not changed since FlashCopy time zero. •Created: A FlashCopy that affects this volume was enabled at the host by an LI REQ operation. Volume properties between the live copy and the FlashCopy have changed. Click this value to open the Flash Copy Details page.
Earliest Deletion On	The date and time when the virtual volume will be deleted. Time that is recorded reflects the time zone in which your browser is located. This value displays as “—” if no expiration date is set.
Logical WORM	Whether the virtual volume is formatted as a WORM volume. Possible values are Yes and No.
Compression Method	The compression method applied to the volume.
Volume Format ID	Volume format ID that belongs to the volume. the following are the possible values: •-2: Data has not been written yet •5: Logical Volume old format •6: Logical Volume new format
3490 Counters Handling	3490 Counters Handling value that belongs to the volume.

Property	Description
Cluster	The cluster location of the virtual volume copy. Each cluster location occurs as a separate column header.
In Cache	Whether the virtual volume is in cache for this cluster.
Device Bytes Stored	The number of bytes used (MiB) by each cluster to store the volume. Actual bytes can vary between clusters, based on settings and configuration.
Primary Physical Volume	The physical volume that contains the specified virtual volume. Click the VOLSER hyperlink to open the Physical Stacked Volume Details page for this physical volume. A value of None means that no primary physical copy is to be made. This column is only visible if a physical library is present in the grid. If there is at least one physical library in the grid, the value in this column is shown as “—” for those clusters that are not attached to a physical library.
Secondary Physical Volume	Secondary physical volume that contains the specified virtual volume. Click the VOLSER hyperlink to open the Physical Stacked Volume Details page for this physical volume. A value of None means that no secondary physical copy is to be made. This column is only visible if a physical library is present in the grid. If there is at least one physical library in the grid, the value in this column is shown as “—” for those clusters that are not attached to a physical library.
Copy Activity	Status information about the copy activity of the virtual volume copy. The following are the possible values: •Complete: This cluster location completed a consistent copy of the volume. •In Progress: A copy is required and currently in progress. •Required: A copy is required at this location but has not started or completed. •Not Required: A copy is not required at this location. •Reconcile: Pending updates exist against this location's volume. The copy activity updates after the pending updates get resolved. •Time Delayed Until [time]: A copy is delayed as a result of Time Delayed Copy mode. The value for [time] is the next earliest date and time that the volume is eligible for copies.
Queue Type	The type of queue as reported by the cluster. The following are the possible values: •Rewind Unload (RUN): The copy occurs before the rewind-unload operation completes at the host. •Deferred: The copy occurs some time after the rewind-unload operation completes at the host. •Sync Deferred: The copy was set to be synchronized, according to the synchronized mode copy settings, but the synchronized cluster could not be accessed. The copy is in the deferred state. For more information about synchronous mode copy settings and considerations, see Synchronous mode copy in the Related information section. •Immediate Deferred: A RUN copy that was moved to the deferred state due to copy timeouts or TS7700 Grid states. •Time Delayed: The copy will occur sometime after the delay period has been exceeded.
Copy Mode	The copy behavior of the virtual volume copy. The following are the possible values: •Rewind Unload (RUN): The copy occurs before the rewind-unload operation completes at the host. •Deferred: The copy occurs some time after the rewind-unload operation at the host. •No Copy: No copy is made. •Sync: The copy occurs on any synchronization operation. For more information about synchronous mode copy settings and considerations, see 3.3.5, “Synchronous mode copy” on page 124. •Time Delayed: The copy occurs sometime after the delay period has been exceeded. •Exist: A consistent copy exists at this location, although No Copy is intended. A consistent copy existed at this location at the time the virtual volume was mounted. After the volume is modified, the Copy Mode of this location changes to No Copy.
Deleted	The date and time when the virtual volume on the cluster was deleted. Time that is recorded reflects the time zone in which the user's browser is located. If the volume has not been deleted, this value displays as “—”.
Removal Residency	The automatic removal residency state of the virtual volume. In a TS7700 Tape Attach configuration, this field is displayed only when the volume is in the disk partition. This field is not displayed for TS7740 Clusters. The following are the possible values: •—: Removal Residency does not apply to the cluster. This value is displayed if the cluster attaches to a physical tape library, or inconsistent data exists on the volume. •Removed: The virtual volume has been removed from the cluster. •No Removal Attempted: The virtual volume is a candidate for removal, but the removal has not yet occurred. •Retained: An attempt to remove the virtual volume occurred, but the operation failed. The copy on this cluster cannot be removed based on the configured copy policy and the total number of configured clusters. Removal of this copy lowers the total number of consistent copies within the grid to a value below the required threshold. If a removal is expected at this location, verify that the copy policy is configured and that copies are being replicated to other peer clusters. This copy can be removed only after enough replicas exist on other peer clusters. •Deferred: An attempt to remove the virtual volume occurred, but the operation failed. This state can result from a cluster outage or any state within the grid that disables or prevents replication. The copy on this cluster cannot be removed based on the configured copy policy and the total number of available clusters capable of replication. Removal of this copy lowers the total number of consistent copies within the grid to a value below the required threshold. This copy can be removed only after enough replicas exist on other available peer clusters. A subsequent attempt to remove this volume occurs when no outage exists and replication is allowed to continue. •Pinned: The virtual volume is pinned by the virtual volume Storage Class. The copy on this cluster cannot be removed until it is unpinned. When this value is present, the Removal Time value is Never. •Held: The virtual volume is held in cache on the cluster at least until the Removal Time has passed. When the removal time has passed, the virtual volume copy is a candidate for removal. The Removal Residency value becomes No Removal Attempted if the volume is not accessed before the Removal Time passes. The copy on this cluster is moved to the Resident state if it is not accessed before the Removal Time passes. If the copy on this cluster is accessed after the Removal Time has passed, it is moved back to the Held state.
Removal Time	This field is displayed only if the grid contains a disk-only cluster. Values displayed in this field depend on values displayed in the Removal Residency field. Possible values include: •—: Removal Time does not apply to the cluster. This value is displayed if the cluster attaches to a physical tape library. •Removed: The date and time the virtual volume was removed from the cluster. •Held: The date and time the virtual volume becomes a candidate for removal. •Pinned: The virtual volume is never removed from the cluster. •No Removal Attempted, Retained, or Deferred: Removal Time is not applicable.   The time that is recorded reflects the time zone in which the user's browser is located.
Volume Copy Retention Group	The name of the group that defines the preferred auto removal policy applicable to the virtual volume. This field is displayed only for a TS7700 Cluster or for partition 0 (CP0) on a TS7700 Tape Attach Cluster, and only when the grid contains a disk-only cluster.   The Volume Copy Retention Group provides more options to remove data from a cluster as the active data reaches full capacity. Volumes become candidates for removal if an appropriate number of copies exist on peer clusters AND the volume copy retention time has elapsed.   The Retention Time parameter describes the number of hours a volume remains in cache before becoming a candidate for removal. Retention time is measured beginning at the volume's creation time -- when a write operation was performed from the beginning of a tape -- or at the time the volume was most recently accessed. Volumes in each group are removed in order based on their least recently used access times. If the virtual volume is in a scratch category and resides on a disk-only cluster, removal settings no longer apply to the volume and the volume is a candidate for removal. In this instance, the value that is displayed for the Volume Copy Retention Group is accompanied by a warning icon. Possible values are: •—: Volume Copy Retention Group does not apply to the cluster. This value is displayed if the cluster attaches to a physical tape library. •Prefer Remove: Removal candidates in this group are removed prior to removal candidates in the Prefer Keep group. •Prefer Keep: Removal candidates in this group are removed after removal candidates in the Prefer Remove group are removed. •Pinned: Copies of volumes in this group are never removed from the accessing cluster. The volume copy retention time does not apply to volumes in this group. Volumes in this group that are subsequently moved to scratch become priority candidates for removal.   Caution: Care must be taken when assigning volumes to this group to avoid cache overruns.
Retention Time	The length of time, in hours, that must elapse before the virtual volume named in Volume Copy Retention Group can be removed. Depending on the Volume Copy Retention Reference setting, this time period can be measured from the time when the virtual volume was created or when it was most recently accessed.
Volume Copy Retention Reference	The basis for calculating the time period defined in Retention Time. The following are the possible values: •Volume Creation: Calculate retention time starting with the time when the virtual volume was created. This value refers to the time a write operation was performed from the beginning of a tape. It can be either a scratch mount or a private mount where writing began at record 0. •Volume Last Accessed: Calculate retention time starting with the time when the virtual volume was most recently accessed.
TVC Preference	The group containing virtual volumes that have preference for premigration. This field is displayed only for a TS7740 Cluster or for partitions 1 through 7 (CP1 through CP7) in a TS7720/TS7760 Tape Attach cluster. The following are the possible values: •PG0: Volumes in this group have preference to be premigrated over other volumes. •PG1: Volumes in this group have preference to be premigrated over other volumes. A “least recently used” algorithm is used to select volumes for premigration if there are no volumes to premigrate in preference group 0.
Time-Delayed Premigration Delay	The length of time, in hours, that must elapse before a delayed premigration operation can begin for the virtual volumes designated by the TVC Preference parameter. Depending on the Time-Delayed Premigration Reference setting, this time period can be measured from the time when the virtual volume was created or when it was most recently accessed.
Time-Delayed Premigration Reference	The basis for calculating the time period defined in Time-Delayed Premigration Delay. The following are the possible values: •Volume Creation: Calculate premigration delay starting with the time when the virtual volume was created. This value refers to the time a write operation was performed from the beginning of a tape. It can be either a scratch mount or a private mount where writing began at record 0. •Volume Last Accessed: Calculate premigration delay starting with the time when the virtual volume was most recently accessed.
Storage Preference	The priority for removing a virtual volume when the cache reaches a predetermined capacity. The following are the possible values: •Prefer Remove: These virtual volumes are removed first when the cache reaches a predetermined capacity and no scratch-ready volumes exist. •Prefer Keep: These virtual volumes are the last to be removed when the cache reaches a predetermined capacity and no scratch-ready volumes exist. •Pinned: These virtual volumes are never removed from the TS7700 Cluster.
Partition Number	The partition number for a TS7700 Tape Attach Cluster. Possible values are C0 through C7. “Inserted” logical volumes are those with a -1 partition, meaning that there is no consistent data yet.

Note: You can use the Modify Virtual Volume function to manage virtual volumes that belong to a non-MVS host that is not aware of constructs. MVS hosts automatically assign constructs for virtual volumes, and manual changes are not recommended. The Modify Virtual Volumes window acts on any logical volume belonging to the cluster or grid regardless of the host that owns the volume. The changes that are made on this window take effect only on the modified volume or range after a mount-demount sequence, or by using the LI REQ COPYRFSH command.

Note: Only the unused logical volumes can be deleted through this window, meaning volumes in insert category FF00 that have never been mounted or have had their category, constructs, or attributes modified by a host. Otherwise, those logical volumes can be deleted only from the host.

Tip: To avoid cache overruns, plan ahead when assigning volumes to this group.

Remember: The user can print or download the results of a search query by using Print Report or Download Spreadsheet on the Volumes found table at the end of the Search Results window.

Column name	Description
Categories	The type of category that defines the virtual volume. The following values are valid: •Scratch: Categories within the user-defined private range 0x0001 through 0xEFFF that are defined as scratch. Click the plus sign (+) icon to expand this heading and reveal the list of categories that are defined by this type. Expire time and hold values are shown in parentheses next to the category number. See Table 9-10 for descriptions of these values. •Private: Custom categories that are established by a user, within the range of 0x0001 - 0xEFFF. Click the plus sign (+) icon to expand this heading and reveal the list of categories that are defined by this type. •Damaged: A system category that is identified by the number 0xFF20. Virtual volumes in this category are considered damaged. •Insert: A system category that is identified by the number 0xFF00. Inserted virtual volumes are held in this category until moved by the host into a scratch category. If no defined categories exist for a certain type, that type is not displayed on the Categories table.
Owning Cluster	Names of all clusters in the grid. Expand a category type or number to display. This column is visible only when the accessing cluster is part of a grid.
Counts	The total number of virtual volumes according to category type, category, or owning cluster.
Scratch Expired	The total number of scratch volumes per owning cluster that are expired. The total of all scratch expired volumes is the number of ready scratch volumes.

Tip: The total number of volumes within a grid is not always equal to the sum of all category counts. Volumes can change category multiple times per second, which makes the snapshot count obsolete.

Action	Steps to perform action
Add a scratch category	1. Select Add Scratch Category. 2. Define the following category properties:  – Category: A four-digit hexadecimal number that identifies the category. The valid characters for this field are A - F and 0 - 9. Do not use category name 0000 or “FFxx”, where xx equals 0 - 9 or A - F. 0000 represents a null value, and “FFxx” is reserved for hardware.  – Expire: The amount of time after a virtual volume is returned to the scratch category before its data content is automatically delete-expired1. Select an expiration time from the menu. If the user selects No Expiration, volume data never automatically delete-expires. If the user selects Custom, enter values for the following fields:  • Time: Enter a number in the field according to these restrictions:  1 - 2,147,483,647 if unit is hours   1 - 89,478,485 if unit is days   1 - 244983 if unit is years  • Time Unit: Select a corresponding unit from the menu.  – Set Expire Hold: Check this box to prevent the virtual volume from being mounted or having its category and attributes changed before the expire time has elapsed.2 Checking this field activates the hold state for any volumes currently in the scratch category and for which the expire time has not yet elapsed. Clearing this field removes the access restrictions on all volumes currently in the hold state within this scratch category.
Modify a scratch category	The user can modify a scratch category in two ways: •Select a category on the table, and then, select Actions → Modify Scratch Category. •Right-click a category on the table and either hold, or select Modify Scratch Category from the menu. The user can modify the following category values: •Expire •Set Expire Hold The user can modify one category at a time.
Delete a scratch category	The user can delete a scratch category in two ways: 1. Select a category on the table, and then, select Actions → Delete Scratch Category. 2. Right-click a category on the table and select Delete Scratch Category from the menu. The user can delete only one category at a time.
Hide or show columns on the table	1. Right-click the table header. 2. Click the check box next to a column heading to hide or show that column in the table. Column headings that are checked display on the table.
Filter the table data	Follow these steps to filter by using a string of text: 1. Click in the Filter field. 2. Enter a search string. 3. Press Enter.   Follow these steps to filter by column heading: 1. Click the down arrow next to the Filter field. 2. Select the column heading to filter by. 3. Refine the selection:  – Categories: Enter a whole or partial category number and press Enter.  – Owning Cluster: Enter a cluster name or number and press Enter. Expand the category type or category to view highlighted results.  – Counts: Enter a number and press Enter to search on that number string.  – Scratch Expired: Enter a number and press Enter to search on that number string.
Reset the table to its default view	1. Right-click the table header. 2. Click Reset Table Preferences.

---

Note: There is no cross-check between defined categories in the z/OS systems and the definitions in the TS7700.

Tip: Pools 1 - 32 are preinstalled and initially set to default attributes. Pool 1 functions as the default pool and is used if no other pool is selected.

Important: The reclaim pool that is designated for the Copy Export pool needs to be set to the same value as the Copy Export pool. If the reclaim pool is modified, Copy Export disaster recovery capabilities can be compromised.

Note: You can use identical values in Key Label 1 and Key Label 2, but you must define each label for each key.

Note: Pools 1-32 are preinstalled. Pool 1 functions as the default pool and is used if no other pool is selected. All other pools must be defined before they can be selected.

Important: The reclaim pool designated for the copy export pool should be set to the same value as the copy export pool. If the reclaim pool is modified, copy export disaster recovery capabilities can be compromised.

Note: This control is applied to the reclamation of both sunset and R/W media.

Note: This control is applied to the reclamation of both sunset and R/W media.

Note: This control is applied to the reclamation of both sunset and R/W media.

Note: If the system contains TS1140 or TS1150 tape drives, the system requires at least 15 scratch physical volumes to run reclamation for sunset media.

Note: Your encryption key server software must support default keys to use this option.

Note: You can use identical values in Key Label 1 and Key Label 2, but you must define each label for each key.

Tip: This window is not visible on the TS7700 MI if the grid does not possess a physical library.

Note: JD (ATDD) and JL (ATLE) media types are only available if the highest common format (HCF) is set to E08 or later.

Note: This option applies only to private media, not scratch tapes.

Note: Before a stacked volume with active virtual volumes can be ejected, all active logical volumes in it are copied to a different stacked volume.

Important: When inserting a VOLSER that belongs to a defined tape attach TS7700 range, it is presented and inventoried according to the setup in place. If the newly inserted VOLSER does not belong to any defined range in the TS7700T, an intervention-required message is generated, requiring the user to correct the assignment for this VOLSER. If a physical volume range contains virtual volumes with active data, those virtual volumes must be moved or deleted before the physical volume range can be moved or deleted.

Note: JA and JJ media are supported only for read-only operations with 3592 E07 tape drives. 3592-E08 does not support JA, JJ, or JB media.

Note: JA and JJ media are supported only for read-only operations with 3592 E07 tape drives. 3592-E08 does not support JA, JJ, or JB media.

Note: Only one search can be run at a time. If a search is in progress, an information message displays at the top of the Physical Volume Search window. The user can cancel a search in progress by clicking Cancel Search within this message.

Note: Only one search can be run at a time. If a search is in progress, an information message displays at the top of the Physical Volume Search window. The user can cancel a search in progress by clicking Cancel Search within this message.

Note: The search-in-progress message is displayed on the Physical Volume Search window until the in-progress search completes or is canceled.

Tip: This percentage is a hyperlink; click it to open the Modify Pool Properties window, where the user can modify the percentage that is used for this threshold.

Tip: This window is not visible on the TS7700 MI if the grid does not possess a physical library.

Note: If the user is monitoring this field while changing the encryption status of a drive, the new status does not display until you bring the TS7700 Cluster offline and then back online.

Tip: This window is not visible on the TS7700 MI if the grid does not possess a physical library.

Tip: A value in the Full field is displayed as a hyperlink; click it to open the Active Data Distribution subwindow. The Active Data Distribution subwindow displays a graphical representation of the number of physical volumes per utilization increment in a pool. If no full volumes exist, the hyperlink is disabled.

Consideration: If the cluster does not possess a physical library, the Primary Pool field is not available in the Add or Modify options.

Remember: If the cluster does not possess a physical library, the Secondary Pool field is not available in the Add option.

Note: The default MC cannot be deleted.

Important: Scratch categories and DCs work at the system level and are unique for all clusters in a grid. Therefore, if they are modified in one cluster, they are applied to all clusters in the grid.

Tip: The user can create up to 256 DCs per TS7700 grid.

Note: Although the term InfoCenter is still used in the interface of the product, the term IBM Knowledge Center is the current correct term.

Note: A restore of cluster settings (from a previously taken backup) will not restore or otherwise modify any user, role, or password settings defined by a security policy.

Tip: The Local Policy name is Local and cannot be modified.

Note: If an IBM service representative resets a cluster authentication policy to Local, the Local authentication policy is enabled on all clusters in the grid, regardless of previous LDAP policy setting. Previously enabled LDAP policies are disabled and should be re-enabled following resolution of any LDAP authentication issue.

Important: If this field is blank for an enabled policy, then IBM service representatives must log in using LDAP login credentials obtained from the system administrator. If LDAP server is inaccessible, IBM service representatives cannot access the cluster.

Tip: Passwords for the users are changed from this window also.

Note: The user cannot modify the user name or Group Name. Only the role and the clusters to which it is applied can be modified.

Important: When a Storage Authentication Service policy is enabled for a cluster, service personnel are required to log in with the setup user or group. Before enabling storage authentication, create an account that can be used by service personnel.

Remember: If the Primary or alternative Server URL uses the HTTPS protocol, a certificate for that address must be defined on the SSL Certificates window.

Note: Generally, select the Allow IBM Support options to grant access to the IBM services representative to the TS7700.

Tip: The policy needs to be configured to an LDAP server before being added in the TS7700 MI. External users and groups to be mapped by the new policy are checked in LDAP before being added.

Note: If the user name entered belongs to a user not included on the policy, test results show success, but the result comments show a null value for the role and access fields. Additionally, the user name that entered cannot be used to log in to the MI.

Important: When a Direct LDAP policy is enabled for a cluster, service personnel are required to log in with the setup user or group. Before enabling LDAP authentication, create an account that can be used by service personnel. Also, the user can enable an IBM SSR to connect to the TS7700 through physical access or remotely by selecting those options in the DIRECT LDAP POLICY window.

Note: LDAP external authentication policies are not available for backup or recovery through the backup or restore settings operations. Record it, keep it safe, and have it available for a manual recovery as dictated by the security standards.

Note: Valid characters for the Name of Custom Role field are A-Z, 0-9, $, @, *, #, and %. The first character of this field cannot be a number.

Note: Valid characters for this field are A-Z, 0-9, $, @, *, #, and %. The first character of this field cannot be a number.

Remember: The user can apply the permissions of a predefined role to a custom role by selecting a role from the Role Template menu and clicking Apply. The user can then customize the permissions by selecting or clearing tasks.

Tip: If you are planning to use the same container name, do not delete the original empty container.

Note: A container cannot be created within another container

Note: Any modifications to IP addresses on the accessing cluster interrupt access to that cluster for all current users. If the accessing cluster IP addresses are modified, the current users are redirected to the new virtual address.

Important: Enabling grid encryption significantly affects the performance of the TS7700. System performance can be reduced by 70% or more when grid encryption is enabled.

Note: These settings can be backed up by using the Backup Settings function under Cluster Settings tab and restore them for later use. When the backup settings are restored, new settings are added but no settings are deleted. The user cannot restore feature license settings to a cluster that is different from the cluster that created the ts7700_cluster<cluster ID>.xmi backup file. After restoring feature license settings on a cluster, log out and then log in to refresh the system.

Note: A user with read-only permissions cannot modify the contents of the Destination Settings table.

Tip: A valid IPv4 address is 32 bits long, consists of four decimal numbers, each 0 - 255, separated by periods, such as 98.104.120.12. A valid IPv6 address is a 128-bit long hexadecimal value that is separated into 16-bit fields by colons, such as 3afa:1910:2535:3:110:e8ef:ef41:91cf. Leading zeros can be omitted in each field so that :0003: can be written as :3:. A double colon (::) can be used once per address to replace multiple fields of zeros. For example, 3afa:0:0:0:200:2535:e8ef:91cf” is also 3afa::200:2535:e8ef:91cf”.

Tip: This window is visible only if at least one instance of FC5271 (selective device access control (SDAC)) is installed on all clusters in the grid.

Important: VOLSERs that are not found in the SDAC VOLSER range table use this default group to determine access. The user can modify this group to remove any or all default Library Port IDs. However, if all default Library Port ID values are removed, no access is granted to any volumes not in a defined range.

Note: Access groups and access group ranges are backed up and restored together. For additional information, see “Backup settings” on page 500 and “Restore Settings window” on page 503.

Reminder: The items on this window can modify the cluster behavior regarding local copy and certain I/O operations. Some LI REQUEST commands also can do this action.

Note: This override can be enabled independently of the status of the copies in the cluster.

Note: These settings override the default TS7700 behavior and can be different for every cluster in a grid.

Tip: This window is not visible on the TS7700 MI if the grid does not possess a physical library.

Note: Inhibit Reclaim schedules cannot overlap.

Note: Plan the Inhibit Reclaim schedules carefully. Running the reclaims during peak times can affect production, and not having enough reclaim schedules influences the media consumption.

Note: Only IBM Security Key Lifecycle Manager (SKLM) supports both external disk encryption and TS1140 and TS1150 tape drives. The settings for Encryption Server are shared for both tape and external disk encryption. The IBM Security Key Lifecycle Manager for z/OS (ISKLM) external key manager supports TS7700 physical tape but does not support TS7700 disk encryption.

Note: Some IP addresses (i.e.: 10.x.x.x, 192.168.x.x, 172.16.x.x) are commonly used in local networks (internal use) and should not be propagated through the Internet. If TS7700 and key manager reside in different networks, separated by the Internet, those subnets must be avoided.

Tip: A valid IPv4 address is 32 bits long, consists of four decimal numbers, each 0 - 255, separated by periods, such as 98.104.120.12. A valid IPv6 address is a 128-bit long hexadecimal value separated into 16-bit fields by colons, such as 3afa:1910:2535:3:110:e8ef:ef41:91cf. Leading zeros can be omitted in each field so that :0003: can be written as :3:. A double colon (::) can be used once per address to replace multiple fields of zeros. For example, 3afa:0:0:0:200:2535:e8ef:91cf can be written as: 3afa::200:2535:e8ef:91cf.

Tip: The user can back up these settings as part of the ts7700_cluster<cluster ID>.xmi file and restore them for later use or use with another cluster. If a key server address is empty at the time that the backup is run, when it is restored, the port settings are the same as the default values.

Note: FlashCopy is enabled from LI REQ (Library Request Host Console) command.

Setting	Description
Write Protect State	Displays the status of Write PRotect Mode on the active cluster. The following are the possible values: •Disabled: Write Protect mode is disabled. No Write Protect settings are in effect. •Enabled: Write Protect Mode is enabled. Any host command to modify volume data or attributes by using virtual devices in this cluster will fail, subject to any defined category exclusions. •Write protect for Flash Copy enabled: Write Protect Mode is enabled by the host. The Write Protect for Flash Copy function was enabled through the LI REQ zOS command and a DR test is likely in progress. Important: Write Protect Mode cannot be modified while LI-REQ-initiated write protection for Flash Copy is enabled. User must disable it first by using the LI REQ command before trying to change any Write Protect Mode settings on the TS7700 MI:  – DR family: The name of the disaster recovery (DR) family the Write Protect for Flash Copy was initiated against.  – Flash time: The data and time at which flash copy was enabled by the host. This mimics the time at which a real disaster occurs.
Disable Write Protect Mode	Select this to disable Write Protect Mode for the cluster.
Enable Write Protect Mode	Select this option to enable Write Protect Mode for devices that are associated with this cluster. When enabled, any host command fails if it attempts to modify volume data or volume attributes through logical devices that are associated with this cluster, subject to any defined category exclusions. After Write Protect Mode is enabled through the TS7700 Management Interface, it persists through any outage and can be disabled only through the TS7700 Management Interface. Note: Write Protect Mode can only be enabled on a cluster if it is online and no Write Protect Flash copy is in progress.
Ignore fast ready characteristics of write protected categories	Check this box to permit write protected volumes that were returned to a scratch or a fast ready category to be recognized as private volumes.   When this box is checked, DR test hosts can mount production volumes as private volumes even if the production environment has already returned them to scratch. However, peer clusters, such as production clusters, continue to view these volumes as scratch volumes. This setting does not override the Fast Ready characteristics of excluded categories. 1. When the production environment returns volumes to scratch that are still needed for read operations on a DR test host the user must ensure that the data is available to be read by the DR hosts. To meet this requirement, scratch categories in the production environment can use delete expire hold for a period of time that is long enough to cover the DR test. Otherwise, even if selective write protect is being used on the DR clusters, the data is no longer available to the DR hosts if the production volume is returned to scratch and deleted or reused. One alternative is to avoid running return to scratch processing from the production environment during the DR test. Another alternative in a DR environment that is composed only of TS7700s is to use Flash Copy for DR testing, which is immune to production changes, including any scratch processing, deletion, and reuse. 2. Additionally when this box is checked, if the production host deletes a volume, that volume is also deleted on the DR cluster.

Note: Categories configured and displayed on this table are not replicated to other clusters in the grid.

Important: Backup and restore functions are not supported between clusters operating at different code levels. Only clusters operating at the same code level as the accessing cluster (the one addressed by the web browser) can be selected for Backup or Restore. Clusters operating different code levels are visible, but the options are disabled.

Setting	Can be backed up from	Can be restored to
Storage Classes Data Classes	Any TS7700 cluster	Any TS7700 Cluster
Partitions	TS7720T TS7760T TS7760C	TS7720T or TS7760 T   TS7760C
Inhibit Reclaim Schedule   Physical Volume Pools   Physical Volume Ranges	A TS7700 cluster that is attached to a tape library	A TS7700 cluster that is attached to a tape library
Library Port Access Groups   Categories   Storage Groups   Management Classes   Session Timeout   Account Expirations   Account Lock   Roles and Permissions   Encryption Key Server Addresses   Cluster Network Settings   Feature License Settings   Copy Policy Override   SNMP   Write Protect Mode Categories	Any TS7700 Cluster	Any TS7700 Cluster

Important: A restore operation after a backup of cluster settings does not restore or otherwise modify any user, role, or password settings defined by a security policy.

Note: The user can back up these settings as part of the ts7700_cluster<cluster ID>.xmi file and restore them for later use on the same cluster. However, the user cannot restore feature license settings to a cluster different from the cluster that created the ts7700_cluster<cluster ID>.xmi backup file.

Important: If the user navigates away from this window while the backup is in progress, the backup operation is stopped and the operation must be restarted.

Note: Backup and restore functions are not supported between clusters operating at different code levels. Only clusters operating at the same code level as the current cluster can be selected from the Current Cluster Selected graphic. Clusters operating at different code levels are visible, but not available, in the graphic.

Important: If the backup file was created by a cluster that did not possess a physical library, physical volume pool settings are reset to default.

Note: If the backup file was created by a cluster that did not possess a physical library, the Inhibit Reclaim schedules settings are reset to default.

Important: Changes to network settings affect access to the TS7700 MI. When these settings are restored, routers that access the TS7700 MI are reset. No TS7700 grid communications or jobs are affected, but any current users are required to log back on to the TS7700 MI by using the new IP address.

Note: The user cannot restore feature license settings to a cluster that is different from the cluster that created the ts7700_cluster<cluster ID>.xmi backup file.

Note: The restore operation overwrites existing settings on the cluster.

Important: If the user navigates away from this window while the restore is in progress, the restore operation is stopped and the operation must be restarted.

Note: If this value is a Domain Name Server (DNS) address, then you must activate and configure a DNS on the Cluster Network Settings window.

Note: To send logs to a syslog server, RSyslog must be enabled and the status of the remote target must be Active. Otherwise, no logs will be sent.

In order to...	Do this:
Enable or Disable RSyslog	To change the state, select either Enable RSyslog or Disable RSyslog.
Create a remote target	1. Select Actions → Create Remote Target. 2. Add the remote target settings: IP Address or Hostname Port Status The user can have a total of two remote targets. 3. Click OK to add the remote target, or Cancel to quit the operation.
Modify a remote target	1. Highlight a remote target. 2. Select Actions → Modify Remote Target. 3. Modify the remote target settings: IP Address or Hostname Port Status 4. Click OK to modify the remote target, or Cancel to quit the operation.
Delete a remote target.	1. Highlight a remote target. 2. Select Actions → Delete Remote Target. 3. Click OK to delete the remote target, or Cancel to quit the operation.
Change the order of the remote targets	Click the Target Number column heading.
Hide or show columns on the table	1. Right-click the table header. 2. Select the check box next to a column heading to hide or show that column in the table. Column headings that are selected display on the table.
Reset the table to its default view	1. Right-click the table header. 2. Click Reset Grid Preferences.

Numerical code	Facility	Description
0	kern	Kernel messages
1	user	User-level messages
3	daemon	System daemons
4	auth	Security and authorization messages
5	syslog	Messages generated internally by syslogd
7	news	Network news subsystem
9	cron	Clock daemon
10	security	Security and authorization messages
11	ftp	FTP daemon
12	ntp	NTP subsystem
13	logaudit	Log audit
14	logalert	Log alert
15	clock	Clock daemon
16	local0 (MI_EVENT)	MI EVENTS
17	local1 (X11)	HOST MESSAGES
18	local2 (MDE_CH)	MDE Call Home

Note: The user can modify this field even if a Copy Export operation is running, but the changed value does not take effect until the next Copy Export operation starts.

ID	ID of the Event, Host Message, or Call Home MDE
Custom Severity	Custom severity of the notification. The following are the possible values: •Default •Informational •Warning •Impact •Serious/Error •Critical
Description	Description of the notification.
Type	The type of notification that is listed: Event, Host Message or Call HOME MDE.
Notification State	Whether the notification is active or inactive. If inactive, it will not be sent to any notification channel.
Notification Channels	How the notification is sent, possible selections are: •Host •Management Interface •SNMP •RSyslog   Note: Host Messages cannot be sent to the Management Interface.
Comments	Field available to add user comments. The comments are sent with the message, through the notification channels, when the message is triggered by the system.   Note: Comments for Call Home MDEs will not be sent to Host. Only the MDE code is sent to the Host.

To...	Do this:
Enable or disable host notifications for alerts	1. Select Actions → Modify Host Notification State by Cluster. 2. Select the cluster in the Modify Host Notification State by Cluster box. •Select Active, then OK to enable notifications. •Select Inactive, then OK to disable notifications.
Set notifications to Active or Inactive	1. Select at least one notification. 2. Select Actions → Modify Notifications Settings. •Select Active, then OK to enable notifications. •Select Inactive, then OK to disable notifications.
Set custom severity level for notifications	1. Select at least one notification. 2. Select Actions → Modify Notifications Settings. 3. From the Custom Severity drop-down box, select the severity level. 4. Verify that the Notification State is Active, then click OK. The option to set a custom severity can be performed only if all clusters in the grid are at microcode level 8.41.2 or later.
Modify notification state by severity	1. Select at least one notification. 2. Select Actions → Modify Notifications State by Severity. •Select Active, then OK to enable notifications. •Select Inactive, then OK to disable notifications. This action will work based on the current value of the severity, whether is the default severity or custom severity.
Download a CSV file of the notification settings	Select the File icon (export to CSV).   The time reported in the CSV file is shown in Coordinated Universal Time (UTC).
Hide or show columns on the table	1. Right-click the table header. 2. Click the check box next to a column heading to hide or show that column in the table. Column headings that are checked display on the table.
Filter the table data by using a string of text	1. Click the Filter field. 2. Enter a search string. 3. Press Enter.
Filter the table data by using a column heading	1. Click the down arrow next to the Filter field. 2. Select the column heading to filter by. 3. Refine the selection.
Reset the table to its default view	1. Right-click the table header. 2. click Reset Grid Preferences.

Note: The Copy Export Recover and Copy Export Recover Status options are only available in a single cluster configuration for a tape-attached cluster.

Note: Keep the IP addresses for the clusters in the configuration available for use during a failure of a cluster. Thus, the MI can be accessed from a surviving cluster to initiate the ownership takeover actions.

Important: An IBM SSR must configure the TSSC IP addresses for each cluster in the grid before AOTM can be enabled and configured for any cluster in the grid.

Read/write ownership takeover mode		Read-only ownership takeover mode
Operational clusters in the grid can run these tasks: •Perform read and write operations on the virtual volumes that are owned by the failed cluster. •Change virtual volumes that are owned by the failed cluster to private or SCRATCH status.		Operational clusters in the grid can run these tasks: •Perform read operations on the virtual volumes that are owned by the failed cluster. Operational clusters in the grid cannot run these tasks: •Change the status of a volume to private or scratch. •Perform read and write operations on the virtual volumes that are owned by the failed cluster.
A consistent copy of the virtual volume must be available on the grid or the virtual volume must exist in a scratch category. If no cluster failure occurred (grid links down) and the ownership takeover was started by mistake, the possibility exists for two sites to write data to the same virtual volume.		If no cluster failure occurred, it is possible that a virtual volume that is accessed by another cluster in read-only takeover mode contains older data than the one on the owning cluster. This situation can occur if the virtual volume was modified on the owning cluster while the communication path between the clusters was down. When the links are reestablished, those volumes are marked in error.

Important: The Traceroute command is intended for network testing, measurement, and management. It imposes a heavy load on the network and should not be used during normal operations.

Note: Periods that are covered by TS7700 Log Collection files cannot overlap. If the user attempts to generate a log file that includes a period that is covered by an existing log file, a message prompts the user to select a different value for the hours field.

Note: Data that is collected during this operation is not automatically forwarded to IBM. The user must contact IBM and open a problem management report (PMR) to move manually the collected data off the system.

Important: If data collection is started on a cluster that is in service mode, the user might not be able to check the progress of data collection. The Tasks window is not available for clusters in service mode, so there is no link to it in the message.

Tip: This window is only visible in a single tape-attach cluster.

Reminder: The recovery cluster needs tape drives that are compatible with the exported media. Also, if encrypted tapes are used for export, access to the EKs must be provided.

Important: In a grid configuration, each TS7700 is considered a separate source. Therefore, only the physical volume that is exported from a source TS7700 can be used for the recovery of that source. Physical volumes that are exported from more than one source TS7700 in a grid configuration cannot be combined to use in recovery. Recovery can occur only to a single cluster configuration; the TS7700 that is used for recovery must be configured as Cluster 0.

Note: The number of virtual volumes that can be recovered depends on the number of FC5270 licenses that are installed on the TS7700 that is used for recovery. Additionally, a recovery of more than 2 million virtual volumes must be run by a TS7740 operating with a 3957-V07 and a code level of 8.30.0.xx or higher.

Important: The Copy Export recovery status is only available for a stand-alone TS7700T cluster.

Note: Modem option is no longer offered with the latest TSSC FC 2725. All modem-based call home and remote support was discontinued at the end of 2017.

Note: All inbound connections are subject to the security policies and standards that are defined by the client. When a Storage Authentication Service, Direct Lightweight Directory Access Protocol (LDAP), or RACF policy is enabled for a cluster, service personnel (local or remote) are required to use the LDAP-defined service login. Important: Be sure that local and remote authentication is allowed, or that an account is created to be used by service personnel, before enabling storage authentication, LDAP, or RACF policies.

Note: The AOTM and ECC interfaces should be in different TCP/IP subnets. This setup avoids both communications from using the same network connection.

Note: All authentications are subject to the authentication policy that is in effect, as described in 9.3.9, “The Access icon” on page 465.

Important: Each tape attach TS7700 cluster requires its own logical library in the tape library. The ALMS feature must be installed and enabled to define a logical library partition in both TS3500 and TS4500 tape libraries.

Note: The TS7700 preset is disabled when less than four unassigned tape drives are available to create a logical library.

Note: For the 3592 J1A, E05, E06, and E07 drives, an intermix of tape drive models is not supported by TS7720T or TS7740, except for 3592-E05 tape drives working in J1A emulation mode and 3592-J1A tape drives (the first and second generation of the 3592 tape drives).

Note: Do not share drives belonging to a TS7700T. They must be exclusive.

Note: Do not change drive assignments if they belong to an operating TS7700T, or tape controller. Work with your IBM SSR, if necessary.

Important: In an IBM Z environment, use the Drive Assignment window only for these functions: •Initially assign the tape drives from the TS3500 tape library GUI to a logical partition (LPAR). •Assign more tape drives after they are attached to the TS7740 or a tape controller. •Remove physical tape drives from the configuration after they are physically detached from the TS7740 or tape controller. In addition, never disable ALMS at the TS3500 tape library after it is enabled for IBM Z host support and IBM Z tape drive attachment.

Reminders: Tape drives must be set to Native mode when encryption is used. To activate encryption, FC9900 must be ordered for the TS7740 or the TS7720T, and the license key must be installed. In addition, the associated tape drives must be Encryption Capable 3592-E05, 3592-E06, 3592-E07, or 3592-E08.

Important: Keep the Advanced Encryption Settings as NO ADVANCED SETTING, unless set otherwise by IBM Engineering.

Tip: The CAP does not reassign an already assigned tape cartridge. If needed, you must first unassign it, then manually reassign it.

Important: Before inserting physical volumes belonging to a TS7700T into the tape library, ensure that the VOLSER ranges are defined correctly at the TS7700 MI. For more information, see “Defining VOLSER ranges for physical volumes” on page 542.

Important: Cartridges that are not in a CAP range (TS3500) or associated to any logical library (TS4500) are not assigned to any logical library.

Tip: Only place cartridges in a frame whose front door is open. Do not add or remove cartridges from an adjacent frame.

Note: Make sure that CAP ranges are correctly defined. Insert Notification is not supported on a high-density library. If a cartridge outside the CAP-defined ranges is inserted, it remains unassigned without any notification, and it might be checked in by any logical library of the same media type.

Clarifications: Insert Notification is not supported in a high-density library for TS3500. The CAP must be correctly configured to provide automated assignment of all the inserted cartridges. A cartridge that has been manually assigned to the TS7700 logical library does not display automatically in the TS7700T inventory. An Inventory Upload is needed to refresh the TS7700 cluster inventory. The Inventory Upload function is available on the Physical Volume Ranges menu as shown in Figure 9-98. Cartridge assignment to a logical library is available only through the tape library GUI.

Remember: Cleaning action is performed automatically by the tape libraries when necessary. A cleaning cartridge is good for 50 cleaning actions.

Note: VOLSER Ranges (or CAP) should be correctly assigned at tape library before using the tape library with IBM Z hosts. Native physical volume ranges must fall within ranges that are assigned to IBM Z host logical libraries.

Important: Operator intervention is required to resolve unassigned volumes.

Tip: A tutorial is available in the Physical Volume Pools window to show how to modify encryption properties.

Note: Subroutines of the Automated Read-Only Recovery (ROR) process are started to reclaim space in the physical volumes. Those cartridges are made read-only momentarily during the reclaim process, returning to normal status at the end of the process.

Clarification: Each reclamation task uses two tape drives (source and target) in a tape-to-tape copy function. The TS7700 TVC is not used for reclamation.

Number of available drives	Maximum number of reclaims
3	1
4	1
5	1
6	2
7	2
8	3
9	3
10	4
11	4
12	5
13	5
14	6
15	6
16	7

Tip: The maximum number of Inhibit Reclaim Schedules is 14.

Important: A physical volume pool that is running out of scratch cartridges might stop mounts in the TS7740 or TS7720T tape attach partitions, affecting host tape operations. Mistakes in pool configuration (media type, borrow and return, home pool, and so on) or operating with an empty common scratch pool might lead to this situation.

Priority	Condition	Reclaim schedule honored	Active data threshold% honored	Number of concurrent reclaims	Comments
1	Pool in Panic scratch state	No	No	At least one, regardless of idle drives. If more idle drives are available, more reclaims are started, up to the maximum limit.
2	Priority move	Yes or No	No	At least one, regardless of idle drives. If more idle drives are available, more reclaims are started, up to the maximum limit.	If a volume is within 10 days of a Secure Data Erasure and still has active data on it, it is reclaimed at this priority. An SDE priority move accepts the inhibit reclaim schedule.   For a TS7700 MI-initiated priority move, the option to accept the inhibit reclaim schedule is given to the operator.
3	Pool in Low scratch state	Yes	Yes	At least one, regardless of idle drives. If more idle drives are available, more reclaims are started, up to the maximum limit.	Volumes that are subject to reclaim because of Maximum Active Data, Days Without Access, Age of Last Data Written, and Days Without Data Inactivation use priority 3 or 4 reclamation.
4	Normal reclaim	Yes	Yes, pick from all eligible pools	(Number of idle drives divided by 2) minus 1   8 drv: 3 max 16 drv: 7 max	Volumes that are subject to reclaim because of Maximum Active Data, Days Without Access, Age of Last Data Written, and Days Without Data Inactivation use priority 3 or 4 reclamation.

Tips: A physical drive is considered idle when no activity has occurred for the previous 10 minutes. The Inhibit Reclaim schedule is not accepted by the Secure Data Erase function for a volume that has no active data.

Note: The settings for Encryption Server are shared for both tape and external disk encryption.

Note: Up to 10,000 logical volumes can be inserted at one time. This applies to both inserting a range of logical volumes and inserting a quantity of logical volumes.

Note: The Fast Ready attribute provides a definition of a category to supply scratch mounts. For z/OS, it depends on the definitions. The TS7700 MI provides a way to define one or more scratch categories. A scratch category can be added by using the Add Scratch Category menu.

Tip: Do not add a scratch category by using MI that was previously designated as a private volume category at the host. Categories should correspond to the defined categories in the DEVSUPxx from the attached hosts.

Number of virtual volumes: The addition of all volumes counts that are shown in the Counts column do not always result in the total number of virtual volumes due to some rare, internal categories not being displayed on the Categories table. Additionally, movement of virtual volumes between scratch and private categories can occur multiple times per second and any snapshot of volumes on all clusters in a grid is obsolete by the time a total count completes.

Important: Do not use category name 0000 or FFxx, where xx equals 0 - 9 or A - F. 0000 represents a null value, and FFxx is reserved for hardware.

Note: If No Expiration is selected, volume data never automatically delete-expires.

Tip: Add a comment to DEVSUPnn to ensure that the scratch categories are updated when the category values in DEVSUPnn are changed. They always need to be in sync.

Remember: Scratch categories are global settings within a multi-cluster grid. Therefore, each defined scratch category and the associated Delete Expire settings are valid on each cluster of the grid. The Delete Expired Volume Data setting applies also to disk only clusters. If it is not used, logical volumes that have been returned to scratch are still considered active data, allocating physical space in the TVC. Therefore, setting an expiration time on a disk only TS7700 is important to maintain an effective cache usage by deleting expired data.

Note: The value 0 is not a valid entry on the dialog box for Expire Time on the Add Category page. Use No Expiration instead.

Tip: The client network must use whether IPv4 or IPv6 for all functions, such as MI, key manager server, SNMP, Lightweight Directory Access Protocol (LDAP), and NTP. Mixing IPv4 and IPv6 is not currently supported.

Caution: Enabling grid encryption significantly affects the performance of the TS7700.

Reminder: The items on this window can modify the cluster behavior regarding local copy and certain I/O operations. Some LI REQ commands also can do it.

Note: Scratch mount candidate list as defined in MI (Figure 9-119) is only accepted upon being enabled by using the LI REQ setting.

Note: The Retain Copy mode option is effective only on private (non-scratch) virtual volume mounts.

Clarification: Host writes to the disk only TS7700 cluster and inbound copies continue during this state.

Clarification: New host allocations do not choose a disk only cluster in this state as a valid TVC candidate. New host allocations that are sent to a TS7700 cluster in this state choose a remote TVC instead. If all valid clusters are in this state or cannot accept mounts, the host allocations fail. Read mounts can choose the disk only TS7700 cluster in this state, but modify and write operations fail. Copies inbound to this cluster are queued as Deferred until the disk only cluster exits this state.

State	Enter state (free space available)	Exit state (free space available)	Host message displayed
Automatic removal	< 4 TB	> 4.5 TB	CBR3750I when automatic removal begins
Limited free cache space warning (CP0 for a TS7700 tape attach)	<= 3 TB or <=15% of the size of cache partition 0, whichever is less	>3.5 TB or >17.5% of the size of cache partition 0, whichever is less	CBR3792E upon entering state CBR3793I upon exiting state
Out of cache resources (CP0 for a TS7700 tape attach)	< 1 TB or <= 5% of the size of cache partition 0, whichever is less	> 3.5 TB or >17.5% of the size of cache partition 0, whichever is less	CBR3794A upon entering state CBR3795I upon exiting state
Temporary removal1	<(X + 1 TB)2	>(X + 1.5 TB)b	Console message

---

Note: Logical volumes are only removed if there is another consistent copy within the grid.

Tip: This field is only visible if the selected cluster is a disk only TS7700 in a grid configuration.

Note: The Temporary Removal Threshold is not supported on the TS7740.

Note: The cluster that is elected to initiate Temporary Removal process is not selectable in the list of target clusters for the removal action.

Note: This process does not initiate Service Prep mode.

Note: The Temporary Removal Threshold task ends when the originator cluster enters in Service mode, or the task is canceled on the Tasks page in MI.

Note: Use Coordinated Universal Time in all TS7700 clusters whenever possible.

Tip: Before starting service preparation at the TS7700, all virtual devices on this cluster must be in the offline state with regard to the accessing hosts. Pending offline devices (logical volumes that are mounted to local or remote TVC) with active tasks should be allowed to finish execution and volumes to unload, completing transition to offline state. Virtual devices in other clusters should be made online to provide mount point to new jobs, shifting workload to other clusters in the grid before start service preparation. After scheduled maintenance finishes and TS7700 can be taken out of service, then virtual devices can be varied back online for accessing hosts.

Note: Perform the Inventory Upload from the TS3500 tape library to all TS7700T tape drives that are attached to that tape library whenever a library door is closed, manual inventory or Inventory with Audit is run, or a TS7700 cluster is varied online from an offline state.

Note: By design, the tape attach TS7700 never ejects a cartridge that contains any active data. The requirement to eject a physical cartridge is to move off all active data to another physical cartridge in the same pool, and only then the cartridge can be ejected.

Note: Subroutines of the same Automated ROR process are started to reclaim space in the physical volumes and to perform some MI functions, such as eject or move physical volumes or ranges from the MI. Those cartridges are made read-only momentarily during the running of the function, returning to normal status at the end of the process.

Important: In a TS7700T cluster, only the tape attached partitions are affected.

Important: Repairing a 3592 tape must be done only for data recovery. After the data is moved to a new volume, eject the repaired cartridge from the TS7700 library.

Tip: Always see the appropriate documentation (TS7700 IBM Knowledge Center and MVS System Messages) for the meaning of the messages and the applicable recovery actions.

---