8464ch11_Monitoring.fm Draft Document for Review February 7, 2020 3:15 pm A response record consists of the database fields that are defined, as shown in Example 11-4  for Volume A03599. The overall length of each record is 400 bytes with blank padding after  the last field, as needed. Example 11-4 Sample response record for VOLSER A03599 A03599,2,FULL,READ-WRITE,2007-05-05-06.40.08.030061,2007-05-04-13.45.15.918473,... Tip:  Generating the response might take several minutes to complete, depending on the  number of volumes that is requested and how busy the TS7700 cluster is at the time of the  request.  A database is maintained on each TS7700 cluster that contains status information about the  logical volumes that are defined to the grid. Two key pieces of information are whether the  cluster contains a valid copy of a logical volume and whether the copy policy for the volume  indicates that it must have a valid copy.  Copy audit information This request runs an audit of the databases on a set of specified TS7700 distributed libraries  to determine whether any volumes do not have a valid copy on at least one of them.  If no further parameter is specified, the Audit checks whether a logical volume has a copy on  the specified cluster. No validation occurs regarding whether that cluster should have a copy.  To consider the copy modes, specify a second parameter  COPYMODE .  If the COPYMODE option is specified, whether the volume is supposed to have a copy on the  distributed library is considered when determining whether that distributed library includes a  valid copy. If COPYMODE is specified and the copy policy for a volume on a specific cluster is  “S”, “R”, “D”, or “T”, that cluster is considered during the audit.  Using COPYMODE If the copy policy for a volume on a specific cluster is “N”, the volume’s validity state is ignored  because that cluster does not need to have a valid copy. The request then returns a list of any volumes that do not have a valid copy, subject to the  copy mode if the COPYMODE option is specified, on the TS7700 clusters specified as part of  the request.  The specified clusters might not have a copy for the following reasons: GLYPH<SM590000> The copy policy that is associated with the volume did not specify that any of the clusters  that are specified in the request were to have a copy and the COPYMODE option was not  specified. This issue might occur because of a mistake in defining the copy policy or  because it was intended.  GLYPH<SM590000> The copies were not yet made from a source TS7700 to one or more of the specified  clusters. This issue can result because the source TS7700 or the links to it are  unavailable, or because a copy policy of Deferred was specified and a copy was not yet  completed when the audit was run.  For example, volumes that are used in a disaster recovery test must be on the disaster  recovery TS7700 only and  not  on the production TS7700s. If the request specified only  the production TS7700 tape drives, all of the volumes that are used in the test are returned  in the list. 658  IBM TS7700 Release 5.0 Guide