I can only say "I am astonished" that someone would code based on the presence of a field name. We have every right to define fields in any level of macros that are convenient.
This will almost certainly not be changed. For what it's worth, you can probably use SYSSTATE_OSREL, created via SYSSTATE TEST as of z/OS 1.8 (and shipped also into JBB77S9 and JBB772S) to indicate the release of the macro. If SYSSTATE_OSREL has no value, then your old check will probably work (no guarantees). If it has a value, then consider using it. This issue really has nothing do with the APAR, which is hiper, and refers to the fact that the bit CVTZOS_010700 / CVTZOS_V1R7 / CVTH7720 (they're all the same bit) is incorreclty on, so any runtime determination looking for "am I on z/OS 1.7 or later" would be misled. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
