Hi Victor,

Are you perhaps recording Type 19 records?  If not why don't you post your SMF 
parms.

Here is our SMFPRMxx and like most sites I expect we exclude type 19.  IIRC 
this can still cause delays switching SMF data sets.  z/OS R6 improves the 
handling of SMF buffers considerably and makes it practical to allow SMF more 
than 128M. 

   SYS1.PARMLIB(SMFPRM00) - 01.10                         CHARS 'NOTYP
===>                                                          Scroll =
******************************** Top of Data *************************
ACTIVE                          /* ACTIVE SMF RECORDING             */
DSNAME(SYS1.&SYSNAME..MAN1,                                           
      SYS1.&SYSNAME..MAN2,                                            
      SYS1.&SYSNAME..MAN3,                                            
      SYS1.&SYSNAME..MAN4)                                            
NOPROMPT                        /* DO NOT PROMPT OPERATOR           */
REC(PERM)                       /* TYPE 17 PERM RECORDS ONLY        */
MAXDORM(1500)                   /* WRITE IDLE BUFFER AFTER 30 MIN   */
MEMLIMIT(4G)                    /* ALLOW USE OF STORAGE ABOVE BAR   */
BUFSIZMAX(512M)                 /* 4X DEFAULT IBM BUFFERS           */
STATUS(003000)                  /* WRITE SMF STATS AFTER 1 HOUR     */
JWT(0015)                       /* 522 AFTER 15 MINUTES             */
SID(&SYSNAME)                   /* UNIQUE TO EACH LPAR IN SYSPLEX   */
LISTDSN                         /* LIST DATA SET STATUS AT IPL      */
SYS(NOTYPE(4,5,19,20,34,35,40,69,120),INTERVAL(010000),NODETAIL,      
    EXITS(IEFU83,IEFU84,IEFU85,IEFACTRT,IEFUTL,IEFUSI,IEFUJI,IEFU29)) 
 SUBSYS(STC,EXITS(IEFUSI,IEFU29,IEFU83,IEFU84,IEFU85)),               
 SUBSYS(TSO,                                                          
   EXITS(IEFACTRT,IEFUJI,IEFUSI,IEFUTL,IEFU29,IEFU83,IEFU84,IEFU85))  



        Best Regards,

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

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

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of 
Víctor de la Fuente
Sent: Monday, January 16, 2006 8:55 AM
To: [email protected]
Subject: How SMFDUMP works?

Hi all!
I was wondering which is the process of clearing SMF datasets. We are having a 
problem, and I'd like to know the process to see which is that problem.

When one SMF dataset is full, it should get into DUMP REQUIRED state to be 
cleared. The problem we are having is that, sometimes (randomly in time) the 
dataset stays in CLOSE PENDING for several minutes). If the charge of the 
system is high, that time is plenty to let SMF fill up all of its 128 MBs, so 
we start to lose data. Could some of you tell me when the dataset changes its 
state, and why?

Thank you very much!!!!
====================
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