PH46915: ABEND 378-18 IN EZBREREM +ACC AT HIP6250

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• ABEND 378-18 occurs in CSECT EZBREREM (EZBRERET entry point)
  during normal task termination of application while attempting
  to release storage.
  
  ANALYSIS:
  This problem was caused by a very narrow timing window that is
  exposed during multiple executions of the resolver resource
  manager code during a recovery processing event.
  
  During normal task-termination of the application, code
  processing within the EZBRERET entry point of EZBREREM module is
  in a loop freeing storage blocks.
  
  System trace reveals that one of the storage release operations
  did not complete because the task received an ABEND 13E while
  the release operation was underway.
  
  ABEND 13E means the parent task asynchronously issued DETACH
  macro for this sub-task. Currently, not sure why that happened,
  but the system trace shows the resource manager code that was
  originally in a loop freeing storage blocks prior to the ABEND
  13E was driven again. In this subsequent iteration of the code,
  at the point where it is to loop through and free storage
  blocks, the ABEND 378-18 occurs because the pointer that
  contains the address to be freed still contained the last freed
  address from the previous iteration of the resource manager,
  before the ABEND 013E.
  
  KNOWN IMPACT:
  No impact other than dump being produced for ABEND 378-18.
  
  VERIFICATION STEPS:
  System trace should show an ABEND interrupting the code flow in
  EZBRERET during the storage release operation, and it should
  also show the subsequent ABEND 378-18 after the resource manager
  code is driven again and storage release is again attempted with
  the bad address.
  

Local fix

• .
  KEYWORDS:   AB378 ABEND378 ABEND378-18 AB378-18
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All the users of IBM Communications Servers for Z/OS Version *
  * 2 Release 5 IP: RESOLVER                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * ABEND 378-18 occurs during normal task termination of        *
  * application while attempting to release storage.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply PTF                                                    *
  ****************************************************************
  

Problem conclusion

• Resolver task termination processing has been amended to set
  pointers to the next RAID or next RAIM before releasing the
  storage for RAID or RAIM.
  

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:

  UI81673

Modules/Macros

• EZBREREM
  

Fix information

• Fixed component name

  TCP/IP MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R250 PSY UI81673

     UP22/09/10 P F209

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.