Skip to main content

Calling Cobol from .NET

  • April 18, 2018
  • 3 replies
  • 0 views
D

Hi all.

We use acucobol.CVM class from wrunnet.dll to call COBOL program from .NET module.

 

Unfortunately we get FALSE from the Initialize() method and we do not undestand why. 

Is there a way to get a more detailed error code/message? Some kind of log or something like that ?

 

Thank you

--

Davide Giudici


#AcuCobol
#Interoperating
#.net

    3 replies

    D

    Hi all.

    We use acucobol.CVM class from wrunnet.dll to call COBOL program from .NET module.

     

    Unfortunately we get FALSE from the Initialize() method and we do not undestand why. 

    Is there a way to get a more detailed error code/message? Some kind of log or something like that ?

     

    Thank you

    --

    Davide Giudici


    #AcuCobol
    #Interoperating
    #.net
    A first step would be to call Initialize() with a command line that includes a trace file and a config file that turns on tracing:

    Initialize("-c myconfig -le myerr.txt myprog")

    And then make sure that myconfig has at least:

    A-TRACE 3
    FILE-TRACE 3
    FILE-TRACE-FLUSH TRUE

    Hopefully the myerr.txt file will have some more information about what might be failing.
    D

    Hi all.

    We use acucobol.CVM class from wrunnet.dll to call COBOL program from .NET module.

     

    Unfortunately we get FALSE from the Initialize() method and we do not undestand why. 

    Is there a way to get a more detailed error code/message? Some kind of log or something like that ?

     

    Thank you

    --

    Davide Giudici


    #AcuCobol
    #Interoperating
    #.net
    Hi rzack.

    I tried your suggestion but with no result (I mean, no trace file created).
    I guess that the runtime fail before starting.

    --
    Davide Giudici
    D

    Hi all.

    We use acucobol.CVM class from wrunnet.dll to call COBOL program from .NET module.

     

    Unfortunately we get FALSE from the Initialize() method and we do not undestand why. 

    Is there a way to get a more detailed error code/message? Some kind of log or something like that ?

     

    Thank you

    --

    Davide Giudici


    #AcuCobol
    #Interoperating
    #.net

    Hi all.

    I finally get the solution.

    My bad ! !

    We was trining to call the wrun32.dll from a 64bit .NET application.

    Simply changing the configuration from "Any CPU" to "x86" we solve our problem.

     

    Thank you all.

    --

    Davide Giudici

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement