> I intended that literally, as I wrote it. Address range >x'80000000' - x'FFFFFFFF' is always a global guard area under z/OS. >There nothing you can specify on IARV64 which will cause z/OS to >create any virtual storage (or even a guard area which you request >via IARV64) in this address range. > >Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY >
But what is interesting is that if you specify a 31 bit address with the amode bit on in a SLIP Command, it is treated as a 64 bit address (which in all likelyhood will never be matched). I don't think this is WRONG, just unexpected fallout from an ISV that listed module starting addresses (for debugging) with the amode bit on (now fixed). Keith E. Moe Laid Back Software, Inc. http://www.laidbacksoftware.com (408) 749-0655 Creator of the TSO Environment and Administration Manager Product. Seeking employment and consulting opportunities with MVS. Located in Silicon Valley. Willing to Travel. Over 35 years in the industry (26 with one company). Resume: http://www.laidbacksoftware.com/resume.html Contact: [EMAIL PROTECTED] ---------------------------------------------------------------------- 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
