The D2 display shows the BLDL/FIND requests that CA PMO processed. A BLDL/FIND request is an instruction that initiates a directory search for a member of a library. There is a difference between the number of BLDL/FIND requests issued on the system and the number of library directories that are searched in response to each request. For example, suppose that a BLDL/FIND request is issued for a member in the following concatenation of libraries:
//PDSDD DD DSN=SYS1.LIB1 // DD DSN=SYS1.LIB2 // DD DSN=SYS1.LIB3
This concatenation contains the names of three libraries. A search for a member starts in the directory of the first library listed in the concatenation and it stops when the member is found. In this example, if the member is in SYS1.LIB1, there is one library directory search for this BLDL/FIND request. If the member is in SYS1.LIB2, there are two library directory searches for this request. And if the member is in SYS1.LIB3, or if it is not in any of the libraries, there are three library directory searches for this request. But regardless of the number of library directories that are searched, there is only one BLDL/FIND request in this search.
The following screen illustrates a sample D2 display:
PMO 4.4 ( Active ) Sys=XE23 23MAR10:09:26:31 PMO Active Time= 1.514 hrs D2 BLDL/FIND Request Activity Count Per Hour % % Total BLDL/FIND Requests = 2,190 1,444 100 100 LNKLST Requests = 1,395 918 64 Member Not Found = 85 54 Private Requests = 795 522 36 Member Not Found = 351 230 * ExtBLDL Reissues = 253 Trim= 397 * Probable Optimizations: Yes = 250 No = 3 PMO Assisted BLDL/FIND Requests = 1,485 979 100 68 LNKLST Requests = 1,015 670 68 Member Not Found = 0 Private Requests = 470 310 32 Member Not Found = 209 137 Other BLDL/FIND Requests = 705 464 100 32 LNKLST Requests = 380 248 54 Member Not Found = 85 54 Private Requests = 325 212 46 Member Not Found = 142 94
The row headings on the D2 display are described in the following:
All requests issued since CA PMO became active.
Requests for members of LNKLST libraries.
Requests where the sought-for member was not found.
To calculate the number of times that a member was found, subtract the number of times that a member was not found from the count shown directly above it.
Requests for members of private libraries.
Count of BLDL reissues using an enhanced DEB chain trimming code.
Count of actual DEB chain link reductions.
Probable Optimizations DESERV exit activity count.
The Yes value is a count of BLDL's optimized and the No value is a count of BLDL's not optimized.
Requests that involve a library that CA PMO manages. For example, suppose that a BLDL/FIND request is issued for a member in the following concatenation of libraries:
//PDSDD DD DSN=SYS1.LIB1 // DD DSN=SYS1.LIB2 // DD DSN=SYS1.LIB3
Suppose CA PMO manages SYS1.LIB3, but it does not manage the other two libraries. The search starts with the directory of the first library in the concatenation. If an entry for the member is found in the directory of SYS1.LIB1, this is not a CA PMO-assisted BLDL/FIND request. If an entry for the member is found in the directory of SYS1.LIB3, this is a CA PMO-assisted request.
Search requests that CA PMO did not help to resolve (see PMO Assisted BLDL/FIND Requests).
If this field shows many LNKLST requests where the sought-for member was not found, you should specify the parameter RETNF=YES.
The column headings on the D2 display are described in the following list:
The number of requests that have been issued.
The number of requests per hour. CA PMO divides the amount of time that it has been active into the total number of BLDL/FIND requests to determine this rate.
A breakdown of requests into the percentage for LNKLST library members, and the percentage for private library members.
A breakdown of total requests into the percentage that CA PMO handled and the percentage it did not handle.
|
Copyright © 2011 CA.
All rights reserved.
|
|