Open mainframed opened 7 months ago
The question is, do we still have a need for that? In the end, we will have rolling releases (sort of)
I'm fine with that, but how do you envision the BREXX PDS naming convention?
BREXX.CURRENT.RXLIB/SAMPLES/JCL
or something like BREXX.RXLIB
? Since the new build engine dynamically creates those dataset names at build time we can really call it anything you want.
On the one hand I like the BREXX.RXLIB
convention, its short and simple, but I also like the naming convention of BREXX.<version>.RXLIB
, etc. That way you know exactly what version you have installed at a glance but then we lose the rolling release.
It would be nice as part of the install process if an alias was created to the various PDSs that are installed.
I.e.
BREXX.CURRENT.RXLIB
-->BREXX.V2R5M3.RXLIB
etcThis could be done in the JCL that unxmits the various libraries (delete the alias and make a new one, or provide a seperate step to make the aliases if desired). This way the TSO clist or other JCL would only have to referece
BREXX.CURRENT.XXPDSXX
instead of having to update all the JCL etc.