Question & Answer
What are the known issues, limitations and work-arounds for using IBM z/OS Debugger with COBOL v6.2?
The following table lists the issues, limitations and available work-arounds for IBM z/OS Debugger with COBOL v6.2:
|Compile option||All||Limitation||IBM z/OS Debugger does not support TEST(NOSOURCE).||None.|
|Debug command||Debug Tool compatibility
|Issue||When explicit debug mode is active and a user enters the LoadDebugData (LDD) command for the load module and compile unit, IBM z/OS Debugger does not find the side file for that compile unit.||None.|
|Breakpoints||Debug Tool compatibility||Issue||When compiling with TEST(SEPARATE), breakpoints set using AT STATEMENT may fail to restore.||Reset the breakpoint after the debug sessions initiates.|
|Debug Tool compatibility||Issue||
There are a number of known issues and limitations with usage of COBOL paragraph breakpoints in the debugger.
|A fix has been provided by z/OS Debugger. See APAR PH13364|
|Debug info||All||Limitation||When compiling with TEST(SEPARATE) and using EQADEBUG to specify the location for debug information, a user cannot specify a z/OS UNIX directory.||None.
Only a *.dbg file can be specified in z/OS UNIX.
|Debug Tool Compatibility
|Limitation||For a COBOL v6.2 program compiled with TEST (SEPARATE), a user must specify the side file location. This is because the COBOL v6.2 compiler does not store the original location of the side file in the generated load module. Users can do this by specifying the EQADEBUG DD card, the SET DEFAULT LISTING command, the EQAUEDAT user exit, the SET SOURCE command or the EQA_DBG_SYSDEBUG environment variable.||None.
This is a requirement for finding side files for a COBOL v6.2 program compiled with TEST(SEPARATE).
|Debug Tool Compatibility
|Limitation||If the compile unit name does not match the member name for the side file, users must use the SET SOURCE command to specify the location of the side file.||None.
This is a requirement for finding side files for a COBOL v6.2 program when the member name does not match.
|Full-screen||Issue||If you debug CICS and use the DTCN transaction and do not bind the LE assembler exit EQADCCXT to debug programs compiled with COBOL v6.2 or above with compile options TEST(SEPARATE) or TEST(SEPARATE(DSNAME)) and move the separate debug files after compilation without specifying a EQADEBUG DD in your CICS region that points to the moved side file, the remote debug session will not start.||
Addressed in z/OS Debugger 15.0.1. See PH31381.
For older versions, choose any of the following:
|Debug Tool Compatibility||Limitation||For COBOL v6.2 programs compiled with TEST(SEPARATE(DSNAME)), z/OS Debugger fails to display the appropriate SYSDEBUG data set name when pressing PF4 during full screen debugging.||
Addressed in z/OS Debugger 14.2.4 and 15.0.0.
See APAR PH25820.
|Stepping||Debug Tool compatibility
|Issue||After compiling with TEST(SEPARATE), an application may run to completion when performing a Step Over for CU at initialization.||Use Step Into instead of Step Over.|
|Debug Tool compatibility||Issue||After compiling with the November 2018 COBOL compiler PTF (APAR PH04745/PTF UI59885) the STEP OVER command on a PERFORM statement will incorrectly step over the PERFORM statement and the statement after it.||An update is provided by the compiler in APAR PH06193.|
|Listing||Standard||Issue||When specifying EQASRCE or EQA_DBG_SRCE to specify alternate location for source, the source will be found but the name of the file in the debug editor shows the path to the location where the source was originally found.||Ignore the name of the source in the debug editor.|
|Visual Debug||Standard||Limitation||Visual Debug does not work when the source view is used.||None.|
18 March 2021