PLO is an expensive instruction. It can do a little or a lot. There are about 10 pages in the POP to describe it. However, until transactional processing is supported in all environments, ISV's, who never know what environment they are running under, need to keep using the PLO instruction. OK, Peter, we could dual path it, but who likes to maintain dual paths?
Chris Blaicher Technical Architect Mainframe Development P: 201-930-8234 | M: 512-627-3803 E: [email protected] Syncsort Incorporated 2 Blue Hill Plaza #1563 Pearl River, NY 10965 www.syncsort.com Data quality leader Trillium Software is now a part of Syncsort. -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of John McKown Sent: Friday, August 11, 2017 9:10 AM To: MVS List Server 2 <[email protected]> Subject: Re: PLO <subject change: was Just Testing - It got very quiet> On Fri, Aug 11, 2017 at 6:23 AM, Peter Relson <[email protected]> wrote: > <snip> > does anyone know of good write-ups/presentations of PLO and its > capabilities and uses for an assembler programmer who knows how to use > CS and CDS. > </snip> > > My hope is that, going forward once you have a machine that supports > it and, for those who care about z/OS under z/VM, once/if it is > supported for z/OS running under z/VM, no one ever uses PLO again but > instead uses transactional execution, particularly TBEGINC for the simpler > cases. > > Peter Relson > z/OS Core Technology Design > Now, that is a very interesting statement. -- If you look around the poker table & don't see an obvious sucker, it's you. Maranatha! <>< John McKown
