II09159: CHANGES TO DB2 SQL REFERENCE SC26-3270-00 THAT DID NOT MAKE V4.1 GA PUBS.CONTINUED IN II12330

APAR status

• Closed as canceled.

Error description

• 5740xyr00 DB2 R410 V4       continued in II12330
  This APAR documents changes to the DB2 SQL Reference
  SC26327000 which did not make Version 4.1 GA pubs.
  ================================================================
  Version 4 Book Title:  V4R1 SQL Reference
  Pages:  pg 78, 412
  Change Description:
  On page 78, change the second sentence of the last full
  paragraph on the page to:
      The default for the initial value is 1 unless your
      installation has changed it to be ANY by modifying the
    | CDSSRDEF subsystem parameter in the DSN6SPRM macro.
  On page 412, change the second sentence of the second
  paragraph in the Notes section to:
      The default for the initial value is 1 unless your
      installation has changed it to be ANY by modifying the
    | CDSSRDEF subsystem parameter in the DSN6SPRM macro.
  ===============================================================
  Version 4 Book Title: SQL Reference
  Page: 88, 89
  Change Description:
  
  To reflect that "indicator arrays" and not
  "indicator structures" are supported, change the last two
  sentences of the second paragraph under "Host Structures
  in PL/I, C, and COBOL" on page 88 to:
  
     The form a host structure reference is identical
     to the form of a host variable reference. The
     reference :S1:S2 is a host structure reference if
     S1 names a host structure.
  |  If S1 designates a host structure, S2 must be a small
  |  integer variable or an array of small integer variables.
  |  S1 is the host structure and S2 is its indicator array.
  
  In the remaining paragraphs under that section on pg 89,
  (Host Structures in PL/I, C, and COBOL), change all
  occurrences of:
     - "indicator structure" to "indicator array"
     - "main structure" to "host structure"
  ==============================================================
  Version 4 Book Title: SQL Reference
  Page: 139
  Change Description:
  For the DECIMAL function on page 139, modify the paragraph
  about string arguments to include the restriction that
  "+" and "-" characters are not supported:
  
     If the first argument is a string, its length must not
     exceed 254.  Leading and trailing blanks are eliminated
  |  from the string. The string must not include a plus (+)
  |  character or a minus (-) character. The resulting
     substring must conform to the rules for forming an SQL
     integer or decimal constant.
  ============================================================
  Version 4 Book Title:  V4R1 SQL Reference
  Pages:  pg 183
  Change Description:
  On page 183, change the last paragraph of the description
  for update-clause (FOR UPDATE OF) to:
  
    When FOR UPDATE OF is used, FETCH operations referencing
    the cursor acquire U locks rather than S locks when:
  
    -  The isolation level of the statement is cursor
       stability
    -  The isolation level of the statement is repeatable
       read or read stability and field U LOCK FOR RR/RS on
       installation panel DSNTIPI is set to get U locks.
  
    For a discussion of U locks and S locks, see Section 5
    (Volume 2) of Administration Guide.
  ============================================================
  Version 4 Book Title:   SQL Reference
  Pages:  199
  Change Description:
  Modify the 3rd sentence of the description for the PART
  clause to include the list of clauses that cannot be
  used when PART is specified:
  
     You must not use this clause if the index is not
  |  partitioned, or if you use the BUFFERPOOL, CLOSE,
  |  DSETPASS, or CONVERT TO clause.
  ============================================================
  Version 4 Book Title:  SQL Reference
  Pages: Pages 201, 224-225, 261, 294
  
  Change Description: For ALTER INDEX and CREATE INDEX,
  add this sentence to the paragraph that addresses the
  default for SECQTY as follows:
  
     .... the default for SECQTY is either 10% of PRIQTY
     or 3 times the index page size (4K), whichever is larger.
  |  If this value exceeds 131068, the default is 131068.
  
  For ALTER TABLESPACE and CREATE TABLESPACE, add this
  sentence to the paragraph that addresses the default
  for SECQTY as follows:
  
    .... the default for SECQTY is either 10% of PRIQTY or
    3 times the page size of the table space, whichever is
  | larger. If this value exceeds 131068, the default is 131068.
  ============================================================
  Version 4 Book Title:  SQL Reference
  Pages:    202
  Change Description:
  
  In the first paragraph for the CONVERT TO clause, change
  the second sentence to:
  
    The index is left in recover pending state, and the
    index change does not take place until the index is
    rebuilt by a LOAD REPLACE or REORG of the entire
    table space, or a RECOVER or RELOAD of the whole
    index.
  ============================================================
  Version 4 Book Title:  SQL Reference
  Pages: 203
  Add the following usage note to the Notes section:
    Altering a Type 2 Index to Type:
    When you change a type 2 index to a type 1 index, the
    plans and packages associated with that index are
    invalidated.  You must rebuild those plans and packages.
  ============================================================
  Version 4 Book Title: SQL Reference
  Pages: 206, 269, and 432
  Change Description:
  
  On pages 206 and 269 for ALTER STOGROUP and CREATE STOGROUP,
  change the usage note on "Number of Volumes" to read:
  
     Number of volumes:  There is no specific limit on the
       number of volumes that can be defined for a storage
  |    group.  However, for both SMS-managed and DB2
  |    user-defined data sets, the MVS limit on the number
  |    of volumes that can be defined and allocated per
  |    data set is currently 59. For the latest information
       on that restriction, see DFSMS/MVS: Access Method
       Services for the Integrated Catalog.
  
  On page 432, change this entry in Table 28:
      Maximum number of volume IDs               133
      in a storage group
  
  to:
      Maximum number of volumes in               Limited by
      an SMS-managed or DB2 user-defined         MVS to 59
      data set
  ============================================================
  Version 4 Book Title: SQL Reference
  Pages: 206, 269, and 432
  
  Change Description:
  On pages 206 and 269 for ALTER STOGROUP and CREATE STOGROUP,
  change the usage note on "Number of Volumes" to read:
  
     Number of volumes:  There is no specific limit on the
     number of volumes that can be defined for a storage
     group. However, the maximum number of volumes that can
     be managed for a storage group is 133.  Thus, there is
     no point in creating a storage group with more than 133
     volumes.
  
     MVS imposes a limit on the number of volumes that can
     be allocated per data set: 59 at this writing. For the
     latest information on that restriction, see DFSMS/MVS:
     Access Method Services for the Integrated Catalog.
  
  Change Table 28 (DB2 limits on SQL statements) on
  page 466 as follows:
  
  Replace row: Maximum number of volumes in       Limited by
               an SMS-managed or DB2 user-        MVS to 59
               defined data set
  
  With row:    Maximum number of volume IDs       133
               in a storage group
  ============================================================
  Version 4 Book Title: SQL Reference
  Pages: 220 and 298
  Change Description:
  For the LOCKSIZE clause of the ALTER TABLESPACE (pg 220)
  and CREATE TABLESPACE statements (pg 298), change the first
  sentence of the description of the value ANY to these
  two sentences:
  
        ANY
    |     Specifies that DB2 reserves the right to use any
    |     lock size.  Currently, DB2 never chooses row locks.
          In most cases, DB2 uses ...
  ============================================================
  Version 4 Book Title: SQL Reference
  Pages: pg 224  (ALTER TABLESPACE)
         pg 226  (ALTER TABLESPACE)
         pg 294  (CREATE TABLESPACE)
  Change Description:
  
   For the description of PRIQTY on pg 224, add this paragraph
   before the last paragraph.
     At least one of the volumes of the identified storage
     group must have enough available space for the primary
     quantity.  Otherwise, the primary space allocation will
     fail.
  
   Add a second sentence to the last paragraph on page 226:
     The changes to the storage attributes take effect the
     next time you use the REORG, RECOVER, or LOAD REPLACE
   | utility on the table space or partition.  If there is
   | not enough storage to satisfy the primary space
   | allocation, a REORG might fail.  If you change the
     primary space allocation parameters or erase rule, you
     can have the changes take effect earlier if you move
     the data before you start the table space or partition.
  
   For the description of PRIQTY on pg 294, add this paragraph
   before the last paragraph.
     At least one of the volumes of the identified storage
     group must have enough available space for the primary
     quantity.  Otherwise, the primary space allocation will
     fail.
  ============================================================
  Version 4 Book Title:  SQL Reference
  Pages: Page 265
  
  Change Description: Extend the first bullet for the
  description of the VALUES clause for CREATE INDEX as
  follows:
     The first constant corresponds to the first column of the
     key, the second constant to the second column, and so on.
     Each constant must have the same data type as its
  |  corresponding column. For example, if a column has a
  |  decimal data type, the constant must include a decimal
  |  point (.).
  ============================================================
  Version 4 Book Title:   SQL Reference
  Pages:  304
  Modify the first sentence of the third paragraph under
  WITH CHECK OPTION to read:
  
        WITH CHECK OPTION must not be specified if the view
        is read-only or its search condition includes a
   |    subquery, or the search condition of an underlying
   |    view includes a subquery.
  =============================================================
  Version 4 Book Title:  SQL Reference
  Pages:  432
  Change Description:
   For Table 24  "DB2 Limits on SQL Statements" modify the
   Item portion of these two entries in the table (the
   Limit remains the same) from:
  
   "Maximum number of partitions in a partitioned table space"
  
   "Maximum size of a partition"
  
   To:
   "Maximum number of partitions in a partitioned table
    space or partitioned index"
  
   "Maximum size of a partition (table space or index)"
  ============================================================
  Version 4 Book Title: SQL Reference
  Pages: 433
  Change Description:
  
  Add the following items to the DB2 Limits on SQL Statements
  table:
  
  Maximum number of bytes that can        32765 bytes
  be passed in a single parameter
  of an SQL CALL statement
  
  Maximum number of bytes that can        5.4 megabytes
  be passed to or from a stored
  procedure
  
  Also add a footnote to the table that says:
  
  Because DB2 does not know the addressing modes of the
  stored procedure and its caller, DB2 always allocates
  storage for passing data below the 16 megabyte line.
  Passing too much data when you execute an SQL CALL
  statement might lead to a storage shortage.
  ============================================================
  Version 4 Book Title: SQL Reference
  Page: 523
  Change Description:
  Add these words to the list of SQL reserved words in
  Appendix F:
  
     ISOBID    PSID
  ============================================================
  continued in II12330
  

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