(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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to