Kees wrote:
>>Now, like Mike's proposal, it can help you make life a little easier. >>PLPA can spill over to COMMON, but not vica versa. So if you want to >>manage space for both easily, you can do this by creating a small PLPA >>and a large COMMON, which has free space for both. With both a large >>PLPA and a COMMON, you must manage growth and free space for both. Not a >>very big issue, but just a little thing to make life somewhat easier. What prevented me from ever doing the small PLPA thing was the last part of the description of the IRL005E message... ILR005E PLPA PAGE DATA SET FULL, OVERFLOWING TO COMMON DATA SET Explanation: The PLPA page data set has become full. All subsequent writes for the PLPA will be sent to the COMMON page data set. System Action: The system continues to build the link pack area by writing pages for the remaining LPA modules to the common page data set. If the common page data set is unavailable or becomes full, the system will be terminated with a wait state code X'03C' reason 3. The way I always figured it was belts & braces... if either one of them became unavailable, the other one was still there, which is why I also have them on separate volumes. Could never see the point of gambling with the possibility of downtime on a Prod system... Herbie Elavon Financial Services Limited Registered in Ireland: Number 418442 Registered Office: Block E, 1st Floor, Cherrywood Business Park, Loughlinstown, Co. Dublin, Ireland Directors: Robert Abele (USA), John Collins, Terrance Dolan (USA), Pamela Joseph (USA), Declan Lynch, John McNally, Malcolm Towlson Elavon Financial Services Limited, trading as Elavon, is regulated by the Financial Regulator ---------------------------------------------------------------------- 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
