> As others have pointed out, accessing an active SFS directory can be > a big contributor. I confirmed this by letting a machine sit idle > for 2 hours while it had such a directory accessed. After 2 hours, I > released the directory and it was disconnected 15 minutes later. In > this case, I would expect to see VTIME incrementing because CMS is > accepting the interrupts. If they are IUCV interrupts, that measure > is blown out the door, too. Is there no such thing as an idle user anymore?
When you use RELEASE to release an SFS dirid, CMS does not really gets rid of this directory. So, CMS will still get notified of updates to that directory. Only when CMS becomes short on storage it will completely release the SFS dirs that it maintains in the background. To really break it, use the CSL call DMSPURWU, but that releases everything, also the directories that are fully ACCESSed. I've got an SFSDISC EXEC that uses DMSPURWU and reaccesses the directories that are fully accessed. Kris, IBM Belgium, VM customer support
