The SRM Component of CPExpert
(Applies only to Compatibility Mode)
The SRM Component processes and analyzes members of
to detect potential problems with the values specified in the
SYS1.PARMLIB members, and to build SAS data sets containing the
Information currently is collected from the following members of SYS1.PARMLIB:
The SRM Component applies dozens of expert system rules against the keywords and parameter values contained in the SYS1.PARMLIB members to determine whether potential problems exist with the specifications.
The SRM Component analyzes the SYS1.PARMLIB members individually, searching for specific problems with the parameter settings.
The SRM Component also analyzes the SYS1.PARMLIB members collectively, searching for problems caused by inconsistent parameter values between the members.
For example, some settings in IEAIPSxx may be inconsistent with the values specified in IEAOPTxx. The SRM Component will detect situations such as this and alert you to a potential problem.
The SRM Component produces a narrative report, describing potential problems and listing the specific parameters which may be inappropriately specified.
If you have a good understanding of the SRM parameters and how the SRM functions, some of the rules may seem superficial.
However, each rule in the SRM Component corresponds to a problem that has been observed at client installations, has been reported in the professional literature, or has been described in IBMLink documents.
Why do these problems arise? The SRM is complex, the concepts in the MVS Initialization and Tuning Guides are difficult to appreciate, and SRM parameters often have unexpected results.
Papers are regularly presented at professional conferences to describe newly-discovered performance problems or solutions resulting from experiences with the System Resources Manager.
For example, the MVS Initialization and Tuning Guides (prior to MVS/ESA SP4.2) advise that the ISV value for TSO Period 2 should be the sum of the DUR values of both TSO Period 1 and TSO Period 2 to avoid Exchange Swaps in Period 2. As Rule SRM132 explains, following this advice can result in unnecessary Exchange Swaps.
Most installations are unaware that following the advice in the Initialization and Tuning Guides can result in unnecessary swapping, and ISV values are improperly set for TSO Period 2 at many installations.
This example illustrates that some of the rules might be applicable even for the most sophisticated installation, and we believe that many of the rules will be of benefit to most installations.
The SRM Component User Manual provides a discussion of each potential problem it discovers with the SYS1.PARMLIB specifications. The discussion describes the implications of the finding, suggests alternatives, and provides specific references to IBM documents or other publications where the potential problem is described. The references are updated with each new release of MVS.
The SRM Component builds SAS data sets to describe the keywords and parameters contained in the SYS1.PARMLIB members. These SAS data sets help guide the other CPExpert components when they analyze the performance of your system.
Many installations specify different IEAICS/IEAIPS combinations for different operations shifts. You can specify any combination of IEAICS/IEAIPS members to the SRM Component and it will build SAS data sets for each combination.
When analyzing data contained in your MXG, SAS/Service Vision, or MICS performance data base, CPExpert examines information in SMF Type 72 records to identify the correct IEAICSxx/IEAIPSxx/IEAOPTxx combination. CPExpert dynamically selects the correct SYS1.PARMLIB information to guide its analysis of system performance.
The SRM Component of CPExpert is not applicable to MVS Goal Mode. With Goal Mode, most of the SYS1.PARMLIB members analyzed by the SRM Component are not applicable. Consequently, most of the analysis that would be performed by the SRM Component cannot be done. The remaining functions of the SRM Component have been incorporated into the WLM Component of CPExpert.
Return to main page
Last updated by Don Deese on 06/15/2001.