JCL LIKE for PDSE Version and MAXGENS

In JCL, the DD LIKE parameter is used to specify the allocation attributes of a new data set by
copying the attributes of an existing cataloged data set.

One attribute it copies is the DSNTYPE parameter, which includes whether the model data set is
a PDS vs. a PDSE. That is, if the model data set is a PDSE, then LIKE=model.data.set is equivalent
to specifying DSNTYPE=LIBRARY.
But now DSNTYPE=LIBRARY has a subfield: version. If the default PDSE version is 1 (as set by
IGDSMSxx PDSE_VERSION), then in JCL to create a PDSE Version 2 you must code DSNTYPE=(LIBRARY,2).

The problem is that LIKE doesn't copy the library version. So if you allocate a new data set by
copying the attributes of an existing PDSE Version 2, then it will allocate it as version 1
(if PDSE_VERSION=1), or vice versa.

This is exacerbated by another issue: DD LIKE does not copy the MAXGENS parameter, which is
closely related to DSNTYPE=(LIBRARY,2). So if you use DD LIKE to copy a PDSE defined with
MAXGENS greater than 0, then the new PDSE will have no MAXGENS: either because it allocates
as DSNTYPE=(LIBRARY,1) with PDSE_VERSION=1, or even if PDSE_VERSION=2, because it doesn't copy
the MAXGENS that was defined on the model data set.

I don't see any other parameter in JCL to remedy this.

Does IBM intend for DD LIKE to be able to model PDSE Version 2 libraries with MAXGENS?

I don't see any changes to DD LIKE in z/OS 2.4.