TSS7227E UPDATE ACCESS NOT GRANTED received when creating a GDG dataset even though the user has ACCESS(ALL).

Products

• Cleanup
• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware
• Top Secret
• Top Secret - LDAP
• Top Secret - VSE

Issue/Introduction

Description:

A permit for the dataset with .* as the last parameter and ACCESS(ALL) is common to include all generations of the GDG.

EXAMPLE:
TSS PERMIT(user) DSN(GDGDSN.UPDATE.ERR.*) ACCESS(ALL)

The user may then receive:
TSS7227E UPDATE Access Not Granted to Dataset GDGDSN.UPDATE.ERR

Solution:

The dataset in the TSS7227E message is the base GDG. The next generation of the GDG was successfully created. After the successful creation a second call is made to UPDATE the base GDG with the newly created generation. It is this call that fails. The GDG base does not include the .* so therefore the permit for ACCESS(ALL) to DSN(GDGDSN.UPDATE.ERR.*) does not match.

A permit for ACCESS(UPDATE) is needed to the base GDG.

In the example the dataset would be: DSN(GDGDSN.UPDATE.ERR)

If you want to make sure that GDGDSN.UPDATE.ERR is not used as a high level qualifier then the dataset could be in quotes on the permit.

EXAMPLE:
TSS PERMIT(user) DSN('GDGDSN.UPDATE.ERR') ACCESS(UPDATE)

Environment

Release:
Component: AWAGNT