II07456: CHANGES TO APPLICATION PROGRAMMING AND SQL GUIDE THAT DID NOT MAKE R230 GA PUBS

APAR status

• Closed as canceled.

Error description

• This apar is a continuation of apar II06453
  and documents changes to the DB2 Application
  Programming and SQL Guide that did not make R230 GA
  Pubs.  5740XYR00 SC26-4377-02
  ================================================================
  
  DB2 Version 2 Release 3 Application Programming and SQL Guide,
      SC26-4377-02, page 423-425:  Replace the section titled
      "Return and Reason Codes" with:
  
  Error Messages and DSNTRACE
  ---------------------------
  
  CAF produces no error messages unless you allocate a DSNTRACE
  data set.  If you allocate a DSNTRACE data set either
  dynamically or by including a //DSNTRACE DD statement in your
  JCL, CAF writes diagnostic trace message to that data set.  You
  can refer to "Sample JCL for Using CAF" on page 425 for sample
  JCL that allocates a DSNTRACE data set.  The trace message
  numbers contain the last 3 digits of the reason codes.
  
  Return and Reason Codes Generated by CAF
  ----------------------------------------
  
  This section explains the return and reason codes that CAF
  returns.  The codes are returned either to the variables named
  in the return and reason code parameters of a CAF call or, if
  those parameters are not used, to registers 15 and 0. Detailed
  explanations of the reason codes appear in Messages and Codes.
  
  When the reason code begins with X'00F3' (except for
  X'00F30006'), you can invoke the CAF TRANSLATE function and
  obtain printable, and displayable, error message text.
  
  For SQL calls, CAF returns standard SQL return codes in the
  SQLCA.  See Section 2 of Messages and Codes for a list of those
  return codes and their meanings.  CAF returns IFI return and
  reason codes in the instrumentation facility communication area
  (IFCA).
  
    Return code   Reason code   Explanation
    -----------   -----------   -------------------------------
    0             X'00000000'   Successful completion.
  
    4             X'00C10823'   Release level mismatch between DB2
                                and the call attachment facility
                                code.
  
    4             X'00C10824'   CAF reset complete. Ready to make
                                a new connection.
  
    200 (note 1)  X'00C10201'   Received a second CONNECT from the
                                same TCB.  The first CONNECT could
                                have been implicit or explicit.
  
    200 (note 1)  X'00C10202'   Received a second OPEN from the
                                same TCB. The first OPEN could
                                have been implicit or explicit.
  
    200 (note 1)  X'00C10203'   CLOSE issued when there was no
                                active OPEN.
  
    200 (note 1)  X'00C10204'   DISCONNECT issued when there was
                                no active CONNECT.
  
    200 (note 1)  X'00C10205'   TRANSLATE issued when there was no
                                connection to DB2.
  
    200 (note 1)  X'00C10206'   Wrong number of parameters or the
                                end-of-list bit was off.
  
    200 (note 1)  X'00C10207'   Unrecognized function parameter.
  
    200 (note 1)  X'00C10208'   Received requests to access two
                                different DB2 subsystems from the
                                same TCB.
  
    204           (note 2)      CAF system error. Probable error
                                in the attach or DB2.
  
  Notes:
  
  1 A CAF error probably caused by errors in the parameter lists
    coming from application programs.  CAF errors do not change
    the current state of your connection to DB2; you can continue
    processing with a corrected request.
  2 System errors cause abends.  For an explanation of the abend
    reason codes see Section 4 of Messages and Codes.  If tracing
    is on, a descriptive message is written to the DSNTRACE data
    set just before the abend.
  
  Subsystem Support Subcomponent Codes (X'00F3')
  ----------------------------------------------
  
  These reason codes are issued by the subsystem support for
  allied memories, a part of the DB2 subsystem support
  subcomponent that services all DB2 connection and work requests.
  The codes, along with abend and subsystem termination reason
  codes issued by other parts of subsystem support, are described
  in Section 4 of Messages and Codes.
  

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