Let CA PMO run for another hour, then start up PMOMON.
Follow the procedure outlined in Steps 2 and 3 in the previous section, Performing Initial Tuning, to determine if the larger value for MLSIZE has lowered the number of sorts per hour and raised the percentage of LNKLST searches that CA PMO resolves. Re-tune MLSIZE if necessary.
If CA PMO is automatically choosing what private libraries to manage (the default), look at the D6 display. If "NUMADDED Exceeded" is higher than 1%, raise the value for that parameter. If "Virt Stg Exhausted" is higher than 1%, see the section Specifying an Appropriate Amount of Visual Storage in this chapter for the correct procedure.
Review the D7 and D8 displays to see the amount of I/O that CA PMO is eliminating. If you think CA PMO could be eliminating more I/O, check the D9 display to be sure that you have not specified the EXCLAUTO parameter for any libraries that have a large amount of directory search activity. If you cannot change the EXCLAUTO parameter, you may want to specify the INCLPRVT parameter or the F PMO,INCLPRVT command to include additional libraries for CA PMO management.
If you are manually telling CA PMO what private libraries to manage (that is, if you specified EXCLAUTO=* in your parameter data set), include the first 40 libraries on the D9 screen.
