Highlighted
New Member.
1087 views

Fix for MFED JCL debugger in Enterprise server the COBOL module breakpoints not working the code is bypassing all the preassigned breakpoints.

I am using MFED for Eclipse -  Enterprise Developer 3.0 Version: 3.0.00494.

There is an issue in the Enterprise Debugger for both CICS and JCL , when set with breakpoints in COBOL modules. The debugger doesn't stop on any of the breakpoints and runs through the entire routine without stopping. It does not look like a code issue since its working fine in Mainframe terminal.

Can anyone please suggest how to fix this issue?

0 Likes
3 Replies
Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

One - is the region set up for dynamic debugging? Have the project been compiled for debugging? When you start the debugger for either CICS or Batch does the debug perspective start and do you get the waiting for attachment message? Do you get any particular message? Is the behavior the same for both batch and CICS? Have you tried setting a breakpoint in the main module prior to starting?
0 Likes
Highlighted
New Member.

The region has been set for Dynamic Debugging in The ES server instance and clean compile build has been run prior to starting the ES server instance. Yes there is prompt for Debugger perspective when selecting CICS or batch debugging and the Debug View tab has the waiting for attachment message prior to the JCL submission to the enterprise server.

The breakpoints issue is happening for both CICS and Batch debugging. All breakpoints were assigned prior to starting the debugger. The issue is reoccurring whenever there is a change made in any COBOL module in the project and then recompiled and set to debug. Currently using Debug Launch config files to start debugging.

Debugging Console showing just these two messages and the routine runs through without stopping on the breakpoint:

Loaded: E:\MFED\bin\casumxit.dll\casumxit- Not compiled for debugging
Loaded: E:\MFED\bin\mfjmvs.dll\mfjxxit- Not compiled for debugging
0 Likes
Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Do you have multiple directories on the transaction path for CICS or JES Program Path for batch. Search your drives to see if you may have multiple versions of the PROGRAM.DDL and PROGRAM.IDY files. I'm assuming you are building the projects to DLL's.

Where are the executables residing, a local drive or a network drive?
How did you start your regions - the web admin page, the server explorer page in Eclipse or from the command line with CASSTART?
Do you have any fix packs applied to Enterprise Developer? If not you may want to get the latest one and apply it to see if that may help. Also Enterprise Developer 4 has been aout for some time, it's a free upgrade if you are on maintenance so you may also want to consider upgrading, although this issue should have nothing to do with being on 3.0 as thousands of customer use it daily with no issues.
if you are on maintenance ro doing a evaluation, you may want to consider opening a support ticket. supportline.microfocus.com as the engineers there are likely to be at least as responsive as this forum
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.