PH38416: Entry point name is used as input to IGZIUXB instead of compile unit name for programs with multiple entry points

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• If a program compiled with TEST(SEPARATE(NODSNAME)) is called
  using a secondary entry point, for example DLITCBL for IMS
  programs using that convention, the debug information will be
  inaccessible. Contrary to documentation, the exit IGZUIXB, used
  to map the compile unit name to a debug file, is passed the
  secondary entry name rather than the compile unit name.
  

Local fix

• Use TEST(NOSEPARATE).
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: User of Enterprise COBOL 6.2 and later       *
  *                 releases running programs compiled with      *
  *                 TEST(SEPARATE(NODSNAME)) that have           *
  *                 multiple entry points and produce a          *
  *                 CEEDUMP when the program is entered          *
  *                 through an alternate entry point.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: In the CEEDUMP, the COBOL               *
  *                      'Local Variables' section               *
  *                      generates the following message:        *
  *                                                              *
  *                      Variables for {program-name}:           *
  *                      COBOL variables were inaccessible.      *
  *                      Reason: no debug file was found.        *
  *                      (TEST(SEPARATE(NODSNAME) was used and   *
  *                      IGZIUXB/IGZIUXC failed).                *
  *                                                              *
  *                      Along with the message, the COBOL       *
  *                      statement number that results in the    *
  *                      CEEDUMP might be missing.               *
  ****************************************************************
  * RECOMMENDATION: Install the provided PTF.                    *
  ****************************************************************
  The COBOL Runtime had an error locating and using the side
  debug file for programs with multiple entry points
  compiled with TEST(SEPARATE(NODSNAME)) and entered through
  an alternate entry point when a CEEDUMP was produced.
  The alternate entry point name was being used for
  locating the side debug file (via IGZIUXB) rather than the
  compile unit name.
  
  COB0602T/K COB0603T/K
  

Problem conclusion

• The COBOL Runtime has been fixed to use the compile unit name
  to access the side debug file (via IGZIUXB) regardless
  of what entry point was used to enter a COBOL program.
  

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:

  UI79086 UI79087 UI79088

Modules/Macros

• IGZCEV4  IGZCMGEN IGZCMGUE IGZLLIBV IGZXAPI  IGZXCA31 IGZXCDA
  IGZXD24  IGZXDMR  IGZXJNI2 IGZXLPIO IGZXLPKA IGZXLPKB IGZXLPKC
  IGZXLPKD IGZXLPKE IGZXLPKF IGZXLPKG IGZXPK2
  

Fix information

• Fixed component name

  LE ENT COBOL LI

• Fixed component ID

  568819812

Applicable component levels

• R7B0 PSY UI79086

     UP22/02/01 P F201

• R7C0 PSY UI79087

     UP22/02/01 P F201

• R7D0 PSY UI79088

     UP22/02/01 P F201

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.