VTOC SCAN datasets in MainView SRM - is there a a way to limit the number of non-master VSCAN datasets created?

Version 1
    Share:|

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


    PRODUCT:

    MainView SRM Reporting


    APPLIES TO:

    MainView SRM Reporting - all supported versions



    QUESTION:

    I can see in our SVOS output that every time we run a VTOC SCAN we create a dataset. For example:

    SVO5001I VTOC SCAN STARTED 
    SVO5002I VTOC SCAN COLLECTION DATA SET: hlq.HIST.PER.SMVSCF00.D190509.T063000 
    SVO5003I VTOC SCAN ENDED ON A NON-MASTER. RC=04, REASON=INCOMPLETE DATA SET STATISTICS 

    I can see we have 37 of these output datasets, but I can't see where we control the number of these datasets - is it in some parm member?
    Or if not, can they safely be deleted with automation perhaps? 
     


    ANSWER:

    According to the online manual - https://docs.bmc.com/docs/display/MVSRM79/VTOC+scan+processing - you have a choice between using one Master VSCAN dataset or many individual ones.
    So one solution to your problem would be to use the Master instead. Using the master is the default unless someone at your installation has changed it.

    If you don't wish to use a Master dataset, older copies of the individual non-master SMVSCF00 datasets may safely be deleted with automation.

    We know of no way to control the number of these datasets that are retained. 

    Keep in mind that the data being reported is based on the parameters set up in the SMVSCFxx parm member. If they have container VSCAN datasets that are being generated by different parm members, the data may not be the same in all the datasets. 
    The WBVTOC view will show you from which SMVSCFxx parm member(s) the container dataset is being generated.
    You may want to display the contents of the SMVSCFxx parm member(s), by using line command "B", to determine what data is being gathered.
    If there are no exclusions being done, and RECORD_TYPE=D, then all data is being gathered.  


    We don’t have a benchmark that we recommend for how many of these files you shoudl keep. It depends on how much history you want to keep.

    You could alternatively set up the datasets to be migrated by HSM (or similar archiving product). The datasets would show up in the WBVTOC view as being at ML1 or ML2 level, but could be easily recalled as needed.
     


    Article Number:

    000168208


    Article Type:

    FAQ/Procedural



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