II05830: CHANGES TO COMMAND AND UTILITY MANUAL THAT DID NOT MAKE R230 GA PUBS

APAR status

• Closed as canceled.

Error description

• This apar documents changes to the DB2 Command and Utility
  Reference which did not make the GA R230 Pubs.  5740xyr00
  sc26-4378-02 ac26437802
  ============================================================
  In the Command and Utility Reference on page 46 under
  CURRENDATA, paragraph that begins "Ambiguous cursors are
  those not defined....", should be replaced with the
  following paragraph:
  
    A database cursor is ambiguous if it is neither declared
    for FETCH ONLY or UPDATE, nor the target of a WHERE
    CURRENT OF clause on an SQL UPDATE or DELETE statement and
    the package has dynamic SQL capability.  All other
    database cursors are non-ambiguous.
  ---------------------------------------------------------
  On page 278 in the section on DSN1CHKR DSNDB06.SYSSTR will
  be added to the following paragraph.
  ...
  DSN1CHKR should not be run on table spaces DSNDB06.SYSCOPY,
  DSNDB06.SYSGPAUT,DSNDB06.SYSPAKAGE, DSNDB06.SYSUSER,
  DSNDB01.SCT02, DSNDB01.SPT01, and DSNDB06.SYSSTR.
  ============================================================
  In the Command and Utility Reference on page 118 under the
  DSNH (TSO CLIST) command, General DSNH CLIST parameter
  table, ENTRY parameter - under the first bullet, remove the
  first sub-bullet, "PLICALLA if the run value is IMS".
  the run value is IMS".
  ============================================================
  Book Title:    Command and Utility Reference (SC26-4378-02)
  Page Number:   109
  Change Description:
  
  Change the Usage Note "Protected Threads":
  
  Protected Threads:  The DSNC MODIFY TRANSACTION command
  changes the value of the THRDA parameter of the
  DSNCRCT TYPE=ENTRY or TYPE=POOL macro.  You can decrease the
  value of THRDA; however, no threads are terminated until the
  number of threads reaches THRDMAX-2, and there are inactive
  threads to terminate.
  ================================================================
  Book Title:    Command and Utility Reference (SC26-4378-02)
  Page Number:   237
  Change Description:
  
  Add under "Online Utility Restart":
  
  If you restart a utility, you may need to change the DISP
  parameters to ensure that the work data sets are not
  inadvertently deleted if a restart problem occurs.  For
  example, when restarting a utility after DB2 has come down,
  if you receive a return code of '8', work data sets with a
  disposition of DISP=(MOD,DELETE,CATLG) are lost.  Specifying
  the disposition as DISP=(MOD,CATLG,CATLG) prevents the deletion
  if the restart fails.
  ================================================================
  Book Title: Command and Utility Reference (SC26-4378-02)
  Page Number: p. 253
  
  Add the following new paragraph after the paragraph beginning
  with "Incremental Copy and LOAD or REORG:  If a LOAD..."
  and ending with "...is not allowed."
  
     "If a LOAD or REORG operation is successful, and if the LOG
     option was set to YES, the copy pending status is not set
     for this table space.  However, a full image copy is
     recommended.  An incremental image copy is not allowed.
  ================================================================
  Book Title:    Command and Utility Reference
  Page Number:   319
  
  Add to the FORMAT UNLOAD option of the LOAD utility description:
  
  Do not add columns or change column definitions of tables
  between running REORG UNLOAD ONLY and LOAD FORMAT UNLOAD.
  ================================================================
  Book Title:    Command and Utility Reference (SC26-4378-02)
  Page Number:   328
  Change Description:
  
  Change the definition of FLOAT EXTERNAL in the LOAD utility
  description:
  
  FLOAT EXTERNAL(length)
  A string of characters that represent a number.  The format
  is that of an SQL floating point constant as described in
  Chapter 3 of the SQL Reference.
  ================================================================
  Book Title:    Command and Utility Reference
  Page Number:   354
  
  Add to RECOVER TABLESPACE usage notes under the sample JCL
  shown for cataloged image copies on one or more tape volumes:
  
  Not specifying the VOL parameter EXACTLY as shown above can
  result in an incomplete recovery, which can produce
  unpredictable results and abend messages.  The incomplete
  recovery might not be detected until you run RECOVER INDEX.
  ==============================================================
  Book Title:  Command and Utility Reference (SC26-4378-02)
  Page Number: p.375
  
  After the sentences "The DELETE statement operates without
  regard for referential constraints.  If you delete a parent
  row, its dependent rows remain unchanged in the table space."
  
  Change the next sentence to read:
  
     However, in the DB2 catalog and directory table spaces
     where links are used to reference other tables, deleting
     a parent row causes all child rows to be deleted as well.
  ==============================================================
  Book Title:  Command and Utility Reference (SC26-4378-02)
  Page Number: p. 362
  
  In the description of SORTDEVT, the sentence beginning with
  "If you omit SORTDEVT and a sort is required..." should be
  changed as follows:
  
  "If you omit SORTDEVT and a sort of the index keys is
  required, you must provide the DD statements that the SORT
  program needs for the temporary data sets."
  ==============================================================
  Book Title:  Command and Utility Reference (SC26-4378-02)
  Page Number: p. 368
  
  Add the following under "Dropped Tables":
  
   "If you drop a table, the space is made available only after
   all of the following:
  
   * The drop is committed.
  
   * REORG is run on the table space and there is no point in
     time recovery after the reorganization.
  
   * MODIFY is run to delete all image copies (taken before
     the reorganization) that contain rows of the dropped table.
     MODIFY reclaims space only if there are SYSCOPY rows to
     delete."
  ==============================================================
  Book Title:    Command and Utility Reference
  Page Number:  187
  
  Change Description:  Under START RLIMIT, replace the ID
  keyword description with the following:
  
  ID=id
  
      Identifies the resource limit specification table
      for the governor to use.
  
      id is the one or two identification characters
      specified when the table was created.  See
      Section 7 (Volume 3) of the Administration Guide for
      more information about resource limit specification tables.
  
  |   The full name of the table is authid.DSNRLSTid, where authid
  |   is what was specified for the RLFAUTH parameter when DB2
  |   was installed.
  
      The DEFAULT ID is the one specified in the RLFTBL parameter
      when DB2 was installed.
  ================================================================
  
  Book Title:    Command and Utility Reference
  Page Number:  241, 246, 249, 340, 344, 348, 359, 370, 383, 387
  
  Change Description: Change Authorization section for CHECK DATA,
  CHECK INDEX, COPY, MODIFY, MERGECOPY, QUIESCE, REORG,
  REPAIR, and RUNSTATS so that the sentence about SYSOPR
  is changed to the following:
  
  
  An ID with installation SYSOPR authority can also
  execute this utility, but only on a table space in the
  DSNDB01 or DSNDB06 database.
  
  
  Page number:  350
  
  For RECOVER INDEX and RECOVER TABLESPACE, the sentence should
  read:
  
  An ID with installation SYSADM or SYSOPR authority can also
  execute this utility, but only on a table space in the
  DSNDB01 or DSNDB06 database.
  
  
  Page number:  383
  
  For REORG, the sentence should read:
  
  An ID with DBCTRL or DBADM authority over database DSNDB06
  can run the REPORT utility on any tablespace
  in DSNDB01 or DSNDB06, as can any ID with installation
  Page number:  383
  
  For REORG, the sentence should read:
  
  An ID with DBCTRL or DBADM authority over database DSNDB06
  can run the REPORT utility on any tablespace
  in DSNDB01 or DSNDB06, as can any ID with installation
  SYSOPR, SYSCTRL, or SYSADM authority.
  ================================================================
  
  Book Title:    Command and Utility Reference (v2r3)
  Page Number:   358
  
  Change Description: In the RECOVER utility usage
  note "Critical Catalog Indexes", change references to
  "DSNDB06.SYSDBASE" to "DSNDB06.SYSDBAUT".
  ================================================================
  
  Book Title:    Command and Utility Reference (v2r3)
  Page Number:   364
  
  Change Description: Add a Usage Note for REORG:
  
  REORG utility section under USAGE NOTES:
  
  
  | DFSORT and SORTDATA:  When you specify SORTDATA on your
  | REORG statement, DB2 estimates how many rows are to be
  | sorted and passes this information to DFSORT on the
  | parameter FILSZ, letting DFSORT dynamically allocate the
  | necessary sort workspace.  If the table space contains
  | rows with VARCHAR columns, DB2 might not be able to
  | accurately estimate the number of rows.  If the estimated
  | number of rows is too high, and the sort work space is not
  | available, DFSORT may fail and cause an abend.
  
  | You can override this dynamic allocation of sort work-
  | space in two ways:
  
  | 1. Allocate the sort work data sets yourself with
  |    SORTWKnn DD statements in your JCL
  
  | 2. Override DB2's row estimate in FILSZ using control
  |    statements passed to DFSORT.  The following gives an
  |    example how:
  
  |    //DFSPARM DD *
  |      OPTION FILSZ=E005000
  |    /*
  
  ================================================================
  
  Book Title:    Command and Utility Reference (v2r3)
  Page Number:   261
  
  Change description:
  
  The diagram for the DDF statement of the DSNJU003 utility is
  incorrect in the DB2 Command and Utility Reference.
  There should be a comma separating the LOCATION= parameter
  and the LUNAME= parameter of the DDF statement.  If a blank
  is used as a separator between the parameters, the second
  parameter will be treated as a comment and ignored by the
  utility.
  ================================================================
  
  Book Title:    Command and Utility Reference (v2r3)
  Page Number:   318
  
  Change description: Modify description of LOAD RESUME:
  
    RESUME
        Tells whether records are to be loaded into an empty
  |     or non-empty table space.  For non-segmented table
  |     spaces, space occupied by rows that have been marked
  |     as deleted or for rows of dropped tables will not be
  |     reused.
  
        NO
        __
            Loads records into an empty table space.  If the
            table space is not empty, and you have not used
            REPLACE, a message is issued and the utility job
            step terminates with a job step condition code of 8.
  
  |         For non-segmented table spaces containing deleted
  |         rows or rows of dropped tables, better efficiency
  |         may be obtained by using the REPLACE keyword.
  
  ================================================================
  
  Book Title:    Command and Utility Reference (v2r3)
  Page Number:   385
  
  Change description:  Modify the description of REPORT RECOVERY
  output as follows:
  
  
    REPORT RECOVERY:  REPORT RECOVERY displays all the
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• This is for doc changes that occured after the GA pubs
  

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