Host Console Operations
This chapter provides information about how to operate the IBM TS7700 Virtualization Engine, with emphasis on commands and procedures that are initiated from the host operating system. This section covers the following main topics:
IBM Data Facility Storage Management Subsystem (DFSMS) Operator Commands
IBM MVS System Commands
Host Console Request Function
LMPOLICY Command
DEVSERV Command
Scratch Volume Recovery
Ejecting Logical Volumes
TS7700 Host Console Messages
EXPIRE HOLD and Scratch Processing
Scratch Counts Mismatch
Effects of Changing Categories
9.1 System-managed tape
This section describes the commands that are used to operate a tape library in an IBM z/OS and system-managed tape environment. It is not intended to replace the full operational procedures in the product documentation. It is a quick reference for some of the more useful Data Facility Storage Management Subsystem (DFSMS) and MVS commands.
9.1.1 DFSMS operator commands
Some of the commands contain libname as a variable. In this case, the storage management subsystem (SMS)-defined library name is required. Depending on whether you reference a TS7700 Virtualization Engine composite library, TS7700 Virtualization Engine distributed library, or your native drives partition, the output differs slightly for some of these commands. For more information about DFSMS commands, see z/OS DFSMS Object Access Method Planning, Installation, and Storage Administration Guide for Tape Libraries, SC23-6867.
Information from the IBM TS3500 Tape Library is contained in some of the outputs. However, you cannot switch the operational mode of the TS3500 Tape Library with z/OS commands.
 
Restriction: DFSMS and MVS commands apply only to 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. The activation of a source control data set (SCDS) with this libname must have already been performed for SMS to recognize the library.
The following DFSMS operator commands support the tape library:
DISPLAY SMS,LIBRARY(libname|ALL),STATUS
This is an SMS Configuration level view, which indicates whether the SMS-defined libraries are online, offline, or pending offline, on each of the systems in the configuration.
STATUS is the default parameter.
DISPLAY SMS,LIBRARY(ALL),DETAIL
The DETAIL display, although a single-system view, gives slightly more information. The display is similar to the result of DISPLAY SMS,OAM, but each library gets its own line of information. See Example 9-1.
Example 9-1 D SMS,LIB(ALL),DETAIL
D SMS,LIB(ALL),DETAIL
CBR1110I OAM library status: 738
TAPE LIB DEVICE TOT ONL AVL TOTAL EMPTY SCRTCH ON OP
LIBRARY TYP TYPE DRV DRV DRV SLOTS SLOTS VOLS
CLIB00 VCL GRID 512 0 0 0 0 0 N Y
DTS7720 VDL 3957-VEB 0 0 0 559 516 0 Y Y
D0001 VDL 3957-V07 0 0 0 1000 960 0 Y N
D0002 VDL 3957-V07 0 0 0 1000 880 0 Y N
E0001 VDL 3957-V07 0 0 0 1000 883 0 Y N
E0002 VDL 3957-V07 0 0 0 1000 880 0 Y N
HYDRAE VDL 3957-V07 0 0 0 185 129 0 Y Y
HYDRAG VCL GRID 512 2 2 0 0 45547 Y Y
 
DISPLAY SMS,LIBRARY(libname),DETAIL
This command provides details about the status of a single library. It is the only command that displays the library state (auto, pause, or manual mode). Reasons for the mode and indications of inoperative parts of the library are given in extra status lines. See Example 9-2.
Example 9-2 D SMS,LIB(libname)DETAIL
D SMS,LIB(HYDRAG),DETAIL
CBR1110I OAM library status: 754
TAPE LIB DEVICE TOT ONL AVL TOTAL EMPTY SCRTCH ON OP
LIBRARY TYP TYPE DRV DRV DRV SLOTS SLOTS VOLS
HYDRAG VCL GRID 512 2 2 0 0 45547 Y Y
----------------------------------------------------------------------
MEDIA SCRATCH SCRATCH SCRATCH
TYPE COUNT THRESHOLD CATEGORY
MEDIA1 10 0 0021
MEDIA2 45537 0 0022
----------------------------------------------------------------------
DISTRIBUTED LIBRARIES: HYDRAE DTS7720
----------------------------------------------------------------------
LIBRARY ID: 00186
OPERATIONAL STATE: AUTOMATED
ERROR CATEGORY SCRATCH COUNT: 1
CORRUPTED TOKEN VOLUME COUNT: 24
----------------------------------------------------------------------
Library supports import/export.
Library supports outboard policy management.
Library supports logical WORM.
Library enabled for scratch allocation assistance.
DISPLAY SMS,VOLUME(volser)
This command displays all information that is stored about the volume in the tape configuration database (TCDB), also known as the VOLCAT, and the assigned SMS constructs. See Example 9-3.
Example 9-3 D SMS,VOL
D SMS,VOL(B00941)
RESPONSE=MZPEVS2
CBR1180I OAM tape volume status: 195
VOLUME MEDIA STORAGE LIBRARY USE W C SOFTWARE LIBRARY
TYPE GROUP NAME ATR P P ERR STAT CATEGORY
B00941 MEDIA2 SGG00001 HYDRAG P N N NOERROR PRIVATE
-------------------------------------------------------------------
RECORDING TECH: 36 TRACK COMPACTION: YES
SPECIAL ATTRIBUTE: NONE ENTER/EJECT DATE: 2011-02-14
CREATION DATE: 2011-02-14 EXPIRATION DATE: 2014-11-15
LAST MOUNTED DATE: 2014-11-10 LAST WRITTEN DATE: 2014-11-10
SHELF LOCATION:
OWNER: DENEKA
LM SG: SGG00001 LM SC: SC00030R LM MC: MNDNN020 LM DC: D000N004
LM CATEGORY: 002F
DISPLAY SMS,OAM
This command, shown in Example 9-4, is primarily useful for checking the status of the object access method (OAM) user exits.
Example 9-4 D SMS,OAM
D SMS,OAM
RESPONSE=MZPEVS2
CBR1100I OAM status: 744
TAPE TOT ONL TOT TOT TOT TOT TOT ONL AVL TOTAL
LIB LIB AL VL VCL ML DRV DRV DRV SCRTCH
3 1 0 0 3 0 1280 2 2 45547
There are also 7 VTS distributed libraries defined.
CBRUXCUA processing ENABLED.
CBRUXEJC processing ENABLED.
CBRUXENT processing ENABLED.
 CBRUXVNL processing ENABLED.
VARY SMS,LIBRARY(libname),OFFLINE
From the host standpoint, the vary online and vary offline commands for a TS7700 Virtualization Engine Library always use the library name as defined through ISMF.
This command acts on the SMS library, which is referred to as libname. That is, it stops tape library actions and gradually makes all of the tape units within this logical library unavailable. This simple form is a single-system form. The status of the library remains unaffected in other MVS systems.
 
