× 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.



Try the Qp0lGetAttr API with attribute array constant 11 -
QP0L_ATTR_AUTH: The public and private authorities associated with the
object.  Since the IFS does not honor adopted authority you will still
have to process under a profile with at least read rights to the object.
Switching to an *ALLOBJ authority profile within your job should do the
trick.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H H Lampert
Sent: Tuesday, December 19, 2006 11:05 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Owning USRPRF of an IFS object?


I keep running into brick walls on this!

Is there a simple way, WITHOUT having to be running under 
a privileged account, for an ILE program to get the USER 
PROFILE NAME (NOT the numeric UID!) of the owner of an IFS 
object? Or the USER PROFILE NAME associated with a UID?

Or even better, the last user to modify a particular IFS 
object?

This is really starting to give me a headache. First, I 
look into using the chown() API to set the owner to 
whatever user is modifying a *STMF, only to find it only 
works if you're prived, or if you're the owner of the 
object. So then, since every change to the *STMFs in 
question involves rewriting the whole thing, I try 
deleting the *STMF before writing it. That solves the 
problem of SETTING the owner to whoever changed the file, 
but not of GETTING the *USRPRF.

--
JHHL

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.