On Fri, 20 Nov 2009 14:50:11 -0600, Mark Zelden <mark.zel...@zurichna.com> wrote:
>On Fri, 20 Nov 2009 15:29:01 -0500, Baraniecki, Ray ><ray.baranie...@morganstanley.com> wrote: > >>Is it possible to isolate one LPAR in a CEC and set the date/time to a >different value than the other LPARs in the same CEC? >> > >Yes. This has been possible since the 9672 G5 (I think... could >have been prior). This was needed for Y2K testing. Of course >you have to have your CLOCKxx member set up to not use >the sysplex timer. > >Search the archives or google for Y2K and TOD. > >Mark >-- >Mark Zelden >Sr. Software and Systems Architect - z/OS Team Lead >Zurich North America / Farmers Insurance Group - ZFUS G-ITO >mailto:mark.zel...@zurichna.com >z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ >Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO >Search the archives at http://bama.ua.edu/archives/ibm-main.html While setting a different time is possible; but, it may not be the best of ideas. Shared DASD concerns may take precedence. If a system with a higher date touches any dataset(s), HSM (or equivalent package) may start behaving in an unexpected way. That dataset's last reference date would be changed to a new (higher) date, and impact any incremental backups in an undesired manner. (Also, GRS will not allow 2 systems with different dates; so, integrity is out the window.) Think it through first. A completely isolated LPAR should work fine. Concerns will arise if anything is shared. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
