<snip> (NO)SETABOOL - If it's unset (default), behaviour as today; if set, then SETA 0 is treated as False, and SETA (anything else) as True? </snip>
Just a point: any option like this might have to be documented for use only when no ISV- or IBM-provided macros are invoked with the new option, if it's possible that a behavioral change could cause the macro not to function as it "always has". I don't know about individual ISVs, but I don't see IBM spending resources to validate that our huge set of macros works with respect to a new option, let alone make changes if something does not work. So you're welcome to use such an option on your own code and with your own macros, but any risk with respect to macros that you don't own would be yours to bear. Peter Relson z/OS Core Technology Design
