PM53154: MEMORY NOT RELEASED OR REUSED BY CALLING PROCESS WHEN A MAP FAILS WITH ERROR CODE 2 - 'NOT ENOUGH MEMORY TO EXECUTE MAP'

APAR status

• Closed as program error.

Error description

• When running a series using either the Launcher or the WTX API,
  after a map has finished running, the use of memory by the
  process should return to a base value.
  
  After the execution of a map that termintes with error code 2 -
  'Not enough memory to execute map' the memory is not released
  and not reused.  This can lead to further occurances of the
  condition, eventually leading to no available memory, and
  unpredictable results.
  

Local fix

• WTXCQ - WTX00039527
  PB / PB
  Circumvention: None
  

Problem summary

• Users Affected:
  WebSphere Transformation Extender customers who receive 'not
  enough memory' error
  
  Problem Description:
  If WTX map fails with 'not enough memory' error, all memory
  allocated for operands is not released. This can affect
  execution of other maps.
  In order to expose this issue, a map has to first fail with 'not
  enough memory'.
  
  Platforms Affected:
  ALL
  

Problem conclusion

• Correct the core engine code to release all memory when handling
  'not enough memory' error condition. This does not resolve
  original error caused by too large data processed as blob
  
  Delivered in:
  8.1.0.6, 8.2.0.6, 8.3.0.5, 8.4.0.1
  

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:

Fix information

• Fixed component name

  WEBSPHERE EXTEN

• Fixed component ID

  5724M4007

Applicable component levels

• R810 PSY

     UP