II09145: CHANGES TO DB2 COMMAND REFERENCE SC26-3276-00, THAT DID NOT MAKE V4.1 GA PUBS.CONTINUED IN II10279.

APAR status

• Closed as canceled.

Error description

• 5740xyr00 DB2 R410 V4
  This APAR documents changes to the DB2 Command Reference
  SC26326700 which did not make Version 4.1 GA pubs.
  continued in II10279.
  ================================================================
  V4.1 Book Title: Command Reference
  Pages: 25
  Change Description:  Modify the first bullet under
  the bullet for "Recognition Character".  Begin a new
  paragraph at the sentence starting "In Version 4 of DB2,
  the command ..." and modify as follows:
  
     In Version 4 of DB2, the command prefix can be up to
     eight characters.  The default is '-DSN1'.  However,
     the majority of examples in this book assume that
     the command prefix has been defined as a hyphen (-).
     Examples involving members of a data sharing group
     demonstrate the use of multi-character command prefixes,
     such as -DB1G.
  
     Inserting a space between the command prefix and the
     command is optional.  For example, you can use either
     format:
  
         -DB1GDIS THREAD(*)
         -DB1G DIS THREAD(*)
  
     Using a space makes it easier for users to identify
     the command, especially when the command prefix has
     multiple characters.
  
     The command prefix can be defined ... (last paragraph
     stays the same).
  ============================================================
  Version 4 Book Title:  DB2 Command Reference
  Pages: 28, 102
  Change Description:
  
  On page 28, add the following paragraphs:
  
  Output from DISPLAY Commands
  
  The amount of output that you receive from a DB2 command is
  always less than 256KB.  The following factors determine the
  maximum amount of output you can receive:
  
  - The amount of storage available to your DB2 subsystem or
    to an individual command.
  
  - The environment from which you issue the DB2 command.
  
    For example, if you issue a DB2 command from an IMS
    console,   you can receive no more than 32KB out output.
  
  - For DISPLAY DATABASE, the value of the LIMIT parameter.
  
  - For DISPLAY THREAD, the number of lines of output.
  
    DISPLAY THREAD does not display more than 254 lines of
    output.
  
  On page 102, remove the statement under LIMIT that says,
  The message area cannot be greater than 256k.
  ============================================================
  Version 4 Book Title: Command Reference
  Pages: 41
  Change Description:
  
   Modify the first sentence of the second paragraph of the
   description of the MODE(QUIESCE) option of ARCHIVE LOG
   as shown here:
  
   In a data sharing environment, before archiving logs
   of any member, the option
   quiesces all active members of a data sharing group.
  |The option also ensures that each inactive
  |member had successfully quiesced its update activity and
  |resolved any indoubt units of recovery (URs) before the
  |inactive subsystem completed normal termination.
  ==============================================================
  Version 4 Book Title:  Command Reference
  Pages:  56, 48, 51, 195, 198
  Change Description:
    Under the description of the CACHESIZE option remove
    the reference to the Adm Guide from the following
    sentence:
     "For additional information on choosing a CACHESIZE, see
      Section 5 (Volume 2) of Administration Guide or
      Section 5 of Application Programming and SQL Guide"
  
    And change it to read:
     "For additional information on determining an optimal
      cache size, see Section 5 of Application Programming
      and SQL Guide".
  
    Also, on pages 48 (BIND PACKAGE), 51 (BIND PLAN),
    195 (REBIND PACKAGE), and 198 (REBIND PLAN), add
    the following sentence as the last paragraph in
    the "Authorization" section:
     "For more information on the authorization required to
      execute BIND PACKAGE (BIND PLAN, REBIND PACKAGE, REBIND
      PLAN, as appropriate), see Section 3 (Volume 1) of
      Administration Guide."
  ============================================================
  Version 4 Book Title:  Command Reference
  Pages: 71
  Change Description:
  Add a third bullet under "For more information about:"
  - The TSO/E restriction that limits the maximum number of
    packages specified in the PKLIST, see TSO/E Programming
    Services.
  ============================================================
  Version 4 Book Title:  Command Reference
  Pages: 101, 103
  Change Description:
  
  change the USE option bullet from:
  - The applications and subsystems to which the database or
    space is allocated
  to:
  - The applications and subsystems of the database or space
    which has internal DB2 resources allocated
  - The applications and subsystems of the database or space
    on whose behalf locks for the space are held or waited upon
  
  change the ACTIVE option description from:
    Limits the display to table spaces or index spaces that
    have been allocated to applications or to databases that
    contain such spaces.
  to:
    Limits the display to table spaces or index spaces that
    meet either of the following criteria:
    - Spaces that have internal DB2 resources allocated to
      applications and are in a started state
    - Databases that contain the spaces described in the
      previous bullet
  ============================================================
  Version 4 Book Title: Command Reference
  Pages: 102
  Change Description:
  
  Add this sentence after the sentence: "The maximum
  number of messages that can be displayed is limited by
  the space available."
  
    The message area cannot be greater than 256k.
  ============================================================
  Version 4 Book Title: Command Reference
  Pages: 103
  Change Description:
  
  The following paragraph will be added under USAGE
  NOTES currently on Pg. 103 after the first item
  "Displaying DB2 Catalog Tables" to help clarify
  the results of the RESTRICT parameter
  for the DISPLAY DATABASE command:
  
    "Displaying Restricted Objects:  To display table
     spaces and indexes in restricted status,
     use the SPACENAM parameter with RESTRICT.
     To display databases in restricted status,
     do NOT use the SPACENAM parameter."
  ==============================================================
  Version 4 Book Title: Command Reference
  Pages: 103
  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 4 Book Title: Command Reference
  Pages: 115
  Change Description:
  
  The display for DISPLAY GROUPBUFFERPOOL using the
  GDETAIL option is not correct in the format of message
  DSNB785I. There should be two numbers for the line
  DIRECTORY ENTRY NOT CREATED. The second number should
  always be 0. It is used for exception reporting, not
  performance monitoring. Here is a partial display from
  page 115:
  
                     DIRECTORY ENTRY NOT CREATED      = 47, 0
  ============================================================
  Version 4 Book Title:  Command Reference
  Pages:  142
  Change Description:
  
  Replace this text:
  
  "During a DSN session, you can enter comments (which start
  with *) and DB2 commands (which start with the 1 to 8
  character command prefix defined for the DB2 subsystem)."
  
  with this text:
  
  "During a DSN session, you can enter DB2 commands or
  comments.  DB2 commands must start with a hyphen (-).
  Comments must start with an asterisk (*)."
  ============================================================
  Version 4 Book Title:  Command Reference
  Pages: 192 & 258
  Change Description:
  
  Page 192, Under -MODIFY TRACE (DB2) "Environment" add
    a new paragraph at the end of this section:
  
    Traces started by a IFI/IFC program:
  
    Before you modify an active trace, ensure that an IFI
    application program or the IFC Selective Dump utility
    (DSN1SDMP) did not start the trace.  If you modify a
    trace started by DSN1SDMP, the DSN1SDMP utility
    abnormally terminates.  When DSN1SDMP terminates, it
    stops the trace.  This stop could interfere with the
    MODIFY TRACE command which stops and restarts the trace.
  
  Page 258, Under -STOP TRACE (DB2) "Environment" add
    a new paragraph at the end of this section:
  
    Traces started by a IFI/IFC program:
  
    Before you stop an active trace, ensure that an IFI
    application program or the IFC Selective Dump
    utility (DSN1SDMP) did not start the trace. If you stop
    a trace started by DSN1SDMP, the DSN1SDMP utility
    abnormally terminates.
  ============================================================
  Version 4 Book Title:  Command Reference
  Pages:  200
  Change Description:
    In the Usage Note "RECOVER BSDS Following BSDS I/O Error",
    change the pointer to the Administration Guide from
    "Section 3" to "Section 4".
  ==============================================================
  Version 4 Book Title: Command Reference
  Pages: 227
  Change Description:
  Modify the syntax diagram to add option TRACE=NO or YES.
           (Put exact Info APAR text here.
  Add the following option description on page 229.
    TRACE=
    Specifies whether IRLM is to capture traces in wrap-
    around IRLM buffers.  Each buffer is reused when the
    previous buffer is filled.  Traces are captured at IRLM
    startup.  The default is TRACE(NO).
     NO - Does not capture traces unless the TRACE CT command
          is issued.  See TRACE CT (MVS IRLM) on page 266 for
          details.  The default is TRACE(NO).
     YES - Captures traces in wrap-around buffers.
  ============================================================
  Version 4 Book Title: Command Reference
  Pages: 238
  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 4 Book Title:  Command Reference
  Pages:  262
  Change Description:
  Under the -Term Utility command, "Authorization" section,
  add this paragraph at the end.
  
  Database DSNDB06 contains the table spaces and index spaces
  required to check authorization.  If a table or index space
  required for authorization checking is affected by a utility
  which you need to terminate, then installation SYSADM
  authority is required to terminate that utility.
  ============================================================
  Version 4 Book Title: Command Reference
  Pages: 266-267
  Change Description:
  Remove the repeat symbol and the Note: from the syntax
  diagram.  Add the following to the description for option
  SUB=
    Traces EXP, INT and XIT are ON by default.  You cannot
    turn off traces EXP and INT.  If you do not specify a
    subname on the TRACE command, the trace is performed on
    all subnames that you control.  Specifying one subname
    restricts the traces to that trace plus the EXP and INT
    traces.
  ============================================================
  continued in II10279.
  

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