An OS config for each plex (not LPAR) is the best way to handle this case. No harm in giving yourself plenty of extra volumes in the test plex config for adding or moving data. Just not hundreds. Varying 50 volumes offline takes a far smaller toll on your system than 500.
Having lived this way for many years, I suggest also maintaining a fallback OS config that puts all volumes online at IPL just in case something you need happens to wander outside the designated range. Include a LOADxx member for this all-inclusive config. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Shane Ginnane <ibm-m...@tpg.com.au> To: IBM-MAIN@LISTSERV.UA.EDU, Date: 06/18/2014 05:43 PM Subject: Re: Need help for two LPARS sharing DASD Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Wed, 18 Jun 2014 18:56:44 +0000, Gibney, Dave wrote: > I don't like the idea of messing with my IODF every time I change the volumes my sandbox(s) need. This seems a common refrain, but I have to agree with Matthew - I like the OSCONFIG option. Seems the John has a fairly static list of volumes - extras needed can be varied as needed. Now, about GRS ... Shane ... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