Note: A composite and distributed Virtual Tape Server (VTS) library can be varied online and offline like any VTS library, though varying a distributed library offline from the host really has no meaning (does not prevent outboard usage of the library). Message CBR3016I warns the user when a distributed library is initialized or
varied offline.
This command is required to bring the SMS-defined library back to operation after it has been offline. The logical library does not necessarily go offline as a result of an error in a component of the physical library.
Therefore, some messages for error situations request that the operator first vary the library offline and then back online. This usually clears all error indications and returns the library back into operation. However, this is only the MVS part of error recovery. You must clear the hardware, software, or operational error within the physical library and TS7700 Virtualization Engine before you bring the library online to MVS.
VARY SMS,LIBRARY(libname,sysname,...),ON/OFF and VARY SMS,LIBRARY(libname,ALL),ON/OFF
This extended form of the VARY command can affect more than one system. The first form affects one or more named MVS systems. The second form runs the VARY action on all systems within the SMSplex.
The VARY SMS command enables the short forms ON as an abbreviation for ONLINE and OFF as an abbreviation for OFFLINE.
LIBRARY EJECT,volser{,PURGE|KEEP|LOCATION}{,BULK}
This command is used to request the ejection of a volume from a tape library. The following options are available for this command:
 – Eject to the convenience I/O station for physical volumes. Delete from the tape library for logical volumes that are considered scratch.
 – Eject to the bulk output station (BULK or B) for physical volumes. Delete from the tape library for logical volumes that are considered scratch.
 – Remove the volume record from the TCDB (PURGE or P).
 – Keep the volume record in the TCDB and update it to indicate that the cartridge has been ejected (KEEP or K). If the record contains information in the SHELF location field, it is not changed. If the SHELF location field is empty, the operator must enter information about the new location as a reply to write to operator with reply (WTOR). The reply can be up to 32 characters long.
 – Keep the volume record in the TCDB and update it, including updating the SHELF location even if there is information in this field (LOCATION or L). The operator must enter the new information as a reply to WTOR.
If none of the variations (PURGE, KEEP, or LOCATION) are indicated in the command, a default decides whether the record is kept or purged. This default can be set separately for each library through the ISMF Library Definition window.
This command is available for the operator to eject single cartridges. Mass ejection of cartridges is usually performed through program interfaces, such as ISMF, a tape management system, or a batch job.
9.1.2 MVS system commands
The following commands are described in detail in z/OS MVS System Commands, SA22-7627:
VARY unit,ONLINE/OFFLINE
The VARY unit command is no different from what it was before. However, new situations are seen when the affected unit is attached to a library.
When the library is offline, the tape units cannot be used. This is internally indicated in a new status (offline for library reasons), which is separate from the normal unit offline status. A unit can be offline for both library and single-unit reasons.
A unit that is offline for library reasons only cannot be varied online by running VARY unit,ONLINE. Only VARY SMS,LIBRARY(...),ONLINE can do so.
You can bring a unit online that was individually varied offline, and was offline for library reasons, by varying it online individually and varying its library online. The order of these activities is not important, but both are necessary.
The LIBRARY DISPDRV command tells you if a device is online or offline, and the reason if it is offline.
DISPLAY M=DEV(xxxx)
The D M=DEV command is useful for checking the operational status of the paths to the device. See Example 9-5.
Example 9-5 D M=DEV
D M=DEV(2500)
IEE174I 04.29.15 DISPLAY M 626
DEVICE 02500 STATUS=OFFLINE
CHP B2 B3 B8 B9
ENTRY LINK ADDRESS 20 21 22 23
DEST LINK ADDRESS D4 D5 D6 D7
PATH ONLINE Y Y N N
CHP PHYSICALLY ONLINE Y Y Y Y
PATH OPERATIONAL Y Y Y Y
MANAGED N N N N
CU NUMBER 2500 2500 2500 2500
MAXIMUM MANAGED CHPID(S) ALLOWED: 0
DESTINATION CU LOGICAL ADDRESS = 00
SCP CU ND = NOT AVAILABLE
SCP TOKEN NED = 003490.C2A.IBM.78.0000000H6395.0000
SCP DEVICE NED = 003490.C2A.IBM.78.0000000H6395.0000
DISPLAY U
The DISPLAY U command displays the status of the requested unit. If the unit is part of a tape library (either manual or automated), device type 348X is replaced by 348L. An IBM 3490E is shown as 349L, and a 3590 or 3592 is known as 359L.
MOUNT devnum, VOL=(NL/SL/AL,serial)
The processing of MOUNT has been modified to accommodate automated tape libraries and the requirement to verify that the correct volume has been mounted and is in private status in the TCDB.
UNLOAD devnum
The UNLOAD command enables you to unload a drive, if the Rewind Unload process was not successful initially.
9.1.3 Host Console Request function
The LIBRARY REQUEST host console command (LI REQ) provides a simple way for an operator to determine the status of the TS7700, to obtain information about the resources of the TS7700, and to run an operation in the TS7700. It can also be used with automation software to obtain and analyze operational information that can then be used to alert a storage administrator that something must be examined further.
With the 3.2 code release, the TS7700 Management Interface enables an operator to issue a Library Request host console command as if it was issued from the z/OS host. The result of the command is displayed on the MI panel.
Specify the following information for the command:
A library name, which can be a composite or a distributed library.
It also enables one to four keywords, with each keyword being a maximum of 8 characters.
The specified keywords are passed to the TS7700 identified by the library name to instruct it about what type of information is being requested or which operation is to be run. Based on the operation requested through the command, the TS7700 then returns information to the host that is displayed as a multiline write to operator (WTO) message.
This section describes some of the more useful and common LI REQ commands that a client would normally use. A detailed description of the Host Console Request functions and responses is available in IBM Virtualization Engine TS7700 Series z/OS Host Command Line Request User’s Guide, which is available at the Techdocs website:
Command syntax for the Host Console Request function
The Host Console Request is also referred to as the Library Request command. The syntax of the command is shown in Example 9-6.
Example 9-6 Host Console Request function syntax
>>__ _LIBRARY_ ___REQUEST___,__library_name________________________>
|_LI______| |_REQ_____|
 
