AW: Re: BPXOINIT and SYSPLEX Mode Question
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. Ownership issues? Have you changed UIDs in the OMVS segments of your userids? 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). It well does! The result of a D OMVS,U= or D OMVS,PID= has the *userid* on the far left. Note that this is the userid, not the uid that is associated with the process (PID). Do you have the BPX.DEFAULT.USER profile defined to class FACILITY? If so what is the content of the APPLDATA field of this profile? --Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: BPXOINIT and SYSPLEX Mode Question
Peter, Thank you for your insight on this. I was just hoping on a single system BPXOINIT could somehow tell me more. Lots of changes for stuff like filling /tmp when we move from V1R13 to V2R1. Thanks again, Dave -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Hunkeler Sent: Thursday, October 23, 2014 10:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: AW: Re: BPXOINIT and SYSPLEX Mode Question 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. Excerpt from the MVS System Commands book: DISPLAY or DDisplay the type BPXMCDS couple data set information relating to theshared file system file system. D is an alias of DISPLAY. z/OS UNIX Services do not use a couple data set if you run with SYSPLEX=NO. It seems to be that the information you're looking for is retrieved from the CDS. Specifically, the term OWNER denotes the z/OS instance that is the system that is currently responsible for the mounted file system. Ownership can be transferred to another system in the sysplex, either if the system is shutdown, or by command. Ownership in this sense does not apply with SYSPLEX=NO. You can mount a files sytem in R/W mode on one system only and this is also the owner. If the D OMVS,F... answers your request, this system is automatically the owner. A file system can be mounted in R/O mode on multiple systems concurrently, but each system is owning its own mount. They do not talk to each other regarding file system activity. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: BPXOINIT and SYSPLEX Mode Question
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. MNPB4Ufuser -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 ASIDPID PPID STATE START CT_SECS WEBNCSP WEBNCSP 00D5 50331938 1 HK-- 06.50.2732.7 LATCHWAITPID= 0 CMD=IMWHTTPD THREAD_IDTCB@ PRI_JOB USERNAME ACC_TIME SC STATE 25DF8D00 00AFF208 OMVS.039 KIN KU 25E12501 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Hunkeler Sent: Thursday, October 23, 2014 11:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: AW: Re: BPXOINIT and SYSPLEX Mode Question My fuser -cu /tmp command shows many users of /tmp: MNPB4Ufuser -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=ddd' where ddd 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
AW: Re: BPXOINIT and SYSPLEX Mode Question
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 take the value to the D OMVS,PID= command. I'm sorry to have mislead you. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
AW: Re: BPXOINIT and SYSPLEX Mode Question
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. Excerpt from the MVS System Commands book: DISPLAY or DDisplay the type BPXMCDS couple data set information relating to theshared file system file system. D is an alias of DISPLAY. z/OS UNIX Services do not use a couple data set if you run with SYSPLEX=NO. It seems to be that the information you're looking for is retrieved from the CDS. Specifically, the term OWNER denotes the z/OS instance that is the system that is currently responsible for the mounted file system. Ownership can be transferred to another system in the sysplex, either if the system is shutdown, or by command. Ownership in this sense does not apply with SYSPLEX=NO. You can mount a files sytem in R/W mode on one system only and this is also the owner. If the D OMVS,F... answers your request, this system is automatically the owner. A file system can be mounted in R/O mode on multiple systems concurrently, but each system is owning its own mount. They do not talk to each other regarding file system activity. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
AW: Re: BPXOINIT and SYSPLEX Mode Question
My fuser -cu /tmp command shows many users of /tmp: MNPB4Ufuser -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=ddd' where ddd 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
BPXOINIT and SYSPLEX Mode Question
Dear Friends, I've noticed on our z/OS V1R13 system that we do a F BPXOINIT,SHUTDOWN= 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 MOUNTEDLATCHES TFS11 ACTIVE RDWR 04/15/2014 L=23 NAME=/TMP 19.06.21Q=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: MNPB4Ufuser -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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hansen, Dave L - Eagan, MN Sent: Wednesday, October 22, 2014 1:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: BPXOINIT and SYSPLEX Mode Question Dear Friends, I've noticed on our z/OS V1R13 system that we do a F BPXOINIT,SHUTDOWN= 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 MOUNTEDLATCHES TFS11 ACTIVE RDWR 04/15/2014 L=23 NAME=/TMP 19.06.21Q=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: MNPB4Ufuser -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 lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: BPXOINIT and SYSPLEX Mode Question
Like Rex said, probably due to UID=0. Since you seem to want a mvs command to do it you can execute f axr,bpxwlsof '/tmp' to find out the user id. If you need to know the jobname I have a rexx that you can also put on the system rexx library to list it. Regards, Leo -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hansen, Dave L - Eagan, MN Sent: Wednesday, October 22, 2014 2:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: BPXOINIT and SYSPLEX Mode Question Dear Friends, I've noticed on our z/OS V1R13 system that we do a F BPXOINIT,SHUTDOWN= 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 MOUNTEDLATCHES TFS11 ACTIVE RDWR 04/15/2014 L=23 NAME=/TMP 19.06.21Q=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: MNPB4Ufuser -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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: BPXOINIT and SYSPLEX Mode Question
Leo, Is bpxwlsof in your SYS1.SAXREXEC lib? I don't see it in mine, my message is not found in REXXLIB. In V2R1 TFS gets FSFULL. I'm just trying to get through on V1R13. We have no df commands that execute to query the filesystems. I guess we just wait for the full message. I guess we don't get a full message on V1R13 for a TFS filesystem. Sounds like we all should be querying /tmp until we get to V2R1. Thank you, Dave -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Leonardo Vaz Sent: Wednesday, October 22, 2014 2:55 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: BPXOINIT and SYSPLEX Mode Question Like Rex said, probably due to UID=0. Since you seem to want a mvs command to do it you can execute f axr,bpxwlsof '/tmp' to find out the user id. If you need to know the jobname I have a rexx that you can also put on the system rexx library to list it. Regards, Leo -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hansen, Dave L - Eagan, MN Sent: Wednesday, October 22, 2014 2:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: BPXOINIT and SYSPLEX Mode Question Dear Friends, I've noticed on our z/OS V1R13 system that we do a F BPXOINIT,SHUTDOWN= 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 MOUNTEDLATCHES TFS11 ACTIVE RDWR 04/15/2014 L=23 NAME=/TMP 19.06.21Q=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: MNPB4Ufuser -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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: BPXOINIT and SYSPLEX Mode Question
Hello Dave!
Yes, it is in the z/OS 2.1 SAXREXEC library and it is an alias of ZLSOF. You
can customize your own rexx to be executed by system rexx though, I've done
this for my personal use, should work under system rexx just fine (no
guarantees ^_^):
/* rexx */
parse arg path
call syscalls 'ON'
address syscall 'getcwd cwd'
address syscall 'geteuid'
myeuid=retval
if myeuid0 then
do
say 'Not running UID=0 - attempting to set UID=0'
address syscall 'getuid'
myuid=retval
address syscall 'setreuid 0 0'
lerrno=errno
lerrnojr=errnojr
address syscall 'geteuid'
if retval0 then
do
say
say 'Unable to set UID to 0. Errno='lerrno 'Reason='lerrnojr
exit retval
end
end
cmd=fuser -cu path
cmdrc=bpxwunix(cmd,,'cmo.','cme.')
say 'command return code='cmdrc
say
if cmdrc 0 then do
do i=1 to cmo.0
say cmo.i
end
do i=1 to cme.0
say cme.i
end
end
else if cmo.0 0 then do i=1 to cmo.0
say 'Listing users of 'word(cme.1,1)
SAY 'JOBNAME |PID |ASIDX'
do j = 1 to words(cmo.i)
psrc=bpxwunix('ps -p 'word(cmo.i,j)' -ojobname -opid
-oxasid',,'pso.','pse.')
upper pso.2
say
left(word(pso.2,1),8)'|'left(word(pso.2,2),10)'|'right(word(pso.2,3),4,'0')
end
end
Regards,
Leo
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Hansen, Dave L - Eagan, MN
Sent: Wednesday, October 22, 2014 4:42 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: BPXOINIT and SYSPLEX Mode Question
Leo,
Is bpxwlsof in your SYS1.SAXREXEC lib? I don't see it in mine, my message is
not found in REXXLIB. In V2R1 TFS gets FSFULL. I'm just trying to get through
on V1R13. We have no df commands that execute to query the filesystems. I
guess we just wait for the full message. I guess we don't get a full message
on V1R13 for a TFS filesystem. Sounds like we all should be querying /tmp
until we get to V2R1.
Thank you, Dave
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Leonardo Vaz
Sent: Wednesday, October 22, 2014 2:55 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: BPXOINIT and SYSPLEX Mode Question
Like Rex said, probably due to UID=0. Since you seem to want a mvs command to
do it you can execute f axr,bpxwlsof '/tmp' to find out the user id. If you
need to know the jobname I have a rexx that you can also put on the system rexx
library to list it.
Regards,
Leo
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Hansen, Dave L - Eagan, MN
Sent: Wednesday, October 22, 2014 2:44 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Re: BPXOINIT and SYSPLEX Mode Question
Rex, I wish I did have zlsof. MNPB4Uzlsof zlsof: FSUM7351 not found Thank you for your suggestion. I reformatted it a bit so I can cross-reference the number to the name. MNPB4Ups -e -oruser=USER -ouid -opid -oppid -ostime -oatime -oargs=CMD USER EUIDPID PPIDSTIME 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex Sent: Wednesday, October 22, 2014 2:54 PM To: IBM-MAIN@LISTSERV.UA.EDU 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hansen, Dave L - Eagan, MN Sent: Wednesday, October 22, 2014 1:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: BPXOINIT and SYSPLEX Mode Question Dear Friends, I've noticed on our z/OS V1R13 system that we do a F BPXOINIT,SHUTDOWN= 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 MOUNTEDLATCHES TFS11 ACTIVE RDWR 04/15/2014 L=23 NAME=/TMP 19.06.21Q=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: MNPB4Ufuser -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 lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
