Skip to main content

cbl_debugbreak in Net Express called by VB.net

  • November 13, 2013
  • 24 replies
  • 0 views
A
  • Anonymous

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

24 replies

Chris Glazier
Forum|alt.badge.img+2
  • Chris GlazierModerator
  • Moderator
  • November 13, 2013

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

You can only have one debugger active under Windows at any one time so you can either debug the VB.NET side of it or the Net Express side of it but not both together.

If you run your VB.NET application without the debugger do you get the cbl_debugbreak prompt when your COBOL is called?

A
  • Anonymous
  • November 13, 2013

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

When I build the vb.net app as release and run as 'start without debugging'(albeit under the debug tab), I don't get a cbl_debugbreak prompt when COBOL is called - it just executes.

Chris Glazier
Forum|alt.badge.img+2
  • Chris GlazierModerator
  • Moderator
  • November 13, 2013

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

Are you sure that the COBOL .dll is actually being called?

How exactly are you calling the COBOL .dll from VB?

Is the COBOL compiled as a COM server or are you calling the unmanaged code using .NET P/Invoke?

Is Net Express installed on this machine or is this a production machine with Server 5.1 on it?

A
  • Anonymous
  • November 13, 2013

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

Net express and visual studio are on my machine, In net express, I can run the code through animator, but have to fill in linkage myself.  The vb code that calls it looks like this:

if NativeMethods.SetDllDirectory(CobolDirectory) Then

               Case BatchInterfaceType.PremiumVouchers

                   NativeMethods.RMFIEPVCH(batchLinkage)

           End Select

Public NotInheritable Class NativeMethods

 Private Declare Unicode Function GetShortPathName Lib "kernel32.dll" Alias "GetShortPathNameW" (ByVal longPath As String, <MarshalAs(UnmanagedType.LPTStr)> ByVal ShortPath As System.Text.StringBuilder, <MarshalAs(UnmanagedType.U4)> ByVal bufferSize As Integer) As Integer

      Friend Declare Sub RMFIEPVCH Lib "MFIPPVCH.DLL" Alias "MFIEPVCH" (ByRef start As BatchInterfaceLinkage)

A
  • Anonymous
  • November 19, 2013

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

Do I need to be out of .net when I call the .net front end (ie do I call it from DOS)?  I really want to get the debugger working in .net express cobol so I can see what is causing the problem.

Chris Glazier
Forum|alt.badge.img+2
  • Chris GlazierModerator
  • Moderator
  • November 19, 2013

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

If you would like to debug the COBOL portion under Net Express then the easiest way is to start the NX IDE and open your project containing the .dll to be debugged and then select Start Animating and click the browse button and navigate to the location of your VB .EXE program and select it as your starting program.

Then the VB program will run at full speed and when COBOL is called the animator will start and then you will be debugging the COBOL.

A
  • Anonymous
  • November 20, 2013

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

When I tried this I get:

The IDY file below does not contain any info for debugging GNT or OBJ code.  You cannot step through this program and any breakpoints set for this program are not valid.

C:\\mpiuadev\\mpiua\\dev\\cobol\\debug\\mfippvch.idy

run thru button                       Stop Animating Button

A
  • Anonymous
  • November 20, 2013

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

I did finally get program B to go into debug by adding the initcall (CBL_DEBUGBREAK) in the project directives, but it breaks in program B, not program A where I have the call "cbl_debugbreak" stmt as a first stmt  (B is called by A later in the processing).  Not sure why this is or how to fix it.

D

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

I use VB .Net and Cobol until Visual Studio 2003 - 2013...

You must call the Cobol Filie via "Marshal"...

Here is th Call:

   Declare Function DOKABLIEFERANTCALL Lib "COBIEFERANT.dll" (ByRef VBSATZDATEN As VBSATZ ) As Integer

...

...

       CblStatus = DOKABLIEFERANTCALL(VBSATZ001)

In COBOL you have an ENTRY that you can call...

The Debuger will starting after the "CBL_DEBUGBREAK".

But you must have install Net Express on your Machine!

Not only the Runtime...

D

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

I use VB .Net and Cobol until Visual Studio 2003 - 2013...

You must call the Cobol Filie via "Marshal"...

Here is th Call:

   Declare Function DOKABLIEFERANTCALL Lib "COBIEFERANT.dll" (ByRef VBSATZDATEN As VBSATZ ) As Integer

...

...

       CblStatus = DOKABLIEFERANTCALL(VBSATZ001)

In COBOL you have an ENTRY that you can call...

The Debuger will starting after the "CBL_DEBUGBREAK".

But you must have install Net Express on your Machine!

Not only the Runtime...

A
  • Anonymous
  • November 21, 2013

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