>___ _,keyword1___________________________________________________><
|_,keyword2____________________| |_,L=_ _a______ __|
|_,keyword3____________________| |_name___|
|_,keyword4____________________| |_name-a_|
The following parameters are required:
REQUEST | REQ Specifies a request to obtain information from the TS7700 Virtualization Engine, or to run an outboard operation.
library_name Specifies the library name associated with the TS7700 Virtualization Engine to which the request needs to be directed. The library name specified can be a composite or a distributed library, and which library is applicable depends on the other keywords specified.
keyword1 Specifies which operation is to be run on the TS7700 Virtualization Engine.
The following parameters are optional. The optional parameters depend on the first keyword specified. Based on the first keyword specified, zero or more of the additional keywords might be appropriate:
keyword2 Specifies additional information in support of the operation specified with the first keyword.
keyword3 Specifies additional information in support of the operation specified with the first keyword.
keyword4 Specifies additional information in support of the operation specified with the first keyword.
L={a | name | name-a}
Specifies where to display the results of the inquiry: the display area (L=a), the console name (L=name), or both the console name and the display area (L=name-a). The name parameter can be an alphanumeric character string.
Note the following information:
If the request is specific to the composite library, the composite library name must be specified.
If the request is specific to a distributed library, the distributed library name must be used.
If a request for a distributed library is received on a virtual drive address on a TS7700 cluster of a separate distributed library, the request is routed to the appropriate cluster for handling, and the response is routed back through the requesting device address.
Overview of the Host Console Request functions
Table 9-1 lists some of the LI REQ commands, and gives a short description of each of them.
Table 9-1 Overview of Host Console Request functions
Keyword1
Keyword2
Keyword3
Keyword4
Description
Comp Lib
Dist Lib
TS7720
TS7720T
TS7740
CACHE
 
 
 
Requests information about the current state of the cache and the data managed within it.
N/A
Y
ALL
COPY
ACTIVITY
See the User’s Guide
 
Requests information about Active Copy jobs.
N/A
Y
ALL
COPY
SUMMARY
 
 
Requests information about all the copy jobs.
N/A
Y
ALL
LVOL
volser
FLASH
 
Requests information about a specific logical volume.
Y
N/A
ALL
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
ALL
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
ALL
PDRIVE
 
 
 
Requests information about the physical drives and their current usage associated with the specified distributed library.
N/A
Y
TS7740
and TS7720T
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
and TS7720T
PVOL
volser
 
 
Requests information about a specific physical volume.
N/A
Y
TS7740
and TS7720T
PVOL
volser
DELETE
 
Requests the specified physical volume record to be deleted from the TS7700 database. The specified physical volume must be empty and not physically in the library.
N/A
Y
TS7740
and TS7720T
RECALLQ
volser
 
 
Requests the content of the recall queue starting with the specified logical volume. Keyword2 can be blank.
N/A
Y
TS7740 and TS7720T
RECALLQ
volser
PROMOTE
 
Requests that the specified logical volume be promoted to the top of the recall queue.
N/A
Y
TS7740
and TS7720T
RRCLSUN
ENABLE
DISABLE
STATUS
 
 
In response to the RRCLSUN request, the cluster associated with the distributed library enables, disables, or displays the status of the force residency on recall feature.
N/A
Y
TS7740 and TS7720T
SETTING
ALERT,
CACHE,
THROTTLE
DEVALLOC
RECLAIM
CPYCNT
COPY
LINK
DELEXP
EXISTDEL
See Settings descriptions after this table
See Settings descriptions after this table
Settings to control functions in the grid.
N/A
Y
ALL
SETTINGS2
SCRATCH
 
CACHE
PFRLOCO
 
MAXLGMC
ENABLE
DISABLE
Additional settings to control functions in the grid.
N/A
N/A
ALL
STATUS
GRID
 
 
Requests information about the copy, reconcile, and ownership takeover status of the libraries in a grid configuration.
Y
N/A
ALL
STATUS
GRIDLINK
 
 
Requests information about the status and performance of the links between the TS7700 Virtualization Engines in the grid configuration.
N/A
Y
ALL
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
ALL
DRSETUP
CCCCCCCC (DR family name)
ADD
REMOVE
0-7
(cluster ID)
Add/remove a cluster to/from the disaster recovery (DR) family.
Y
N/A
ALL
WP
ENABLE/
DISABLE
Enable/disable write protect mode within the DR family.
Y
N/A
ALL
FLASH
ENABLE/
DISABLE
Enable/disable Flash
Copy within the DR
family.
Y
N/A
ALL
DOALL
ENABLE/
DISABLE
Enable/disable write protect mode and Flash Copy with a single command.
Y
N/A
ALL
LIVECOPY
FAMILY/
NONE
Enable or disallow use of a live copy within the DR family.
Y
N/A
ALL
SHOW
CCCCCCCC (DR family name)
 
View information about the DR family.
Y
N/A
ALL
PARTRFSH
 
 
 
