Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

SM2R1 analysis routine

The SM2R1 routine analyzes the data collected by the SM2 monitoring program and stored in a system-global SM2 output file. The result of the analysis is output in the form of charts and/or tables containing statistical data or is stored in a transfer file for further processing by the corresponding programs.

Users

SM2R1 is not confined to privileged users. Any user who has access to the SM2 output file and SM2R1 can use the analysis routine.

Control file

SM2R1 is a table-based analysis routine. The analysis control data is stored in the SYSDAT.SM2.<ver>.MTFILE control file. A valid control file is supplied with SM2 and SM2R1. SM2R1 can be executed only with the associated SYSDAT.SM2.<ver>.MTFILE.

File to be analyzed

The SM2 output file can be processed by SM2R1 only in SAM format, i.e. PAM files must be converted to SAM files using SM2U1.

Text file

SM2R1 is written in PL/1 and therefore requires the PL/1 text file for error exits. This file is supplied together with SM2 and SM2R1.

Output file

The results of an SM2R1 run are written to a file which can be output on the printer by means of the PRINT-DOCUMENT command. The output file can be freely selected.

The period of time for which the SM2 output file is to be analyzed is called the analysis period in the following. An analysis period may encompass several SM2 monitoring cycles plus interleaved periods of time during which no monitoring took place.

ISO format

SM2R1 outputs all dates in ISO format (yy-mm-dd) and expects input of the date in the same format. June 13, 2012, for example, has to be entered as follows: 12-06-13. Dates can also be entered in the form yyyy-mm-dd.

SM2R1 result lists

  1. Header page

  2. Monitoring environment of first analyzed session (see "Monitoring environment output")

  3. System configuration output (see PRINT-CONFIGURATION statement)

  4. Actual analysis results; these are broken down as follows:

    • Time series and statistics (REPORTS)
      For statistics, the average, minimum, maximum and standard deviation values are supplied for the whole output period.
      For time series, the average, minimum, maximum and standard deviation values are supplied for the whole output period. In addition to the statistics display, these mean values are displayed in charts as a function of the time.

    • Summaries
      The essential data of a monitoring cycle is summarized.

    • Task statistics (TASK STATISTICS)

    • Queue statistics (QUEUE STATISTICS)

    • HSMS statistics (HSMS-STATISTICS)

    • Automatic performance analysis

  5. If the SM2 output file contains multiple sessions then the monitoring environment for the last analyzed session is output.

  6. Information on the analysis run (see "Monitoring environment output")

  7. Table of contents (see "Table of contents for SM2R1")

SM2R1 transfer file

The values determined by SM2R1 are transferred to a so-called SM2R1 transfer file (SM2R1 data interface). For each SM2R1 monitoring value requested the following information is written to this transfer file:

  • mean value for the overall analysis period

  • maximum value for the overall analysis period

  • minimum value for the overall analysis period

  • standard deviation for the overall analysis period

  • number of subcycles in the analysis period

  • mean values of the individual subcycles.

Structure of the transfer file:

  • The first record of the transfer file contains information pertaining to the analysis period and the duration of the subcycle. This record is given the record identifier TIM2.

  • The next record of the transfer file contains general system information pertaining to the SM2 monitoring environment. This record is given the record identifier SYST.

  • Afterwards, the configuration valid for the analysis period is output. The configuration requires several records. These records are given the record identifier CONF.

  • This is followed by “pairs of records” each of which provides a description (first part) and monitoring data (second part) of an SM2R1 monitored variable. The records which contain the description are given the identifier DSCR. The records which contain the monitoring information are given the identifier DATA. In addition, these record pairs supply the report number and the monitored variable number for the respective SM2R1 monitored variable (for a description of the records see section "SM2R1 transfer filerecords").

Interruption-free clock resetting

When time-series charts are created, “double” time stamps that are the result of the local clock being set back are left out.
In task, queue and HSMS statistics, the ELAPSED TIME of the titles is determined from the UTC time.

