II07119: CHANGES TO DB2 ADMINISTRATION GUIDE VOLUME II THAT DID NOT MAKE R230 GA PUBS

APAR status

• Closed as canceled.

Error description

• This APAR documents changes to the DB2 Administration Guide
  Volume II which did not make the GA R230 Pubs.  5740xyr00
  sc26-4374-02 ac26437402
  This APAR is a continuation of APAR II05925.
  ================================================================
  Book Title:  Administration Guide, Sect. 4: 'Designing a
               Database', SC26-4374-02
  Page Number: 4-113
  
  Change Description:  Replace the last paragraph with:
  Invalidated Plans and Packages: When you drop the definition of
  an object on which a plan or package depends, DB2 marks the plan
  or package as invalid.  When a user with the EXECUTE authority
  tries to execute an invalid plan or package, DB2 first
  rebinds it automatically, using the same options that were
  used during the most recent bind operation.   (To see if a plan
  or package is invalidated, check the VALID column in
  SYSIBM.SYSPLAN or SYSIBM.SYSPACKAGE.)  For more information
  about invalidated plans and packages and rebinding,
  see Section 4 of 'Application Programming and SQL Guide'.
  ================================================================
  Book Title:  Administration Guide, Section 5: "Security and
               Auditing" , SC26-4374-02
  Page Number: 5-21
  Change Description:
  
  Replace the last paragraph, "Performance Hint", with the
  following:
  
  When checking the authorization to execute a plan, DB2 uses a
  cache to improve performance.  Checking is fastest when the
  EXECUTE privilege is granted to PUBLIC and next when the plan
  is reused by an ID that already appears in the cache.  The
  size of the cache is set in the BIND PLAN subcommand.  For
  suggestions on setting the cache size, see Section 4 of
  Application Programming and SQL Guide.
  ================================================================
  Book Title:  Administration Guide, Section 5: "Security and
               Auditing" , SC26-4374-02
  Page Number: 5-24 to 5-25
  Change Description:
  
  Change the information in the Operation column (column 1)
  in the following cases:
  
  From:                         To:
  
  BIND a new plan               BIND a new plan using
  with default owner            the default owner or
                                primary authorization ID
  
  BIND a new package            BIND a new package using
  with default owner            the default owner or
                                primary authorization ID
  
  BIND REPLACE or REBIND        BIND REPLACE or REBIND
  for a plan or package         for a plan or package using
  with default owner            the default owner or primary
                                authorization ID
  
  Name a new owner for          Name an OWNER other than the
  any bind operation            primary authorization ID for
                                any bind operation
  ================================================================
  ================================================================
  Book Title:  Administration Guide, Section 5, "Security and
               Auditing" , SC26-4374-02
  Page Number: 5-86
  Change Description:
  
  Replace the section, "Access by Stand-Alone DB2 Utilities"
  with the following:
  
  The DB2 utilities DSN1COPY and DSN1PRNT access table space
  and index space data sets outside DB2 control.
  DSN1LOGP accesses the recovery log data sets (active logs,
  archive logs, and the bootstrap data sets) outside DB2 control.
  
  DSN1CHKR accesses DB2 directory and catalog table spaces
  outside DB2 control.  The Change Log Inventory and Print
  Log Map utilities access the bootstrap data sets.  Those
  are batch jobs, protected by the USER and PASSWORD options
  on the JOB statement. To provide a value for the USER option,
  say SVCAID, issue the following statements:
  
   - For DSN1COPY:
  
  PERMIT 'DSNC230.*' ID(SVCAID) ACCESS(CONTROL)
  
   - For DSN1PRNT:
  
  PERMIT 'DSNC230.*' ID(SVCAID) ACCESS(READ)
  
   - For DSN1LOGP:
  
  PERMIT 'DSNC230.LOGCOPY*' ID(SVCAID) ACCESS(READ)
  PERMIT 'DSNC230.ARCHLOG*' ID(SVCAID) ACCESS(READ)
  PERMIT 'DSNC230.BSDS*'    ID(SVCAID) ACCESS(READ)
  
   - For DSN1CHKR:
  
  PERMIT 'DSNC230.DSNDBDC.*' ID(SVCAID) ACCESS(READ)
  
   - For Change Log Inventory:
  
  PERMIT 'DSNC230.BSDS*' ID(SVCAID) ACCESS(CONTROL)
  
   - For Print Log Map:
  
  PERMIT 'DSNC230.BSDS*' ID(SVCAID) ACCESS(READ)
  
  The level of access depends on the intended use, not on the
  type of data set (VSAM KSDS, VSAM linear, or sequential).
  For update operations, ACCESS(CONTROL) is required; for read-onl
  operations, ACCESS(READ) is sufficient.
  
  With RACF, you can permit programs,
  rather than user IDs, to access objects.
  Thus, IDs that are not authorized to access the log data sets
  can perhaps do so by running the DSN1LOGP utility.  Access to
  to database data sets can be permitted through DSN1PRNT or
  DSN1COPY.
  ===============================================================
  Book Title: DB2 Administration Guide, Vol. III (SC26-4374-02)
  Page Number: p. 7-90
  Change Description:
  
  After the paragraph with the "Search Order" heading, add the
  following new text:
  
  RLST COMBINATIONS FOR SPUFI:  Because SPUFI is bound as a
  package, SPUFI users must have an RLST row with the values
  RLFFUNC=2 and PLANNAME=BLANK.  The values for RLFCOLLN and
  RLFPKG can be blank.
  ===============================================================
  Book Title: DB2 Administration Guide, Appendix E (SC26-4374-02)
  Page Number: p. X-76
  Change Description:
  
   In Table 193, Exit Parameter List for Connection and Sign-on
   Routines, there are errors in the Offset and Data Type columns
   for the last 3 rows.  Those rows should read as follows:
  
  +----------+-----+------------+-----------------------------+
  | EXPLSITE | 2C  | Character, | Location name of the        |
  |          |     | 16 bytes   | requesting location.        |
                                  Blank if not known.         |
  +----------+-----+------------+-----------------------------+
  | EXPLLUNM | 3C  | Character, | Locally known LU name of the|
  |          |     | 8 bytes    | requesting location.        |
  +----------+-----+------------+-----------------------------+
  | EXPLNTID | 44  | Character, | Fully qualified network name|
  |          |     | 17 bytes   | of the requesting location. |
  +----------+-----+------------+-----------------------------+
  ===============================================================
  Book Title: DB2 Administration Guide, Appendix E (SC26-4374-02)
  Page Number: p. X-112
  Change Description:
  
      Change the second paragraph on the page to read as follows:
  
  A terminal-driven transaction that uses a protected thread
  takes the dynamic plan selection exit only on the first SQL
  statement of the transaction and cannot change plans before the
  CICS end-of-task (EOT).  If a terminal-driven transaction that
  uses a protected thread tries to refer to a different plan,
  it gets a nonzero SQLCODE.
  ===============================================================
  Book Title: DB2 Administration Guide, Vol II (SC26-4374-02)
  Page Number: 6-16
  Change Description:
  In Chapter 6-1, "Running Batch Applications," add this bullet
  item to the list following "In the example,"
  
   -  IKJEFT01 identifies an entry point for TSO TMP invocation.
      Alternate entry points defined by TSO are also available
      to provide additional return code and ABEND termination
      processing options. These options permit the user to select
      the actions to be taken by the TMP upon completion
      of command or program execution.
  
      Because invocation of the TSO TMP using the IKJEFT01 entry
      point might not be suitable for all user environments, refer
      to the TSO publications to determine which TMP entry
      point provides the termination processing options
      best suited to your batch execution environment.
  
  ================================================================
  Book Title: DB2 Administration Guide, Vol II (SC26-4374-02)
  Page Number: 6-42
  Change Description:
  In Chapter 6-2, "Connecting from Dependent Regions," modify
  the second paragraph under item 2 ("Load the DB2 ...") to read:
  
      For a message processing program (MPP) region or IMS fast
      path (IFP) region, the connection is made when the IMS
      region is initialized, and an IMS transaction is available
      for scheduling in that region.
  
      An IMS dependent region establishes two connections to DB2;
      a region connection and an application connection which
      occurs at execution of the first SQL statement.
  
  ================================================================
  Book Title: DB2 Administration Guide, Vol II (SC26-4374-02)
  Page Number: 6-63
  Change Description:
  In Chapter 6-3,  "The -ARCHIVE LOG Command," modify the third
  paragraph to read:
  
      When you issue the above command, DB2 truncates the current
      active log data sets, then runs an asynchronous off-load,
      and updates the BSDS with a record of the off-load.  The RBA
      that is recorded in the BSDS is the beginning of the last
      complete log record written in the active log data set being
      truncated.
  
  ================================================================
  Book Title: DB2 Administration Guide, Vol II (SC26-4374-02)
  Page Number: 6-74
  Change Description:
  In Chapter 6-3, "Determining the BSDS Log Inventory Contents,"
  add the following bullet before "Changing the BSDS Log
  Inventory" at the top of the page:
  
    - The values in the TIME column of the ARCHIVE LOG COMMAND
      HISTORY section of the report represent the time the ARCHIVE
      LOG command was issued.  This time value is saved in the
      BSDS and is converted to printable format at the time the
      print log map utility is run.  Therefore this value, when
      printed, can differ from other time values that were
      recorded concurrently.  Some time values are converted to
      printable format when they are recorded and then saved in
      the BSDS.  These printed values will remain the same when
      the printed report is run.
  
  ================================================================
  Book Title: DB2 Administration Guide, Vol II (SC26-4374-02)
  Page Number: 6-95
  Change Description:
  In Chapter 6-5, "Planning for Backup and Recovery," add the
  following paragraph:
  
      To improve recovery capability in the event of a DASD
      failure, it is advisable to use dual active logging
      and to place the copies of the active log data sets and
      the bootstrap data sets on different DASD volumes.
  
  ================================================================
  Book Title: DB2 Administration Guide, Vol II (SC26-4374-02)
  Page Number: 6-120
  Change Description:
  In Chapter 6-5, "Order of Recovering Catalog and Directory
  Objects," add the following paragraph before "The catalog and
  directory contain ..."
  
      Although you can place all objects under one job step,
      the archive logs are still read as required for each
      execution of a RECOVER statement.  To reduce processing time
      consider running recovery jobs in parallel.
  
  ================================================================
  Book Title: DB2 Administration Guide, Vol II (SC26-4374-02)
  Page Number: 6-124
  Change Description:
  Chapter 6-5, "Recovering Data to a Prior Point of Consistency,"
  add the following as the last bullet before "Restoring
  the Catalog ..."  "
  
    - When data is restored to a prior point in time on a
      segmented table space, information in the DBD for the table
      space might not match the restored table space.  If the DB2
      RECOVER utility is used, the DBD is updated dynamically to
      match the restored table space on the next non-index access
      of the table.  The table space must be in WRITE access mode.
      If RECOVER is not used, you can run the REORG utility on the
      table space to correct the DBD.
  
  ================================================================
  Book Title: DB2 Administration Guide, Vol II (SC26-4374-02)
  Page Number: 6-157
  Change Description:
  Chapter 6-6, "BSDS Failure," change the last two sentences of
  the first paragraph:
  
      The damaged copy of the BSDS must be recovered prior to the
      next restart.  This requires stopping DB2.  If you are in
      single mode and damage the only copy of the BSDS, or if you
      are in dual mode and damage both copies, DB2 stops until the
      BSDS is recovered.  To proceed under these conditions, see
      "BSDS Recovery" on page 6-160.
  
  ================================================================
  

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