Re: the OPERLOG. Unless I totally misunderstood, a DASD logstream cannot be shared between multiple systems. And it does not appear to me that I can make a system unique OPERLOG, one for each system. So I can't use an OPERLOG at all without a Coupling Facility and a parallel sysplex.
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2g391/2.14.2.3 <quote> You can also use OPERLOG as a DASD-only log stream. This method is only suitable for a single system sysplex, because a DASD-only log stream is single-sysplex in scope and you can only have one OPERLOG log stream per sysplex. This means that if you make OPERLOG a DASD-only log stream, only one system can access it. See the system logger chapter of z/OS MVS Setting Up a Sysplex for information on DASD-only log streams. </quote> -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM <snip> > > Why can't you use operlog in a basic sysplex? Use a dasd-only > logstream. > On first thought I can't think of any reason why this is not possible. > > Kees. ---------------------------------------------------------------------- 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
