Caveat: I get the daily digest so you might already have discussed this...
Kees: I notice that DINTERVAL is an option on SETSMS. Maybe you could automate reducing the value (say 10-15 seconds) before & raising it after the re-org/load+replace work occurs? That way your system overhead is not badly affected. I suspect CacheTime is not really involved here. ps. I, too, use both Quiesced volumes as well as an Overflow Group for the very same purpose. I also use FDR Report & FDR Move for any datasets found on the 'Spill' volumes or groups to try and put them back where they belong. Of course, they can't be in-use/enqueued so it has some limitations ie: DB2, hFS/zFS. In that case, I e-mail a report to the DBAs - after so many days of trying ie. CRDate.GT.3 weeks - asking for a re-org (the only way I know to put it back un-disruptively). --------> signature = 6 lines follows <-------- Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada telephone:1 613 562 5800 x4585 fax:1 613 562 5161 mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee “How *do* you plan for something like that?” Guardian Bob, Reboot “For every action, there is an equal and opposite criticism.” “Systems Programming: Guilty, until proven innocent” John Norgauer 2004 -----Original Message----- From: Vernooij, CP (SPLXM) - KLM [mailto:kees.verno...@klm.com] Sent: April 9, 2014 09:40 Subject: Re: How often does SMS update its free space information? Good hint for Interval and Dinterval. I found the following: [snip] DINTERVAL(nnn) : Directs SMS to allow nnn seconds (1 to 999) to elapse between reading device statistics from a 3990-3 control unit. The default is 150 seconds. [snip] 150 seconds is the interval to update the volume statistics. It seems, that if DBM1 deletes a dataset from a volume, SMS will not be informed of the new free space info of that volume. In this scenario, with large tablespaces, we could need extra space on other volumes for the entire tablespace, just because SMS is not aware of the fact that DBM1 just made space available for the new allocation. [snip] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
