> Q). It says "The Modify Function Cannot Be Performed". Besides turning on
> SYSPLEX=YES, how can I get BPXOINIT to do a FILESYS=DISPLAY? Yes, I can work
> with "D OMVS,F" for Filesystems, but the RedBook on z/OS V1R13 Implementation
> shows that bpxoinit can tell me the UID and the OWNER.
Exce
> My "fuser -cu /tmp" command shows many users of /tmp: > > fuser -cu
> /tmp > /SYSTEM/tmp: 8c(IBMUSER) 25c(RMFGAT) 50331938(IBMUSER)
> 33554852c(AUTO2)> > fuser says these are TSO USERIDs. But when I enter "d
> omvs,u=IBMUSER" I get back > IBMUSER NOT FOUND. With "ps -ef" I can see the
> PIDS
> So HEX PID 50331938 is DEC 1345526072
My bad. I didn't lookup the description of fuser. due to the "c" in the process
id of the first process, I was concluding it was a hex value. It is not, it is
decimal! The "c" is a usage indicator. So drop any trailing "c" or "r" from the
process id and
> Displays process information for all processes associated with the specified
> TSO/E user ID.
The problem is that some documentation is using some terms inappropriately.
"TSO Userid" being one of the terms. z/OS UNIX books mostly thoughtlessly talk
about "TSO Userid" when they actually mea
> When we move from V1R13 to V1R2 the superuser stuff will change.
Not sure what you mean. BPX.DEFAULT.USER goes away, but this has nothing to do
with superuser.
> So far with the superuser changes we have been getting hit with OWNERSHIP
> issues in regards to IBMUSER in the filesystems.
Owner
