HP3000-L Archives

September 2000, 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:
Chris Goodey <[log in to unmask]>
Reply To:
Chris Goodey <[log in to unmask]>
Date:
Wed, 20 Sep 2000 12:01:19 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
The usual problem is that a data base has been RELEASED,
but when rebuilt by a capacity change, loses the setting.

If you are using normal group and account security, it should
not be a problem, but if releasing the entire data base,
you will need to redo this after each capacity change.


-----Original Message-----
From: Damian Sobieralski [mailto:[log in to unmask]]
Sent: Wednesday, September 20, 2000 9:50 AM
To: [log in to unmask]
Subject: [HP3000-L] TurboImage and access error


  We had a dataset capacity changed this week (not by me) and now I notice
(perhaps coincidentally, but this is the only thing that I see that could
have changed this as this worked all the time before the start of this week)
that when we try to use query to access the database from a user whose
account and group is NOT where the database is located at, I get an error:

:QUERY

> BASE=MYDB.DATABASES.GENERAL
> PASSWORD = >>
> MODE = >>
TurboIMAGE Error Message:
MPE FILE ERROR -248 RETURNED BY FOPEN ON DBG

  Yet if I access the database from someone who lives in account GENERAL all
is fine.  *sigh*  I know very little about T/I but is there a way to
restrict access based on account?  I can access(print) flat files from
within databases.general so I wouldn't think it would be an account/group
MPE file system specific issue.

 Does DBUTIL allow you (or any util) to limit access to the database based
on such criteria. If so, how?

ATOM RSS1 RSS2