II10644: CHANGES TO DB2 ADMINISTRATION GUIDE VOL. 2 SC26-3265-00, THAT DID NOT MAKE V4.1 GA PUBS. CONT. IN II09143, II09480 & II10880.

APAR status

• Closed as canceled.

Error description

• 5740xyr00 DB2 R410 V4 continued in II09143, II09480 & II10880
  This APAR documents changes to the DB2 Admin. Guide Vol. 2
  SC26326500 which did not make Version 4.1 GA pubs.
  ==============================================================
  Version 4 Book Title: Administration Guide, Volume 2
  Pages: 5-90
  Change Description:
   In the section 'How DB2 Determines DSMAX' change the third
   bullet as follows:
   o Let indexes be the number of indexes per table. The
  |  installation CLIST sets this variable to 2.
  ============================================================
  Version 4 Book Title: Administration Guide, Vol. 2
  Pages: 5-97
  Change Description:
      This is a slight change to the description that appeared
      originally in Information APAR II09143.
  
  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 4 Book Title: Adminstration Guide, Vol. 2
  Pages: 5-126
  Change Description:
  
  The first paragraph under the section 'Thread Reuse for
  Database Access Threads' erroneously states a requirement
  for RELEASE(COMMIT) to allow DBAT reuse. This paragraph is
  removed:
  
  To prepare database access threads for reuse, specify
  ACQUIRE(USE) and and RELEASE(COMMIT) when you bind the plan.
  Packages do not have a separate ACQUIRE option. ACQUIRE(USE)
  is implicit when a program executes from a package.
  
  The remaining paragraph in that section is ok.
  ============================================================
  Version 4 Book Title: Administration Guide, Volume 2
  Pages:  5-278
  Change Description:
  
    The example for hybrid join should be:
  
      T1     0     3     1   null  null null null
      T2     2     6     2    3     3     1    2
  ============================================================
  Version 4 Book Title: Administration Guide Vol. 2
  Pages: x-84 and x-85
  Change Description: rewritten pages x-84 & x-85
  
  | Reading Complete Log Records (IFCID 0306)
  
  | The major benefits for using IFCID 0306 are:
  |
  | - IFCID 0306 can request DB2 to decompress log
  |   records if compressed, before passing them to the
  |   return area of your IFI program.
  | - In Data Sharing , DB2 merges the log records in
  |   timestamp sequence from all active members of the data
  |   sharing group before returning them to your program.
  | - IFCID can retrieve log records from the archive data sets.
  | - Complete log records are always returned.
  
  To use this new IFCID, use the same call as described
  in "Reading Specific Log Records (IFCID 0129)"
  on page ...  IFCID 0306 must appear in the IFCID area.
  | IFCID 0306 returns complete log records and the spanned
  | record indicators in bytes 2 will have no meaning, if
  | present.  Multi-segmented control interval log records
  | are combined for a complete log record.
  
  Specifying the Return Area:  For IFCID 0306 requests,
  | your program's return area must reside in ECSA key 7
  | storage.  The IFI application program must set the
  | eye-catcher to 'I306' at offset 4 in the Return
  | Area before making the IFCID 0306 call. There is an
  | additional 60 byte area that must be included after
  | the 4-byte length indicator and the 'I306'
  | eye-catcher. This area is used by DB2 between
  | successive application calls and must not be
  | modified by the application.  The return area
  | mapping is documented later in this section.
  
  | The IFI application program needs to run in
  | supervisor state to request the ECSA key 7 return
  | area.  The return area storage size need be a
  | minimum of the largest DB2 log record returned plus
  | the additional area defined in DSNDQW04.  Minimize
  | the number of IFI calls required to get all log data
  | but do not over use ECSA by the IFI program.  The
  | other IFI storage areas can remain in user storage
  | key 8.  The IFI application must be in supervisor
  | state and key 0 when making IFCID 0306 calls.
  
  | Qualifying Log Records:  To retrieve IFCID 0306 log
  records, your program must intitialize certain fields
  in the qualification area mapped by DSNDWQAL.
  These qualification fields are described here:
  
  WQALLMOD
          In this 1-byte field, specify one of the following
          modes:
  
          D
  |           Retrieves the single log record whose RBA
  |           value and member id is specified in
  |           WQALLRBA.  Issuing a D request while holding
  |           a position in the log, causes the request to
  |           fail and terminates the log position held.
  
          F
  |           Used as a first call to request log records
              beyond the LRSN or RBA specified in WQALLRBA
              that meet the criteria specified in WQALLCRI.
  
          H
              Retrieves the highest LRSN or log RBA in the
              active log.  The value is returned in field
              IFCAHLRS of the IFI communications area (IFCA).
  |           There is no data returned in the return area
  |           and the return code for this call will indicate
  |           that no data was returned.
  
          N
              Used following mode F or N calls to request any
              remaining log records that meet the criteria
              specified in WQALLCRI. As many log records as fit
              in the program's return area are returned.
  
          T
              Terminates the log position that was held
              by any previous F or N request.  This
              allows held resources to be released.
  
          Mode R is not used for IFCID 0306.
  
          For both F or N requests, each log record
          returned contains a record-level feedback area
          recorded in QW0306L. The number of log records
  |       retrieved is in QW0306CT.  The ending log RBA or LRSN
  |       of the log records to be returned is in QW0306ES.
  
  WQALLRBA
          In this 8-byte field, specify the starting
          log RBA or LRSN of the log records to be
          returned. For IFCID 0306, this is used on
          the "first" option (F) request to request
          log records beyond the LRSN or RBA specified
  |       in this field.  Determine RBA or LRSN value from
  |       H request.  For RBAs, the value plus one should be
  |       used.  For IFCID 0306 with D request of WQALLMOD,
  |       the high order 2 bytes must specify member id and the
  |       low order 6 bytes contain the RBA.
  
  WQALLCRI
          In this 1-byte field, indicate what type of log
          records you want:
  
          X'00'   Tells DB2 to retrieve only log records
                  for changed data capture and unit of
                  recovery control.
  
          X'FF'   Tells DB2 to retrieve all types of log
  |               records.  Use of this option canretrieve
  |               large data volumes and degrade DB2.
  
  WQALLOPT
          In this 1-byte field, indicate whether you want
          the returned log records to be decompressed.
  
          X'01'
                  Tells DB2 to decompress the log records
                  before they are returned.
  
          X'00'
                  Tells DB2 to leave the log records in
                  the compressed format.
  
  |A typical sequence of IFCID 0306 calls is:
  |
  |WQALLMOD=H This is only necessary if you want to find the
  |          current position in the log. The lrsn/rba is
  |          returned in IFCAHLRS. The return area is not used.
  |
  |WQALLMOD=F The WQALLLRBA, WQALLLCRI AND WQALLLOPT
  |          should be set. If 00E60812 is returned you
  |          have all the data for this scope. You should
  |          wait a while before issuing another WQALLMOD=F
  |          call.  In data sharing, log buffers are flushed
  |          when the F request is issued.
  |
  |WQALLMOD=N If the 00E60812 has not been returned you
  |          issue this call until it is.  You should wait
  |          a while before issuing another WQALLMOD=F call.
  |
  |WQALLMOD=T This should only be used if you do not want to
  |          continue with the WQALLMOD=N before the end is
  |          reached. It has no use if a position is not held
  |          in the log.
  
  |IFCID 0306 Return Area Mapping
  
  |IFCID 0306 has a unique return area format.  The
  |first section is mapped by QW0306OF instead of the
  |writer header DSNDQWIW. See Appendix E for details.
  ============================================================
  Version 4 Book Title:  Administration Guide, Volume 2
  Pages:  X-133, X-137 to X-138
  Change Description:
  
  Change the first paragraph of Appendix F.  Sharing Read-Only
  Data on page X-133 to this:
  
  DB2 allows you to read common DB2 data from a number of DB2
  subsystems using shared read-only data.  With shared
  read-only data, you can share the physical data for a given
  database among DB2 subsystems, but one DB2 subsystem has
  exclusive control over updating the data in that shared
  database.  The database in the system that can update
  data is called the owner.  The same database in any other
  system is called a reader.  A system can only read the
  data in a reader.  Data cannot be read from a reader while
  the owner is being updated.
  
  Change the third paragraph of Appendix F.  Sharing Read-Only
  Data on page X-133 to this:
  
  We recommend that you use full read-write data sharing,
  rather than shared read-only data.  For information on
  full read-write data sharing, see Data Sharing:  Planning
  and Administration.
  
  Change the first paragraph of "Excluding Data Sets"
  on page X-137 to this:
  
  For read-only data sharing, you must exclude from sharing
  the bootstrap data set, the catalog and directory, and all
  user data sets that are not shared resources.  Also
  exclude the MVS system catalog.  To exclude these VSAM
  data sets from sharing, add entries to your GRS SYSTEMS
  exclusion resource name list.  Use TYPE(GENERIC) entries
  with QNAME(SYSDSN) and RNAME(data set high level qualifier).
  
  Add this paragraph after the above paragraph:
  
  If you enable full data sharing at a later time, you must
  remove the bootstrap data set, the catalog, and the
  directory from the exclusion resource name list.
  
  Delete the sections entitled "Including Data Sets" and
  "Converting Hardware Reserves" on page X-138.  Keep
  the pointer to "MVS/ESA Planning:  Global Resource
  Serialization."
  
  Add the following index entry for the Tune GRS for DB2
  section:
  GRS (global resource serialization)
    tuning for read-only data sharing
  ============================================================
  Version 4 Book Title:  Administration Guide, Volume 2
  Pages:  X-161
  Change Description:
    Remove the following sentence form the top of page X-161.
    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.'
  ============================================================
  This APAR is continued in II10880.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• CLOSE FOR INTERNET VIEWING
  

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