Re: CPE3025 - No such path or directory. (re: QDFTOWN)

On 30-Dec-2014 13:39 -0600, Gary Thompson wrote:

On Tuesday, December 30, 2014 12:11 PM CRPence wrote:

On 29-Dec-2014 15:24 -0600, Gary Thompson wrote:

<<SNIP>>
Public Read and Execute with all Directories owned by QDFTOWN
<<SNIP>>

The purpose of the User Profile (USRPRF) object named QDFTOWN is
to own objects for which there is no discernible owner; either in
restore or /reclaim/ of ownership. Any ownership by that user
profile should be deemed an error in need of correction; i.e.
recovery from the error should be effected using one of the Change
[Object] Owner (CHGOBJOWN or CHGOWN) commands against the
object(s). The Change Owner should request *YES for the option to
Revoke Current Authority (RVKOLDAUT) to ensure that the user
QDFTOWN does not maintain any authorities to the object; that user
should AFaIK have authorities only to itself, such that Display
User Profile (DSPUSRPRF) for the Object Authority (*OBJAUT) Type Of
Information (TYPE) should list only the one object QDFTOWN of
object type *USRPRF.

Thank you Chuck for your comments, but I'm not understanding what, if
any, action should or could be made with respect to the fact that
QDFTOWN appears as the owner of Directories on the QNTC.

It seems 'normal' that QDFTOWN shows as owner given that the QNTC
had provided a view of Directories and files located on a different
server ?

If the OS chose to use the actual user profile name versus a Special Value to represent the logical condition of "no discernible owner" [due to the object residing on a remote system; e.g. *RMTSYS to denote that the ownership is defined\available at\to the remote system] in the described scenario [i.e. use of /QNTC], then that is unfortunate :-( If the owner of an object is manifest as QDFTOWN and a program attempts to correct the ownership by Change Owner (CHGOWN), the program should not have to know all of the file systems for which to special-case the legitimate value 'QDFTOWN'; the program should be able to test the first byte of the value designating the owner for the asterisk [or against the consistent Special Value; e.g. *RMTSYS], to know that an attempt to /correct/ the ownership is futile.

My comment was merely for any physical ownership; i.e. any object [within /QSYS.LIB or any other file system] actually *owned* by the User Profile object named QDFTOWN.