The LOAD ON CONDITION instruction is quite interesting, and the 'obvious' answer in this case. Thanks for pointing it out! Funny thing is, with the use of this instruction almost all cases where an SP macro would be used in the code I am working with has almost entirely disappeared. :-)
I am curious as to what particular cases people have used LOAD ON CONDITION and/or STORE ON CONDITION instructions. This particular case seems to me to be a bit of an outlier. It's useful here because this is a CICS XDLIPRE user exit, and it has to handle be invoked by a PL/I program where parameters are passed with a 'second level of indirection', if you will, but when invoked by COBOL or assembler there is only the "standard" one level of indirection. But what other more general cases are these instructions used for? Thanks! Frank -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, May 13, 2016 1:25 AM To: [email protected] Subject: Re: Structured Programming Macros Frank, you could extent your question to cover LOAD ON CONDITION... then the generated code would look like this: CLI R9,UEPPLI PLI PROG? LOC R8,0(R8),8 YES - FOLLOW POINTER MVC PCB,0(R8) MOVE PCB TO MESSAGE Does not need a label for branching But I highly doubt that the macros do yet support this. Notes: 1.) The original code used an X reg - which is not possible with LOC. But i highly doubt that this is correct. The last instr (the MVC) uses R8 in a normal position. So i guess there is no AR involved. 2.) The high number of eights in the LOC is not a mistake- - first register to load - second (in brackets) base for location to load from - condition under which the LOAD should be executed -- Martin Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE more at http://www.picapcpu.de The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you.
