Skip to main content

I have any programs that run correctly on netexpress 5.1!

Now i am testing the new version visual cobol 8.0 and have now programs that want works.

Own lbr's or dll's are not found by debugging or running see a little example here:

Where must be placed the own lbr's or dll'?
Wich runtime modules are needed?

There are any modules that i was not able to find on vc8 as tools.lbr or utils.lbr, also cblvios.dll, cblrtss.dll and other

I missed also many possibilities on debugging on vc8 comparing with netx5.1!!!!

How can help? What are your experience?

Thanks for your help

Here a extract from a program:

working-storage section.
* Pointer
01 cgtoolsptr procedure-pointer.
01 cob32apiptr procedure-pointer.
*
PROCEDURE DIVISION.
main.
perform load-module
*> wapiutil is in ossyslib.lbr and not found     !!!!!!!!!!!!!!!!!
call 'wapiutil' using null *> vorladen
/
load-module section.
*> own lbr-modul not found in vc80 !!!!!!!!
call 'ossyslib.lbr' on exception
continue
end-call
*> own dll-modul not found in vc80
set cgtoolsptr to entry 'cgtools.dll'
if cgtoolsptr = NULL
display 'Cannot load cgtools.dll!'
exit program
end-if
*> Windows-Modul are found
set cob32apiptr to entry 'cob32api.dll'.
if cob32apiptr = NULL
display 'Cannot load cob32api.dll!'
exit program
end-if
.

I have any programs that run correctly on netexpress 5.1!

Now i am testing the new version visual cobol 8.0 and have now programs that want works.

Own lbr's or dll's are not found by debugging or running see a little example here:

Where must be placed the own lbr's or dll'?
Wich runtime modules are needed?

There are any modules that i was not able to find on vc8 as tools.lbr or utils.lbr, also cblvios.dll, cblrtss.dll and other

I missed also many possibilities on debugging on vc8 comparing with netx5.1!!!!

How can help? What are your experience?

Thanks for your help

Here a extract from a program:

working-storage section.
* Pointer
01 cgtoolsptr procedure-pointer.
01 cob32apiptr procedure-pointer.
*
PROCEDURE DIVISION.
main.
perform load-module
*> wapiutil is in ossyslib.lbr and not found     !!!!!!!!!!!!!!!!!
call 'wapiutil' using null *> vorladen
/
load-module section.
*> own lbr-modul not found in vc80 !!!!!!!!
call 'ossyslib.lbr' on exception
continue
end-call
*> own dll-modul not found in vc80
set cgtoolsptr to entry 'cgtools.dll'
if cgtoolsptr = NULL
display 'Cannot load cgtools.dll!'
exit program
end-if
*> Windows-Modul are found
set cob32apiptr to entry 'cob32api.dll'.
if cob32apiptr = NULL
display 'Cannot load cob32api.dll!'
exit program
end-if
.

When working in Visual Studio each project has its own output folder (bin\\x86\\debug for example), which is specified on the Properties-->COBOL tab. In order to load a .DLL or a .LBR they either need to be in the current directory of the calling program or their localations specified in the COBPATH environment variable or for .DLL's they can also be specified within the PATH.

The easiest way to remedy this is to chance the output folders of your subprogram projects to be the same as the output folder of the main program or have a common folder that they are all output to. You could also add the COBPATH environment variable to the environment under the Properties Application tab and then it will be searched at run-time.

As far as the missing files go, NX and VC are different products. No cblrtss.dll exists because the single-threaded run-time is no longer supported. We had also removed all of the .LBR's from the product and have either replaced them with .DLL's or have simply removed them because they are not used anymore.

Product differences and new to Visual Studio documentation can be found in the documentation here

Terms & ConditionsAccessibility statement