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:
Tony Summers <[log in to unmask]>
Reply To:
Tony Summers <[log in to unmask]>
Date:
Fri, 2 Sep 2005 15:23:59 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (132 lines)
Options (1) and (2).  

ALLOWME.PUB.ORBIT or GOD.PUB.VESOFT (programs from 3rd party vendors)
might give the job the necessary capabilities to execute the LOG
command. 

Option (3) 

         [log in to unmask]@      }
   ALLOW {user.@   };COMMANDS=command[,command,...]
         [log in to unmask]   }
         {user.acct }

Change sysstart.pub.sys to ALLOW the execution of the "LOG" command to a
named MPE USER.ACCOUNT that only has BA mode access (i.e. cannot logon
as a session) and you change the backup job to run under that
USER.ACCOUNT.    

P.s. See NEWUSER command for option (3) you want BA access, but not IA
access. 

capabilitylist      The list of capabilities, separated by commas,
                    permitted to this user. Each capability is
                    denoted by a two letter mnemonic, as follows
 
                    System Manager        =       SM
<clip>
                    Programmatic Sessions =       PS
                    User Logging          =       LG
                    Process Handling      =       PH
                    Extra Data Segments   =       DS
                    Multiple RINs         =       MR
                    Privileged Mode       =       PM
                    Interactive Access    =       IA
                    Batch Access          =       BA


-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of James B. Byrne
Sent: 02 September 2005 14:14
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 *

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________



The contents of this email are confidential to the intended recipient
and may not be disclosed. Although it is believed that this email and
any attachments are virus free, it is the responsibility of the recipient to confirm this.

Smith & Williamson Corporate Finance Limited - A member of the London Stock Exchange.  
A member of M&A International Inc. http://www.mergers.net  Registered in England No. 4533970. Authorised and regulated by the Financial Services Authority 
Smith & Williamson Investment Management Limited, Registered No. 976145. Authorised and regulated by the Financial Services Authority.
Smith & Williamson Pension Consultancy Limited - Independent Intermediary. Registered No. 3133226. Authorised and regulated by the Financial Services Authority.
Smith & Williamson Fund Administration Limited, Registered No. 1934644. Authorised and regulated by the Financial Services Authority.
Smith & Williamson Limited - A member of Nexia International.  Registered in England No. 4534022. Regulated by the Institute of Chartered Accountants in England & Wales for a range of investment business activities.
NCL Investments Limited, Registered No. 1913794.
Member of the London Stock Exchange authorised and regulated by the Financial Services Authority.

Registered Office: 25 Moorgate, London EC2R 6AY
Telephone: 020 7131 4000 http://www.smith.williamson.co.uk

Nexia Audit Limited - A member of Nexia International. Registered in
England No. 4469576. Registered to carry on audit work and regulated by the Institute of Chartered Accountants in England & Wales for a range of investment business activities.

Registered Office: 25 Moorgate, London EC2R 6AY
Telephone: 020 7131 4000 http://www.nexiaaudit.co.uk


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

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

ATOM RSS1 RSS2