A fix is available
APAR status
Closed as program error.
Error description
DB2 programs compiled with COB V5.2 that use the integrated DB2 coprocessor and are tested with Debug Tool do not have the actual values of the DB2 variables displayed in Debug Tool for variables contained in a SELECT or FETCH. Instead, Debug Tool shows an address for each variable contained in the SELECT or FETCH. Example of output: 0004 ADDRESS OF DBLCOL-LENDING-TYPE-N OF DBLCOL-RECORD 0005 X'29A1BFA8' 0006 ADDRESS OF DBLCOL-STOCK-BOND-TYPE-N OF DBLCOL-RECORD 0007 X'29A1BFB1' The compiler generates "ADDRESS OF" because the DB2 coprocessor is converting the EXEC SQL into a call that contains "ADDRESS OF", and the compiler is generating the DWARF automonitor info based on that instead of what's in the original source. The BLOG at https://www.ibm.com/developerworks/community/blogs/31c890c6-ace1 -4eeb-af6b-5950f3a1a5d1/entry/debug_tool_support_for_cobol_5_1_l ength_of_and_address_of_in_automonitor_output?lang=en discusses that when "ADDRESS OF" is used in the COBOL code that COB V5.1 will now display the address. However, this should not be applicable to the variables in a SELECT and FETCH.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of Enterprise COBOL V5.1 using the * * TEST compiler option on programs that have * * EXEC SQL statements in them and then * * debugging them using the auto monitoring * * feature of the Debug Tool product. * **************************************************************** * PROBLEM DESCRIPTION: Incorrect output of Debug Tool: When * * debugging a COBOL program that has * * EXEC SQL statements in it, the auto * * monitoring feature of Debug Tool * * displays the address of all host * * variables in the SQL statement instead * * of displaying the contents of the host * * variables. * **************************************************************** * RECOMMENDATION: * **************************************************************** The compiler generated a debug auto monitoring information based on internally generated COBOL statements from the EXEC SQL statements, instead of the SQL statements themselves, which is why we got the address of a host variables instead of the host variable itself in the auto monitoring table.
Problem conclusion
Apply provided service.
Temporary fix
Comments
APAR Information
APAR number
PI53065
Reported component name
ENT COBOL FOR Z
Reported component ID
5655W3200
Reported release
520
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-11-24
Closed date
2015-11-30
Last modified date
2016-01-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
IGYCCBE
Fix information
Fixed component name
ENT COBOL FOR Z
Fixed component ID
5655W3200
Applicable component levels
R520 PSY UI33431
UP15/12/02 P F512
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.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS6SG3","label":"Enterprise COBOL for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"520","Edition":"","Line of Business":{"code":"LOB17","label":"Mainframe TPS"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"520","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 January 2016