I was trying to avoid the branch instruction. I guess in today's world where the CPU can actually follow both paths until the actual branch is taken, this is more of my silliness.
-- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Assembler List [mailto:ASSEMBLER- > [email protected]] On Behalf Of Binyamin Dissen > Sent: Monday, November 26, 2012 4:21 PM > To: [email protected] > Subject: Re: Stupid? though on a new "execute" instruction. > > On Mon, 26 Nov 2012 15:38:32 -0600 "McKown, John" > <[email protected]> wrote: > > :>OK, since I have you here anyway. What about a real weirdie? An > instruction which says whether or not to execute the next instruction, > based on the condition code? That would enable every instruction to be > a conditional instruction. Perhaps EXNC (Execute Next Conditional). > What comes to mind? Perhaps: > > What about simply > > Jc *+2/4/6 > > does exactly what you want > > > Can be done by a macro as well. > > -- > Binyamin Dissen <[email protected]> > http://www.dissensoftware.com > > Director, Dissen Software, Bar & Grill - Israel > > > Should you use the mailblocks package and expect a response from me, > you should preauthorize the dissensoftware.com domain. > > I very rarely bother responding to challenge/response systems, > especially those from irresponsible companies.
