PH66809: IDAA WRAPPER RECEIVE TRACES API RETURNS A 16KB LIMITATION STRING, CAUSING POTENTIAL OVERFLOW

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Using UMS / Admin Foundation, the creation of an accelerator
  trace fails with message IZPSV0002E accompanied by exception
  org.springframework.core.io.buffer.DataBufferLimitException.
  
  The legacy IDAA Wrapper receiveTraces API returns its response
  Using UMS / Admin Foundation, the creation of an accelerator
  trace fails with message IZPSV0002E accompanied by exception
  org.springframework.core.io.buffer.DataBufferLimitException.
  
  as a plain string in the form of a byte array, which has a 16 KB
  size limitation for each call while building and appending the
  final response. When handling large responses (e.g., around 700
  MB), the recursive approach used for buffer construction leads
  to a stack overflow exception due to excessive recursion depth.
  
  
  The receiveTraces API in the IDAA Wrapper has been updated to
  return an InputStreamResource instead of a byte array. This
  enhancement resolves the size limitation by enabling
  chunk-by-chunk buffer construction, thereby supporting larger
  output traces.
  
  
  Affected Users: DevOps administrators and users working on the
  IDAA accelerator to save the traces.
  
  Additional keywords:
  TS019136679 TS019261894
  Admin Services
  20250611-0147-IDAA-Admin-Services
  IDAAV8R1/K IDAAV7R5/K
  
  Prerequisites= UMS 1.2.0.10
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the IBM Db2 Administration          *
  *                 Foundation for z/OS and IDAA integration     *
  *                 features                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Stack overflow exception due to         *
  *                      excessive recursion depth.              *
  ****************************************************************
  The legacy IDAA Wrapper receiveTraces API returns its response
  as a plain string in the form of a byte array, which has a 16 KB
  size limitation for each call while building and appending the
  final response. When handling large responses (e.g., around 700
  MB), the recursive approach used for buffer construction leads
  to a stack overflow exception due to excessive recursion depth.
  
  The receiveTraces API in the IDAA Wrapper has been updated to
  return an InputStreamResource instead of a byte array. This
  enhancement resolves the size limitation by enabling
  chunk-by-chunk buffer construction, thereby supporting larger
  output traces.
  

Problem conclusion

• Apply the PTF provided by this APAR
  

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:

Modules/Macros

• IZPHLVP  IZPMNFST IZPSERVE IZPUI    IZPYAML
  

Fix information

• Fixed component name

  UNIFIED MGMT SV

• Fixed component ID

  5698UM100

Applicable component levels

• R120 PSY UO03795

     UP25/06/28 P F506

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.