Sysview fails to start with error GSV2314E - Missing Security Dataset - CNM4BSEC

Products

• SYSVIEW Performance Management

Issue/Introduction

Sysview not coming up after Maintenance, CNM4BSEC Missing

Sysview fails to start after maintenance.

• Error message: GSV2314E (MAIN) GSVXDASR ALLOCATE failed. F1 DSCB not found
• Error message: GSVX205E (MAIN) Nucleus load failed, reason 24 set up failed for system configuration
• Error message: GSVX572E (MAIN) MAIN task initialization failed

Cause

The security dataset specified in the configuration (e.g., *.CNM4BSEC) is missing or has been deleted from the volume.

Resolution

1. Verify the dataset name in the GSV2318I message immediately preceding the GSV2314E error.

Option - 1 

1. Work with your Storage Administration team to recover the deleted dataset or identify a valid backup.

Option - 2 (If Storage team is not able to recover the dataset).

 a. Find the INST0050 member located in your SYSVIEW SAMPJCL data set.  (You can also use the Sysview 16.0 security dataset in this job to convert it into 17.0 security dataset).

 b. Edit the SYSUT1 DD statement to specify the name of your existing security data set (e.g., CNM4BSEC).

 c. Run the Job.

Note :   Once the SYSVIEW product is initialized, you will need to update the security authorizations for any new command and display fields introduced in the new release. 

3. If a new dataset is used, update the GSVXGSVX configuration member to point to the new dataset name.

4. Restart SYSVIEW.

Additional Information

Convert the Security Data Set (INST0050)

https://techdocs.broadcom.com/us/en/ca-mainframe-software/mainframe-essentials/sysview-essentials/17-0/installing/complete-the-configuration-tasks/configure-sysview-manually/convert-the-security-data-set-inst0050.html

Best Practices:

• Maintain separate security datasets for production and test regions.
• Ensure regular backups of all security datasets to prevent data loss.