If you are writing code for only your own shop, this version of SYSSTATE is pretty handy, as it keeps up with your system:
SYSSTATE OSREL=SYSSTATE,ARCHLVL=OSREL For software to be distributed elsewhere, then don't do that; unless you're willing to bet all targets are always equal or greater than your z/OS level. sas On Mon, Feb 11, 2019 at 11:02 AM Peter Relson <[email protected]> wrote: > (Everyone should do this) > > Help the poor macros out. Tell them via SYSSTATE OSREL and ARCHLVL what > the macros are allowed to assume. > Unless you like lousy code. > > The XM services were written when non-stacking PCs were the only thing > available and the interface for non-stacking PC requires various hoops to > be jumped through. But those PC's were changed to stacking many releases > ago (z/OS 1.6). > > For the most part we try not to assume things about what release you might > be running your code on, and thus the default remains to expand the way it > originally did. But you almost always know better. Share that information. > Unless you like extra STM, ESAR, SSAR, LM in your expansions. At a > minimum, pick the oldest release your code might run on. If that oldest > release is older than z/OS 1.6, perhaps you could consider changing your > business model. > > Peter Relson > z/OS Core Technology Design > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- sas ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
