Hi Lizette, We run HSM in STCMED with no issues in a large plex, a small plex and single systems environment. HSM can consume a lot of resources but if your WLM policy is sound and your workloads are happy then STCMED should suffice. The system related companion tasks in SYSSTC are usually there for a reason; monitors, JES, VTAM, TCP/IP etc....Having them in other places in WLM, of lower importance, can be painful. But I'm probably preaching at this point.
--- On Mon, 5/11/09, Lizette Koehler <stars...@mindspring.com> wrote: From: Lizette Koehler <stars...@mindspring.com> Subject: DFHSM and WLM Settings To: IBM-MAIN@bama.ua.edu Date: Monday, May 11, 2009, 5:00 PM I ran into a small issue where when using Interval Migration DFHSM took all the resources on my small LPAR. Even on my largest LPAR it still consumes a lot of resources. IBM Suggested I set DFHSM to STCMED. My concern is that since we have a lot of tasks in WLM at SYSSTC (not my choice) that if a recall or migrate was requested, that DFHSM might be impacted by the other high runnings tasks. Has anyone delt with Interval Migration and controlling it via WLM? Does anyone else have DFHSM in STCMED and if so, how is that working for DFHSM. Lizette ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