The records of the transfer file are not affected by the interruption-free clock resetting, since the “double” time stamps are already left out when the time-series charts are created.

Automatic performance analysis

SM2R1 detects bottlenecks in the system by means of the automatic performance analysis facility and reports them to the user via appropriate messages. This considerably reduces the need for large quantities of paper, as is normally required for diagnosing a performance problem: after the resource causing the bottleneck has been identified by SM2R1 during the automatic analysis, the manual file analysis can restrict itself to the data relevant to this resource.

The automatic analysis can be started on its own or in conjunction with other SM2R1 analyses.

The specification of one or more analysis periods is also valid for the performance analysis, i.e. only the selected periods are checked for bottlenecks.

Alongside the records that are present by default, automatic analysis also analyzes the records from the monitoring programs SERVICETIME, SYSTEM, TASK and, if present, VM.

Automatic analysis is activated by means of the START-AUTOMATIC-ANALYSIS statement.

When Live Migration takes place, a new session with the new server is started in the SM2 output file. Automatic performance analysis across the session boundary leads to separate analyses for the server concerned.

Table of contents for SM2R1

SM2R1 outputs a table of contents at the end of the entire analysis. This table begins on a new page under the header TABLE OF CONTENTS and now comprises four levels.
The individual levels can be identified by the depth of indentation.

Level 1

specifies the individual runs of the SM2 output file (a normal case includes only one run).The following lines are output:

FIRST EVALUATION

SECOND EVALUATION

etc.

The SM2R1 title page is output to indicate a run. The following header also belongs to level 1:

EVALUATION STATISTICS ...

It supplies information about the SM2 output file.

Level 2

refers to general data, the configuration and subanalyses.

Possible entries for this level:

 1. DATA FOR FIRST SESSION ...
 2. DATA FOR LAST SESSION ...
 3. CONFIGURATION-TABLE ...
 4. QUEUE STATISTICS ...
 5. AUTOMATIC ANALYSIS ...
 6. TIME-SERIES EVALUATION ...
 7. STATISTICS EVALUATION ...
 8. TASK STATISTICS ...
 9. HSMS STATISTICS ...
10. SUMMARY STATISTICS ...

The first five entries for level 2 do not include any subelements of level 3.

Levels 3 and 4

provide more detailed subanalyses of the entries (headers) output in level 2.

Example of a table of contents

                         T A B L E  O F  C O N T E N T S
                         ===============================
FIRST EVALUATION                                                                   1
   DATA FOR FIRST SESSION                                                          1
   CONFIGURATION TABLE                                                             2
   SUMMARY STATISTICS                                                             25
      ACTIVITY REPORT                                                             25
      PCS REPORT                                                                  28
   QUEUE STATISTICS                                                               31
   TASK STATISTICS                                                                40
      CPU-TIME AND #IOS SORTED, FIRST 20 TASKS                                    40
      CLASS-5 + CLASS-6-PAGES-SORTED, FIRST 20 TASKS                              41
      CATEGORIES                                                                  42
   TIME-SERIES EVALUATION                                                         50
      *CPU                                                                        50
         UTILIZATION NORMED                           (REPORT   1)                50
         SUM SVC CALLS                                (REPORT 137)                51
      *IO                                                                         52
         IO'S FOR DEVICE CLASSES                      (REPORT   3)                52
      *DISK                                                                       53
         UTILIZATION                                  (REPORT 124)                53
         IO'S                                         (REPORT 125)                54
         PAM IO'S                                     (REPORT 127)                55
      *SERVICETIME                                                                56
         DURATION OF IO'S FOR DEVICE                  (REPORT 231)                56
      *CHANNEL                                                                    57
         UTILIZATION                                  (REPORT  10)                57
   AUTOMATIC ANALYSIS                                                             59
EVALUATION STATISTICS                                                             60