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

Note: Remember that all authentications are subject to the Authentication policy in effect. See the information under 9.2.8, “The Access icon” on page 526.

Tip: Starting with Release 3.0, a new graphical user interface (GUI) has been implemented. It gives the TS7700 MI a similar look and feel to the XIV and DS8000 management interfaces.

Tip: The following web browsers are supported currently: •Firefox 6.0, 7.0, 10.0, 10.0 ESR, and 13.0 •Internet Explorer 8 and 9

Function	Port	Direction (from library)	Protocol
TS3500 Tape Library Specialist	80	Inbound	TCP/IP
Simple Network Management Protocol (SNMP) traps	161/162	Bidirectional	User Datagram Protocol (UDP)/IP
Encryption Key Manager	1443	Outbound	Secure Sockets Layer (SSL)
Encryption Key Manager	3801	Outbound	TCP/IP

Important: In order to support Japanese input, a Japanese front-end processor needs to be installed on the computer where a web browser is running the MI.

Important: You cannot use the Back or Forward buttons or the Go Back or Go Forward options in your browser to navigate between MI pages.

To perform this task	Action
Return to the main system page from any other page of the MI	Click the home icon in the breadcrumb navigation displayed on the left side of the banner. The main system page is the Cluster Summary if the accessing cluster is a stand-alone cluster, or the Grid Summary if the cluster is part of a grid.
View the same page for a different cluster in a grid	• Hover over the cluster nickname in the breadcrumb navigation. •Click a cluster from the drop-down menu.
Log out of the MI	Select User Name → Log Out.
Change the password associated with the User Name	Select User Name → Change Password. Password rules: •Must be at least six, but no more than 16 alphanumeric characters •Must contain at least one number •First and last characters cannot be numbers •Cannot contain the User Name Note: This menu option is available only if the following conditions are true: •The user has permission to change passwords. •Local Authentication Policy is enabled on the accessing cluster.
View help for the MI page	Select TS7700 Learning &Tutorials.
Launch the TS7700 Customer Information Center	Select Information Center.
View system hardware and software information for this cluster	Select About.

Indicator	Description
Tasks	A clipboard icon containing a check mark, displayed in lower-left corner of the page. Use to determine any running or recently completed long-running tasks. Note: If the accessing cluster is a stand-alone cluster, any tasks shown are for that cluster only. If the accessing cluster is part of a grid, the tasks shown are for the entire grid. A number inside a blue circle is displayed on the clipboard to indicate the total number of running or recently completed tasks: •Hover over the number of tasks to display the three most recently started tasks and their status. •Click a task to open the Tasks page. When a new task starts, completes, or fails, this indicator displays a notification for approximately two seconds.
Events	A clipboard icon containing an X, displayed in lower-right corner of the page. Use to determine active critical and warning events for the grid. Note: This indicator is not displayed if the accessing cluster is a stand-alone cluster. A number inside a yellow circle is displayed on the clipboard to indicate the total number of Warning or Degraded events on the grid.   A number inside a red circle is displayed on the clipboard to indicate the total number of Critical or Failed events on the grid: •Hover over the number of alerts to display the three highest severity events on the grid. •Click an event to open the Events page.   When a new alert arrives, this indicator displays a notification for approximately two seconds.
Physical Cache	Displays physical cache capacity for the accessing cluster using this color scheme: •Green: Cache used •Light green: Available cache •Yellow: Low cache level (within 3 TB cache full level), accompanied by warning icon. This status is shown only on a TS7720 Cluster, since a low cache level is normal for TS7740 Cluster operations. •Red: Out of cache level (within 1 TB cache full level), accompanied by failure icon. This status is shown only on a TS7720 Cluster, since a low cache level is normal for TS7740 Cluster operations. Clicking the Physical Cache indicator will open up the Cache Utilization page.   Hover over the Tape Volume Cache icon to display additional cache information.
Copy Queues	Displays incoming copy queue information for the accessing cluster using this color scheme: •Gray: Queue is empty.       Note: Since copies occur between clusters, this status is shown when the accessing cluster is       a stand-alone cluster. •Blue: Immediate, Deferred, or Family-deferred copies exist in the queue. •Yellow: Synchronous-deferred, Immediate-deferred, or copy refresh copies exist in the queue. •Hover over the indicator to display the three largest queues, ordered by importance. •Click a queue item to open the Copy Queue page.
Health Status	Displays health status of the accessing cluster and any critical or warning events on the cluster. The following color scheme is used: •Green: Normal, no issues exist on the cluster. •Yellow: A warning or degraded event exists. •Orange: A failed event exists. •Red: An unrecoverable event exists.   If multiple events exist, the indicator displays the color corresponding to the most severe active event: •Hover over the indicator to display the top three highest severity events. •Click an event to open the Events page.

To perform this task	Actions
Select options specific to the table	Click Select Action menu.
Sort table results	Click Select Action → Table Actions → Edit Sort or click Edit Sort.
Clear table sort	Click Select Action → Table Actions → Clear All Sorts or click Clear All Sorts or click Reset.
Show or hide filter options; apply filter conditions	Click Select Action → Table Actions → Show/Hide Filter Row or click Show/Hide Filter Row. Refine by entering a Condition or Text values.
Clear filters	Click Select Action → Table Actions → Clear All Filters or click Clear All Filters.
Display or hide columns	1. Click column icon on last table column. 2. In the pop-up list of column names, check columns to be displayed. Clear columns to be hidden. 3. Click Reset Table Preferences to undo changes.   Note: This icon is only visible in some new tables introduced with 8.30.0.xx microcode.
Configure columns	Click Select Action → Table Actions → Configure Columns or click Configure Columns.
Resize a column	Hover over the right edge of the column header until the select arrow becomes a double-arrow resize pointer. When the resize pointer is shown, click and hold the left mouse button and drag the cursor to the right or left.
Print a report of table data	Click Print Report.
Saves a copy of the table data in a comma-separated value (.csv) file to a local directory	Click Download Spreadsheet.

Tip: The Compatibility View is not supported by the TS7700 Virtualization Engine. In the browser menu bar, clear Tools → Compatibility View.

Note: To support Japanese input, a Japanese front-end processor needs to be installed on the computer where a web browser is accessing the MI.

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 panel is shown upon login.

To perform this task	Action
Investigate the details and health of a specific cluster	• Review any Health State icon shown on the lower-right corner of a cluster image. •Hover over a cluster icon to display a description of its health state. •Click a cluster icon to launch the Cluster Summary panel.
Change the order of clusters displayed	Select Order by ID or Order by Family from the Actions menu.
Show or hide cluster family relationships	Select or clear Show Families from the Actions menu.
Change cluster family configurations	Select Cluster Families from the Actions menu.
Change grid nickname or description	Select Modify Grid Identification from the Actions menu.
Change temporary removal threshold settings	Select Temporary Removal Threshold from the Actions menu.
Check host throughput values	Hover over a cluster image to display the Raw Host Throughput window. Click this window to launch the Host Throughput panel.
Check copy queue status for a specific cluster	• When the copy queue bar is shown to the right of the cluster, review displayed queue levels and limits. •Hover over the copy queue bar to display queue details in the Copy Queue window. •Click the Copy Queue window to launch the Incoming Copy Queue panel.
Identify throttling behavior for a specific TS7700 Cluster	Hover over any throttling notification bar displayed beneath the cluster name to display the Throttling Status window. Click the question mark (?) icon in the Throttling Status window to review possible causes and remedies for the throttling behavior.

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

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

