II08169: CHANGES TO DB2 MESSAGES & CODES SC26-4892-00 WHICH DID NOT MAKE VERSION 3 GA PUBS. CONTINUATION OF II07607 & II07908.

APAR status

• Closed as canceled.

Error description

• This Info. APAR documents changes to the DB2 Messages and Codes
  SC26-4892-00 which did not make the Version 3 GA pubs.
  Continuation of II07607 & II07908. Continued in II08715.
  5740xyr00 R310
  ================================================================
  Version 3 Book Title: DB2 Messages and Codes
  Pages: 2-14
  Change Description:
   Replace SQL code -144 with the following text:
  
   -144 INVALID SECTION NUMBER number
   EXPLANATION: One of the following:
   1. The user attempted to execute an invalid section
   2. This release of DB2 does not support the SQL statement
   3. The section number in the call parameter list is either
      - Negative,
      - An invalid duplicate, or
      - Greater than the maximum section number of the DBRM
        or package.
   SYSTEM ACTION: The statement is not executed.
   SYSTEM PROGRAMMER RESPONSE:
   For case 1:
   If you are executing a package that was bound with
   SQLERROR(CONTINUE), determine whether the statement
   was bound as a valid section.  You can use these
   statements to query the DB2 catalog:
     SELECT SQLERROR
     FROM   SYSIBM.SYSPACKAGE
     WHERE  COLLID    = collection-id AND
           NAME      = package-id    AND
           VERSION   = version-name;
  If that query returns 'C', the package was bound with
  SQLERROR(CONTINUE).
    SELECT STMTNO, TEXT
    FROM   SYSIBM.SYSPACKSTMT
    WHERE  COLLID    = collection-id AND
           NAME      = package-id    AND
           VERSION   = version-name  AND
           SECTNO    = number        AND
           BINDERROR = 'Y';
  If that query returns any rows, the section is invalid.
  Refer to the error messages issued during the bind to
  determine the  cause.  Correct any errors and bind the
  package again, using the REPLACE option.
  For case 2:
  If the DB2 system has fallen back to a previous release,
  determine whether there are any SQL statements with a
  section number of zero that are not supported by that
  release.  You can use these statements to query the DB2
  catalog.  When executing from a DBRM, use:
    SELECT *
    FROM   SYSIBM.SYSSTMT
    WHERE  SECTNO = 0
    ORDER BY NAME, PLNAME, STMTNO, SEQNO;
  When executing from a package, use:
    SELECT *
    FROM   SYSIBM.SYSPACKSTMT
    WHERE  SECTNO = 0
    ORDER BY COLLID, NAME, VERSION, STMTNO, SEQNO;
  For case 3:
  Examine the application to determine whether the call
  parameter list has been changed in some way.  In general,
  you should not  attempt to change the output of the
  precompiler.
  SQLSTATE: 58003
  ================================================================
  Version 3 Book Title: Messages and Codes
  Pages: 3-7
  Change Description:
  
  The first paragraph of the message explanation is changed
  to read:
  
  An abnormal condition is detected for one of the following
  reasons:
  
   - The associated table space or index space contains
     modified pages that cannot be written to DASD for a
     period of time that is longer than expected.
     This can be caused by either unbalanced write
     intents resulting from logical errors on the page or by
     an internal logic error.
  
   - This message follows an abnormal termination due to
     inconsistent data or an incomplete update to the page.
  ================================================================
  Version 3 Book Title: DB2 Messages and Codes
  Pages: 3-22
  Change Description:
   In message DSNC014I, replace the explanations of the fields
   in the statistics report with the following text:
  
   TRAN    CICS transaction name.
   PLAN    DB2 plan name.
   CALLS   Total number of SQL statements in this connection.
   AUTHS   Total number of new authorizations for sign-ons.
           Sign-on occurs only if the CICS transaction ID or
           DB2 authorization ID has changed.
   W/P     Number of times all available threads for this
           entry were busy and the transaction had to wait or
           the thread request was diverted to the POOL.
   HIGH    Maximum number of concurrent threads required by
           transactions associated with this entry at any
           time since the CICS attachment facility was
           started.
   ABORTS  Total number of units of recovery that were rolled
           back.
   COMMITS One of the following two fields is incremented
           each time a DB2 transaction associated with this
          entry has an explicit or implicit (such as EOT)
          sync point.
  1-PHASE The total number of single phase commits for
          transactions associated with this entry.
  2-PHASE The total number of two-phase commits for
          transactions associated with this entry.
  For a more detailed explanation of the fields in the
  report, refer to "Controlling CICS Connections" in
  Section 6 (Volume 2) of Administration Guide.
  ================================================================
  Version 3 Book Title:  Messages and Codes
  Pages: 3-140, 3-141
  Change Description:
  Replace the message text for
  DSNL701I and DSNL703I as follows:
  DSNL701I CDB OBJECT object-name DOES NOT EXIST
  
  DSNL703I CDB TABLE table-name DOES NOT HAVE PROPER
           INDEX DEFINITIONS, INDEX index-name IS
           MISSING OR INCORRECTLY DEFINED
  ================================================================
  Version 3 Book Title: DB2 Messages and Codes
  Pages: 3-176
  Change Description:
  
  For message DSNT376I, replace the paragraph that begins
  "Several different system plans..." with the following
  paragraph:
  
  Several different system plans can appear in 'plan-id1'
  and 'plan-id2'.  These system plans are not documented
  in SYSIBM.SYSPLAN.  If you receive a system plan in this
  message, you are in contention with another user.
  If you are not doing an automatic rebind, message
  DSNT500I or DSNT501I accompanies this message and
  identifies that resource.  If you need additional
  information, refer to the SQLCA and any additional bind
  messages.  If you are doing an auto rebind, the SQLCA is
  not available.  Refer to Section 4 of Application
  Programming and SQL Guide for more information about
  automatic rebinding.  The system plans are:
  ================================================================
  Version 3 Book Title: Message and Codes
  Pages: 3-176
  Change Description:
  
  Under 'Explanation', change the sentence in the last
  paragraph that begins 'If you are not doing an automatic
  rebind' to read:
  
  If you are not doing an automatic rebind, message DSNT500I
  or DSNT501I might accompany this message and identify that
  resource.
  
  Under 'System Programmer Response', change the first bullet
  to read:
  
  If the resource involved in the timeout is listed in the
  DSNT500I/DSNT501 message as a table or table space, check
  the following items forother possible causes of the timeout:
  ================================================================
  Version 3 Book Title: Messages and Codes
  Pages: 3-176, 3-177, 3-277
  Change Description:
    For messages DSNT375I and DSNT377I, add the following
  sentence to the end of the Explanation:
    If you receive a system plan in this message, see the
  information about system plans in message DSNT376I.
    For message DSNV404I, add the following sentence to
  the end of the explanation of variable 'pname':
    If you receive a system plan in this field, see the
  information about system plans in message DSNT376I.
  ================================================================
  Version 3 Book Title: DB2 Messages and Codes
  Pages: 3-237
  Change Description:
  Under EXPLANATION, following "or point in time recover
  has been done on the table space" add:
   or the table space is in COPY PENDING state and the
   requested  full image copy is for a site other than the
   current site.
  Under USER RESPONSE, following "guarantee the correct
  recovery on both sites" add:
   or check DSNZPARM to ensure that the current site is the
   site at which the image copy is being taken.
  ================================================================
  Version 3 Book Title: DB2 Messages and Codes
  Pages: 4-218
  Change Description:
  For 00E30081 under System Programmer Response, change the
  second sentence from:
    the SPRMSWT parameter of the DSN6SPRM assembler macro
  to:
    the IRLMSWT parameter of the DSN6SPRM assembler macro
  ================================================================
  Version 3 Book Title:  DB2 Messages and Codes
  Pages: 4-224
  Change Description:
  
  For reason code 00E40006, replace the Explanation, System
  Action, and Problem Determination.  Add the User Response.
  
  Explanation: An error was detected while manipulating the
  utility-in-progress bits of the DBA table.  The error might
  occur if the SYSIBM.SYSUTIL table and the DBA table are out
  of sync, if the utility-in-progress condition was not
  properly reset after execution of a prior utility, or if a
  resource unavailable condition exists.
  
  This abend reason code is issued by the following CSECT:
  DSNUGUIP
  
  System Action: Utility processing is abended.  This abend
  might be accompanied by message DSNT500I.  An SDUMP might be
  requested.
  
  User Response: If applicable, correct the resource
  unavailable condition identified by the DSNT500I message.
  Either restart the utility from the last commit point or
  terminate the utility and submit it again.  Refer to Figure
  8 in Appendix B, "Problem Determination" on page X-7
  for an explanation of resource types.
  
  If DSNT500I was not issued, register 2 contains a secondary
  DB2 reason code that gives more information about the
  problem.  If the secondary reason code is not documented in
  this manual, it is an internal IBM code.  Consult the
  system programmer to diagnose the problem.
  
  Problem determination: If the condition cannot be corrected,
  determine the failing environment.  Collect the following
  diagnostic items listed in Appendix B: 1 5 31 45 59 60 71
  ================================================================
  Version 3 Book Title: DB2 Messages and Codes
  Pages: 4-224
  Change Description:
  
  For reason code 00E40009, replace the first sentence of the
  explanation with the following sentence:
  
  An error was detected while attempting to access the target
  object (table space or index space).
  ================================================================
  Version 3 Book Title: DB2 Messages and Codes
  Pages: X-3
  Change Description:
  
  Add the following two lines to the list under "Problem
  Determination":
  
     60   Single phase commit failed.
  
     64   Task was purged under CICS.
  ================================================================
  Version 3 Book Title: DB2 Messages and Codes
  Pages: X-8
  Change Description:
  
  Add the following line to abend reason code 00C90101 in
  figure 9:
  
  ABEND Reason Code    CSECT-name:ERQUAL   Explanation
  
    00C90101              DSNICUMW:5004         4
  ================================================================
  Version 3 Book Title: DB2 Messages and Codes
  Pages: X-8 and X-10
  Change Description:
  
  Add the following line to abend reason code 00C90101 in
  figure 9 on page X-8.
  
  ABEND Reason Code    CSECT-name:ERQUAL   Explanation
  
    00C90101              DSNIDEFR:5005        13
  
  Add the explanation for 13 at the end of the list on page
  X-10:
  
  13. Log RBA is unavailable for the associated table space
      or index space.
  ================================================================
  Continued in Info. APAR II08715.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• closed for retention
  

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