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

APAR status

• Closed as canceled.

Error description

• 5740xyr00 DB2 R410 V4
  continued in II09160, II10645, II12139
  This APAR documents changes to the DB2 Utility Guide and
  Reference SC26339500 which did not make Version 4.1 GA pubs.
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 2-7
  
  In Table 1 "Data Sets Used by Utilities," delete the
  entire row containing DD Name SORTLIB.
  
  The following change will appear in the "Invoking DB2
  Online Utilities" section. Add a new footnote in Table 1,
  "Data Sets Used by Online Utilities":
  
  Add footnote 5 to occurrences of LOAD, REORG, and CHECK DATA
  under SORTOUT and SYSUT1.
  
  Footnote 5:
  "Data sets can not be shared between SORTOUT and SYSUT1.
  Sharing these data sets can cause unpredictable results."
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Pages: 2-89
  In the "Loading Partitions" section, add the following note
  prior to the first example:
  
  "Attention: If you are not loading columns in the same order
  as in the CREATE TABLE statement, you must code field
  specifications for each INTO TABLE statement."
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 2-101
  
  Add information to the DISCARD row in Table 22 as follows:
    -------------------------------------------------
     DISCARD     CURRENT   SYSMAP and SYSERR     4
  |                        SORTOUT and SYSUT1    8
                 PHASE     SYSMAP and SYSERR     4
  |                        SORTOUT and SYSUT1    8
    -------------------------------------------------
  
  Add this footnote:
  
  8. The SYSUT1 data set is required if the target table
     space is segmented or partitioned.
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 2-105
  
  In the "Option Descriptions" section of LOAD LOG NO, add
  the following paragraph:
  
  "If the table space has a TYPE 2 nonpartitioning
  index, some logging might occur in the build
  phase if DB2 is accessing another partition for
  an SQL statement or utility. Also, DB2 logs index structure
  changes to allow recoverability of the nonpartitioning
  index in case an abend occurs."
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Pages: 2-169
  
  In RECOVER TABLESPACE, "Retaining Tape Mounts" section,
  change the examples to emphasize user-provided variables.
  For the first example, the data set names COPY1 and COPY2
  will appear in italics, as well as the volume serial
  number. The second example will show the image copy data set
  names IC1, IC2 and IC3 in italics.
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 2-180
  
  In the section "Calculating the Size of the Work Data Sets,"
  delete the first bullet item in the list after the
  sentence "For compressed data, double again the space
  allocated for the sort work data sets if you use the
  following REORG options:"
  
  The list now reads:
    "* UNLOAD PAUSE without KEEPDICTIONARY
     * UNLOAD CONTINUE without KEEPDICTIONARY"
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Pages: 2-180
  
  In "Before Running REORG," add the following subsection:
  
  "Catalog and Directory Table Spaces:
  Before running REORG on a catalog or directory table space,
  you must take an image copy. Be aware that for the
  DSNDB06.SYSCOPY, DSNDB01.DBD01, and DSNDB01.SYSUTILX table
  spaces, REORG scans logs to verify that an image copy is
  available. If the scan of logs does not find an image copy,
  DB2 will request archive logs."
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Pages: 2-221
  
  Add the following paragraph to the end of the
  "Reporting Recovery Information" section:
  
  | For image copies of partitioned table spaces taken with
  | the DSNUM ALL option, we recommend that you run REPORT
  | RECOVERY DSNUM ALL. If you run REPORT RECOVERY DSNUM ALL
  | CURRENT, DB2 reports additional historical information
  | dating back to the last full image copy taken for the
  | entire table space.
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 2-233
  
  The following addition will appear in Table 57 of
  the RUNSTATS section:
  
  SYSTABSTATS
  CARD   Total number of rows in the partition.
  NPAGES Total number of pages on which rows of this partition
         appear.
  ===============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 2-233
  
  In Table 57, "DB2 Catalog Columns Used to Select Data
  Access Paths," delete the row for CLUSTERED under
  SYSINDEXES.
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 3-6
  The following change will appear in the DSNJU003 (Change Log
  Inventory) chapter.
  
  Under "Making Changes for Active Logs," within the
  "Enlarging" subsection, change the introductory sentence
  to read:
  
  "One of the following procedures must be used when DB2 is
  inactive (down)."
  
  Delete the entire first procedure within that section.
  
  The second sentence of this section now reads: "Use the
  following procedure if you can use the access method
  services REPRO command:"
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Pages: 3-14 and 3-16
  
  Delete the PORT=port and RESPORT=resport options in the
  DDF statements section of the DSNJU003 syntax diagram.
  
  Also delete the PORT, RESPORT, and NGENERIC keywords and
  definitions from the Option Descriptions section on
  page 3-16. *Keep* the NGENERIC keyword and option
  description that appears on p. 3-21.
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Pages: 3-16, 3-21
  
  In DSNJU003 (Change Log Inventory), change the syntax
  diagram keyword GENERICLU to GENERIC.
  
   DDF statement
  
              <_,_________________________
   >>__DDF_______LOCATION=locname_______|____________________
                |_LUNAME=luname_________|
                |_ _PASSWORD=password_ _|
                | |_NOPASSWD__________| |
                |_ _GENERIC=gluname_____|
                | |_NGENERIC__________| |
                |_PORT=port_____________|
                |_RESPORT=resport_______|
  
  Also, change the Option Description keyword GENERICLU to
  GENERIC.
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 3-45
  
  The following change will appear in the DSN1COPY chapter,
  under "Naming the Output Data Set."
  
  Add the following sentence to the end of the fourth bulleted
  paragraph:
  
  "If SYSUT1 is an image copy of a whole partitioned table
  space, SYSUT2 should be the name of the first data set of
  the table space. DSN1COPY allocates all of the target data
  sets. However, the target data sets must be previously
  defined using IDCAMS. Specify the NUMPARTS parameter to
  identify the number of partitions in the whole table space.
  
  (add to end of 6th bulleted paragraph):
  "However, the target data sets must be previously defined
  using IDCAMS."
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Pages: 3-49 and 3-50
  
  Make the following changes in the SYSXLAT DD Card description
  section of "Creating the JCL to Run DSN1COPY."
  
  In the third paragraph:
  
    Only the first two records are required for a type 1 index
  | space; for a type 2 index, the SYSXLAT data set must contain
  | the index fan set OBID in addition to the DBID and ISOBID.
  
  Add this note after: "The following SQL statements
  yield the above information:"
  
  | Note: The example for type 2 indexes yields the above
  |       information, along with an additional column of data.
  
  Change the second example label to:
  
  | For type 1 index spaces:
  
  Add the following example:
  
  | For type 2 index spaces:
  |    SELECT DBID, ISOBID, OBID FROM SYSIBM.SYSINDEXES
  |       WHERE NAME='index_name'
  |         AND CREATOR='creator_name';
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 3-54
  
  In the Option Descriptions section of DSN1COPY, add the
  following for the RESET parameter:
  
  "If you do not specify RESET when copying a table space
  from one DB2 system to another, a down-level ID check may
  result in abend reason code 00C2010D when the table space
  is accessed. For more information about down-level
  detection, see Section 4 (Volume 1) of Administration
  Guide."
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 3-68
  Change LUWID option portion of syntax diagram as follows:
  
      <------------------
  >----------------------'----------------------------------->
       |               |
       --LUWID(luwid))--
  
  ============================================================
  Version 4 Book Title: Utility Guide and Reference
  Page: 3-83
  Change the "Stopping DSN1SDMP" heading to "Stopping or
  Modifying DSN1SDMP Traces".
  
  Modify this section to include the following information:
  
     If you must stop DSN1SDMP, use the STOP TRACE command.
  
     If DSN1SDMP does not finish execution, it can be stopped
     by an operator STOP TRACE command, for example:
  
          -STOP TRACE=P CLASS(32)
  
  |  DSN1SDMP is designed to execute as a standalone batch
  |  utility without requiring external intervention from the
  |  MVS console operator or other programs. During execution,
  |  DSN1SDMP issues an IFI READA request to obtain the data
  |  from the OPn buffer, and a -Stop Trace command to
  |  terminate the original trace started by DSN1SDMP.
  
  |  A -STOP TRACE or -MODIFY TRACE command entered from an
  |  MVS console against the trace started by DSN1SDMP causes
  |  immediate abnormal termination of DSN1SDMP processing.
  |  The IFI READA function terminates with an appropriate IFI
  |  termination message and reason code. Additional error
  |  messages and reason codes associated with the DSN1SDMP
  |  STOP TRACE command will vary depending on the specific
  |  trace command entered by the console operator.
  
  |  If the console operator terminates the original trace
  |  using the -STOP TRACE command, the subsequent STOP TRACE
  |  command issued by DSN1SDMP fails.
  
  |  If the console operator enters a -MODIFY TRACE command,
  |  the modified trace might also be terminated by the STOP
  |  TRACE command issued by DSN1SDMP if MODIFY TRACE processing
  |  completes before the DSN1SDMP command is issued.
  ============================================================
  continued in II12139
  

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