Remember: Each cluster family must contain at least one cluster. If you attempt to save changes and a cluster family does not contain any clusters, an error message displays and the Cluster Families window remains in edit mode.

Element	Description
Enable Temporary Thresholds	Check this box and click OK to start the pre-removal process. Clear this box and click OK to abandon a current pre-removal process.
Cluster to be serviced	Select from this drop-down menu the cluster that will be put into service mode. The pre-removal process is started on this cluster. Note: This process does not initiate service prep mode. If the cluster selected from this drop-down menu is a TS7720 Cluster, the cluster is disabled in the TS7720 List since the Temporary Removal Threshold will not be lowered on this cluster.
TS7720 List	This area of the modal window contains each TS7720 cluster in the grid and a text field to set the temporary removal threshold for that cluster.

If the current state is	You can select	Restrictions and notes
Online	Service Prep	All following conditions must first be met: •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	You can select this option if you think that an operation has stalled and is preventing the cluster from entering Service Prep.   Select Force Service to confirm this change. Note: You can place all but one cluster in a grid 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 you cancel service mode on one of them, that cluster will not return to normal operation until service mode is canceled on all clusters in the grid.
	Return to Normal	You can 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, you can skip hot token reconciliation.
Online-Pending or Shutdown Pending	Menu disabled	No options to change state are available when a cluster is in a pending state.

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

Consideration: Although you can place all clusters except one in service mode, the best approach is if only one cluster is in service mode at a time. If more than one cluster is in service mode, and you cancel service mode on one of them, that cluster does not return to normal operation until service mode is canceled on all the clusters.

Note: If the grid contains both TS7720 and TS7740 clusters, you can lower your removal threshold to prevent a TS7720 cluster from running out of cache when the TS7740 clusters are in service. To lower the removal threshold, click TS7720 Lower Removal Threshold when a TS7720 cluster is in the online state.

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

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

Detail	Definition
Cluster identifier	The cluster name followed by the cluster number and distributed library sequence number.
Accessing Cluster	Whether the cluster displayed is the one used to log in to the grid. If these words are absent in the details window, a different cluster in the grid was used when logging in.
Health State	The health of the cluster as a whole. The following values are possible: •Normal •Degraded •Failed •Service •Service Prep •Unknown
Event	Whether an outstanding event exists on the cluster. If a value other than Normal occurs in this field, you can click the icon to launch the Events panel and review details of the event.
Family	The name of the family to which the cluster is assigned.
Model	The cluster model number. The following values are possible: •TS7720 •TS7740
Microcode	The microcode level at which the cluster operates.
Name	The cluster name.
Description	The cluster description.
Disk Encryption	Whether disk encryption is in effect and if so, whether a local or external key manager is in use.

Tip: The expansion frame icon will only be displayed if the accessed cluster has an expansion frame.

Restriction: If the cluster is not a TS7740, the Tape Library icon does not display on the TS7700 Virtualization Engine 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 Virtualization Engine.
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 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 panel.

Operator Intervention: Messages are now displayed under Events with R3.0 MI.

Tip: Notice in Figure 9-28 that the Systems icon only shows up in a grid configuration, and the Cluster Summary item only shows up under Monitor in a stand-alone configuration.

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 these 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 will be cleared automatically by the system when the condition causing the event has been resolved. No. The event requires user intervention to clear. You must clear or deactivate the event manually after resolving the condition causing the event.

To perform 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, you must confirm your selection. Other selected events are cleared immediately. Note: You can clear a running task 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. Note: Tasks are not sent to the host.
View a recommended fix procedure for an alert	Select Actions → View Fix Procedure. Note: 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 additional 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 on the table header. 2. Click Reset Table Preferences.

Column type	Description
Copy Type	The type of copy that resides in the queue. The following values are possible: •Immediate: Volumes can reside in this queue if they are assigned to a Management Class that uses the Rewind Unload (RUN) copy mode. •Synchronous-deferred: Volumes can reside in this queue if they are assigned to a Management Class 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 reside in this queue if they are assigned to a Management Class 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 reside in this queue if they are assigned to a Management Class that uses the Deferred copy mode. •Copy-refresh: Volumes can reside in this queue if the Management Class assigned to the volumes has changed and a LIB REQ command was issued from the host to initiate a copy. •Family-deferred: Volumes can reside in this queue if they are assigned to a Management Class 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 resided in the TVC. Although this might not be the cluster from which the copy is received, the majority of copies are typically obtained from the TVC cluster. Note: This column is only shown when “View by Last TVC” is selected.
Size	Total size of the queue, displayed in GiB. Note: See 1.5, “Data storage values” on page 13 for additional information concerning 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 page is not visible on the TS7700 Virtualization Engine MI if the grid does not possess a physical library.

Column name	Description
Position	The position of the virtual volume in the recall queue. The following values are possible: •In Progress: A recall is in progress for the volume. •Scheduled: The volume is scheduled to be recalled. If optimization is enabled, the TS7700 Virtualization Engine will schedule recalls to be processed from the same physical cartridge. •Position: A number that represents the volume’s current position in the list of volumes that have not yet been scheduled. These unscheduled volumes can be promoted using the Actions menu.
Virtual Volume	The virtual volume to be recalled.
Physical Cartridges	The serial number of the physical cartridge on which the virtual volume resides. This column can be hidden.
Time in Queue	Length of time the virtual volume has been in the queue, displayed in hours, minutes, and seconds as HH:MM:SS. This column can be hidden.

Column name	Description
Address	The virtual drive address takes the format vtdXXXX, where X is a hexadecimal number.
Host Device Number	The device identifier as defined in the attached host. The value in this field does not affect drive operations, but if the host device number is set, it is easier to compare the virtual tape drives to their associated host devices. Follow these steps to add host device numbers: 1. Select one or more virtual tape drives. 2. Select Assign Host Device Numbers from the Actions menu. 3. Enter the host device address that you want assigned to the first virtual tape drive. Host device numbers are added to subsequent virtual tape drives incrementally.
Mounted Volume	The volume serial number (VOLSER) of the mounted virtual volume.
Previously Mounted Volume	The VOLSER of the virtual volume mounted on the drive prior to this one.
Status	The role that the drive is performing. The following values are possible: Idle: The drive is not in use. Read: The drive is reading a virtual volume. Write: The drive is writing a virtual volume. This column is blank if no volume is mounted.
Time on Drive	The elapsed time that the virtual volume has been mounted on the virtual tape drive. This column is blank if no volume is mounted.
Cache Mount Cluster	The TVC cluster performing the mount operation. If a synchronous mount exists, this field displays two clusters. This column is blank if no volume is mounted.
Online	Whether the mounting virtual tape drive is online.
Bytes Read	Amount of data read from the mounted virtual volume. This value is shown as Raw KiB (Compressed KiB).
Bytes Written	Amount of data that was written to the mounted virtual volume. This value is shown as Raw KiB (Compressed KiB).
Virtual Block Position	The position of the drive on the tape surface in a block number, as calculated from the beginning of the tape. This value is displayed in hexadecimal form. When a volume is not mounted, this value is 0x0.
Stand-alone Mount	Whether the virtual drive is a stand-alone mount, which means that the mount request is initiated by the cluster and not the host. Follow these steps to mount a virtual volume: 1. Select a volume. 2. Select Stand-alone Mount from the Actions menu. Note: You can only mount virtual volumes not already mounted, on a drive that is online. Follow these steps to unmount a virtual volume: 1. Select a mounted volume. 2. Select Unmount from the Actions menu. Note: You can unmount only those virtual volumes that are mounted and have a status of Idle.

