Xmanager access required over detector datastore
Article ID: 76576
Updated On:
Products
CA Bind Analyzer for DB2 for z/OS
CA SQL-Ease for DB2 for z/OS
CA Sysview Performance Management Option for DB2 for z/OS
CA Plan Analyzer for DB2 for z/OS
CA Subsystem Analyzer for DB2 for z/OS
Issue/Introduction
INSUFFICIENT ACCESS AUTHORITY 353 FROM DB77.DB2TOOLS.CA.** (G) 353 ACCESS INTENT(CONTROL) ACCESS ALLOWED(UPDATE )
when initializing data collection "5. Initialize SSID collection", I get the following error 10.10.06 STC13634 ICH408I USER(DB00MON ) GROUP(DBPCALA ) NAME(DB2 TASK /JJOR 353 DB77.DB2TOOLS.CA.DETDATST.DTR0003.D770 CL(DATASET ) VOL(SYS 353 INSUFFICIENT ACCESS AUTHORITY 353 FROM DB77.DB2TOOLS.CA.** (G) 353 ACCESS INTENT(CONTROL) ACCESS ALLOWED(UPDATE ) whereas the doc says xmanager only requires read/update on the detector datastore https://docops.ca.com/ca-detector-for-db2-for-z-os/19-0/en/getting-started/product-setup/authorization-and-security/mvs-authorization-requirements why does xmanager require control here?
when initializing data collection "5. Initialize SSID collection", I get the following error 10.10.06 STC13634 ICH408I USER(DB00MON ) GROUP(DBPCALA ) NAME(DB2 TASK /JJOR 353 DB77.DB2TOOLS.CA.DETDATST.DTR0003.D770 CL(DATASET ) VOL(SYS 353 INSUFFICIENT ACCESS AUTHORITY 353 FROM DB77.DB2TOOLS.CA.** (G) 353 ACCESS INTENT(CONTROL) ACCESS ALLOWED(UPDATE ) whereas the doc says xmanager only requires read/update on the detector datastore https://docops.ca.com/ca-detector-for-db2-for-z-os/19-0/en/getting-started/product-setup/authorization-and-security/mvs-authorization-requirements why does xmanager require control here?
Environment
z/os DB2
Resolution
During the dataset initialization of the Detector datastore dataset, the GENCB macro uses MACRF of CNV, which provides access to the entire contents of the control interval rather than to the individual data record. So to initialize the Detector Dataset successfully, the user needs Control access for the VSAM dataset.
Feedback
Yes
No
Powered by
