GSVX252E trying to initialize sysview

Document ID : KB000013600
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

Why am I getting

GSVX252E SYSVIEW subtask could not be attached -

 RC= <code>reason code 30 not authorized to create or update subsystem.

Answer:

The error is due to not having the correct security permissions defined.

Installation Enhancements - 

As part of migrating to the use of the GSVXSCFG DDname in the server address spaces, it 

became necessary to add additional security measures. 

 

 These measures prevent unauthorized 

users from overriding configuration options. This release now requires that all of the                                  

CA SYSVIEW® Performance Management server address spaces have access to the following 

resource: 

 

ESM SAF Class SAF Entity Access 

ACF2 SYSVIEW SV.CREATE.SSID.<smfid>.<ssid> READ 

RACF FACILITY SV.CREATE.SSID.<smfid>.<ssid> READ 

TSS CAGSVX SV.CREATE.SSID.<smfid>.<ssid> READ 

 

<smfid> is the SMF ID of the system where the server address space is executing. 

<ssid> is the Subsystem ID that was specified for the SSID= parameter during installation. 

The default SSID is GSVX. 

 

Optionally define the SAF Entity as a generic resource in your External Security Manager: 

SV.CREATE.SSID.* 

The server address spaces include: 

SYSVIEW Main Services Address Space (SYSVIEW) 

SYSVIEW User Interface Address Space (SYSVUSER) 

SYSVIEW Auxiliary Services Address Space (SYSVAUX) 

 

You should restrict update access to: 

The procedure library containing the startup JCL for any of the server address spaces.

The System Configuration data set pointed to by the GSVXSCFG DDname. 

Starting a server address space that does not have access to this SAF resource will fail. 

 

 

Additional Information:

Link to documentation https://docops.ca.com/ca-sysview/14-2/en/security/interfacing-with-external-security/saf-requirements