Sam, The APAR text talks about the TOD clock, not the local time. So this isn't really a problem for any shop that doesn't use GMT=LOCAL, correct? Or is that not the way you interpret it? I supposed I can open a PMR for clarification.
Strange that the description / title says "z/OS 1.8 only", but the problem says HBB7730 and above. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html On Sun, 18 May 2008 13:10:27 -0400, Knutson, Sam <[EMAIL PROTECTED]> wrote: >Hi, > >Looking ahead to falling back from Daylight Savings Time November 2, 2008 this APAR OA18496 might be good to have. > > Best Regards, > > Sam Knutson, GEICO > Performance and Availability Management > mailto:[EMAIL PROTECTED] > (office) 301.986.3574 > >"Think big, act bold, start simple, grow fast..." > >APAR Identifier ...... OA18496 Last Changed ........ 08/05/02 > SYSTEM ABEND15F REASON 401 RC401 RC 401 ONLY Z/OS 1.8 ONLY > > > Symptom ...... AB ABEND15F Status ........... CLOSED PER > Severity ................... 2 Date Closed ......... 08/04/17 > Component .......... 5752SC1CR Duplicate of ........ > Reported Release ......... 730 Fixed Release ............ 999 > Component Name 5752 REAL STOR Special Notice ATTENTION > Current Target Date ..08/05/09 Flags > SCP ................... > Platform ............ PERVASIVE > > > Status Detail: SHIPMENT - Packaged solution is available for > shipment. > > PE PTF List: > > PTF List: > Release 730 : UA40526 available 08/05/01 (F804 ) > Release 740 : UA40527 available 08/05/01 (F804 ) > Release 750 : PTF not available yet > > > Parent APAR: > Child APAR list: > > > ERROR DESCRIPTION: > During NIP processing the real storage manager builds a table > for global LRU steal processing during processing in ieavnpe8. > The code uses store clock to establish time stamps for the > entries in this table but the clockxx parameter does not > get processed until ieavnp21. Therefore the TOD clock can be > changed after rsm has already stored the clock, making the > times rsm stored invalid during later SRM processing. > > > LOCAL FIX: > none > > > PROBLEM SUMMARY: > **************************************************************** > * USERS AFFECTED: Users at HBB7730 and above. * > **************************************************************** > * PROBLEM DESCRIPTION: If the TOD clock setting is moved * > * backwards in time (via CLOCKxx in * > * parmlib, reply to IEA101A, etc), * > * calculations of the time spent on a * > * Global LRU segment scan may produce * > * a negative result, ultimately * > * resulting in ABEND15F, reason code * > * 401. * > **************************************************************** > * RECOMMENDATION: * > **************************************************************** > SRM's scan of the Global LRU segments to calculate the UIC of > each segment determines that the GLRUSegmentPreviousStartTime > is greater than the GLRUSegmentStartTime, leading to System > ABEND15F, reason code 401. > > > PROBLEM CONCLUSION: > Time values stored in the LRU Segment block must be > re-initialized after the TOD clock value for the IPL processor > is established in IEAVNP21. > > > TEMPORARY FIX: > > > COMMENTS: > > > MODULES/MACROS: IAXSEGMT IEAVNP21 > > > SRLS: NONE > > > RTN CODES: > > > CIRCUMVENTION: > > > MESSAGE TO SUBMITTER: > > >==================== >This email/fax message is for the sole use of the intended >recipient(s) and may contain confidential and privileged information. >Any unauthorized review, use, disclosure or distribution of this >email/fax is prohibited. If you are not the intended recipient, please >destroy all paper and electronic copies of the original message. > >---------------------------------------------------------------------- >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 >-------------------------------------------------------- > >This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. >-------------------------------------------------------- > >---------------------------------------------------------------------- >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 ---------------------------------------------------------------------- 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
