HP3000-L Archives

February 1998, Week 1

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:
Gavin Scott <[log in to unmask]>
Reply To:
Gavin Scott <[log in to unmask]>
Date:
Thu, 5 Feb 1998 16:25:04 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
Bob writes:
> I would seem that as soon as an HFS name appears, in either ISQL or
> pre-processed code, it is assumed to be a remote database and
> starts looking at the Allbase/Net info.

I suspect that Allbase (specifically the "router" which decides whether
a DBE name is local or remote) doesn't know from Posix path names.  I
suspect that you can continue to specify a fully qualified MPE name
for the database, even though you are compiling "as a Posix application".
This assumes that the DBE is in an MPE GROUP (which may still be an
Allbase requirement).

By the time you get to Allbase, it won't have a clue that it is being
invoked from a "Posix" program and probably will use HPFOPEN to open
the DBE file, so the name you give to embedded SQL is going to get
interpreted as MPE naming syntax, not HFS or even MPE-escaped syntax.

If you fully qualify the DBE name as an MPE style FILE.GROUP.ACCOUNT,
then it will probably work regardless of the current working directory
(CWD) of the process.

This is a guess however.

G.

ATOM RSS1 RSS2