SMF OVERLAPS DATA ALREADY IN INDEX

book

Article ID: 131974

calendar_today

Updated On:

Products

CA JARS CA JARS Resource Accounting CA JARS SMF Director

Issue/Introduction

We have scheduled batch job in our system to extract SMF Records, sometimes job ends with MAXCC=4 due to following warning message which triggers an incident for us:

CAF2218I SMF DATA USING CONFIGURATION TETA IS BEING PROCESSED
CAF2417W SMF DATA FOR TETA 04/13/2019 4:32:19 OVERLAPS DATA ALREADY IN INDEX

Although, it is not abnormal, we would like to know if there is any way to overcome this problem.

Could you suggest a permanent solution for this scenario.

 

Environment

This can occur with any release of SMF Director.

 

Resolution


To set the OVERLAP option to 10 seconds as you are suggesting, you can take your existing SMF Director configuration JCL and modify the OPTIONS statement to add an OVERLAP(10) operand to the statement and recompile. All compilations in SMF Director are additive, so there will be nothing lost or changed, and this way you will have the operand value set in your compilation for later. 

Alternatively, you can compile the OPTIONS statement by itself, although this is not recommended since if you need to rebuild the SCDS in the future, you won't have the OVERLAP set in your configuration JCL. 

What I would recommend you do for this is as follows: 

1) Take a BACKUP of the SCDS file to ensure that if something goes wrong with the job, the SCDS can be restored. 

2) Recompile your current configuration definitions with the new OVERLAP(10) operand on the OPTIONS statement. 

If everything goes as expected, no future dumps will be tagged as overlapping unless there is an overlap of 10 seconds or more in the time ranges on the dumps.