II09188: CHANGES TO DB2 ADMINISTRATIVE GUIDE VOLUME 3, THAT DID NOT MAKE V3 PUBS. CONT. II07837, II08214, II08289, II08459 & II08461.

APAR status

• Closed as canceled.

Error description

• This APAR documents changes to the DB2 Administration Guide
  Volume 3 SC26488800 which did not make Version 3 GA pubs.
  Continuation of II07837, II08214, II08289, II08459 & II08461.
  5740xyr00 R310 DB2
  ===============================================================
  Version 3 Book Title: Administration Guide, Volume 3
  Pages: 7-29
  Change Description:
    Remove the following sentence from the top of page 7-29.
    It is not true.
     'You can reset the statistics collection interval and the
     origination time without stopping and starting the trace
     by using the MODIFY TRACE command.'
  ============================================================
  Version 3 Book Title: Administration Guide, Volume 3
  Pages: 7-76
  Change Description:
  The following 2 sentences in the description of the
  hiperpool CASTOUT attribute are incorrect:
    "Specifying CASTOUT as NO protects pages from being
     stolen when their usage is low.  Pages remain
     unless MVS hiperspace maintenance
     requires that the expanded storage pages
     be reconfigured out of the system"
  
  Replace the above sentences with:
  
     Specifying CASTOUT as NO tells MVS to give high
     priority to keeping the data cached in the hiperpool.
  ===============================================================
  Version 3 Book Title: Administration Guide, Volume 3
  Pages: 7-91
  
  Change Description:
  Change the formula for the Sort Pool Size calculation on
  p. 7-91 to the following:
  
     16000 x (12 + sort key length + sort data length + 4
     (if ESA hardware sort assist))
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. 3
  Pages: 7-111
  Change Description:
    Change Query 2 to account for the fact that there can
    be duplicate index names. This is a fix to INFO APAR
    II08459.
  
  Query 2:
    SELECT CLOSERULE, COUNT(*)
     FROM   SYSIBM.SYSINDEXES T1, SYSIBM.SYSINDEXPART T2
     WHERE  T1.NAME = T2.IXNAME
  |  AND    T1.CREATOR = T2.IXCREATOR
     AND    T2.PARTITION < 1
     GROUP BY CLOSERULE;
  ============================================================
  Version 3 Book Title: Administration Guide, Volume 3
  Pages: 7-118
  Change Description:
    This is a slight change to the description that appeared
    originally in Information APAR II08461.
  
  We recommend that the number of records for the active log
  be divisible by the blocking factor of the archive log
  (DASD or tape).
  
  To determine the blocking factor of the archive log,
  divide the value specified on the BLOCK SIZE field of
  installation panel DSNTIPA by 4096 (that is, BLOCK
  SIZE / 4096). Then modify the DSNTIJIN installation job
  so that the number of records in the DEFINE CLUSTER for
  the active log data set is a multiple of the blocking
  factor.  DB2 always writes complete blocks when it creates
  the archive log copy of the active log data set.
  
  If you make the archive log blocking factor evenly
  divisible into the number of active log records, DB2 does
  not have to pad the archive log data set with nulls to
  fill the block. This can prevent REPRO errors if you
  should ever have to REPRO the archive log back into the
  active log data  set, such as during disaster recovery.
  ============================================================
  Version 3 Book Title:  Administration Guide, Vol III
  Changes to chap7 page127
  
    MVS PERFORMANCE OPTIONS FOR DB2
    _______________________________
  
  You can set MVS performance options for DB2 in two ways:
  
   o   Using system resources manager (SRM)
  
       This is sometimes called "compatibility mode"
       in MVS Version 5 Release 1 or later.
  
   o   Using goal mode, for MVS Version 5 Release 1 or later.
  
     In GOAL MODE, the MVS Workload Manager (WLM) controls the
     dispatching priority based on goals you supply.
     Workload manager raises or lowers the
     priority as needed to meet the specified goal.
     A major objective of goal
     mode is to remove the need to fine tune the
     exact priorities of every
     piece of work in the system and to focus
     instead on business objectives.
  
  There are three kinds of goals:response-time, velocity, and
  discretionary.
  Response times are appropriate goals for "end user"
  applications, such as QMF users running under
  the TSO address space
  goals, or users of CICS using the CICS workload goals.
  For more
  information about setting response time goals
  for users, see MVS/ESA Planning: Workload Management.
  
  For DB2 address spaces, VELOCITY GOALS are
  more appropriate, and velocity
  goals are what we focus on in this section.
  A small amount of the work
  done in DB2 is counted toward this velocity
  goal (most of it applies to
  the end user goal described above).
  Velocity goals indicate how quickly
  you want your work to be processed.
  
  This section describes two ways to set
  DB2 address space performance options:
  
  o   "Using SRM (Compatibility Mode)"
  o  "Using Workload Management Velocity Goals"
  
   USING SRM (COMPATIBILITY MODE)
  
  You can run in compatibility mode in MVS Version 5
  with few or no changes to
  existing SRM values.
  .
  .
  Add to page 7-129:
  
  USING WORKLOAD MANAGEMENT VELOCITY GOALS
  
  To determine velocity goals, you can start by
  determining an address space's
  velocity while you are running your systems in
  compatibility mode.  You can
  define a report performance group for the address
  space, or group of address
  spaces you are interested in, and review the RMF Monitor I
  workload activity report,
  which shows the execution velocity of that
  report performance group
  in compatibility mode.
  You should gather this information during peak work
  times.
  
  As a starting point,
  you can then define a service goal with the same value
  for the work defined in a service class.
  
  Recommendations
  
  We recommend using the workload manager default
  service class for started
  tasks (SYSSTC) for certain key address spaces,
  such as the following:
  
      VTAM address space
      IRLM address space (IRLMPROC)
      IMS control address sapce
      DB2 system services address space (ssnmMSTR)
      DB2 database services address space (ssnmDBM1)
      DB2 distributed data facility address space (ssnmDIST)
      PCAUTH address space     (see note1 for explanation)
  
  For other address spaces, start with velocity
  goals that are similar to what
  you are currently running in compatibility mode.
  If you need to change a
  goal, changing the velocity by 2 or 3% is
  not noticeable.  Velocity goals
  don't translate directly to priority.
  Higher velocity tends to have higher
  priority, but this is not always the case.
  The list of dispatching priorities in Admin Guide
  under title "Setting Address Space Priority"
  can help you
  determine the relative importance of
  various address spaces when setting
  velocity goals.
  
   Other Considerations
  
   o   When running with CICS Version 4 Release 1 or later,
       or with IMS Version
       5 Release 1 or later, both of which use workload
       manager, the velocity goals for CICS and IMS regions
       are not used except during startup or
       restart.  After transactions begin running, SRM
       ignores the CICS or IMS
       velocity goals and assigns priorities based on
       the goals of the
       transactions that are running in the regions.
  
   o   Workload manager uses the processor dispatching
       priority to set the I/O
       priority.  Goal mode does not use the IPS PARMLIB
       member.
  
   o   SRM dynamically manages storage isolation to meet
       the goals you specified.
  .
  Note1 :  (LJY 2000/01/20 W/T PMR 43805,010,618)
  If PCAUTH is set to discretionary priority, DB2 TCB (DSNYAUTH)
  may not be resumed after it is suspended for the PCAUTH local
  lock. This could cause application to hang (slow performance)
  when CPU utilization is high.
  Looking at application at time of hang we always see that
  TCB is waiting in csect DSNYAUTH + x'12C' within a WAIT SVC.
  
  
  
  ============================================================
  Version 3 Book Title: DB2 Administration Guide, Volume 3
  Pages: 7-167
  Change Description:
  
   The description of the RESOURCE TIMEOUT field of
   installation panel DSNTIPI includes a list of operations
   and their associated timeout multipliers.  Add the command
   STOP DATABASE to this list, and indicate that the
   multiplier is 10.
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. 3
  Pages:  7-196
  Change Description:
   Add the following to the description of the QUERYNO column:
  
  FETCH statements do not each have an individual
  QUERYNO assigned to them.
  Instead, DB2 uses the QUERYNO of the DECLARE CURSOR
  statement for all corresponding FETCH
  statements for that cursor.
  =============================================================
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• CLOSED FOR DB2INFO USE
  MVS SRM/WLM DISPATCHER DISPATCH PRIORITY
  Note: The JCL DPRTY parm of the EXEC statement can be altered to
        increase or decrease the dispatching priority of the
        address space to be assigned to a JOB.  The parm has 2
        associated values (v1,v2).  V1 ia a multiple of 16 and
        v2 is an additive value.  The max priority is 255.  This
        max value would be set as:  DPRTY=(15,15)  where v1=15
        and v2=15.  So,  (15x16)+15=255  ..  If you wanted to
        code a lower value like 222, you would set:  DPRTY=(13,14)
        where  v1=13 and v2=14. So, (13x16)+14=222
          See your associated  MVS/JCL Reference  for information.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels