What is Best Practice to generate MainView Batch Reports?

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 Infrastructure



    QUESTION:

     
        
    • What is Best Practice to generate MainView Batch Reports?
    •  


    ANSWER:

    The panel “Generate MainView Batch Reports JCL” gives you 16 lines to enter commands – but each line has a limit of 66 characters.

      --------------------- Generate MainView Batch Reports JCL ---------------
    Command ===>                                                            
                                                                            
    JCL Member name        ===> MVBATCH1  Replace (Y/N)?  YES               
    JCL Member Description ===> Example                                  <===
    Report format:         ===> ASIS      (ASIS or CSV)                     
    Lines/Page:            ===> 60        (ASIS format only)                                                                                        
    …                                                                      
     PRODUCT ===> MVCICS   (Prompt = PF4)                                   
     ===> CON CAGA;CREGION;TIME * *  4H;INCL TIME;SORT JACT$INT.A)          
     ===> CON ALL PLEXMGR;ALARMS;TIME * * *)                                
     ===> CON ALL PLEXMGR;ALHIST)                                           
     ===> CON BMCB ICAP;LOGRALL;TIME * * 24H;WHERE LOREEVTC = 'DC*'         
     
       ===> …                                                                   
      
    The common sequence for composing commands is:  
       
    1. context
    2.  
    3. product (for command line one the product usually is determined by the initial prompt)
    4.  
    5. view-name
    6.  
    7. determination time frame (TIME)
    8.  
    9. selection criteria (WHERE)
    10.  
    11. additional inclusions (DATE, TIME, SYSTEM, TARGET)
    12.  
    13. SORT criteria
       Only the specification of the initial product and the initial view-name is mandatory.
    The behavior is comparable to using the same commands as in a MainView online terminal session.
      
      If you enter the following commands separated by “;” the output is produced once:          
      
      ===> SYSOVER ;TIME *-1 23:59 1D;INCL DATE;INCL TIME   
      
      If you enter the following commands in separate lines the output is produced multiple times:                    
      
      ===> SYSOVER
    ===> TIME *-1 23:59 1D
    ===> INCL DATE
    ===> INCL TIME   
      
    If the 66-character limit is not sufficient to enter all the necessary commands and you don’t want to produce the output more than once, there is one more option:
    Create a user customized view with the desired attributes
      
       
    • Selection criteria (WHERE)
    •  
    • Additional inclusions (DATE, TIME, SYSTEM, TARGET)
    •  
    • SORT criteria
       and then call the customized view.  
      ===> $LPARCAP;TIME *-1 23:59 1D  
       Hint:
    Another way to circumvent the limit of 66 characters is modifying the generated JCL statements. Example:   
      SET BATCMD = +
    &STR(ALHISTR; +
    SETS LOGNUMREC 3000;SETS LOGSEARCHDIR 'FWD';+
    SETS LOGSTARTDATE 2019/03/25;SETS LOGSTARTTIME 00:00;+
    SETS LOGENDDATE 2019/03/25;SETS LOGENDTIME 23:59)
      
    Here are some further examples of how to use the MVBATCH Utility:  
      PRODUCT ===> MVMVS    (Prompt = PF4)                              
    ===> SYSOVER;TIME *-1 23:59 24H;INCL TIME;INCL DATE;SORT JACT$INT.A       
    ===> CSAREM;TIME * * *;WHERE CDRECSAU > 0;SORT CDRECSAU.D
    ===> CON ALL MVCICS;CREGION                    
    ===> CON SSP1 MVAO;AOEVENTS;WHERE AA20CNT >10000                  
    ===> CON SYSP CMF;JCPU;TIME 22MAR2019 06:00 12H;WH ASGNAME = 'HSM'          
    ===> CON SYSP CMF;JCPU;WH ASGNAME = 'HSM';SORT JACT$INT.A
    ===> CON SYSP PLEXMGR;ALARMS;TIME * * * 
      
      

     


    Article Number:

    000166125


    Article Type:

    FAQ/Procedural



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