Determining system response time goals

Goal mode introduces several changes in the definition of a work request's response time. The changes more accurately reflect end-user expectations of response time.

The number of batch transactions equals number of jobs. Defining a response time goal may not be appropriate for some types of batch work, such as jobs with very long execution times. Work that is appropriate for a response time goal should have at least three transaction completions per 20 minutes of elapsed time. If there are too few completions, use a velocity or discretionary goal.

TYPRUN=HOLD and TYPRUN=JCLHOLD times are not included in batch response times.

Examples of service classes with response time goals

  • A service class representing TSO/E work with multiple periods.
    Service Class
    TSO
    Period
    1
    Response Time
    85% 0.5 second
    Importance
    1
    Duration
    400 Service Units
    Period
    2
    Response Time
    80% 1 second
    Importance
    3
    Duration
    1000 Service Units
    Period
    3
    Response Time
    60% 15 second
    Importance
    4

    Note that the percentile in period 1 and 2 refer to the transactions ending in each period, not the total TSO/E transactions.

  • A service class representing CICS® transactions.
    Service Class
    CICSHOT
    Period
    1
    Response Time
    0.5 second AVG
    Importance
    1
  • A service class representing IMS™ transactions.
    Service Class
    IMSCAT1
    Response Time
    95% .3 Second
    Importance
    1
  • A service class representing IMS transactions.
    Service Class
    OIMSCAT3
    Response Time
    5 sec AVG
    Importance
    3
Parent topic: Defining performance goals