PK96747: ABND=0C4-00000010 DSNLVALM+148A

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DDFL09 DB2PRVT DB2HOP
  Abend 0C4-00000010 DSNLVALM+148A.
  
  PIDS/5740XYR00 PROGRAM ID: 5740XYR00
  RIDS/DSNLILLM#L LOAD MODULE NAME: DSNLILLM
  RIDS/DSNLVALM CSECT NAME: DSNLVALM
  AB/S00C4 SYSTEM ABEND CODE: 00C4
  PRCS/00000010 ABEND REASON CODE: 00000010
  REGS/0EA86 REGISTER/PSW DIFFERENCE FOR R0E: A86
  REGS/C071A REGISTER/PSW DIFFERENCE FOR R0C:-071A
  RIDS/DSNLFRCV#R RECOVERY ROUTINE CSECT NAME: DSNLFRCV
  HER SERVICEABILITY INFORMATION
  DATE ASSEMBLED: 11/09/06
  MODULE LEVEL: UK19563
  SUBFUNCTION: DCRM ADD LLMBTEST LATCH
  .
  The problem only happens with DB2z V9 and only when using
  Private Protocol.
  *************************************************************
  Additional symptoms and keywords:
    ABEND0C4 AB0C4 S00C4 0C4 0C4-00000010 00000010 RC00000010
      DSNLVALM DSNLVALM+148A 148A
    DPSBRQAP RQA refers to Above The Bar storage.
    Private Procotol
    Hop Hopping
    SNA VTAM Session Limit Limits exceeded or constrained
    CHK_LIMITED
  

Local fix

• 1) Bind package using DBPROTOCOL(DRDA) and/or
  2) Increasing the number of IBMDB2LM negotiated between two
     sites.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
  *                 Specifically where Private Protocol hop      *
  *                 conditions occur.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABEND 0C4-00000010 DSNLVALM+148A on     *
  *                      a DB2 9 for z/OS subsystem when         *
  *                      "hopping" via Private Protocol.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A remote client application (site1) accesses a DB2 9 for z/OS
  system (site2) via DRDA protocols and executes SQL that causes
  a Private Protocol "hop" to another DB2 z/OS system (site3).
  If SNA session limits are constrained between site2 and site3,
  the site2 DB2 9 for z/OS subsystem may abend 0C4-00000010
  DSNLVALM+148A.
  The abend can only occur in DB2 9 for z/OS subsystems because
  CSECT DSNLVALM does not expect, in a hop environment, that RQA
  control blocks may now reside Above The Bar.
  

Problem conclusion

• DSNLVALM has been changed to expect RQA control blocks to
  reside in storage above the 2gb addressing range.
  

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:

  UK50641

Modules/Macros

• DSNLVALM
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R910 PSY UK50641

     UP09/10/15 P F910

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.