Use Absolute Generation and Version Numbers for DVM GDG Dataset Validation

The Scenario:

Currently for GDG Dataset Validation when creating a Virtual Table in DVM Studio, DVM uses the relative gdg name such as HIGH.LEVEL.QUALIFIER (0)) rather than using the absolute gdg name such as HIGH.LEVEL.QUALIFIER.G0001V00.

Security rules for gdg datasets control access to HIGH.LEVEL.QUALIFIER.**.

Security rules for non-gdg datasets with the same HLQ as a gdg dataset control access to

HIGH.LEVEL.**

HIGH.LEVEL.QUALIFIER*.**

Users may have access to a gdg such as HIGH.LEVEL.QUALIFIER.G0001V00 but NOT to non-gdg HIGH.LEVEL.QUALIFIER.LOWQUAL

The Problem:

DVM Dataset validation for gdgs checks access to HIGH.LEVEL.QUALIFIER(0) but this does not match the security rule of HIGH.LEVEL.QUALIFIER.** which controls access to the gdg.

To accommodate the DVM security check for gdgs, the user needs access to HIGH.LEVEL.QUALIFIER*.** but this security rule controls access to non-gdgs as well which the user may not be authorized to access.

Current workarounds:

To accommodate the DVM security check for gdgs, users need access to HIGH.LEVEL.QUALIFIER*.** which is a less specific rule that opens up access to datasets above and beyond the intended gdg dataset.

Proposed solutions:

When performing dataset validation in DVM Studio for gdg datasets, check security access to the absolute gdg name, HIGH.LEVEL.QUALIFIER.G0001V00, instead of checking access to the relative gdg name, HIGH.LEVEL.QUALIFIER (0).

The Benefits/Value:

Checking access to the absolute gdg ensures a more accurate check against the specific gdg name rather than a general high level qualifier name that could match other non-gdg datasets.