IZ60647: GETJCCSPECIALREGISTERPROPERTIES() THROWS -4700 ERROR AGAINST DB2Z/OS DATABASES RUNNING IN COMPATIBILITY MODE

DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• The getJccSpecialRegisterProperties() method throws a -4700
  error against DB2 z/OS databases running in Compatibility Mode.
  
  Beginning with JCC 3.53, a new method
  getJccSpecialRegisterProperties() has been introduced.  This
  method currently does not perform a check against a DB2 z/OS
  database to confirm if it is running in New Function Mode or
  Compatibility Mode.  As such, the method generates the following
  SQL which uses several registers that are available only in New
  Function Mode.
  
  select CURRENT CLIENT_ACCTNG, CURRENT CLIENT_APPLNAME, CURRENT
  CLIENT_USERID, CURRENT CLIENT_WRKSTNNAME, CURRENT DEGREE,
  CURRENT FUNCTION PATH, CURRENT MAINTAINED TABLE TYPES FOR
  OPTIMIZATION, CURRENT PACKAGE PATH, CURRENT REFRESH AGE,
  CURRENT SCHEMA, CURRENT SQLID from SYSIBM.SYSDUMMY1
  
  As several of these registers do not exist in a DB2 z/OS
  database running in Compatibility Mode, a check needs to be
  added to the method to detect which mode the target database is
  running, and generate the appropriate syntax based on the
  database mode.
  

Local fix

• No current workaround beyond converting the target database to
  run in New Function Mode.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users running JCC 3.53+ connected to DB2 on z/OS running in  *
  * Compatability Mode                                           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The getJccSpecialRegisterProperties() method throws a -4700  *
  * error against DB2 z/OS databases running in Compatibility    *
  * Mode.                                                        *
  *                                                              *
  *                                                              *
  * Beginning with JCC 3.53, a new method                        *
  * getJccSpecialRegisterProperties() has been introduced.  This *
  * method currently does not perform a check against a DB2 z/OS *
  * database to confirm if it is running in New Function Mode or *
  * Compatibility Mode.  As such, the method generates the       *
  * following SQL which uses several registers that are          *
  * available only in New Function Mode.                         *
  *                                                              *
  *                                                              *
  *                                                              *
  * select CURRENT CLIENT_ACCTNG, CURRENT CLIENT_APPLNAME,       *
  * CURRENT CLIENT_USERID, CURRENT CLIENT_WRKSTNNAME, CURRENT    *
  * DEGREE, CURRENT FUNCTION PATH, CURRENT MAINTAINED TABLE      *
  * TYPES FOR OPTIMIZATION, CURRENT PACKAGE PATH, CURRENT        *
  * REFRESH AGE, CURRENT SCHEMA, CURRENT SQLID from              *
  * SYSIBM.SYSDUMMY1                                             *
  *                                                              *
  *                                                              *
  * As several of these registers do not exist in a DB2 z/OS     *
  * database running in Compatibility Mode, a check needs to be  *
  * added to the method to detect which mode the target database *
  * is running, and generate the appropriate syntax based on the *
  * database mode.                                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to DB2 9.1 FP8 or convert target database to run in  *
  * New Function Mode.                                           *
  ****************************************************************
  

Problem conclusion

• 9.1 FP8
  

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:

Fix information

• Fixed component name

  DB2 CUE ISERIES

• Fixed component ID

  5724M1500

Applicable component levels

• R910 PSY

     UP