Change cache partition assignment.
 
 
TS7720T
Overview of the Host Console SETTING request
The SETTING request provides information about many of the current workflow and management settings of the cluster specified in the request and the ability to modify the settings. It also enables alerts to be set for many of the resources managed by the cluster.
In response to the SETTING request, the cluster associated with the distributed library in the request modifies its settings based on the additional keywords specified. If no additional keywords are specified, the request returns the current settings. When a value is specified, lead blanks or zeros are ignored.
ALERT settings
Thresholds can be set for many of the resources managed by the cluster. For each resource, two settings are provided. One warns that the resource is approaching a value that might result in an effect to the operations of the attached hosts. A second provides a warning that the resource has exceeded a value that might result in an effect to the operations of the attached hosts. When the second warning is reached, the warning message is repeated every 15 minutes.
These threshold settings are described in detail in Chapter 10, “Performance and monitoring” on page 597.
In the ALERT settings, you can also specify how messages are treated, and influence other aspects of TS7700 behavior.
Figure 9-1 shows the alert thresholds available for various resources managed by the cluster.
Figure 9-1 Alert setting diagram
Remember: All settings are persistent across system restarts, service actions, or code updates. The settings are not carried forward as part of disaster recovery (DR) from copy-exported tapes or the recovery of a system.
Table 9-2 shows the ALERT thresholds that are supported.
Table 9-2 ALERT thresholds
Keyword3
Keyword4
Description
COPYHIGH
value
Uncopied Data High Warning Limit
This is the threshold, in gigabytes (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 generates a message indicating that the amount of uncopied data has exceeded a high warning limit. The following message text is shown:
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 generates a message indicating that the amount of uncopied data has exceeded a low warning limit. The following message text is shown:
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 generates a message indicating that the number of available physical drives has fallen below the critical warning limit. The following message text is shown:
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 generates a message indicating that the number of available physical drives has fallen below the low warning limit. The following message text is shown:
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 generates a message indicating that the number of available scratch physical volumes has fallen below the critical warning limit. The following message text
is shown:
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 enters panic reclaim if the number of scratch volumes available to a defined pool is less than two, 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 generates a message indicating that the number of available scratch physical volumes has fallen below the low warning limit. The message following text
is shown:
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 enters panic reclaim if the number of scratch volumes available to a defined pool is less than two, 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 generates a message indicating that the amount of resident data has exceeded a high warning limit. The following message text is shown:
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.
RESDTHIGH
value
This is the same threshold with RESDHIGH, but only applicable to the total TS7720 TA tape attached cache partitions (CPx). The following message test is shown:
When above the threshold:
AL5015 Sum of resident data in tape partitions of xxxxxxxx GB above high warning limit of yyyyyyyy GB.
When below the threshold:
AL5016 Sum of resident data in tape partitions no longer above resident data high warning limit of yyyyyyyy GB.
RESDLOW
Value
Resident Data Low Warning Limit
This is the threshold, in gigabytes of resident data, at which the TS7700 Virtualization Engine generates a message indicating that the amount of resident data has exceeded a low warning limit. The following message text is shown:
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.
RSDTLOW
Value
This is the same threshold with RESDLOW, but only applicable to the total TS7720 TA tape attached cache partitions (CPx). The following message text is shown:
When above the threshold:
AL0012 Sum of resident data in tape partitions of xxxxxxxx GB above low warning limit of yyyyyyyyy GB.
When below the threshold:
AL0013 Sum of resident data in tape partition no longer above low warning limit of yyyyyyyy GB.
PCPYLOW
Value
Pending Copy Low
This is the threshold in GBs of volumes in the copy queue. The following message text is presented 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 same messages, AL0011 and AL0010, are presented (see 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 following messages are shown:
G0005 Distributed Library xx has entered the immediate deferred state
G0032 Distributed Library xx has entered the synchronous deferred state due to volser yyyyyy are generated regardless of the DEFDEG setting.
LINKDEG
ENABLE
DISABLE
Prevents a composite library from entering the link degraded state when Grid link degradation 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 following operator messages are still generated regardless of the LINKDEG setting:
G0030 Library XXXXX, PPP, AAA Grid Link are degraded.
G0031All grid links for this cluster have left the degraded state.
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.
CACHE settings
If the second keyword of CACHE is specified, the cluster modifies how it controls the workflow and content of the TVC. The supported CACHE settings are shown in Table 9-3.
Table 9-3 CACHE settings
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 begins increasing the number of premigration tasks that are allowed to compete with host I/O for cache and processor cycles.
 
Tip: Do not change this setting from the default unless you understand the effect 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 begins introducing a delay in responding to host write operations on all virtual tape device addresses of the TS7700 Virtualization Engine.
 
Tip: Do not change this setting from the default unless you understand the effect 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, automatic removal is enabled on this disk-only cluster.
When the DISABLE keyword is specified, automatic removal is 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 starts 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 - 10000 can be set. As an example, a value of 2000 means that the TS7700 starts 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 is set to 2000. If a value more than 10000 is given, it is set to 10000.
CPYPRIOR
ENABLE,
DISABLE
Limit premigration resources under Grid copy activity
When the ENABLE keyword is specified, the number of premigration tasks starts decreasing when Grid copy activity crosses the threshold defined by the CPYPRITH command.
When the DISABLE keyword is specified, the number of premigration tasks do not decrease.
The default value is DISABLED.
CPYPRITH
Value
Premigration resources start being limited when Grid copy activity crosses the threshold
When CPYPRIOR is enabled, the number of premigration tasks starts decreasing when the total Grid copy activity (the data transfer rate to read/write the data from/into the local cluster’s cache) is above the threshold.
RBPRIOR
Value
Cache Rebuild Priority
RBTHLVL
Value
Cache Rebuild Priority Threshold
THROTTLE settings
If a second keyword of THROTTLE is specified, the cluster modifies how it controls the data flow rates into and out to the cluster. Supported THROTTLE settings are shown in Table 9-4.
Table 9-4 THROTTLE settings
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
The default value is 125 milliseconds.
ICOPYT
ENABLE,
DISABLE
Immediate Copy Throttling
The default is enabled.
DCTAVGTD
value
Deferred Copy Throttling Average Threshold
A value of 0 sets the threshold to the default. A value of 1 - 500 can be set.
DEVALLOC (Device Allocation) settings
If a second keyword of DEVALLOC is specified, the cluster modifies how it runs scratch allocation assistance (SAA) or device allocation assistance (DAA) for private tapes. For details about SAA and DAA, see Chapter 10, “Performance and monitoring” on page 597. The DEVALLOC settings shown in Table 9-5 are supported.
Table 9-5 DEVALLOC settings
Keyword3
Keyword4
Description
SCRATCH
ENABLE,
DISABLE
Device Allocation Assist for Scratch Volumes
The default is disabled.
PRIVATE
ENABLE, DISABLE
Device Allocation Assist for Private Volumes
The default is enabled.
Reclaim settings
If a second keyword of RECLAIM is specified, the cluster modifies how the reclaim background tasks controls the workflow and content of the TVC.
 
Note: Also, if a valid RECLAIM request is received while reclaims are inhibited, that request takes effect as soon as reclaims are no longer inhibited by the Inhibit Reclaim schedule.
The RECLAIM settings shown in Table 9-6 are supported.
Table 9-6 RECLAIM settings
Keyword3
Keyword4
Description
RCLMMAX
value
Reclaim Maximum Tasks Limit
CPYCNT (Copy Thread Count) settings
If a second keyword of CPYCNT is specified, the domain modifies how many concurrent threads are allowed to process either RUN or Deferred copies over the grid.
The CPYCNT settings shown in Table 9-7 are supported.
Table 9-7 CPYCNT settings
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 gigabit Ethernet (GbE) 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.
Table 9-8 lists the supported settings for COPY.
Table 9-8 Copy settings
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, subsequent modification level 5 (8.7.0.155), or 2.0 release level 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, for more information:
SCRATCH
ALWAYS/
NEVER/
NONTLDY
Control the replication of logical volumes in the scratch category:
If a keyword4 of ALWAYS is specified, all logical volumes regardless of the category are replicated in the grid the same as the previous code level.
If a keyword 4 of NEVER is specified, no logical volumes in the scratch category are replicated in the grid.
If a keyword 4 of NONTDLY is specified, only the logical volumes in the scratch category with Time Delayed copy policy aren’t replicated in the grid. The logical volumes with other copy modes are still replicated.
 
The request is supported only when all the clusters in the grid have the code level of 8.32.X.X or later. The default value is ALWAYS.
TIMEOUT
value
Volume Copy Timeout Time
This is the timeout value in minutes for logical volume copies between clusters to complete. The allowed values for copy timeout are 30 - 999 minutes.
Link failover settings
If a second keyword of LINK is specified, the cluster modifies how to react in a link failure during a remote mount.
Table 9-9 shows the supported settings for LINK.
Table 9-9 LINK settings
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 uses the failover capability in a link failure during a remote mount.
Keyword4 of DISABLE removes the failover capability.
The default behavior is ENABLE.
Delexp (Delete Expire) count settings
In response to a request where a composite library is specified, the Delete-Expire setting is modified as described in Table 9-10.
Table 9-10 Delete-Expire setting
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.
Existdel Settings
In response to this request where a distributed library is specified, the cluster modifies how to handle the data of E (Exist) copy mode volume. See Table 9-11.
Table 9-11 Existdel Settings
Keyword3
Keyword4
Description
CRITERIA
 
STALE/
ALWAYS/
NONE
Delete E (Exist) copy mode volume at mount/demount.
STALE: Only delete E copy mode volume when it is inconsistent.
ALWAYS: Always delete E copy mode volume if all other non-E copy mode sites are consistent.
NONE: Never delete consistent or inconsistent E copymode volumes.
The request is supported only when all clusters in the domain have the code level of 8.31.x.x or later. The default is STALE.
WHEN
ATCLOSE/
AUTO
This is the setting to determine when E copy mode volumes that satisfy the condition set by the “CRITERIA” keyword can be deleted. E copy mode volume is deleted at the timing based on the following settings:
ATCLOSE: E copy volume is deleted at the volume mount/demount. It is the same behavior with the previous release 8.31.
AUTO: In addition to the volume mount/demount timing, TS7700 periodically checks E copy mode volume, then deletes it if it satisfies the condition set by CRITERIA. The check runs once per 24 hours and it deletes up to 100 E copy mode volumes all
at once.
The request is supported only when all clusters in the domain have the code level of 8.32.x.x or later. The default is “ATCLOSE”.
9.1.4 Library LMPOLICY command
Use the LIBRARY LMPOLICY command to assign or change a volume’s policy names outboard at the library. You can use this command only for private, library-resident volumes that are in a library that supports outboard policy management.
The processing for the LIBRARY LMPOLICY command starts the Library Control System (LCS) external services FUNC=CUA function. Any errors that the Common User Access (CUA) interface returns can also be returned for the LIBRARY LMPOLICY command. If the change use attribute installation exit (CBRUXCUA) is enabled, the CUA function calls the installation exit. This can override the policy names that you set by using the LIBRARY LMPOLICY command.
The results of this command are specified in the text section of message CBR1086I. To verify the policy name settings and to see whether the CBRUXCUA installation exit changed the policy names you set, display the status of the volume.
The syntax of the LIBRARY LMPOLICY command to assign or change volume policy names is shown in Example 9-7.
Example 9-7 LIBRARY LMPOLICY command syntax
LIBRARY|LI LMPOLICY|LP , volser ,SG= Storage Group name |*RESET*
,SC= Storage Class name |*RESET*
,MC= Management Class name |*RESET*
,DC= Data Class name |*RESET*
The following parameters are required:
LMPOLICY | LP
Specifies a request to set one or more of a private volume’s policy names in the TS7700.
Volser
Volser specifies the volume serial number of a private volume that is in a TS7700.
You must specify at least one of the following optional parameters. These parameters can be specified in any order:
 – SG={Storage Group name | *RESET*}
Specifies a construct name for the SG parameter
 – SC={storage class name | *RESET*}
Specifies a construct name for the SC parameter
 – MC={Management Class name | *RESET*}
Specifies a construct name for the MC parameter
 – DC={Data Class name | *RESET*}
Specifies a construct name for the DC parameter
If the request is successful, the construct name is changed to the requested name. If you specify the *RESET* keyword, you are requesting that OAM set this construct to the default, which is blanks.
The values that you specify for the SG, SC, MC, and DC policy names must meet the storage management subsystem (SMS) naming convention standards:
Alphanumeric and national (special) characters only
Name must begin with an alphabetical or national (special) character ($, *, @, #, or %)
No leading or embedded blanks
Eight characters or less
9.1.5 Useful DEVSERV QUERY Commands
Some of the more useful DEVSERV QUERY commands are described in this section.
DEVSERV QTAPE COMMAND
The DEVSERV QTAPE or DS QT command allows a query of the basic configuration of the SMS tape library as it has been defined in the input/output definition file (IODF). With the RDC operand, it is useful for viewing the Composite Library ID and Lib Port ID.
The following command shows the syntax:
DS QT,devnum,1,RDC
The following are the values in the command:
DS Device service
QT Query tape
devnum Device address
1 Number of devices to be displayed
RDC Read device characteristics
Figure 9-2 shows the output of a DS QT system command.
Figure 9-2 Sample DEVSERV QT command output
 
Clarification: The distributed library number or cluster index number for a given logical drive can be determined with the DS QT command. As identified in Figure 9-2, the response shows LIBPORT-ID 01 for logical drive 9600. LIBPORT-ID 01 is associated with Cluster 0. The association between distributed libraries and LIBPORT-IDs is discussed in 5.4.1, “Defining devices through HCD” on page 187.
From the DS QT command in Figure 9-2, you can derive the LIBRARY-ID for the composite library and the LIBPORT-ID of the logical control unit (LCU) presenting the logical device.
The real device type of the physical devices is unknown to the host, and DEVSERV always shows 3592 as DEVTYPE. The LIBID field identifies the composite library ID associated with the device.
 
Tip: You can get the real device type from the Host Console Request function
LI REQ,<distributed library name>,PDRIVE in the distributed library.
DEVSERV QLIB,CATS Command
The command DS QLIB,CATS allows you to view and change logical VOLSER categories without need to initial program load (IPL) the system, but be careful when you use this command. Example 9-8 shows how to list all of the categories used in a system.
Example 9-8 Sample output of DEVSERV QLIB,CATS
DS QL,CATS
IEE459I 10.56.27 DEVSERV QLIB 626
5001 5002 5003 5004 5005 5006 5007 5008 5009 500A 500B 500C 500D
500E 500F
After you have the actual categories, you can change them. To perform that task, change the first 3 digits of the category. However, the last digit must remain unchanged because it represents the media type.
Example 9-9 shows the command that changes all categories to 111 for the first 3 digits.
Example 9-9 Sample output of DEVSERV QLIB,CATS(111*)
DS QL,CATS(111*)
IEE459I 10.57.35 DEVSERV QLIB 899
1111 1112 1113 1114 1115 1116 1117 1118 1119 111A 111B 111C 111D
111E 111F
Ensure that this change is also made in the DEVSUPxx PARMLIB member. Otherwise, the next IPL reverts categories to what they were in DEVSUPxx. For a further description of changing categories, see 9.5, “Effects of Changing Categories” on page 595.
DEVSERV QLIB,LIST Command
Example 9-10 shows how you list all of the active composite libraries using the DS QL,LIST command. The QLIB command uses the LIBRARY-IDs (LIBIDs), not the TAPE LIBRARY NAME that was used in the D SMS,LIB command.
Example 9-10 DEVSERV QLIB,LIST
DS QL,LIST
IEE459I 09.39.33 DEVSERV QLIB 933
The following are defined in the ACTIVE configuration:
*BA062 *CA045 *BA060 *BA045 *BA003 *BA031 *BA032 *BA002 *BA039 *BA038
*BA010 BA066 BA051 BA004
 
Note: The asterisks in the QLIB displays indicate libraries that are attached to the host.
For a complete description of all of the DS QLIB commands, see Appendix D, “DEVSERV QLIB command” on page 841.
9.1.6 Scratch volume recovery for logical volumes
If you determine that a volume was mistakenly returned to scratch, you can sometimes return the volume to private status to recover its contents. If EXPIRE HOLD has been ENABLED, the volume will not be reused before the EXPIRE time has been reached. The method to recover depends on the tape management system used. In general, change the status volumes from scratch to private, and change the expiration date by adding at least one week to prevent the Tape Management System from returning the volume to scratch during the next few days. Further details about how to recover a logical volume scratched in error follow.
Checking volser to determine if it has been reused already
The first step in determining if a volume can be recovered is to check that the VOLSERs that you want to recover have not already been reused as SCRATCH mounts. Issue the
D SMS,VOL(volser) command for each volume that you want to check on. See Example 9-11.
Example 9-11 Checking if VOLSERs are still available
D SMS,VOL(A0000P)
CBR1180I OAM tape volume status: 095
VOLUME MEDIA STORAGE LIBRARY USE W C SOFTWARE LIBRARY
TYPE GROUP NAME ATR P P ERR STAT CATEGORY
A0000P MEDIA2 *SCRTCH* HYDRAG S N N NOERROR SCRMED2
USE ATR of S indicates that the volume is still in SCRATCH status and has not yet been reused. Therefore, you have a chance to recover the volume contents if there is a consistent copy in the TS7700. If at this point the display for this command says USE ATR of P, it has been reused and you cannot recover the contents of the volume using the normal procedures.
Checking for a consistent copy of the volume
The second step in determining if a volume can be recovered is to check that the VOLSERs that you want to recover have a consistent copy that resides in the TS7700 somewhere. The best command to use to check field-known consistent copies is the LI REQ,LVOL command, as shown in Example 9-12.
Example 9-12 Checking for a consistent copy
LI REQ,HYDRAG,LVOL,A0000P
 
LOGICAL VOLUME INFORMATION V4 .1
LOGICAL VOLUME: A0000P
MEDIA TYPE: ECST
COMPRESSED SIZE (MB): 627
MAXIMUM VOLUME CAPACITY (MB): 4000
CURRENT OWNER: 00001
.
CATEGORY: 0022
LAST MOUNTED (UTC): 2014-10-02 15:29:28
LAST MODIFIED (UTC): 2014-10-02 15:29:04
LAST MODIFIED VNODE: 00
LAST MODIFIED DEVICE: 000B
TOTAL REQUIRED COPIES: 1
KNOWN CONSISTENT COPIES: 1
If KNOWN CONSISTENT COPIES is zero, you cannot recover this volume because it has been DELETE EXPIRED already.
Changing STATUS of scratched volumes to MASTER
The next step in recovering the volumes is to change the status from SCRATCH back to MASTER. The next steps will vary depending on your tape management system (TMS). If your TMS is DFSMS Removable Media Manager (DFSMSrmm), you might use DFSMSrmm to search on a volume string.
Then put all of the scratch volumes matching that string into a file with a TSO subcommand to change their status back to MASTER, and set an Expiration Date to some future value (to prevent the next run of DFSMSrmm Housekeeping from sending the volume back to SCRATCH), as shown in Example 9-13.
Example 9-13 Changing status
//STEPA EXEC PGM=IKJEFT01
//SYSTSPRT DD DUMMY
//RMMCLIST DD DSN=DENEKA.RMMCV,
// DISP=(NEW,CATLG,DELETE),
// SPACE=(CYL,(2,2),RLSE),
// UNIT=SYSDA
//SYSTSIN DD *
PROF NOMSGID
RMM SV VOLUME(A*) OWNER(*) LIM(1) HOME(HYDRAG) STATUS(SCRATCH) -
CLIST('RMM CHANGEVOLUME ',' STATUS(MASTER) EXPDT(14355)
/*
The output in the RMMCLIST DD is as follows:
READY
RMM CHANGEVOLUME A0000P STATUS(MASTER) EXPDT(14355)
Use the job control language (JCL) shown in Example 9-14 to run the previously generated CLIST. This can be done in the same job as the RMM SV command if no editing of the generated list was needed to remove volumes without a consistent copy found. (Altering the status of such volumes to MASTER needlessly uses a scratch volser, because the volume contents have already been expire deleted.)
Example 9-14 JCL for CLIST
//STEPB EXEC PGM=IKJEFT01,DYNAMNBR=60
//SYSTSPRT DD DSN=DENEKA.RMMCV.OUT,
// DISP=(NEW,CATLG,DELETE),
// SPACE=(CYL,(10,2),RLSE),
// UNIT=SYSDA
//SYSTSIN DD DISP=SHR,
// DSN=DENEKA.RMMCV
The D SMS,VOL command can now be used to verify that the VOLSER was changed from S to P, as shown in Example 9-15.
Example 9-15 Verify the change
D SMS,VOL(A0000P)
VOLUME MEDIA STORAGE LIBRARY USE W C SOFTWARE LIBRARY
TYPE GROUP NAME ATR P P ERR STAT CATEGORY
A0000P MEDIA2 SGG00001 HYDRAG P N N NOERROR PRIVATE
9.1.7 Ejecting logical volumes
Logical volumes are not physical entities that can be individually removed from the library. They can also be on stacked volumes with many other logical volumes.
Because of the permanent nature of the EJECT, the TS7700 Virtualization Engine only allows you to EJECT a logical volume that is in either the INSERT or SCRATCH category. If a logical volume is in any other status, the EJECT fails. If you eject a scratch volume, you cannot recover the data on that logical volume.
 
Tip: Logical volumes that are in the error category (000E) can be moved back to the scratch category by using ISMF ALTER to move them from Scratch to Scratch category.
Tapes that are in INSERT status can be ejected by the resetting of the return code through the CBRUXENT exit. This exit is usually provided by your tape management system vendor. Another way to EJECT cartridges in the INSERT category is by using the MI. For more information, see “Delete Virtual Volumes window” on page 368.
After the tape is in SCRATCH status, follow the procedure for EJECT processing specified by your tape management system vendor. For DFSMSrmm, issue the RMM CHANGEVOLUME volser EJECT command.
If your tape management system vendor does not specify how to do this, you can use one of the following commands:
The z/OS command LIBRARY EJECT,volser
ISMF EJECT line operator for the tape volume
The eject process fails if the tape is in another status or category. For libraries managed under DFSMS system-managed tape, the system command LIBRARY EJECT,volser sent to a logical volume in PRIVATE status fails with this message:
CBR3726I Function incompatible error code 6 from library <library-name> for volume <volser>
 
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 eventually fails the eject, but the tape management system has already marked the volume as ejected.
If your tape management system is DFSMSrmm, you can use the commands shown in Example 9-16 to clean up the Removable Media Management (RMM) control data set (CDS) for failed logical volume ejects, and to resynchronize the TCDB and RMM CDS:
Example 9-16 Clean up the RMM CDS
RMM SEARCHVOLUME VOL(*) OWN(*) LIM(*) INTRANSIT(Y) LOCATION(vts) -
CLIST('RMM CHANGEVOLUME ',' LOC(vts)')

EXEC EXEC.RMM
The first RMM command asks for a list of volumes that RMM thinks it has ejected, and
writes a record for each in a sequential data set called prefix.EXEC.RMM.CLIST. The CLIST then checks whether the volume is still resident in the VTS library and, if so, it corrects the RMM CDS.
Issuing a large number of ejects at one time can cause some resource effect on the host. A good limit for the number of outstanding eject requests is no more than 10,000 per system. More ejects can be initiated when others complete. The following commands can be used on the System z hosts to list the outstanding and the active requests:
F OAM,QUERY,WAITING
F OAM,QUERY,ACTIVE
9.2 Messages from the Library
This section describes TS7700 enhanced message support and relevant messages.
9.2.1 Alert setting messages
The SETTING function provides a new set of messages. These messages are described in 9.1.3, “Host Console Request function” on page 572.
The following example shows the message format:
CBR3750I Message from library lib-id: ALxxxx message description
 
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 on the following website:
9.2.2 TS7700 Host Console Messages
Some of the TS7700 Virtualization Engine-specific messages that you might see are listed. For a complete and current list, see the appropriate volume of z/OS MVS System Messages.
Incompatibility error message
In an incompatible function error, you might see the message CBR3726I:
CBR3726I Function incompatible error code error-code from library library-name for volume volser.
In this message, an error has occurred during the processing of volume volser in library library-name. The library returned a unit check with an error code error-code, which indicates that an incompatible function has been requested. A command has been entered that requests an operation that is understood by the subsystem microcode, but cannot be run.
The explanation for the error-code can be found in the TS7700 Customer Information Center under Reference → Perform library function codes → Error recovery action codes → Function Incompatible.
Warning VTS operation degraded messages
When a VTS is operating in a degraded state, the following message is generated:
CBR3786E VTS operation degraded in library library-name
When the degradation is resolved, you see this message:
CBR3768I VTS operations in library library-name no longer degraded
Warning cache use capacity (TS7720 Virtualization Engine)
For the TS7720 Virtualization Engine, warning and critical cache free space messages are displayed:
CBR3792E Library library-name has entered the limited cache free space warning state.
CBR3794E Library library-name has entered the out of cache resources critical state.
When the cache situation is resolved, the following messages are shown:
CBR3793I Library library-name has left the limited cache free space warning state.
CBR3795I Library library-name has left the out of cache resources critical state.
Out of Physical Volumes
When a distributed library associated with a cluster runs out of scratch stacked physical volumes, operations of the TS7740 or TS7720T are affected. As part of normal processing, data is copied from cache to physical volumes in a primary pool managed by the Virtualization Engine. A copy might also be made to a physical volume in a secondary pool if the dual copy function is specified using Management Class.
Empty physical volumes are needed in a pool or, if a pool is enabled for borrowing, in the common scratch pool, for operations to continue. If a pool runs out of empty physical volumes and there are no volumes that can be borrowed, or borrowing is not enabled, operations that might use that pool on the distributed library must be suspended.
If one or more pools run out of empty physical volumes, the distributed library enters the Out of Physical Scratch state. The Out of Physical Scratch state is reported to all hosts attached to the cluster associated with the distributed library and, if included in a grid configuration, to the other clusters in the grid.
The following MVS console message is generated to inform you of this condition:
CBR3789E VTS library library-name is out of empty stacked volumes.
Library-name is the name of the distributed library in the state. The CBR3789E message remains on the MVS console until empty physical volumes are added to the library, or the pool that is out has been enabled to borrow from the common scratch pool and there are empty physical volumes to borrow. Intervention-required conditions are also generated for the out-of-empty-stacked-volume state, and for the pool that is out of empty physical volumes.
If the option to send intervention conditions to attached hosts is set on the TS7700 Virtualization Engine that is associated with the distributed library, the following console messages are also generated to provide specifics about the pool that is out of empty
physical volumes:
CBR3750I Message from library library-name: OP0138 The Common Scratch Pool (Pool 00) is out of empty media volumes.
 
CBR3750I Message from library library-name: OP0139 Storage pool xx is out of scratch volumes.
The OP0138 message indicates the media type that is out in the common scratch pool. These messages do not remain on the MVS console. The intervention conditions can be viewed through the TS7700 Virtualization Engine MI.
If the TS7740 or TS7720T is in a grid configuration, and if its associated distributed library enters the out-of-empty-stacked-volume state, operations are affected in other ways:
All copy operations are immediately suspended in the cluster (regardless of which pool has become empty).
If the cluster has a Copy Consistency Point of RUN, the grid enters the Immediate Mode Copy Operations Deferred state, and an MVS console message is generated:
CBR3787E One or more immediate mode copy operations deferred in library
library-name.
If another cluster attempts to copy a logical volume that is not resident in the cache, the copy attempt fails.
The grid prefers clusters that are not in the out-of-empty-stacked-volume state in choosing a TVC cluster, but the gird can still select a remote TVC whose cluster is in that state. If the data needed is not in the remote cluster’s TVC, the recall of the data fails. If data is being written to the remote cluster’s TVC, the writes are allowed.
However, because there might not be any empty physical volumes available to copy the data to, the cache might become full of data that cannot be copied. In this case, all host I/O using that cluster’s TVC becomes throttled to prevent a cache overrun.
Monitor the number of empty stacked volumes in a library. If the library is close to running out of a physical volume media type, either expedite the reclamation of physical stacked volumes or add more volumes. You can use the Bulk Volume Information Retrieval (BVIR) function to obtain the physical media counts for each library. The information obtained includes the empty physical volume counts by media type for the common scratch pool and each
defined pool.
If your Pool properties have a Second Media defined, and the primary media type is exhausted, the library does not go into degraded status for out of scratch.
Above Threshold Warning state
The TS7740 or TS7720T enters the Above Threshold Warning state when the amount of data to copy exceeds the threshold for the installed cache capacity for five consecutive sample periods (the amount of data to copy is sampled every 30 seconds). The TS7740or TS7720T leaves the Above Threshold Warning state when the amount of data to premigrate is below the threshold capacity for 30 consecutive sample periods. The consecutive sampling criteria is to prevent excessive messages from being created.
This state produces the following message:
CBR3750I Message from library library-name:OP0160 Above threshold for uncopied data in cache, throttling possible
9.3 EXPIRE HOLD and Scratch Processing Considerations
This topic deals with the interaction of SCRATCH processing and the EXPIRE settings on the TS7700. The topic of EXPIRE time and EXPIRE HOLD were introduced in 2.3.21, “Expired virtual volumes and Delete Expired function” on page 71, and should be referenced for a basic understanding of these two settings. We consider the following cases:
EXPIRE HOLD option is enabled and the TS7740 or TS7720T is low on scratch volumes.
EXPIRE HOLD option is enabled and Cache Utilization is beyond the desired threshold in TS7720.
EXPIRE HOLD and Low on Scratch Tapes in the TS7740 or TS7720T
The EXPIRE HOLD option is used to ensure that a logical volume sent to the SCRATCH pool cannot be reused or deleted before the grace period that is specified as the EXPIRE time has passed. This can sometimes create a problem where the library might run out of available volumes to satisfy mount requests to write new data. If the EXPIRE time has been set too long, and there are not enough logical volumes being released to keep a healthy level of SCRATCH volumes available, it might be necessary to reduce the EXPIRE time.
This change, however, only affects new volumes that are going into the SCRATCH pool. The existing volumes in the pool continue to be held until the original EXPIRE time has passed. However, if EXPIRE HOLD is cleared, these volumes can then begin to be added to the candidate list for SCRATCH mounts. Therefore, clearing the EXPIRE HOLD option immediately helps to alleviate the low on scratch condition, but it no longer protects data that has inadvertently been sent to SCRATCH. The recovery of user data on volumes in the SCRATCH pool might no longer be certain.
EXPIRE HOLD and Cache Utilization in the TS7720
When the EXPIRE HOLD option is enabled, the cache in the TS7720 and TS7720T is used up in part by holding data from logical volumes that have been sent to the SCRATCH pool. In addition to the risk of running out of logical volumes to mount, there is a risk of running out of cache in the TS7720 when AUTOREMOVAL is not enabled.
Again, EXPIRE time should be considered, and if the TS7720 is consistently running high on cache utilization, this EXPIRE time should be adjusted. In this case, the clearing of the EXPIRE HOLD setting does not immediately alleviate the high cache utilization condition. The effect of disabling the EXPIRE HOLD from the cache perspective is to enable volumes in the SCRATCH pool to begin entering the candidate list for expire delete processing.
Once per hour, a task runs in the library that processes some number of volumes from this list, and reduces cache utilization by deleting the expired volumes from cache. The number of volumes that are deleted per hour is by default 1000. The number of volumes that are moved to this candidate list is customizable (1000 - 2000), and is controlled by using the
LI REQ DELEXP COUNT command that is documented in 9.1.3, “Host Console Request function” on page 572, and in the following white paper:
Remember that EXPIRE time is the grace period that enables the recovery of the data in case of procedural error. Careful consideration needs to be made to ensure that this value is long enough to allow for such errors to be detected, and the data recovered, before the DELETE EXPIRE process removes the logical volume permanently.
9.4 Scratch Count Mismatch
There is often some discrepancy between the values reported for scratch counts from various sources. One reason for this is that the ISMF panels and the TS7700 Management Interface reports the total number of scratch volumes. However, the D SMS,LIBRARY command only reports the number of usable scratch volumes.
When EXPIRE HOLD is in effect, the total number of scratch volumes differs from the total number of usable SCRATCH volumes, because volumes for which the EXPIRE time has not yet elapsed are not eligible to be mounted. For this reason, the most accurate source of scratch counts for a TS7700 is always the D SMS,LIBRARY report.
9.5 Effects of Changing Categories
As was discussed in 4.3.6, “Partitioning the TS7700 Virtualization Engine between multiple hosts” on page 152 through 4.3.8, “Library names, Library IDs, and port IDs” on page 153, categories are assigned according to the DEVSUPxx parmlib member on the host that performs cartridge entry processing. These categories can be changed dynamically using the DEVSERV QLIB,CATS command, and modified in the DEVSUPXX member.
Special consideration should by given to the effects that the change will have on the host system. The most common problem is that all of the logical volumes in the scratch pool belong to the initially defined categories, and requests for scratch mounts begin to fail with CBR4196D error code 140169.
There are several ways to resolve such an issue. If the categories were changed because there is a desire to partition the library, then a new scratch pool must be created for this host by adding a range of volumes that are accepted by the TMS. If the old scratch pool was intended to be used by this host, then the category can be updated by using the ISMF panels to ALTER the USE ATTRIBUTE of a volume or range of volumes from S (Scratch) to S (Scratch).
This has the effect of resetting the category of the volume to match the currently defined categories on the host. If a large range of volumes needs to be changed, consider using the CBRSPLCS utility to perform such a change. For more information about how to use this utility, see z/OS DFSMS Object Access Method Planning, Installation, and Storage Administration Guide for Tape Libraries, SC23-6867.
A modification of the volume entries using IDCAMS does not change categories, and should not be used for this purpose.
9.6 Library Messages and Automation
There are some messages that can be useful to automate. In particular, there are three that represent issues with the library being unable to call home. All library messages, including these three, are prefaced with CBR3750I:
OP0463: A TSSC error has occurred. The TSSC is unable to call home.
OP0625: A system reboot interrupted a call home.
OP0550: Service Call Home, TSSC was unable to generate a PMR number.
The advised action for these messages is to contact the service center and engage support to determine why the call home was being attempted.
In addition to the CBR3750I prefaced messages, there are other messages that are worth considering monitoring for. A complete list of these messages can be found on the following website:
 
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.133.127.37