8464ch11_Monitoring.fm Draft Document for Review February 7, 2020 3:15 pm For the Physical Volume Status Pool request,  xx  specifies the pool for which the data is to be  returned. If no physical volumes are assigned to the specified pool, that issue is indicated in  the response record. Data can be requested for pools 0 - 32. For the Cloud Volume Map request, if the total number of cloud volume map entries exceeds  4 million, the use of  xx  can provide the next 4 million entries. For example, when ‘0’ is  specified (which is equivalent to no  xx ), the first million entries that are ordered by volser are  provided in response. For point-in-time and historical statistics requests, any other characters that are provided in  the request record past the request itself are retained in the response data, but otherwise  ignored. In a TS7700 grid configuration, the request volume must be valid on only the specific  cluster from which the data is to be obtained.  Use a specific MC that includes a copy policy that is defined to indicate that only the wanted  cluster is to have a copy of the data. By ensuring that a sole copy of the request volume  exists, any virtual device address on any of the clusters in the same grid configuration can be  used to request and access the data. It is not necessary for host connectivity to exist to the  specific cluster. If an MC is used that indicates that more than one cluster is to include a valid  copy of the request volume, unpredictable response data results can occur. 11.4.4 BVIR Response data format When the request data set was written to the volume and then closed and unmounted, the  TS7700 validates the contents of the request volume when mounted again and appends the  requested data records to the data set.  Human-readable appended records can vary in length, depending on the reports that are  requested and can be 80 - 900 bytes. Binary data appended records can be variable in length  of up to 24,000 bytes. The data set is now a response data set. The appropriate block counts  in the end of file (EOF) records are updated to reflect the total number of records that are  written to the volume.  These records contain the specific response records based on the request. If the request  cannot be understood or was invalid, that issue is indicated. The record length is fixed; the  record length of each response data is listed in Table 11-4. Table 11-4 Record length of response data BVIR request Record length in bytes VOLUME STATUS  vvvvvv 640 CACHE CONTENTS 80 VOLUME MAP (PRIMARY or BACKUP) 80 POINT IN TIME STATISTICS 24000 HISTORICAL STATISTICS FOR  xxx-yyy 24000 PHYSICAL MEDIA POOLS 80 PHYSICAL VOLUME STATUS VOLUME  zzzzzz 440 PHYSICAL VOLUME STATUS POOL  xx 440 COPY AUDIT COPYMODE INCLUDE/EXCLUDE libids 80 GGM COPY STATUS/RESULT 400 652  IBM TS7700 Release 5.0 Guide