On Thu, 13 Mar 2008 21:54:31 -0400, Knutson, Sam <[EMAIL PROTECTED]> wrote:
>At the time change here an anomaly occurred in RMF. >I opened a PMR on this but we have only the WTO message which occurred on every system in the Sysplex when the ETR changed the time. > >There are no hits for the ERB307I BPX1SDD with return code 0000 >Reason 0000 found by me or Level-2. ERB3GINI is the RMFGAT init module calling BPX1SDD to make RMFGAT a permanent process. RMF only issues the message if it gets a non-zero return VALUE back from the USS service request. The time change drive an RMF restart, and this error occurred when >RMFGAT was restarting. > >01:59:55.62 JOB84350 00000090 IECTMS9 0749,006204,DDBBJDB ,OUTDD1 ,CATALOG ,0001,S.BACKUP.G0307V00 > >02:59:59.92 00000290 IEA271I ETR TIME OFFSET CHANGES HAVE OCCURRED. > >03:00:02.54 STC05879 00000090 ERB307I III: MONITOR III DATA GATHERER ERB3GINI. INTERFACE BPX1SDD >03:00:02.54 STC05879 00000090 ERB307I III: FAILED. RETURN CODE: 0000 REASON CODE: 0000 > >I only noticed it because we had automation that picked up the ERB307I message. No dumps, no other messages, and nothing in logrec. > >It would be useful if someone else also had this occur so Level-2 had more than a one customer population that asserts something is odd here. I don't like odd. The message should not come out if RC/RSN = 00 but it did so something is not correct. > >If you observe daylight savings time, run RMF Monitor III, and make the time change automatically using an ETR (or not) I would appreciate it if you could check and see if you had this happen and contact me. > Sam, Our procedures say RMF III (RMFGAT) has to be recycled for a time change (either backwards or forwards). This was from past experience and was also documented in the Redbook "S/390 Time Management and IBM 9037 Sysplex Timer". If you didn't recycle RMF III the time in the displays would not change. Anyway... so you are saying that was fixed at some point? We still have some other things that have to be recycled. CA-GSS (ISERVE) has to be recycled for a forward or backward change, JOBTRAC has to be recycled for both.. but has to be left down for an hour in the fall. Datacom needs a command only for spring and for fall can be left up if current enough on your release and the documented procedure is used (see CA web site). CA-Dispatch needs to be recycled also for both.. but you don't have to wait an hour in the fall. That's it for what still left on my list, but that only applies to this shop. 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 ---------------------------------------------------------------------- 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
