<snip>What does that mean? to me, "may not be able" sounds very close to "unpredictable".</snip> It's even closer to "you must not rely upon its being able". <snip>Looking at 2.5 WTO I don't see any qualifications about the location of control parameters other than in the primary address space, which would imply above the BAR is OK.
However, there is a general restriction "A program running in AMODE 64 should not call a service with data, parameters, or parameter addresses that are higher than 2 gigabytes, unless the individual service description indicates that it is allowed."</snip> There is no "implication". You have made an unfounded assumption. What is true (and, unfortunately, no one in IBM ever felt it worth the $$ to address) is that there was never an effort made (and likely never will be) to have all the services document their AMODE, RMODE (for code and, if you mis-apply the term "RMODE", data) requirements and restrictions with the advent of "64". That is why the "default" (which is the "assumption" and the "implication") is: not AMODE 64, not RMODE 64, not data above 2G. <snip>How many subscribers to this list are likely to see the joyous day when all services are supported in the highest available AMODE/RMDE (still 64 by then?), and even the initiator EXECs PGMs with 8-byte parameter addresses and they can be oblivious to the lower modes? I fear I won't make it.</snip> I'd say that no one will "make it". Even if all "services" support the highest AMODE/RMODE, changing the initiator would be wholly incompatible. That will never happen. Peter Relson ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
