ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

CA View - Question on CVDEJCL member HBRMMETX (View Metrics)

book

Article ID: 200652

calendar_today

Updated On:

Products

Deliver View

Issue/Introduction

The client is using SARINIT SMFTYPE=240, the SMF records are being generated, however the Metrics job appears to not be using them.

These records are being used for the date range: 

SMFTYPE=240,DATE=090001-098365,TIME=0000-2359,RPT=USER
SMFTYPE=240,DATE=090001-098365,TIME=0000-2359,RPT=ACCS
SMFTYPE=240,DATE=090001-098365,TIME=0000-2359,RPT=LOAD
SMFTYPE=240,DATE=090001-098365,TIME=0000-2359,RPT=CHNG

Should something else be used?

 

Environment

Release : 12.2

Component : CA View

Resolution

In using the View Metrics, the date ranges in the control statements are as follows:

. cyyddd-cyyddd

. . where:
. . . c - century - 0 is for 1900s, 1 is for 2000s
. . . yy - last 2 digits of year
. . . ddd - Julian day

. . example: 090001-098365
. . . c - century - 0 ==> 1900s
. . . yy - year - 90 ==> 1990
. . . yy - year - 98 ==? 1998
. . . ddd - day - 001 is for January 1
. . . ddd - day - 365 is for December 31 or December 30, depending on a leap year.

What will appear in any resulting reports will be based on data that was captured in the SMF dump file.

Each View database should have a unique SARINIT SMFTYPE=nnn parameter.

When adding or changing the SMFTYPE=nnn parameter, it is a requirement to recycle the related SARSTC task.