Generally 'resources' in the context of 'freeing up' refers to CPU cycles, in which case there is no difference between V XCF,OFF and deactivating the LPAR. If the LPAR is a coupling facility used only by the sandbox, it should be shut down as well.
The problem with 'freeing up memory'--another resource--is that trying to use that memory elsewhere can be problematic. Except for very restricted cases, you cannot add memory to an LPAR without bouncing it. If you move memory to another LPAR disruptively, you have to take another disruptive outage to get it back for your sandbox. If you repeatedly need that level of disruption, you should consider adding memory. The only nondisruptive means I know of for moving memory among LPARs is to define 'reserved' memory in the production LPAR(s). A reserved chunk comes up offline at IPL and can then be configured online/offline via OS command. We used to do this for DR testing. It worked. Memory was a lot more expensive in those days. . . . 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 [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lucas Rosalen Sent: Sunday, December 21, 2014 5:52 AM To: [email protected] Subject: Re: Shutdown or deactivate? Yes, shut the system down and deactivate it on hmc to free up the amount of memory allocated for that LPAR. Em 21/12/2014 11:38, "גדי בן אבי" <[email protected]> escreveu: > Hi, > > I was asked to shut down our sandbox partitions in order to free up > resources. > > Does it matter of I deactivate the partitions? > > Gadi ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