Danke fĆ¼r diese Idee.

D

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

Funktioniert es?

A
  • Anonymous
  • December 19, 2013

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

Nein, leider nicht. Ich verstehe COBOL sehr gut, aber nicht .NET.

D

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak
Should the Cobol and VB code be in the same folder?
Chris Glazier
Forum|alt.badge.img+2

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak
It is not a requirement but probably a good idea. If .DLLs are being called then the system PATH will be searched in order to find the .DLL if it is not in the current directory so the location should at least be included in the PATH. When debugging the IDY and source files must also be available.
D

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak
I am trying to debug the MF cobol code in net express. I have placed all the DLL's in a folder and (.obj, . cbl, .idy) files in another folder. I have provided the compiler directives to include debugbreak and rebuild the project. when i provide the path to .dll files and invoke the cobol from VB, everything goes fine but there is no debugbreak inititated. It completely runs. But when I specify the path as the (.obj, . cbl, .idy) files, it throws error. Please let me know is there any other setting I need to do. Is there any start/stop debug visual studio code to be provided with any path.
PS: each cobol code is in a seperate project
D

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak
I am trying to debug the MF cobol code in net express. I have placed all the DLL's in a folder and (.obj, . cbl, .idy) files in another folder. I have provided the compiler directives to include debugbreak and rebuild the project. when i provide the path to .dll files and invoke the cobol from VB, everything goes fine but there is no debugbreak inititated. It completely runs. But when I specify the path as the (.obj, . cbl, .idy) files, it throws error. Please let me know is there any other setting I need to do. Is there any start/stop debug visual studio code to be provided with any path.
PS: each cobol code is in a seperate project
D

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

I tried a simple display program with both "CBL_DEBUGBREAK" inside the program and also in compiler derivative and still it runs and displays the output. But i fixed it by including a .exe file.

Chris Glazier
Forum|alt.badge.img+2

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak
Are these .DLLs compiled with the ANIM directive?

You can try setting the following environment variables before starting your application:
COBIDY - set to the directory containing the .idy file for the component.
COBCPY - set to the directory containing the source files for the component.
D

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak
[deleted]
D

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

Hi Chris,

Now the CBL_DEBUGBREAK is working in windows XP and I get the message that "encountered CBL_DEBUGBREAK" and I have options to animate or runthru.I have 3 cobol programs which have a call to one another.
I have given CBL_DEBUGBREAK to one program only. Now when i say i want to animate, it says .idy files not found. When I browse and give the location of .idy file, it says source code not found. Could you please let me know where these path's are originally mentioned.

Since I have many projects, I have put all the .idy files and .dll files in a location. Should the source code also be in the same location as .idy files?

Also the CBL_DEBUGBREAK did not work in windows 7. Is there any other settings to be done?

D

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak

Hi Chris,

Now the CBL_DEBUGBREAK is working in windows XP and I get the message that "encountered CBL_DEBUGBREAK" and I have options to animate or runthru.I have 3 cobol programs which have a call to one another.
I have given CBL_DEBUGBREAK to one program only. Now when i say i want to animate, it says .idy files not found. When I browse and give the location of .idy file, it says source code not found. Could you please let me know where these path's are originally mentioned.

Since I have many projects, I have put all the .idy files and .dll files in a location. Should the source code also be in the same location as .idy files?

Also the CBL_DEBUGBREAK did not work in windows 7. Is there any other settings to be done?

Chris Glazier
Forum|alt.badge.img+2

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak
What version of Net Express are you using? Only Net Express 5.1 with wrappack 4 or higher installed is supported under Windows 7.

I had posted previously that you can set two environment variables that will help the run-time system locate the required files.

COBIDY - set to the directory containing the .idy file for the component.
COBCPY - set to the directory containing the source files for the component.

If you have a Net Express project setup this would be much easier. You could simply open the project and then point your Start Debugging at field to point to your VB application and then run the VB app into it reached a breakpoint that you have set in your COBOL code.

BTW, you cannot debug your VB code at the same time as you are debugging your COBOL code as only one system debugger can be active at a time under Windows. If you wish to debug COBOL then the VB should be run at full speed.

If you continue to have problems with this then I would suggest that you open up a support incident with Customer Care so we can investigate.

Thanks.
D

Can I  use cbl_debugbreak in NetExpress COBOl which is called by VB.net code?  I need to be able to debug from the VB into the cobol and then back to the VB.  I have put the call cbl_debugbreak in the cobol program and recompiled it, but when I debug in VB.net, it does not bring the COBOL up.


#cbl_debugbreak
Thank you Chris. Previously I did not set the COBCPY. Now it is working.

Recent badge winners

Explore all badges
Terms & ConditionsAccessibility statement