II09176: CHANGES TO DB2 COMMAND & UTILITY REFERENCE SC26-4891-00 THAT DIDNOT MAKE V3 GA PUBS. CONT. II07612, II07864, II08602 & II10828.

APAR status

• Closed as canceled.

Error description

• THIS INFO. APAR DOCUMENTS CHANGES TO THE DB2 COMMAND & UTILITY
  REFERENCE SC26489100 WHICH DID NOT MAKE VERSION 3 GA PUBS.
  CONTINUED IN APAR II07612, II07864, II08602 & II10828.
  5740XYR00 R310 DB2
  ================================================================
  Version 3 Book Title: Command and Utility Reference
  Page: 36
  Change Description:
  The following sentence in the description of the
  CASTOUT(NO) option of the -ALTER BUFFERPOOL command
  is incorrect:
    "Prevents MVS from discarding data cached in the
     hiperpool unless expanded storage pages are
     reconfigured out of the system"
  
  Replace the above sentence with:
    "Tells MVS to assign a high priority to keeping
     the data cached in the hiperpool"
  ============================================================
  Version 3 Book Title:  DB2 Command and Utility Reference
  Pages:  61, 186
  Change Description:
  
    Under the description of the CACHESIZE option for
    BIND PLAN and REBIND PLAN, change the sentence:
     "For additional information on choosing a CACHESIZE, see
      section 7 (Volume 3) of Administration Guide"
  
    to:
     "For additional information on determining an optimal
      cache size, see Section 4 of Application Programming
      and SQL Guide".
  
    Also, add the following sentence to the end of the
    the "Authorization" section of BIND PACKAGE,
    BIND PLAN, REBIND PACKAGE, and REBIND PLAN:
     "For more information on the authorization required
      to execute BIND/REBIND PLAN/PACKAGE, see
      Section 5 (Volume 2) of Administration Guide.
  ============================================================
  Version 3 Book Title: Command and Utility Reference
  Pages: 96
  Change Description:
  
  Add new paragraph to "Displaying DB2 Catalog Tables" under
  Usage Notes as follows:
  
   If DISPLAY DATABASE LOCKS is issued on the
   catalog (DSNDB06),
   the user may see a lock held on SYSDBASE
   with the correlation ID
   020.DBCMD_05 or 020.DBCMD_06.
   This simply indicates the lock that
   DISPLAY DATABASE itself needs and is normal.
  ============================================================
  Version 3 Book Title: Command and Utility Reference
  Pages: 169
  Change Description:
    Modify the third bullet under the description of MODIFY
     TRACE to delete an incorrect statement about MODIFY
     beginning a new statistics interval. The bullet should
     read as follows:
  
     'Writes statistics records.'
  ============================================================
  Version 3 Book Title: Command and Utility Reference
  Pages: 212
  Change Description:  Replace first paragraph under
    "Restricted Mode (RO and UT) with:
  
  When a START DATABASE command for a restricted mode (RO
  and UT) takes effect depends upon whether applications
  are started after -START DATABASE has completed, or whether
  applications are executing at the time the command is issued.
  For applications started after -START DATABASE has completed,
  access restrictions are effective immediately.  For
  applications executing at the time -START DATABASE is issued,
  the access restrictions take effect when a subsequent claim
  is requested or the application is allowed to run to
  completion.  Whether the application is interrupted by the
  -START DATABASE command depends upon various factors.
  These factors include the ACCESS mode specified on the
  -START DATABASE command, the type of drain activity, if any,
  on the table space or partition, and whether there are held
  cursors on the table space or partition.
  ============================================================
  Version 3 Book Title: Command and Utility Reference
  Pages: 225
  Change Description:
  
  In Table 20, Classes for DB2 Trace Types, change
  the description of audit trace class 6 to:
  
  Bind time information about SQL statements that involve
  audited objects
  ============================================================
  Version 3 Book Title:  Command and Utility Reference
  Pages:  322
  Change Description:
  Replace this paragraph:
  
  It is a good idea to first copy the stopped table
  space to ...
  
  With this paragraph:
  
  It is a good idea to first copy the stopped table
  space to a temporary data set using DSN1COPY.
  Use the DB2 naming convention for the copied
  data set.  Run DSN1CHKR on the copy, which frees
  the actual table space for restart to DB2.
  ============================================================
  Version 3 Book Title:  Command and Utility Reference
  Pages: 325
  Change Description:
  
    Add a new third paragraph under Example 1:
     "The RIDs in Step 5 of the example are for example
      purposes only.  Using them results in a error
      message.  Change them to the actual
      RIDs to be checked."
  ============================================================
  Version 3 Book Title: Command and Utility Reference
  Pages: 330
  Change Description:
  
   Insert the following paragraph under "Usage Notes."
   Place the paragraph after the one for Message DSN1941.
  
    Running DSN1COMP on a Table Space with Identical Data:
    If you run DSN1COMP on a table space in which the data is
    the same for all rows, message DSN1941I is issued and
    DSN1COMP does not compute any statistics.
  ============================================================
  Version 3 Book Title: Command and Utility Reference
  Pages: 401, 404, 418, 441
  Change Description:
  p. 401, MODIFY:
  
  Change the first sentence of the first paragraph to
  "The MODIFY online utility with the RECOVERY option
  deletes records from the SYSIBM.SYSCOPY catalog table,
  related log records from the SYSIBM.SYSLGRNG directory
  table, and entries from the DBD."
  
  p. 418, "Keyword and Parameter Descriptions":
  
  Second paragraph under TABLESPACE, add the sentence:
  "You cannot recover catalog or directory table spaces in a
  list."
  
  p. 441, "Dropped Tables":
  
  First paragraph: add "See "Reclaiming Space in the DBD" on
  page 404 for actions to take when you drop a table."
  
  Delete the second paragraph, including the list.
  
  p. 404, "Usage Notes," add two new notes:
  
  Reclaiming Space in the DBD
  ___________________________
  To reclaim space in the DBD when you drop a table, use the
  following procedure:
  
  1. Commit the drop
  2. Run the REORG utility on the tablespace
  3. Run the COPY utility to make a full image copy of the
     table space
  4. Run MODIFY with the DELETE option to delete all previous
     image copies.  MODIFY reclaims space only if there are
     SYSCOPY rows to delete.
  
  Improving REORG Performance after Adding a Column
  _________________________________________________
  If you add a column to a table space and the record was
  previously fixed-length, DB2 treats the record as
  variable-length. As a result, the REORG utility decompresses
  the rows of the table space during the UNLOAD phase and then
  compresses them again during the RELOAD phase. To remedy
  this for subsequent REORGs use the following procedure:
  
  1. Run the REORG utility on the tablespace
  2. Run the COPY utility to make a full image copy of the
     table space
  3. Run MODIFY with the DELETE option to delete all
     previous image copies.  MODIFY will return the record
     to fixed-length status only if there are SYSCOPY
     rows to delete.
  ============================================================
  Version 3 Book Title: Command and Utility Reference
  Pages: 409
  Change Description:
  
    Add a new paragraph in the "Usage Notes" section
    after the "Restrictions" paragraph:
  
      If Too Many Table Spaces Are Specified
      --------------------------------------
      If QUIESCE is run on a list of more than
      1165 table spaces, it
      terminates with a return code of 8 as shown:
  
      DSNU000I    DSNUGUTC - OUTPUT START FOR UTILITY,
                             UTILID = QUIESCE
      DSNU046I    DSNUGPSP - UTILITY STATEMENT IS TOO
                             LONG OR TOO COMPLEX
      DSNU012I    DSNUGBAC - UTILITY EXECUTION TERMINATED,
                             HIGHEST RETURN CODE=8.
  ============================================================
  Version 3 Book Title: Command and Utility Reference
  Page: 424
  Change Description:
  The following change will appear in the RECOVER TABLESPACE
  section. Adding a new paragraph in Fallback Recovery:
  
  In a JES3 environment, fallback can be accomplished by
  issuing a JES3 "cancel,s" command at the time the allocation
  mount message is issued. This could be necessary in the
  case where a volume is not available or the given volume
  is not desired.
  =============================================================
  Version 3 Book Title:  Command and Utility Reference
  Pages: 433
  Change Description:
  
           Replace the paragraph beginning "The size of the
           sequential data set..." with the following:
  
    The size required for the unload data set varies depending on
    the options used for REORG.
  
      1) If you use REORG with UNLOAD PAUSE or CONTINUE and
         with KEEPDICTIONARY (assuming a compression dictionary
         already exists), the size of the unload data set, in
         bytes, can be roughly calculated as the VSAM hi-used
         RBA for the table space, where the hi-used RBA can
         be obtained from the associated VSDAM catalog.
  
      2) If you use REORG UNLOAD ONLY, or UNLOAD PAUSE or
         CONTINUE without KEEPDICTIONARY, the size of the
         unload data set, in bytes, can be calculated as
         the maximum row length multiplied by the number
         of rows.  The maximum row length is the row length,
         including the 6 byte record prefix, plus the length
         of the longest clustering key.
  
         If there are multiple tables in the table space,
         the formula is:
  
            Sum over all tables (row length * number of rows)
  ============================================================
  Version 3 Book Title: Command and Utility Reference
  Page: 434
  Change Description:
  
  In the "Reorganizing Partitioned Table Spaces" section of
  REORG, add the following information:
  
  "If you reorganize a single partition, all indexes of the
  table space are affected. Depending on how disorganized the
  nonpartitioned indexes are, you might want to reorganize them
  as well. For more information about when to reorganize, see
  Section 7 (Volume 3) of Administration Guide."
  ============================================================
  Version 3 Book Title: Command and Utility Reference
  Pages: 457-8
  Change Description:
  
    Example 1, line 3 is changed to:
       VERIFY OFFSET 50 DATA X'A00'
    Example 1, line 4 is changed to:
       REPLACE OFFSET 50 DATA X'D11'
  
    Example 5, step 1, line 3 is changed to:
       VERIFY OFFSET X'0A' DATA X'00002422'
    Example 5, step 1, line 4 is changed to:
       REPLACE OFFSET X'0A' DATA X'00000000'
    Example 5, step 2, line 3 is changed to:
       VERIFY OFFSET X'06' DATA X'00002521'
  ==============================================================
  Version 3 Book Title:  Command and Utility Reference
  Pages: 479
  Change Description:
  
           Add the following to the second paragraph under
           "Concurrency and Compatibility ":
  
    However, since STOSPACE updates the catalog, concurrent
    STOSPACE utility jobs or other concurrent applications that
    update the catalog could cause timeouts and deadlocks.
  ============================================================
  continued in APAR II10828
  

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