HP3000-L Archives

October 1996, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Mon, 14 Oct 1996 15:46:19 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
When the preprocessor stores a module in the system catalog of a
DBEnvironment at preprocessing time, it places a copy of the module in an
installable module file.  By default the installable module file is named
SQLMOD. The module in this file can be installed into a DBEnvironment
different from the DBEnvironment accessed at preprocessing time by using
the INSTALL command in ISQL.

@@@
> Hey all,
>
> I have written a host module which uses Image/SQL and have it
> working well in the development environment.
>
> My problem is that it needs to be transportable - be able to be
> used from different accounts (customer accounts on our machine)
> as well as send as part of the package to other customers with
> their own machines.
>
> Since the preprocessor inserts a module in the DBE with the
> user/account of the user preprocessing, it seems that I need
> to have compilers/preprocessors on our production machines.
> The problem is that none of these machines have compilers
> as they have no need to have them.
>
> How can I preprocess and compile this module, which will
> reside in an XL and distributed, without having to re-preproces
> and recompile on the target machine (or account)?
>
> Thanks in advance...
> Joe Geiser

ATOM RSS1 RSS2