PM74477: ABEND0C4 RC00000038 DSNXEDWA OFFSET1660 WITH PRE-V8 PACKAGE / TRIGGER THAT REFERS TO SPECIAL REGISTERS I 12/10/24 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• xxx,ABND=0C4-00000038,U=user  ,M=(N),C=910.RDS -SQL
  ,M=DSNTFRCV,LOC=DSNXGRDS.DSNXEDWA+1660
  
  
  
  The problem occurs for packages bound before Version 8 that
  reference one of the following special registers in an SQL
  statement:
  
  CURRENT PACKAGESET, CURRENT PATH, CURRENT SQLID, CURRENT USER
  and CURRENT OPTIMIZATION HINT
  
  SQLCODE -909 SQLCODE909 should be issued instead.
  
  KEYWORDs:
  SQLTRIGGER SQLID
  

Local fix

• Rebind of the old package is a sufficient workaround for the
  problem.
  
  DROP/CREATE TRIGGER
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 9 for z/OS users of special register *
  *                 packages bound before DB2 for z/OS V8.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABEND0C4 RC00000010 CSECT DSNXEBR can   *
  *                      occur when running a package bound      *
  *                      before DB2 V8 with special register     *
  *                      setting.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  ABEND0C4 RC00000010 can happen at CSECT DSNXEBR when any package
  bound on a release prior to Version 8 that has an SQL statement
  that references one of the following special registers :
  (CURRENT PACKAGESET,CURRENT PATH,CURRENT SQLID,CURRENT USER or
  CURRENT OPTIMIZATION HINT)
  The problem occurs when the package is executed on Version 9
  after PM66040/UK80992 applied. This problem happens because
  PM66040 fixed an internal infinite loop problem and the fix
  bring more opportunity to open another code path for an
  incorrect procedure handling.
  
  An example of an SQL application which may encounter the problem
  follows :
  
  EXEC SQL
   SELECT CURRENT SQLID
    INTO :HV FROM T1;
  
  Bind the package on DB2 V7 or previous release.
  
  BIND PACKAGE (P1) MEMBER(PMR1)
  BIND PLAN (P1) PKLIST (P1.PMR1)
  
  Above abend can occur when running the program on DB2 V9.
  

Problem conclusion

• DB2 has been changed to call the internal procedure correctly.
  
  ADDITIONAL KEYWORDS : SQLSPECIALREG
  

Temporary fix

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

Comments

• ž**** PE14/08/22 FIX IN ERROR. SEE APAR PI23366  FOR DESCRIPTION
  

APAR Information

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

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

  UK91616

Modules/Macros

• DSNXEBR
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R910 PSY UK91616

     UP13/02/28 P F302 ®

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.