Peter,
I can get very confused reading the books. This is from the V1R13 MVS
System Commands book for "D OMVS,U":
U=userid
Displays process information for all processes associated with the specified
TSO/E user ID. Use this operand when a user requests that a hung process be
canceled. You can display all processes owned by the user and find the
address space ID (ASID) of the process that needs to be canceled. Then use
the CANCEL command to cancel the address space.
<MNPB4U>fuser -cu /tmp
/SYSTEM/tmp: 8c(IBMUSER) 25c(RMFGAT) 50331938(IBMUSER) 33554852c(AUTO2) 475(IBMU
SER)
So HEX PID 50331938 is DEC 1345526072
D OMVS,PID=1345526072
BPXO042I 09.17.49 DISPLAY OMVS 889
OMVS 000E ACTIVE OMVS=(00,FF,PB)
1345526072 NOT FOUND
D OMVS,U=IBMUSER
BPXO042I 09.20.04 DISPLAY OMVS 090
OMVS 000E ACTIVE OMVS=(00,FF,PB)
IBMUSER NOT FOUND
D OMVS,PID=50331938
BPXO070I 09.28.55 DISPLAY OMVS 879
OMVS 000E ACTIVE OMVS=(00,FF,PB)
USER JOBNAME ASID PID PPID STATE START CT_SECS
WEBNCSP WEBNCSP 00D5 50331938 1 HK------ 06.50.27 32.7
LATCHWAITPID= 0 CMD=IMWHTTPD
THREAD_ID TCB@ PRI_JOB USERNAME ACC_TIME SC STATE
25DF8D0000000000 00AFF208 OMVS .039 KIN KU
25E1250000000001 00AC6560 OMVS .110 ACP JF V
I can look at what they are doing to get a guess of who it is. Just hoping I
could learn more about the USERIDs from BPXOINIT that are filling up /tmp. I
suppose I can start a batch shell process using the OMVS segment associated
with IBMUSER. Would I show up as an "MVS USERID"? Yup, When we move from
V1R13 to V1R2 the superuser stuff will change. So far with the superuser
changes we have been getting hit with OWNERSHIP issues in regards to IBMUSER in
the filesystems. I just find it interesting the OMVS DISPLAY can see the PID,
but not the USERID. The shell knows about the PID and about IBMUSER (or some
UID=0 USER).
Have a good weekend, Dave
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Peter Hunkeler
Sent: Thursday, October 23, 2014 11:12 PM
To: [email protected]
Subject: AW: Re: BPXOINIT and SYSPLEX Mode Question
> My "fuser -cu /tmp" command shows many users of /tmp: > > <MNPB4U>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 with IBMUSER on them: > IBMUSER 50331938 1 - Oct 21 ? 0:13 IMWHTTPD >>
> Q). How can IBMUSER have PID 50331938 that's using /tmp and not be found as
> an OMVS USERID?
There is no such thing as a "TSO USERID" or "OMVS USERID". There are only "MVS
USERIDs". Every STC, job or user session runs with a specific MVS USERID (short
"userid" hereafter). If a user wants to be able to logon to TSO, its userid
needs an "attachement" called "TSO segment". Similarly, if user, job, STC, etc.
wants to use some z/OS UNIX function, the corresponding userid and the
associated group need an "attachement" called "OMVS segment".
The OMVS segments, besides other attributes, hold the important UNIX attributes
"UID" and "GID". File system objects, such as directories, files, links, etc.,
are *owner* by a UID and belong to a GID.
UNIX processes have UIDs and GIDs assigned. These are pure numbers, not names!
Mostly, when UNIX ownership is displayed as result of a command, the number
(UID, GID) is translated to the associated USERID and GROUP, resp. with the
help of the security product. This works fine as long as you don't have any UID
or GID shared, i.e. assigned to more than one USERID or GROUP.
I bet IBMUSER does have an OMVS segment with UID=0. There seem to be multiple
USERIDs with UID=0 in their OMVS segments. In response to the command, uid=0 is
translated back to a USERID, and its just one of those having the uid that will
be shown. Note this is not specific to uid=0; it equally applies to any uid
that is shared between USERIDs.
Try "D OMVS,PID=ddddddd"' where ddddddd is the *decimal* value corresponding
the pid show in *hex* in the response to the fuser command.
--
Peter Hunkeler
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
