PH37217: AFTER INSTALLING PH24597/UI70704, DB RECORDS RETRIEVED BY A PATHCALL, RECEIVE AN UNEXPECTED NO DATA CONDIT 21/05/13 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Application comes in via IMS Connect, using ODBM to get data
  from the Seg_lvl_04 segment via a path call from the account
  database. Seg_lvl_01 is the root, Seg_lvl_02 is child(parent
  Seg_lvl_01),  Seg_lvl_03 is child(parent Seg_lvl_02), and
  Seg_lvl_04 is child (parent Seg_lvl_03). Not all account entries
  have data in Seg_lvl_04.
  ?Before PH24597 was installed, good returns on the call would
  occur for all accounts regardless of the presence or absence of
  Seg_lvl_04.  The data requested from Seg_lvl_04 would be null if
  not present.
  ?After PH24597 was installed, accounts with Seg_lvl_04 data
  would succeed , accounts missing Seg_lvl_04 failed with ?no
  data? condition.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IMS V15 users who are using ODBM and issuing a path call *
  * from UDB                                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The problem is related to applications using IMS UDB and     *
  * ODBM to get data from IMS. Earlier, when IMS returned GE     *
  * status code due to being unable to find a segment that       *
  * satisfies the segment search argument (SSA) IMS was not      *
  * displaying any partial data in the segments that hit GE      *
  * code. After APAR PH24597, that behavior changed, IMS is      *
  * returning segment partial data even when it hits the GE      *
  * code.                                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When IMS UDB sends the handshake message to the ODBM server and
  gets the reply, the application can find out the ODBM level. If
  ODBM level is 9, the IMS UDB client will add a new code point
  together with a boolean flag to tell it wants the partial data
  or not. The ODBM Server will parse the new code point and
  respond appropriately.
  We have 2 following scenarios:
    1- Any applications that don't have an upgraded IMS UDB driver
  of level 8 or higher, the old behavior of not returning partial
  data when applications get GE status code will be applied.
    2- Any applications that have the upgraded IMS UDB driver of
  level 8 or higher and set the boolean flag to 1, they will get
  the new behavior that partial data is returned when GE status
  code happens.
  

Problem conclusion

• We are adding a new DRDA ODBM level 9 and new code point
  GEPARDTA for handling  getting partial data when IMS return GE
  state code for that segment.
  

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:

  UI78098

Modules/Macros

• CSLDDMO0 CSLDRDA0 CSLDBR00 CSLDIN00 CSLDDDMS CSLDREG0 CSLDDDMT
  

Fix information

• Fixed component name

  IMS V15

• Fixed component ID

  5635A0600

Applicable component levels

• R500 PSY UI78098

     UP21/11/18 P F111 {

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.