We are planning on creating ALIASs for some of our datasets. How will CA ACF2 handle dataset validations when the datasets are accessed by the ALIAS name?
search cancel

We are planning on creating ALIASs for some of our datasets. How will CA ACF2 handle dataset validations when the datasets are accessed by the ALIAS name?

book

Article ID: 51102

calendar_today

Updated On:

Products

ACF2 ACF2 - DB2 Option ACF2 for zVM ACF2 - z/OS ACF2 - MISC PanApt PanAudit

Issue/Introduction

When accessing a dataset via the dataset alias name CA ACF2 will validate against the original dataset name, not the alias
name.

 

Environment

Release:
Component: ACF2MS

Resolution

When accessing a dataset via the dataset alias name CA ACF2 will validate against the original dataset name, not the alias
name. For example:

  • An ALIAS is created for dataset MY.TEST.DATASET using IDCAMS:

    DEFINE ALIAS (NAME(MY.TEST.ALIAS.DATASET) RELATE(MY.TEST.DATASET))

  • The dataset ALIAS is accessed using IEBGENER by logonid USER001 which has the CA ACF2 logonid TRACE bit set:

    //STEP1 EXEC PGM=IEBGENER
    //SYSPRINT DD SYSOUT=*
    //SYSIN DD DUMMY
    //SYSUT1 DD DISP=SHR,DSN=MY.TEST.ALIAS.DATASET
    //SYSUT2 DD SYSOUT=*

  • The ACFRPTDS report shows the access for the actual dataset name:

    USER001 10.308 04/11 07.44 DATASET TRACE REQ
    IEBGENER VOL=DASD01 DDN=SYSUT1 DSN=MY.TEST.DATASET
    STEP1 VOL= PGM=IEBGENER LIB=SYS1.LINKLIB
    JOB06097 DA-OPN INPUT NAM=TEST USER1 ROL=
    SYSX SRC=A99LO908 UID=OMVSDGRPBBBCUSER001
Powered by Wolken Software