PM81984: SQLCODE -725 WHEN SENDING A LOWER CASE SCHEMA NAME IN A SET CURRENT SCHEMA STATEMENT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• SQLCODE -725 SQLCODE725 from a distributed application when
  issuing a SET CURRENT SCHEMA = 'lower_case_name' clause.  The
  error text referred to a PRIOR ERROR.
  

Local fix

• In this instance, eClient was using data source with a custom
  property currentSchema with a lowercase value, and turning off
  WAS Connection Pooling circumvented this error.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 10 for z/OS users of current schema  *
  *                 special register in the distributed          *
  *                 environment.                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: DB2 incorrectly returned SQLCODE -725   *
  *                      (SQLCODE725) indicating the application *
  *                      has supplied an invalid schema value    *
  *                      for the current schema special register *
  *                      when running the application in the     *
  *                      distributed environment.                *
  *                                                              *
  *                      This APAR is applicable for all         *
  *                      applications connecting to DB2 v10 via  *
  *                      JDBC DataSource interface with          *
  *                      currentSchema='lowercase' passed in the *
  *                      connection string.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  DB2 incorrectly returned SQLCODE -725 (SQLCODE725) indicating
  the application has supplied an invalid schema value for the
  current schema special register when running the application
  in the distributed environment.
  
  The following java example can help illustrate the error:
  
  public class pm17324y {
  
   public static void main(String   args) throws SQLException {
  
    try {
     Class.forName("com.ibm.db2.jcc.DB2Driver");
    } catch (ClassNotFoundException e) {
     e.printStackTrace();
    }
  
    String url = "jdbc:db2://utecxxx.xxxx.xxx.xxx.xxx:xxx/xxxxxx";
    java.util.Properties props = new java.util.Properties();
    props.put("user", "xxxxxxx");
    props.put("password", "xxxxxxxx");
    props.put("traceFile", "trace.out");
    props.put("traceLevel",
                com.ibm.db2.jcc.DB2BaseDataSource.TRACE_ALL
      + "");
    //The following property setting is the one caused the problem
    props.put ("currentSchema", "dummy_schema_name_01");
  
    Connection con = DriverManager.getConnection(url, props);
    con.setAutoCommit(false);
    System.out.println("Got connection " + con.toString());
    System.out.println("Autocommit is set to "
     + con.getAutoCommit());
    con.commit();
    con.close();
    System.out.println("Connection closed.");
   }
  }
  
  Additional keywords: SQLCODE725
  

Problem conclusion

• DB2 is fixed to avoid SQLCODE -725 (SQLCODE725).
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK91830

Modules/Macros

• DSNXESSR DSNXRSPG
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK91830

     UP13/03/07 P F303

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.