# fuser -cu /tmp
/SYSTEM/tmp: 67108942c(OEDFLTU) 130c(OEDFLTU) 132c(OEDFLTU) 133c(OEDFLTU)
134c(OEDFLTU) 135c(OEDFLTU) 136c(OEDFLTU) 137c(OEDFLTU) 13
8c(OEDFLTU) 139c(OEDFLTU) 140c(OEDFLTU) 141c(OEDFLTU) 142c(OEDFLTU)
143c(OEDFLTU) 144c(OEDFLTU) 145c(OEDFLTU) 146c(OEDFLTU) 50331805
c(OEDFLTU) 16777953(OMVSKERN) 83887581c(OEDFLTU)
And It would be disruptive to stop some of these after going through the
exercise of mapping them to active address spaces. Note 2nd to last is OMVSKERN
Dave Gibney
Information Technology Services
Washington State University
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of Paul Gilmartin
> Sent: Monday, April 08, 2013 3:48 PM
> To: [email protected]
> Subject: Re: TFS tmp directory problems
>
> On Mon, 8 Apr 2013 21:50:28 +0000, Gibney, Dave wrote:
>
> >My point was to possibly make it bigger. I guess I don't see 1866M as small
> >:)
> >If you wish to increase it, without an IPL, I expect that to be a problem :)
> >
> >FUSER fuser -- List process IDs of processes with open files might be
> >helpful,
> but I would expect some important address spaces to show up as users.
> >
> The OP might get better information from the MVS-OE LISTSERV.
>
> I don't know whether fuser reports files that have been unlinked but remain
> open, which may be the OP's problem.
>
> -- gil
>
> ----------------------------------------------------------------------
> 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
