PI55201: IF A COBOL II SECONDARY ENTRY IS DYNAMICALLY CALLED FROM BOTH COBOL II AND COBOL V5, EACH MAY SEE A DIFFERENT WORKING-STORAGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• If a VS COBOL II module has a secondary entry at which it is
  dynamically called, it may end up with a different
  working-storage for a call from another VS COBOL II module and a
  call from a COBOL v5 module, as if the callee were in fact two
  different modules.
  
  In other words, state changes to the callee's working-storage
  when called by a VS COBOL II caller will not be present when the
  COBOL v5 caller later calls the callee, and vice versa. For
  example a file opened by one caller will appear closed to the
  other.
  
  This is a somewhat unusual callee structure in that in order for
  the callee to be called dynamically at the secondary entry, the
  executable must be built with the secondary entry name as the
  executable's ENTRY and NAME, not the usual PROGRAM-ID.
  

Local fix

• Use the PROCEDURE DIVISION statement as the entry point.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: User with applications containing a mix of   *
  *                 COBOL V5 programs and programs compiled with *
  *                 previous COBOL compiler releases,and both    *
  *                 types of programs make dynamic calls to VS   *
  *                 COBOL II programs with alternate ENTRY       *
  *                 points.                                      *
  *                                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Incorrect output:  The VS COBOL II      *
  *                      program may get file status 92 in READ, *
  *                      WRITE and REWRITE statements if the VS  *
  *                      COBOL II program is dynamically called  *
  *                      by both COBOL V5 and pre-V5 COBOL       *
  *                      programs.                               *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Apply provided service.                      *
  ****************************************************************
  After a VS COBOL II program with alternate ENTRY points is
  dynamically called by COBOL V5, a subsequent dynamic call to the
  same VS COBOL II program by a program compiled with a pre-V5
  compiler releases may cause the file control area or the
  WORKING-STORAGE section to be re-initialized.
  

Problem conclusion

• The library routine in COBOL V5 has been fixed to correctly
  handle dynamic calls to VS COBOL II programs with alternate
  ENTRY points.
  

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 UI34683

     UP16/01/28 P F601

• R780 PSY UI34684

     UP16/01/28 P F601

• R790 PSY UI34685

     UP16/01/28 P F601

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.