Hi Mark,

We recycled last year because of OA19062 but having the PTFs applied did
not include a recycle of RMF in our procedures this year.  I don't know
when it changed but it has been a while I thought.  

APAR Identifier ...... OA19062     Last Changed ........ 07/02/02
 RMF MONITOR I OR RMF DISTRIBUTED DATA SERVER (DDS):
 HIGH CPU USAGE AFTER TIME CHANGE

 Symptom ...... LP LOOP              Status ........... CLOSED  PER
 Severity ................... 3      Date Closed ......... 07/01/15
 Component .......... 566527404      Duplicate of ........
 Reported Release ......... 705      Fixed Release ............ 999
 Component Name RMF                  Special Notice
 Current Target Date ..07/01/26      Flags
 SCP ...................
 Platform ............

 Status Detail: SHIPMENT - Packaged solution is available for
                           shipment.

 PE PTF List:

 PTF List:
 Release 705   : UA31745
 Release 708   : UA31746
 Release 720   : UA31753
 Release 730   : UA31754

        Best Regards, 

                Sam Knutson, GEICO 
                System z Performance and Availability Management 
                mailto:[EMAIL PROTECTED] 
                (office)  301.986.3574 
                (cell) 301.996.1318 
             

"Think big, act bold, start simple, grow fast..." 



-----Original Message-----

So looking at a sandbox where RMFGAT was not recycled, I do see the
same messages:

03.00.00 STC40593 ---- SUNDAY,    09 MAR 2008 ----

          
03.00.00 STC40593  ERB803I III: MONITOR III DATA SET SUPPORT TERMINATED

          
03.00.01 STC40593  ERB307I III: MONITOR III DATA GATHERER ERB3GINI.
INTERFACE BPX1SDD 
03.00.01 STC40593  ERB307I III:     FAILED. RETURN CODE: 0000 REASON
CODE:
0000       
03.00.01 STC40593  ERB105I III: DATA GATHERER ACTIVE

          

And the time looks fine in the panels.

So this was fixed.   When? Was it on a release boundary or there an
APAR? 
Maybe it was this APAR in 2002:

  APAR Identifier ...... OW52129      Last Changed ........ 02/02/04
  VARIOUS RMF PROBLEMS AT MONITOR III DATASET SUPPORT.

This fixed affected z/OS 1.2 and lower systems.  Even though the z/OS
1.2 level of RMF was still used in z/OS 1.3 and 1.4, the fix was
included
at GA (I assume from looking at the APAR). 

I'll have to get our procedures updated to remove the need to recycle
RMF at the time changes.

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
====================
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

Reply via email to