PI94364: UNEXPECTED SQLCODE713 FOR SET CURRENT APPLICATION COMPATIBILITY AFTER FALL BACK TO FL100 FROM FL501

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• QMF/TSO packages bound with APPLCOMPAT(V12R1M501) when running
  at FL501.
  Then fallback to FL100, within QMF/TSO, special register CURRENT
  APPLICATION COMPATIBILITY was initialized to V12R1M501.
  If user or QMF itself try to SET CURRENT APPLICATION
  COMPATIBILITY to V12R1M501, user or QMF gets: SQLCODE -713.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Db2 v12 for z/OS users of special                        *
  * register CURRENT APPLICATION COMPATIBILITY.                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * An unexpected SQLCODE713 is received                         *
  * for the special register                                     *
  * CURRENT APPLICATION COMPATIBILITY                            *
  * after reverting back to function level                       *
  * FL100 from FL501.                                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  An unexpected SQLCODE713 is received for the
  CURRENT APPLICATION COMPATIBILITY special register
  after reverting back to function level FL100 from FL501.
  
  Here's the reported scenario.
  
  Step 1.
  Running Db2 12 for z/OS at FL501
  with QMF/TSO packages bound with
  the APPLCOMPAT(V12R1M501) bind
  option.
  
  Step 2.
  Fell back to FL100 and did not
  change the QMF/TSO APPLCOMPAT
  bind options.
  
  Step 3.
  After going back to FL100, within QMF/TSO,
  the CURRENT APPLICATION COMPATIBILITY
  special register is initialized to
  V12R1M501 (due to the APPLCOMPAT bind option).
  
  Step 4.
  If the user (or via QMF) tries to set special
  register as follows,
  SET CURRENT APPLICATION COMPATIBILITY to V12R1M501,
  the user (or QMF) receives an unexpected SQLCODE -713.
  
  A similar scenario can be described as follows:
  
  1.The Db2 system is at level V12R1M501.
  2. Create a package with
     SET CURRENT APPLICATION COMPATIBILITY = 'V12R1M501'.
  3. BIND the package with BIND option APPLCOMPAT(V12R1M501).
  4. Execute the package.
  5. Revert the Db2 system to M100*
  6. Execute the existing package again containing
     the special register
     SET CURRENT APPLICATION COMPATIBILITY = 'V12R1M501'.
  7. Note the error,  SQLCODE -713 issued from
  DSNXRSPG error location -711.
  

Problem conclusion

• The code in Db2 is modified to process the special register
  CURRENT APPLICATION COMPATIBILITY
  properly to prevent the SQLCODE -713.
  
  Additional Keywords: SQLCODE713 SQLSPECIALREG
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  UI55851

Modules/Macros

• DSNXRSPG DSNXOSPR
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI55851

     UP18/05/30 P F805 ¢

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.