Others have made excellent points. The bottom line is that there is no good technical solution. Sharing DASD and catalogs brings problems like yours. Not sharing DASD brings business problems.
The 'best' technical solution is a totally isolated LPAR with only its DASD online. Many of us can't do that, so we live with the consequences. For your case, I'd suggest finding out what is causing the reserve and see if using GRS to convert the reserve to an enqueue is suitable for you. Sometimes full pack backups cause these kinds of problems. Consider routing those jobs to LPARS that can own a reserve and not hurt anything. HTH -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Victor Zhang Sent: Tuesday, July 08, 2008 2:36 AM To: [email protected] Subject: Sharing catalog among systems,benefits or trouble? Hi all, We have a shared dasd that hold a shared user catalog and there are a third party software installed on that dasd, occasionally we met a problem that a LPAR will reserve the dasd and there are IOS071I meesage appeared in syslog/operlog, how can we avoid the problem? Is it suggested to share catalog and dasd among systems that may from different sysplex/standalone systems? Regards Victor NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- 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
