HP3000-L Archives

April 2009, 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:
Tue, 21 Apr 2009 09:05:45 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (102 lines)
Well, one positive aspect, from the DB Admin point of view, is using the 
maintenance word adds to the security of the database, by discouraging 
non-secure workarounds, like removing security from areas around the 
database.

 I notice that Adager supports this concept, and prompts a non-dbcreator 
for the maintenance word, if it is set.

How to convince the DB Admin? Make it their idea!

Cheers,
Mike.



Walter J. Murray wrote:
> Mike,
>
> Nice and simple, but it would require convincing the Database
> Administration unit to (1) apply maintenance words on a number of
> databases on all of the servers, and (2) remove or publish the password
> on DBUTIL.  I might still go this way, though.
>
> Thanks for the suggestion.
>
> Walter  
>
>
> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
> Behalf Of Michael
> Sent: Tuesday, April 14, 2009 7:10 AM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] How to see what's locked in a TurboIMAGE
> database
>
> Simple; Set a maintenance word on the database(s)
>
> DButil will allow database maintenance from a non-creator user/account 
> if the maintenance word is known.
>
> "I always start things very complicated".
> Mike.
>
>
>
> Walter J. Murray wrote:
>   
>> Greetings,
>>
>> I am looking for a way to permit ordinary users (programmers and
>>     
> support
>   
>> staff) to see who is using a TurboIMAGE database, and what locks are
>>     
> in
>   
>> effect and are pending--the information you would see with DBUTIL
>>     
> using
>   
>> SHOW ... USERS and SHOW ... LOCKS or SHOW ... ALL.
>>
>> I have to work within these constraints:  (1) Can't let them log on
>>     
> with
>   
>> SM capability.  (2) Can't let them log on as the database creator.
>>     
> (3)
>   
>> Can't reveal the password on the MPEX GOD program.  (4) Can't reveal
>>     
> the
>   
>> password on DBUTIL.
>>
>> Any suggestions?  Any utility to do this?
>>
>> My best idea so far is to set up a command file that would use the
>>     
> MPEX
>   
>> %WITHCAPS command to grant SM capability temporarily, then run DBUTIL.
>>
>> Walter  
>>
>> Walter J. Murray
>>
>> * To join/leave the list, search archives, change list settings, *
>> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>>
>>   
>>     
>
>
>   

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2