We run DFHSM in two address spaces for this reason DFHSM and DFHSM#. Take a look at the HOSTMODE=AUX parameter and documentation. I classify the primary DFHSM in SYSSTC and the auxiliary DFHSM in STCLO to provide a service level roughly equivalent to production batch. We have not yet cutover to z/OS R6 yet but IIUC the only big changes in this area were to allow for MORE (nee ANY) multi-tasking in Secondary Space Management. From my student notebook "SETSYS MAXSSMTASKS allows you to set multi-tasking on for two parts of SSm - the migration function and the cleanup function. Note although there is multiple threaded migration from ML1 to ML2, there is still only one task used for ML1-to-ML2 DASD data movement.".
Thanks, Sam -----Original Message----- Q1: DFHSM CPU Utilization We are having a problem with DFHSM CPU utilization. It seems that no matter when we schedule PRIMARY SPACE MANAGEMENT, somebody complains. DFHSM runs as a high priority started task. This is so that recalls are handled quickly. I admit that I have not gone into the manuals yet. I'm am very pressed for time due to staff reductions <sorry>. So, is it possible to have two DFHSM started tasks? One would be high priority for recalls, the other a lower priority for PRIMARY SPACE MANAGEMENT. I know very little of DFHSM. If possible, is it "easy" or "a pain"? Thanks. <> ==================== This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
