Rex,

   I wish I did have zlsof.

<MNPB4U>zlsof
zlsof: FSUM7351 not found

   Thank you for your suggestion.  I reformatted it a bit so I can 
cross-reference the number to the name.

<MNPB4U>ps -e -oruser=USER -ouid -opid -oppid -ostime -oatime -oargs=CMD
    USER       EUID        PID       PPID    STIME  TIME CMD
 IBMUSER          0          1          0   Oct 21  0:02 BPXPINPR
 IBMUSER          0          2          1   Oct 21  0:00 EZBREINI


      Thank you,  Dave



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Pommier, Rex
Sent: Wednesday, October 22, 2014 2:54 PM
To: [email protected]
Subject: Re: BPXOINIT and SYSPLEX Mode Question

If you want the UID in the ps -ef command, try this instead:

ps -e -ouid  -opid,ppid,pcpu=C -ostime,tty=TTY -oatime,args=CMD

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Hansen, Dave L - Eagan, MN
Sent: Wednesday, October 22, 2014 1:44 PM
To: [email protected]
Subject: BPXOINIT and SYSPLEX Mode Question

Dear Friends,

   I've noticed on our z/OS V1R13 system that we do a "F 
BPXOINIT,SHUTDOWN=xxxx" and it works!  However about z/OS V1R7 came a BPXPRMxx 
parameter SYSPLEX(YES/NO).  We are a SYSPLEX=NO shop.  So when I enter "F 
BPXOINIT,FILESYS=DISPLAY,FILESYSTEM=/TMP" I get an error: "BPXM106I UNIX SYSTEM 
SERVICES WAS NOT STARTED IN SYSPLEX MODE".  I am looking for some help after 
reading the books.  Perhaps the UID and OWNER information is only populated 
with zFS ownership (rather that z/OS UNIX ownership) of filesystems.  I'd still 
like to track down our /tmp users in a non-shared environment.  Supposedly /tmp 
filled up the other day and we IPL'd.  UID=0 can report different USERIDs if 
they are all UID=0.  It looks like OMVS USERIDS and TSO USERIDS also reported 
differently.  And OWNERSHIP might change depending on whether or not you have 
zFS Sysplex Sharing (SYSPLEX=YES).

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.


  My OMVS display "d omvs,f,n=/tmp" shows:

   D OMVS,F,N=/TMP
BPXO045I 12.58.20 DISPLAY OMVS 697
OMVS     000E ACTIVE             OMVS=(00,FF,PC)
TYPENAME   DEVICE ----------STATUS----------- MODE  MOUNTED    LATCHES
TFS            11 ACTIVE                      RDWR  04/15/2014  L=23
  NAME=/TMP                                         19.06.21    Q=0
  PATH=/SYSTEM/tmp
  MOUNT PARM=-s 10

   Figure 15-27 in the RedBook on z/OS V1R13 Implementation shows more 
information from the omvs command that what I am getting.  It shows UID=888 and 
OWNER=SC74.

Q).  How can I get more information out of my "d omvs,f" command so I can see 
the UIDs and OWNERs?


   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?


      Thank you,  Dave

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful.  If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format.  Thank you.

----------------------------------------------------------------------
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

Reply via email to