II09158: CHANGES TO DB2 RELEASE GUIDE SC26-3394-01 THAT DID NOT MAKE V4.1 GA PUBS.

APAR status

• Closed as canceled.

Error description

• 5740xyr00 DB2 R410 V4
  This APAR documents changes to the DB2 Release Guide
  SC26339401 which did not make Version 4.1 GA pubs.
  ==============================================================
  Version 4 Book Title:  Release Guide
  Pages: 46, 53
  Change Description:
    On page 46, change the second bullet under 'Plan to
    convert to type 2 indexes because:' to the following:
      o There are restrictions on using type 1 indexes with
        UR isolation, as described on page 53.
    On page 53 change the 'Restrictions on Use' section to the
    following:
  Restrictions:  You cannot use UR isolation for the types
  of statement listed below.
  If you bind with ISOLATION(UR), and the
  statement does not specify WITH RR or WITH RS,
  then DB2 uses CS isolation for:
    o INSERT, UPDATE, and DELETE
    o Any cursor defined with FOR UPDATE OF
  If you bind with isolation UR or specify WITH UR on a
  statement, DB2 does not choose a type 1 index as a candidate
  for the access path.  For packages
  bound without specifying an isolation,
  DB2 might choose a type 1 index
  for the access path.
  If it does, and then you run the package under
  plan bound with UR, DB2 changes the isolation level to
  cursor stability.
  ============================================================
  Version 4 Book Title: Release Guide
  Pages: 55 - 57
  Change Description:
  
  Make the following changes to Table 1:
  
  1. For the 'Read-only SELECT portion'
     - Change the heading to 'SELECT with read-only or
       ambiguous cursor, or with no cursor'
  
  2. For the UPDATE or DELETE with cursor' section:
  
     - Remove the subscripts 9 and 12 on the Data page/row X
       locks. (Note 12 was added per PN75407).
       These notes are confusing because they are
       describing the S locking that happens
       during the SELECT operation of the cursor.
       However, we already have a separate
       'SELECT with FOR UPDATE OF' section that covers
       those cases.
       For the 'UPDATE or DELETE' with cursor section, we
       should only talk about the locks for that
       operation, which means X locks.
  
     - Combine this section into one section that
       covers CS, RS, RR.  This information is the same
       for all these isolation levels.
       This section is incorrect because
  
  3. Remove number 9 from the notes section.
          Resequence notes appropriately.
  
  4. Note #6 should say "SELECT statements with cursor
     stability that do not use a cursor, or that use a
     read-only or ambiguous cursor,
     and are bound with CURRENTDATA(NO), might not require
     any lock if DB2 can determine that the data to be read
     is committed."
  ============================================================
  Version 4 Book Title: Release Guide
  Pages: 134
  Change Description:
  
   Page 134, Security Enhancement for Distributed Connections,
   add the following after the last entry:
  
       In addition to the DDF security enhancement described
       here, the following RACF checks may also be performed
       during DDF connection processing:
  
       1) If the RACF APPL class is active, RACF will verify
       that the ID has been given access to the DB2 APPL.  The
       APPL resource that is checked is the LU name that the
       requester used when the attach request was issued.
       This will either be the local DB2 logical unit name
       (LUNAME) or the generic LU name.
  
       2) IF the RACF APPCPORT class is active, RACF will
       verify that the ID is authorized access to MVS from the
       port of entry (POE).  The POE that is used in the verify
       call is the requesting LU name.
  
       For additional details, see (ref. to the DB2 Admin
       Guide, Vol 1, Chapter 3-4, Controlling Access to a DB2
       Subsystem).
  ============================================================
  Version 4 Book Title:  Release Guide
  Pages:  139
  Change Description:
  
  After this text:
  
  Accessing Logical Partitions Concurrently
  -----------------------------------------
  In DB2 Version 3, utilities and SQL applications can access
  independent partitions of a table space or index space
  concurrently.  Access to a nonpartitioned index, however,
  must be sequential.
  
  In DB2 Version 4, logical partitions of a nonpartitioned
  index can be accessed by utilities and SQL applications
  concurrently.  The index must be type 2.  (For a description
  of type 2 indexes, see "Improved Indexes" in topic 4.1.)
  
  With this change, DB2 Version 4 allows full independence
  on tables that do not have type 1 indexes.  That is
  particularly important with the introduction of the new CMOS
  microprocessors.  On those processors, all utilities except
  COPY and RECOVER will probably be processor bound.  Running
  a utility in parallel on different parts of a table can
  help you fit the job into a small window.
  
  Add this paragraph:
  
  When you run utilities and execute SQL statements
  on a partitioned table space, keep in mind that the
  partitions that an SQL statement accesses and the access
  path that DB2 chooses for the statement are highly
  correlated.  Therefore, even though you might think that
  an SQL statement accesses only one partition, the access
  path might cause DB2 to access multiple partitions.
  ============================================================
  Version 4 Book Title:  Release Guide
  Pages:    170
  Change Description:
  
  In the first paragraph for ALTER INDEX, change the
  second sentence to:
  
    The 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.  (The utility job must be done in a single
    invocation; running separate jobs in parallel using
    partition independence does not accomplish the change.)
  ============================================================
  Version 4 Book Title:  Release Guide
  Pages:       170
  Change Description:
    Modify the description of the TYPE 1 clause to
    read:
  
    TYPE 1
  |   Specifies that the index is type 1.  When you change
  |   a type 2 index to a type 1 index, the plans and
  |   packages associated with that index are marked
  |   invalid; you must rebuild those plans and packages.
      CONVERT TO TYPE 1 is not allowed if:
      -  The table space associated with the index has
         a LOCKSIZE value of ROW.
      -  The index was defined with UNIQUE WHERE NOT NULL.
  ============================================================
  Version 4 Book Title:  Release Guide
  Pages:  195
  Change Description:
  
  In the introduction to "Changes to Commands," add this
  paragraph:
  
  There is also a change to the way you can enter commands
  using DB2I.  The DB2 COMMANDS panel has 7 fields for
  commands.  If a command fits on one line, you can enter it
  in any of those fields.  If your command requires multiple
  lines, use one of fields 3 through 7.
  ============================================================
  Version 4 Book Title:  Release Guide
  Pages: 250
  Add the following to the list of incompatible changes:
  
  Changed Format of DSN9022I Message from START And STOP DB2
  
  The completion message, DSN9022I, from a START DB2 or
  STOP DB2 command no longer contains the subsystem
  recognition character as part of the message text.
  For example, whereas you previously saw this:
  DSN9022I - DSNYASCP '-START DB2' NORMAL COMPLETION
  
  In Version 4, you see this:
  DSN9022I - DSNYASCP 'START DB2' NORMAL COMPLETION
  ============================================================
  Version 4 Book Title:  Release Guide
  Pages: 250
  Change Description:
  
  Modify the previous change for incompatible change to
  DSN9022I to also include DSN9023I:
  
  Add the following to the list of incompatible changes:
  
  Changed Format of DSN9022I and DSN9023I Messages from
          START And STOP DB2:
  The completion messages from a START DB2 or
  STOP DB2 command no longer contain the subsystem
  recognition character as part of the message text.
  For example, whereas you previously saw this:
  DSN9022I - DSNYASCP '-START DB2' NORMAL COMPLETION
  In Version 4, you see this:
  DSN9022I - DSNYASCP 'START DB2' NORMAL COMPLETION
  ============================================================
  Version 4 Book Title: Release Guide
  Pages: 256
  Change Description:
  
  Add the following topic under "Release Incompatibilities":
  
  DSNALI Linkage Attributes
  
  DSNALI is now shipped with the attributes AMODE(31) and
  RMODE(ANY).  You must re-link DSNALI if your applications
  need to load it below the 16MB line.
  ==============================================================
  Version 4 Book Title: Release Guide
  Pages: 257
  Change Description:
  
  The following is added to Chapter 12 on Planning for
  migration and fallback:
  
  SQLCODE -101
  
  After migrating to DB2 Version 4, it is possible to receive
  SQLCODE -101 on long or complicated SQL statements that
  previously executed successfully.  This is possible because
  SQL statements and DB2 internal structures are buffered in
  the same local storage, and release changes in the
  internal structures can result in less storage
  available for the SQL statements.
  
  Re-write the offending SQL statements by using correlated
  references, or by breaking up UNIONs.
  ============================================================
  Version 4 Book Title: Release Guide
  Pages: 258
  Change Description:
    Under 'Invoke Utilities Differently' add the following:
  
  Return Code Change for LOAD REPLACE with ENFORCE
    CONSTRAINTS:
  
  Previously, if you loaded a parent table space and enforced
  constraints, the LOAD utility ended with a return code 0,
  even though dependent table spaces were placed in a
  CHECK-pending status. Now, to help alert you to the fact
  that CHECK-pending table spaces exist, the LOAD utility
  ends with a return code 4 and issues message DSNU563I.
  ============================================================
  

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