PI48427: INCORRECT WORKING-STORAGE DATA WHEN PROGRAM CALLED BY BOTH PL/I AND COBOL

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When an Enterprise COBOL V5 program is first FETCHed and CALLed
  by a PL/I program, then subsequently CALLED dynamically by anoth
  er COBOL program, the WORKING-STORAGE data of the first COBOL pr
  ogram is not in the last used state.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Enterprise COBOL V5 users compiling and      *
  *                 running programs that are both fetched by    *
  *                 PL/I programs and dynamically called by      *
  *                 COBOL programs.                              *
  *                                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABEND or Incorrect output: When an      *
  *                      Enterprise COBOL V5 program is first    *
  *                      FETCHed and CALLed by a PL/I program,   *
  *                      then subsequently CALLed dynamically by *
  *                      another Enterprise COBOL V5 program,    *
  *                      the WORKING-STORAGE data of the first   *
  *                      COBOL program is not in the last used   *
  *                      state. In addition, the application may *
  *                      terminate abnormally with an S0C4       *
  *                      ABEND, when the COBOL program is being  *
  *                      cleaned up twice by both PL/I and COBOL *
  *                      termination (via LE Event 41.)          *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Apply provided service.                      *
  ****************************************************************
  When searching for the target program by name in the internal
  load list, the dynamic call library routine failed to locate
  programs that were originally loaded and called by another LE
  language other then COBOL. This caused the dynamic call library
  routine to allocate a new WORKING-STORAGE area for the second
  invocation. During LE enclave termination, PL/I termination
  would signal an ILC CANCEL to the COBOL program, at the same
  time normal COBOL termination would try to clean up all loaded
  COBOL programs as well. This would cause the WORKING-STORAGE
  address to be freed twice, resulting in an S0C4 ABEND.
  

Problem conclusion

• The Enterprise COBOL V5 dynamic call library routine is changed
  to search the load list again using the program entry point
  address, so that the WORKING-STORAGE associated to the program
  can be reused if one exists. The COBOL enclave termination code
  is changed to skip the freeing of WORKING-STORAGE. The
  deallocation is unnecessary since normal LE enclave termination
  would release all heap storage where the COBOL WORKING-STORAGE
  is allocated from.
  

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

• IGZXLPKA
  

Fix information

• Fixed component name

  LE ENT COBOL LI

• Fixed component ID

  568819812

Applicable component levels

• R7A0 PSY UI32124

     UP15/10/23 P F510

• R780 PSY UI32125

     UP15/10/23 P F510

• R790 PSY UI32126

     UP15/10/23 P F510

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.