Microfocus Object Cobol v 4.0.32 Shared Runtime Setting

I want  to know what files of runtime are necessary to Run a Cobol program
compiled with the Microfocus Object Cobol v 4.0.32.
Best regards,
Massimo.

On Fri, 4 Feb 2005 16:06:12 UTC, "Massimo Morgia"
<blue_max_53@hotmail.com> wrote:

> I want  to know what files of runtime are necessary to Run a Cobol program
> compiled with the Microfocus Object Cobol v 4.0.32.
> Best regards,
> Massimo.
>
>

It depends on how the program is distributed and what features it is
using.

The minimum is coblib.dll, but if the program is dstributed as 'GNT'
modules (possibly in LBR files) you will need also cobenv.dll and
utils.lbr and utility.lbr and possibly  others.

There should be a list of runtime files in the documentation of the
compiler package.

--
Lorne Sunley

> There should be a list of runtime files in the documentation of the
> compiler package.

The Object COBOL User's Guide details which files you would need to ship
along with your application.

SimonT.

Simon,
Is that also where the documentation is on what run-time LICENSING
requirements are, i.e. what needs to be paid for - for each machine upon whi
ch
certain run-time support is installed?  (The original post seemed tome as if
 the
poster may not be aware of this.)

--
Bill Klein
wmklein <at> ix.netcom.com
"Simon Tobias" <Simon.Tobias@microfocus.com> wrote in message
news:cu08pp$d40$1@hyperion.microfocus.com...
> 
>
> The Object COBOL User's Guide details which files you would need to ship
> along with your application.
>
> SimonT.
>
>

Massimo Morgia wrote:
> I want  to know what files of runtime are necessary to Run a Cobol
program
> compiled with the Microfocus Object Cobol v 4.0.32.
> Best regards,
> Massimo.

You should have an "OSX" (Operating System Extensions). This provides a
complete set of the COBOL Run-time files needed to support COBOL
applications created with Workbench 4.0.32.

If you create your executable with cbllink and use the -T switch you
shouldn't need any additional files, but you are responsible for
specifying the optional object files your application needs.

If you don't use the -T switch there are three DLL files you will need:
....MFRTS32.DLL
....MFSCREEN.DLL
....MFPRNT32.DLL

Hi Bill.

Looking at the Object COBOL 4.0 User's Guide again, under the Shipping
Applications section, there's a subheading, Licensing, which states :

---- 8< cut here ----
All the support modules described in this chapter are part of Micro Focus
OSX (Operating System Extensions). OSX consists of the following parts:

a.. COBOL run-time

b.. OSX server components

c.. OSX client components

d.. OSX integration components
On DOS, Windows, and OS/2, you must pay a license fee for each copy of OSX
support modules you ship to end-users, except for the COBOL run-time
components.

Look at the on-disk document osxpack.doc to find out whether your
application uses any modules which require further licensing. It lists all
the modules in each of the four categories shown above. If your application
only uses COBOL run-time modules, you can ship it without paying any extra
license fees; otherwise you must pay a license fee for each copy of your
application shipped to end-users.

---- 8< end of snippet ----

There's also an earlier section, OSX, which details the contents of the 3
"OSX..." categories listed above.

Just as a reminder to anyone following this thread, that the documentation
references are from the Object COBOL (and Workbench) 4.0 products, and not
Net Express.

Hope this helps.

SimonT.

> Just as a reminder to anyone following this thread, that the
documentation
> references are from the Object COBOL (and Workbench) 4.0 products,
and not
> Net Express.

You are quite correct.  It is possible to ship fully functional
applications without run-time fees as long as you do not use OSX
components.

This also appears to be true for NetExpress up to 2.something.  The
'upgrade' to NE 3.x  allegedly removed the wording that allowed free
run-time distribution.

You have to check your actual licences and your actual manual set as
there was apparently some variation in these for different markets (but
that was just a MF salesman saying that and she was clueless about most
other things).

The main thing is that you cannot ship .int and .gnt files as these
require a run-time system that is part of the OSX.  You have to compile
to .EXEs  and .DLLs but these can be set to intermediate byte code
using OPT(0).  ie they can be .int inside a .EXE or .DLL.

You also should statically link the run-time plus ADIS, ADISKEY and
EXTFH to the main .EXE or link these as .DLLs as explained in the User
Guide.

There are several callable routines which are considered part of the
OSX, such as byte stream.  These should be detailed in the user guide
or somesuch.