On Wed, Jun 5, 2019 at 11:04 AM Steve Smith <[email protected]> wrote:
> Just test the O'opcode result. No guessing or research needed. > I have done that for some things. I am now looking at the EXECUTABLE=NO operand of the STORAGE OBTAIN. I already check the z/OS level "02.02.00" or greater to dual path my assembly code. But I have also read that although z/OS 2.3 will accept this operand, on anything less than a z14, it is ignored. So I am trying to make sure that the person assembling the code is targeting a z14 or above. I haven't found a way to determine that. I am doing initial work on a z/OS 1.12 system, so &SYSOPT_CURR_OPTABLE is not available on the HLASM on that system. I will give it a try on a z/OS 2.3 system which I can access. I don't do much on the 2.3 system because it belongs to a friend and _he_ pays for the work that I do. Yes, I am probably trying to over optimise. But this is what I am considering a learning experience. So I want to "push the envelope" to determine what I can, and cannot, do. > > sas > > -- This is clearly another case of too many mad scientists, and not enough hunchbacks. Maranatha! <>< John McKown
