Re: Interlocked Acess Facility 2
On 5/8/2021 6:05 AM, Peter Relson wrote: You haven't had to bifurcate your code like this since z/OS 2.2 which has the z11 as it's minimum requirement. Actually, there was no z/OS release that had z196 as its minimum requirement. z/OS 2.2's minimum is z10. z/OS 2.3's minimum is zEC12 (so includes z196). My bad. I had forgotten you guys jumped ahead two full generations (skipping over the z11) for the latest ALS! :-[ Regardless, it remains true that as of z/OS 2.3 (and thus for all in-full-support z/OS releases) you can rely on the availability of IAF2. We had the bifurcated code in a macro that now tests &SYSOSREL and doesn't even generate the FLC test and the OIL/NIL path at all for code targeted for z/OS 2.3 and higher. -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use.
Re: Interlocked Acess Facility 2
You haven't had to bifurcate your code like this since z/OS 2.2 which has the z11 as it's minimum requirement. Actually, there was no z/OS release that had z196 as its minimum requirement. z/OS 2.2's minimum is z10. z/OS 2.3's minimum is zEC12 (so includes z196). Regardless, it remains true that as of z/OS 2.3 (and thus for all in-full-support z/OS releases) you can rely on the availability of IAF2. Peter Relson z/OS Core Technology Design
Re: Interlocked Acess Facility 2
On 5/7/2021 3:42 PM, Keven Hall wrote: Based on my reading of the description of the Interlocked Access Facility 2, I'm led to assume that the following code paths are functionally equivalentt in a multi-threaded/mutli-processing application. If I assume in error, please feel at liberty to point out my folly. You are correct. The only difference in your two paths is register usage. IAF-2 has been standard ever since the z196 (z11) came out way back when. You haven't had to bifurcate your code like this since z/OS 2.2 which has the z11 as it's minimum requirement. And, that release is no longer in service. So, say good bye to OIL and NIL... -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use.