II10645: CHANGES TO DB2 UTILITY GUIDE & REFERENCE SC26-3395-00 THAT DID NOT MAKE V4.1 GA PUBS. CONTINUED IN II09160 & II10826.

APAR status

• Closed as canceled.

Error description

• 5740xyr00 DB2 R410 V4    continued in II09160 & II10826
  This APAR documents changes to the DB2 Utility Guide and
  Reference SC26-3395-00 which did not make Version 4.1 GA pubs.
  ===============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 2-64
  Change Description:
  
  The following change will appear in the COPY section.
  Replace this statement:
  
  "If you issue TERM UTILITY while COPY is in the active or
  stopped state, the table space is put in copy pending
  status."
  
  With this statement:
  
  "If you issue TERM UTILITY while COPY is in the active or
  stopped state, a "T" record is inserted in SYSIBM.SYSCOPY.
  When you run COPY, it does not allow an incremental image
  copy if the "T" record exists."
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 2-89
  Change Description:
     In the text for the last example under "Loading
     Partitions", add the following as the third sentence:
  
  "The RESUME YES option placed before the PART option
  inhibits concurrent partition processing while the
  utility is running."
  
  Following the current last example, add the following new
  text and example:
  
  "The following example allows partitioning independence
  when loading more than one partition concurrently.
      LOAD DATA INDDN SYSREC LOG NO
      INTO TABLE DSN8410.EMP PART 2 REPLACE"
  
  Page: 2-104
  
  Change Description:
  
  In the option description for RESUME, replace the second
  and third sentences with the following new paragraph:
  
  "Attention: Specifying LOAD RESUME (rather than PART
  integer RESUME) causes the LOAD utility to drain the
  table space, which can inhibit concurrent processing
  of separate partitions.  If you want to process other
  partitions concurrently, specify PART integer RESUME."
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 2-93
  Change Description:
  
  The following addition will appear in the "Improving
  Performance" section of LOAD:
  
  "Use one LOAD DATA statement when loading multiple tables
  in the same table space. Follow the LOAD statement with
  multiple INTO TABLE WHEN statements."
  ============================================================
  Version 4 Book Title:  Utility Guide and Reference
  Pages: 2-105
  Change Description:
  
  Add the following sentence to the description
  of the LOG NO option of the LOAD utility:
  
  Some logging can occur in the BUILD phase if the index
  is a TYPE 2   NPI and is being concurrently accessed
  either by SQL being done on  a different partition of
  the same Tablespace or by an Utility being run on a
  different partition of the same table space.
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 2-153
  Change Description:
  The following change will appear in the RECOVER INDEX
  section:
  
  If WORKDDN is omitted and a DD card for SYSUT1 is not
  provided, RECOVER INDEX performance will improve by
  eliminating I/O for SORT.
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Pages:  2-162 ("Recovering Catalog and Directory Objects")
  Change Description:
      Replace the text following the numbered list ("16. User
      table spaces.") up to the sentence begining
      "The access method services REPRO function..." with the
      following text:
  
  Recovery of the items on the list can be done in parallel
  or included in the same job step.  However, some
  restrictions apply:
  
  1. When you recover the following table spaces or index,
     the job step in which the RECOVER statement appears
     must not contain any other utility statements.  No
     other utilties can run while the job step is running.
         - DSNDB01.SYSUTILX
         - DSNDB01.DBD01
         - All indexes on SYSUTILX
  
  2. When you recover the following table spaces, no other
     utilities can run while the RECOVER TABLESPACE utility
     is running.  Other utility statements may exist in the
     same job step.
         - DSNDB06.SYSCOPY
         - DSNDB01.SYSLGRNX
         - DSNDB06.SYSDBAUT
         - DSNDB06.SYSUSER
         - DSNDB06.SYSDBASE
  
  Attention: If the logging environment requires adding or
  restoring active logs, restoring archive logs, or
  performing any action that affects the log inventory
  in the BSDS, you should recover the BSDS before catalog
  and directory objects.  For information on recovering
  the BSDS, see Section 4 (Volume 1) of the Administration
  Guide.
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 2-168
  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 4 Book Title: Utility Guide and Reference
  Page: 2-172
  Change Description:
  
  In the RECOVER TABLESPACE section, the following change
  will appear:
  
  If you use a list of tablespaces, the valid keywords are:
  DSNUM, TORBA, TOLOGPOINT, LOGONLY, and LOCALSITE/RECOVERYSITE.
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 2-174
  Change Description:
  
  The following change will appear in the RECOVER TABLESPACE
  section:
  
  The LRSN is a string of 12 hexadecimal digits and
  is reported by the DSN1LOGP utility.
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 2-176
  Change Description:
  
  The following change will appear in the RECOVER TABLESPACE
  section. The first line of the "Sample JCL and Control
  Statements" example has been changed to read:
  
  //UTILSAMP EXEC PGM=DSNUTILB,REGION=4096K,
  ============================================================
  Version 4 Book Title:  Utility Guide and Reference
  Pages:  2-177
  Change Description:
  
  Delete the paragraph which begins with the words "An
  authority other than installation SYSADM or installation
  SYSOPR ..."
  
  Replace the paragraph with the following:
  
  An authority other than installation SYSADM or installation
  SYSOPR can receive message DSNT500I, "resource unavailable,"
  while trying to reorganize a tablespace in the catalog
  or directory. This can happen when the DSNDB06.SYSDBAUT
  or DSNDB06.SYSUSER catalog table space or one of the
  indexes on these table spaces is unavailable.
  If this problem occurs, run the REORG TABLESPACE utility
  again using an authorization ID with the installation
  SYSADM or installation SYSOPR authority.
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Pages: 2-182
  Change Description:
  
  Add the following paragraph to the "Reorganizing the Catalog
  and Directory" section of REORG:
  
  When you REORG the SYSCOPY table space with the LOG NO option,
  DB2 places the table space in copy pending status. Take a
  full image copy of the table space to remove the copy
  pending status before continuing to reorganize the catalog
  or directory table spaces.
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 2-187
  Change Description:
  
  In the "Reorganizing Partitioned Table Spaces" section of
  REORG, modify the information as follows:
  
  "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 Appendix G
  (Volume 2) of Administration Guide."
  ============================================================
  Version 4 Book Title:  Utility Guide and Reference
  CHAP3 Page14
  Change Description:
  
  On 3-14, correct the DSNJU003 syntax diagram to include missing
  DDF options.
  
            <----------------------------
  >--DDF------|-LOCATION=locname------|---------------
              |-LUNAME=luname---------|
              |---PASSWORD=password---|
              |----NOPASSWD-----------|
              |---GENERICLU=gluname---|
              |----NGENERIC-----------|
  
  On page 3-21, insert the following option descriptions
  after the description of NOPASSWD:
  
  | GENERICLU=gluname
  |   Replaces the value of the DB2 GENERIC LUNAME subsystem
  |   parameter in the BSDS.
  
  | NGENERIC
  |   Changes the DB2 GENERIC LUNAME to binary zeros in
  |   the BSDS, indicating that no VTAM generic LU name
  |   support is requested.
  ============================================================
  Version 4 Book Title:  Utility Guide and Reference
  Pages:  3-31
  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 4 Book Title:  Utility Guide and Reference
  Pages:  3-32
  Change Description:
  Add the following introductory sentence to
  "Running DSNICHKR on a Valid Table Space"
  
    |  Run DSNICHKR only on a valid table space.
  ============================================================
  continued in II10826
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• CLOSED FOR DB2INFO RETENTION
  

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