I would go with 1 HSMplex unless the technopolitical factors contraindicate! YMMV.
Short version: 1) Multiple HSMplexes are allowed. Depend's on your needs. (I have no experience w/multiple HSMPLEX's). Probably also depends on your GRS configuration, catalog sharing,..... If you do run multiple HSMplexes, each member of the HSMplex must share the associated control datasets. 2) Each image will run a copy of DFHSM. At least 1 image will run another task (DFHSMP). DFHSM tasks handle command tasks i.e. individual dataset migration/recall. DFHSMP handles automatic (HSM scheduled) tasks. i.e. backup, space management, etc.... See http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2I480/CCON TENTS?SHELF=DGT2BK90&DN=SC35-0418-10&DT=20090605105438 Section 2 Customizing DFHSM Topic 2.1 HSM in a SYSPLEX environment. HTH, <snip> Quick question(s). In a multi-image environment, where all systems are part of the same sysplex(some systems production, some DEV, but all in the same sysplex), and all DASD is shared with all systems, is there any pro's or con's to having one big HSM plex? Or having multiple HSM plex? Are there any restrictions? Can dataset recalls occur across HSMplex's? </snip> ---------------------------------------------------------------------- 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
