PH50392: LOCAL VARIABLES MISSING IN CEEDUMP FOR COBOL LLA/VLF PROGRAMS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• CEEDUMP may not print out Local Variables due to "Reason: cannot
  initialize DWARF in the program object for LLA/VLF. "
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Enterprise COBOL 6.2 and later      *
  *                 releases running programs loaded from LLA    *
  *                 and compiled with TEST(NOSEPARATE) 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: cannot initialize DWARF in      *
  *                      the program object for LLA/VLF.         *
  *                      Attempted DD:ddname(member):            *
  *                      //DD:STEPLIB({program-name})            *
  *                                                              *
  *                      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 loaded from LLA with multiple entry
  points
  compiled with TEST(NOSEPARATE) 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 within the program object
  rather than the compile unit name.
  
  COB0602T/K COB0603T/K COB0604T/K
  

Problem conclusion

• The COBOL Runtime has been fixed to use the compile unit name
  to access the side debug file within the program object
  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:

Modules/Macros

• IGZCEV4  IGZCJNI2 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

• R7C0 PSY UI90123

     UP23/01/24 P F301

• R7D0 PSY UI90124

     UP23/01/24 P F301

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.