I am using the IDENTIFY macro in the following way... 1. LOAD EP=PROGRAMA 2. Save returned entry point address (R0) in R3. 3. IDENTIFY EP=PROGRAMB,ENTRY=(R3) Sometimes, all the steps above may be repeated by code running under the same TCB. There are no intervening DELETEs for PROGRAMA. When it is repeated, the IDENTIFY macro usually results in R15=4, which is okay. However, in one scenario that I haven't been able to recreate, the IDENTIFY macro got an R15=8. According to the manual, it sounds like the entry for PROGRAMB already "exists" (which is true), but the entry point address in the entry is different that what is being passed in R3 this time. The only way I think this can happen is if PROGRAMA is deleted (without me knowing about it) and gets reloaded at a different address. Is there another way this can happen if everything is running under the same TCB? When this happens (R15=8), is PROGRAMB an "orphaned" entry since it seems to point to a load module that is no longer in storage (I don't have a dump to make sure that is the case)? Is there a way to "delete" the original IDENTIFY entry so it can be recreated, or is the entry name PROGRAMB unusable for the lifetime of the TCB? Is there a way to reuse the original IDENTIFY entry but have it point to the new load module, without having to chase entries and replace an address? FYI...PROGRAMA is really DFHSKTSK, a CICS general purpose subtask front end that is delivered as part of CICS. I'm simply trying to identify another name for it. Thanks, Ira W. Broussard
---------------------------------------------------------------------- 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
