Thomas David Rivers wrote:
I'm having some situations where IDENTIFY "sometimes" works, but sometimes it gives me a return-code of 12 in R15. Return code 12 says: Entry Address is not within an eligible load module; entry address was not added.
To follow-up - I think I know the problem. It seems that sometimes the IDENTIFY happens after an ATTACH, and the module was LOAD'd by the parent task, not the current task... so, the address being identified is not available to the current task. Will need to rework some logic to ensure the order is ATTACH LOAD IDENTIFY As far as the "sometimes" - it seems that was just a bug that got "lucky" when it worked; and unlucky when it didn't. Regarding some of the very good points/questions, there is no AMODE 24 here... and IDENTIFY does strip off the upper-bit for an AMODE 31 address (the doc indicates it does anyway.) 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. This would seem to mean that while you can issue IDENTIFY in AMODE 63, the given entry-point address must be below-the-bar, and the pointer to the name (for the EPLOC= parm) must also be below-the-bar. Seems like the doc could/should be updated to indicate that (I also did have SYSSTATE AMODE=64 specified.) I only looked at the expanded macro, I didn't actually look at the macro source, so maybe I'm using it wrong. - Thanks - - Dave Rivers - -- [email protected] Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
