HP3000-L Archives

September 2005, 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:
"Skeet, Nigel" <[log in to unmask]>
Reply To:
Skeet, Nigel
Date:
Mon, 5 Sep 2005 08:53:30 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (67 lines)
Hi James,

Do you have VESOFT SEC3000 ? If so you can add the $ALLOW command to the
SECURCON file and that will allow the log command for specific accounts
/ users.

Regards,

Nige... 

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of James B. Byrne
Sent: Friday, September 02, 2005 3:14 PM
To: [log in to unmask]
Subject: [HP3000-L] STOPLOG/STARTLOG commands in job file

As part of our backup recovery plan revamping I have added
STOPLOG/STARTLOG commands to our backup job stream so that if the backup
fails then access to the databases is prevented until the underlying
issue is resolved.  My problem is this:

:  LOG HALDBLOG,STOP
Executing this command by other than the master operator  requires
permission using the ALLOW command. (CIERR 3000)
:  PAUSE 5
:ENDIF

While HELP ALLOW OPERATION has this to say:

The operator may ALLOW console capabilities only to users who are
currently logged on to the system, unless the @.@ option of the ALLOW
command is used.  In this case, all users are affected, whether or not
they are logged on.
Additional capabilities granted to a user last only for the duration of
their current session; once the user logs off, any special capabilities
previously assigned are no longer applicable.

The user command SHOWALLOW indicates which operator commands have been
allowed globally and to which specific user.  Refer to SHOWALLOW.

This command can be issued from a session, job, program, or in BREAK.
Pressing [Break] has no effect on this command.  It is executable only
from the console unless it is distributed to users with the ALLOW
command.

Now, I am none too keen on issuing an ALLOW STOPLOG @[log in to unmask] Issuing an
ALLOW command from the console is not practical in this application.
What other options are there?

Regards,
Jim

--
     *** e-mail is not a secure channel ***
mailto:byrnejb.<token>@harte-lyne.ca
James B. Byrne                Harte & Lyne Limited
vox: +1 905 561 1241          9 Brockley Drive
fax: +1 905 561 0757          Hamilton, Ontario
<token> = hal                 Canada L8E 3C3

* 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