Note: If the cluster does not possess a physical library, physical resources are not shown in the virtual volume summary, virtual volume details table, or the cluster-specific virtual volume properties table.

Removal Residency state		Removal Time indicator
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		“—” The Removal Time field is not applicable.

Note: If the cluster contains a physical library, Removal Residency does not apply and this field displays a value of “—”.

Important: Care must be taken when assigning volumes to this group to avoid cache overruns.

Important: This function is only for non-MVS hosts.

Important: A volume can only be deleted from the insert category if the volume has never been moved out of the insert category after initial insert and has never received write data from a host.

Tip: Only one search can be executed at a time. If a search is in progress, an information message will occur at the top of the Virtual Volumes Search window. You can cancel a search in progress by clicking Cancel Search.

Hexadecimal value	Category
0001 - FEFF	General programming use
FF00	Insert
FF01	Insert for Virtual Tape Server (VTS) stacked volumes
FF03	Scratch for VTS stacked volumes
FF04	Private for VTS stacked volumes
FF05	Disaster recovery for VTS stacked volumes
FF06	Disaster recovery for VTS stacked volumes
FF08	VTS stacked volume internal label is unreadable
FF09	Temporary category used by the VTS
FF10	Convenience eject
FF11	High-capacity eject
FF12	Export pending volumes
FF13	Exported volumes
FF14	Import volumes
FF15	Import pending volumes
FF16	Unassigned volumes (VTS import)
FF17	Export-hold volumes
FF20	Volume with corrupted tokens (peer-to-peer VTS usage only)
FFF4	Cleaner volume (Enterprise Tape Cartridge (ETC))
FFF5	Service volume (ETC)
FFF6	Service volume (High Performance Cartridge Tape (HPCT)/Extended High Performance Cartridge Tape (EHCPT))
FFF9	Service volume (Cartridge System Tape (CST)/Enhanced Capacity Cartridge System Tape (ECCST)
FFFA	Manually ejected
FFFD	Cleaner volume (HPCT/EHPCT)
FFFE	Cleaner volume (CST/ECCST)
FFFF	VOLSER specific

Tip: Plan when assigning volumes to this group to avoid cache overruns.

Remember: You can print or download the results of a search query using “Print Report” or “Download Spreadsheet” on the Volumes found: table at the end of the Search Results window, as shown in Figure 9-49 on page 483.

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 (Fast Ready). Click the plus sign (+) icon to expand this heading and reveal the list of categories defined by this type. Expire time and hold values are shown in parentheses next to the category number. See Table 9-16 for descriptions of these values. •Private: Custom categories 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 defined by this type. •Damaged: A system category identified by the number 0xFF20. Virtual volumes in this category are considered damaged. •Insert: A system category 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. Some internal categories do not show in the table. Also, volumes can change category multiple times per second, what 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 (Fast Ready) category before its data content is automatically delete-expired. Select an expiration time from the drop-down menu. If you select No Expiration, volume data never automatically delete-expires. If you select Custom, enter values for the following fields:  • Time: Enter a number in the text field according to these restrictions:  1 - 32,767 if unit is hours   1 - 1,365 if unit is days   1 - 195 if unit is weeks  • Time Unit: Select a corresponding unit from the drop-down 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. Checking this field activates the hold state for any volumes currently in the scratch (Fast Ready) 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 (Fast Ready) category.
Modify a scratch category	You can modify a scratch category in two ways: •Select a category on the table, and then, select Actions → Modify Scratch Category. •Right-click on a category on the table and either hold, or select Modify Scratch Category from the pop-up menu. You can modify the following category values: •Expire •Set Expire Hold You can modify one category at a time.
Delete a scratch category	You 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 pop-up menu. You 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 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.

Tip: Pools 1 - 32 are preinstalled. Pool 1 functions as the default pool and will be 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 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.

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

Note: JC (EATC) and JK (EAETC) media types are only available if the highest common format (HCF) is set to E07 or higher.

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

Tip: When inserting a VOLSER that belongs to a defined TS7740 range, it will be presented and inventoried according to the setup in place. If the newly inserted VOLSER does not belong to any defined range in the TS7740, an intervention-required message is generated, requiring the user to correct the assignment for this VOLSER.

Important: 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 only supported for read-only operations with 3592 E07 Tape Drives.

Note: JA and JJ media are only supported for read-only operations with 3592 E07 Tape Drives.

Note: Only one search can be executed at a time. If a search is in progress, an information message displays at the top of the Physical Volume Search page. You can cancel a search in progress by clicking “Cancel Search” within this message.

Note: Only one search can be executed at a time. If a search is in progress, an information message displays at the top of the Physical Volume Search page. You 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 page until the in-progress search completes or is canceled.

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

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

Note: If you are monitoring this field while changing the encryption status of a drive, the new status will not display until you bring the TS7700 Cluster offline and then return it to an online state.

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

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

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

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

Remember: If the cluster does not possess a physical library, the Secondary Pool field will not be available in the Modify option.

Restriction: You will not be permitted to delete the default Management Class.

Tip: You can create up to 256 Storage Classes per TS7700 Virtualization Engine Grid.

Important: Scratch (Fast Ready) categories and Data Classes work at the system level and are unique for all clusters in a grid. Therefore, if you modify them on one cluster, they will be applied to all clusters in the grid.

Tip: You can create up to 256 Data Classes per TS7700 Virtualization Engine Grid.

Note: Before Release 3.0 (from R1.6 to R2.1), RBAC policies only applied to the MI.

Important: Before enabling Storage Authentication or Direct LDAP policies, create an account that can be used by service personnel (local and remote).

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

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

Restriction: You cannot modify the Username 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 Alternate Server URL uses the HTTPS protocol, a certificate for that address must be defined on the SSL Certificates page.

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 actually added.

Note: If the User Name entered belongs to a user not included on the policy, test results will show success but the result comments will show a null value for the role and access fields. Additionally, the User Name 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.

Note: LDAP external authentication policies 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 recommended by your security standards.

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

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 Virtualization Engine. System performance can be reduced by 70% or more when grid encryption is enabled.

Note: You can back up these settings as part of the ts7700_cluster<cluster ID>.xmi file and restore them for later use. When the backup settings are restored, new settings are added but no settings are deleted. You cannot restore feature license settings to a cluster different than the cluster that created the ts7700_cluster<cluster ID>.xmi backup file. After you restore feature license settings on a cluster, it is suggested that you 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 ranging from 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” is also “3afa::200:2535:e8ef:91cf”.

Note: Any change to SNMP settings is logged on the Tasks page.

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

Important: VOLSERs not found in the Selective Device Access Control (SDAC) VOLSER range table use this default group to determine access. You 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 572 and “Restore Settings page” on page 575.

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

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

Tip: This page is not visible on the TS7700 Virtualization Engine 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 your production, and not having enough reclaim schedules will influence your media consumption.

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

Note: Your Encryption Key Server software must support default keys to use this option.

Note: You 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 performed, when it is restored, the port settings are the same as the default values.

Tip: A valid IPv4 address is 32 bits long, consists of four decimal numbers, each ranging from 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.

Note: You can add up to 16 categories per cluster; however, you cannot add, modify, or delete categories if one or more clusters in the grid are operating at a code level of 8.6.0.xx or lower.

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 options are greyed out.

Note: If the cluster does not possess a physical library, physical volume pools will not be available.

Note: If the cluster does not possess a physical library, the Inhibit Reclaim Schedules option will not be available.

Note: This setting is only available if all clusters in the grid are operating with microcode levels of 8.20.0.xx or higher and the SDAC feature is installed.

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

Note: You 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, you cannot restore feature license settings to a cluster different than the cluster that created the ts7700_cluster<cluster ID>.xmi backup file.

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

Important: If you navigate away from this page 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 grayed out, in the graphic.

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

Important: Management Class settings are related to the number and order of clusters in a grid. Take special care when restoring this setting. If a Management Class is restored to a grid having more clusters than the grid had when the backup was performed, the copy policy for the new cluster or clusters will be set as No Copy. If a Management Class is restored to a grid having fewer clusters than the grid had when the backup was performed, the copy policy for the now-nonexistent clusters will be changed to No Copy. The copy policy for the first cluster will be changed to RUN to ensure that one copy exists in the cluster.

Note: If the backup file was created by a cluster that did not define one or more scratch mount candidates, the default scratch mount process is restored. The default scratch mount process is a random selection routine that includes all available clusters. Management Class scratch mount settings can be modified after the restore operation completes.

Note: If this setting is selected and the cluster does not support logical Write Once Read Many (LWORM), the Logical WORM setting is disabled for all Data Classes on the cluster.

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.

Note: This setting is only available if all clusters in the grid are operating with microcode levels of 8.20.0.xx or higher.

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

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

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 using the new IP address.

Note: You cannot restore feature license settings to a cluster different than the cluster that created the ts7700_cluster<cluster ID>.xmi backup file.

Note: The restore operation will overwrite existing settings on the cluster.

Important: If you navigate away from this page while the restore is in progress, the restore operation is stopped and the operation must be restarted.

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

Note: Do not attempt ownership takeover if the communication path between clusters has failed but no clusters are in a failed state. The integrity of the virtual volumes in the grid can be compromised if a takeover mode is enabled for a cluster that is not actually in a failed state.

Read/write ownership takeover mode		Read-only ownership takeover mode
Operational clusters in the grid can perform these tasks: •Perform read and write operations on the virtual volumes owned by the failed cluster. •Change virtual volumes owned by the failed cluster to private or SCRATCH status.		Operational clusters in the grid can perform these tasks: •Perform read operations on the virtual volumes owned by the failed cluster. Operational clusters in the grid cannot perform these tasks: •Change the status of a volume to private or scratch. •Perform read and write operations on the virtual volumes 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 invoked 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 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 will be marked in error.

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.

Note: If a remote cluster has failed and no other clusters in the grid have taken ownership of its virtual volumes, information for that cluster occurs in bold text, sorted to appear at the top of the table.

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

Note: Time periods covered by TS7700 Log Collection files cannot overlap. If you attempt to generate a log file that includes a time period covered by an existing log file, a message prompts you to select a different value for the hours field.

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

Important: If you start data collection on a cluster in service mode, you may not be able to check the progress of data collection. Tasks page is not available for clusters in service mode; consequently there is no link to it in message.

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

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

Note: The number of virtual volumes that can be recovered is dependent on the number of FC5270 licenses installed on the TS7700 Virtualization Engine used for recovery. Additionally, a recovery of more than two million virtual volumes must be performed by a TS7740 Virtualization Engine 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 in a single cluster configuration for a TS7700 grid.

Important: ALMS is a requirement for IBM System z attachment. ALMS is always installed and enabled in a TS7700 Virtualization Engine z/OS environment. Therefore, automatic cleaning is enabled.

Tip: If virtual I/O slots are enabled, your library automatically imports cleaning cartridges.

Restriction: DFSMS and MVS commands apply only to storage management subsystem (SMS)-defined libraries. The library name defined during the definition of a library in Interactive Storage Management Facility (ISMF) is required for “libname” in the DFSMS commands.

Clarification: This command does not change the operational mode of the TS3500 Tape Library itself. It only applies to the SMS-defined logical libraries.

Clarification: The specified keywords must be from one to eight characters in length and can consist of alphanumeric characters (A - Z and 0 - 9) and the national character set ($*@#%). A keyword cannot contain any blanks. The only checking performed by the host is to verify that the specified keywords conform to the supported character set. The validity of the keywords themselves and the keywords in combination with each other is verified by the TS7700 Virtualization Engine processing the command.

Keyword1	Keyword2	Keyword3	Keyword4	Description	Comp. Lib.	Dist. Lib.	TS772 or TS7740
CACHE				Requests information about the current state of the cache and the data managed within it associated with the specific distributed library.	N/A	Y	Both
COPY	ACTIVITY	See the User’s Guide		Requests information about Active Copy jobs.	N/A	Y	TS7720
COPY	SUMMARY			Requests information about all the copy jobs.	N/A	Y	Both
COPYEXP	volser	RECLAIM		Requests that the specified physical volume that has been exported previously in a Copy Export operation be made eligible for priority reclaim.	N/A	Y	TS7740
COPYEXP	volser	DELETE		Requests that the specified physical volume that has been exported previously in a Copy Export operation be deleted from the TS7700 Virtualization Engine database. The volume must be empty.	N/A	Y	TS7740
GRIDCNTL	COPY	DISABLE		Requests that copy operations for the specified distributed library be disabled. Copies that are in progress are allowed to complete, but no new copies using the specified distributed library as the source or target are initiated.	N/A	Y	Both
GRIDCNTL	COPY	ENABLE		Requests that copy operations for the specified distributed library be enabled. Copy operations can again use the specified distributed library as the source or target for copies.	N/A	Y	Both
LVOL	volser			Requests information about a specific logical volume.	Y	N/A	Both
LVOL	volser	PREFER MIGRATE REMOVE REMOVE REMOVE	PROMOTE INFO	Requests a change in the cache management for a logical volume.	N/A N/A   N/A N/A N/A	Y Y   Y Y Y	Both TS7740   TS7720 TS7720 TS7720
LVOL	volser	COPY	KICK FORCE	Kick requests to move a logical volume to the front of the copy queue. Force puts a copy job against a removed logical volume and promotes it to the front of the copy queue. It is useful when it is required to get a removed volume back into a TS7720 by copying it from another consistent cluster.	N/A	Y	Both
PDRIVE				Requests information about the physical drives and their current usage associated with the specified distributed library.	N/A	Y	TS7740
POOLCNT	00-32			Requests information about the media types and counts, associated with a specified distributed library, for volume pools beginning with the value in keyword2.	N/A	Y	TS7740
PVOL	volser			Requests information about a specific physical volume.	N/A	Y	TS7740
RECALLQ	volser			Requests the content of the recall queue starting with the specified logical volume. Keyword2 can be blank.	N/A	Y	TS7740
RECALLQ	volser	PROMOTE		Requests that the specified logical volume be promoted to the top of the recall queue.	N/A	Y	TS7740
RRCLSUN	ENABLE DISABLE STATUS			In response to the RRCLSUN request, the cluster associated with the distributed library will enable, disable, or display the current status of the force residency on recall feature. The TS7700 has a resident on recall function to accelerate format change to the newest media.	N/A	Y	TS7740
SETTING	ALERT, CACHE, THROTTLE DEVALLOC RECLAIM CPYCNT	See “Overview of the Host Console SETTING request” on page 607	See “Overview of the Host Console SETTING request” on page 607	Settings to control functions in the grid.	N/A	Y	See “Overview of the Host Console SETTING request” on page 607
STATUS	GRID			Requests information about the copy, reconcile, and ownership takeover status of the libraries in a grid configuration.	Y	N/A	Both
STATUS	GRIDLINK			Requests information about the status and performance of the links between the TS7700 Virtualization Engines in the grid configuration.	N/A	Y	Both
COPYRFSH	volser	See the User’s Guide	See the User’s Guide	Refresh copy policy and queue a copy job on the copy target clusters without mounting or dismounting a volume.	N/A	Y	Both
GNACNTL	ENABLE DISABLE STATUS	See the User’s Guide	See the User’s Guide	Request to change TS7700 internal TCP algorithm on grid links.	N/A	Y	Both
OTCNTL	CONFIG DIST START STOP STAT	See the User’s Guide	See the User’s Guide	Request to move the ownership of the logical volumes in the background.	N/A	Y	Both

Important: This command can change several settings on a specified TS7700, which can potentially modify the known behavior of this cluster. If this resource is shared by different clients or environments, a previous agreement is advisable between administrators.

Remember: All settings are persistent across machine restarts, service actions, or code updates. The settings are not carried forward as part of disaster recovery from copy-exported tapes or the recovery of a system.

Remember: For messages where a variable is included (the setting), the value returned is left-aligned without leading zeroes or right padding, for example: AL5000 Uncopied data of 1450 GB above high warning limit of 1050 GB.

Keyword3	Keyword4	Description
COPYHIGH	value	Uncopied Data High Warning Limit This is the threshold, in GBs of data in cache, that needs to be copied to other TS7700 Virtualization Engines in a grid configuration, at which point the TS7700 Virtualization Engine will generate a message indicating that the amount of uncopied data has exceeded a high warning limit. For this message to be generated, the amount of uncopied data must be above the value specified in keyword4 for 150 seconds. As long as the amount of uncopied data remains above the threshold, the above warning limit message is repeated every 15 minutes. If the message has been generated and the amount of uncopied data is at or falls below that threshold for 150 seconds, a message is generated indicating that the amount of uncopied data is below the high warning limit. The default value is 0, which indicates no warning limit is set and no messages are to be generated. A value greater than the enabled cache size less 500 GB cannot be set. If a value is specified that is not 500 GB lower than the enabled cache size, the threshold is set to the enabled cache size less 500 GB. A value less than 100 GB cannot be set. If a value is specified that is not 100 GB or greater, the threshold is set to 100 GB. If the uncopied data low warning limit is not zero and a value is specified that is not 100 GB greater than the uncopied data low warning limit, the uncopied data low warning limit will be changed so that it is 100 GB less than the value specified (but never lower than 0). The message text is shown (xxxxxxxx is the amount of uncopied data, and yyyyyyyy is the threshold): •When above the threshold: AL5000 Uncopied data of xxxxxxxx GB above high warning limit of yyyyyyyy GB. •When below the threshold: AL5001 No longer above uncopied data high warning limit of yyyyyyyy GB.
COPYLOW	value	Uncopied Data Low Warning Limit This is the threshold, in GBs of data, in cache that needs to be copied to other TS7700 Virtualization Engines in a grid configuration, at which the TS7700 Virtualization Engine will generate a message indicating that the amount of uncopied data has exceeded a low warning limit. For this message to be generated, the amount of uncopied data must be above the value specified in keyword4 for 150 seconds.   If the message has been generated and the amount of uncopied data is at or falls below that threshold for 150 seconds, a message is generated indicating that the amount of uncopied data is below the low warning limit.   The default value is 0, which indicates no warning limit is set and no messages are to be generated.   If the uncopied data high warning limit is set to 0, the uncopied data low warning limit cannot be set to a value greater than the enabled cache size less 500 GB or to a value less than 100 GB. If a value is specified that is not 500 GB lower than the enabled cache size, the threshold is set to the enabled cache size less 500 GB. If a value is specified that is less than 100 GB, the threshold is set to 100 GB.   If the uncopied data high warning limit is not zero, the uncopied data low warning limit cannot be set to a value greater than the uncopied data high warning limit less 100 GB. If a value is specified that is not 100 GB lower than the uncopied data high warning limit, the threshold is set to the uncopied data high warning limit less 100 GB (but never lower than 0).   The message text is shown (xxxxxxxx is the amount of uncopied data, and yyyyyyyy is the threshold): •When above the threshold: AL0000 Uncopied data of xxxxxxxx GB above low warning limit of yyyyyyyy GB. •When below the threshold: AL0001 No longer above uncopied data low warning limit of yyyyyyyy GB.
PDRVCRIT	value	Available Physical Drive Critical Warning Limit This is the threshold, in number of physical drives, at which the TS7700 Virtualization Engine will generate a message indicating that the number of available physical drives has fallen below the critical warning limit. For this message to be generated, the number of available physical drives must be below the value specified in keyword4 for 15 minutes.   As long as the number of available physical drives is below the threshold, the “below the threshold” message is repeated every 15 minutes. If the message has been generated and the number of available physical drives is at or has risen above that threshold for 15 minutes, a message is generated indicating that the number of available physical drives is above the critical warning limit.   The default value is 0, which indicates no warning limit is set and no messages are to be generated.   A value greater than the number of installed physical drives minus 1 cannot be set. If a value is specified that is greater than the number of installed physical drives minus 1, the threshold is set to the number of installed physical drives minus 1. A value less than 3 cannot be set. If a value is specified that is less than 3, the threshold is set to 3.   If the available physical drive low warning limit is not zero and a value is specified that is not 1 less than the available physical drive low warning limit, the available physical drive low warning limit will be changed so that it is 1 more than the value specified (but never more than the number of installed physical drives).   The message text is shown (xx is the number of available drives, and yy is the threshold): •When fallen below the threshold: AL5004 Available physical drives of xx is below critical limit of yy. •When risen above the threshold: AL5005 Available physical drives no longer below critical limit of yy.
PDRVLOW	value	Available Physical Drive Low Warning Limit This is the threshold, in number of physical drives, at which the TS7700 Virtualization Engine will generate a message indicating that the number of available physical drives has fallen below the low warning limit. For this message to be generated, the number of available physical drives must be below the value specified in keyword4 for 15 minutes.   If the message has been generated and the number of available physical drives is at or has risen above that threshold for 15 minutes, a message is generated indicating that the number of available physical drives is above the low warning limit.   The default value is 0, which indicates no warning limit is set and no messages will be generated.   If the available physical drive critical warning limit is set to 0, the available physical drive low warning limit cannot be set to a value greater than the number of installed physical drives or less than 3. If a value is specified that is greater than the number of installed physical drives, the threshold is set to the number of installed physical drives. If a value is specified that is less than 3, the threshold is set to 3.   If the available physical drive critical warning limit is not zero and a value is specified that is not 1 greater than the available physical drive critical warning limit, the available physical drive low warning limit will be changed so that it is 1 more than the available physical drive critical warning limit (but never greater than the number of installed physical drives).   The message text is shown (xx is the number of available drives, and yy is the threshold): •When fallen below the threshold: AL0004 Available physical drives of xx is below low limit of yy. •When risen above the threshold: AL0005 Available physical drives no longer below low limit of yy.
PSCRCRIT	value	Physical Scratch Volume Critical Warning Limit This is the threshold, in number of scratch physical volumes, at which the TS7700 Virtualization Engine will generate a message indicating that the number of available scratch physical volumes has fallen below the critical warning limit. For this message to be generated, the number of available physical scratch volumes for one of the active general pools (pools 1 - 32) must be below the value specified in keyword4 for 16 minutes. Available volumes include those in pool 0 if borrowing is allowed for the pool.   All media types allowed for borrowing are considered. As long as the number of scratch physical volumes is below the threshold, the below the threshold message is repeated every 16 minutes. If the message has been generated and the number of available physical scratch volumes for the pool is at or has risen above that threshold for 16 minutes, a message is generated indicating that the number of available physical scratch volumes is above the critical warning limit.   The default value is 0, which indicates no warning limit is set and no messages will be generated.   A value greater than 190 cannot be set. If a value is specified that is greater than 190, the threshold is set to 190. A value less than 5 cannot be set. If a value is specified that is less than 5, the threshold is set to 5.   If the physical scratch volume low warning limit is not zero and a value is specified that is not 10 less than the physical scratch volume low warning limit, the physical scratch volume low warning limit will be changed so that it is 10 more than the value specified (but never greater than 200).   The message text is shown (xxx is the number of available physical scratch volumes, yyy is the threshold, and zz is the pool number): •When fallen below the threshold: AL5006 Available physical scratch volumes of xxx below critical limit of yyy for pool zz. •When risen above the threshold: AL5007 Available physical scratch volumes no longer below critical limit of yyy for pool zz. Tip: The TS7700 Virtualization Engine will enter panic reclaim if the number of scratch volumes available to a defined pool is less than 2, including ones that it can borrow from pool 0.
PSCRLOW	value	Physical Scratch Volume Low Warning Limit This is the threshold, in number of scratch physical volumes, at which the TS7700 Virtualization Engine will generate a message indicating that the number of available scratch physical volumes has fallen below the low warning limit. For this message to be generated, the number of available physical scratch volumes for one of the active general pools (pools 1 - 32) must be below the value specified in keyword4 for 16 minutes. Available volumes include those in pool 0 if borrowing is allowed for the pool.   All media types allowed for borrowing are considered. If the message has been generated and the number of available physical scratch volumes for the pool and media type is at or has risen above that threshold for 16 minutes, a message is generated indicating that the number of available physical scratch volumes is above the low warning limit.   The default value is 0, which indicates no warning limit is set and no messages are to be generated.   If the physical scratch volume critical warning limit is set to 0, the physical scratch volume low warning limit cannot be set to a value greater than 200 or less than 5. If a value is specified that is greater than 200, the threshold is set to 200. If a value is specified that is less than 5, the threshold is set to 5.   If the physical scratch volume critical warning limit is not zero and a value is specified that is not 10 greater than the physical scratch volume critical warning limit, the physical scratch volume low warning limit will be changed so that it is 10 more than the physical scratch volume critical warning limit (but never greater than 200).   The message text is shown (xxx is the number of available physical scratch volumes, yyy is the threshold, and zz is the pool number): •When fallen below the threshold: AL0006 Available physical scratch volumes of xxx below low limit of yyy for pool zz. •When risen above the threshold: AL0007 Available physical scratch volumes no longer below low limit of yyy for pool zz. Tip: The TS7700 Virtualization Engine will enter panic reclaim if the number of scratch volumes available to a defined pool is less than 2, including ones that it can borrow from pool 0.
RESDHIGH	value	Resident Data High Warning Limit This is the threshold, in gigabytes of resident data, at which the TS7700 Virtualization Engine will generate a message indicating that the amount of resident data has exceeded a high warning limit. For this message to be generated, the amount of resident data must be above the value specified in keyword4 for 150 seconds. As long as the amount of resident data remains above the threshold, the above warning limit message is repeated every 15 minutes.   If the message has been generated and the amount of resident data is at or falls below that threshold for 150 seconds, a message is generated indicating that the amount of resident data is below the high warning limit.   The default value is 0, which indicates no warning limit is set and no messages are to be generated.   A value greater than the enabled cache size less 500 GB cannot be set. If a value is specified that is not 500 GB lower than the enabled cache size, the threshold is set to the enabled cache size less 500 GB. A value less than 100 GB cannot be set. If a value is specified that is not 100 GB or greater, the threshold is set to 100 GB.   If the resident data low warning limit is not zero and a value is specified that is not 100 GB greater than the resident data low warning limit, the resident data low warning limit will be changed so that it is 100 GB less than the value specified (but never lower than 0).   The message text is shown (xxxxxxxx is the amount of resident data, and yyyyyyyy is the threshold): •When above the threshold: AL5008 Resident data of xxxxxxxx GB above high warning limit of yyyyyyyy GB. •When below the threshold: AL5009 No longer above resident data high warning limit of yyyyyyyy GB. Tip: For a TS7740 Virtualization Engine, resident data is the data that has not been copied to back-end physical volumes. For a TS7720 Virtualization Engine, resident data is the data that occupies the cache.
RESDLOW	Value	Resident Data Low Warning Limit This is the threshold, in gigabytes of resident data, at which the TS7700 Virtualization Engine will generate a message indicating that the amount of resident data has exceeded a low warning limit. For this message to be generated, the amount of resident data must be above the value specified in keyword4 for 150 seconds.   If the message has been generated and the amount of resident data is at or falls below that threshold for 150 seconds, a message is generated indicating that the amount of resident data is below the low warning limit.   The default value is 0, which indicates no warning limit is set and no messages are to be generated.   If the resident data high warning limit is set to 0, the resident data low warning limit cannot be set to a value greater than the enabled cache size less 500 GB or to a value less than 100 GB. If a value is specified that is not 500 GB lower than the enabled cache size, the threshold is set to the enabled cache size less 500 GB. If a value is specified that is less than 100 GB, the threshold is set to 100 GB.   If the resident data high warning limit is not zero, the resident data low warning limit cannot be set to a value greater than the resident data high warning limit less 100 GB. If a value is specified that is not 100 GB lower than the resident data high warning limit, the threshold is set to the resident data high warning limit less 100 GB (but never lower than 0).   The message text is shown (xxxxxxxx is the amount of resident data, and yyyyyyyy is the threshold): •When above the threshold: AL0008 Resident data of xxxxxxxx GB above low warning limit of yyyyyyyyy GB. •When below the threshold: AL0009 No longer above resident data low warning limit of yyyyyyyy GB. Tip: For a TS7740 Virtualization Engine, resident data is the data that has not been copied to back-end physical volumes. For a TS7720 Virtualization Engine, resident data is the data that occupies the cache.
PCPYLOW	Value	Pending Copy Low This is the threshold in GBs of volumes in the copy queue. The following limitations are for this alarm to be set: •The difference between the critical value (described below) and the low value must be equal to or bigger than 500. •The lower value for this field must be equal to or bigger than 500 GB. When adjusting the lower/high value, if the difference is lower than 500, the lower value is decreased automatically to accommodate the difference.   The message text is presented (xx is the distributed library name, yyyy is total pending copy GB, and zzzz is the threshold of the alert) when the level falls below or rises above the threshold: •AL0011 Distributed Library xx has successfully fallen below the inbound copy backlog low warning limit of zzzz GB. •AL0010 Distributed Library xx has a total pending inbound copy backlog of yyyy GB which is above the low warning limit of zzzz GB.
PCPYCRIT	Value	Pending Copy Critical This is the upper limit in GB for volumes in the copy queue. The difference between the critical value (described above) and the low value must be equal to or bigger than 500. When adjusting the lower/high value, if the difference is lower than 500, the lower value is decreased automatically to accommodate the difference. The same messages, AL0011 and AL0010, are presented (see above in the PCPYLOW keyword section).
DEFDEG	ENABLE DISABLE	Synchronous deferred or the immediate deferred condition occurs: •When the ENABLE keyword is specified, the degraded state is reported to the host through the operational state change attention. •When the DISABLE keyword is specified, the degraded state is not reported to the host through the operational state change attention. The default setting is ENABLE. The command is acceptable only when all clusters in the grid are at code level 8.30.xx.xx or higher. The following messages are shown: G0005 Distributed Library xx has entered the immediate deferred state and G0032 Distributed Library xx has entered the synchronous deferred state due to volser yyyyyy are generated regardless of the DEFDEG setting.
REMOVMSG	ENABLE DISABLE	Prevents a distributed library (TS7720) from reporting Automatic Removal start and stop events to the MI and operator messages to the host when Auto Removal occurs. When the ENABLE keyword is specified, an event will be posted to the TS7700 MI when automatic removal of logical volumes starts and another event will be posted when it stops. An associated host message will be sent for each event as well. When the DISABLE keyword is specified, no event or message associated with automatic removal of logical volumes will be posted in the TS7700 MI or sent to the host. The default setting is ENABLE. This command is acceptable only on TS7720 with code level 8.21.0.144 or higher.

Keyword3	Keyword4	Description
COPYFSC	ENABLE, DISABLE	Copies To Follow Storage Class Preference When the ENABLE keyword is specified, the logical volumes copied into the cache from a peer TS7700 Virtualization Engine are managed using the actions defined for the Storage Class construct associated with the volume as defined at the TS7700 Virtualization Engine receiving the copy. When the DISABLE keyword is specified, the logical volumes copied into the cache from a peer TS7700 Virtualization Engine are managed as PG0 (prefer to be removed from cache). The default is disabled.
PMPRIOR	value	Premigration Priority Threshold This is the threshold, in gigabytes of unpremigrated data, at which the TS7700 Virtualization Engine will begin increasing the number of premigration tasks that will be allowed to compete with host I/O for cache and processor cycles.   The amount of unpremigrated data must be above the value specified in keyword4 for 150 seconds before the additional premigration tasks are added. As the amount of data to premigrate continues to grow above this threshold setting, so do the number of enabled premigration tasks until the maximum is reached. The maximum is the number of available physical drives minus 1 (the TS7700 Virtualization Engine always keeps a minimum of one drive available for recalls).   If the amount of unpremigrated data subsequently falls below this threshold for at least 150 seconds, the number of premigration tasks might be reduced depending on host I/O demand. If I/O host demand is high, the number of premigration tasks will eventually be reduced to a minimum of one.   The default value is 1600.   If a value is specified that is higher than the premigration throttling threshold value, it is set to the premigration throttling threshold value.   Tip: Do not change this setting from the default unless you understand the impact that the change will have on the operation of the TS7700 Virtualization Engine. Raising the value might increase the length of time a peak write rate might be accepted, but also means that more data is solely resident in the cache and delays copying that data to physical tape.
PMTHLVL	value	Premigration Throttling Threshold This is the threshold, in gigabytes of unpremigrated data, at which the TS7700 Virtualization Engine will begin introducing a delay in responding to host write operations on all virtual tape device addresses of the TS7700 Virtualization Engine.   The amount of unpremigrated data must be above the value specified in keyword4 for 150 seconds before the delay is introduced. The amount of delay begins with a few milliseconds and increases to 2000 milliseconds as the amount of unpremigrated data approaches the total cache capacity. The amount of unpremigrated data must fall below this threshold for 150 seconds for all delay to be removed.   The default value is 2000.   A value greater than the enabled cache size less 500 GB cannot be set. If a value is specified that is not 500 GB lower than the enabled cache size, the threshold is set to the enabled cache size less 500 GB.   Tip: Do not change this setting from the default unless you understand the impact that the change will have on the operation of the TS7700 Virtualization Engine. Raising the value might increase the length of time a peak write rate might be accepted, but also means that more data is solely resident in the cache and delays copying that data to physical tape.
RECLPG0	ENABLE, DISABLE	Recalls Preferred to be Removed from Cache When the ENABLE keyword is specified, logical volumes that are recalled into cache are managed as PG0 (prefer to be removed from cache). This overrides the actions defined for the Storage Class associated with the recalled volume. When the DISABLE keyword is specified, logical volumes that are recalled into cache are managed using the actions defined for the Storage Class construct associated with the volume as defined at the TS7700 Virtualization Engine. The default is disabled.
REMOVE	ENABLE, DISABLE	Automatic removal starts when cache usage size crosses the removal threshold. When the ENABLE keyword is specified, the automatic removal will be enabled on this disk-only cluster. When the DISABLE keyword is specified, the automatic removal will be disabled on this disk-only cluster. The default value is enabled.
REMVTHR	Value	Automatic removal starts when the cache usage size crosses the removal threshold. When automatic removal is enabled on this disk-only cluster, logical volume removal will start when the free cache space is below the removal threshold plus 1000 GB (1000 GB is the out-of-cache warning threshold). The default value is 3000 (in GB). A value of 2000 to 10000 can be set. As an example, a value of 2000 means that the TS7700 will start the automatic removal when there is less than 3000 GB (2000 GB + 1000 GB) of free cache space. If a value less than 2000 is given, it will be set to 2000. If a value more than 10000 is given, it will be set to 10000.

Keyword3	Keyword4	Description
COPYFT	ENABLE, DISABLE	Full Cache Copy Throttling When the ENABLE keyword is specified, throttling when the cache is full of uncopied data to other TS7700 Virtualization Engines is enabled. When the DISABLE keyword is specified, throttling when the cache is full of uncopied data to other TS7700 Virtualization Engines is disabled. The default is enabled. Tip: Full Cache Copy Throttling is also disabled for 24 hours after one of the other TS7700 Virtualization Engines has been in service mode. This is to prevent immediate host throttling when the TS7700 Virtualization Engine being serviced is returned to use.
DCOPYT	value	Deferred Copy Throttle This is a delay, in milliseconds, that the TS7700 will introduce for every 256 KB copy transfer for all deferred mode copy tasks in which it is the source. The delay is introduced when the TS7700 detects that it is in a period of high host write workload. The criteria the TS7700 uses is if the data rate into the cache exceeds 100 MB/s (this is after compression) or if the idle processor cycles of the TS7700 fall below 15%. A value of 0 to 250 milliseconds can be set. The default value is 125 milliseconds.
ICOPYT	ENABLE, DISABLE	Immediate Copy Throttling When the ENABLE keyword is specified, immediate copy throttling is enabled. The depth of the immediate copy queue and the amount of time copies have been in the queue are examined to determine whether the throttle must be applied. When the DISABLE keyword is specified, immediate copy throttling is disabled. The default is enabled.
DCTAVGTD	value	Deferred Copy Throttling Average Threshold This value is used to determine at what average compressed Host I/O rate to keep deferred copy throttling delayed. The average compressed host I/O rate is an average of the I/O rate over a 20-minute period. When this average compressed rate is exceeded, the deferred copies are delayed as specified by the DCOPYT value. The default value is 100 in MBps. A value of 0 will set the threshold to the default. A value of 1 - 500 can be set.

Keyword3	Keyword4	Description
SCRATCH	ENABLE, DISABLE	Device Allocation Assist for Scratch Volumes If a keyword4 of ENABLE is specified, a domain at code level 8.20.x.x or greater shall process device allocation assist commands for scratch volumes. A keyword4 of DISABLE will remove the capability to process device allocation assist commands for scratch volumes. The default is disabled.
PRIVATE	ENABLE, DISABLE	Device Allocation Assist for Private Volumes If a keyword4 of DISABLE is specified, a domain at code level 8.20.x.x or greater inhibits processing device allocation assist commands for private volumes. A keyword4 of ENABLE allows the capability to process device allocation assist commands for private volumes. The default is enabled.

Note: Also, if a valid RECLAIM request is received while reclaims are inhibited, that request will take effect as soon as reclaims are no longer inhibited by the Inhibit Reclaim schedule.

Keyword3	Keyword4	Description
RCLMMAX	value	Reclaim Maximum Tasks Limit Sometimes, you might want to have fewer reclaims running and use the service resource for other activities in the cluster. If keyword3 is specified as RCLMMAX, the cluster can be directed to limit the maximum number of reclaims to a certain value. The number of available tasks is closely related to the number of physical drives connected to the cluster: •Three - five drives give a maximum number of reclaim tasks of 1 •Six - seven drives give a maximum number of reclaim tasks of 2 •Eight - nine drives give a maximum number of reclaim tasks of 3 •Ten - 11 drives give a maximum number of reclaim tasks of 4 •Twelve - 13 drives give a maximum number of reclaim tasks of 5 •Fourteen - 15 drives give a maximum number of reclaim tasks of 6 •Sixteen drives give a maximum number of reclaim tasks of 7

Keyword3	Keyword4	Description
RUN	Number of Concurrent RUN Copy Threads	The number of concurrent copy threads for processing RUN copies The allowed values for copy thread counts are 5 - 128. The default value is 20 for clusters with two 1 Gb Ethernet links, and 40 for clusters with four 1 Gb Ethernet links or two 10 Gb Ethernet links.
DEF	Number of Concurrent Deferred Copy Threads	The number of concurrent copy threads for processing Deferred copies The allowed values for copy thread counts are 5 - 128. The default value is 20 for clusters with two 1 Gb Ethernet links, and 40 for clusters with four 1 Gb Ethernet links or two 10 Gb Ethernet links.

Keyword3	Keyword4	Description
IMMSNS	All UNEXP NONE	Immediate-Deferred State Reporting Method This is the control method to report the immediate-deferred state in the CCW (RUN) ERA35 sense data. With Release 1.6 code, TS7700 reports all the immediate-deferred state in the CCW (RUN) ERA35 sense data. Since Release 1.7 pre-general availability (PGA) 5 (8.7.0.155) or 2.0 codes, the reporting method can be modified: •If keyword4 of ALL is specified, all the immediate-deferred state is reported in the ERA35 sense data the same as Release 1.6. •If keyword4 of UNEXP is specified, only the immediate-deferred state induced unexpectedly is reported in the ERA35 sense data. •If keyword4 of NONE is specified, no immediate-deferred state is reported in the ERA35 sense data except the case where no valid source to copy is available. •The default value is NONE. See IBM Virtualization Engine TS7700 Series Best Practice Understanding, Monitoring and Tuning the TS7700 Performance, WP101465, which is available at http://www.ibm.com/support/techdocs for more information.
TIMEOUT	value	Volume Copy Timeout Time This is the timeout value in minutes for logical volume copies between clusters to complete. A volume copy between TS7700s has a timeout value. If a volume copy starts and does not finish in the allotted time, it is canceled and returned to the copy queue for retry. Prior to Release 2.0 codes, the timeout value is fixed at 180 minutes. Starting with Release 2.0 codes, the timeout value can be modified. The default value is 180 minutes; however, a larger timeout value may be needed when copy tasks increase or limited bandwidth is available. The allowed values for copy timeout are from 30 - 999 minutes.

Keyword 3	Keyword4	Description
FAILOVER	ENABLE DISABLE	IP Link Failover for Remount Mounts If keyword4 of ENABLE is specified, a cluster at code level 8.21.x.x or greater shall use the failover capability in a link failure during a remote mount. Keyword4 of DISABLE shall remove the failover capability. The default behavior is ENABLE.

Keyword3	Keyword4	Description
COUNT	Value	Delete Expire Count The Delete Expire Count can be set to any value from the default value of 1000 to the maximum value of 2000. If the keyword4 specified value is smaller than the default, the default value will be set. If the keyword4 specified value is greater than the maximum, it will be set at the maximum value.

Tip: The previous examples are only a few samples of the available commands. For a complete list of commands and parameters, see the IBM Virtualization Engine TS7700 Series z/OS Host Command Line Request User’s Guide Version 3.0, which is available at http://www.ibm.com/support/techdocs/atsmastr.nsf/Web/Techdocs.

Tip: Before invoking service preparation at the TS7700 Virtualization Engine, all virtual devices must be varied offline from the host. All logical volumes must be dismounted, all devices associated with the cluster varied offline, and all jobs moved to other clusters in the grid before service preparation is invoked. After service is complete, and when the TS7700 Virtualization Engine is ready for operation, you must vary the devices online at the host.

Note: Perform Inventory will be shown if there is no high-density frame installed on the tape library. Perform Inventory will inventory high-density frame cells only for the first cartridge unless the first cartridge differs from the stored library inventory. Perform Inventory with Audit will inventory all cells in a high-density frame.

Important: As stated on the confirmation window (Figure 9-124), if you continue, all jobs in the work queue might be delayed while the request is performed. The inventory will take up to one minute per frame. The audit will take up to one hour per high-density frame.

Note: Perform the Inventory Upload from the TS3500 Tape Library to all TS7740 Virtualization Engines attached to that tape library whenever a library door is closed, manual inventory or Inventory with Audit is performed, or TS7740 is varied online from an offline state.

Tips: •The inventory is performed only on the frame where the door is opened and not on the frames to either side. If you insert cartridges into a frame adjacent to the frame that you opened, you must perform a manual inventory of the adjacent frame using the operator window on the TS3500 Tape Library itself. •For a TS7740 Virtualization Engine, it is important to note that the external cartridge bar code label and the internal VOLID label match or, as is the case for a new cartridge, the internal VOLID label is blank. If the external label and the internal label do not meet this criteria, the cartridge will be rejected.

Consideration: Unassigned cartridges can exist in the TS3500 Tape Library, but “unassigned” cartridges can have different meanings and need different actions. See IBM System Storage TS3500 Tape Library with ALMS Operator Guide, GA32-0594, for more information.

Consideration: Because having a distributed library in the out-of-empty-stacked-volume state affects operations in a TS7740 Virtualization Engine, avoid this situation if at all possible.

Tip: Logical volumes that are in the error category (000E) can be moved back to the scratch category by using ISMF to move them from Scratch to Scratch category.

Clarification: In a DFSMS system-managed tape environment, if you try to eject a logical volume and get this error, OAM notifies the tape management system. This is done through the OAM eject exit CBRUXEJC command before the eject request is sent to the tape library. The Integrated Library Manager will eventually fail the eject, but the tape management system has already marked the volume as ejected. Before APAR OW54054, there was no notification back that the eject failed. Failed Eject Notification was added to OAM with APAR OW54054 and is currently in all supported releases of DFSMS. Any tape management system supporting this notification can use this function.

Tip: Limiting the number of outstanding ejects to a few thousand total per system will limit exposure to performance problems.

More information: For the latest information about ALxxxx messages and all other messages related to CBR3750I, see the IBM Virtualization Engine TS7700 Series Operator Informational Messages white paper, which is available at the following address: http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101689

Clarification: Library type VCL indicates the composite library, as opposed to VDL for the distributed library.

Important: Repairing a 3592 tape must only be done for data recovery. After the data has been moved to a new volume, replace the repaired cartridge.

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