Ughh. Sometimes I overlook the subject and other times [as
apparently was the case this time] I take the subject line quite
literally for an apparent implication.
Hopefully my later reference in a followup reply to the List
Authorized Objects (QSYLOBJA) API proves fruitful.
P.S. Using the Delete User Profile (DLTUSRPRF) effects the loss of a
variety of things that are not easily or even not possibly recovered by
re-create of the user profile using Create User Profile (CRTUSRPRF) to
the same name; e.g. interactive SQL sessions, and Interactive Profile
Entries (IPEs) that maintain application and OS /preferences/.
On 26-Mar-2014 10:24 -0700, Jack Kingsley wrote:
Misc profiles and or QDFTOWN.
On Wed, Mar 26, 2014 at 1:20 PM, Briggs, Trevor wrote:
I was assuming the OP was talking about a non-system *USRPRF,
because I would surmise that changing the ownership of
system-owned objects would be an extremely dangerous thing to
CRPence on Wednesday, March 26, 2014 1:14 PM wrote:
While certainly an option for a non-system *USRPRF, is that an
option for a system user profile? <<SNIP>>
On 26-Mar-2014 09:53 -0700, Briggs, Trevor (TBriggs2) wrote:
You could always do a DLTUSRPRF with *CHGOWN and then re-create
the user profile when you're done.