> > When there is another architecture levelset so that it makes sense for us > to do that. > As far as I know, no z/OS macros generate different code based on machines > newer than the most recent architecture levelset. > > That is partly why I wrote that SYSSTATE ARCHLVL=xx is intended for > notifying z/OS macros. > > If there is a business need to provide such support in advance of an ALS, > then submit an RFE and make your case. > Providing such support in the next release after a machine ships would be > no problem; providing such support rolled back to all supported releases > whenever a machine ships requires justification. > > Peter Relson > z/OS Core Technology Design >
I did a quick Google search on "architectural level set" in ibm.com. I didn't see anything which explains when something is considered to be an architectural level set. Obviously not just new facilities because the z14 has a lot of new stuff over the z12. Or does this concept relate more to the software side than the hardware side? I am guessing the latter. I am guessing that when an ALS is established, that is a "cut off" point where the software requires at least that level of hardware to execute due to use of specific instructions or facilities which are not in previous previous versions of the hardware. IOW, -- This is clearly another case of too many mad scientists, and not enough hunchbacks. Maranatha! <>< John McKown
