More granular level of tape data retention than just categories

At the host, a user can set more than one retention period for a category/media type for an LPAR. The TS7700 allows only one retention period per Category by design.
The issue is that if a host user modifies the retention period at the host
(maliciously or accidently), the longest retention period for the category must be used at the TS7700 to ensure the volume is not deleted before its time. This causes a side effect where logical volumes are held longer than needed. For instance, if category xC000 has 3 retention periods at
the host (2 weeks, 1 year and 10 years) then all lvols in this category must be held for 10 years on the TS7700 to avoid the case where someone
changes a retention period of one of the 10 year volumes to 1 day and it expires prematurely.
Dual Authentication at the zHost would help this issue from occurring however, with the potential introduction of the ability to have immutable
retention periods, it becomes a problem again since there is no flexibility in choosing multiple expiration times. This item is a request to add the ability to enter volume level retention
periods. This could be done in dataclass along with the LWORM capabilities and as part of immutable lworm retention periods.
Also note that this item should be included as part of the Dual Control mechanism.