II07120: CHANGES TO MESSAGES AND CODES THAT DID NOT MAKE R230 GA PUBS CONTINUATION OF II05810, II06784 & II07372

APAR status

• Closed as canceled.

Error description

• This apar documents changes to the DB2 Messages and Codes
  manual that did not make the r230 ga pubs.  5740xyr00
  sc26-4379-02 sc26437902
  This apar is a continuation of apar II07120.
  ===============================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: 2-13
  Change Description:
  
  Replace SQL code -144 with the following:
  
  -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:
     - 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 in question
  was bound as a valid section.  You can use the following
  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 the following 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
  ================================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: 2-41
  Change Description:
  
  Replace SQLCODE -733 with the following:
  
  -733 THE DESCRIPTION OF A TABLE SPACE, INDEX SPACE, OR TABLE
       IN A ROSHARE READ DATABASE MUST BE CONSISTENT WITH ITS
       DESCRIPTION IN THE OWNER SYSTEM
  
  EXPLANATION: SQLCODE -733 is issued while creating a table space
  index, or table in the ROSHARE READ database.  These objects
  must be consistent with their descriptions in the ROSHARE OWNER
  database as follows:
  
  For a table space, the following attributes must be the same:
  1. Page size
  2. Segment size
  3. Number of partitions
  
  For an index, the following attributes must be the same:
  1. Number of partitions
  2. Number of subpages
  3. Table OBID
  4. Total key length
  5. Number of key columns
  
  For a table, the following attributes must be the same:
  1. Table OBID
  2. Maximum record length
  3. Number of columns
  4. Whether an edit procedure exists
  
  SYSTEM ACTION: The statement cannot be executed.
  
  PROGRAMMER RESPONSE: Ensure that the definition of the table
  space, index, or table is consistent with that in the ROSHARE
  OWNER database.
  
  SQLSTATE: 56056
  ================================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: 3-14
  Change Description:
  
  In DSNC014I, replace the explanations of the fields in the
  statistics report with the following:
  
  TRAN         CICS transaction name.
  
  PLAN         DB2 plan name.
  
  CALLS        Total number of SQL statements in this connection.
  
  AUTHS        Total number of sign-ons, "new authorizations".
               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 statistics
  report, refer to "Controlling CICS Connections" in
  Section 6 (Volume 2) of Administration Guide.
  ================================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: 3-81
  Change Description:
  
  In DSNJ004I, add the following to the SYSTEM ACTION:
  
  If DB2 is shut down or abends while in single mode with the
  ZPARM option still set for dual active data sets,
  the previous state of the active log data sets determines
  what happens when DB2 is started, as follows:
  
   -  If fewer than two data sets are available (not flagged
      as STOPPED) for each set of active logs, DB2 startup
      terminates and message DSNJ112E is issued.
  
   -  If an active log data set is in NOTREUSABLE state, DB2
      can be started in single logging mode, but dual mode
      takes effect when the other active log data set becomes
      available after offloading.
  ================================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: 3-86
  Change Description:
  
  In DSNJ099I, remove this phrase at the end of the EXPLANATION:
  "...and is the RBA of the last possible byte in the data set."
  ================================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: 3-92
  Change Description:
  
  In the EXPLANATION of DSNJ125I, replace the sentence that
  begins, "A read error occurred while dumping..." with the
  following:
  
  An error occurred while dumping the BSDS data set during the
  off-load process.
  ================================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: 3-126
  Change Description:
  
  In DSNP008I, add the following to the EXPLANATION:
  
  If the name of the data set in the message is different from
  the name of the original data set, (for example, '....A002'
  instead of '....A001), a new data set might need to be
  created.  A different name indicates that the original data
  set exceeded 2GB.
  ================================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: 3-160
  Change Description:
  
  For DSNT396I, replace the definition of 'part' in the
  explanation (the third bullet) with the following:
  
  The 'part' is the partition number.
  It is blank for a simple table space, simple index space,
  or segmented table space.
  ================================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: 3-204
  Change Description:
  
  In the SYSTEM PROGRAMER RESPONSE of DSNU340I, replace the
  sentence that begins "CHECK DATA can be run to verify ..."
  to the following:
  
  CHECK INDEX can be run to verify that the data and
  indexes are consistent.
  ================================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: 3-227
  Change Description:
  
  In DSNU619I, change the SEVERITY from 4 (warning) to
  0 (informational).
  ================================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: 4-15
  Change Description:
  
  In the SYSTEM ACTION in abend reason code 00C200F9, delete the
  sentence, "The page set containing the migrated data set is
  stopped.
  
  In the USER RESPONSE, delete the sentence, "Start the page set."
  ================================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: 3-162
  Change Description:
  
  In abend reason code 00D44011, replace the first
  paragraph of the EXPLANATION with the following:
  
  The DB2-DL/I batch support or IMS BMP job
  step cannot continue because the application program
  could not be loaded.
  Replace the SYSTEM PROGRAMMER RESPONSE with the following:
  
  Be sure the DDITV02 SYSIN data (for DB2-DL/I batch support)
  or IMSBATCH procedure (for an IMS BMP job step) names a subsyste
  member (SSM) parameter that points to a resource translation tab
  (RTT).  The RTT maps the IMS application name to the DB2 plan na
  
  If you suspect an error in DB2, refer to Section 3 of Diagnosis
  Guide and Reference for information on identifying and
  reporting the problem.
  ================================================================
  Book Title:  Messages and Codes (SC26-4379-02)
  Page Number: X-3
  Change Description:
  
  In Appendix A. CICS Transaction Abend/Dump Code, PROBLEM
  DETERMINATION section, add these codes:
  
  4C  Unable to interpret SQL call
  50  Shutdown during commit or abort
  54  Abort is the only valid request
  58  Wrong language interface used with instrumentation facility
      interface application
  5C  Cannot link to dynamic plan exit
  ===============================================================
  

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