As a guy who has wrestled with this sort of question as a lead ISV developer
let me share my viewpoint.
Yes, I agree with @Peter and @Mark's general approach: decide how early a
release of z/OS (or z/VM or z/VSE, if that's your thing) you are going to
support -- presumably the oldest release th
We're actually using OPTABLE(Z12). Honestly, I'd rather the assembler fail
than have a customer get some kind of program exception because they didn't
have the right hardware (or feature). I can justify Z12 easily so that's
why we have it set in the configuration.
*Mark*
On Wed, May 15, 2024
PS. Sorry, forgot to say. I had to install PTF PH39324 to get LFI recognized
with OPTABLE(ZSA), which, from your post, seems to be what you're using
(apologies for the noise if I misread it):
https://www.ibm.com/support/pages/apar/PH39324
Mark,
You may find that the LFI instruction is present on the machine. (I found it
was present on our old EC12.)
LFI is an extended opcode for IILF.
If you use IILF, it will probably work.
Regards,
Emir Garza
Just my 2 cents but this makes sense. A few years ago, my company
(actually lead developer at the time and I) decided that we would
"standardize" on supported versions of IBM operating systems. z/SO 2.2 had
just gone 'end of life' and (per Peter's reference) required z10
hardware so that became o
IMHO that is a very useful way to think about and organize the available
instructions. The reference to the architecture level table in the z/OS
Planning guide is most helpful.
Merging that organization with the HLASM OPTABLE outputs might also be of some
use, though I suspect there may be s
Mike Shaw wrote
This _gold_ for ISVs writing code that must execute on many different z
models.
Thanks to Dan and Yves for all the work.
For Dan's, I'd suggest (somehow) adding a "key" to the 2-character facility
names (I know most of them, but many might not, so it could be helpful to have
