Skip to Content

Dual data sets with CONTINUE=YES, STOP=NO, and ARCHIVE=NONE

This topic provides an example of controlling data set switching with no archiving.

The following figure shows that DSN1 and DSN2 each can contain about four hours’ worth of CMRDETL data. The yellow highlighted hours indicate that when data collection last stopped, they had recorded three hours of data. The gray highlighted hours indicate that the data has not been archived because you specified ARCHIVE=NONE. The data in DSN2 was recorded before the yellow highlighted hours. 

Related topic

Detail-data-collection-scenarios


Example of dual CMRDETL data sets with daily data

image2020-4-16_14-2-23.png

When data collection starts for the IBM CICS region, BMC AMI Ops Monitor for CICS determines which CMRDETL was last used. In this case it is DSN1.  Because CONTINUE=YES is specified, recording continues on DSN1.

When DSN1 becomes full, BMC AMI OpsM for CICS determines the next CMRDETL data set and in this example, it is DSN2. BMC AMI OpsM for CICS then determines if the data in DSN2 has been archived.  It is not but because you specified STOP=NO,  the switch is completed, and the unarchived data in DSN2 is overwritten. In this example, all the data in DSN2 is overwritten and no longer available to the online CHIST views.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Monitor for CICS 7.5