A fix is available
APAR status
Closed as program error.
Error description
The wrong message displayed if the SYSDEBUG file is changed. The user sees: SYSDEBUG/SEPARATE file can not be found. But the correct message should be: The Debug File creation date does not match. * This can happen if the program has been recompiled and the SYSDEBUG side file has been replaced by the recompile, but the executable that is running is not from that same compilation.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: COBOL users who compiled their program with * * the TEST(SEPARATE) option and are running * * the program with the Debug Tool. * * * **************************************************************** * PROBLEM DESCRIPTION: When a program that was compiled with * * the TEST(SEPARATE) option is run with * * the Debug Tool, COBOL will validate * * that the SYSDEBUG side file is * * consistent with the load module being * * executed. * * * * If a recompile of the program is done * * using the TEST(SEPARATE) option, the * * side file from a previous compile * * can be overlaid by a new side file. * * This can cause a mismatch between * * the load module and side file if * * the executable from the earlier * * compile is run. * * * * The message that is issued in this * * case indicates that the SYSDEBUG side * * file cannot be found, rather than that * * the SYSDEBUG side file timestamp does * * not match the load module. The message * * can be misleading. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** The COBOL API that validates the SYSDEBUG side file against the load module did not return consistent return codes when there were problems encountered with the SYSDEBUG side file. This caused an incorrect error message to be issued by Debug Tool. The fix made in this APAR is not complete without the changes that were made for Debug Tool APAR PK65551. Without having the changes for both of these APARs applied there will not be any noticeable change in behavior.
Problem conclusion
The COBOL API is changed to give a consistent return code to Debug Tool when problems with a SYSDEBUG side file are encountered. To see the effects of the changes made for this APAR the fix for Debug Tool APAR PK65551 must also be applied. That fix will be available in the PTFs for the following Debug Tool rollup APARS: PK59841 for Debug Tool V6R1 PK61305 for Debug Tool V7R1 PK63156 for Debug Tool V8R1
Temporary fix
Comments
APAR Information
APAR number
PK65572
Reported component name
LE COBOL LIB
Reported component ID
568819802
Reported release
720
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2008-05-05
Closed date
2008-05-08
Last modified date
2008-06-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK36326 UK36327 UK36328
Modules/Macros
IGZIDCU
Fix information
Fixed component name
LE COBOL LIB
Fixed component ID
568819802
Applicable component levels
R720 PSY UK36326
UP08/05/29 P F805
R730 PSY UK36327
UP08/05/29 P F805
R740 PSY UK36328
UP08/05/29 P F805
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.
[{"Line of Business":{"code":"LOB16","label":"Mainframe HW"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.2"}]
Document Information
Modified date:
22 January 2021