On Mon, 17 Jul 2006 18:10:00 +0000 "Jeffrey D. Smith" <[EMAIL PROTECTED]> wrote:
:>=================================================== :>-----Original Message----- :>From: "Edward Jaffe" <[EMAIL PROTECTED]> :>Sent: 7/17/2006 11:46 AM :>To: "[email protected]" <[email protected]> :>Subject: Re: z/OS level for SETFRR for AMODE(64)? :>Jeffrey D. Smith wrote: :>> As an ISV, I don't have the luxury of coding to the :>> most current architecture. My code must still run on :>> ESA/390 which may not have those instructions. sigh... :>As an ISV?? (Guess I wouldn't know anything about that. ;-) FWIW, we use TAM, SAM31, and SAM64 when PSAZARCH says we can.) :>Weren't you the one asking if you could issue SETFRR in AMODE 64? In my experience, a program that runs in AMODE 64 looks a whole lot different (uses a different instruction set) than one that runs in AMODE 31. If you're running in AMODE 64, you have TAM, SAM31, and SAM64 available. If you're not running in AMODE 64, then it matters not if SETFRR allows it. :>If you try to use pointer-defined linkage (e.g., BSM) to manage your AMODE in all cases, watch out for the low order bit of the target address! (It has a different meaning in z/Architecture than in ESA/390: the difference between an AMODE switch and a specification exception due to an odd PSW.) You mean the higher bits in the registers that you use for work. A 64 bit caller will not have garbage bits in registers. -- 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. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
