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

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.
  ================================================================
  Version 2 Release 3 Book Title: Messages and Codes
  Pages:  2-30
  Change Description:  Add SQLCODE -351:
  
  -351  AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION
        "<position-number>" ON A PREPARE OR DESCRIBE OPERATION.
  
  Explanation: Some SQL data types are not supported by
  DB2 Version 2 Release 3.  "<position- number>" is the
  position of the first elemnt with an invalid data type in
  the SQLDA.  A common reason why this error occurs is when
  DB2 attempts to describe large object data residing at a
  non-DB2 server.  Some of the SQLTYPEs that can cause this
  error are: LOB, BLOB, CLOB, and DBLOB.
  
  System Action: The statement cannot be executed.
  
  Programmer Response: The application program must not
  include any SQL operations that describe SQL data types
  which DB2 Version 2 Release 3 does not support when DB2
  is the application requester (AR).  For example, instead of
  dynamically selecting all columns from SYSTABLES, only
  select those columns that have data types defined to DB2.
  If the error is caused by an unsupported LOB type, then
  exclude such data from the list of data to be described.
  
  SQLSTATE: 56084
  ===============================================================
  Version 2 Release 3 Book Title:  Messages and Codes
  Pages: 4-164
  Change Description:
  
  00D44034
  
  Explanation: The DB2-DL/I batch support cannot continue
  because an unrecoverable error was encountered during
  resolve indoubt processing between IMS and DB2.
  The status of the current indoubt DB2 thread remains
  unchanged.
  
  This abend reason code is issued by the following CSECT:
  DSNMTV03
  
  System Action: The DB2-DL/I batch support processing
  is terminated, and a DB2 04E SVC dump is requested.
  
  Operator Response: Enter the DISPLAY THREAD
  TYPE (INDOUBT) command to determine the current status of
  indoubt thread processing between IMS and DB2
  at the time of the failure. Notify the system programmer.
  
  System Programmer Response: This may be an internal protocol
  error between the IMS external subsystem attach facility and
  the DB2 IMS attachment facility, or an execution environment
  error external to both IMS and DB2.  Examine both the IMS
  and MVS console logs for any error messages or abnormal
  return codes associated with the DL/I batch job.
  
  Problem Determination: Locate and examine any DB2 IMS
  attachment snap records (code X'5501FE') that are
  present in the IMS log data set, and examine WAL trace table
  entries included in the dump.
  
  If a DB2 reason code is provided in either the WAL trace
  entry, or the WALSFER2 field of the X'5501FE' log record,
  follow the instructions associated with this reason code for
  additional information concerning the failure.
  
  If you suspect an error in DB2, refer to Section 3 of
  Diagnosis Guide and Reference for information on identifying
  and reporting the problem.
  
  Collect the following diagnostic items listed in Appendix B,
  "Problem Determination": 1, 2, 5, 24, 26, 31, 44, 48, 49.
  ================================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: 4-189
  Change Description:
  
  In abend reason codes 00E2000D and 00E2000E, replace the
  SYSTEM PROGRAMMER RESPONSE with the following:
  
  The most likely cause of the problem is a storage overlay
  or an invalid storage request from a DB2 component.  A
  product other than DB2 could cause the storage overlay problem.
  In most cases, you should call the IBM Support Center for help
  in diagnosing the problem.
  ================================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: 4-244
  Change Description:
  
  In abend reason code 00E4070A, replace the USER RESPONSE,
  SYSTEM PROGRAMMER RESPONSE, and PROBLEM DETERMINATION sections,
  as follows:
  
  USER RESPONSE: Review the definition of the exception tables
  involved to determine if the following conditions are causing
  the error:
  
   -  The exception table has referential constraints.
   -  The exception table has unique indexes.
   -  The exception table "table-name2" is identical with
      "table-name1" in the FOR EXCEPTION keyword.
  
  If none of these is the cause, notify the system programmer.
  
  SYSTEM PROGRAMMER RESPONSE: Determine the failing environment,
  and refer to Section 3 of Diagnosis Guide and Reference for
  information on identifying and reporting the problem.
  
  PROBLEM DETERMINATION: If the errors listed in the User
  Response section are not the cause, this is an internal error.
  
  Collect the following diagnostic items listed in Appendix B,
  "Problem Determination" on page X-5: 1, 5.
  ================================================================
  Book Title:  Messages and Codes, SC26-4379-02
  Page Number: X-8
  Change Description:
  
  Add the following entry to figure 7 in Appendix B:
  
  ABEND Reason Code   CSECT-name:ERQUAL  Explanation
    00C90101           DSNIRNXT:53D3        3
  ================================================================
  

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