Another way around this that I've seen is to load a non-reentrant module and modify it to point to your getmained program. Do an IDENTIFY to that glue code and then you can LINK/ATTACH etc.
In article <[EMAIL PROTECTED]> you wrote: > Well, he's not the only graybeard who didn't get that memo. I missed it > too. I just looked it up, and Ed is correct -- IDENTIFY *must* specify an > address within an already-loaded/fetched/etc. program. > Now why'd they go and do that? That means I can't use that old CompSci > trick of compile-to-memory-and-attach-task any more. Shucks. I remember > when I did that with Fortran arrays in college. > (I know, I know, it's all about security and integrity. No comments in that > area, please.) > Not the same thing, of course, but what does that restriction do for JIT > languages? ISTM that the IDENTIFY service would be useful there, except > that a JIT language compiles to dynamically-obtained memory, not to a load > module. > Peter -- Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive [EMAIL PROTECTED] (919) 531-5637 Cary, NC 27513 ---------------------------------------------------------------------- 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
