Mark, I asked IBM about that, but in their words, the timing of that command was hard to pin down. It would have to be early enough in the startup or last thing in the shutdown (prior to F BPXOINIT,shutdown=filesys). They didn't sound too keen on the idea.
_________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Mark Post Sent: Monday, December 21, 2015 5:29 PM To: [email protected] Subject: Re: managing /tmp >>> On 12/21/2015 at 08:09 AM, "Jousma, David" <[email protected]> wrote: > All, > > We have for the longest time used a 256MB TFS for /tmp. Beauty of that is > with every IPL, the transient data is wiped out, and start fresh again. > We've very rarely ever run into filesystem space problems. However, > our DB2 sysprogs are running into problems when performing maintenance > activities on our IDAA appliances when loading new/updated code to it > via their gui interface. Seems as though that tool wants to use /tmp space > between copying > data from DB2 filesystem to IDAA hardware. Some of these objects are 2G or > larger in size, so they have run into space problems, and they claim > there is no way to override what to use for temp space. > > So, I've been contemplating making /tmp a standard ZFS of sufficient > size, but am wondering how you all setup controls to manage the space? Aside from what others have mentioned, an additional thing you could do is with every IPL, do an "rm -rf /tmp/*" command. This will replicate the previous behavior in that everything goes away with an IPL, so there shouldn't be a significant backlash from it. If you were able to get by with a 256MB /tmp before, and are only doing this for one (mis-behaving) application, I'm not sure that skulker is really going to be that necessary. Of course, time will tell. Mark Post ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
