MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » March 2014

Re: QDFTOWN changing objects to a new owner



fixed

Misc profiles and or QDFTOWN.


On Wed, Mar 26, 2014 at 1:20 PM, Briggs, Trevor (TBriggs2) <
TBriggs2@xxxxxxxxxxx> wrote:

Chuck, 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 undertake.

Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Wednesday, March 26, 2014 1:14 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: QDFTOWN changing objects to a new owner

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.

While certainly an option for a non-system *USRPRF, is that an option

for a system user profile? I seem to recall [and I verified on v5r3
that still,] the DLTUSRPRF command had the "system" user profile names
hard-coded against which to test the specified USRPRF() specification
for which the effect would be CPD2205 "User profile cannot be deleted."
F/QCAIFLD with additional details suggesting "This user profile is
required by the system and cannot be deleted."

If that checking within the command was since removed, then...

As a /system/ user profile, would the request to DLTUSRPRF QDFTOWN
OWNOBJOPT(*CHGOWN NewOwnName) fail immediately [per the msg CPD2205 as
was the case in the past, but as a result of the CPP vs the command
definition objects parameter checking], or would the request enable the
effect of the CHGOBJOWN\CHGOWN processing, and then fail only to effect
the actual user profile deletion?

--
Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


************************************************************************************************************************************************************************************************************
This message originates from Lincare Holdings Inc. It contains information
which may be confidential or privileged and is intended only for the
individual or entity named above.
It is prohibited for anyone else to disclose, copy, distribute or use the
contents of this message.
All personal messages express views solely of the sender, which are not to
be attributed to Lincare Holdings Inc., and may not be copied or
distributed without this disclaimer.
If you received this message in error, please notify us immediately at
MailAdmin@xxxxxxxxxxx or (800) 284-2006.

************************************************************************************************************************************************************************************************************

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact