You keep using the "cobol" command.  As Larry and I suggested, you need to use the "cob" command on UNIX.  This command can do a compile or link (or both).  Normally, there is no "cobol" command on UNIX for Visual COBOL, but it looks like you have one that is a compile-only command.

We understand that you don't desire a command-line solution.  However, if the command-line solution works for you, it should be a strong hint on how to accomplish the solution in Eclipse.  It would just be a matter of getting Eclipse to pass the "-I COBWIN2" to the link step of the project.  Neither Larry nor I have an Eclipse environment to explore how to do this in detail.  Larry has offered to look into this on Monday if you are not able to work it out on your own with your Eclipse environment.

Dear Sir,

We are Testing in Visual Cobol for Eclipse in ENDOWS 7. Here when you use  the Visual Cobol Command Pront  the command is COBOL not COB.

TKS

Dear Sir,

SORRY....

We are Testing in Visual Cobol for Eclipse in WINDOWS 7. Here when you use  the Visual Cobol Command Pront  the command is COBOL not COB.

On Windows, the command to link is cbllink:

    cbllink -otemplate01.exe template01.obj cobwin2.obj

This will link in cobwin2.obj, which contains the required entry points for popup windows.  Note that no space is allowed between the -o option and its argument, the output file name.  After the -o option and its argument, list the object files in your project plus cobwin2.obj.