ACF2 VIO records showing up when LOG is specified in ACFRPTDS PARMs
search cancel

ACF2 VIO records showing up when LOG is specified in ACFRPTDS PARMs

book

Article ID: 259835

calendar_today

Updated On:

Products

ACF2 - z/OS ACF2 ACF2 - MISC

Issue/Introduction

The ACF2 ACFRPTDS report is ran with the following parameters, but the report is showing VIOlations even though the report parameters use LOG. Why is this occurring?

PARMs being used:

//REPORT    EXEC PGM=ACFRPTDS,   
//  PARM=('LINECNT(99999)',     
//        'LIDMASK(TESTUSER)',  
//        'LOG',                
//        'TERMINAL',           
//        'EXTEND')             

Sample output:

1CA ACF2 - ACFRPTDS - DATASET ACCESS JOURNAL        
 DATE 02/13/xx (xx.044) TIME 14.04 LINECNT(99999),LIDMASK(TESTUSER),LOG  
                                                                        
TESTUSER  xx.011 01/11 14.09       DATASET  VIOLATION                                                  

Environment

Release : 16.0

Resolution

Specify TITLE in the PARM input:

//REPORT  EXEC PGM=ACFRPTDS,   
//  PARM=('TITLE(ACFRPTDS)',   
//        'LINECNT(99999)',    
//        'LIDMASK(TESTUSER)',  
//        'LOG',               
//        'TERMINAL',          
//        'EXTEND') 

The TITLE parameter is required. If this parameter is not specified, the report generator uses the first 35 characters in the PARM field of the EXEC statement. If this character string is longer than 35 characters, only the first 35 characters are used. If LOG is part of the PARM field without a TITLE parameter, then it will be used as part of the TITLE and not for report filtering. 

Evidence of this can be seen from the report output where the TITLE of the report should be:

1CA ACF2 - ACFRPTDS - DATASET ACCESS JOURNAL        
 DATE 02/13/xx (xx.044) TIME 14.04 LINECNT(99999),LIDMASK(TESTUSER),LOG