× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Kenneth

At 01:26 PM 4/10/1998 -0700, you wrote:
>Midrangers....
>
>What, if any, difference is there between the following two methods of
>giving a user access to a command screen with QSECOFR authority:

A followup--

In my previous post, I answered as I did, because we have written it this
way. Steve G. and Simon C. are correct, if you use the API as you've
specified.

We use the API, but in combination with adopted authority. We change the
user profile's auditing (so that everything is logged in the audit
journal), use the API to set the profile in the job, and then give the user
(usually a programmer, with special needs--we do this through a carefully
controlled protocol) a command line that adopts QSECOFR's authority. There
are a number of controls to keep this fairly secure.

In this circumstance, the QSYGETPH API is run over the user's profile, not
QSECOFR.

I think our code is based on a NEWS/400 article.

Anyone interested in more (including code), let me know private email.

Cheers

Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN 55401
(612) 371-1111 x480


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.