It is true that IDENTIFY searches things loaded by the invoking task. That is stated right at the beginning of the doc.
<snip> And - speaking of AMODE, it seems that IDENTIFY is supported in AMODE 64. But, I looked at the expansion of the macro and it seemed to only deal in 32-bit registers. </snip> I think that you have made this sort of (mistaken) statement before. Supporting calls in AMODE 64 has no necessary relationship to data above the bar or 64-bit registers. If a service does not say that it supports data above the bar, then the default is that it does not. That applies regardless of what AMODE you might be able to invoke the service in. Wouldn't it be nice if every service said one way or the other? Sure. But it was not felt that that justified the cost of doing so. Thus, as with compatibility, the default is what it used to be -- AMODE 64 is not supported and, even if it is, data is expected to be below 2G. As of z/OS 2.3, IDENTIFY supports ENTRY64 as an option. When you use IDENTIFY and ENTRY64 and are running on z/OS 2.3, you can identify an address that is above 2G as long as you have a module that is above 2G. (And if you used it on a release earlier than 2.3, it would not work.) Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
