I did not see in this thread any mention of who owns the DR environment. We own and manage our own DR environment, so we know exactly what's there. If OP's DR is in the hands of a vendor, then the I/O configuration may differ as others have indicated. In particular, UCB location can make a big difference if there are lots of devices. I believe that LOCANY defaults to NO. Unless specifically coded for above-the-line location, UCBs in a large configuration can take up a lot of space below 16M. If as others have suggested the specified CSA value is already close to a megabyte boundary, a lot of unexpected UCBs could cause COMMON to encroach on PRIVATE.
. . . 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 Ed Finnell Sent: Thursday, August 27, 2015 2:09 PM To: [email protected] Subject: Re: Smaller Private Area in DR A "pocket protector's" worth of Display Commands. http://idcp.marist.edu/pdfs/ztidbitz/MVS%20CONSOLE%20COMMANDS.pdf In a message dated 8/27/2015 3:55:31 P.M. Central Daylight Time, [email protected] writes: Of course, you want to recheck the end of the specification and the next 1M boundary once in a while, and (continue to!) monitor used CSA to make sure overt action (such as reducing what's in the LPA list) is not needed to pull the starting address back far enough to preserve CSA free space. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
