What configuration steps are necessary to enable MainView for Java Environments to access and exploit SMF data?

Version 2
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    MainView for Java Environments


    COMPONENT:

    MainView for Java Environments



    QUESTION:

    What configuration steps are necessary to enable MainView for Java Environments to access and exploit SMF data?

     


    ANSWER:

    Currently MainView for Java Environments uses three different SMF records to provide details of specific JVM types:
     
    SMF29                 -             IMS-Message Region

                                                  IMSBMP - IMS batch region with java 
      
      IMSJBP - IMS batch java only region     
      IMSJMP - IMS java only message region   
      IMSMSG - IMS message region with java  
       SMF121              -             JZOS - Java started using the JZOS launcher
    SMF123              -             ZCON - z/OS Connect EE

    1. Global Customization z/OS:
    Make sure the requested SMF-types are collected
    (i.e. not suppressed by SMFPRMxx-member of SYS1.PARMLIB)  
       
       2. Global Customization MVJE:
    MJEINIxx:
    SMF29=YES
    SMF121=YES

    3. Double check that appropriate exit SMF84 is active:
     
     -D PROG,EXIT,EXITNAME=SYSSTC.IEFU84,DIAG      
     
    The name will be MJESmjess , JCOM will show as parameter 2 in the display.                                    
       
              CSV464I 07.16.58 PROG,EXIT DISPLAY 597                                             
              EXIT SYSSTC.IEFU84                                                                 
              MODULE    STATE EPADDR    LOADPT    LENGTH    JOBNAME   PARAM                      
              CZAG84X0    A   A8650360  00000000  00000000  *                                    
              STRBGMS3    A   B1EF7010  00000000  00000000  *                                    
              IEFU84      A   87F75798  00000000  00000000  *                                    
              ERBDSSMF    A   876A67A0  00000000  00000000  *                                    
              SGPERU84    A   BA3E3000  00000000  00000000  *                                    
              MJESSN32    A   A6643270  00000000  00000000  *          3 {JCOM                 
       
                   
       4. Individual Customization JVM:
    Every individual JVM must have SMF recording specified.
       
       
    1. 4.1 IMS Message Region             In the DFSENVXX member
      
      JLEOPT=N 
      SMFINTERVAL=<nnnn> (milliseconds)
      
        
      
       
    1. 4.2  JZOS                                       
      
       
    • For JZOS to use /etc/profile, you need to add a line to //STDENV input (which may or may not be the default) . /etc/profile
    •  
    • You can add those same lines to an individual jzos STDENV,  instead of . /etc/profile also
          
         JZOS version 7.1 or later
      
       
       JZOS_JVM_SMF_LOGGING=true  
       export JZOS_JVM_SMF_LOGGING 
      
      
            
      JZOS version 8.0 SR1     
      
       
       HJV_JZOS_JVM_SMF_LOGGING=true  
       HJV_JZOS_JVM_SMF_THREADS=true  
       HJV_JZOS_JVM_SMF_LOGGING_INTERVAL=n (seconds)  
       export HJV_JZOS_JVM_SMF_LOGGING  
       export HJV_JZOS_JVM_SMF_THREADS  
       export HJV_JZOS_JVM_SMF_LOGGING_INTERVAL  
       export HJV_JZOS_JVM_SMF_THREADS_NATIVE_ID =true 
      
          
       
    • Do not include both     
           
      • HJV_JZOS_JVM_SMF_LOGGING and
      •    
      • JZOS_JVM_SMF_LOGGING
      •    
      • you will get an error and JZOS will fail
      •   
      
       
    1. 4.3 zOS Connect EE               in server.xml
      
      <!-- Audit interceptor configuration -->                                                                   
      <zosconnect_auditInterceptor id="auditInterceptor" sequence="1"/>                                          
                                                                                                                
      <!-- Interceptor list configuration -->                                                                    
      <zosconnect_zosConnectInterceptors id="interceptorlist1" interceptorRef="auditInterceptor"/>               
                                                                                                                
      <!—Add global interceptor list to zosconnect -->  
      <zosconnect_zosConnectManager                                                                              
          globalInterceptorsRef="interceptorlist1"                                                               
          setUTF8ResponseEncoding="true"/>                                                                     
      
        
                                                                    
       5. Finally, you have to ensure that the JVM has the appropriate authority to produce SMF records:
     
    PERMIT BPX.SMF CLASS(FACILITY) ACCESS(READ) ID(userid)
     
    Lookout for possible error messages like this:
     
    ICH408I USER(xxxxxxxx) GROUP(yyyyyyyy) NAME(zzz)
                   BPX.SMF CL(FACILITY)
                   INSUFFICIENT ACCESS AUTHORITY
                   ACCESS INTENT(READ     ) ACCESS ALLOWED(NONE    )

     
     
     
     
      

     


    Article Number:

    000169568


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles