Discussion:
HIPRI misuse
(too old to reply)
Tony Summers
2006-05-31 10:51:48 UTC
Permalink
Just back from holiday so apologies for the delay.

I have a vague impression that MPEX can intercept all jobs and constrain
them in the manner you require. But if your "users" have SM or OP
capability (which they must have to override HIPRI being downgraded to
pri=13) then they would be able to amend the Security/3000 config files
anyway.

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:HP3000-***@RAVEN.UTC.EDU] On
Behalf Of Edward Berner
Sent: 23 May 2006 23:55
To: HP3000-***@RAVEN.UTC.EDU
Subject: Re: [HP3000-L] HIPRI misuse
Anyone have a creative way to disable the HIPRI option to everyone
except
those with SM or OP capability? I'm having users streaming jobs with
HIPRI because they don't want to wait their turn.
You might be able to have a logon UDC check for HPJOBTYPE = "J" and
HPINPRI = 15. Then you can do some other logic to see if it is a
legitimate use of HIPRI and if not do an EOJ or ABORTJOB. (Or open the
company's accounting database and perform a suitable transfer of
funds... "Starting next week all HIPRI jobs will be charged $X per CPU
minute." :)

The logon UDC should even be able to catch users with the OP capability,

though I suspect there are ways around it if they're willing to try hard

enough.

Edward

* 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
______________________________________________________________________

LexisNexis Taxation Awards 2006

Winners of:
The Lifetime Achievement award
Richard Mannion of Solomon Hare LLP, a member of the Smith & Williamson group

Shortlisted for:
Best High Net Worth Tax Team
Best Tax Team in a Large Firm (Professional Practices Tax Team)

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 Smith & Williamson Audit Limited - A member of Nexia International. Registered in England No. 4469576.
Nexia Smith & Williamson Audit Limited is a company registered to carry out audit work and is regulated for a range of investment activities by the Institute of Chartered Accountants in England and Wales. Smith & Williamson Limited is a separate company that provides professional resources and certain services to Nexia Smith & Williamson Audit Limited under the terms of a formal agreement on an arm+IBk-s length basis.

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

All telephone calls are recorded for business purposes.


______________________________________________________________________
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 *
Greg Stigers
2006-05-31 13:38:06 UTC
Permalink
Job queues could work. I haven't thought this out all the way, so others
should probably advise. But if your impatient users run their jobs in a
queue that you maintain and tune, you can limit how much that queue can
grab, while also limiting the number of jobs that can run in that queue.

Greg Stigers

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