How CICS PA selects cyclic SMF files for reporting
You cannot report on a mix of cyclic SMF files with and without origins. If a system contains some cyclic SMF file definitions with origins and some without, then you must either exclude the files with no origin, or exclude all of the others. CICS PA does not select excluded files for reporting.
If you exclude the files with origin values, then CICS PA selects all of the files with no origin, regardless of the requested reporting period.
Otherwise, CICS PA calculates a "from" date and a "to" date for each file, indicating the date range of its SMF records. If this range overlaps or falls entirely within the requested reporting period, then CICS PA might use this file, depending on whether other files also meet this requirement. If a sequence of several files covers the same required date range, without gaps, as a single file, then CICS PA uses the sequence of files instead of the single file. CICS PA selects the combination of files that result in the least gap in data, without any overlaps. This ensures that, while a report can contain gaps, it will never contain duplicate data.
CICS PA calculates "from" and "to" dates based on the origin, interval, and DISP values for each cyclic SMF file. The following table shows the allowed combinations of origin, interval, and DISP, and the resulting "from" and "to" dates.
Origin | Interval | DISP | From date | To date |
---|---|---|---|---|
DAY | 1 | MOD | Today | |
OLD | Yesterday | |||
day of week | WEEK | MOD | If day of week is
today, then the "from" date is today. Otherwise, the "from" date is the previous occurrence of that day of the week. |
"From" date + (interval -
1 day) For example, for an interval of WEEK: "From" date + 6 days |
OLD | As for MOD, but one week prior. For example, if day of week is Friday, and today is Monday, then the "from" date is not the Friday just passed, but the Friday before that. |
|||
yyyy-mm-dd |
DAY |
MOD | If the range of dates from the origin to "origin
+ interval" includes today, then the "from" date is the origin. Otherwise, step the date range forwards one interval at a time until the date range includes today. The "from" date is the start of that date range. |
|
OLD | As for MOD, but one interval prior. | |||
0 | Not applicable | Origin | Today | |
****-mm-dd See Origin values for data set names with symbolic variables for other allowed values. |
Any | MOD | Origin (with current year in place of ****) | "From" date + (interval - 1 day) |
OLD | One interval before the origin | |||
CDATE |
DAY |
Not applicable | File creation date (plus or minus nnn days) | "From" date + (interval - 1 day) For a GDG, only the "to" date of the latest generation is calculated in this way. For earlier generations, the "to" date is determined by the "from" date of the next generation. |
NONE | Not applicable |
Origin values for data set names with symbolic variables
Table 1 shows the origin values with asterisks that are allowed if you do not use symbolic variables to specify the data set name of the SMF file. If you use symbolic variables, then there are many more allowed combinations of origin values with asterisks: you use asterisks in the origin value to match the symbolic variables in the data set name. For example (this is not a comprehensive list of the combinations):Data set name | Origin |
---|---|
SMF.DAILY.D&YY.&MM.&DD..SAVE | 20**-**-** |
SMF.DAILY.D&MM&DD | ****-**-** |
SMF.DAILY.J&DDD | ****-*** |
SMF.DAILY.D&DD | ****-**-** |
SMF.MONTHLY.M&YY&MM | 20**-**-dd |
SMF.MONTHLY.M&MM | ****-**-dd |
SMF.A&YYYY | ****-ddd |
SMF.A&YY | ****-mm-dd |
SMF.D&YYYY&DDD | ****-*** |