How long will data in MVJE ZCONREQ view stay?

Version 1
    Share This:

    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


    APPLIES TO:

    MainView for Java Environments version 3.1.00.



    QUESTION:

    How long will data in MVJE ZCONREQ view stay? Is there an option we can specify?


    ANSWER:

    ZCONREQ data is extracted from SMF type 123 records and written into NGL logsets.  If there is a new SMF type 123 record, MVJE PAS will intercept it, parse it, build a record and write it into NGL logset.

    The logset with Z character would be the logset name for z/OS Connect EE data, this can be seen in the BMCNGL59204I message, see an example below:

    BMCNGL59204I 10.4.00 CLIENT CONNECTION SUCCESSFUL TO NGL(MJGT) DBC(MJDC) LOGSET(JEscZ_ss )

    The attributes are defined in MJEINIxx and the MJELGZxx member.  

     
    As for the length of time the data is kept, it is dependent on the allocation of the logset, this is defined in MJELGZxx member, you can view the parameters in this member in the PASPARM and PARMEDT view by hyperlinking on the member name. 
      
     
    How long the data is retained is controlled by these 4 parameters:  
     
      1) RETENTION                                                                        
    The number of days that the log set should span. RETENTION controls both the number of log files that will be used to record data and the number of log files that will be allocated during a log set start.

    NGL uses the RETENTION specification to insure that enough log files are     allocated at log set startup to cover the RETENTION period. The number of log files allocated will be DSMIN at the minimum and up to the greater of DSMAX or the actual number of log files that have been added to the NGL registry. If more log files are available from the NGL registry after the RETENTON period is met and DSMAX has not been reached, then the additional log files will be marked as candidates and will be allocated as more log files are needed to maintain the RETENTION period.

    For example, if the log set needs to span a time frame of 7 days, then RETENTION should specify 7. NGL will adjust the number of data sets available and active based on the DSMAX and RETENTION values when a data set becomes full and a log file switch is required. If the RETENTION criterion is not met and DSMAX has not been reached, then an additional data set will be allocated and used to record data. Additional log files will be allocated until DSMAX is reached to meet the RETENTION period
      specified.
      
    Default: 10

    2) SPACE
    SPACE specifies the amount of DASD space to allocate for a  data set in the log set.  The SPACE specification is in megabytes.  
        
                                                 
    Default: 10

    3) DSMAX                                                    
    specifies the maximum number of data sets that will comprise the log set.                                            
    DSMAX is used in conjunction with RETENTION to control the number of data sets allocated.  If RETENTION is not specified, DSMAX is set to DSMIN. 
    DSMAX must be at least one greater than DSMIN.       
                

    Default: 5

    4) DSMIN                            
    specifies the minimum number of data sets that will comprise the log set.        
                           

    Default: 2    
                                       
      

     


    Article Number:

    000170771


    Article Type:

    FAQ/Procedural



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