cpp migration MicroFocus Workbench 2 NetExpress 
Author Message
 cpp migration MicroFocus Workbench 2 NetExpress

Hello i have i great problem with netexpress from merant.
the merant german support told me my problem is out of range from the  

This is my environment:
Microsoft windows nt 4.0 service pack 3.0
Merant    netexpress 3.0 service pack 1.0
Microsoft Visual C++ 5.x
IBM       universal database 5.2

In the past we use cobol workbench 4.0.26 with no problems.

But now i get this error-code:
173 program not found "checkfil"

a little bit closer:
A cpp executable is started, maybe in the netexpress dosbox or direct by
clicking the icon (it dosen't matter).

This cpp executable starts some more dlls (system dlls and some own cpp  

I can follow the loadlist by using the c++ de{*filter*} and catch the process.

A cobol dll (not static) will be loaded, the runtime cblrtss.dll will be  

A few more cpp dlls will be loaded.
The last cpp dll loads a cobol dll (not static).
This cobol dll should load one more cobol dll (not static).
This step fails with the error "173 ... CHECKFIL"

This are the steps i done with no solution:
Start the application from the netexpress dos prompt.
Check the path-environment is less than 256 characters.
Include the netexpress\base\bin and application-path in the path
Check cobdir and include also the application-path.
Only using must-have directives like CASE and MAKESYN.
Naming the second dll with fullpath does also not solute the problem.

So i think the problem must be between the calling and called program.

I think it's an environment-problem. But what ist the problem?
We build all our cobolsources (more then 750 dlls) as a massmake from the  

I didn't understand following results:
If i link externl.obj to my cobol-dlls the error 173 changes to 119, which  
means that checkfil is not unique.

So what? CHECKFIL not found or CHECKFIL not unique?

If i use a cobol executable instead of the cpp appication all works fine.

I think it must be my environment, but where is the error or what can i do?

Some more informations:
We do not prefer to build one big dll.
We can't use the CANCEL-Command after calling a dynamic cobol-subprogram,  
because our programs should also run in a mainframe environment.

What can i do?
Our problem is the Y2K-problem. The cobol workbench 4.0.26 is imho not Y2K  

At Last:
I'm sorry about my terrible english - i hope you can understand this text.
This posting is my last hope


Fri, 14 Jun 2002 03:00:00 GMT  
 [ 1 post ] 

 Relevant Pages 

1. migration workbench 2 netexpress

2. MF COBOL Newsgroup?? Especially for NetExpress and Workbench

3. PL/I -- The Microfocus MVS Workbench

4. MicroFocus Workbench/CICS option

5. Wang COBOL on MicroFocus Workbench

6. MicroFocus Cobol Workbench v3.2x

7. microfocus workbench

8. MicroFocus Cobol Workbench

9. MicroFocus Cobol Workbench 4.0?

10. Microfocus Workbench 3.2.43


12. Looking for latest version update for Microfocus workbench v3.2.43


Powered by phpBB® Forum Software