stnadalone .EXE 1

[YossiN]

hi
I wrote a small app that DISPLAY "HELLO WORLD" using Fujitsu COBOL V3 (free student version)

it works ok on my comuputer but when I send the EXE to another computer it doesn't work but start asking for DLLs....

If I deliver all the DLLs in the FSC directory it works ok, but for sure this is not the solution.

How do I compile/link the .COB file so I'll have a stndalone .EXE I can distribute?

thanks

 

[Tromba]

Hi

You need to copy a series of .dll files into pc where you will run the application.
See your documentation for details about the .dll that must be delivered with your executable.

Gianni

 

[PROFESSORSPARKIE]

There is an @OPTION called DLOAD/NODLOAD that defines if the output program is to dynamically load the required DLLs(dynamic link modules like printer open and run rountines) or to statically link the whole package together into one loadable program. I have never taken the time to read all of the documentation to figure it out, but you can give it a try. There are a few steps to it. If you dig it out, document it and respond with your own answer.

Concept:

DLOAD: is the default and allows many programs to share one DLL which saves disk space. Each load of a program causes the loader to get the latest & only copy of the routine.

NODLOAD put a complete loadable package to gether as a single .exe file. This program can be moved from one system to another by moving the single .exe file.
If any of the DLLs are updated you won't use the update unless you re-link the program. I you don't use DLOAD you have to copy the required DLLs to the other systems.

A simple read-disk-print with a few program functions like DATE, SIN, etc can need 10-20 DLLs.
Example: An INDEX file uses a different DLL than sequential or a direct file.

 

[allien01]

Sorry SParkie, that does not work. I believe that this option is only for sub-programs, not system DLL's

I still would like to know how to do this as I am busy evaluating this product and this could be stumbling block for me.

Thanks

 

[etom]

If you are busy evaluating V3 of Fujitsu Cobol as a free compiler then go ahead however, V3 is not anything like the current version of Fujitsu Cobol. The current version (Cobol for Windows) is version 7. It also requires a runtime however, they do supply an install wrapper to install you written programs and the runtime all at once using the standard Windows installer.

You need to understand that v3 (freebe) has had some features turned off and hundreds of new features exists in the most current version (around $1500). The newest version is feature rich and the user interface is far better than the version 3.

etom

 

[allien01]

Thanks for that. I also have a problem with the COPY statement e.g. COPY "S:\COBOL\LISTMERG\COBOL\JOBPARM.CPY".
These are common copybooks we use that reside on a repository on our server. I get the following message:
"1011-U LIBRARY CANNOT BE OPENED." Could this also be because the "freebie" version does not handle this copy statement properly?

Thanks

 

[etom]

Not sure about the Copy statement in v3. There are a lot of people using version 3 on this site. Maybe they can help. You might want to post that question specifically.

 

[PROFESSORSPARKIE]

In the V3 COBOL package in FSC\PCOBOL32 there are two link programs LINK & WINLINK which are used to do the linking of the programs, the LINK is a very large program and if you type "LINK /? >LPT1:" on the command line you will get a listing of all of the link options. The WINLINK has no options, it is much smaller and seems to used to call the LINK program.

By reading how to compile & link from the command line maybe you can control the linking process better. Again I have never followed it to the end but surely there is an option but maybe not.

The COBOLL85 Users's Guide for 3.0 on page 63 start discussing how to control the compile & linking of your programs from the command line with out the developer menu system. As I said I went down this path a little ways but never finished the trip. I hope someone finishes it to prove if it can/cannot be done.