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:
Michael L Gueterman <[log in to unmask]>
Reply To:
Michael L Gueterman <[log in to unmask]>
Date:
Mon, 14 Oct 1996 08:34:10 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (56 lines)
Joe,

A couple other things to keep in mind as well:
1.  If the section your installing has a CLASS as it's owner instead of a true user, the user doing
      the INSTALL command (currently) must have DBA authority.
2.  You'll need to GRANT whatever RUN authorities are required (unless your replacing modules
      already INSTALLed, and you preserved those grants).
3.  When you've installed all of the modules, issue a VALIDATE ALL MODULES command.  This
      can save some time when the modules are first hit.

Regards,
Michael L Gueterman
Easy Does It Technologies
voice: (509) 946-6179
fax:    (509) 946-1170
email: [log in to unmask] (temporarily)
http://www.editcorp.com (coming soon!)
--

----------
From:  [log in to unmask][SMTP:[log in to unmask]]
Sent:  Monday, October 14, 1996 7:46 AM
To:  [log in to unmask]
Subject:  "Transportable" Host Image/SQL Programs

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