PI59378: GHU FOLLOWED BY REPL CALL TO UPDATE THE SOURCE SEGMENT OF A DEDB WITH FPSI RESULTS IN A FH STATUS CODE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer did a GHU followed by REPL call to update the source
  segment of a DEDB (which had a FPSI) & got an FH status code.
  There were fields in the source segment that were part of the
  duplicate data (DDATA) in the pointer segment.  We need to
  update those fields as part of index maintenance.  For DDATA
  index maintenance, (because DDATA is not part of the key), we do
  a GHU followed by REPL.  But REPL calls against the DDATA fields
  in the secondary index are only allowed when the secondary index
  is defined as NOPROT and the customer is processing the
  secondary index as a stand alone database.  But the secondary
  index in this case was by default defined as PROT, and when we
  issued the REPL call, the full function replace module set a
  status code  of AM meaning an attempt to change system protected
  data. When we return back to Fast Path, because of the AM status
  code, we issue an FH.
  *
  REPL calls to update DDATA in a secondary index are only allowed
  when the secondary index is being processed as a stand alone
  database & the secondary index is defined as NOPROT.  But here
  we are doing index maintenance.
  We should complete the REPL call during index maintenance
  regardless of the PROT/NOPROT specification.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IMSFP V14 DEDB Fast Path Secondary Index FPSI users.         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * GHU FOLLOWED BY REPL CALL TO UPDATE THE SOURCE SEGMENT OF A  *
  * DEDB WITH FPSI RESULTS IN A FH STATUS CODE                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * INSTALL CORRECTIVE SERVICE FOR APAR/PTF                      *
  ****************************************************************
  Customer did a GHU followed by REPL call to update the source
  segment of a DEDB (which had a FPSI) & got an FH status code.
  
  There were fields in the source segment that were part of the
  
  duplicate data (DDATA) in the pointer segment.  We need to
  update those fields as part of index maintenance.  For DDATA
  index maintenance, (because DDATA is not part of the key), we do
  a GHU followed by REPL.  But REPL calls against the DDATA fields
  in the secondary index are only allowed when the secondary index
  is defined as NOPROT and the customer is processing the
  secondary index as a stand alone database.  But the secondary
  index in this case was by default defined as PROT.  When we
  issued the REPL call, the full function replace module set a
  status code AM meaning an attempt to change system protected
  data.   Because of the AM status code, Fast Path issue an FH.
  

Problem conclusion

• The following change has been made to correct the reported
  problem:
  DFSDLDR0:   Modified code to bypass issue AM status when it
  detect protected data being replaced, if the caller is Fast Path
  index maintenance.
  

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:

  PI59658 UI37281

Modules/Macros

• DFSDLDR0
  

Fix information

• Fixed component name

  IMS V14

• Fixed component ID

  5635A0500

Applicable component levels

• R401 PSY UI37281

     UP16/04/28 P F604 ¢

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.